COBIe Support

COBIe Support

What is COBIe?

COBIe (Construction Operations Building information exchange) is an information exchange specification for the life-cycle capture and delivery of information needed by facility managers. COBIe can be viewed in design, construction, and maintenance software as well as in simple spreadsheets. This versatility allows COBie to be used on all projects regardless of size and technological sophistication.

Depending upon specific project circumstances Cadnet can collect, collate and capture data and embed the details within a project model. We can then export the data and generate data drops at specified points within the project lifecycle.

COBie is always best defined at the outset of a modelling project, but a model can if populated at a later date if required. Either way, achieving COBie compliant data drops requires client and their suppliers to provide a significant amount of information at the early stages of design development.

Who produces the information and when?

BS 1192-4 sets out the process for the information exchange – and the details should be specified in accordance with the CIC BIM Protocol in a production and delivery table.

What tools do we use to generate COBIe drops?

Cadnet uses a combination of Revit and the AutoDesk COBIe toolkit plugin and SOLIBRI to generate COBIe drops. We also utilise BIM 360 Glue and can facilitate the use of BIM 360 Field to capture and consolidate data within ‘the cloud’. In addition to the BIM toolset we also utilise the standard Microsoft Office Suite and various IFC viewers and data extraction tools.

How do we deliver COBIe data?

The process for delivering COBIe data depends on the strategic approach to a project. It can be either:

  1. A traditional Level 2 approach (separate models managed via a CDE)
    Cadnet will process incoming data and align the detail with the desired outcome, adjusting asset related data into the correct format and importing the detail into the host model as necessary. The COBie drops are generated in an editable XLS or database format and textual data is imported as necessary.
  2. A pseudo Level 3 approach (separate and single models managed in the cloud)
    Similar to the process above, but the data is uploaded to the cloud. This strategy and approach depends on our client’s capability with cloud based applications.