Handover, Facility Management and Digital Twins

Introduction and context

Building Information Modelling (BIM) is often presented as a design and construction technology, but its greatest strategic value may arise after practical completion. Buildings and infrastructure remain in service for decades, and the cost of operating, maintaining, adapting and eventually decommissioning an asset commonly exceeds its initial construction cost. Handover therefore should not be treated as the final administrative event in a project. It is the controlled transfer of reliable asset information, systems knowledge, responsibilities and operational capability to the owner and facility-management (FM) organization.

A successful handover connects project information with operational requirements. It enables facility managers to locate equipment, understand its characteristics, access maintenance instructions, verify warranties, plan statutory inspections and respond to faults. Increasingly, this information is connected to computer-aided facility management (CAFM) systems, computerized maintenance-management systems (CMMS), building-management systems (BMS), Internet of Things (IoT) sensors and digital-twin platforms.

The central challenge is not merely producing a geometrically accurate model. It is ensuring that information is structured, verified, authorized, secure and usable for decisions throughout the asset life cycle.

Learning objectives

By the end of this chapter, students should be able to:

1. Explain the purpose and principles of information handover and commissioning.
2. Distinguish design, construction, as-built, asset and operational information.
3. Develop an asset-information delivery strategy linked to an owner’s information requirements.
4. Explain how BIM connects with CAFM, CMMS, BMS, sensors and digital twins.
5. Evaluate information quality, interoperability, security and governance risks.
6. Apply lifecycle thinking to maintenance, renewal and operational decision-making.
7. Analyze a practical handover and digital-twin implementation scenario.

1. From project completion to operational readiness

1.1 Handover as an information process

Traditional handover may consist of drawings, operation and maintenance manuals, test certificates, warranties and training records delivered in boxes or disconnected folders. Such a package can be technically complete but operationally ineffective. Facility personnel need information that is searchable, linked to physical assets and presented in a form appropriate to their work.

BIM-enabled handover is a managed process in which information is progressively developed, checked and approved. It includes:

• identification of maintainable and replaceable assets;
• verified location and spatial relationships;
• technical characteristics such as capacity, manufacturer and model;
• commissioning and performance evidence;
• inspection, testing and certification records;
• warranty, replacement and service information;
• operational procedures and safety requirements;
• asset identifiers that can be used consistently across systems;
• information about responsibilities, approval status and revision history.

The handover deliverable is therefore not simply a model file. It is an integrated information set containing structured data, documents, geometry, relationships and evidence.

1.2 Information requirements and the information delivery cycle

A reliable process begins with the owner’s information requirements. These should describe the decisions that the owner and FM team must make, rather than merely requesting “a complete BIM model.” Requirements may include locating shut-off valves, scheduling air-handling-unit maintenance, demonstrating energy performance, managing room bookings or planning future refurbishment.

A typical information hierarchy is:

The exact terminology varies among standards and organizations. The important principle is that information requirements should precede modelling effort. Unnecessary detail increases cost, file size and maintenance burden, while missing information reduces operational value.

The information delivery cycle can be represented as a sequence:

Figure: Information delivery cycle from requirements through operation, with feedback into future requirements.

2. Asset information and as-built records

2.1 What constitutes an asset?

An asset is an item that has potential or actual value to an organization. In facility management, the term normally refers to equipment, systems, spaces, fabric elements and infrastructure whose performance, maintenance or replacement must be managed. Not every modelled object should become a managed asset. A decorative object may need geometry for design coordination but no maintenance record. Conversely, a concealed valve may require an operational record even though it has little visual prominence.

Asset classification should reflect operational decisions. Common classes include:

• building fabric: roofs, doors, windows and finishes;
• mechanical systems: boilers, pumps, fans, chillers and air-handling units;
• electrical systems: switchboards, generators, transformers and emergency lighting;
• public-health systems: tanks, pumps, sanitary fixtures and treatment equipment;
• life-safety systems: fire alarms, sprinklers, smoke-control equipment and emergency exits;
• vertical transportation: lifts and escalators;
• external works and civil infrastructure: drainage, roads, lighting and utilities;
• spaces and zones: rooms, plant areas, circulation areas and occupancy zones.

2.2 Asset attributes and relationships

