Tuesday, September 3, 2013

A Rose Is A Rose: Shared Parameter Names

A rose by any other name is still a rose.  So, no matter what it is called, a rose will carry the same attributes.  It will look the same, smell the same and hopefully bring smiles to certain loved ones just the same.  Call it a Cinnamomeae and it is still the same flower.  Similarly, despite what a Shared Parameter is named, or even what group it is assigned to, it is possible for it to perform seamlessly with Models and Family files.

The most important attributes of a Shared Parameter are the Global Unique Identifier (GUID) value and the Datatype assignment.  The name and group can change without affecting the performance of the parameter.  Change the GUID and the Parameter is now a separate Shared Parameter.  Change the Datatype and risk corruption in a file and loss of that project.  Because of this, great care has been taken to only change the name and provide a starting point for the grouping of parameters.

As the Shared Parameters were sampled from manufacturer families, there began to develop a library of parameters that were found across many different sources.  As Shared Parameters are added to the Master File, the original name of the parameter is archived and a new name is given using the Labeling Convention (Reference Here) based on its properties and purpose.  The Labeling Convention will help identify the parameter as part of the Master Library, but won’t affect the Shared Parameter’s ability to function in a model that has not adopted the Labeling Convention.  

Families that have already been created using parameters from these existing libraries (AD 1-1) will still work, without any modification, in schedules that are being used by Families of the Labeling Convention (ME 1-2) as shown below.  As the existing families are inserted into a model following the Labeling Standard, the Shared Parameters will be labeled according to that standard.  Opening the Family, from within the model it has been loaded into, will also replace all the old names of the parameters with the new names.  Families originating from an existing library will work with new families following the Labeling Convention of the Master Library in the same Schedule, provided they are the same GUID, without doing any work.


Did anything else catch your attention?

-Craig

No comments:

Post a Comment