Checking C COBie e fo f for c r com for co comp ... - BIM Task Group

Checking COBie 

(image courtesy TU Delft) 

for compliance 

for f continuity 

for comp 

pletenolas Nich ness Nisbet 

February 2013 

© AEC3 UK Ltd

Checking COBie using the COBie-UK-2012 application 

0 Introduction 

The BIM 

task Group has already published an outline guide to t COBie-UK-2012 including 

checklists for compliance. It is expectedd that subsequent submissions of COBie datasets 

should show continuity whilst adding more detail. Recently the published templates has 

been developed into the COBie-UK-2012 demand matrix. These publications allow 

the 

development of tools to check the quality of COBie 

datasets. 

Since the first steps of UK BIM implementation, the importance of levels of detail within 

BIM adoption have 

been recognised. The recurrent remark for the needd to identify 

what 

information was to 

be exchanged and when, has led to the developmend 

nt of a UK BIM 

Element and Attribute Demand Matrix. 

The UK BIM Element and Attributee Demand Matrix (COBie-UK- 

standards for information 

necessary to include in BIM models from 

inceptionn through project p delivery establishing 

what information 

is exchanged at several project stages. This guidancee is presented as a 

2012_DemandMatrix.xls based on COBie), starts to provide 

COBie-like document to be used for identifying and tracking BIM information, it covers 

Building 

Information Types, (as well as Facility, Floors, Systems and Spaces), when they 

are relevant, and to what level of development (in-line with CIC stages) throughout a 

building 

lifecycle. The Systems, Types and Spaces 

elements are organized and ordered 

by general Uniclass classification and properties listed as Attributes, marked with the CIC 

stage by which they are expected. 

To 

prove the 

concept the demandd matrix is being tested to show how the 

information listed under spatial and physical objects could bee used to answer clients’ 

questions. Using a Classroom 

as an example, 10 Types from the Objectt Matrix were 

prioritised (FFE, Doors, Windows, Wall exterior, Wall interior, General Lighting, Audio 

Visual, Telecommunications 

and Data Network). The properties presumed to answer 

clients question were selected and included on the 

Classroom 

BIM model at specific 

project stages (released as IFC I and as COBie at four specific CIC stage-gates). 

To 

demonstrate automated checking, a single application (developed by AEC3) 

generates three separate marked up versions of a COBie submittal thatt show: 

Compliance with the COBie standard, checking data integrity 

Continuity is judged by 

detectingg the addition and removal of f objects and 

attributes, along with changes. 

Completeness is judged against a list of properties and a attributes along 

with 

the expected stage at the t end off which they should be provided. 

Deliverables: 

o 

o 

COBIe-UK-2012.msi (installer for a Windows 64-bit application, 

including three open-source rules sets, and this handbook). 

COBie-UK-2012_DemandMatrix. 

xls (COBie-like summary of 

expected attributes by CIC stage-gates). 

Examples 

o 

o 

Standard_Classroom_CIC_n.ifc (example 

classroomm model att CIC 

stages 2,3,5, ,6) 

Standard_Classroom_CIC_n_asCOBie.xls 

(example classroom 

COBie at CICC stages 2, ,3,5,6) 

© 2013 AEC3 UK Ltd 

2 

February 2013


AEC3 has developed the “COBie-UK 

K-2012” tool and thee underlying rule sets for 

the UK 

BIM task 

Group to distribute. Neither AEC3 nor the UK BIM Task Group 

makes 

any warranty on the speed or efficacy 

of the tools. Issues of compliance, 

continuity and completeness are ultimately profession 

nal and contractual 

judgements. 

The application 

is at ‘alpha’ stage of development, andd some functionality 

has 

yet to be tested. Comments, observations and suggestions may be sent either 

to BIM 

task group http:// /www.bimtaskgroup.org/contact/ or too nn@aec3.com 

. 

0.1 Compliance, 

Continuity and Completeness 

Figure 1: Checking 