An asset record commonly includes an identifier, name, classification, location, system association, manufacturer, model, serial number, capacity, installation date, expected service life, warranty details, maintenance requirements, responsible party and links to documents. The appropriate attributes depend on the asset class and intended use.

Relationships are as important as attributes. A pump may belong to a chilled-water system, serve a particular zone, be located in a plant room and be connected to a control panel. These relationships support fault diagnosis and planned maintenance. A list of isolated equipment records cannot provide the same understanding.

A practical asset information schema should define:

1. a unique identifier and naming convention;
2. allowed values and units for each attribute;
3. mandatory and optional fields;
4. classification codes;
5. links between assets, spaces, systems and documents;
6. responsibility for creating and approving each field;
7. a method for recording uncertainty or information status.

2.3 As-built information is verified information

“As-built” should not mean that the design model was simply renamed at project completion. Construction changes, substitutions, site routing, access panels and commissioning adjustments must be incorporated and supported by evidence. Depending on the asset, evidence can include installation inspection, photographs, test results, laser scanning, survey data, manufacturer documentation and signed checklists.

The appropriate level of geometric detail depends on use. A facility manager may need the accurate location and clearance zone of a major air-handling unit, but not every internal component. Overly detailed models are difficult to validate and maintain. The objective is fitness for purpose, not maximum detail.

3. Commissioning and operational readiness

Commissioning is the systematic process of verifying that building systems are installed, functionally tested, integrated and capable of meeting the owner’s operational requirements. It is broader than checking whether equipment starts. It examines whether systems work together under normal, abnormal and emergency conditions.

A commissioning process commonly includes:

• review of owner requirements and design intent;
• commissioning planning and responsibility assignment;
• inspection of installation and accessibility;
• equipment start-up and pre-functional checks;
• functional performance tests;
• integrated systems testing;
• correction of deficiencies;
• training and transfer of operating knowledge;
• completion of records and seasonal or deferred testing.

For example, a fire alarm signal may need to start smoke extraction, release magnetic door holders, control lifts and notify a monitoring centre. Testing only the fire alarm panel would not demonstrate the integrated performance of the life-safety strategy.

Commissioning evidence should be linked to the relevant asset and system. A test record should identify the equipment, test date, test conditions, measured result, acceptance criterion, person conducting the test, witness, deficiencies and final status. This makes the information useful during future audits and fault investigations.

3.1 Handover gates

A staged approach reduces the risk of discovering information deficiencies at practical completion. Useful gates include:

• requirements gate: operational uses and information requirements approved;
• design gate: maintainable assets and data requirements identified;
• installation gate: equipment and locations verified;
• pre-commissioning gate: installation checks complete;
• functional testing gate: individual and integrated tests passed;
• information gate: asset records and documents validated;
• readiness gate: staff trained and systems accepted for operation;
• post-occupancy gate: early operational issues captured and information updated.

Acceptance criteria should be measurable where possible. A record may be rejected because a serial number is missing, a document is obsolete, an asset cannot be located, a test result is outside tolerance or a system relationship is incorrect.

4. Connecting BIM with facility-management systems

4.1 The systems landscape

BIM, CAFM, CMMS and BMS perform different but complementary functions.

These categories overlap in commercial products. The distinction is functional rather than dependent on product branding.

4.2 Interoperability and identifiers

Integration fails when the same asset has different names or identifiers in different systems. A pump labelled “P-01” in the model, “CHWP-1” in the BMS and “Asset 00047” in the CMMS may be the same physical item, but the relationship must be explicit. A master identifier, cross-reference table or governed mapping service is necessary.

Interoperability involves more than file exchange. It includes:

• semantic consistency, so that “fan,” “air fan” and “supply fan” are interpreted correctly;
• units and measurement conventions;
• stable identifiers;
• geometry and coordinate-reference consistency;
• document links that remain valid;
• authentication and authorization;
• event and time-series formats;
• version and change management.

Open standards and structured exchange formats can reduce dependence on a single software vendor, but they do not guarantee semantic quality. An open file containing poorly classified or incomplete data remains poor information.

4.3 Practical integration workflow

A robust integration workflow is as follows:

