726
Edocuments platform needs to establish a connection to the model objects and O&M database.
The platform will deliver the COBie data so there is no need to add COBie data to the model objects or asset registers.
Note: All Field Values for both single (Mark) or group (Type Mark) assets must be unique and not duplicated.
3D Model Object Data
All model objects must be consistently named and data placed in the same field in all objects.
The Revit Object Field Name and Edocuments O&M Field Name must match exactly. These Names are usually the Designers or Clients reference used throughout the project documentation to denote the product/materials.
Minimum Data Fields - (Connect and exchange data between models + Edocuments database)
|
COBIe Name |
NIBS 3 Description (www.nibs.org/nbims) |
Edocuments Schedules |
Revit Model Field |
|---|---|---|---|
| Space.Name | the Space.Name must match the value found on design drawings at the equivalent project stage of the current deliverable. | Room Name |
Identity Data RoomName |
| Type.Name | the Type.Name must match the value found on design drawing schedules at the equivalent project stage of the current deliverable. | Type Ref |
Identity Data UNI_TypeMark |
| Type.Description | a general text description of the type. If description is present on desging drawings schedules, this value must match. | Description |
Identity Data UNI_TypeDescription |
| Component.Name | the Component.Name must match the value found on design drawing schedules at the equivalent project stage of the current deliverable. For equipment scheduled by Type (and not Component) naming requirements to ensure unique names for every component shall be specified by contract. | Asset Ref |
Identity Data UNI_Mark |
| n/a | the model object (instances) are required to be connected to an external database | n/a |
Identity Data UNI_ModelLink or UNI_CompValidate |
- UNI - Universal ID note that a project specific reference can be added as prefix to the model object field column name)
- Design Stage - mainly Type Data, with some Component data e.g. Doors, Fire Products or Equipment, (customer dependent).
- Construction Stage - Type and Component data required.
Fig 01 below show a Revit model object with data in the "UNI" which will also be in the Edocuments Equipment Schedules database Fig 02 so that the data will link.
Note that UNI_ModelLink checkbox must be clearly ticked as sometimes this appears to be ticked (grey background) but in fact has not and therefore provides a null value.
Fig 01: Screenshot of Revit Object Identity Data
Fig 02: Edocuments Schedules database with same TypeMark.
Examples
The naming and numbering convention below are examples, typically following designers naming and numbering conventions. These should be consistently used by all content providers - sub-contractors, suppliers, manufacturers, commissioning teams.
- Unique Asset (Component) - A quantity of 1. e.g. Door, AHU, Distribution Board
- Group Asset (Type) - A quantity of >1. e.g. Walls, Partitions, Valves, Luminaires
- Model Link - connects models to O&M's. (validate and push/pull data from models)
To connect a Revit model to the Edocuments platform, the "UNI_ModelLink" must be selected. This enables data validation and synchronization between the two platforms. Once linked, Edocuments O&M can be configured to add, validate, and export information to COBie, Asset Register, or CAFM systems.
Other reading you may find of interest:
Can I add more data into the models for transfer to Springboard?