interface 

The application generates three separate marked up versions of the COBie, with 

highlights in red, amber and green withh comments on the sheets, rows s and cells that t 

are: 

(a) non-compliant. (Compliance) 

(b) additions, changes and deletionss since an earlier version (Continuity) 

(c) excessive or missing data for the current stage (Completeness).. 

All issues are classified but the appropriate remedial action may not necessarily be the 

one recommended, especially if the issues arose in a model or database. 

Issues represent the generall opinion off the authors of the relevant standards and other 

recommendations. Issues are graded by their anticipated serious from the point of view 

of the client as recipient. 


3 

February 2013


Figure 2: Example 

file selection 

The following sectionss discuss the Compliance, Continuity and 

Completeness critieria. 

0.2 Quick reference 

Red 

Amber 

Green 

Compliance 

Broken 

Incomplete 

Inadequate* 

Continuity 

Removed 

Changed 

Added 

Completeness 

Late 

Expected 

Early 

Note: Judgement 

is still required to evalayte the accuracy off the reports and the 

appropriate action. 

*A green cell may 

still require examination and correction. 

0.3 Outcomes 

The outcomes are available as 

 

 

Three marked up COBie datasets with red, amber and green issues highlighted. 

A detailed log of the same issues 

0.4 Uses 

The mark-up and log can be used to monitor … 

 

 

 

evolving supply side 

deliverables 

planned demand side deliveries 

third party 

COBie authoring and generation applications 

The Red/Amber/Green coloration may form the basis of a scoring mechanism, typically 

based on an estimated number of hours effort needed to resolve the issues. 


4 

February 2013


0.5 Additional checks 

The rules are captured in an open rule format (XSLT) designed to be applied to an 

open 

XML representation of the COBie (Spreadsheet XML 2003). Users can therefore review 

and extend the rules set. 

The COBie-UK-2012 application can be replaced with openly available XSLT toolkits 

(such as Saxon, Xalan, Altova or MsXML). 

0.6 Interactive usage 

(see screen shots above) 

COBie-UK-2012.exe 

The user may make a desktop shortcutt to the expected location of the 

this supporting documentation. 

program and/or 

C:\Program Files\ \AEC3\BimServices\COBie-UK-2012.exe 

C:\Program Files\ \AEC3\BimServices\COBie-UK-2012.pdf 

0.7 Command line usage 

To check compliance only: 

COBie-UK-2012.exdir 

current_compliance.xlsx 

dir current.log 

current.xlsx >current.log 

To check compliance and continuity: 



dir current_continuity.xlsx 


previous.xlsx current.xlsx >current.log 

To check compliance, continuity and completeness: 



dir current_continuity.xlsx 

dir current_completeness.xlsx 


demand.xlsx previous.xlsx current.xlsx 

x >current.log 


5 

February 2013


1.0 

Compliance 

Compliance is judged by reference to the COBie data schemaa and otherr requirements. 

1.1 Compliance 

requirements 

Compliance with the COBie standard checks dataa integrity. 

This stage does not check the continuity nor completeness. 


checks 

The following COBie structural and content checks 

are made: 

 

 

 

 

 

 

 

No unexpected sheetss 

Sufficient contacts (one or more) and facility (exactlyy one) row. 

Unique rows - no duplication of objects or supplementary data) 

Relational integrity – any reference cell (pink) refers to some other valid row 

Relational integrity - valid pickss from pick-lists 

Valid dates, emails, numbers 

Useful values in mandatory cellss 

In addition the following UK expectations are checked: 

 

 

 

 

Facility.Phase shall use the format “CIC n : aaaaaaa” 

This 

is critical for subsequent Completeness checking – see section 3. 

The region is set to en-UK or en-GB 

This 

confirms that t UK classification 

is expected 

Each Space 

is assigned to at least one Zone 

This 

supports the overall “business case” 

Each Component is assigned to at least one System 

This 

supports the focus on “cost, carbon and value” v . 