1. Define operational use cases, such as reactive maintenance, energy optimization or statutory inspection.
2. Identify the assets, spaces, documents and sensor points needed for each use case.
3. Establish a common data dictionary, classification system and identifier policy.
4. Clean and validate source data before migration.
5. Map model objects and documents to CAFM or CMMS records.
6. Connect selected BMS and sensor points, beginning with high-value and reliable data.
7. Test transactions, including creation of a work order from an alarm and navigation from a work order to the asset.
8. Establish ownership, monitoring and change-control procedures.
9. Train users and measure operational outcomes.

Integration should be incremental. Attempting to connect every available data source at once creates unnecessary technical and governance risk.

5. Digital twins for the built environment

5.1 Definition and characteristics

A digital twin is a digital representation of a physical asset, process or system that is connected to the physical counterpart through data and can support analysis, monitoring, prediction or decision-making. A static BIM model is not automatically a digital twin. The distinguishing feature is an operational connection and an intended use.

A useful digital twin usually contains five elements:

1. physical entity: the actual building, infrastructure or equipment;
2. digital representation: geometry, asset data, rules and relationships;
3. data connection: sensor readings, work orders, inspections or other updates;
4. analytical capability: visualization, diagnosis, simulation or prediction;
5. decision and feedback process: actions that affect operation, maintenance or planning.

Digital twins exist on a spectrum. A documentation twin may provide verified asset records. A monitoring twin may display live conditions. An analytical twin may detect anomalies or estimate deterioration. A predictive or control-oriented twin may recommend or execute operational changes, subject to safety and authorization.

5.2 Sensors, data quality and context

Sensors provide measurements such as temperature, humidity, pressure, flow, vibration, occupancy or energy consumption. Their value depends on placement, calibration, sampling interval, communications reliability and context. A temperature value without a location, unit, timestamp and sensor identity is difficult to interpret.

Sensor data should therefore be governed by metadata including:

• unique device identifier;
• measured variable and unit;
• location and zone;
• timestamp and time zone;
• calibration status;
• sampling and transmission interval;
• quality flag and missing-data convention;
• ownership and retention period.

Data quality can be assessed through completeness, validity, consistency, timeliness, uniqueness and accuracy. A digital twin should represent uncertainty rather than presenting all data as equally reliable.

5.3 Analytics and maintenance decisions

A digital twin can support condition-based maintenance by comparing observed behaviour with expected behaviour. For example, a pump may show increasing vibration, reduced flow or a growing difference between commanded and measured speed. These signals can trigger inspection before failure.

However, correlation is not proof of causation. A high temperature could result from a failing fan, a blocked filter, an incorrect sensor or an unusual occupancy pattern. Analytics should support professional diagnosis, not replace it without validation. For safety-critical systems, automated control requires rigorous testing, fail-safe design and clearly defined authority.

6. Lifecycle asset management

Lifecycle asset management aligns asset performance, risk, cost and organizational objectives over time. BIM and digital twins contribute information, but they do not substitute for financial planning, maintenance strategy or professional judgment.

Key management questions include:

• What service does the asset provide?
• What performance level is required?
• What can fail, and what are the consequences?
• What maintenance is justified by risk and criticality?
• When should repair, renewal or replacement occur?
• What information is needed to support the decision?

A basic risk-prioritization model can be expressed as:

where R is a risk score, P is the assessed probability or likelihood of failure, and C is the consequence of failure. The expression is a screening model, not a universal law. Probability and consequence must use defined scales, and the result should not be treated as a precise physical quantity. Some organizations use multidimensional or matrix-based methods because safety, environmental, financial and reputational consequences are not always meaningfully reduced to one number.

Maintenance decisions may also consider whole-life cost. A simplified present-value model is:

where PV is present value, C₀ is initial cost at time zero, C_t is cost in year t, r is the discount rate per year, n is the analysis period in years and S_n is residual or salvage value at year n. Costs must be expressed in the same monetary basis, and the model assumes that the selected discount rate and timing convention are appropriate. It excludes taxes, inflation and risk adjustments unless they are explicitly incorporated.

Worked example: comparing two maintenance strategies

An organization compares two strategies over three years. Strategy A has an immediate cost of £10,000 and annual costs of £2,000, £2,000 and £3,000. Strategy B has an immediate cost of £6,000 and annual costs of £4,000, £4,000 and £5,000. Assume a discount rate of 5%, no residual value and costs paid at year-end.

