This is a delivery-method resource, not project-specific design. Electrical protection, cable sizing, cooling capacity, fire strategy and structural loads require the appointed designers and the applicable codes. Technical review of this cluster by a named senior BIM/MEP lead is pending; do not treat it as sealed guidance.
Handover is the transfer of information from delivery to operation. ISO 19650-1 explicitly includes the operational phase in its scope — information management using BIM is not only a design activity. But what information, in what form, for what use? The answers must be specified at the start, not discovered at handover.
What BIM handover actually means
There is no single definition. Handover requirements vary by client, asset type, operational strategy and contractual structure. What is common is that the information produced during delivery must transition to whoever operates the asset. That may include:
- Federated models representing as-constructed geometry.
- Asset data in structured formats (COBie, IFC, proprietary FM system feeds).
- O&M documentation linked to model elements or asset registers.
- Commissioning records, test results, certificates.
- Access to the CDE or export from it.
As-built honesty
As-built is a promise that the model reflects what was constructed. On data-centre projects with dense MEP, RFIs, site changes and late vendor adjustments, that promise is hard to keep. Honest practice:
- Define what as-built means in the appointment — full geometric update, or confirmed-against-record-drawings.
- State the information state at handover — Published / Archived / As-Constructed.
- Document known deviations: where the model differs from installed condition and why.
- Do not claim digital twin for a model that has never been reconciled against site reality.
AIM realities
ISO 19650 distinguishes the Project Information Model (PIM) during delivery from the Asset Information Model (AIM) in operation. The AIM is not the PIM with a new filename. It may contain different data, at different granularity, structured for FM and operational queries rather than coordination.
PIM vs AIM
| Aspect | PIM (delivery) | AIM (operation) |
|---|---|---|
| Purpose | Design, coordination, construction | Operation, maintenance, asset management |
| Geometry | Design intent, coordination accuracy | As-installed, updated after changes |
| Data | Design parameters, construction scheduling | Asset IDs, maintenance schedules, warranty info |
| Ownership | Delivery team | Client / FM operator |
| Update cadence | Per coordination cycle | Per maintenance event or asset change |
Commissioning and the model
Commissioning (Cx) is the process of verifying that systems perform as designed. BIM can support commissioning by:
- Locating equipment — the model helps identify what is where, reducing search time on site.
- Linking to commissioning checklists — if asset parameters are structured, checklists can reference model elements.
- Tracking completion — commissioning status as an attribute visible in the model or linked register.
- Recording test results — attached documents, linked databases, or structured parameters.
BIM does not perform the commissioning. Functional tests, load tests, witnessed run-ups, integrated systems testing — all require physical presence and engineering judgement. The model is a locator and a record container, not a substitute for the commissioning engineer.
What BIM cannot replace at handover
- Commissioning witness and sign-off — professional judgement is not geometric.
- O&M manuals — unless they were created as linked data from the start.
- Certificates and statutory approvals — the model can reference them, not substitute them.
- Training — operators need training, not a federated model dropped on them.
- Ongoing FM input — if FM does not know how to query the model, it becomes a static archive.
Common handover failures
Handover requirements undefined until project end
Why it happens. We will figure out what FM needs later.
Impact. Data gaps, scramble to extract COBie, no AIM.
Mitigation. Define handover requirements in EIR/BEP at start.
Design model called as-built without update
Why it happens. No budget or time for as-built reconciliation.
Impact. FM uses inaccurate model; trust erodes.
Mitigation. Be honest about information state at handover.
Digital twin claimed without infrastructure
Why it happens. Marketing language entered the appointment.
Impact. Model is static; no live data integration exists.
Mitigation. Digital twin is a capability, not a file format. Specify what it means.
FM cannot access or query the model
Why it happens. No license, training or compatible software.
Impact. Model archived, never used.
Mitigation. Handover includes access path, viewer and training.
FAQ
- Is COBie mandatory for handover?
- Only if the appointment specifies it. COBie (Construction Operations Building information exchange) is one structured format for asset data. Alternatives exist (IFC, proprietary FM schemas). The UK Government Soft Landings programme and some public clients require COBie, but it is not universal.
- What format should the handover model use?
- Define it in the EIR. Common options: native Revit, IFC (for open archival), NWD (for Navisworks viewing). Consider what software the FM team actually uses.
- Can we hand over a model without site updates?
- Yes, if the appointment allows it. Many projects hand over a coordination model or design-intent model with a documented statement that it does not reflect site variations. Be explicit about the information state.
- Does ISO 19650 require a digital twin?
- No. ISO 19650 is an information-management framework. Digital twin describes a broader concept involving live data integration. The standards do not mandate it.
Sources
- 1. ISO, ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Part 1: Concepts and principles (2018). https://www.iso.org/standard/68078.html. Accessed 2026-09-03.
- 2. ISO, ISO 19650-2:2018 — Information management using building information modelling — Part 2: Delivery phase of the assets (2018). https://www.iso.org/standard/68080.html. Accessed 2026-09-03.
- 3. BSI, ISO 19650 — Building Information Modelling (BIM) (2026). https://www.bsigroup.com/en-GB/products-and-services/standards/iso-19650-building-information-modelling-bim/. Accessed 2026-09-03.
- 4. UK BIM Framework, Information management according to BS EN ISO 19650 — Guidance Part 1: Concepts (2nd edition) (2019). https://ukbimframework.org/wp-content/uploads/2019/10/Information-Management-according-to-BS-EN-ISO-19650_-Guidance-Part-1_Concepts_2ndEdition.pdf. Accessed 2026-09-03.
- 5. buildingSMART International, Industry Foundation Classes (IFC) (2024). https://technical.buildingsmart.org/standards/ifc/. Accessed 2026-09-03.
