Shared Parameters inside Family VS Project Parameters

[XXalessio.amodioXX]

Hi all,

I have several parameters to be displayed in schedule (e.g. Door Category: Door frame,door panel ...).

To do so I have created several Shared Parameters.

By your experience is more convenient add those paramenters inside the family or as Project Parameters?

I asked so because sometimes I fear prepare a family full of paramenters not in need in all project.

Any idea?

[Alfredo_Medina]

Use shared parameters if you want to use always the same parameters in different projects. If those parameters are brought into a project as Project Parameters, and assigned to doors, the door families do not need to have those parameters created in the family editor. You could enter the values for those parameters in the properties of your doors in a project, or in a door schedule.

[XXalessio.amodioXX]

Exactly. I am just asking, by your experience, which is the better or more conveninet workflow.

[Alfredo_Medina]

In your shared parameters file, create a new group for DOORS. In that group, create new parameters. Maybe all of them beginning with Door_ (or similar) to keep them group alphabetically. Then, in your projects, add those shared parameters as project parameters that apply to the Doors category. Then, all your door families will show those parameters in their properties.

[jkarben]

Adding them into your family allows you to predefine the parameter's value, which is often more convenient.

[Alfredo_Medina]

Yes, there isn't anything wrong with adding the shared parameters inside the family. It depends if the properties must come already with values or just blank to enter values in the project. Just keep things consistent. 

[HVAC-Novice]

It depends. If the parameter actually impacts the family (i.e. look or pressure drop, or voltage or something else) it should be shared parameter. 

If it is something that doesn't' actually change the family or the system attached, you can use either.

One thing to consider is that project parameters will show up in all family properties of the category. that may clutter up the properties. Like if you have overhead doors, and regular doors, ideally the OHD properties are not cluttered up with parameters only applicable to regular doors.  For mechanical equipment is worse since there are hundreds of different equipment that don't share many parameters. For example in a VAV box I had a min flow parameter, I don't want that to show up in boilers and pumps. 

No right or wrong, and trying it out within your project will tell you which works better. 

[ToanDN]

- Information that controls physical aspect of family components (dimensions, materials) shall be built-in or shared parameters in families
- Information that needs to be tagged shall be built-in or shared parameters in families
- Information that is applicable to only certain types of families shall be shared parameter in families
- Information that the sole purpose is for sorting, grouping, filtering in project shall be project parameters

[XXalessio.amodioXX]

Hi. That is a good point to start with. I asked because sometimes as BIM managers we have to deal with hundrends of parameters and families, and finding the most convenient workflow can same tons of time 

[XXalessio.amodioXX]

Hi, Thanks for your answer. Actually I am trying to find which could be the more convenient worflow. 

I was thinking that (e.g. Door_WithEPS (+/-) can be easly a Project parameter as has to be applied to the whole category)

[lumbera_darwin]

Hi @XXalessio.amodioXX 

If you want the shared parameter to show to every Doors for example, then create it as a Project Parameter.

If you just want to show it to specific elements (doors could be a Normal Door, Fire Shutter, Access Panel) , then create it as a Family parameter.

[XXalessio.amodioXX]

Hi @ToanDN 

What about 

-Information that has to be scheduled but not tagged (e.g. Frame material description (Text))?

[ToanDN]

---

@XXalessio.amodioXX wrote:

Hi @ToanDN 

What about 

-Information that has to be scheduled but not tagged (e.g. Frame material description (Text))?

---

I would use a shared parameter in families.

[XXalessio.amodioXX]

Thanks for suggestions

[RDAOU]

---

@XXalessio.amodioXX wrote:

Hi. That is a good point to start with. I asked because sometimes as BIM managers we have to deal with hundrends of parameters and families, and finding the most convenient workflow can same tons of time 

---

Technically speaking once the set up is there, it is not the BIM Manager who has to deal with the hundreds of  parameters and families, it is all other project stakeholders (each in their discipline). That being said considering that there are no SHALLS in BIM (only coulds and shoulds), what @Alfredo_Medina stated in reply 6 is the most sensible/reasonable reply "Keep things consistent" what needs to be predefined goes in the family and everything else can be either or as long as it is consistent