6 

February 2013


1.4 Origination of compliance ruless 

The sources for these rules include: 

 

 

 

 

Published COBie internal rules 

COBie Responsibility matrix 

COBie‐UK‐2012 documentation 

Additional UK expectations (see above). 


Checking method 

All sheets are copied, and checks are applied on the Sheets, Rows and 

Cells. 


RAG 

All issues found are graded but appropriate the remedial action may not necessarily be 

obvious, especially 

if the issues arose from a model or database. Judgement is still 

required to evaluate the accuracy of thee reports and the appropriate action. 

Compliance 

Red 

Amber 

Green 

Broken 

Incomplete 

Inadequate* 

Broken or duplicated entries 

Poor value 

Note: *A green cell may still require examination 

and correction. 


7 

February 2013


1.9 Example 


Compliance issues marked up on 

the Contact sheet 

BimServices COBie-UK-2012-64 v2012-12-17T12:00:00 licenced to AEC3 UK Ltd. 

_Compliance v2012-12-19 of COBie byy AEC3 UK Ltd on 2013-01-07T12:12:57 

Table ! 

 

 

 

Contact 

Broken : Contact “ejesus@unknown.com” 

Category “ n/a” does not match an 

entry in its 

PickList. ( unmatchedd pick). 

Inadequatee : Contact “ejesus@unknown.com” Company “n/a”. (unuseful value). 

Inadequatee : Contact “ejesus@unknown.com” Phone “n/a”. (unuseful value). 


8 

February 2013


2 Continuity 

Continuity is judged by detecting the addition and 

removal of o objects and attributes, 

along with changes. 

2.1 Continuity requirements 

 

 

Continuity is 

expected where a series of deliverables are made to the client 

Continuity is 

based on the unique naming of COBie objects and supplementary data 

2.2 Continuity checks 

Checked 

 

 

 

Sheets 

are matched and checked for additions, changes, or deletions. 

Rows are matched (by unique name, compound name or by row 

position) and checked for additions, 

changes, or deletions. 

o Row matching by y ExtIdentifier (GlobalId orr GUID) is 

not 

attempted. 

Cells are matched and checked for additions, 

changes, or deletions. 

2.3 Origination of continuity rules 

It includes 

 

 

. 

Implied COBie process rules 

COBie‐UK‐2012 documentation 

2.4 Continuity Checking method 

All sheets are examined, and 

checks are applied on the Sheets, Rows ( with those Cells 

that contribute to the unique 

identity off each Row), and finally on the content of Cells. 

2.5 Continuity RAG 

All changes detected are graded and logged. Judgement is still s required to evaluate the 

accuracy of the reports and any appropriate action. 

Red 

Amber 

Green 

Continuity 

Removed 

Changed 

Added 

Data is re-instated 

Previous value is added as a comment 

Data that has been added 


9 

February 2013


2.6 Example 

Figure 4: Continuity issues found on a Component sheet. Type references r have been lost. 

Continuity v2012-06-01 of COBie relative to previous baseline by AEC33 UK Ltd on 

2013- 

01-03T15:31:34 

Param : baselinee taken as C:\COBie2\ 

\Standard_Classroom_CIC_5_asCOBie2.xml 

 

 

 

Table ! Component 

Changed : Component “Twin Switched Socket 

Outlet:PROJECTOR: 

:PROJECTOR:195895“ CreatedOn “2012-12-12- 

13T15:56:14.000” to t “2012-12-13T16:00:00.000” 

Changed : Component “Twin Switched Socket 

Outlet:PROJECTOR: 

:PROJECTOR:195895” TypeName “Twinn Switched 

Socket Outlet:PROJECTOR” too “n/a” 


10 

February 2013


3 Completeness 

It is not possible to automatically verify the completeness of o the list of Components and 

Spaces. Seee COBie‐UK‐2012 documentation for 

guidance on the expected Components 

and Spaces. 

Compliance requires that at least one System and 

