Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Correct organization of your Systems

dRofus databases classification must be setup before starting to link and Synchronize systems:

Add Classification to the database

We recommend reading: Introduction dRofus Systems

Relationship between Revit Systems and dRofus Systems

One-to-one relationship

To ensure alignment with the BIM data-model, dRofus Systems is based on a data-model that will be as aligned as possible with the data-model in BIM. Therefore you can create Systems and synchronize data consecutively between BIM-models and the database. This is dependent on correct organization of your Systems in the BIM-model:

  • All systems have a System item. System component or owner of a system?

  • System objects in Revit is equivalent to the System Component in dRofus and are Revit objects that can have Systems connected.

One to one Relationship

As with most BIM objects, Revit families consist of both: 

  • A type

  • An instance object.

Revit Family type will be known as Item in dRofus. Revit instance will be known as Occurrence in dRofus.

It should be a one to allows for creating and synchronizing Systems. In Revit, a Family Type consists of both a type and an instance object. The Revit Family type is linked with an Item in dRofus, while the Revit instance is linked with an Occurrence in dRofus. An Item Occurrence that owns a system is called System Component in dRofus and Occurrence that is part of a system is called Component in dRofus.

...

It is essential to maintain a one-to-one relationship between Revit Family types and Items in dRofus. This is important because an each item in dRofus can only have one :

...

Type classification and/or One pr Item?

...

number giving type and system classification.

...

Therefore, you cannot it is not possible to use the same Family type object for instance different instances that should have require different classifications. 

Example:

Same Family type object for electrical distribution with instance object that should have different classification:

  • 23-35 31 15 - Electrical distribution (Omniclass table 23)

  • 21-07 40 10 10 - Electrical Utility Services (Omniclass table 21).

Two separate Revit Family types will be needed to set those classifications.

System Organization.

We recommend assigning a family type instance as the owner to your Systems in Revit when using number giving classification, in order to ensure accurate generation of the classification number.

...

Below is an example of an Occurrence of an Item in dRofus, referred to as a System Component. The System Component, along with the system it belongs to, is imported from a Revit Family type instance that is owner of two systems within Revit. It is worth noting that the System Component in both Revit and dRofus is:

(1) Owner of two systems

(2) Connected as a component in two systems.

...

System Type or System Name

Revit have two levels of Systems for Mechanical and Piping Systems, (1) Revit System Types , (2) Revit System Name.

...

It is possible to switch between which levels the dRofus Systems should be synchronize with. However, to achieve optimal control, we advise using only one level for synchronization.

...

System Component:

In Revit System Browser the Family Type instance that is set to own one or more systems, have a folder icon under the System Type. This Instance is what we call in dRofus a System Component.

...

Child pages (Children Display)
alltrue