COBie and Structured Handover Data

Information only — not legal advice.

COBie stands for Construction to Operations Building information exchange. It is a structured approach to exchanging information about assets that an owner needs to operate and maintain. A handover should let an operator identify equipment, find it, understand what it is and retrieve the information needed to look after it. The NIBS COBie overview describes this operational purpose.

Imagine receiving 400 manuals with filenames such as “final2.pdf.” They may contain useful information, but the operator still has to discover which manual belongs to which installed asset. Structured handover data makes those relationships explicit.

First agree the version and delivery rules

COBie has evolved. Projects still use version 2.4, while NIBS has published version 3. Version 3 changes some table and field names, including Floor to Level, and supports JSON exchange. Use the version and requirements specified by the receiving organization; do not mix headings from different versions. NIBS: version 3 changes.

The example below is a simplified teaching model. It omits mandatory exchange fields and is not an import-ready or validated COBie deliverable.

Follow one asset through a fictional library

• Facility: LIB-01, the Meadow Library building.
• Level: L01, its first level. A version 2.4 exchange uses the corresponding Floor structure.
• Space: L01-PLANT, the plant room on that level.
• Type: AHU-T01, a specified model of air-handling unit. Shared product characteristics belong to this type.
• Component: AHU-001, the actual installed unit, serial DEMO-7841, located in L01-PLANT and linked to AHU-T01.
• System: VENT-01, the ventilation system to which the installed unit belongs.
• Document: DOC-021, the applicable operating manual, linked to the appropriate type or component.
• Job: a maintenance task associated with the relevant asset information, with its agreed interval and supporting instructions.

These are illustrative relationships, not exact column headings. The required schema defines the fields and reference rules.

Type and component: the distinction that matters

Suppose the library has a second unit, AHU-002, of the same model. Both components refer to AHU-T01. The common product description does not need to become two conflicting descriptions. Each installed unit still needs its own identifier, serial number, location and relevant installation information.

If the second unit is a different model, it needs the correct type relationship. Copying the first unit's serial number or manual to make a row look complete creates misleading data.

What the operator should be able to do

A technician receives an alert for AHU-001. They locate the plant room, identify the installed unit, open its applicable manual, check the service requirement and identify the warranty contact. They can distinguish this unit from AHU-002 without reading every project PDF.

A drawing or BIM model may help locate and coordinate assets. COBie data supports structured operational information exchange; a populated spreadsheet does not replace all geometry, commissioning evidence or contractual handover requirements.

Collect information progressively

1. Define requirements: the owner specifies maintainable assets, required information, version, formats, milestones and acceptance tests.
2. Design: establish spaces, intended types and stable references.
3. Procurement: suppliers provide product information and supporting documents.
4. Installation: confirm what was actually installed, including identifiers, locations and serial numbers.
5. Commissioning: link test results and resolve discrepancies.
6. Handover: validate relationships, transfer documents and test the receiving system with a representative sample before final acceptance.

Assign both a data supplier and reviewer for each requirement. This follows the early-planning approach in the NIBS COBie process guidance.

Three common errors and how to catch them

Broken reference: AHU-001 points to type AHU-T99, which does not exist. Check relationships, not just whether cells contain text.

Wrong evidence: the linked manual describes another model. Open the document and compare it with the installed equipment.

Unreadable handover: all links work for the contractor but require an account the owner does not have. Test with the intended recipient's access and agreed delivery location.

Also check duplicate identifiers, units, date formats and agreed rules for unknown or not-applicable values. Do not invent serial numbers or enter zero where the information is unknown.

How much COBie is enough?

The owner and project requirements determine the deliverable. Agree operational questions first, then select the required information and validation rules. A small accurate dataset that meets agreed requirements is more useful than a large unchecked export.

Related reading: Common Data Environments, Project Workspace Setup and Meeting Minutes and Action Registers, including the handover action template.

Important information

This article provides general information and does not constitute legal advice or replace a qualified professional's assessment of your circumstances. Laws, official guidance, standards and product features can change. Check current primary sources and the requirements applicable to your jurisdiction, contract and project before making decisions. Examples illustrate the discussion; they are not official rulings or instructions for a particular case. For legal decisions, consult a qualified lawyer; for technical or other specialist matters, consult the responsible professional.