COBie-UK-2012.pdf

COBie-UK-2012          

V11 Nicholas Nisbet th

10 July 2012

UK COBie 2.4 Requirements

© 2012 AEC3 UK Ltd

2

July 2012


© 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 from USACE ERDC and AEC3 unless unless otherwise stated.

Date

Version

Author

2012-02-17

V08

First issue for consultation

[email protected]

2012-02-21

V09

Improved formatting.

[email protected]

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 requirements .

[email protected]

Recommended additional Attributes appended 2012-06-10

V11

COBie drop examples included

[email protected]

COBie Type templates referenced

© 2012 AEC3 UK Ltd

3

July 2012


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 1.5 IFC and and COBie COBie ..................................................................................................................................... ..................................................................................................................................... 8 1.6 Background ................................................................................................... ...................................... 8 1.7 Process 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............................................................. Gates............................................................. ................................................................ ............... 17 4.2 Lower tiers in the design chain and supply chain. ....................................................................... 18 4.3 Strategic, Managerial and Managerial and Implementation Implementation obligations ................................................................. 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.................................................................. 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

© 2012 AEC3 UK Ltd

4

July 2012

UK COBie 2.4 Requirements 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

© 2012 AEC3 UK Ltd

5

July 2012


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 i nto product types and into other systems. Usually the information needed to complete the COBie deliverable will be available already, either in yo ur 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. T he RIBAE NBL initiative will be contributing suggested UK specific properties.

1 Scope 

Required shared structured …



… Information including objects, properties and relationships …



… for a Facility including building and infrastructure …



… Operation including (design and construction) stages prior to handover and (use) stages subsequent to handover.

This Part defines expectations for the Required shared structured Information relating to spatial and

© 2012 AEC3 UK Ltd

6

July 2012

UK COBie 2.4 Requirements 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 “enGB” 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.

© 2012 AEC3 UK Ltd

7

July 2012


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 client’s 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

© 2012 AEC3 UK Ltd

8

July 2012


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 b e 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.

© 2012 AEC3 UK Ltd

9

July 2012


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

© 2012 AEC3 UK Ltd

10

July 2012


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)

© 2012 AEC3 UK Ltd

11

July 2012


2 Referenced Standards o

UK BS1192:2007 : Collaborative production of architectural, engineering and construction information.

o

UK PAS 1192 part 2: Required Information for Facility Procurement

o

UK PAS 1192 part 3: Required Information for Facility Operation (forthcoming)

o

ISO 16739:2005: Industry Foundation Classes (IFC2x) Platform Specification

o

ISO 16739: 2012: Industry Foundation Classes (IFC4) Specification

o

ISO 29481 Information Delivery Manual

o

ISO 12006 part 2 (UK: CIC CPIC Uniclass) and part 3 (IFD)

o

UK CIC Unified “Plan of Work” process map (WP104, undergoing review and comment)

o

COBie documentation (www.buildingsmartalliance.org)

o

BSI PAS 55:2008 Asset management

See also the definitive material listed in 8.1

© 2012 AEC3 UK Ltd

12

July 2012


3 Definitions 3.1 Requirements Requirements are the documented expectations of facility owners/commissioners for sharable structured information. These are also referred to as the Employers Information Requirements (EIR) (qv) (alternatively the Clients Information Requirements). NOTE: Detailed requirements are scheduled in the Examples

3.2 Manageable assets Those aspects of the facility that may be managed during the facility life‐cycle include both physical and spatial objects, and their functional groupings. NOTE: An asset is a uniquely identifiable element which has a financial value and against which maintenance actions are recorded. NOTE: Some aspects, such as the structural frame, or individual pipe and duct segments, fixings and secondary elements may be excluded from scope by the employer.

3.3 Purposes Those aspects of the Facility that are intended to be managed by the facility owner. NOTE: Some Purposes, such as supporting the business case, may be common with the briefing and design processes.

3.4 Gates / Stages A standardised process map for the acquisition of a facility may be divided into stages and gateways at some of which the Requirements shall be delivered. NOTE: The stages at which Drops are required should be specified in the EIR by reference to the agreed Stage and Gate names. See the CIC “Plan of Work”