Zone should exist for all Components 

and Spaces respectively and that Floorss and Types should exist for all Spaces and 

Components respectively. 

Completeness is judged against a list of properties 

and attributes alongg with the stage at 

the end 

of which they are expected. 

Compliance requires that the 

Facility.Phase must be marked according 

such as 

“CIC 2 : Design “ 

to CIC stages 

Figure 5: COBie facility sheett showing the current CIC stage (extreme right hand side) 

3.1 Completeness requirements 

Given the lists of these objects, it is possible to check that the expectedd object 

properties, Attributes and Impacts and Documents have been provided. 

The next level of specification and checking rests on the preparation of f a matrix of COBie 

Objects 

(Facility, Floor, Space, Zones, Types, Systems and ComponentsC 

s), their attributes 

and relationships 

and the stage gates they are expected as part p of the Employers 

Information Requirements. 

What? Object and 

specialisation… 

What aspect? Property 

or attribute … 

When expected? On completion 

of… 

Corridor spaces 

Net area 

CIC 3 : Design 

development 

Note that since COBie is expected to bee specified as part of the t Employers Information 

Requirements, the 

Demand Matrix mayy be specificc to a project or programme. However, 

the Demand Matrix can be maintained and developed so as to t be as generic and re-r 

usable as possible. 

3.2 Demand side 

matrix 

Amongst the many possible presentations of the Demand Matrix, the most directly 

useful 

form is to use COBie itself. This has thee following benefits: 


11 

February 2013


(1) COBie is naturally familiar and so no new nor informal structure is needed. . 

(2) Existing templates and examples can be rapidly re-used. Best practice can be 

automatically cut-and-pasted from existing 

COBie models. 

(3) Descriptions, enumerated allowed values and complex types (lists, tables, 

ranges) are 

available. Assignment to property sets can be documented. 

(4) COBie authors can cut-and pastee from the Matrix. 

(5) Checking applications 

can consume both the receivedd COBie andd the Matrix 

systematically. 

(6) Classification references can be included. Note that the methodology is 

independent of any specific choice of classification, ass long as the chosen table t is 

used in both the Demand matrixx and the COBie model. 

(7) Both COBie 

Object sheets (facility, system, 

component, type, floor, zone, space 

etc) and COBie Supplementary sheets (attribute, document, impact etc) can have 

the demands documented. 

Examples of the COBie Object and Supplementary 

sheets with expectedd gate of delivery 

appear below. 

3.3 Stages 

The matrix will document the 

expected delivery gate: specifically it will identify the stage 

at the end of which the gate occurs. This is preferable to identifying drop numbers 

which 

may be 

redefined by the client. The current drop names can be correlated againstt with 

the CICC stage gate 

names. 

UK CIC Scope of Work (COBie Facility.Phase) 

CIC 1 : Brief and early design 

CIC 2 : Concept 

CIC 3 : Design Development issued for tender 

CIC 4 : Tender submission 

CIC 5 : Contractors design development and planning 

CIC 6 : Handover 

UK BIM task group ‘footballs’’ 

Drop 1 

Drop 2a 

Drop 2b 

Drop 3 

Drop 4 

Note: the description of the facility f phase (after the colon) iss not significant in the 

Completeness checking. 

3.4 Supply side 

The Demand matrix is intended to document the Demand-sid 

de expectations. It can be 

further amplified to document information requirements within the design and 

construction Supply chains. The stage at which each specific the information is first 

captured or documented may be earlierr than the stage at which it is expected by the 

Client. Some dataa may be expected by agreed processes internal to thee Supply side even 

if not demanded by the Client. 

Within a specific project, responsibility 

for authoring can be documented 

ed using the 

‘Created By’ column, inserting entries from the Contact tab. Similarly the stage gate at 

which objects should be supplied can be documented in the ‘Created‘ 

On’ column. 


12 

February 2013


Any such internal Supply side information is not checked by the 

rule-set. 

Completeness 

Note that if the Supply side does develop the matrix further, it must fit t within, and not 

conflict 

with, the Demand Matrix as referenced from the EIR. For example, the Supply 

chain should not plan to firstt supply data at a stage later than when it is being 

demanded. 

3.5 Spatial and Physical Aspects of the Demand Matrixx 

Both COBie models and the Demand matrix cover 

two distinct information aspects: 

about the spatial objects (Floors, Spaces and Zones) and about the physical objects 

(Components, Systems and Types). The variety of physical objects o means that the 

demands will be for more extensive compared to those about the spatial objects 

3.6 Demand Matrix 

Each demand matrix needs to t specify two distinct aspects: demands d onn the fixed objects 

sheets, and the demand on the t supporting attribute sheets. 

3.6.1 Object Demand Matrix 

The expected stage that the fixed columns on the COBie object sheets can be 

documented. Some Sheets will need several rows to cover all the potential object 

specialisations and 

predefined types. 

Where there are several specialisations, such as types of Space, the category attribute is 

used to 

create a correspondence between the Demand Matrix and the Model. 


of a COBie 

Demand Matrix for Spaces (correction: created by, created 

on and category should not be 

tagged with a CIC stage; The Category attribute mightt read 

D: Spaces). 

In this example, Spaces should be created during the briefing stage, but the net area is 

not expected until 

after design development. The room tag may not bee determined until 

handover. 

The following object sheets are includedd in the Completenesss check: 

(a) Contact 

(b) Facility 

(c) System, Type, Component 

(d) Zone, Floor, Space 

Entries in the object sheets in the Demand Matrix are relatedd to entriess in the object 

sheets in the current COBie model by their category (classification) codes. Component 

entries are related 

through the classification of their Types. 

Exceptionally, the single Facility entry is directly related, without use off any category 

connection. 


13 

February 2013


3.6.2 Supplementary Demand Matrix 

The following supplementary 

sheets aree included in the Completeness check: 

(a) Attribute, Document, Impact 

(b) Spare and Job 

The stage at which the flexible rows on the COBie supplementary sheets are expected 

can be documented. Most attention is needed on the Attribute sheet. 


from a COBie Demand Matrix Supplementa 

ary tab for Attributes 

(correction: the RowName should not be * but a space name from the Space sheet of the t 

demandd matrix.). 

In this example, Spaces should be given an Occupancy Number (part of the property set 

for Space Occupancy) during 

the briefing stage, but the Net Volume (part of the set of 

Base Quantities) is not expected till Design development is completed. 

c 

Entries in the supplementary 

sheets in the Demand Matrix are related to entries in 

the 

supplementary sheets in the current COBie model by the category (classification) 

codes 

of their 

owning objects. Entries in the Supplementary sheetss of Components are related r 

throughh the classification of their Types. 

The key 

value on these supplementary 

sheets, where the expected CICC stage is 

documented, are: 

Supplementary sheet 

Attribute 

Document 

Impact 

Job 

Spare 

Column where CIC stage expectationn set 

Value 

(see figure 6 above for examples) 

File 

Value 

Frequency 

Supplier 

So to demand that a certain Document is made available at CIC stage 4, the Document 

should be described and associated to the Facility (or other object) o but the File cell must 

be set as “CIC 4” 

3.6.3 

Other sheets 

The following sheets are excluded from 

the Completeness check, as, for the reasons 

indicated, it is not 

practical to t demand their provision: 


14 

February 2013


(a) 

(b) 

(c) 

3.7 Derivation of demand matrix 

It includes 

Introduction, PickList (part of the COBie format, not the deliverable data) 

Resource, Coordinate (unclassified secondary data). 

Assembly, Connection, Issue (relating multiple objects) 

 

 

 

 

 

common properties from 

COBie for facility, floor, space, zone, system, type, component, etc 

properties and quantities from buildingSMART recommenda 

ations for spaces, systems and 

types etc 

