COBie Data Drops: What Clients Actually Want at Handover

A filled-in COBie (Construction-Operations Building information exchange) spreadsheet is not what the client wants. What they seek is precise and verified information about the assets actually installed that is useful for their facilities management systems. The information should link the building, BIM model, asset list and O&M documents, so FM teams can effortlessly pinpoint and maintain each asset without having to look for missing information.

Does Every ISO 19650 Project Need COBie?

No, COBie is not required for every ISO 19650 project.

The UK standard that specifically discussed the use of COBie for exchanging facility information was BS 1192-4:2014, which was later withdrawn in September 2022. BS EN ISO 19650-4 provides a broader view of information exchange and does not prescribe the necessity to use COBie for every project. COBie is not the only method or format for information exchange.

What Should the Project Define?

The project’s information requirements and appointment documents should explicitly specify:

• Whether COBie is required by the client
• Which assets are within scope
• Which data fields are compulsory
• At what stage the information must be exchanged
• Who is overseeing the information exchange process
• How the information will be evaluated and approved
• Which FM platform will receive the information

The BIM Execution Plan (BEP) then sets out how the team will deal with all this information thoroughly to provide the deliverables the client requires.

What Do Clients Actually Want from COBie at Handover?

When a client asks for a “COBie file,” “full COBie,” or “COBie-compliant handover,” it does not always make it clear what information they actually want.

In simple terms, clients usually need:

• A clear list of all assets that need to be maintained
• Information that matches the equipment installed on site
• Consistent equipment names and unique asset numbers
• Correct building, floor, room, and system information
• Manufacturer and product details
• Model and serial numbers where required
• Installation and commissioning information
• Warranty details
• Maintenance requirements and expected service life
• Links to O&M manuals, product information, and certificates
• Information that matches across the BIM model, COBie data, and drawings
• Data that can be easily added to the client’s FM or asset management system
• Evidence that the information has been checked and approved

In short, clients do not simply need as much information as possible. They need the right information, at the right time, in the agreed format, and at a quality level that they can actually use.

What the Standard Expects vs. What Clients Ask For

What Should Be Agreed Before COBie Production Begins

COBie should be treated as a task of utmost priority as the project begins, rather than dealing with it at the end. Prior to gathering any information, the client and project team should discuss the what, who, and how of the project, i.e., data requirements, their provision, their format, and their evaluation and approval.

Requirements

First and foremost, the objective for the team should be to identify the information requirements the client asks for. AIR (Asset Information Requirements), EIR (Exchange Information Requirements), PIR (Project Information Requirements), BEP (BIM Execution Plan), responsibility matrices, information delivery plans, naming and classification standards, COBie guidance where applicable, and CDE procedures might be some of the inclusions. Documents like these are essential for providing clarity on what information is needed, when it is required, and how it should be managed.

Template

The COBie format should be agreed at the outset of data collection. Clients have their specific requirements or different templates that they use. Information such as which worksheets are required, which fields are mandatory, whether additional fields are desired, and what naming, date, classification, and validation rules should be followed are the responsibility of the team to confirm with the client. What helps the most is a completed and approved sample COBie file to meet the client’s expectations precisely.

Assets

Which items should be included as maintainable assets in the model must be agreed with the team. A COBie record is not applicable for every object in a BIM model. Whether a separate record should be maintained for repeated equipment, whether the smaller components should be dealt with as individual equipment or be considered part of larger systems, and the inclusions and exclusions of this equipment are essential things that a client must confirm at the earliest. Doing so helps avoid collecting irrelevant information or overlooking vital assets.

Responsibilities

The responsibility for the provision of certain information must be clear to every group. Contractors or suppliers are responsible for providing information that falls within their scope, so BIM teams do not have to guess the data on their own. The help that comes on behalf of the teams is that they can then manage, structure, populate, and check the data. Manufacturer details, model and serial numbers, warranty information, installation dates, O&M documentation, maintenance requirements, and commissioning records are examples of information that the relevant parties are responsible for delivering.

Handover

The team should agree how the information will be used after the project is completed. The client should confirm which Common Data Environment (CDE), Computer-Aided Facility Management (CAFM), Computerised Maintenance Management System (CMMS), or other system will receive the information, along with the required file formats and import requirements. The team should also agree if a trial import is needed and who will check and approve the final submission.

The goal is not just to produce a COBie spreadsheet. It is to provide accurate and well-structured asset information that the client can use for operation and maintenance after handover.

What Information is Typically Included?

To-the-point information required always depends on the client’s expectations; however, maintainable asset data typically include a few main areas.

Asset Identification

