Skip to content

COBie Requirements (BEP Chapter)

1. Purpose

This chapter defines the mandatory requirements for the creation, management, and delivery of COBie (Construction Operations Building Information Exchange) data. The purpose of these requirements is to ensure: - A consistent data structure across all disciplines - Unambiguous identification of assets - Compliance with COBie 2.4 and COBie NL - Compatibility with client Asset Information Models (AIM) and Common Data Environments (CDE)

These requirements apply to all modelling parties contributing to the federated project model.

2. General Requirements

2.1 COBie Standard

All COBie data shall comply with: - COBie 2.4 Deliverable Specification - COBie Responsibility Matrix - COBie NL (if applicable) - ISO 19650-2 - Client Information Delivery Milestones

2.2 Source of Truth

Revit models and other authoring tools are the primary source for COBie data. Manual editing of COBie sheets is not permitted.

2.3 Parameter Naming

COBie parameters shall use the Autodesk COBie Extension naming: COBie.Facility.Name, COBie.Component.Name, COBie.Type.Name, etc.

2.4 Data Type Requirements

  • String: A--Z, 0--9, _, -
  • Date: ISO 8601 (YYYY-MM-DD)
  • Number: Decimal point as .

3. Facility Requirements

3.1 COBie.Facility.Name

Purpose: Unique identifier for the facility.

Requirements: - Value must exist - Must be unique - Allowed characters: A--Z, 0--9, _, - - Must match the project code or building identifier

Example: P01234_BuildingA

3.2 COBie.Facility.Description

A concise facility description. May contain letters, numbers, and basic punctuation.

3.3 COBie.Facility.ProjectName

Must match the official project name defined in the BEP.

4. Floor Requirements

4.1 COBie.Floor.Name

  • Unique identifier per floor
  • Allowed characters: A--Z, 0--9, _, -
  • No spaces

Example: L01, B02, GND

4.2 COBie.Floor.Elevation

Must match the Revit level elevation.

5. Space Requirements

5.1 COBie.Space.Name

Unique identifier per space. Allowed: A--Z, 0--9, _, -

Example: 01.12, B1_023

5.2 COBie.Space.Category

Functional classification of the space.

5.3 COBie.Space.Description

Optional short description.

6. Type Requirements

6.1 COBie.Type.Name

  • Unique across the project
  • Must match FamilyType name
  • Allowed: A--Z, 0--9, _, -
  • No spaces

Example: AHU_Type_01

6.2 COBie.Type.Category

Must match the category or classification used in the BEP.

7. Component Requirements

7.1 COBie.Component.Name

Purpose: Unique identifier for each asset instance.

Requirements: - Value must exist - Must be unique - Allowed characters: A--Z, 0--9, _, - - No spaces - Typically mapped from Revit Mark

Examples: DR-00123, LGT_A2-045

7.2 COBie.Component.Description

Short description based on FamilyType.

7.3 COBie.Component.SerialNumber

Used for equipment with factory serial numbers.

7.4 COBie.Component.InstallationDate

Format: YYYY-MM-DD. Empty if unknown.

7.5 COBie.Component.TagNumber

Client asset tagging identifier.

7.6 COBie.Component.WarrantyStartDate

Warranty start date, ISO format.

8. System Requirements

8.1 COBie.System.Name

Unique identifier per system.

Example: HVAC_Zone_01

8.2 COBie.System.Category

Shall match the discipline classification.

9. Attribute Requirements

9.1 COBie.Attribute.Name

Derived from the associated parameter.

9.2 COBie.Attribute.Value

Must match the defined data type.

10. Document, Spare, and Resource Requirements

10.1 COBie.Document

Documents delivered per the Information Delivery Plan.

10.2 COBie.Spare

Delivered only if contractually required.

10.3 COBie.Resource

Delivered only if specified.

11. Responsibilities

Party Responsibility

Modelling Parties Populate COBie parameters Lead Appointed Party Verify compliance Information Manager Coordinate COBie validation Contractor Installation & warranty dates Client Approve deliverables

12. COBie QA and Validation

12.1 Automated Checks (DAQS)

Automated validation of: - Missing values - Invalid characters - Duplicates - Naming inconsistencies - Type ↔ Component mismatches - Date format correctness

12.2 Manual Checks

Manual review of: - Attribute completeness - Document links - Serial numbers - Warranty dates

13. Deliverables

  • COBie 2.4 spreadsheet
  • Federated model
  • Validation report
  • Authoring tool source files
  • Corrective action list