The handover problem
On handover day, a giga-project produces two things: a finished building and a mountain of information about it. Models, drawings, datasheets, warranties, operation and maintenance manuals. Thousands of files.
The building is usually ready. The information often is not.
The facility management team opens the handover package and finds PDFs they cannot search, models they cannot load into their maintenance system, and equipment lists that do not match what was installed. The owner then pays a second time, to collect data that should have arrived with the keys.
COBie exists to prevent exactly this.
What is COBie?
COBie stands for Construction Operations Building information exchange. It is a structured format for handing over building asset information to the people who will operate and maintain it.
It is not software and it is not a 3D model. It is an agreed structure, usually delivered as a spreadsheet or exported from an IFC model, that lists what the owner needs to run the building and links each asset to its documents.
COBie was developed in the United States and is part of the US National BIM Standard (NBIMS-US), maintained by the National Institute of Building Sciences. In the UK it was adopted as a code of practice, BS 1192-4. Today it is widely used alongside ISO 19650 to deliver asset information in a form operations teams can actually use.
What COBie contains
COBie organises a building's information from the general to the specific. Select a group to see what it holds.
Facility, floors, spaces and zones
The building itself, its levels, every room and how rooms are grouped into zones, such as fire, HVAC or tenancy zones. This is the map every asset is placed on.
Types
One record for each kind of product: a model of chiller, pump or fire damper, with its manufacturer, model number, warranty terms and expected life. Fifty identical pumps share one type.
Components
Every individual maintainable asset, placed in its space: its tag, serial number, installation date and warranty start date. This is the asset register the maintenance team works from.
Systems
How components work together: the chilled water system, the fire alarm system, the domestic water system. When one part fails, the team sees everything it affects.
Documents, spares, jobs and resources
Warranties, manuals and certificates linked to the assets they cover, plus the spare parts, planned maintenance jobs and tools each type needs. This turns a list of equipment into a maintenance plan.
Why handover fails on large projects
On giga-projects the scale makes small gaps expensive. Many parties produce asset information: designers, contractors, subcontractors and suppliers. If nobody defines one structure, each delivers it their own way, and the gap shows up at handover. Switch between the two views below.
Without agreed requirements: every party delivers data its own way. It piles up at handover, and much of it never reaches the operations team in a usable form.
With COBie from day one: everyone fills the same structure as the project progresses, the data is checked against the requirements, and it flows straight into the maintenance system.
The same problems come up again and again:
- Requirements are defined too late. If nobody specifies the asset data at the start, contractors deliver whatever their own process produces.
- Data lives in documents, not in fields. A pump's serial number inside a PDF is useless to a CAFM system.
- No one checks the data before handover. Errors are found when operations start, after the contractor has left the site.
- Design data and as-built data drift apart. The model shows the specified equipment, not what was actually installed.
None of these are technology problems. They are requirements problems, and the owner is the only party who can fix them.
What owners should ask for, and when
Good handover data is planned from day one, not collected at the end. Select a stage to see what the owner should require.
1 · Brief and appointment
Write the Asset Information Requirements (AIR) into the contract: which assets to record, which attributes for each, the naming rules and the delivery format. If it is not in the appointment, it will not be delivered.
2 · Design
Agree the asset types and naming convention, and start the COBie data in the design model: spaces, zones and the types the design specifies.
3 · Construction
As equipment is installed, the contractor adds the real data: tags, serial numbers, installation dates and warranties. Data collected as the work happens is far more reliable than data collected from memory at the end.
4 · Before handover
Check the data against the agreed requirements, with errors fixed before acceptance, not after. Test that your CAFM or maintenance system can import the file without manual rework.
5 · Handover
Accept a validated COBie file as part of the Asset Information Model (AIM), alongside the as-built model. Someone on the owner's side signs off the data, just as they sign off the building.
How COBie fits with ISO 19650
ISO 19650 is the international framework for managing information across the life of a built asset, and it is the standard behind BIM requirements in Saudi Arabia. In ISO 19650 terms:
- The AIR (Asset Information Requirements) defines what the owner needs in order to operate the building.
- The AIM (Asset Information Model) is the information the owner receives at handover and keeps up to date in operation.
ISO 19650 does not mandate one file format. COBie is one of the most practical ways to structure the asset part of the AIM, so it moves cleanly from the project team to operations. With the Saudi BIM mandate for government buildings in effect since January 2024, owners now have a clear reason to define these requirements early.
Is your handover data ready?
Answer six questions to see where your project stands and the best next step.
Handover readiness check
Six questions, under a minute. Nothing is sent until you choose to contact us.
Answer all six to see your result.
From handover to a working building
Clean COBie data does more than close a contract. It is the foundation for everything that comes after:
- Planned maintenance in a CAFM or CMMS system, built on the real asset list.
- Faster repairs, because the technician has the right manual, spare part and warranty in hand.
- An operational digital twin, where live data from the building management system meets the asset register.
A digital twin built on incomplete data is only a 3D picture. Built on structured, checked asset data, it becomes a tool the operations team uses every day. Read more in our guide to digital twins for buildings in Saudi Arabia, or see how TwinMs runs buildings on that data.
Common mistakes on giga-projects
- Asking for "COBie" without saying what goes in it. Define which assets and which attributes. Not every door handle needs a maintenance record.
- Leaving it to the end. Data reconstructed after the contractor's team has moved on is incomplete and costly.
- Accepting a file without checking it. A COBie file that does not import is not a deliverable.
- Forgetting the operations team. Involve the people who will use the data when you write the requirements.
- Letting the data go stale. After handover, someone must own the asset register and keep it current.
Glossary
- COBie
- Construction Operations Building information exchange: a structured format for handing over asset information.
- AIR
- Asset Information Requirements: the ISO 19650 term for the information an owner needs to operate an asset.
- AIM
- Asset Information Model: the information the owner receives at handover and maintains in operation.
- CAFM
- Computer-aided facility management: software for space, assets and services.
- CMMS
- Computerised maintenance management system: where work orders are raised and closed.
- Asset register
- The list of every maintainable asset, with its location, details and documents.
- IFC
- Industry Foundation Classes: an open file format for exchanging BIM data between software.
- As-built model
- A BIM model that matches the building as it was actually built.
Questions and answers
What does COBie stand for?
Construction Operations Building information exchange. It is a structured format for handing over the information an owner needs to operate and maintain a building.
Is COBie software?
No. COBie is a data structure, usually delivered as a spreadsheet or exported from an IFC model. Most BIM and CAFM tools can create or import it.
Is COBie required in Saudi Arabia?
COBie is not named as a single national requirement. It is a practical way to meet the asset information requirements that owners set under ISO 19650, which sits behind BIM requirements on Saudi public projects. Each project should state what it needs in its contracts.
Who is responsible for producing COBie data?
The owner defines the requirements. Designers start the data, contractors and suppliers complete it as equipment is installed, and the owner checks and accepts it at handover.
When should COBie be planned?
At the start, when contracts are written. Adding it at the end costs more and produces less reliable data.
Can COBie be created for an existing building?
Yes. For an existing building, asset data is collected through surveys or scan to BIM and structured in the same way, so the building can be run from a reliable asset register.
How does COBie relate to a digital twin?
COBie provides the structured asset register a digital twin needs. The twin then connects that register to live data from the building's systems.
Sources and further reading
- National Institute of Building Sciences, NBIMS-US: COBie history and COBie structure.
- ISO 19650-1:2018, Organization and digitization of information about buildings, concepts and principles.
- ISO 19650-3:2020, Information management using BIM, operational phase of assets.
- BSI, BS 1192-4:2014, Fulfilling employer's information exchange requirements using COBie, code of practice.
Heading to handover on a large project?
A senior BIM lead reviews your asset information requirements and handover plan, and replies within 24 hours.
Review my handover requirements