3.5 Metrics The acceptability of the deliverable may be assessed against the Requirements shown in the Examples and/or against indicative ratios and counts based on the information provided.

© 2012 AEC3 UK Ltd

13

July 2012


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.

© 2012 AEC3 UK Ltd

14

July 2012


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 p riorities 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. Confidence 90 to 95%, margin ± 5 to 10% 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. Confidence 95 to 98%, margin ± 2 to 5% 4.1.6 CIC 6: Handover - with drop 4 As constructed systems, operation and maintenance, updated p redicted 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)).

© 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


4.1Gates Gates G1 to G7 occur at the end of the associated stage CIC 1‐ CIC 7. COBie drops shall be made at Gates G1, G2, G3 and G6 NOTE the Employers Information Requirements may add additional delivery gates.

The client‐appointed first tier party shall deliver the Requirements to the Client at least at the specified gates including G3 Design completion or G6 Handover. NOTE first tier party will typically be lead designer or contractor.

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.

Parties may ensure that lower tier parties be similarly obligated to deliver specified aspects of the Requirements in preparation for these Gates. NOTE A lower tier party could be a specialist designer or sub‐contractor or product supplier. NOTE Figure 6 shows a typical delegation process.

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

4.3 Strategic, Managerial and Implementation obligations A party shall fulfil its strategic, managerial and detailed obligations for the delivery of the EIR 4.3.1 Strategic: (a) Receive and accept Requirement (EIR) (b) Propagation of Requirement (EIR) downwards to next tier (c) Review and approval prior to submission © 2012 AEC3 UK Ltd

18

July 2012


4.3.2 Management and Quality Assurance (a) Review of received information (b) Receipt and merge / integration of delegated submissions (c) Review of prepared information for continuity, completeness and accuracy 4.3.3 Implementation (a) Entry of expected information a. Use of spread‐sheet or database applications i. Use of copy‐and‐paste (use paste‐special: text only) ii. Use of filter/sort iii. Use of text based formulae b. Use of BIM authoring tools i. Use of the Project Information commands ii. Use of the vendors specific commands and toolkits iii. Use of export to IFC and mapping to COBie c.

Use of NBS Create, Codebook i. Use of the export to COBie command

Note: For example Autodesk Revit can be augmented with COBie toolkits. NOTE: Application vendors may provide specific guidance on the managerial and implementation of the COBie requirements

© 2012 AEC3 UK Ltd

19

July 2012


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: The primary driver for the early drops is to manage the P08 business case based on P02 Use and P07 Impacts.

Purpose

Detail

BSI Pas 55 references

P01

Registration

Registration of the assets is a prerequisite for the following purposes.

4.5.1a, 4.4.6, 4.6.6, 4.5.1.3

P02

Use and utilisation

Includes data for any soft-landings usage review

4.5.1b, 4.5.1 i, 4.5.1.4

P03

Operations

Includes data for any soft-landings operational review

4.5.1 i, 4.5.1.2, 4.6.1

P04

Maintenance and repair

Includes the tasks and required resources and spares.

4.5.1c, 4.5.1.2, 4.5.1.5, 4.5.2

P05

Replacement

Includes information relating to the specification and selection of Types.

4.5.1.7

P06

Assessment and reuse

Including end-of-use, re-purposing and facility capacity analysis

4.5.1d, 4.5.1.6

P07

Impacts

Economic and environmental (but not social) impacts

4.5.1 iii

P08

Business case

Continuously review is the primary driver for the intermediate ‘Drops’.

4.5.1

P09

Security and surveillance

Aspects of the model may be specifically excluded from shared data.

4.4.7

P10

Regulation and Compliance

Information relating to the H&S and CDM and safety of operations in the facility

4.5.1 iii, 4.6.2, 4.4.8

Table 1: Summary of Employers Purposes and references to BSI PAS 55 part 1 & 2.

© 2012 AEC3 UK Ltd

20

July 2012


5.1 P01: Regist ry 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. 

o

“spaces identified in design drawings and/or related schedules”.

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.

© 2012 AEC3 UK Ltd

21

July 2012


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.

© 2012 AEC3 UK Ltd

22

July 2012


5.2 P02: Use and u tilis ation . 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 

© 2012 AEC3 UK Ltd

