Construction-Operations Building Information Exchange (COBie)
Last updated: 08-04-2014
Within This Page
The handover of a new, or newly renovated, facility is celebrated by the project team, facility occupants, and owners. For those responsible to operate, maintain, and manage that facility, however, the work is just beginning. To start the facility manager begins by unpacking boxes of paper documents and retyping asset information and maintenance schedules into Computerized Maintenance Management Systems (CMMS). The pallets of boxes full of paper of operations and maintenance manuals and drawings shown in the figure below are typical of the requirements of contractors complying Unified Facility Guide Specifications 01 78 00 - Closeout Submittals, and 01 78 23 - Operations and Maintenance Data.
Figure 1 Typical Delivery of Handover Documents
Facility managers have reported that this effort may require man-years of effort to create and review and transcribe hundreds of pages of documents, validate the transcriptions and manually enter data.
To transfer the cost of this manual data entry from the facility manager to the construction contractor, UFGS 01 78 24.00 20, Facility Electronic Operating and Maintenance Support Information (eOMSI), requires the contractor to enter data directly into one specific CMMS.
Even if a CMMS is used, mechanics need to search for information in these paper boxes to complete many of their jobs. Over time such documents are moved or lost which increases the cost to complete O&M activities and potentially increasing downtime of mission-critical facilities. A 2011 study predicted that 8% of the annual maintenance budget could be saved if open-standard electronic information were available to the technicians before starting complex work orders. Such savings could allow man-years of additional work towards backlogs or needed renovations. During the life of a project the owner collects and recollects information again and again, transcribing and then losing the same information over and over.
In 2007, the Construction-Operations Building information exchange (COBie) requirements analysis report (PDF 1.1 MB) proposed a new way for designers and contractors to directly provide electronic operations, maintenance, and asset management information as that information is created. Following an on-site study of COBie at Fort Lewis Washington, a proposed UFGS specification was developed for design-build and construction contracts. Further investigation of COBie compared the life-cycle costs of current and COBie-based processes (PDF 8.3 MB) and demonstrated that tens of thousands of man-hours or large projects are spent in performing redundant tasks trying to handle information locked-in documents.
Simply understanding, documenting, and proposing the information needs of operators, maintainers, and facility managers is insufficient to have COBie be used in practice. In parallel efforts the Engineer Research and Development Center, through the buildingSMART alliance, worked to establish COBie as an internationally recognized open-standard implemented in over 30 Commercial Off-The-Shelf Software (COTS) systems.
COBie is a performance-based specification (PDF 6.2 MB) for facility asset information delivery. Two types of assets are included in COBie: equipment and spaces. While manufacturer data for installed products and equipment may one day be directly available (via the SPie project), COBie helps the project team organize electronic submittals approved during design and construction and deliver a consolidated electronic O&M manual with little or no additional effort. COBie data may then be imported directly into CMMS and asset management software, again at no cost. The PDF, drawing, and building information model files that accompany COBie are organized so that they can be easily accessed through the secure server directories already in place at the facility management office. The federal government's requirement for delivery of Real Property Inventory (RPI) information may be met by COBie.
While the technical details of COBie can appear complex. COBie files are not intended for end-users. COBie provides system-to-system exchange of the space and equipment information without user intervention. Consider COBie and similar "information exchange" projects to be a kind of "ASCII for buildings." Today, people don't need to know ASCII to use a web browser, email system, word processor, or other software; the words just come along because of ASCII. In the same way, once we have achieved COBie everywhere, only a very few programmers will need to give COBie a second thought.
To make COBie as useful as possible COBie data is available in several formats. Software system exchanges during the design process could use the STEP Physical File Format (ISO 10303 Part 21) files conforming to the Industry Foundation Class (ISO 16739) COBie Model View Definition. When people want to look at the COBie data directly, and they do not want to learn to read complex STEP file formats, they can use a translation of data into a spreadsheet. Examples of COBie files of different formats, and at various stages of design and construction, can be found on the Common BIM Files page. COBie spreadsheet templates may be found on links at the bottom of the COBie Means and Methods page.
Exchanges of small bits of COBie data about individual assets is another type of exchange supported by COBie. For example, an entire file need not be exchanged simply to update the installation date and serial number of a specific piece of equipment. These individual COBie transactions can be captured through National Information Exchange Model format called COBieLite.
As in any other part of a design or construction contract, the quality of the product received depends on the ability of the designer or contractor to meet the specification. Before COBie, there was little need to clearly define the quality of the data provided since the volume of paper documents provided effectively prohibited more than a cursory review of the construction handover documents. Since COBie offers the possibility to automatically check the equality of electronic handover documents, the best owners will be sure they consider what to include in their COBie specification.
There are three sets of decisions owners can make to ensure that they get the information they need through COBie. The first is to specify the classifications they already use to organize existing CMMS data. If there is no CMMS data, COBie provides a default classification system, OmniClass, provided by the Construction Specifications Institute. The second set of decisions owners can make is to limit the set of scheduled information provided via COBie to only those assets that are actually managed or maintained. Finally, the owner can identify the specific properties to be mandated for each of these assets. Here again the default position is that COBie data simply reflect that data found on the drawing schedules. In most cases, such a level of detail will be well above the information currently captured. A brief video introduces COBie for owners.
From the designer's point of view, COBie data is simply the compiled set of all the schedules found on design drawings. Design software has been working hard since 2007 to ensure that they can export COBie data that matches their drawings. To ensure that design schedules can be properly exported to COBie designers should follow the instructions provided by their design software product. This brief video introduces the topic of COBie for designers.
From the contractor's point of view, COBie data is simply a way to produce construction submittals so information does not have be repeatedly copied and re-organized. Development of COBie data for the contractor should, if done correctly, also eliminate the need for equipment surveys. Properly compiled and organized COBie data also automatically produces O&M manuals. This brief video introduces the topic of COBie for contractors.
While facility managers will gain value from COBie on new facilities, they often express concern for about capturing COBie data collection on their existing building inventory. One 2009 study demonstrated that as-built COBie data surveys could be easily accomplished. Given management emphasis, the capture of COBie data for an entire campus may be accomplished in 12-14 months simply by modifying service and work orders forms.
COBie began in late 2006 under the NIBS Facility Maintenance and Operations Committee. Small grants from NASA and the White House Office of Science and Technology Policy lead, within six months, to a initial specification that considered all available alternatives (PDF 1.1 MB). As the buildingSMART alliance was formed as a NIBS Council, the first demonstration of software meeting the COBie requirements was held less than two years later at the National Academy of Sciences. Since March 2012 COBie has been part of the United States National Building Information Model Standard (NBIMS-US V2). An update to COBie to version 2.4 was balloted and approved in 2014 NBIMS-US V3.
Commercial software testing ensures that end-users can create realistically sized models in practice. Results of "COBie Challenges" are fully public so that any user can test the software for themselves. The complete set of software tested can be found on the COBie Means and Methods page. The list of COBie challenge events are provided in the list below.
- July 2008 Challenge
- March 2009 Challenge
- December 2009 Challenge
- March 2010 Challenge
- December 2010 Challenge
- March 2011 Challenge
- May 2011 Case Studies
- December 2011 Challenge
- December 2011 Case Studies
- March 2012 Challenge
- January 2013 bSa Challenge
- March 2013 Challenge
- January 2014 bSa Challenge
Today COBie has been included in design and construction contracts in the United States, United Kingdom, and Singapore. There is no telling where it will turn up next since no one has to report their use of open standards! Given the typically slow pace of adoption of new technology in the construction industry, the progress of COBie has been nothing less than meteoric. This is not because COBie is perfect, or that COBie solves all problems related to BIM interoperability. This success is because COBie does one small job, and does it well. COBie delivers information about equipment and spaces at lower cost and higher quality than today's manual (or proprietary) methods.
COBie for Developers
If you are a software developer and want participate in the COBie project, there are several ways for you to engage. The CMMS/CAFM Committee is a COBie-specific group started to help operations, maintenance, and asset management software best use COBie. A COBie for construction committee was formed in January 2014 to assist those working in the construction and commissioning markets. For more information on the COBie for construction committee contact Mariangelica Carrasquillo-Mangual of the US Army Engineer Research and Development Center. Since only the leading handful of design software firms have implemented (or begun to implement) management of this group is accomplished directly by the COBie Project Committee. If your software covers the design (or fabrication) markets, then please contact Bill East for more information about how you can meet the COBie Challenge!
While COBie began with a small Corps of Engineers project funded by NASA and the White House Office of Science and Technology Policy, COBie version 2.4 (included in NBIMS-US v3) is a national consensus effort. Efforts to make small improvements to COBie are always being discussed by members of the COBie Project Committee. You can see the updates made to COBie 2.4 here. To participate in this committee please contact Bill East.
Relevant Codes and Standards
- Draft UFGS 01 79 00 (29-Jan-14) (PDF 213 KB)
- COBie Practice Guide
- COBie 2.4 MVD (Technical Specification)
- COBieLite (Technical Specification)
- Change Logs
Templates and Additional Resources
- COBie FAQ's
- COBie Means and Methods
- Example COBie Files and BIM Models
- The COBie Calculator
- LinkedIn COBie Group
- COBie for Owners
- COBie for Designers
- COBie for Contractors
- Why COBie?
- History of COBie
- COBie Structure
- COBie and IFC
- Demystifying COBie in Revit
- Implementing COBie at Texas A&M
- Implementing COBie at US Dept of State