Details such as asset name, description, unique ID, equipment tag, asset type, classification, and the system it is part of are listed here.

Location Information

Information that assists in pinpointing the asset at its final installed location is usually included in it, such as the building, floor, zone, area, and room.

Product Information

Details such as manufacturer, model or product number, supplier, product description, serial number, replacement cost where applicable, and expected service life belong to this field.

Installation and Commissioning

Stuff like installation date, commissioning date, operational status, test information, and references to commissioning certificates may be recorded here.

Warranty and Maintenance

Warranty period and start date, warranty provider, preventive maintenance requirements, maintenance intervals, spare-parts information, and recommended replacement periods are usually covered in this.

Supporting Documentation

O&M manuals, warranty certificates, product data sheets, maintenance instructions, commissioning and test records, record drawings, health and safety information, and training information where required could be enumerated as some of the supporting documents.

How COBie Information Evolves Throughout the Project

There is no hard and fast sequence of data drops that can be implemented on every project; however, a similar pattern of progressive exchanges is the key to ensuring that most projects meet handover successfully.

Early Project Information Exchange

In the early stages of the project, emphasis lies on the preparation of basic information anatomy. That may include facility details, floor and space information, project contacts, initial asset categories, classification requirements, naming conventions, and information responsibilities. Typically, finalisation of all equipment is not done at this phase, due to which establishing the required information is more appropriate than populating it with the final deliverable details.

Coordinated-Design Information Exchange

As the design matures, more and more information gradually adds up to the intended asset. This may account for equipment and asset types, associated systems, design locations, generic product information, preliminary equipment tags, and manufacturer details where selections are affirmative. To be in line with the evolving model and design documentation, updates to floor, room, and space information should also be maintained.

Construction-Stage Information Exchange

The project info becomes more detailed and more specific once the equipment and subcontractor packages are approved. This includes the approved manufacturer, equipment tags, product and model numbers, system connections, updated locations, supplier information, basic warranty information, available technical documents, and contractor information. Missing or incorrect details can be spotted and put right at this stage before they cause any conflicts during the final handover.

Final Handover Information Exchange

This indicates that rather than just what was planned or intended, the data should reflect what was actually implemented. Final asset names and tags, actual locations, manufacturer and product details, serial numbers, installation and commissioning dates, warranty and maintenance details, O&M documents, final system and space connections, the finished and verified model and COBie workbook, and any agreed-upon missing information should all be included.

The final handover becomes a straightforward procedure of verifying and updating information rather than a last-minute scramble to gather everything from several teams because the information has been updated gradually throughout the project.

What Components Should a Full COBie Handover Package Have?

More than just the COBie worksheet may be part of a comprehensive digital handover. Final approved COBie workbooks, as-built or coordinated Revit and IFC models, asset schedules, record drawings in PDF and DWG, operations and maintenance documents, client-specific information sheets, details of any missing or rejected information, CDE upload records, CAFM or asset-management test results, and final client approval are all things that might be included in it, depending on the project requirements.

Instead of deciding what needs to be done at the end of the project, the exact handover requirements should be agreed upon at the start of the project and checked at each stage of information sharing.

What Clients Really Look for When Selecting a BIM Delivery Team

Clients consider far more than simply the capacity to complete a COBie spreadsheet, according to a digital competency evaluation employed by BIM Outsourcing. They want to know whether the BIM team is aware of the COBie requirements for the project, when space and equipment information must be supplied, and precisely what information is needed. Additionally, they verify that the team has expertise uploading COBie or Asset Information Model (AIM) data to the project’s CDE, has an appropriate checking and validation procedure, employs appropriate model-checking and validation tools, and is able to provide sample outputs and samples of prior COBie projects.

To put it simply, seasoned customers consider more than just whether the COBie spreadsheet has been completed; they also consider the team’s procedure, expertise, quality assurance, and capacity to handle information effectively.

The Most Typical Issues with COBie Handover

Issues with COBie transfer often arise from unclear requirements or late data collection. Among the most prevalent issues are:

• Without specifying which assets or information are needed, the client requests "full COBie."
• Too late in the project, the authorised COBie template is supplied.
• The needs are set without consulting the facilities management staff.
• There is no agreed-upon list of maintainable assets.
• All model objects are included, even if they don’t need maintenance.
• Before final equipment choices are made, product details are added.
• Serial numbers, warranty information, and commissioning dates are not supplied by subcontractors.
• The COBie workbook’s asset tags don’t correspond to the model or the drawings.
• The asset information is not updated when room numbers or names change.
• Links in O&M documents lead to unreachable files or incorrect locations.
• Different teams use different approaches to categorisation and naming.
• Who is in charge of supplying each piece of information is unclear.
• Despite passing a basic check, the COBie workbook cannot be imported into the FM system of the client.
• Rather than being controlled throughout the design and construction phases, COBie is handled as a last-minute handover activity.