For Strategy A:

PV_A = 10,000 + 2,000/1.05 + 2,000/1.05² + 3,000/1.05³

PV_A ≈ £16,210

For Strategy B:

PV_B = 6,000 + 4,000/1.05 + 4,000/1.05² + 5,000/1.05³

PV_B ≈ £17,797

On this simplified financial basis, Strategy A has the lower present value by approximately £1,587. The result does not automatically establish the preferred strategy: reliability, safety, disruption, carbon emissions, staff capacity and uncertainty must also be considered.

7. Illustrative case: university science building

Background

A university completed a six-storey science building containing laboratories, teaching rooms, specialist ventilation, emergency power and complex water systems. The project team delivered a federated BIM model and thousands of documents. The facilities department, however, used a CMMS with its own asset codes, while the BMS used separate point names. Previous projects had produced incomplete handover information and slow maintenance response.

Problem

At practical completion, the facilities team could not reliably identify which air-handling units served individual laboratories. Several warranty records lacked serial numbers, and commissioning records were stored in folders unrelated to the assets. BMS alarms could not generate meaningful maintenance requests because point names did not match CMMS records.

Analysis

The university identified three high-value use cases: locating critical equipment during an incident, managing statutory and preventive maintenance, and investigating laboratory environmental complaints. It concluded that a highly detailed model was less important than verified asset identity, system relationships, commissioning evidence and usable documents.

Approach and solution

The team established an asset-information requirement and selected maintainable assets using criticality and maintenance criteria. Each asset received a permanent identifier. A mapping table connected BIM identifiers, CMMS records and BMS points. The team then:

• verified equipment locations through site inspection and targeted scanning;
• checked manufacturer, model, serial number and warranty fields;
• linked functional test certificates to equipment and systems;
• associated air-handling units with laboratories and supply zones;
• created CMMS preventive-maintenance schedules;
• connected selected BMS alarms to work-order workflows;
• trained technicians to update asset records after interventions;
• introduced a monthly data-quality review.

The digital twin was deliberately limited to critical mechanical and electrical systems rather than including every object in the building. The platform displayed equipment context, current readings, alarm history, maintenance status and relevant documents.

Outcome

Technicians could navigate from a laboratory to its serving air-handling unit, view current conditions, inspect commissioning evidence and open a maintenance request. The university reported faster asset identification and fewer duplicated inspections during the first operational year. It also discovered that several sensors were poorly located and that some maintenance records were not updated after component replacement. These findings led to revised sensor standards and a formal close-out procedure for work orders.

Learning points

The case demonstrates that digital-twin value depends on governance and operational adoption. The most important investments were not visual sophistication but identifiers, verified relationships, clear responsibilities and feedback from technicians. It also shows that handover is not finished when files are accepted; operational use reveals defects in both the physical system and the information system.

8. Governance, ethics, security and regulation

Operational BIM and digital twins create responsibilities that extend beyond construction documentation.

Information governance

Organizations should define who may create, approve, change, archive and delete information. A record of an approved asset should not be silently overwritten. Version history, approval status and audit trails are essential, especially for safety-critical equipment and regulatory evidence.

Cybersecurity

A connected building can become a cyber-physical risk. Unauthorized access to a BMS may affect comfort, energy use or safety. Controls should include network segmentation, strong authentication, least-privilege access, secure configuration, patch management, backup, incident response and supplier assurance. Remote access should be time-limited and logged.

Privacy and ethics

Occupancy sensors, access records and indoor-location data can reveal individual behaviour. Data minimization, purpose limitation, retention controls, transparency and lawful processing are necessary. A system designed for energy optimization should not automatically be repurposed for employee surveillance.

Safety and professional responsibility

Automated recommendations must not obscure accountability. Engineers and facility professionals remain responsible for decisions within their competence. Models and analytics should communicate confidence, assumptions and limitations. Life-safety systems require compliance with applicable building regulations, fire codes, electrical rules, occupational-safety requirements and data-protection law.

Commercial and contractual issues

Contracts should specify information requirements, delivery formats, validation responsibilities, intellectual-property rights, permitted uses, software dependencies, cybersecurity duties and obligations to update information after change. Ambiguous ownership of data can prevent effective operation and create disputes.

