COBie 2.4 · Asset guide
Connection
Captures logical connections between two Type records or two Component records.
Which asset-to-asset connections matter to operation or maintenance?
Describe operationally important connectivity
Connection identifies a logical relationship between two Type rows or two Component rows. SheetName selects the worksheet, RowName1 identifies the upstream item, and RowName2 identifies the downstream item. ConnectionType can distinguish relationships such as control, flow, return, supply, or structural connectivity.
Optional port names can identify the two connection points, and RealizingElement can name an item that makes the relationship possible. These fields are most useful when the receiving team needs to trace a service path, control dependency, or physical interface that cannot be understood from System membership alone.
Keep connection scope intentional
COBie is not a replacement for a full network model or detailed engineering schematic. Exporting every geometric adjacency or every connector can create a large table with little maintenance value. The project should identify the connection classes, systems, and level of detail that the owner will actually use.
The COBie 2.4 publication says Connection is not required for the U.S. facility and asset-management exchanges covered by its design and handover QC testing. It is tested when supplied and may still be required by a contract or another implementation. When included, both referenced rows must exist, direction should be applied consistently, and repeated or self-referencing relationships should be removed.
Using Revit connector evidence carefully
Revit MEP connectors, electrical circuits, controls parameters, and linked design models can supply candidate connections. Incomplete system modeling, capped connectors, fabrication detail, or discipline boundaries can make raw connectivity unreliable, so automated extraction still needs a reviewable transformation rule.
BIMRelay can retain the source context behind generated Component and Type records and validate Connection references against the active workbook. Reviewers can use the model to investigate the two endpoints while keeping supplemental, project-authored connection rows intact during later model refreshes.
Key relationships
Connects two Types or two Components
May describe ports, direction, or a realizing element
Practical quality checks
- Reference existing components
- Use consistent connection categories
- Record only operationally useful detail
Connection worksheet FAQ
- What is the COBie Connection worksheet?
- Connection records a meaningful logical or physical relationship between two COBie Types or two COBie Components, optionally including direction, ports, and a realizing element.
- How is Connection different from System?
- System records group membership. Connection describes a specific relationship between two endpoints, such as upstream and downstream flow or a control link.
- Does COBie require every model connector to be exported?
- No. Connection scope is normally contract-driven and should focus on relationships that are useful for operation, maintenance, or another defined exchange purpose.
- How can BIMRelay support Connection data?
- BIMRelay can validate each Connection endpoint against active Type or Component rows and preserve project-controlled connectivity while related Revit evidence is refreshed.
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