COBie 2.4 · Asset guide
System
Groups components that work together to deliver a building service or operational function.
Can maintainers see which assets participate in each service system?
Describe assets that work together
The System worksheet groups Components that deliver a common building service or operational function. Examples can include supply air, chilled water, fire alarm, lighting control, security, or other owner-defined systems. A system is a functional grouping, so it can cross Floors and Spaces and can overlap with other systems.
COBie 2.4 uses the system name, category, and referenced Component as a compound identity. Each membership should be represented by its own row rather than a comma-delimited component list. That row-based structure makes missing assets, invalid references, and duplicate memberships easier to validate.
Set boundaries the operator can maintain
A System name should identify the actual service grouping, while Category describes what kind of system it is. The boundary should match how the owner commissions, isolates, inspects, and maintains the service. Exporting every analytical or temporary model system can overwhelm the receiving team with groups that have no lasting operational use.
A Component can belong to more than one System when each membership is meaningful. A pump might participate in a hydronic service, an emergency power group, and a controls network. Reviewers should therefore look for both omissions and inappropriate exclusivity rather than assuming every asset has exactly one system assignment.
Coordinating Revit systems for handover
Revit MEP systems, circuits, custom classification parameters, and linked discipline models can all contribute system evidence. Connectivity quality and naming vary widely, so the source and transformation rule for each COBie System category should be visible and repeatable.
BIMRelay can generate System membership from configured model evidence, connect each member to an existing Component row, and let reviewers inspect the participating assets in model context. Synchronizing the latest Revit versions from Autodesk Forma then refreshes evidence without discarding reviewed workbook values that still match.
Key relationships
Groups Components
May be linked to Documents and Attributes
Practical quality checks
- Use meaningful system boundaries
- Validate every Component name
- Allow components in multiple systems where appropriate
System worksheet FAQ
- What is the COBie System worksheet?
- The System worksheet groups Component rows that work together to provide a common service or operational function, independent of their physical Floor or Space locations.
- Can a COBie Component belong to multiple Systems?
- Yes. Multiple memberships are appropriate when each System represents a distinct, useful operational relationship.
- Should System.ComponentNames be comma-separated?
- COBie 2.4 favors one System membership row per Component. This is easier to validate and avoids ambiguity in delimited lists.
- Can BIMRelay build Systems from Revit MEP data?
- BIMRelay can map configured Revit system evidence to COBie memberships, validate the referenced Components, and provide model context for review before export.
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