9. Contemporary developments and best practices

Current practice is moving toward connected asset graphs, cloud and edge computing, reality capture, automated data checking, open APIs, semantic web technologies and AI-assisted anomaly detection. AI can classify documents, identify missing attributes, detect unusual energy patterns and prioritize work orders. It should be used with human review, traceable evidence and controls against biased or erroneous outputs.

Reality capture using laser scanning, photogrammetry and mobile mapping can improve verification of existing conditions. However, capture data must be registered, filtered and interpreted; a point cloud is not automatically an operational model.

Recommended practices include:

1. Begin with operational decisions and measurable use cases.
2. Specify only information that has a defined purpose.
3. Use stable identifiers and a governed data dictionary.
4. Validate information progressively rather than at the final handover.
5. Link assets to spaces, systems, documents and responsibilities.
6. Treat commissioning evidence as part of the asset record.
7. Integrate with CAFM, CMMS and BMS through tested mappings.
8. Represent data quality, uncertainty and approval status.
9. Protect operational and personal data throughout its life.
10. Budget for information maintenance, training and system administration.
11. Measure outcomes such as response time, data completeness, energy performance and avoided failures.
12. Review the digital twin after modifications, replacements and changes in use.

Challenges and limitations

Several limitations should be recognized. Information requirements may be unclear or change during a project. Contractors may lack incentives to provide accurate data if acceptance criteria are weak. Legacy buildings may have incomplete records and inaccessible services. Proprietary systems can create integration costs and vendor dependence. Sensor networks require calibration, communications and cybersecurity. Digital twins can generate large volumes of data without improving decisions. Finally, models may create false confidence if their geometry or asset status is not verified.

The strategic response is disciplined scope, staged implementation, clear accountability and continuous validation. A modest, trustworthy operational information system is more valuable than an impressive but unreliable digital twin.

Chapter Summary

Handover is a lifecycle information process that transfers operational capability, not merely files. Effective asset information is purpose-driven, structured, verified and linked to physical assets, spaces, systems, documents and responsibilities. Commissioning provides evidence that installed systems perform individually and in combination, while staged handover gates reduce late defects.

BIM can connect with CAFM and CMMS for maintenance and work management, with BMS and IoT platforms for monitoring and control, and with digital-twin platforms for contextualized analysis. Stable identifiers, data dictionaries, interoperability and governance are fundamental to these connections. A digital twin requires a digital representation, a connection to the physical asset, usable data, analytical capability and a decision process; a static model alone is not a twin.

Lifecycle asset management considers performance, risk, cost, safety and organizational objectives. Quantitative tools such as risk screening and present-value analysis can support decisions, but they depend on explicit assumptions and must be supplemented by professional judgment. Security, privacy, safety, contractual responsibility and regulatory compliance are essential. The most successful implementations begin with high-value operational use cases and maintain information throughout the asset life.

Key Terms

Asset information model: Approved information describing an asset during operation.

As-built information: Verified record of what was actually installed and commissioned.

BMS: Building-management system used to monitor and control building services.

CAFM: Computer-aided facility-management system supporting facilities, spaces and services.

CMMS: Computerized maintenance-management system supporting maintenance planning and work orders.

Commissioning: Systematic verification that building systems are installed, tested and capable of meeting requirements.

Common data environment: Managed source of information used for collecting, controlling and sharing project data.

Digital twin: Connected digital representation of a physical asset or system used for monitoring, analysis or decision-making.

Functional performance test: Test demonstrating that a system performs a specified function under defined conditions.

Handover: Controlled transfer of information, systems knowledge, responsibilities and operational readiness.

Information requirement: Defined information needed to support an organizational, asset or project decision.

Interoperability: Ability of systems to exchange and correctly use information.

IoT sensor: Connected device that measures and communicates physical conditions or events.

Lifecycle asset management: Coordinated management of asset performance, risk, cost and value over its life.

Maintainable asset: Asset requiring planned inspection, servicing, repair or replacement.

Preventive maintenance: Maintenance performed according to time, usage or condition before failure.

Reality capture: Collection of physical-condition data using methods such as scanning or photogrammetry.

Unique identifier: Stable code used to distinguish an asset across information systems.

Review Questions

Short Answer Questions