Utilisation as a percentage where 24/7 = 100%

23

July 2012


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

© 2012 AEC3 UK Ltd

24

July 2012


5.4 P04 Maint enance and repair Information on the recommended maintenance tasks including planned preventative maintenance is required to support the facility op erators 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

© 2012 AEC3 UK Ltd

25

July 2012


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 

o

www.bimtaskgroup.org/COBie

“Additional

attributes as found on the design drawings and those additional properties found in the Example object templates “

5.6 P06 Ass essment and End o f u se and Repur pos ing Information on factors and assessment is required to support the management of the end of u se stage, including facility capacity analysis for re-briefing and re-purposing. Spaces 

o

o



Client requirements Physical limitations of spaces (maximum surface loadings, noise criteria, service provision and capability)

Types o

Impacts (especially embedded carbon content)

o

Recyclable percentage

© 2012 AEC3 UK Ltd

26

July 2012


5.7 P07 Impacts (cos ts and carbo n) 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

© 2012 AEC3 UK Ltd

27

July 2012


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

Impact

Production cost

System

Plumbing 1

Impact

Production cost

System

External envelope

Unit

800.00

Pounds

7000.00

Pounds

97000.00

Pounds

etc

Impact

Production cost

Facility

Standard Cell

Figure 12: Example calculation

© 2012 AEC3 UK Ltd

28

July 2012


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

© 2012 AEC3 UK Ltd

29

July 2012


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

© 2012 AEC3 UK Ltd

30

July 2012


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 cost

Type

Plumbing SVP 1

500.00

Attribute

Length

Type

Plumbing SVP 1

1000

millimeters

Attribute

Length

Component

Plumbing SVP 1:211824

2700

millimeters

Impact

Production cost

Component

Plumbing SVP 1:211824

Pounds

500.00 * (2700 / 1000) = 1350.00

Pounds

Figure 11: Example calculation © 2012 AEC3 UK Ltd

31

July 2012


5.8

P08 Bus iness questi ons

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 

o





With Name, Description and Classification



Briefing and design Documents

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 

o



Capacity and benefit values should be associated to spaces and the aggregation to the facility

Main fabric items including Floor, Wall and Roof Types (Structure) with Component areas

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

o



Capacity and benefit values: Clients performance simulation results.



Impacts: cost and CO2e: Energy simulation results.

Types 

© 2012 AEC3 UK Ltd

Quantities

32

July 2012

UK COBie 2.4 Requirements 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

o



Capacity



Control systems

Types and Components 

o



5.9

Quantities

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.

P09 Security and sur veill ance

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.

© 2012 AEC3 UK Ltd

33

July 2012


5.10 P10 Regulatio n 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 



o

may be related to Facility, Floor (Sector), Space, Zone, Component, Type, System may be related to Attributes, Documents or Impacts

Jobs 

© 2012 AEC3 UK Ltd

Safety procedures and cautions within those safety procedures shall be documented

34

July 2012


6 Criteria and metrics: Parties shall provide management and quality oversight and review of the Requirement in terms of :

6.1 Comp lianc e to t he 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 Cont inui ty 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 Comp leteness 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 Accu racy and enumeration s and classifi cation 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 Enumeration s and Classi fic ations Enumerations (as specified in the Attributes and Picklists) shall be adhered to. Classifications must be as provided from the defined Picklists Sheet Facility

Column Phase

Classification Table CIC table. RIBA or OGC otherwise

Facility Type Space System Contact

Category Category Category Category Category

Uniclass Table D (RICS BCIS Facility Classification) Uniclass table L Uniclass table D Uniclass Table G & H or SFCA / SF(CE)CA Uniclass Table C

© 2012 AEC3 UK Ltd

35

July 2012


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 2012-01-01 2012-03-23

2309

Key Date of first change Date of last change 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.

© 2012 AEC3 UK Ltd

36

July 2012


7 Required detail 7.0 Struc tur e 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 th e 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 ‘F loorFinish’ 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 2012-03-15T12:45:00 (all sheets) Component 2012-03-15 Component 2012-03-15 Job 2012-03-15

Column Created On Installation Date Warranty Start Date Start

Table 5: Date format © 2012 AEC3 UK Ltd

