COBie 2.4 · Project guide
Space
Records the rooms and functional areas used to locate assets and manage the facility.
Do the spaces match the owner’s operational room list?
Spaces connect design rooms to operations
The Space worksheet records the rooms and functional areas used to locate assets and organize facility operations. Space.Name is the primary key, and FloorName links every row to the level, roof, or site area that contains it. The list should align with the owner's operational room register, not simply reproduce every enclosed region found in a design model.
Names and descriptions should remain recognizable across drawings, signage, commissioning records, and the receiving facility system. If the project uses room numbers as Space.Name and human-readable labels as Description, that convention should be applied consistently. Duplicate room numbers across buildings or phases need to be resolved before they become workbook keys.
Room tags, height, and area values
RoomTag represents the delivered signage identifier, which may differ from the model's working room number. UsableHeight describes the occupied vertical extent, while GrossArea and NetArea must follow the AreaMeasurement method declared on Facility. These values should be checked against the contract's area rules rather than assumed from whichever boundary calculation happens to be active in Revit.
Spaces can also describe exterior regions on Floor rows categorized as Roof or Site. Whatever the location, each row should have a valid Floor reference and enough identity to support downstream Component locations, Zone membership, documents, issues, and attributes.
Turning Revit rooms into maintainable Space rows
Revit rooms and spaces provide geometry, level assignment, numbers, names, and calculated areas, but model quality directly affects the exchange. Unplaced rooms, redundant rooms, phase filters, linked-model boundaries, and naming collisions should be surfaced for review instead of silently exported as clean operational data.
BIMRelay generates Space rows from the selected Revit phase, keeps stable model identifiers, and lets reviewers select viewable rooms in the embedded model context. Column source settings can prioritize the project's actual Revit parameters, while explicit regeneration preserves compatible user edits and revalidates Floor references.
Key relationships
Belongs to a Floor
Grouped by Zone
Locates Components
Practical quality checks
- Use unique room identifiers
- Reconcile names with signage
- Check every space has a valid Floor
Space worksheet FAQ
- What is a Space in COBie 2.4?
- A Space is a uniquely named room or functional area assigned to a Floor row. Spaces provide the operational locations used by Components, Zones, documents, attributes, and other workbook records.
- Is Space.Name the same as a room name?
- It depends on the project convention. Space.Name must be unique and match the agreed project documents, while Description can carry a more readable room function or label.
- Where do COBie Space areas come from?
- GrossArea and NetArea may be calculated from model geometry, but they must follow the area-measurement convention declared on Facility and any project-specific boundary rules.
- Can BIMRelay create Space rows from Revit rooms?
- Yes. BIMRelay can generate Space evidence from the selected Revit phase, preserve model identity, and present the rows for model-backed review before COBie 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