Family & Category

Naming library objects (RFA): we must distinguish the Revit native library with the firm library. The Revit native library must not be modified. It is necessary to “Save As” before making any changes. The firm library gathers all the families common to all projects and can be added to as needed. RFA files will always have the prefix “ASA”, which will allow to quickly identify which library they come from. There will be no need to add ASA for all the different types of the same family.

FORMAT:

<CSI>_<Functional Type> ‐ <Subtype> ‐ <Manufacturer> ‐ <Descriptor 1> ‐ <Descriptor 2> ‐ <2D if necessary>

Description of fields:

Field/Component Required Description
CSI Required Two first digit of the CSI Masterformat code
Functional Type Required Names the element that the family creates (for example, Door or Window)
Subtype As needed Names the part type, for example, for a Window the subtype could be Casement.
Manufacturer Optional Manufacturer name
Descriptor As needed Material…
2D Required Use only for 2D families

GUIDELINES:

  • Use natural language to name the family. The family name should describe how the family is identified in the real world (i.e., Double Door, TV Stand, etc.).
  • If possible, do not include the family category in the family name, unless the functional type is the same as the category (e.g., window).
  • Capitalize Each Word (as with the title of a book) for family names, as they are case sensitive
  • Keep file names as short as possible. Family names must display in dialogs and in the Type Selector.
  • When adding optional descriptors to family file names, consider the order in which the descriptors are listed to ensure that the family files display in the Project Browser in the most logical and intuitive order.
  • To separate words within a syntax element (e.g., Manufacturer or Descriptor), use the underscore character (_).
  • If a hyphen (‐) is used to include a performance range, enclose the range in parentheses, for example, (230‐250_Ton).
  • If a type catalog is to be used with a family, name the type catalog (.txt file) with the same name as the family.

Examples:

08_Window – Double Hung – Acme – Tilting Sash – Clad

23_Chiller – Air Cooled – Acme – Low Profile – 2D

22_Fountain – Drinking – Acme – Polished Chrome_tgt

08_Window – Double Hung – Generic – Wood

23_Chiller – Air Cooled – Acme – Scroll – (75‐100_Ton) – Pkgd

Family Type

All families must include one predefined type. For families that create real‐world objects that are available in standard sizes, predefined types should be generated. Unless they represent nominal sizes, type names should include units or capacity, and include a unit indicator.

When naming a family type, use the format and guidelines below:

GUIDELINES:

  • Do not include the family name or category in the type name.
  • Type names should indicate the key differences between types (size, count, material) and, when applicable, reflect standard sizes. In some cases, you may base names on the actual type used in the project. If naming by size difference, use common terms rather than numbers.
  • When types are named by size, use dimensions only. Avoid the use of characters or words. (h, w, d, or height, width, depth).
  • Type names should include units or capacity and a unit indicator, unless they represent nominal sizes.
  • Metric types should reflect the local unit standard, unless the types are intended to be generic.
  • Keep type names as short as possible. Type names must display in dialogs and in the Type Selector.

FORMAT:

⇒ Unless there is a market‐specific reason to do otherwise, use the following general order in type names:

  • For doors and windows: Type(A)<width> x <height>
  • For casework and furniture:<width > x <height> x <depth>
  • For other element types: <width> x <depth> or <width> x <height>

For unit‐specific families:

  • For families with most sizes under 10’: fractional inch unit should be used
  • For families with most sizes over 10’: feet and fractional inch unit should be used
  • For families that feature nominal sizes or industry‐standard terms:

In type names, drop the dimension indicators (“,’, or mm) and/or use industry‐standard naming conventions.

  • Brick (industry‐standard naming): Common, Norman, CSR, Metric Modular
  • Lumber (nominal sizes): 2×4
  • Structure (industry‐standard naming): W12 x 204

For system families (wall, floor, roof, ceiling):

<TYPE (code)> – <Structure Thickness Type> ‐ <Finish (quantity) Type> – < Descriptor> – <Fire Rating>

Examples:

TYPE A – 11″ Interior Conc. – 2 HR

TYPE B – 6″ MTL Studs