37

July 2012


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)

Example C3891 : Manufacturers D376 : Detention secure facilities prisons CIC 6 : Handover D376 : Detention secure facilities prisons L72104 : Washbasins 5A1 : Sanitaryware

Sheet Contact Facility Facility Space Type System

Column Category Category Phase Category Category Category

Table 6: Local classification

7.0.4 Lists Lists (including local classification see 7.0.3) shall be comma delimited. Example L0-01A, L0-01B WC Pan 211807,Wallgate ALS180 Basin 211808 1. Spray the CWC with a bathroom type cleaner, 2. 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 Certificate 1,,10

Sheet Zone System Job

Column Space Names* Component Names** Description (sub tasks)

Job

Resource Names

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.

Example millimeters squaremeters cubicmeters Pounds

Sheet Facility Facility Facility Facility

Column Linear Units Area Units Volume Units Currency Unit

Table 8: Common units of measure Numeric values shall be provided without units appended. Unknown values may be entered as 0.

Example millimeters

Sheet Floor (Sector)

© 2012 AEC3 UK Ltd

Column Elevation

38

July 2012

UK COBie 2.4 Requirements millimeters millimeters squaremeters squaremeters millimeters Pounds millimeters

Floor (Sector) Space Space Space Type Type Coordinate

Height Useable Height Gross Area Net Area Nominal Length, Nominal Width, Nominal Height Replacement Cost 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 W kg

Sheet Attribute Impact

Value Column Value Value

Unit Column Unit 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 Year hour Year Year Year Year

Sheet Type Job Job Impact Impact Impact

Value Column Expected Life Duration Frequency LeadInTime Duration LeadOutTime

Unit Column Duration Unit Duration Unit Frequency Unit (fixed) (fixed) (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 p rovided. 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)

© 2012 AEC3 UK Ltd

39

July 2012


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-builder’s) 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

Contact

Contents People and Companies: actors and their roles including designers, consultants, contractors, sub-contractors and suppliers, warrantors and maintainers.

Figure 14: The information sheet summarises the sheet names and content, starting with ‘Contact’

Example [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Sheet Contact (all sheets) Type Type Type Issue Spare

Column Email Created By Manufacturer Warranty Guarantor Parts Warranty Guarantor Labor Owner Suppliers

Table 12: Use of Contacts.

© 2012 AEC3 UK Ltd

40

July 2012


7.3 Object sheets

Figure 15: COBie focuses on 7 principal objects (with 3 additional objects to support maintenance activities). Sheet Facility Floor Space Zone Type Component System Spare Job Resources

Contents Facility includes the Project, Site and Building/Structure Floors (Sectors) are the mandatory spatial structure. Spaces are the spatial locations where inspection, maintenance and operation Jobs occur. Zones are additional functional groupings of specs. Types are the mandatory grouping of Components as types or products, used to organise maintenance tasks Components are the physical assets. Systems are additional functional groupings of Components Spares are the physical objects and Jobs are the processes used to maintain and operate the assets. Jobs are the processes used to maintain and op erate the assets. 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.

© 2012 AEC3 UK Ltd

41

July 2012


7.4 Additional information sheets There is also a variety of additional information that may be associated to the previous Object worksheets. .

Sheet

Attribute

Document Impact Connection

Coordinate Assembly Issue

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 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 documentation. Economic and environmental impacts for objects at specific life cycle stages optionally with a flexible repeating pattern 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 through their Nominal Length, Nominal Width and Nominal Depth.) Types or Components can be aggregated, so that configurations can be managed collectively. 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: www.bimtaskgroup.org/COBie

© 2012 AEC3 UK Ltd

42

July 2012


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 COBie-UK-2012-example1-drop3.xls and .ifc COBie-UK-2012-example1-drop4.xls and .ifc

