Correct organization of your Systems
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 one relationship between Revit Family types and Items in dRofus. This is important because an item in dRofus can only have one:
Type classification and/or One pr Item?
System classification.
Therefore, you cannot use the same Family type object for instance that should have 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.