COBie

COBie
Name	COBie
Abbreviation	COBie
Domain	Building information modeling
First published	2007
Developer	Construction Operations Building Information Exchange Working Group
Related	Industry Foundation Classes, IFC, ISO 16739, gbXML

COBie COBie is a data schema for capturing and exchanging asset information in building and infrastructure projects to support Facility management workflows, Asset management processes, and handover between design, construction, and operations teams. It complements model-centric standards such as Industry Foundation Classes and formats like IFC and gbXML while aligning with procurement and lifecycle requirements from organizations like W3C, ISO, and national standards bodies. Developed through collaboration among practitioners, vendors, and agencies, it targets interoperability among providers including Autodesk, Bentley Systems, Trimble, Nemetschek Group, and public owners such as General Services Administration and US Army Corps of Engineers.

Overview

COBie's purpose is to provide a structured, consistent deliverable for equipment lists, room data, product metadata, and maintenance information to reduce transfer errors between design teams, contractors, and operations clients such as British Standards Institution, National Institute of Building Sciences, and municipal authorities like New York City Department of Buildings. The schema is expressed as tabular spreadsheets, XML schemas, or mappings within IFC models for compatibility with toolchains produced by vendors including Graphisoft, Dassault Systèmes, Siemens, Oracle, and IBM. COBie entries include identifiers, serial numbers, manufacturer names, warranties, and spare parts references to aid lifecycle management by entities such as FM vendors and asset registries used by institutions like University of Cambridge and Massachusetts Institute of Technology.

History and Development

COBie originated from practitioner needs articulated in programs led by organizations like National Institute of Standards and Technology and project pilots in partnerships with stakeholders including GSA Modernization Program and the U.S. Army Corps of Engineers. Early development involved collaboration among industry consortia and standards committees such as buildingSMART International and workstreams influenced by initiatives from European Committee for Standardization and national labs like Argonne National Laboratory. Milestones include data exchange pilots with software from Autodesk Revit, Bentley MicroStation, and integrations tested by research groups at Loughborough University and University College London before formalization in international guidance and guidance adoption by ministries such as UK Cabinet Office and agencies including Health and Safety Executive.

Standards and Specifications

COBie maps to normative schemas like IFC and aligns with international frameworks including ISO 19650, ISO 16739, and reporting practices from International Organization for Standardization. Technical references include spreadsheet templates, XML representations, and linked-data expressions promoted by W3C working groups. Interoperability profiles were refined in coordination with vendors and certification programs run by buildingSMART International and government procurement offices such as General Services Administration (GSA). Related standards and initiatives include PAS 1192-2, PAS 1192-3, BS 1192, National BIM Standard-United States, and data dictionaries used by organizations like OMNICLASS and UniFormat.

Implementation and Workflow

Typical COBie workflows start during conceptual design with asset tagging practices coordinated by clients such as Ministry of Defence (United Kingdom), continue through construction managed by contractors like Skanska or Laing O'Rourke, and culminate in handover to operators such as CBRE or JLL. Implementation steps involve model authoring in tools by Autodesk, validation using software from Solibri or Speckle Systems, and delivery in spreadsheet, IFC, or XML packages acceptable to owners such as Department of Defense facilities. Quality assurance and commissioning activities draw on methods used by consultants from firms like Arup and AECOM and testing protocols applied by certification bodies including BREEAM and LEED assessors.

Software and Tools

A wide ecosystem supports COBie through capabilities in authoring, extraction, validation, and asset management. Prominent vendors offering integrations or native export include Autodesk, Bentley Systems, Graphisoft, Trimble, Nemetschek Group, Solibri, Speckle Systems, SimpleBIM, FME, Bluebeam, Oracle Primavera, IBM Maximo, and SAP. Open-source and academic tools originate from projects at University of Salford, University of Liverpool, and community initiatives facilitated by buildingSMART International and developer communities on platforms like GitHub and collaboration networks such as Open Source Software foundations. Validation suites and converters are produced by consultancy firms like Atkins and technology vendors including CETAS and Vico Office developers.

Use Cases and Benefits

COBie supports asset register creation for clients such as Hospitals NHS Trusts, universities like University of Oxford, and transit authorities including Transport for London; it enables predictable handover for military facilities managed by US Army, commercial portfolios run by CBRE, and data-driven facilities programs at corporations like Google and Amazon. Benefits include reduced facilities management startup costs, clearer procurement specifications for firms such as Arup and Skanska, and improved maintenance planning for equipment supplied by manufacturers like Siemens and Honeywell. It facilitates regulatory compliance in jurisdictions using standards from bodies like British Standards Institution and supports digital twins programs championed by organizations including Siemens and IBM.

Challenges and Criticism

Critics from academia and practice, including researchers at University of Melbourne and consultants formerly at KPMG, cite inconsistent adoption across vendors such as Autodesk and Bentley Systems, ambiguous mapping between IFC entities and spreadsheet fields, and limitations when applied to complex infrastructure projects for agencies like Network Rail or Transport for NSW. Other challenges noted by industry groups like buildingSMART International include gaps in product lifecycle metadata, variation in national implementations by ministries such as Ministry of Housing, Communities and Local Government (UK), and difficulties integrating with enterprise systems from SAP and Oracle. Ongoing work by standards committees and research teams at institutions including Massachusetts Institute of Technology and Delft University of Technology seeks to address semantic alignment, richer ontologies, and streamlined tool certification.

Category:Building information modelingCategory:Data exchange standards