The answer is straightforward: decide on the needs early on, explicitly define roles, then monitor and update the data as the project progresses.

Case Study of the Maidstone Innovation Centre

The RIBA Stage 5 coordinated MEP BIM model for the Maidstone Innovation Centre was delivered by BIM Outsourcing. Working together with the M&E consultants and contractors, the team modelled and coordinated the electrical and HVAC systems, as well as the plant rooms and electrical rooms.

At the end of the project, COBie wasn’t stored in a different file. Instead, the required COBie data was added to the MEP BIM model itself, along with a link to an extra sheet. This made it easier to find and use things like equipment manuals and warranty information. It was useful for managing the building, keeping it in good shape, and planning changes that will be made in the future. There were also links between MEP systems in the project that showed where each system began and ended. This helped people understand and use the system information better.

The primary insight we gained is that for COBie delivery to work, asset information needs to be linked to the BIM model, systems, locations, and related files. Operating and maintaining the building would not have been as easy with a separate worksheet alone.

Our Method for Delivering COBie

We at BIM Outsourcing see COBie as a continuous information management procedure rather than a one-time export. There are five primary phases to our COBie integration services:

Planning and strategy for data

Deciding with the client and project team what information is needed, what assets are required, who is in charge of supplying it, when it should be provided, and how it will be inspected.

Review and analysis of the model

Identifying relevant asset information, missing data, naming issues, wrong locations, duplicate entries, missing system links, and other gaps by reviewing BIM models, schedules, and project documentation.

Population of data

Using data from manufacturers, commissioning teams, contractors, subcontractors, and designers to add the agreed-upon information. Instead of making assumptions, missing information is marked for clarification.

Verification and quality control

Verifying that the model and COBie data match, the asset tags are unique, the locations are accurate, the names and classifications are consistent, and the necessary information is complete. Additionally, we review the approved template, asset linkages, supporting documentation, and project requirements.

Integration and support of facility data

Preparing the data for the client’s FM systems or processes and assisting the client’s team with the final data evaluation and use.

Checklist for the Final COBie Delivery

When you are ready to deliver the final COBie deliverable to the client, ensure that everything is sorted and ready.

• Is the client satisfied with the list of assets that can be readily maintained? Is the correct template being used? Are all the required worksheets and fields completed? Did you add any additional sheets or fields that are bespoke to the client? What is your position on the subject of assurance and approval?
• Does each asset need its own identifier? What is the relationship between the asset tags and the models, drawings and schedules? Is this trustworthy information about the manufacturer and the product? Have the serial numbers been added? Are the installation and commissioning dates available? Is all relevant data about warranty and maintenance available?
• Is the data on the building, floor, room, area correct in terms of systems and places? Have the room numbers been changed? Were the systems’ assets associated correctly? Have all the possible links and connections within the system been made use of?
• Are the O&M manuals correctly linked? Do you have datasheets for your products? Is warranty and commissioning documentation available for inspection? Verify that the links to the document point to the correct CDE site. Are all the details linked and available to the client?
• Is the COBie workbook available for use? Does the worksheet agree with the completed model? Did you manage to fix the problem with the inconsistent and redundant entries? Has the status of missing information been discussed with the appropriate team or documented as an exception? Has the import test been run as required? Has the final submission been approved by the client?

Conclusion

How many worksheet cells have been filled in does not show how well a COBie handover went. It is assessed based on how well the client receives correct, structured, and helpful details about the assets they will own and take care of.

Agree on the assets that can be maintained, the information that is needed, who is responsible for what, when the work needs to be delivered, and how it needs to be accepted. Gather information and double-check it as the project progresses, as the design evolves, as equipment is chosen, and as systems are put in place. When COBie is seen as an ongoing, iterative information process for the whole project, the final handover is more reliable, easier to look over, and more useful for the facilities management team. It is much more likely that information will be missing, asset tags will not match, and documents will not be available if it is left as a job to be done until the end.

FAQ

What’s a COBie data drop?

A COBie data drop is an agreed exchange of building and asset information at a scheduled stage of a project.

Who is the final COBie information provided by?

Responsibility is shared between the client, design and construction teams, suppliers, subcontractors and the BIM or information management team.

Why does a COBie deliverable get turned down?

Some common reasons are lack of required information, wrong asset tags, records in the wrong place, broken document links, the wrong template, missing product details, and changes between the workbook, model, and drawings.