Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Revit Assembly Code - Type vs Instance -

Revit Assembly Code - Type vs Instance -

Hello everyone,


I wanted to bring to your attention an important matter regarding our clients' increasing BIM maturity and their rising expectations for our model deliverables.

 

One of the most frequently requested BIM requirements is the Uniformat Classification in our Revit families.

 

Currently, this parameter is set as a “type” parameter, which has led to several issues.

Changing this to an “instance” based parameter would effectively resolve many of these concerns.

 

Issues for the mechanical discipline

Case of Pipes, pipe fittings, pipe accessories, pipe insulation, flex pipes + equivalent Duct:

  • In mechanical design, we use a Pipe type (and Duct type) that represents a material (for example, black steel with threaded fittings), which is then used across different Uniformat categories (heating, cooling, plumbing, etc.).
  • Since the same material is used in different Uniformat categories and because the Assembly Code parameter is set at the Type level, we are forced to duplicate pipe types, pipe fittings, pipe accessories (and their Duct equivalents) solely to differentiate Uniformat codes.
  • Duplicating these elements creates challenges for model quality management.
  • With the Assembly Code parameter set at the Instance level, we would not need to duplicate families for Uniformat purposes.

These concerns occur in other disciplines as well.

1 Comment
edgar.contrerasH34KJ
Contributor

Limited Granularity (Type vs Instance)

  • The Assembly Code parameter is associated with the element type, which means all elements of the same type share the same code.
  • Issue: If two instances of the same type need different Uniformat codes (e.g., identical walls but with different functions), this is not possible without creating additional types → increases family management complexity.

Impact on Scheduling and Classification

  • Quantity schedules based on Uniformat become less accurate if the code cannot vary by instance.
  • This complicates classification by function (e.g., exterior walls vs. interior walls) without multiplying types.

Coordination with Standards and IFC

  • Uniformat codes are often used for IFC export or integration with cost systems.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea