COBie UK 2012 PDF

COBie-UK-2012

V11
NicholasNisbet
10thJuly2012
UK COBie 2.4 Requirements
2012 AEC3 UK Ltd 2 July 2012

COBie UK
Required Information for Facility Operation
This document is the potential draft of a new BSI PAS, and should be read in conjunction with the
published examples and templates.
Illustrations are acknowledged from USACE ERDC and AEC3 unless otherwise stated.
Date Version Author

2012-02-17 V08 First issue for consultation nn@aec3.com
2012-02-21 V09 Improved formatting. nn@aec3.com
Gate process diagram added.
Impact requirements aggregated
Structure used as infrastructure synonym for
building Fabric
2012-03-23 V10 Improved description of sheet, column and row nn@aec3.com
requirements .
Recommended additional Attributes appended
2012-06-10 V11 COBie drop examples included nn@aec3.com
COBie Type templates referenced

Contents
Required Information for Facility Ownership ........................................................................................... 1
0 Overview .................................................................................................................................................... 6
0.1 The Owners View.................................................................................................................................... 6
0.2 The Designers and Contractors View ...................................................................................................... 6
0.3 Product Specifiers and Suppliers ............................................................................................................. 6
1 Scope .......................................................................................................................................................... 6
1.1 Objective ............................................................................................................................................. 7
1.2 Audience ............................................................................................................................................. 7
1.3 Applicability ........................................................................................................................................ 7
1.4 Organization ........................................................................................................................................ 7
1.5 IFC and COBie ..................................................................................................................................... 8
1.6 Background ......................................................................................................................................... 8
1.7 Process ................................................................................................................................................ 8
1.8 COBie for infrastructure and building ................................................................................................. 9
1.9 COBie for existing facilities and refurbishment .................................................................................. 9
1.10 Use of COBie information ................................................................................................................ 9
1.11 COBie Contacts ................................................................................................................................. 9
1.11 COBie Objects................................................................................................................................... 9
1.12 COBie additional information ......................................................................................................... 11
2 Referenced Standards ............................................................................................................................... 12
3 Definitions ................................................................................................................................................ 13
3.1 Requirements ................................................................................................................................. 13
3.2 Manageable assets........................................................................................................................ 13
3.3 Purposes ......................................................................................................................................... 13
3.4 Gates / Stages ................................................................................................................................ 13
3.5 Metrics ............................................................................................................................................. 13
3.6 Employers Information Requirements .............................................................................................. 14
4 Process Overview ..................................................................................................................................... 15
4.1 Process map and CIC Stages ............................................................................................................. 15
4.1 Gates............................................................................................................................................ 17
4.2 Lower tiers in the design chain and supply chain. ....................................................................... 18
4.3 Strategic, Managerial and Implementation obligations ................................................................. 18
5 Clients strategic Purposes: ....................................................................................................................... 20
5.1 P01: Registry ..................................................................................................................................... 21
5.2 P02: Use and utilisation..................................................................................................................... 23
5.3 P03 Operations .................................................................................................................................. 24
5.4 P04 Maintenance and repair .............................................................................................................. 25
5.5 P05 Replacement ............................................................................................................................... 26
5.6 P06 Assessment and End of use and Repurposing ............................................................................ 26
5.7 P07 Impacts (costs and carbon) ......................................................................................................... 27
5.8 P08 Business questions .................................................................................................................. 32
5.9 P09 Security and surveillance ........................................................................................................ 33
5.10 P10 Regulation and Compliance .................................................................................................... 34
6 Criteria and metrics: ................................................................................................................................. 35
6.1 Compliance to the COBie/IFC schema ............................................................................................. 35
6.2 Completeness .................................................................................................................................... 35
6.3 Accuracy and enumerations and classification .................................................................................. 35
6.4 Units .................................................................................................................................................. 35
6.5 Enumerations and Classifications...................................................................................................... 35
6.4 Metrics............................................................................................................................................... 36
7 Required detail ......................................................................................................................................... 37
7.0 Structure ............................................................................................................................................ 37
7.1 Instruction sheet ................................................................................................................................ 39
7.2 Contact sheet ..................................................................................................................................... 40
7.3 Object sheets ..................................................................................................................................... 41
7.4 Additional information sheets ........................................................................................................... 42
7.5 Specification of objects and additional information sets ................................................................... 42
8 Bibliography ............................................................................................................................................. 43
8.1 Definitive material............................................................................................................................. 43
8.2 UK material ....................................................................................................................................... 43

8.3 US material........................................................................................................................................ 43
8.4 Tools.................................................................................................................................................. 44
Annex A: Recommended Attributes ........................................................................................................... 45
A.1 Facility.................................................................................................................................................. 45
A.2 Space and Zone .................................................................................................................................... 47
A.3 Component ........................................................................................................................................... 49
A.4 Type and System .................................................................................................................................. 49
Annex B: COBie checklist .......................................................................................................................... 51
This checklist combines COBie standard and UK implementation rules. ................................................... 51

0 Overview
0.1 The Owners View

An owner may require the delivery of COBie from the lead designer and/or lead contractor to support the
timely delivery of information to support the management of the Facility. A complete COBie should be
expected at the time of Handover, but earlier interim deliveries can be used monitor the business case for
the facility and to help plan for taking ownership.
The COBie information can be either be kept as delivered, or held in ordinary databases, or it can be
loaded into existing Facility Management and Operations applications, either automatically or using simple
copy-and-pasting. The owner should be explicit about the purposes for which the information is required
and about the timing and content of any interim deliveries.
0.2 The Designers and Contractors View

COBie allows the team to document their knowledge about a Facility in both its spatial and physical
aspects. Spatially it can document the spaces and their grouping into floors/sectors and into other zones.
Physically it documents the components and their grouping into product types and into other systems.
Usually the information needed to complete the COBie deliverable will be available already, either in your
BIM models or in reports and schedules and in other material prepared for handover.
Some information may be offered to you in unstructured formats (such paper and scanned documents), but
you should arrange to obtain COBie information on specific aspects from other team members and
suppliers.
0.3 Product Specifiers and Suppliers

COBie can be used to document product data to support the specification/selection/replacement process. If
the client requirements include this, then the product Types should be given the specific attributes
appropriate to that Type.
There are currently 700 such templates available for general use. The RIBAE NBL initiative will be
contributing suggested UK specific properties.
1 Scope
Requiredsharedstructured
Informationincludingobjects,propertiesandrelationships
foraFacilityincludingbuildingandinfrastructure
Operationincluding(designandconstruction)stagespriortohandoverand
(use)stagessubsequenttohandover.
This Part defines expectations for the Required shared structured Information relating to spatial and

physical assets and their properties and relationships for Facilities including buildings and infrastructure in
Operation including the design and construction stages prior to handover and acquisition and the
subsequent use stages.
It is intended for use during the development of new facilities and during the acquisition and operation of
existing facilities. It is also applicable during the tendering and retendering of FM and operational
contracts. It is intended to be referred to in contractual requirements and specific contract schedules may
modify and refine the requirements. It may act as a checklist for completeness for use by both providers
and recipients of the facility data.

1.1 Objective
The objective of this document is to explain the organization of the COBIE worksheet and identify who
provides what information within the Requirement as the project proceeds from planning, to design, to
commissioning, to occupancy, to handover.
1.2 Audience
The audience for this document is client and any project team member who wants to understand what
information is required by COBie and who is responsible to provide it. This document is primarily
intended for the UK audience.
1.3 Applicability
COBie is a means for sharing structured facility data ready for use by the owner. The COBie spreadsheet
is simply one way to display an underlying harmonized international buildingSMART Industry
Foundation Class Model View. It should be noted that it is ONLY the language code and the
recommended classification lists that vary between locales. COBie data can be created and used
internationally across locales. The details of the classification lists are summarised in section 6.5
The applicable COBIE version is Version 2. Release 4 and the regional code shall be en-UK or en-
GB
Note: Where North American spelling is used for sheet names, column names and property names, these
should be preserved, in order to support reading by receiving applications that may depend on them.
1.4 Organization
This document and the Examples provide an overview of COBie including the overall structure of the
spreadsheet. The Examples provides a detailed listing of each COBIE worksheet to identify the specific
columns in each worksheet and illustrate what information is to be provided in each row.

1.5 IFC and COBie

IFC (Industry Foundation Classes) is an ISO standard data schema for holding and transmitting facility
information throughout the Facility lifecycle. IFC has been developed over the last 16 years by
buildingSMART, a not-for-profit consortium with chapters in the US, UK, Europe, MEA and the Far East
and Australia. www.buildingsmart.org
COBie (Construction Operation Building information exchange) is a data schema for holding and
transmitting information around handover to support the clients ownership and operation of a facility.
www.wbdg.com
1.6 Background
COBie is formally defined as a subset of IFC, including initially the FM-10 Handover MVD and latterly
the full COBie MVD (see normative references and bibliography). It can also be represented in
spreadsheets or relational databases. It was developed by the US Army ERDC with NASA and the
Veterans Association as a response to the perception that specifications for O&M and other
documentation did not allow these owner organisations to take on effective management immediately on
handover. The COBie data schema has subsequently been generalised for international use by ensuring
that classification and unit systems can be specified.
During traditional projects, most of the information required by COBie is already delivered in
unstructured form. COBie gives the opportunity to input critical data just once, allowing it to be re-used in
many outputs, be tested in many ways and be delivered to many applications including facility
management and asset management systems.
Figure 1: Data is preferred to documents for three strategic reasons. (image courtesy of
STABU, NL)
1.7 Process
The COBie process requires that there are progressively more complete contractually required data
deliverables throughout the design and procurement stages, culminating at the Handover point. Any
deliverable after the point of Handover are expected to consist only of corrections and data obtained
during post-occupancy assessments

Figure 2: COBie allows a continuously expanding data set to be complete at

handover.(image courtesy of USACE ERDC)
1.8 COBie for infrastructure and building

COBie is intended for use in both building and infrastructure projects, irrespective of whether there is
already structured information from the design chain and supply chain. When using COBie for
infrastructure and civil projects, the Floor sheet may be read as Sector and used for the primary spatial
subdivision of the overall project. Priority has been given to classification systems and plans-of-work that
support both building and infrastructure in a consistent manner.
1.9 COBie for existing facilities and refurbishment

The COBie format can be used to capture in-use and survey information about a facility. If direct data
entry into the COBie sheets is used, then monitoring should ensure that the recommended classifications
and property names are adhered to.
1.10 Use of COBie information

Projects can collect information in COBie as a route to updating FM systems in use, or for use in its own
right, or for interoperability with other standards such as IFC. The Employers Information requirements
may indicate the intended destination, but consistent adherence to the COBie standard serves to isolate the
supply side from these decisions.
1.11 COBie Contacts

Every participant in developing the COBie file and any third party that is referenced should have its
contact details registered in COBie. This ensures that COBie can act as a primary source of information,
as an index to supporting documentation and as an introduction to the parties in the project.
1.11 COBie Objects

Initially only the Facility need be defined, but as the design stabilises, the Floors (Sectors) and Zones can
be registered. These can then be populated with Spaces. Following on, Types and Systems are specified
and the manageable asset Components assigned. During construction specific products can be identified
and Jobs, Spares and other Resources for their maintenance and operations catalogued.

Figure 3: COBie represents the Facility as a simple spatial and physical hierarchy.
(image courtesy of AEC3 Ltd)

1.12 COBie additional information

Additional information relevant to specific kinds of objects can be associated. This additional data can
include Documents, Attributes, Coordinates, economic and environmental Impacts and Issues. Additional
relationships such as Connections and Assemblies can also be documented.
Figure 4: Various kinds of additional information can be associated to the facility and
its constituents.(image courtesy of AEC3 Ltd)

2 Referenced Standards
o UKBS1192:2007:Collaborativeproductionofarchitectural,engineeringand
constructioninformation.
o UKPAS1192part2:RequiredInformationforFacilityProcurement
o UKPAS1192part3:RequiredInformationforFacilityOperation(forthcoming)
o ISO16739:2005:IndustryFoundationClasses(IFC2x)PlatformSpecification
o ISO16739:2012:IndustryFoundationClasses(IFC4)Specification
o ISO29481InformationDeliveryManual
o ISO12006part2(UK:CICCPICUniclass)andpart3(IFD)
o UKCICUnifiedPlanofWorkprocessmap(WP104,undergoingreviewand
comment)
o COBiedocumentation(www.buildingsmartalliance.org)
o BSIPAS55:2008Assetmanagement

Seealsothedefinitivemateriallistedin8.1

3 Definitions
3.1 Requirements
Requirementsarethedocumentedexpectationsoffacilityowners/commissionersforsharable
structuredinformation.ThesearealsoreferredtoastheEmployersInformationRequirements
(EIR)(qv)(alternativelytheClientsInformationRequirements).
NOTE:DetailedrequirementsarescheduledintheExamples
3.2 Manageable assets

Thoseaspectsofthefacilitythatmaybemanagedduringthefacilitylifecycleincludeboth
physicalandspatialobjects,andtheirfunctionalgroupings.
NOTE:Anassetisauniquelyidentifiableelementwhichhasafinancialvalueandagainstwhich
maintenanceactionsarerecorded.
NOTE:Someaspects,suchasthestructuralframe,orindividualpipeandductsegments,fixings
andsecondaryelementsmaybeexcludedfromscopebytheemployer.
3.3 Purposes
ThoseaspectsoftheFacilitythatareintendedtobemanagedbythefacilityowner.
NOTE:SomePurposes,suchassupportingthebusinesscase,maybecommonwiththebriefing
anddesignprocesses.
3.4 Gates / Stages

Astandardisedprocessmapfortheacquisitionofafacilitymaybedividedintostagesand
gatewaysatsomeofwhichtheRequirementsshallbedelivered.
NOTE:ThestagesatwhichDropsarerequiredshouldbespecifiedintheEIRbyreferencetothe
agreedStageandGatenames.SeetheCICPlanofWork
3.5 Metrics
TheacceptabilityofthedeliverablemaybeassessedagainsttheRequirementsshowninthe
Examplesand/oragainstindicativeratiosandcountsbasedontheinformationprovided.

3.6 Employers Information Requirements

The Employers Information Requirements of the Contract shall nominate:
(a) Which Gates require a data deliverable (Drops)
This document uses the following drops
CIC 1: Drop 1: brief / early design
CIC 3: Drop 2a: design development issued for tender
CIC 4: Drop 2b: tender submission
CIC 5: Drop 3: contractors design development and planning
CIC 6: Drop 4: handover
(b) Whether COBie and/or IFC and Version required. Typically this will be either COBie 2.4 UK
or IFC2x3 CV2 with QTO and Space boundaries level 2. Other proprietary model and
document formats may also be required.
(c) Which Purposes are included and excluded for the data by reference to section 5. Typically this
will include P01-P10 (see section 5 below), along with any additional purposes by extension to
section 5.
(d) Any additional checks and metrics by extension to section 6.
(e) Any additional content by extension to section 7. This may define which of the requirable
(green) fields are required.

4 Process Overview
4.1 Process map and CIC Stages
Note: CIC and individual institutions may publish a concordance with their current plan of works.
4.1.1 CIC 1: Brief - ending with Drop 1

The Brief defining the project objectives, business need, asset management plan, Client priorities and
aspirations; describing the acceptance criteria, including function, mix of uses, scale, location, quality,
cost (Capex & Opex), value, time, safety, health, environment and sustainability (Carbon, embodied and
in use).
4.1.2 CIC 2: Concept

The Project Brief as approved by the Client at the conclusion of Stage 2, establishing the detailed brief,
scope, scale, form and budget and setting out the integrated concept for the Project; Confidence 75 to
80%, margin 20 to 25%
4.1.3 CIC 3: Design Development ending with Drop 2a

The Project Brief as approved by the Client at the conclusion of Stage 3 , developing in detail the
approved concept to finalise the design and definition criteria, establishing the detailed form, character,
function, cost plan (Capex, Opex),Carbon (embodied and in use); defining all components in terms of
overall size, typical detail performance and outline specification.
Confidence 85 to 90%, margin 10 to 15%
4.1.4 CIC 4: Production Information ending with tender and drop 2b

Integrated production information enabling the production of manufacturing and installation information
for construction. Updated Capex, Opex, Carbon use.
4.1.5 CIC 5: Constructed Information ending with drop 3

fabrication and manufacturing details, verification, operation and maintenance. Updated Capex, Opex, and
Carbon. This should also include as constructed updates to the production information. The model and
the documentation should fully reflect the actual construction, defect and tolerance deviation as the basis
for the asset model.
4.1.6 CIC 6: Handover - with drop 4
As constructed systems, operation and maintenance, updated predicted in use performance, (Carbon use,
Capex and Opex).
4.1.6.1 CIC 6A : Post fit-out Handover

Updated As constructed systems, operation and maintenance, updated predicted in use performance,
(Carbon use, Capex and Opex).
4.1.7 CIC 7 : Post Practical Completion

As constructed systems, operation and maintenance, in use performance compared against brief,
(function, mix of uses, scale, location, quality, cost (Capex & Opex), value, time, safety, health,
environment and sustainability (Carbon, embodied and in use)).

Figure 5: Swimlanes showing CIC Stages 1- 7 and Gates G1-G7.

4.1 Gates

GatesG1toG7occurattheendoftheassociatedstageCIC1CIC7.
COBiedropsshallbemadeatGatesG1,G2,G3andG6
NOTEtheEmployersInformationRequirementsmayaddadditionaldeliverygates.
TheclientappointedfirsttierpartyshalldelivertheRequirementstotheClientatleastatthe
specifiedgatesincludingG3DesigncompletionorG6Handover.

NOTEfirsttierpartywilltypicallybeleaddesignerorcontractor.
Figure 6: Drops are planned to support client decision processes.

4.2 Lower tiers in the design chain and supply chain.

Partiesmayensurethatlowertierpartiesbesimilarlyobligatedtodeliverspecifiedaspectsof
theRequirementsinpreparationfortheseGates.

NOTEAlowertierpartycouldbeaspecialistdesignerorsubcontractororproductsupplier.
NOTEFigure6showsatypicaldelegationprocess.
Figure 7: Generic process map for delegation of Requirements.(image courtesy of AEC3

Ltd)
4.3 Strategic, Managerial and Implementation obligations
Apartyshallfulfilitsstrategic,managerialanddetailedobligationsforthedeliveryoftheEIR
4.3.1Strategic:
(a) ReceiveandacceptRequirement(EIR)
(b) PropagationofRequirement(EIR)downwardstonexttier
(c) Reviewandapprovalpriortosubmission

4.3.2ManagementandQualityAssurance
(a) Reviewofreceivedinformation
(b) Receiptandmerge/integrationofdelegatedsubmissions
(c) Reviewofpreparedinformationforcontinuity,completenessandaccuracy
4.3.3Implementation
(a) Entryofexpectedinformation
a. Useofspreadsheetordatabaseapplications
i. Useofcopyandpaste(usepastespecial:textonly)
ii. Useoffilter/sort
iii. Useoftextbasedformulae
b. UseofBIMauthoringtools
i. UseoftheProjectInformationcommands
ii. Useofthevendorsspecificcommandsandtoolkits
iii. UseofexporttoIFCandmappingtoCOBie
c. UseofNBSCreate,Codebook
i. UseoftheexporttoCOBiecommand

Note:ForexampleAutodeskRevitcanbeaugmentedwithCOBietoolkits.
NOTE:Applicationvendorsmayprovidespecificguidanceonthemanagerialand
implementationoftheCOBierequirements


5 Clients strategic Purposes:

The supply of accurate and complete information shall support the Employers purposes for asset
management. These may include strategic anticipation, planning and execution of the following ten
distinct purposes: [P01-P10]. Each of these purposes shall be explicitly included or excluded from the
Employers Information Requirement. Whilst the COBie format is required for the delivery of this
information, other information requirements may be met by the delivery of the 3D model(s) (IFC and/or
proprietary format) with supporting documents and drawings. These resources should be associated to the
appropriate COBie objects.
Note:TheprimarydriverfortheearlydropsistomanagetheP08businesscasebasedonP02
UseandP07Impacts.
Purpose Detail BSI Pas 55 references
P01 Registration Registration of the assets is a prerequisite 4.5.1a, 4.4.6, 4.6.6, 4.5.1.3
for the following purposes.
P02 Use and utilisation Includes data for any soft-landings usage 4.5.1b, 4.5.1 i, 4.5.1.4
review
P03 Operations Includes data for any soft-landings 4.5.1 i, 4.5.1.2, 4.6.1
operational review
P04 Maintenance and Includes the tasks and required resources 4.5.1c, 4.5.1.2, 4.5.1.5,
repair and spares. 4.5.2
P05 Replacement Includes information relating to the 4.5.1.7
specification and selection of Types.
P06 Assessment and re- Including end-of-use, re-purposing and 4.5.1d, 4.5.1.6
use facility capacity analysis
P07 Impacts Economic and environmental (but not 4.5.1 iii
social) impacts
P08 Business case Continuously review is the primary driver 4.5.1
for the intermediate Drops.
P09 Security and Aspects of the model may be specifically 4.4.7
surveillance excluded from shared data.
P10 Regulation and Information relating to the H&S and CDM 4.5.1 iii, 4.6.2, 4.4.8
Compliance and safety of operations in the facility
Table 1: Summary of Employers Purposes and references to BSI PAS 55 part 1 & 2.

5.1 P01: Registry

Registration of assets is required to support accurate audit and reporting. This includes GIS, land
and address identification for the facility. Include spaces and users zoning. Include stacking
(Floors) for buildings or sectoring (Sectors) for infrastructure.
5.1.1 Facility, Floor (Sector) and Zones , Spaces
o One facility
o Every distinct Floor (sector) and outside space and site
o Every manageable/accessible space.
spaces identified in design drawings and/or related schedules.

o Zones at least for public/private access (and other Zones where known).
Note: Design or construction zones need not be provided.
o Every Space shall be assigned to one Floor (Sector)
o Every Space shall be assigned to one (or more) Zones.
o Identity, including Name, Description, Classification, Ext System Id (if available)
o Facility and optionally Floor (Sector) : GIS referencing (lat, long, elev, Site address in
SiteDescription, UPRN, TOID, BuildingID and other LandTitleNumber
registration as Attributes.
Note the orientation of the facility (for example rotation from true North) as used in BIM authoring and
analysis tools is not required in COBie.
o All mandatory fields must be provided as illustrated in the Examples.
Note: In general, properties associated to buildingSMART objects and Pset_ property sets and Base
Quantities quantity sets are mandatory. The example Attributes include other properties provided by BIM
applications.
Note Plan and 3d shapes are not required.

5.1.2 Components, Types and Systems
o Every manageable asset Component
every products and equipment found in design drawings and/or schedules.
o Every distinct functional System including substructure, structure, envelope
o Every distinct Type
Generic or specific products
Constructions and assemblies
Materials
o Every Component shall be assigned to one Type
o Every Component shall be part of one (or more) Systems.
o Identity, including Name, Description, Classification (Types and Systems), Ext System
Id (if available)
o All mandatory fields must be provided as illustrated in the Examples and Templates.
Note: In general, properties associated to buildingSMART objects and Pset_ property

sets and Base Quantities quantity sets are mandatory. The example Attributes include
other properties provided by an actual BIM applications.
Note Plan and 3d shapes are not required.

5.2 P02: Use and utilisation.

Documentation of the intended use, capacity and utilisation of the Facility is required to support
comparisons of actual use and utilisation and portfolio management. It also supports improved
briefing for future projects.
Note: This may include data for soft-landings usage review.
Facility, Floor (Sector) and Zones , Spaces
o Classification
o Functional benefits
areas (net and gross)
the method of measurement used shall be documented on the Facility sheet
bed/pews/occupants/clients.
Note: RICS NRM schedule E contains a list of suggested beneficial measures.
o Utilisation and hours of intended use
Utilisation as a percentage where 24/7 = 100%

5.3 P03 Operations

Information necessary for the normal operations of the facility is required to support the facility operators
and the owner to anticipate costs of operations.
Note: This may include data for soft-landings operations review

Types
o Power consumption (as Attribute (W) and as a yearly Impact with Impact Type as
Primary Energy Consumption and Impact Stage is use (MJ))
o Jobs including start-up, shutdown and operation procedures
Components and Systems
o Test results and normal settings and readings from Commissioning

5.4 P04 Maintenance and repair

Information on the recommended maintenance tasks including planned preventative maintenance
is required to support the facility operators to anticipate and plan for costs of maintenance.
Types
o Jobs including inspection/diagnostics, PPM, repairs (frequency is duplicated with

Impact where the Impact Stage is maintenance)
o Spares
Note: labour cost rates are not required

5.5 P05 Replacement

Information on the reference or expected replacement service life and costs should be available to
the facility operators and to the owner to anticipate costs of maintenance.
Types
o All the additional columns from Nominal Length through to Code Compliance shall
be provided.
o Expected service life (or mean time to failure) shall be provide. (may also be used
within Job and within Impacts)
o Estimated replacement cost (may also be used within Impacts)
o Job replacement
o Impact replacement cycle
o The additional Type attributes that are documented in the UK COBie Type Templates
www.bimtaskgroup.org/COBie
o Additional attributes as found on the design drawings and those additional properties
found in the Example object templates
5.6 P06 Assessment and End of use and Repurposing

Information on factors and assessment is required to support the management of the end of use stage,
including facility capacity analysis for re-briefing and re-purposing.
Spaces
o Client requirements
o Physical limitations of spaces (maximum surface loadings, noise criteria, service

provision and capability)
Types
o Impacts (especially embedded carbon content)
o Recyclable percentage

5.7 P07 Impacts (costs and carbon)

Information is required to support the management of economic and environmental impacts of the facility
throughout the life cycle. Clause 5.7.1 defines the mandatory and optional expectations for Facility
Impacts.
Clauses 5.7.2 onwards offers methods for providing more detail. There are several methods available to
analyse and document discrete Impacts that make up the overall Impact of the Facility. The method
chosen affects how data can be aggregated up to facility and/or disaggregated downwards.
Note: Of the methods for documenting Impact listed below, it is expected that 5.7.2 will predominate
initially, as this is compatible with SFCA and comparable with other standard cost analyses.
Note: energy tariff and carbon trading rate information is not required
5.7.1 Mandatory: Association of Impacts to Facility
The following shall be provided:
Cost and Carbon impacts shall be associated to the Facility
Production and In-Use phases shall be documented separately.
This is equivalent to associating to the Facility:
Costs (capital) and CO2e (embedded) in production phase.
Costs and CO2e in use phase.
Figure 8: Four Facility Impacts
Optionally the following measures may be given
Energy in use phase (Optional)
Costs and CO2e in maintenance phase. (Optional)
Costs and CO2e in replacement phase. (Optional)
5.7.2 Association of Impacts to Systems
Impacts can then be aggregated up to the Facility

Figure 9: Functional analysis of Impacts by System

Example: Given a complete list of Systems within the Facility
Facility.Impact = Sum (System.Impact)

Figure 11: Summing of constituent Systems to assess the Facility
Sheet Name SheetName RowName Value Unit

Impact Production System Plumbing 1 800.00 Pounds
cost
Impact Production System External envelope 7000.00 Pounds

cost
etc
Impact Production Facility Standard Cell 97000.00 Pounds

cost
Figure 12: Example calculation

5.7.3 Association of Impacts to Floors (Sectors) or Spaces or Zones
Applicable to use phase
Not applicable for maintenance phase
Not applicable for replacement phase
Not applicable for production (capital & embedded) phase
Impacts can then be aggregated up to the Facility from the Floors (Sectors) or Zones or Spaces
Figure 10: A predicted quarterly reading of a Zone

5.7.4 Association of Impacts to Components
Impacts can then be aggregated up into Systems to the Facility
Impacts can then be aggregated up into Spaces, Zones, Floors (Sectors) to the Facility
Figure 13: Waste analysis for a specific Component

5.7.5 Association of Impacts to Types
An Impact of a Component is that Impact of the reference Type factored by the ratio of their
quantities. If an Impact such as the production cost of a Type is known, along with at least one
measured Quantity, then the actual Impact of a Component with matching measured Quantity can
be obtained.
Similar Quantities (by name, measurement type and preferably unit) must be associated to Types
and its Components. Whatever the measure(s) are used on the Type, at least one identical
measure must be used on each of its Components. Given matching measures, a ratio can be
calculated to use as a factor to apply to any Impacts associated to the Type. Otherwise the ratio
may be assumed to be "1 .00", or the Component omitted from the calculation
Where there are multiple quantities on the Component and Type, preference should be given to
mass, then volume then area, then length, then unity.
Where there are base, net and gross quantities on the Component and the Type, preference should
be given to gross measures when deriving impact measures.
Impacts can then be aggregated from the Types, through Components up into Systems and
Facility
Impacts can then be aggregated from the Types through Components up into Spaces, Zones and
Floors (Sectors) and Facility
Figure 14: Quantities associated to Type and Component(s)
Figure 15: Impacts associated to Type and Component(s)
Example: Considering the SVP component:
Component.Impact = Type.Impact * (Component.Quantity / Type.Quantity )

Figure 16: Scaling of Component Impacts from reference Types
Sheet Name SheetName RowName Value Unit

Impact Production Type Plumbing SVP 1 500.00 Pounds
cost
Attribute Length Type Plumbing SVP 1 1000 millimeters
Attribute Length Component Plumbing SVP 1:211824 2700 millimeters
Impact Production Component Plumbing SVP 1:211824 500.00 * (2700 / 1000)

cost
= 1350.00 Pounds
Figure 11: Example calculation

5.8 P08 Business questions

Information is required to support the on-going evaluation of the business case for ownership and
operation of the facility. This requires continuous development of the Impacts (P7) and of the beneficial
profile of the asset (P2) from the earliest Drop onwards
CIC Gateway 1: (drop 1) Initial and in-use, benefits and impacts
o Facility and Spaces
Capacity and benefit values should be associated to spaces and the aggregation
to the facility
With Name, Description and Classification
Briefing and design Documents
o Facility and Main fabric Types including Floor, Wall and Roof (Structure) and main
MEP Systems
with estimated areas (covered/served)
Production cost and CO2e Impact (targets)
Maintenance cost and CO2e Impact (targets)
CIC Gateway 3 (drop 2a) and CIC Gateway 4 (drop 2b).
o As CIC Gateway 1 ( drop 1) plus
o Types and Components
Main fabric items including Floor, Wall and Roof Types (Structure) with
Component areas
o Main MEP Systems
with Areas served
Use cost and CO2e Impact (targets)
CIC Gateway 5 (drop 3)
o As drop CIC gateway 4 (drop 2b) plus
o Served Zones for each system (not explicit in COBie)
o Facility / Zones / Spaces
Capacity and benefit values: Clients performance simulation results.
Impacts: cost and CO2e: Energy simulation results.
o Types
Quantities
o Systems / Components
Costs (capital) and Impacts (embedded)
Costs (in-use) and Impacts (in-use)
Estimated installation dates
o Allocation of Components to Systems
o Allocation of Spaces to Zones
CIC 6 : handover (drop 4)
o As drop CIC Gateway 5 (drop 3) plus
o Systems
Capacity
Control systems
o Types and Components
Quantities
o Data required for other Purposes (see P01, P03-P06 and P09-P10)
CIC 7 : (drop 5)
o As drop CIC 6 (drop 4) plus
o Information and corrections from post-occupancy assessment.
5.9 P09 Security and surveillance

Information is required and/or information may be supressed to support the management of the security
and surveillance of the facility. This may include a confidential schedule of objects (such as CCTV
cameras) or attributes (door key codes) to be omitted or concealed from any version of the Requirements
being held outside of the Employers security.

5.10 P10 Regulation and Compliance

Information is required to support the maintenance of the health and safety of the users of the facility
including H&S and CDM
o Issues
may be related to Facility, Floor (Sector), Space, Zone, Component, Type,

System
may be related to Attributes, Documents or Impacts
o Jobs
Safety procedures and cautions within those safety procedures shall be

documented

6 Criteria and metrics:

Parties shall provide management and quality oversight and review of the Requirement in terms of :
6.1 Compliance to the COBie/IFC schema

The deliverables shall be compliant to the COBie/IFC schema.
Note: The most significant rules are listed in the appendix.
Note: Validation can be conducted against the buildingSMART FM-10 handover MVD, the buildingsmart
alliance COBie schema, and published mappings.
6.2 Continuity
The deliverables shall be re-use the names defined in earlier drops for each Facility, Floor (Sector), Zone,
Space, Type, System and Component.
The External System identifiers shall also be maintained.
6.3 Completeness
The deliverables shall be complete as defined in 5.1 Registry and the selected Purposes (5.2-5.10) in the
Employers Information Requirement
6.4 Accuracy and enumerations and classification

For drops 1 and 2, a confidence range of numeric figures for areas and other physical measures of +/- 5%
and 2% shall be acceptable. Other predicted Impacts and performance shall support a confidence range of
numeric figures of +/- 20% and 10%
For drops 3 and 4, an accuracy range of numeric figures against actual of +/- 5% and 2% is expected.
Note: the CIC Plan of Works also refers to expected accuracy
6.5 Units
Units shall be provided separately for all numeric measures except length, area, volume and currency
where used consistently as declared for the Facility overall. Impact durations, warranty durations and Job
frequencies shall be expressed in Years. Job durations shall be expressed in hours.
6.6 Enumerations and Classifications

Enumerations (as specified in the Attributes and Picklists) shall be adhered to.
Classifications must be as provided from the defined Picklists
Sheet Column Classification Table

Facility Phase CIC table. RIBA or OGC otherwise
Facility Category Uniclass Table D (RICS BCIS Facility Classification)
Type Category Uniclass table L
Space Category Uniclass table D
System Category Uniclass Table G & H or SFCA / SF(CE)CA
Contact Category Uniclass Table C

6.7 Metrics
6.7.1 To aid the management process, the following counts and date ranges shall be displayed on the
Instruction sheet for each work sheet and for the COBie data set overall
Example Key
2012-01-01 Date of first change
2012-03-23 Date of last change
2309 Number of entries
Table 2: Metrics used to assess progress
6.7.2 To track progress, the following summaries shall be made.
Example Key
4567 Number of objects in total
9876 Number of addition information rows in total.
Table 3: Summary metrics
6.7.3 To aid the management assessment, the following ratios shall be measured
Expected Ratio Key
More than 10 ? Additional Information per Object
More than 20 ? Components per Type
More than 50 ? Components per System
More than 20 ? Spaces per Zone
More than 10 ? Spaces per Floor (Sector)
Table 4: Examples of ratios that can be used to assess completeness and quality
Note: Normal ranges for these ratios will be obtained from the analysis of existing COBie deliverables.
The expected ratios suggested here are provisional
Figure 12: Example of date and ratio metrics measured on a COBie dataset.

7 Required detail
7.0 Structure
7.0.1 Structure
COBie may be delivered in Spreadsheet XML 2003 format.
Note: This format is acceptable to Microsoft Excel and Open Office applications, so other formats
compatible with these may be anticipated, including XLS and OPS. Formats containing macros or other
embedded code may be rejected by firewalls and security scans.
All sheets, columns and header rows shall be present in the deliverable, named and ordered as in the
examples.
Note: Applications creating COBie data need not reproduce the colour coding of the COBie worksheets
found in the manual COBie template and example files. However when pasting into the COBie sheet, it is
preferable to use paste-special-text-only, to maintain the cells colouration, formatting and validation.
Additional sheets may occur in the deliverable after the final PickLists sheet.
Note: any additional sheets may not be read by receiving applications.
Additional columns may occur in the deliverable to the right of the final specified columns but should
have a header column name.
Note: such columns should be read by receiving applications, as if they were textual Attributes. They can
be used to simplify the generation of COBie information where the Attribute is applicable to the majority
of the objects on the sheet. For example, if all or most Spaces are expected to have a FloorFinish value,
then such a column can be added.
Blank rows should not be inserted between data rows or below the header row.
7.0.1 Naming
Names shall be unique within their sheet, except that the System, Zone and Attribute names must be
unique in conjunction with other columns.
Names shall use neither commas nor unusual punctuation or characters.
Contacts are named by use of their valid email address.
7.0.2 Columns
Mandatory (yellow) fields shall be provided.
Key (salmon) fields shall be provided with text exactly matching a value in the referenced column
System fields (purple) shall be provided if the row is not generated manually.
Requirable fields (green) shall be provided according to the Purposes selected in the Employers
Information Requirement.
7.0.3 Dates
Dates shall be presented in ISO style:

Example Sheet Column
2012-03-15T12:45:00 (all sheets) Created On
2012-03-15 Component Installation Date
2012-03-15 Component Warranty Start Date
2012-03-15 Job Start
Table 5: Date format
7.0.3 Classifications
Local Classifications shall not contain commas, but shall use a colon to separate any code from the
description. These may be lists. (see 6.5 above)

C3891 : Manufacturers Contact Category
D376 : Detention secure facilities prisons Facility Category
CIC 6 : Handover Facility Phase
D376 : Detention secure facilities prisons Space Category
L72104 : Washbasins Type Category
5A1 : Sanitaryware System Category
Table 6: Local classification
7.0.4 Lists
Lists (including local classification see 7.0.3) shall be comma delimited.

L0-01A, L0-01B Zone Space Names*
WC Pan 211807,Wallgate ALS180 Basin 211808 System Component Names**
1. Spray the CWC with a bathroom type cleaner, 2. Job Description (sub tasks)
Lime scale can be removed using proprietary products
and abrasives, 3. Stains and surface marks may be
removed with the use of a scouring pad ( grade Green
fine) used wet with a liquid cleaning agent if
necessary.
Wallgate ALS180 Basin DL7523, CandG P101 Job Resource Names
Certificate
1,,10 Attribute Value (ranges and tables)
Table 7: Comma separated lists
* On the Zone sheet Space lists can be avoided by repeating the row for each member Space.
**On the System sheet Component lists can be avoided by repeating the row for each member
Component.
7.0.5 Numeric Values and units
The units of measure for length, area, volume and currency shall be defined on the Facility sheet.

millimeters Facility Linear Units
squaremeters Facility Area Units
cubicmeters Facility Volume Units
Pounds Facility Currency Unit
Table 8: Common units of measure
Numeric values shall be provided without units appended. Unknown values may be entered as 0.

millimeters Floor (Sector) Elevation

millimeters Floor (Sector) Height

millimeters Space Useable Height
squaremeters Space Gross Area
squaremeters Space Net Area
millimeters Type Nominal Length, Nominal Width, Nominal Height
Pounds Type Replacement Cost
millimeters Coordinate Coordinate X Axis, Coordinate Y Axis, Coordinate Z Axis
Table 9: Use of common units of measure
The units of measure on the Attribute and Impacts sheets shall be provided in the separate column,
selected from the Picklists provided.
Example Sheet Value Column Unit Column

W Attribute Value Unit
kg Impact Value Impact Unit
Table 10: Use of units from Picklists.
The units of measure for Durations and Frequencies on the Type and Job sheets, shall be provided in the
separate column, selected from the Picklists provided. The unit of measure for Impact timings shall be
Years.
Example Sheet Value Column Unit Column

Year Type Expected Life Duration Unit
hour Job Duration Duration Unit
Year Job Frequency Frequency Unit
Year Impact LeadInTime (fixed)
Year Impact Duration (fixed)
Year Impact LeadOutTime (fixed)
Table 11: Time units
Note: The Job Frequency is a duration measured between Job starts. The Impact timings define a
repeating cycle, starting at the time of handover. Initial impacts such as capital costs and embedded
carbon should have zeros entered for all three timings LeadInTime, Duration and LeadOutTime.
7.1 Instruction sheet

Note: The Instruction worksheet provides general information about the COBIE file including the version
and release number. Any regional requirements for COBIE files may also be identified through the
Region field.
7.1.1 Title, Version, Release, Status and Region shall be provided. This information should not change.
7.1.2 The metrics specified in section 6 shall be provided. These will develop with the COBie dataset.
Figure 13: Instruction sheet (release should be 4, not 40)

7.2 Contact sheet

Note: Regardless of when you submit a COBIE file the information about the people who created the data
in the file and the companies that support the project, such as warranty contractors and parts suppliers,
will need to be documented as that information becomes available. Early on the only information in the
Contact table will be the designated person responsible for providing the COBIE data from the designers
(or design-builders) office. As the project progresses and more project partners contribute to COBIE or
when companies that need to be listed for use by facility managers, are found, these will be added to the
Contact worksheet.
Sheet Contents
People and Companies: actors and their roles including designers,
consultants, contractors, sub-contractors and suppliers, warrantors and
Contact maintainers.
Figure 14: The information sheet summarises the sheet names and content, starting with
Contact

nn@aec3.com Contact Email
nn@aec3.com (all sheets) Created By
sales@aec3.com Type Manufacturer
support@aec3.com Type Warranty Guarantor Parts
warranty@aec3.com Type Warranty Guarantor Labor
nn@aec3.com Issue Owner
spares@aec3.com Spare Suppliers
Table 12: Use of Contacts.

7.3 Object sheets
Figure 15: COBie focuses on 7 principal objects (with 3 additional objects to support
maintenance activities).
Sheet Contents
Facility Facility includes the Project, Site and Building/Structure
Floor Floors (Sectors) are the mandatory spatial structure.
Spaces are the spatial locations where inspection, maintenance and operation Jobs
Space occur.
Zone Zones are additional functional groupings of specs.
Types are the mandatory grouping of Components as types or products, used to
Type organise maintenance tasks
Component Components are the physical assets.
System Systems are additional functional groupings of Components
Spares are the physical objects and Jobs are the processes used to maintain and
Spare operate the assets.
Job Jobs are the processes used to maintain and operate the assets.
Resources Support the processes.
Table 13: COBie objects
For infrastructure and civil projects, the Floor sheet can be read as Sector and no elevation or height
information shall be given, but a Coordinate offset shall be provided instead. Components shall be
assigned to the Space (or Spaces) that would be visited to inspect or maintain it, even if they are adjacent
to or outside of the Space.
Note: Equipment Components are typically associated to a single Space. Doors and interior window
Components may require the identification of both Spaces that are connected. Large asset Components
may be inspected and maintained from several Spaces. Some HVAC equipment may be inspected from a
hatchway in a remote Space. However, some receiving systems may read only the first space.

7.4 Additional information sheets

There is also a variety of additional information that may be associated to the previous Object worksheets.
.
Sheet Contents
Additional attributes with name, description, value and units. Property sets of
referenced item. The Attribute worksheet may contain additional information
relating to specific types of object. The Attribute worksheet is required to be used to
capture the distinct. In general intended and provisional data should be replaced with
Attribute actual and as built information.
Associated documents including briefing, product data and other required submittals.
All applicable document references. The Document worksheet may contain indexing
information to file based information relating to any phase of the project. The
Document worksheet used to capture the expected product submittals, to link the
actual approved contract submittals, and to link to any appropriate commissioning
Document documentation.
Economic and environmental impacts for objects at specific life cycle stages
Impact optionally with a flexible repeating pattern
Connection Logical connections between Components
Spatial locations in box, line, or point format. Floors (Sectors), Spaces and
Components can be located, and Spaces given a box size. (Types should be sized
Coordinate through their Nominal Length, Nominal Width and Nominal Depth.)
Types or Components can be aggregated, so that configurations can be managed
Assembly collectively.
Issue Issues and Risks can be recorded and associated to one or two Objects or Documents
Figure 16: Additional information shall be provided as required by the Employers
Purposes.
Where consistent, additional information such as Attribute, Document, Impact and Issue, should be
associated to the Type or System in preference to the Component and associated to the Floor (Sector) or
Zone in preference to the Space.
Example: if all the values on an Attribute of Components sharing the same Type are identical, a single
Attribute should instead be associated to the Type.
Attributes not supporting the clients Purposes shall be omitted.
Example: Attributes relating purely to the graphic appearance or behaviour are not required.
7.5 Specification of objects and additional information sets

The Examples and Templates illustrate the fixed requirements of the COBie/ IFC handover schema and
cover the requirements for specific additional information relating to objects types. See the Annexes.
Type templates can be reviewed and downloaded from:

8 Bibliography
8.1 Definitive material
COBie is freely available. The COBie standard is published

(http://www.buildingsmartalliance.org/index.php/projects/activeprojects/25) and is defined as the FM
Handover MVD (http://www.buildingsmartalliance.org/docs/BSADOC_COBIE/index.htm) which
contains the terms of the COBie license. The COBie spreadsheet is a mapping of the FM Handover MVD
as documented in the COBie responsibility matrix
( http://projects.buildingsmartalliance.org/files/?artifact_id=4093 ).
COBie: http://www.wbdg.org/resources/COBie.php
buildingSMART FM Design Handover view: www.buildingsmart.org buildingSMART Alliance
Handover view: http://www.nibs.org/docs/BSADOC_COBIE/index.htm
(includes Interoperability specification)
The use of Excel or any particular proprietary format or software is not part of the COBie standard. The
published XLS template is available in Spreadsheet XML 2003 and OpenOffice standard formats if
requested.
8.2 UK material
An empty COBie 2.4 sheet is defined in
COBIE-UK-2012.xls
Examples are available in
COBie-UK-2012-example1-drop1.xls and .ifc

COBie-UK-2012-example1-drop2a.xls and .ifc
COBie-UK-2012-example1-drop2b.xls and .ifc
Templates for specific objects are found in
[type-subtype]_UK.xls and .ifc
Note: An example is SanitaryTerminal_WASHHANDBASIN_UK.xls or

SanitaryTerminal_WASHHANDBASIN_UK.ifc
8.3 US material
Overview: http://buildingsmartalliance.org/index.php/projects/commonbimfiles/
8.3.1 Production of BPie deliverable at Design, Programming stage (not in current scope)
Similar to http://projects.buildingsmartalliance.org/files/?artifact_id=4444
With additional properties as specified by:
http://iug.buildingsmart.com/idms/information-delivery-manuals/idm-for-building-programming

8.3.2 Production of COBie deliverable at Design, Construction Documents stage.

http://projects.buildingsmartalliance.org/files/?artifact_id=4445
8.3.3 Production of COBie deliverable at Construction, Product Selection stage.

8.3.4 Production of COBie deliverable at Construction, Handover stage.

8.4 Tools
Note: Tools may support the preparation of COBie datasets directly or through the IFC format which is
supported by most BIM authoring tools.
www.aec3.com BimServices: Command line utilities for mapping between IFC and COBie and making
quality assessments, merging, reporting and comparing. The toolkit includes extended interoperability
specifications that are editable.
BiMServer Custom build with COBie plugins: This download provides a custom build of TNO's BiMServer
with COBie export and import features. Export formats include COBie (spreadsheet XML) and various
HTML reports such as room data sheet and spatial decomposition. A COBie compliance report is also
provided as an export but is subject to pre-validation changes that may be necessary to fit a model into a
valid COBie file. Model merging capability. (includes interoperability specification in the open source
code)
COBie Satellite Server Application: This download provides a standalone client and BiMServer Satellite
application that may be used with or without BiMServer. The primary purpose of this application is to
provide compliance and comparison report exports for COBie (spreadsheet XML) files. In addition to
these file utilities, the application may connect to a running instance of BiMServer and export a COBie
comparison report of two project models.
www.autodesk.com Revit COBie toolkit through usual Autodesk support channels. .
Note: Supporting tools for preparation and consumption are currently documented at
www.buildingsmartalliance.org

Annex A: Recommended Attributes
A.1 Facility
Description
Example
Example
Name
Value
Unit
BuildingID 1234 n/a Auniqueidentifierassignedtoa
567801 building.Atemporaryidentifieris
123445 initiallyassignedatthetimeof
makingaplanningapplication.This
temporaryidentifierischangedtoa
permanentidentifierwhenthe
buildingisregisteredintoastatutory
buildingsandpropertiesdatabase.
GrossArea 20.00 squaremeters Sumofallgrossareasofspaces
withinthebuilding.Itincludesthe
areaofconstructionelementswithin
thebuilding.Maybeprovidedin
additiontothequantitiesofthe
spacesandtheconstruction
elementsassigendtothebuilding.In
caseofinconsistencies,the
individualquantitiesofspacesand
constructionelementstake
precedence.
GrossVolume 55.00 cubicmeters Sumofallgrossvolumesofspaces
enclosedbythebuilding.Itincludes
thevolumesofconstruction
elementswithinthebuilding.May
beprovidedinadditiontothe
quantitiesofthespacesandthe
constructionelementsassigendto
thebuilding.Incaseof
inconsistencies,theindividual
quantitiesofspacesand
constructionelementstake
precedence.
IsLandmarked false logical Thisbuildingislistedasahistoric
building(TRUE),ornot(FALSE),or
unknown.
IsPermanentID true logical Indicateswhethertheidentity
assignedtoabuildingispermanent
(=TRUE)ortemporary(=FALSE).
LandTitle ESX257525 Thelandtitlenumber(designation
Number ofthesitewithinaregionalsystem).
NetArea 18.50 squaremeters Sumofallnetareasofspaceswithin
thebuilding.Itexcludestheareaof

constructionelementswithinthe
building.Maybeprovidedin
additiontothequantitiesofthe
spacesassigendtothebuilding.In
caseofinconsistencies,the
individualquantitiesofspacestake
precedence.
NetVolume 46.25 cubicmeters Sumofallnetvolumesofspaces
enclosedbythebuilding.Itexcludes
thevolumesofconstruction
elementswithinthebuilding.May
beprovidedinadditiontothe
quantitiesofthespacesassignedto
thebuilding.Incaseof
inconsistencies,theindividual
quantitiesofspacestake
precedence.
NumberOf 1 number Thenumberofstoreyswithina
Storeys building.
OccupancyType prison n/a Occupancytypeforthisobject.Itis
definedaccordingtothepresiding
nationalbuildingcode.
RefElevation 50000.0 millimeters RefElevation
RefLatitude 51,30,0 n/a WorldLatitudeatreferencepoint
(mostlikelydefinedinlegal
description).Definedasinteger
valuesfordegrees,minutes,
seconds,and,optionally,millionths
ofsecondswithrespecttotheworld
geodeticsystemWGS84.
RefLongitude 0,7,34 n/a WorldLongitudeatreferencepoint
(mostlikelydefinedinlegal
description).Definedasinteger
valuesfordegrees,minutes,
seconds,and,optionally,millionths
ofsecondswithrespecttotheworld
geodeticsystemWGS84.
TrueNorth 0.0,1.0 Vectorindicatingtheorientationof
themodelagainstgeographicnorth.
UPRN 44010823 n/a TheUPRNisthepersistentkey
identifierprovidingconsistency
acrosstheAddressBaseproduct
range.Allhistoric,alternativeand
provisionaladdressesforaBasic
LandandPropertyUnit(BLPU)are
recordedagainstthesameUPRN.
TOID osgb1000001 n/a TheTOIDisauniquefeature
134770 identifierforthebuildingandcomes
fromtheOSMasterMapTopography
Layer.TheTOIDisa16character
numberthatisprefixedwithosgb
andwillstaythesamethroughout
thelifeofafeature.

Table 14: Recommended additional Facility Attributes

Recommended Facility Attributes are scheduled in specific Templates which can be obtained from
www.buildingsmart.org , www.buildingsmart.org.uk.
A.2 Space and Zone
Description
Name
Value
Unit
Benefit 1 client Beneficialmeasure
CeilingCovering none n/a Labeltoindicatethe
materialorfinishofthe
spaceceiling.Thelabelis
usedforroombook
informationandoften
displayedinroomstamp.
Concealed false boolean Concealed
FinishCeilingHeight 2500.0 millimeters Heightofthesuspended
ceiling(fromtopofflooring
tothebottomofthe
suspendedceiling).Tobe
providedonlyifthespace
hasasuspendedceilingwith
constantheight.
FinishFloorHeight 0 millimeters Heightoftheflooring(from
baseslabwithoutflooringto
theflooringheight).Tobe
hasaconstantflooring
height.
FloorCovering none n/a Labeltoindicatethe
spaceflooring.Thelabelis
usedforroombook
informationandoften
GrossCeilingArea squaremeters Sumofallceilingareasofthe
space.Itincludesthearea
coveredbyelementsinside
thespace(columns,inner
walls,etc.).Theceilingarea
isthereal(andnotthe
projected)area(e.g.incase
ofslopedceilings).
GrossPerimeter 11546.8 millimeters Grossperimeteratthefloor
levelofthisspace.Itallsides
ofthespace,includingthose
partsoftheperimeterthat
arecreatedbyvirtual
boundariesandopenings
(likedoors).
GrossVolume cubicmeters Grossvolumeenclosedby
thespace,includingthe
volumeofconstruction
elementsinsidethespace.
GrossWallArea squaremeters Sumofallwall(andother
verticallybounding
elements,likecolumns)
areasboundedbythespace.
Itincludestheareacovered
byelementsinsidethewall
area(doors,windows,other
openings,etc.).
Height 2500.0 millimeters Totalheight(frombaseslab
withoutflooringtoceiling
withoutsuspendedceiling)
forthisspace(measured
fromtopofslabbelowto
bottomofslababove).Tobe
hasaconstantheight.
InteriorOrExteriorSpace internal n/a InteriorOrExteriorSpace
NetCeilingArea squaremeters Sumofallceilingareasofthe
space.Itexcludesthearea
coveredbyelementsinside
thespace(columns,inner
walls,etc.).Theceilingarea
isthereal(andnotthe
projected)area(e.g.incase
ofslopedceilings).
NetPerimeter 11546.8 millimeters Netperimeteratthefloor
levelofthisspace.It
excludesthosepartsofthe
perimeterthatarecreated
byvirtualboundariesand
openings(likedoors).Itis
themeasurementusedfor
skirtingboardsandmay
includetheperimeterof
internalfixedobjectslike
columns.
NetVolume cubicmeters Netvolumeenclosedbythe
space,excludingthevolume
ofconstructionelements
insidethespace.
NetWallArea squaremeters Sumofallwall(andother
verticallybounding
elements,likecolumns)
areasboundedbythespace.
Itexcludestheareacovered
byelementsinsidethewall
area(doors,windows,other
openings,etc.).
OccupancyNumber 1 each Numberofpeoplerequired
fortheactivityassignedto
thisspace.
OccupancyType custody n/a Occupancytypeforthis
object.Itisdefined
accordingtothepresiding
nationalbuildingcode.
Perimeter 11546.8 millimeters Perimeter
Utilisation 95.50 percent PlannedAvailability
WallCovering none n/a Labeltoindicatethe
spacewalling.Thelabelis
usedforroombook
informationandoften
Table 15: Recommended additional Space and Zone Attributes
Recommended Space and Zone Attributes are scheduled in specific Templates can be obtained from
A.3 Component
Name Value Unit Description

Area 5.74 squaremeters Area
IsExternal false boolean IsExternal
Length 4627.5 millimeters Length
Mark DD1120 n/a Mark
MountingHeight 1200.0 millimeters MountingHeight
Structural false boolean Structural
Tag DD1120 n/a Tag
Volume 0.86 cubicmeters Volume
Table 16: Recommended Component Attributes
Recommended Component Attributes are restricted to any distinct quantities or positional information, as
most attributing should be done onto the Components Type or System(s) .
Recommended Component Attributes are scheduled in specific Templates can be obtained from
A.4 Type and System
Recommended Type and System Attributes, beyond those on the Type and System sheets, should be
appropriate to the Type and System, and are scheduled in specific Templates which can be obtained from
www.buildingsmart.org , www.buildingsmart.org.uk. www.bimtaskgroup.org/cobie
Name Description
(various) SeetemplatespublishedbybuildingSMARTand
buildingSMARTUKandtheUKBIMTaskgroupwebsite
Table 17: recommended Type and System Attributes

Annex B: COBie checklist

This checklist combines COBie standard and UK implementation rules.
Uniqueness of information
o Every Attribute Name (column A), taken with Sheet-Name (column E) and Row-
Name (column F) must be unique
o Every System Name (column A) taken with Component-Names (column E)
must be unique
o Every Zone Name (column A) taken with Space-Names (column E) must be
unique
o Elsewhere every Name and Email (column A) must be unique.
Clarity of Naming
o Names must not use commas. Emails must be valid.
o Names should not use punctuation nor unusual characters (for example & % )
o Classifications should use the colon to separate code from description and not
use comma
Integrity of References
o Every reference to other sheets must be valid
o Every reference to enumerations and classifications must be valid
Consistency of Units
o Length, Area and Volume and Currency values must be consistent with the
Facility unit declarations.
o Units must be provided separately from the value for all other numeric
Attributes.
Completeness of the Data

o Every Component shall be assigned to at least one Space
o Every Component shall be assigned to one Type
o Every Component shall be assigned to at least one System
o Every Space shall be assigned to at least one Zone
o There shall be multiple Zones.
o There shall be multiple Systems.
o All required (yellow) and reference (salmon) fields including classification must
be provided.
o Attributes for the Facility, Spaces and Zones must be provided as Annex A
above
o Attributes for the Types must be provided as required in the Type Templates
(www.bimtaskgroup.org/COBie)
Accuracy
o Zero, unset or undefined Values should not be documented in Attributes
o Graphical and stylistic information should not be documented in Attributes
o Attributes should not duplicate information found elsewhere.
o Common Attributes (excluding identification, quantities and location) should be
assigned to
the Type or System, not the Component
the Floor or Zone, not the Space
o Common Documents (excluding condition reports, photographs and
commissioning reports) should be assigned to
the Type or System not the Component
the Floor or Zone not the Space
Continuity
o Use the same names as previous COBie deliverables
o Maintain any External System identifiers (Global Ids or GUIDS)

Concluded

Commentsandcorrectionsarewelcome.
NicholasNisbetMA(Cantab)DipArch(UNL)
Direct:+44(0)1494714933
Skype:nicholasnisbet
TechnicalCoordinator:buildingSMARTUKChapter
Web:http://www.buildingsmart.org.uk/
Email:nn@buildingSMART.org.uk

COBie UK 2012 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

COBie UK 2012 PDF

Uploaded by

Copyright:

Available Formats

COBie-UK-2012

2012 AEC3 UK Ltd 2 July 2012

Date Version Author

2012 AEC3 UK Ltd 3 July 2012

8.2 UK material ....................................................................................................................................... 43

2012 AEC3 UK Ltd 5 July 2012

0.1 The Owners View

0.2 The Designers and Contractors View

0.3 Product Specifiers and Suppliers

2012 AEC3 UK Ltd 6 July 2012

2012 AEC3 UK Ltd 7 July 2012

1.5 IFC and COBie

2012 AEC3 UK Ltd 8 July 2012

Figure 2: COBie allows a continuously expanding data set to be complete at

1.8 COBie for infrastructure and building

1.9 COBie for existing facilities and refurbishment

1.10 Use of COBie information

1.11 COBie Contacts

1.11 COBie Objects

2012 AEC3 UK Ltd 9 July 2012

2012 AEC3 UK Ltd 10 July 2012

1.12 COBie additional information

2012 AEC3 UK Ltd 11 July 2012

2012 AEC3 UK Ltd 12 July 2012

3.2 Manageable assets

3.4 Gates / Stages

2012 AEC3 UK Ltd 13 July 2012

3.6 Employers Information Requirements

(a) Which Gates require a data deliverable (Drops)

This document uses the following drops

CIC 1: Drop 1: brief / early design

CIC 3: Drop 2a: design development issued for tender

CIC 4: Drop 2b: tender submission

CIC 5: Drop 3: contractors design development and planning

CIC 6: Drop 4: handover

(d) Any additional checks and metrics by extension to section 6.

2012 AEC3 UK Ltd 14 July 2012

4.1.1 CIC 1: Brief - ending with Drop 1

4.1.2 CIC 2: Concept

4.1.3 CIC 3: Design Development ending with Drop 2a

4.1.4 CIC 4: Production Information ending with tender and drop 2b

4.1.5 CIC 5: Constructed Information ending with drop 3

4.1.6 CIC 6: Handover - with drop 4

4.1.6.1 CIC 6A : Post fit-out Handover

4.1.7 CIC 7 : Post Practical Completion

2012 AEC3 UK Ltd 15 July 2012

Figure 5: Swimlanes showing CIC Stages 1- 7 and Gates G1-G7.

2012 AEC3 UK Ltd 16 July 2012

Figure 6: Drops are planned to support client decision processes.

2012 AEC3 UK Ltd 17 July 2012

4.2 Lower tiers in the design chain and supply chain.

Figure 7: Generic process map for delegation of Requirements.(image courtesy of AEC3

4.3 Strategic, Managerial and Implementation obligations

2012 AEC3 UK Ltd 18 July 2012

2012 AEC3 UK Ltd 19 July 2012

5 Clients strategic Purposes:

Purpose Detail BSI Pas 55 references

2012 AEC3 UK Ltd 20 July 2012

5.1 P01: Registry

5.1.1 Facility, Floor (Sector) and Zones , Spaces

o Every distinct Floor (sector) and outside space and site

o Every manageable/accessible space.

spaces identified in design drawings and/or related schedules.