A building is handed over, the keys change hands, and the facility manager receives... boxes of paper manuals and a USB stick full of PDFs. Weeks later, someone is still typing pump serial numbers into a maintenance system. COBie was created to end that ritual. In this guide we explain what COBie is, what data it contains, how it fits into a BIM project, and how Revit users can produce it without losing their minds.
What is COBie?
COBie stands for Construction Operations Building information exchange (NIBS writes it as Construction to Operations Building Information Exchange). It is a non-proprietary way to organise the information an owner needs to run and maintain a facility: equipment lists, product data, warranties, spare parts and maintenance schedules. The National Institute of Building Sciences describes it as "a standard organization of data used to manage and maintain facility assets."
The key idea is that COBie focuses on assets, not shapes. It does not care how beautifully a chiller is modelled; it cares about its type, location, manufacturer, warranty and maintenance needs. That makes it a lightweight subset of the full building model, designed to drop straight into a computerised maintenance management system.
A short history and the current version
COBie began in 2006 and 2007 at the US Army Corps of Engineers' Construction Engineering Research Laboratory, with William East credited as its originator. Version 1.0 appeared in 2007. It later became part of the US National BIM Standard (NBIMS-US), and NIBS took over curation in 2013. The UK also adopted COBie for government BIM projects, initially through BS 1192-4, with work under way to align that guidance with ISO 19650.
The latest edition, COBie V3, was published in 2023 as part of NBIMS-US V4. NIBS lists 58 changes grouped around ease of use, modernisation, new capabilities and workflow. Highlights include removing personally identifiable information fields, replacing the Floor table with a Level table, adding JSON support, new classification and geolocation fields, and new tables for SpaceType, Package, Event and Risk. The standard defines 19 data tables and 144 fields.
Formats and data drops
Formally, COBie is defined as a subset of IFC, the open BIM exchange standard. In practice most people meet it as a spreadsheet, with one worksheet per table, because almost anyone on a project can fill in or check a spreadsheet. NIBS provides a blank template in SpreadsheetML (the Excel format) and also templates in JSON and IFC.
COBie is not meant to be produced in one heroic push at the end. Data is delivered in "data drops" at agreed project milestones. Early drops carry spaces and zones from the design team; later drops add specified products, then installed equipment with serial numbers, warranties and maintenance information from contractors and suppliers. Spreading the work this way means each party contributes what it actually knows, when it knows it.
How to produce COBie from Revit
Autodesk offers a free COBie Extension for Revit as part of its Interoperability Tools for licensed Revit users. It helps set up a model to capture COBie data and export a compliant spreadsheet. A typical workflow looks like this:
- Agree the COBie requirements with the client early: which asset types, which fields and which classification system.
- Install the Autodesk Interoperability Tools for your Revit version through Autodesk Access or your Autodesk account.
- Set up the model with the extension, mapping your own parameters where they already hold the right data.
- Use the Zone Manager to assign rooms or spaces to zones.
- Assign classifications and fill in type and component data as the design matures.
- Export the COBie spreadsheet for each data drop and check it before submission.
Many teams fill gaps in bulk outside Revit; a two-way Excel tool such as DiRoots SheetLink or a Dynamo script can help push values back into parameters.
Common pitfalls
The biggest mistake is treating COBie as an afterthought. When nobody defines the required assets until handover, teams end up exporting thousands of irrelevant objects, such as every door handle, while missing the boilers that matter. Inconsistent naming is the second trap: if one sheet says "AHU-01" and another says "AHU 1", the maintenance system will see two different things. Finally, remember that an empty field filled with "n/a" is not the same as useful data, so agree what "complete" means.
Conclusion
COBie is not glamorous, but it is one of the clearest ways BIM pays off after construction. By organising asset information into a standard, non-proprietary structure and delivering it in stages, project teams give facility managers a working dataset on day one instead of a pile of PDFs. Start with clear requirements, use the tools you already have in Revit, and check each data drop. Your client's maintenance team will thank you.