1. Why is BIM handover more than the delivery of a model file?
2. Distinguish a CAFM system from a BMS.
3. What information should be included in a maintainable-asset record?
4. Why are stable asset identifiers important for system integration?
5. State two characteristics that distinguish a digital twin from a static BIM model.

Long Answer Questions

1. Explain how information requirements should influence the scope and content of an operational BIM deliverable.
2. Describe a staged commissioning and handover process for a complex building.
3. Discuss the role of interoperability in connecting BIM, CMMS, CAFM, BMS and sensor platforms.
4. Explain how digital twins can support condition-based maintenance, including their limitations.
5. Evaluate the governance, cybersecurity, privacy and contractual issues associated with connected building information.

Analytical / Application Questions

1. A hospital project has accurate geometry but missing serial numbers, incomplete commissioning records and inconsistent asset codes between the BIM model and CMMS. Develop a prioritized recovery plan and justify the order of actions.
2. A building owner wants to install sensors on every major building component. Propose a decision framework for selecting sensors and digital-twin use cases, considering value, data quality, cybersecurity and maintenance burden.
3. An air-handling unit shows abnormal vibration and declining airflow in a digital-twin dashboard. Analyze at least four possible explanations, identify additional evidence required and recommend a safe maintenance response.

Multiple Choice Questions with Answers

Question 1

Which statement best describes the primary purpose of BIM-enabled handover?

A. To provide the largest possible model file

B. To transfer verified information and operational capability to the facility-management organization

C. To replace all facility managers with automation

D. To preserve only the architect’s design intent

Correct Answer: B. To transfer verified information and operational capability to the facility-management organization

Question 2

Which system is primarily intended to manage maintenance work orders, preventive maintenance and asset histories?

A. CMMS

B. BMS

C. Rendering engine

D. Structural analysis solver

Correct Answer: A. CMMS

Question 3

What is the most important reason for using a stable asset identifier across BIM, CMMS and BMS?

A. It increases model polygon count

B. It guarantees that all sensors are accurate

C. It enables reliable matching of the same physical asset across systems

D. It eliminates the need for commissioning

Correct Answer: C. It enables reliable matching of the same physical asset across systems

Question 4

Which feature most clearly distinguishes a digital twin from a static BIM model?

A. The use of three-dimensional geometry

B. The presence of architectural materials

C. A connection between the digital representation and the physical asset for operational use

D. The ability to print drawings

Correct Answer: C. A connection between the digital representation and the physical asset for operational use

Question 5

In commissioning, what does an integrated systems test examine?

A. Only whether one item of equipment starts

B. Whether interacting systems perform together under defined conditions

C. Whether the model has attractive graphics

D. Whether construction invoices are paid

Correct Answer: B. Whether interacting systems perform together under defined conditions

Question 6

Using the chapter’s simplified risk model R = P × C, what is the risk score when likelihood is 4 and consequence is 5?

A. 9

B. 20

C. 25

D. 45

Correct Answer: B. 20

Question 7

Which practice best supports sensor-data interpretation in a digital twin?

A. Removing timestamps to reduce file size

B. Recording the measured variable, unit, location, timestamp and quality information

C. Using different names for the same sensor in each system

D. Assuming every reading is equally reliable

Correct Answer: B. Recording the measured variable, unit, location, timestamp and quality information

Question 8

Why should an operational model not automatically include every modelled object as a managed asset?

A. All modelled objects are illegal to maintain

B. Only objects with operational, maintenance or management significance require asset records

C. Facility managers cannot use geometry

D. Documents cannot be linked to assets

Correct Answer: B. Only objects with operational, maintenance or management significance require asset records

Question 9

In the simplified present-value model, what happens to a future cost when the positive discount rate increases, all other variables remaining constant?

A. Its present value generally decreases

B. Its present value becomes equal to its future value

C. Its present value necessarily increases

D. The cost is removed from the analysis

Correct Answer: A. Its present value generally decreases

Question 10

Which is an appropriate cybersecurity control for connected building systems?

A. Allowing unrestricted remote access

B. Sharing one administrator password among all contractors

C. Using least-privilege access, strong authentication and logged remote connections

D. Disabling all audit trails

Correct Answer: C. Using least-privilege access, strong authentication and logged remote connections