COBie 2.4 · Asset guide
Component
Lists each maintainable asset instance that the operator will locate, identify, and manage.
Can the operator identify each installed asset and where it is located?
The installed asset register
Component is the instance-level asset worksheet. Each row identifies one maintainable product or piece of equipment, with Component.Name as its unique key. TypeName connects the instance to shared product information, while Space places it in the operational location from which it is normally accessed or maintained.
The list should follow the agreed asset scope rather than export every modeled element. Operators generally need identifiable, maintainable assets, not every fitting, fastener, or decorative object in the authoring model. Naming rules must be defined for equipment that is scheduled only by Type in Revit so each delivered Component still receives a stable unique identifier.
From design identity to installed identity
During design, a Component may have a model identifier, name, type, space, and description while serial numbers and installation details remain unknown. At construction and handover, SerialNumber, InstallationDate, WarrantyStartDate, TagNumber, BarCode, and AssetIdentifier can be populated from installed equipment and commissioning records.
These fields should be captured at the milestone where they become verifiable. A serial number copied from a submittal may describe a product line rather than the unit installed on site. Final values should be reconciled with nameplates, tags, commissioning evidence, and owner asset-number conventions before import into a CMMS or CAFM platform.
Maintaining model-backed Component rows
A reliable Revit-to-COBie workflow retains the source model, version, element UniqueId, Type relationship, and spatial context behind each generated row. That evidence allows a reviewer to distinguish a renamed asset from a deleted and replaced asset and reduces the chance that synchronization creates duplicate Components.
BIMRelay extracts host and linked-model assets from the latest connected Revit version in Autodesk Forma, applies configurable asset inclusion and naming rules, and presents Component rows beside the model viewer. User edits survive regeneration when row identity matches, while Type and Space references are rechecked before export.
Key relationships
Belongs to a Type
Located in a Space
Grouped into Systems
Practical quality checks
- Use unique asset identifiers
- Validate Type and Space references
- Capture serial and tag data at the right milestone
Component worksheet FAQ
- What is a Component in COBie 2.4?
- A Component is one individual installed asset instance. It has a unique name, references a Type, and normally references the Space from which the asset is located or maintained.
- Does every Revit element belong on the Component worksheet?
- No. The project asset scope should determine which modeled elements are maintainable or operationally important enough to become COBie Components.
- What Space should be used for equipment that spans several rooms?
- COBie guidance uses the Space from which the equipment is most likely to be maintained when a Component cannot be assigned meaningfully to only one physical room.
- How does BIMRelay keep Components synchronized with Revit?
- BIMRelay retains stable source identity for generated rows, compares the latest host and linked-model evidence, preserves compatible user edits, and revalidates Type and Space references during regeneration.
This is an independent practical summary, not a reproduction of the COBie specification. Refer to the official standard for normative definitions and field requirements.
Reviewed against the official NIBS COBie 2.4 publication and Annex A worksheet schemas.
Where the official documents, contract-issued workbook, and project validator differ, follow the contract requirements and accepted validation process.
Open the official COBie 2.4 publicationOpen the official COBie 2.4 Annex A worksheet schemas