Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

To ensure alignment with the BIM data-model, dRofus Systems is based on a data-model that 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.

Correct organization of your Systems is crucial for synchronizing data between BIM-models and the dRofus database. To achieve this, all Systems in the BIM-model must be owned by a single Family Type instance that corresponds to the System Component in dRofus.

Above is an example of an Occurrence of an Item in dRofus that is a System Component. It is imported from Revit and linked to a family type instance. The System Component is (1) connected and owner of two systems, (2) Connected as a component in two systems.

It is essential to maintain a one-to-one relationship between Revit Family types and Items in dRofus. This is because each item in dRofus can only have one type and system classification. Therefore, it is not possible to use the same Family type object for different instances that 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.

Hvorfor kan ikke disse to benyttes?

System Type that has been created systems for

When creating a system in Revit and selected equitment (adding a system Component has been added to the system you will see it in the listing):

  • No labels