The technical Items are often not planned in dRofus before Engineers starts working in dRofus. Therefore, the first step will often be to create designed objects (Family Types) as Items in dRofus.
As with most BIM objects, Revit families consist of both:
A type
An instance object.
It should be a one to one relationship between items in dRofus and Revit family types. This is important because an item in dRofus can only have one type and/or system classification. Therefore, you cannot use the same Family type object for occurrences that should have different classifications.
Note
We recommend that you create Family Types as items as early as possible and give the items the correct classification in dRofus. By doing this you will ensure a good result with correct classifications (codes in the project).
Example:
You cannot use the same family type object for electrical distribution if their occurrences should be classified with 23-35 31 15 - Electrical distribution (Omniclass table 23) and other occurrences should be classified as 21-07 40 10 10 - Electrical Utility Services (Omniclass table 21). Here you need to have two separate revit family types.
Note
One family type can only be associated to one System
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 objects in Revit is equivalent to the System Component in dRofus and are Revit objects that can have Systems connected.