classifications from Uniclass, Uniclass2, and NRM 

(on the space and typee objects etc) ) 

recommended properties from NBL (on system and type etc) 

additional properties from BIM Taskk Group lessons learnt. 

(a) The demand "CICC n" is set in the cells that support the client purposes (business case, use, 

replacement, maintenance); other attributess (such as BREEAM?) may be listed even though they t do 

not have 

a "CIC n" value set. 

(b) Properties are expected to have the same name at every stage. 

3.8 Completeness Uses 

The Demand Matrix can be developed as part of the project preparationn process. 

 

 

 

broaden or narrow the scope according 

to the EIR. 

include internal supply side exchanges. 

reflect supply side delegation 

n of responsibility. 

The demand Matrix can be used during a project 

 

 

 

 

As a part-populated 

COBie deliverable. 

As a resource for cut-and-paste into a COBie deliverable 

As a checking rule-set against a COBie deliverable at a given stage. 

As a checking rule set on demand side deliveries. 


15 

February 2013


3.9 Completeness Checking methodd 

The COBie model must contain the Facility.Phase 

as a CIC number (CICC n). 

3.9.1 Object and 

supplementary demands 

For 

each sheet, row and cell in the COBie model 

If it 

is a supplementary 

sheet, get the object record 

If the object record is a Component, get the Type record 

Get 

its classification 

Find 

the object(s) in the Demandd Matrix with a correspondingg classification. 

If examining Type Demand Matrix possibly 

examinee to the Component 

Demand Matrix. 

If examining a Supplementary COBie model sheet, examine e the 

Supplementary demand matrix sheet 

For 

each column in the 

COBie model 

Check if the equivalentt Demand matrix column has a demandd phase (CIC n) 

set 

Mark the COBie model cell accordingly: red, amber, green. 

3.9.2 

Missing supplementary demands 

Also at the end of 

considering each supplementary 

sheet in the t COBie model: 

For 

the Demand matrix’s matching supplementary sheet s that has a demand 

phase (CIC n) set. 

For 

each row in the Demand matrix 

Get 

the object Demand 

matrix record 

If the Demand matrix object is a Component, get the demandd matrix Type 

Get 

its classification 

Find 

the object(s) in the COBie model with 

a corresponding classification. 

If examining Components in the Demand matrix examine the e Component 

COBie model. 

Examine the Supplementary COBie model sheet 

Check if the matching COBie model row does not exist. 

Copy the Demand matrix row in red or amber to thee COBie model. 

3.9.3 

Matching 

by Category 

Both the processes use matching by Category (Classification). An object in the Demand 

matrix is matched 

to an object in the COBie model if the category codee of the object in 

the Demand matrix “is a prefix of”/”commences” the category code of the object in the 

COBie model. 

 

 

Example of a match 

o Matrix: “L34 : Stuff” 

o Model: “L341 : Detailed stuff” 

Example of a non-match 

o Matrix: “L34 : Stuff” 

o Model: “L3 : General Stuff” 


16 

February 2013


3.10 Completeness RAG 

Red 

Amber 

Green 

Completeness 

Late 

Expected 

Early 

Property 

expected at ann earlier phase 

now 

expected and due 

found early. 

Note: Judgement 

is still required to evaluate the accuracy off the reports and the 

appropriate action. 

*A green cell may 

still require examination and correction. 

3.11 Example 

Figure 

CIC 1 

8: Demand 

matrix for Facility sheet (correction: CurrencyUnit etc should be marked 

Figure 9: CIC 2 Facility sheett marked up. The last column shows the Phase is “CIC 2”. 

(correction : Category should 

not be highlighted). 

 

 

 

Worksheet : Facility 

Early : Facility “Project Number” AreaMeasurement “GSA BIM B Area” CICC 3 found early 

Expected : Facility “Project Number” ” Description 

“n/a” CIC 2 now due 


17 

February 2013

Checking C COBie e fo f for c r com for co comp ... - BIM Task Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?