Performance and Best Practice for paramters

[tnievesP53K8]

Hello! We are in the process of cleaning our templates and unifying across our 4 offices.

I have always wondered myself when it comes to parameters, what is best practice for number of parameters or does it matter or affect performance? We have many parameters that could probably be combined if named slightly differently, but if there is no real benefit then I will leave them separate. Some in our office like to be explicit in naming so for example, "Door Type" instead of something that is more encompassing to any family.

[HVAC-Novice]

You mean shared parameters? Probably depends on what exactly you do with them. I use same-type parameters in all categories. Like apparent power and so on will be the same parameter for electrical and mechanical equipment. 

I don't know if it saves computing resources, it may. But for managing parameters it would be helpful to not have redundant parameters. 

Note you can't rename them. You need to create new ones and re-insert them into the families and schedules. 

While you create new ones, think about a somewhat logical naming scheme that works for you. My shared parameters all are capitalized and start with "SHARED_" that way I always see in properties which ones are the one is created for one reason or another. YMMV.