Asset Information and Handover Data in BIM

Information only — not legal advice.

Asset information handover succeeds when the receiving organisation can use the information to operate, maintain and change the real asset. Delivering a large folder or detailed model is not enough if records cannot be linked to equipment, documents cannot be opened or nobody confirms what was installed.

Start with the operator's tasks and test the receiving process early.

Define the operational questions

A maintainer may need to locate a component, identify a spare part, read a procedure or find commissioning evidence. An asset manager may need system relationships, condition, warranty dates or replacement planning information.

For each agreed task, specify the required objects, fields, documents, format, responsible contributor and acceptance check. Limit the dataset to information with a defined purpose, while meeting applicable contractual and legal requirements.

Example: handing over an air-handling unit

A fictional handover package links the installed unit's unique asset identifier to its location, system, manufacturer, model, serial number, commissioning record, operating instructions and maintenance requirements. The same identifier appears consistently in the register and relevant drawings or model objects.

The operator tests the package by locating the real unit, checking its identity and opening the correct maintenance instructions. A second test imports representative records into the receiving system and checks that document links and relationships survive.

These tests reveal problems that a simple “all fields filled” report would miss, such as a generic manual for a different equipment variant.

Allocate data ownership before procurement

Designers, manufacturers, installers, commissioning teams and the operator know different facts. Assign each required field to its source and the party responsible for confirming it. Set collection dates that match when the information becomes available.

Keep provisional design information distinguishable from verified installed information. A model labelled “as built” should have an agreed verification basis; the label alone does not prove correspondence with the physical asset.

Check at several levels

• Structure: agreed format, schema, identifiers and field definitions.
• Completeness: required assets and information are present for the delivery stage.
• Validity: units, permitted values, uniqueness and relationships follow the agreed rules.
• Evidence: records refer to the actual installed asset and accepted documents.
• Usability: the operator can import, find and read the information using its working tools.

Use automated checks for suitable fields and representative physical or documentary verification for facts that software cannot establish. Record the sample and limitations rather than claiming every installed item was inspected when it was not.

Make acceptance and maintenance explicit

Use a delivery manifest, defect list and acceptance record. Identify remaining exceptions, owners and deadlines, and define whether any exception prevents the intended operational use. Agree who updates the information after replacements and alterations; handover is the start of operational stewardship.

COBie in NBIMS-US Version 4 is one structured information-exchange reference. The exact version, fields and delivery form must be agreed and tested; COBie is not universally mandatory. Read the COBie guide, information requirements and data ownership for the connected decisions.

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.