- Always keep family file size in mind. Get best solution with minimal file size. Avoid excessive use of voids and nesting where possible.
- Make sure that ALL unused nested and host families are purged in the Family Editor (This is an instance where I do recommend in purging) BEFORE loading into host family or Project file for testing.
- Lock geometry into Reference planes rather than into other geometry. See section on Reference Planes.
- Have a clearly defined, consistent Parameter naming convention. (Avoid abbreviations.) Ensure that these families are methodically made and linked with consistency in mind
- Model up the right level of detail for the desired outcome you wish to have.
- Think about the output and how the component may need to change or the various options users may need BEFORE you make the family. Add the correct restrictions; use Instance and Type parameters appropriately.
- Choose your type names well and with forethought. (See Type name section)
- Avoid Copying and pasting families across Project files
- Have a designated, experienced and well trained Content Creator/ Content Manager in your office or use professional Content creators. The “First in … all can have a go” approach is far from ideal.
- Set Origin point right the first time. Avoid changing Origin points of a family once it is in use in Projects. Changing Origins points after a family is in use negatively affects drafter confidence. If drafters experience families moving when re-loading they will be reluctant to reload any repaired families.
- Have good Subcategory naming conventions that can control family geometry through View Template. Subcategories are case specific. Be exact in your naming.
- Choose the appropriate Family Category. See Cuttable and Non-cuttable families in Help Menu. The category you choose will determine whether the item, when cut, will display as an elevation or section profile.
- Use Instance parameters if you want documenters to be able to adjust the family without creating new types.
- Use Type parameters if you want to control type information and force drafters to create a new type if a critical type value needs to change.
- Use formula ghosting of Parameters to protect important Parameter values or the relationships between parameters.
© Copyright Reserved by Michelle Louw (Excerpt from My speaker notes at National Revit Technology Conference 2008.)