Templates for specific objects are found in www.bimtaskgroup.org/COBie [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

© 2012 AEC3 UK Ltd

43

July 2012

UK COBie 2.4 Requirements 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. http://projects.buildingsmartalliance.org/files/?artifact_id=4446 8.3.4 Production of COBie deliverable at Construction, Handover stage. http://projects.buildingsmartalliance.org/files/?artifact_id=4448

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 toolk it 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

© 2012 AEC3 UK Ltd

44

July 2012


Annex A: Recommended Attributes A.1 Facility

e m a N

Building ID

e l p e u l m a a x V E

e l p t i m n a U x E

1234‐ 567801‐ 1234‐45

n/a

Gross Area

20.00

squaremeters

Gross Volume

55.00

cubicmeters

IsLandmarked

false

logical

Is Permanent ID

true

logical

Land Title Number Net Area

ESX257525

© 2012 AEC3 UK Ltd

18.50

squaremeters

n o i t p i r c s e D

A unique identifier assigned to a building. A temporary identifier is initially assigned at the time of making a planning application. This temporary identifier is changed to a permanent identifier when the building is registered into a statutory buildings and properties database. Sum of all gross areas of spaces within the building. It includes the area of construction elements within the building. May be provided in addition to the quantities of the spaces and the construction elements assigend to the building. In case of inconsistencies, the individual quantities of spaces and construction elements take precedence. Sum of all gross volumes of spaces enclosed by the building. It includes the volumes of construction elements within the building. May be provided in addition to the quantities of the spaces and the construction elements assigend to the building. In case of inconsistencies, the individual quantities of spaces and construction elements take precedence. This building is listed as a historic building (TRUE), or not (FALSE), or unknown. Indicates whether the identity assigned to a building is permanent (= TRUE) or temporary (=FALSE). The land title number (designation of the site within a regional system). Sum of all net areas of spaces within the building. It excludes the area of 45

July 2012


Net Volume

46.25

1

cubicmeters

Number Of Storeys Occupancy Type

prison

n/a

Ref Elevation Ref Latitude

50000.0 51 , 30 , 0

millimeters n/a

Ref Longitude

0 , ‐7 , ‐34

n/a

TrueNorth

0.0 , 1.0

UPRN

44010823

n/a

TOID

osgb1000001 134770

n/a

© 2012 AEC3 UK Ltd

number

construction elements within the building. May be provided in addition to the quantities of the spaces assigend to the building. In case of inconsistencies, the individual quantities of spaces take precedence. Sum of all net volumes of spaces enclosed by the building. It excludes the volumes of construction elements within the building. May be provided in addition to the quantities of the spaces assigned to the building. In case of inconsistencies, the individual quantities of spaces take precedence. The number of storeys within a building. Occupancy type for this object. It is defined according to the presiding national building code. Ref Elevation World Latitude at reference point (most likely defined in legal description). Defined as integer values for degrees, minutes, seconds, and, optionally, millionths of seconds with respect to the world geodetic system WGS84. World Longitude at reference point (most likely defined in legal description). Defined as integer values for degrees, minutes, seconds, and, optionally, millionths of seconds with respect to the world geodetic system WGS84. Vector indicating the orientation of the model against geographic north. The UPRN is the persistent key identifier providing consistency across the AddressBase product range. All historic, alternative and provisional addresses for a Basic Land and Property Unit (BLPU) are recorded against the same UPRN. The TOID is a unique feature identifier for the building and comes from the OS MasterMap Topography Layer. The TOID is a 16 character number that is prefixed with ‘osgb’ and will stay the same throughout the life of a feature. 46

July 2012


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

e m a N

Benefit CeilingCovering

Concealed FinishCeilingHeight

e u l a V

1 none

false

FinishFloorHeight

FloorCovering

t i n U

2500.0

boolean millimeters

0

millimeters

none

n/a

GrossCeilingArea

GrossPerimeter

© 2012 AEC3 UK Ltd

client n/a

squaremeters

11546.8

millimeters

47

n o i t p i r c s e D

Beneficial measure Label to indicate the material or finish of the space ceiling. The label is used for room book information and often displayed in room stamp. Concealed Height of the suspended ceiling (from top of flooring to the bottom of the suspended ceiling). To be provided only if the space has a suspended ceiling with constant height. Height of the flooring (from base slab without flooring to the flooring height). To be provided only if the space has a constant flooring height. Label to indicate the material or finish of the space flooring. The label is used for room book information and often displayed in room stamp. Sum of all ceiling areas of the space. It includes the area covered by elementsinside the space (columns, inner walls, etc.). The ceiling area is the real (and not the projected) area (e.g. in case of sloped ceilings). Gross perimeter at the floor level of this space. It all sides of the space, including those parts of the perimeter that July 2012


GrossVolume

cubicmeters

GrossWallArea

squaremeters

Height

InteriorOrExteriorSpace NetCeilingArea

NetPerimeter

2500.0

internal

millimeters

n/a squaremeters

11546.8

millimeters

NetVolume

cubicmeters

NetWallArea

squaremeters

© 2012 AEC3 UK Ltd

48

are created by virtual boundaries and openings (like doors). Gross volume enclosed by the space, including the volume of construction elements inside the space. Sum of all wall (and other vertically bounding elements, like columns) areas bounded by the space. It includes the area covered by elements inside the wall area (doors, windows, other openings, etc.). Total height (from base slab without flooring to ceiling without suspended ceiling) for this space (measured from top of slab below to bottom of slab above). To be provided only if the space has a constant height. InteriorOrExteriorSpace Sum of all ceiling areas of the space. It excludes the area covered by elementsinside the space (columns, inner walls, etc.). The ceiling area is the real (and not the projected) area (e.g. in case of sloped ceilings). Net perimeter at the floor level of this space. It excludes those parts of the perimeter that are created by virtual boundaries and openings (like doors). It is the measurement used for skirting boards and may include the perimeter of internal fixed objects like columns. Net volume enclosed by the space, excluding the volume of construction elements inside the space. Sum of all wall (and other vertically bounding elements, like columns) areas bounded by the space. It excludes the area covered by elements inside the wall area (doors, windows, other July 2012


OccupancyNumber

1

OccupancyType

custody

Perimeter Utilisation WallCovering

each

n/a

11546.8 95.50 none

millimeters percent n/a

openings, etc.). Number of people required for the activity assigned to this space. Occupancy type for this object. It is defined according to the presiding national building code. Perimeter Planned Availability Label to indicate the material or finish of the space walling. The label is used for room book information and often displayed in room stamp.

Table 15: Recommended additional Space and Zone Attributes Recommended Space and Zone Attributes are scheduled in specific Templates can be obtained from www.buildingsmart.org , www.buildingsmart.org.uk .

A.3 Component Name

Area IsExternal Length Mark Mounting Height Structural Tag Volume

Value

5.74 false 4627.5 DD1120 1200.0 false DD1120 0.86

Unit

Description

squaremeters boolean millimeters n/a millimeters boolean n/a cubicmeters

Area IsExternal Length Mark Mounting Height Structural Tag 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 Component’s Type or System(s) . Recommended Component Attributes are scheduled in specific Templates can be obtained from www.buildingsmart.org , www.buildingsmart.org.uk .

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)

