Multiple Shared Parameter Files used in a project - Best Practice?

[Anonymous]

We are juggling with the prospects of multiple shared parameter files being in use on BIM Level 2 projects.

Essentially are looking at having 3 or 4 potential Shared Parameter Files:

1. Office Standard Shared Parameters - parameters used for office standard content/templates
2. NBS Create (Specifications) Shared Parameters - created and used by NBS Create Plugin to bring project parameters into project for associating elements with specification clauses.
3. COBie (Asset information) Shared Parameters - Standard file used by COBie plugin to apply parameters
4. BIM Collaborative Team - potentially a separate shared parameter file being suggested by Project BIM Information Manager to standardise parameters across whole project (architecture, Structures, MEP, Infrastructure etc..) - Potentially for client requested standard asset information parameters not included in COBie that are to be standardised across all disciplines.

It seems that we can switch from using one file to another manually as and when we are pulling a shared parameter into a project. In addition, running one of the plugins (COBie / NBS) automatically switches the 'current' shared parameter file in order to apply that specific parameter set.

Anyone have any experience of working with multiple shared parameter files?

Is this a common approach, or are there any issues with working this way?

Any advise would really be appreciated,

Thanks,

Martin

[kadmonkee]

i would suggest avoiding that.

we are currently cleaning up multiple shared parameter files and finding that they share the same parameter names but point to a different parameter, and the other way around they share the same parameter but use a different parameter name.

i would create groups inside the (1) shared parameter file and do my selection this way.

it reduces the users from a wrong selection or assignment from a conflicting shared parameter file.

you could combine the (2) files into (1) and create a group for NBS and another group for COBie and place all relevant parameters into their respective groups.

regardless of the use of plugins to accomplish a common practice (use of Shared Parameters) this method seems to keep it simple. 

[Anonymous]

Thanks for the response,

Combining them doesn't seem to be an option (although it is possible that we missing something)

We are using plugins for:

NBS Create (for linking specifications to model content)

COBie (for asset information export from specific parameters)

both of which appear to generate their parameters and assign them to the model as project parameters - from their own shared parameter files that come with installation of those plugins, the specific plugins would be hardcoded to look for their own file (not spotted any options to redirect either of them).

We would be keen to avoid any manual combining as it introduces the risks of control over versioning etc. for those parameters sets.

Thanks,

Martin

[kadmonkee]

as I am not too familiar with those particular plugins, I would guess if they work well together maybe that is all.

if it turns out to be another thing to have to manage, then it could cause issues.

or if the plugin acts up, what is the back-up plan.