COBie 2.4 · Project guide

Facility

Sets the identity, classification, units, and project context for one facility.

Worksheet02Project setup
The question the Facility worksheet answers

Which clearly identified facility does this workbook describe?

The root record for a COBie workbook

Facility establishes the identity and measurement context for the workbook, with Facility.Name acting as the worksheet's primary key. Annex A presents one facility per COBie file as the normal delivery pattern, although its spreadsheet schema does not impose a one-row maximum. The contract-issued template and validator remain controlling when a project defines a different arrangement.

That root record anchors the Floor and Space hierarchy and tells a receiving system which project, site, and facility the remaining data describes. A vague working title can create confusion after handover, so Facility.Name, ProjectName, and SiteName should match the contract naming convention and the identifiers the owner intends to retain.

Units, area rules, and project context

Facility also declares the linear, area, volume, and currency units used across most of the workbook. AreaMeasurement records the agreed method behind reported floor and space areas. These values are small in number but high in consequence: a unit mismatch can make otherwise valid dimensions, quantities, costs, and coordinates misleading when imported downstream.

Description, ProjectDescription, SiteDescription, and Phase give the exchange enough context to be understood outside the authoring environment. Teams should agree these values before generating the workbook, document any owner-specific area convention, and avoid treating display settings in a model as proof that the exchange units are correct.

Building Facility data from Revit

Revit can provide project information, site information, units, and stable source identifiers, but the final Facility record still depends on contract decisions. The model may contain internal job names, legacy project numbers, or unit settings that are unsuitable for handover. A reliable mapping therefore combines model evidence with explicit project-controlled fallbacks.

BIMRelay keeps Facility mapping and source priority in workbook settings, uses the latest connected Revit model from Autodesk Forma, and retains the model identifiers needed to trace generated values. Teams can review the single Facility row, correct project-owned fields, and regenerate without turning unknown values into invented placeholders.

Key relationships

Parent context for Floor and Space

Defines workbook measurement units

Practical quality checks

  • Confirm the intended facility scope and naming
  • Verify units before data entry
  • Use the agreed classification system

Facility worksheet FAQ

What is the Facility worksheet in COBie 2.4?
Facility is the root worksheet that identifies the facility, project, and site and declares the main units and area-measurement convention used by the COBie workbook. Annex A describes one facility per file as the expected delivery arrangement.
Can one COBie workbook contain multiple Facility rows?
Annex A describes one facility per file as the expected delivery arrangement, while its spreadsheet schema gives Facility.Name a unique key and does not state a one-row maximum. Use one facility per workbook unless the contract-issued template and validator explicitly define another structure.
Why are units stored on the Facility worksheet?
The Facility unit fields establish how linear, area, volume, and currency values should be interpreted across most other worksheets. Declaring them once prevents each row from carrying its own unit convention.
Can BIMRelay generate Facility data from Revit?
BIMRelay can map Revit project evidence into the Facility row while letting the team control source priorities and contract-specific values. The result remains reviewable before workbook export.
Editorial scope

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