See templates published by buildingSMART and buildingSMART UK and the UK BIM Task group website

© 2012 AEC3 UK Ltd

49

July 2012


Table 17: recommended Type and System Attributes

© 2012 AEC3 UK Ltd

50

July 2012


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 RowName (column F) must be unique o Every System Name (column A) taken with Component-Names (column E) must be unique Every Zone Name (column A) taken with Space-Names (column E) must be o unique Elsewhere every Name and Email (column A) must be unique. o Clarity of Naming 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 o use comma Integrity of References o Every reference to other sheets must be valid Every reference to enumerations and classifications must be valid o Consistency of Units Length, Area and Volume and Currency values must be consistent with the o Facility unit declarations. Units must be provided separately from the value for all other numeric o Attributes. Completeness of the Data 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 o Every Space shall be assigned to at least one Zone There shall be multiple Zones. o o There shall be multiple Systems. All required (yellow) and reference (salmon) fields including classification must o be provided. Attributes for the Facility, Spaces and Zones must be provided as Annex A o above o Attributes for the Types must be provided as required in the Type Templates (www.bimtaskgroup.org/COBie ) Accuracy 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 o assigned to the Type or System, not the Component the Floor or Zone, not the Space Common Documents (excluding condition reports, photographs and o 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 Maintain any External System identifiers (Global Id’s or GUIDS) o

© 2012 AEC3 UK Ltd

51

July 2012

COBie-UK-2012.pdf

Recommend Documents