COBie 2.4 · Project guide
Zone
Groups spaces for a shared function such as occupancy, fire strategy, or service area.
Are operational groupings expressed independently from the floor hierarchy?
Zones are functional groups, not extra floors
A Zone groups Spaces that share an operational, regulatory, environmental, or service purpose. Typical uses include occupancy, fire alarm, lighting, circulation, preservation, and ventilation groupings. Because a Space can participate in several different purposes, Zones sit alongside the Floor hierarchy rather than replacing it.
COBie 2.4 identifies Zone membership with a compound key built from the zone name, category, and referenced Space. The workbook should use one membership row per Space. Older comma-delimited lists implied by the plural SpaceNames heading are deprecated in version 2.4 and are harder to validate reliably.
Designing useful zone boundaries
A useful Zone starts with a clear Category and a Name that describes the specific grouping. For example, 'East Wing' is ambiguous unless the category explains whether it is an occupancy area, fire alarm zone, lighting control area, or maintenance route. Category values should follow the contract or an agreed controlled list.
Membership should be checked in both directions: every Zone row must point to an existing Space, and the resulting group should contain the spaces the operator expects. Overlapping memberships are valid when they represent different purposes, but duplicate rows within the same zone and category add no information.
Creating Zones from coordinated model evidence
Revit may contain rooms, MEP spaces, zones, area schemes, and custom parameters that each express a different kind of grouping. The project must decide which source represents each COBie Zone category. Automatically treating every model zone as an operational zone can mix analytical HVAC groupings with owner-defined management areas.
BIMRelay lets teams map the model parameters that carry zone membership, generate one reference per Space, and inspect the underlying room or space context. The workbook can then validate every Space reference and preserve reviewed groupings when fresh model evidence is synchronized from Autodesk Forma.
Key relationships
Groups one or more Spaces
May classify several overlapping purposes
Practical quality checks
- Use agreed zone categories
- Validate every referenced Space
- Use one row per Space membership
Zone worksheet FAQ
- What is the Zone worksheet in COBie?
- The Zone worksheet groups existing Space rows by a shared purpose such as occupancy, fire alarm, lighting, circulation, or ventilation. It does not create another physical level hierarchy.
- Can one COBie Space belong to more than one Zone?
- Yes. A Space can belong to multiple Zones, especially when the Zones have different categories or operational purposes.
- Should Zone.SpaceNames contain a comma-separated list?
- COBie 2.4 deprecates the older plural-list approach. Use a separate Zone membership row for each referenced Space so the relationship can be validated directly.
- Can BIMRelay map Revit zones to COBie?
- BIMRelay can use configured Revit evidence to build Zone memberships, then validate the generated Space references and retain the reviewed rows through later model refreshes.
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