ch2 BIM 2

5.2.
5 IFC Statements
• IFC is a truly global effort in AEC-FM industries
• IFC has become the most recognized standard for BIM
• IFC is supported by most global CAD software vendors
• IFC is supported by many downstream applications
• IFC is currently being used on many real and pilot projects

with international coverage.
171
“Building Information Modeling (BIM)” – Jack Cheng (HKUST)
5.2.6 Products using IFC
172
5.3 Other BIM Standards
• However, IFC is NOT the only standard in the AEC/FM industry.
• Examples of data standards in the AEC/FM industry:
– IFC / ifcXML (Industry Foundation Classes): neutral data
format to describe, exchange, and share information typically
used within the building and facility management industry
sector (AEC/FM)
– CIS/2 (CIMSteel Integration Standard Release 2): formal
specification specialized for structural steel engineering
– AEX (Automating Equipment information eXchange): XML
specifications to automate information exchange for the design,
procurement, delivery, operation and maintenance of
engineered equipment.
173
• Further examples
– gbXML (Green Building XML): XML specification for integrating
design and development tools used in the building industry.
– GML/CityGML (Geography Markup Language): an open data
model and XML-based format for the storage and exchange of
virtual 3D city models
– LandXML (Land Markup Language) for landscape
– COBie (Construction Operations Building information

exchange): an information exchange specification for the life-cycle
capture and delivery of information needed by facility managers
174
5.3.1 CIS/2 Schema
• CIS/2 (CIMSteel Integration Standards) is the product model and
electronic data exchange file format for structural steel project
information.
• Developed by NIST Building and Fire Research Laboratory since
late 1980’s.
• Latest version CIS/2 2.1 released in 2003
• CIS/2 is available in EXPRESS Schema.
• It has been adopted by the American Institute of Steel Construction
as their format for data exchange between steel related CAD
software. Autodesk Revit Structure also supports CIS/2.
• Mapping between CIS/2 and IFC is by NIST and Georgia Tech.
175
5.3.2 Green Building XML (gbXML)
• gbXML was developed to facilitate the transfer of building
information stored in CAD building information models, enabling
integrated interoperability between building design models and a
wide variety of engineering analysis tools and models.
• Developed by the GeoPraxis since late 1990’s. Latest version
gbXML V5.12 was released in 2014.
• Available in XML schema.
• It is supported by more than 20 application softwares, including
Autodesk Revit, Bentley, Graphisoft, eQuest, and EnergyPlus.
176
5.3.3 LandXML
• LandXML aims to provide a medium for the exchange of land
development data among the various software applications of the
AEC project team and for official submission to owners.
• Developed by Autodesk and published on an online community of
over 160 people from 80 organizations representing owners,
software vendors, and end users to provide feedback on the
evolving standard.
• Available in XML file format.
• Latest version LandXML-1.2 released in 2008.
(LandXML 2.0 (working draft) will be announced in October 2014)
• It is supported by over 48 registered software applications from the
major design software vendors, and has been adopted for use by
many governments around the world.
• Includes PointCloud and LIDAR format, terrain description, as-built
data collection, hydrologoy data, etc.
177
5.3.4 COBie (Construction Operations Building information
exchange)
• COBie helps capture and record important project data at the point of
origin (e.g. equipment lists, product data sheets, warranties, spare
parts lists, preventive maintenance schedules). This information is
essential to support operations, maintenance and asset management
once the built asset is in service.
• The objective of COBie is to create an open standard through which
information created during design and construction can be transferred
directly to facility operators, maintainers, and managers in useable
electronic format.
• COBie can be viewed in design, construction, and maintenance
software as well as in simple spreadsheets.
• The United States Army Corps of Engineers authored a pilot standard
of COBie in 2007. COBie became part of the US National BIM
Standard in 2011.
• Refer to: https://www.wbdg.org/resources/construction-operations-
building-information-exchange-cobie
178
Example of COBie BIM < -- > FM
179
Example of COBie
180
Example of COBie https://www.wbdg.org/resources/cobie.php
video
181
Other Available Information Exchange Standards
• The comparison between COBie sisters and brothers
Sparkie
WALLie
HVACie
WSie
COBie
IFC 4
• Electrical System information exchange (Sparkie)

• HVAC information exchange (HVACie)
• Water System information exchange (WSie)
• Wall information exchange (WALLie)
• Examples and Resources: https://www.nibs.org/?page=bsa_commonbimfiles

182
Other Available Information Exchange Standards
• More on-going / proposed “ie” projects:
most common one
• References: https://www.nibs.org/?page=bsa_infoexchange 183

5.4 Interoperability Among BIM Standards
• Software Interoperability is seamless data exchange at the software level
among diverse applications, each of which may have its own internal data
structure. We also need to handle Information Interoperability.
• Interoperability is achieved by mapping parts of each participating
application’s internal data structure to a universal data model and vice
versa.
• If the employed universal data model is open, any application can
participate in the mapping process and thus become interoperable with
any other application that also participated in the mapping.
• Interoperability eliminates the costly practice of integrating every
application (and version) with every other application (and version).
• Software integration is a special case of interoperability where the same
data model is used in separate applications or where specific integration
between two applications has occurred. In this way, interoperability is
achieved within a limited group of applications.
(NBIMS Part 1) 184

5.4.1 Lack of Interoperability
• Construction spending in the United States is estimated to be
$1.288 trillion for 2008. The Construction Industry Institute
estimates there is up to 57% non-value added effort or waste in
our current business models. This means the industry may waste
over $600 billion each year.
• Major driving cost due to lack of interoperability:
– Manually re-entering data (69%)
– Time using duplicate software (56%)
– Document version checking (46%)
– RFI processing (40%)
– Cost of data translations (31%)
• “(In the Capital Facilities Industry) .. inefficient interoperability costs
more than $15.8 billion, in the year 2002 alone..” (Gallaher et.al.,
NIST Report, 2004)
Gallaher, M. P., O’Connor, A. C., Dettbarn, J. L., and Gilday, L. T. (2004). "Cost Analysis of Inadequate Interoperability in the
Capital Facilities Industry." National Institute of Standards and Technology (NIST).
185
OpenBIM
186
5.4.2 Interoperability through Standards
• In order for a real free flow of information to occur, three factors
need to be in place:
1. The format for information exchange,
2. A standardized understanding of what the information your
exchange actually is, and
3. A specification of which information to exchange and when to
exchange the information
187
Source: NIBS’s National BIM Standard (2012)
188
• buildingSMART Standards
Name Purpose Standard

IFC Data transfer ISO 16739:2013
Industry Foundation Classes
MVD Subset of IFC buildingSMART Standard

Model View Definition
bSDD Terminology / concept ISO 12006 – 3
buildingSMART Data mapping IFD (International Framework
Dictionary for Dictionaries)
IDM Process description ISO 29481 – 1
Information Delivery Manual (exchange requirement ISO 29481 – 2
definition)
BCF Format for model‐based buildingSMART Standard
BIM Collaboration Format communication (native‐
openBIM )
189
5.4.2.1 IFC
190
5.4.2.1 IFC
191
5.4.2.2 MVD - Model View Definitions
• A specification which identifies the properties and specifies
the Exchange Requirements of Model Views.
• A 'standard' Model View Definition (MVD) is a subset of the Industry
Foundation Classes (IFC) schema intended for software developers (not
end users) to implement into their BIM Software Tools
View
Model
Definition
192
5.4.2.2 MVD - Model View Definitions
• A specification which identifies the properties and
specifies the Exchange Requirements of Model Views.
• A 'standard' Model View Definition (MVD) is a subset
of the Industry Foundation Classes (IFC) schema
intended for software developers (not end users) to View
implement into their BIM Software Tools
193
5.4.2.3 bSDD – buildingSMART Data Dictionary
(aka IFD – International Framework for Dictionaries)
• A ‘dictionary’ is used to define names.
• International Framework for Dictionaries (IFD Library) (aka
“buildingSMART Data Dictionary (bSDD)”) (ISO 12006-3:2007)
- A dictionary of construction terminology
• IFD is developed with the purpose of adding value to the IFCs and is
language and culture independent.
• All concepts are assigned a Global Unique Identifier (GUID)
• Entries in the OmniClass tables can be explicitly defined in the
IFDLibrary once and reused repeatedly, enabling reliable automated
communications between applications.
door with its frame
Norwegian English
194
In a briefing document In a briefing document In a CAD system
Properties Properties Properties
In product catalogues In a calculation system
Properties Properties
In classification systems In a Facility management system
Properties Properties
In building specifications For demolition and reconstruction
Properties bSDD/IFD Properties
Source: Espen Schulze, CEN 442 WG4 TG2
195
• Property set values:
instance
196
197
5.4.2.4 IDM – Information Delivery Manuals
Exchange Requirements
Input similar to BEP
Workflow
Activity
Activity Activity
Activity
Input
Exchange Requirements
198
Components:
• Scope Definition (Use-Case)
• Process Maps
• Exchange Requirements
• Technical Implementation (IFC)
199
• Requirement & Goal
– Standardize on
information needed
for specific tasks
within the building
lifecycle
– Development based
upon open data
standards used by all
– Provides
requirements to
software companies
200
IDM: Business Case Development – Aligning
OmniClass to BIM Process
WHO (is requesting)
1 Actor requesting information to support a process or decision
(Authoritative Reference OMNI CLASS – Table 33 & 34)
WHY (project/process use or benefit)

2 Why is this information important for a project activity
(Authoritative Reference OMNI CLASS- Table 32)
WHEN (stage in project)

3 (Authoritative Reference OMNI-CLASS-Table 31)
WHAT
4 Dataset in BIM that supports the request and benefit)
Because BIM use aggregates information several tables support this activity .
(Authoritative Reference OMNI-CLASS Tables 11, 12,14, 21, 23, 41, 49)
FROM WHOM
5 Group/Actor that provides/fullfills the information need OMNI-Class 33 34
HOW
6 Tools/formats/results Table 35 & 22
INPUTS & OUTCOME

7 Information, Product or Service Delivered Omniclass 36
201
OmniClass Table 33
WHO (is requesting) Disciplines/expertise
Actor requesting info to support a process or decision WHO/From WHOM
1 (Authoritative Reference OMNI CLASS – Table 33 & 34) OmniClass Table 34
Organizational Roles
WHY (project/process use or benefit) WHO/From WHOM
(Authoritative Reference OMNI CLASS- Table 32)
3 WHEN (stage in project) OmniClass Table 32 OmniClass Table 31

(Authoritative Reference OMNI-CLASS-Table 31) Services Phases
WHAT Activities/WHY WHEN
Dataset in BIM that supports the request and benefit)
4 (Authoritative Reference OMNI-CLASS Tables 11, 12,14,
21, 23, 41, 49)
From WHOM OmniClass Table 35 OmniClass Table 22

5 Group/Actor that provides/fullfills the information need Tools/supporting Work Results/quality
OMNI-Class 33 34
HOW HOW
HOW
6 Tools/formats/results Table 35 & 22
INPUTS & OUTCOME OmniClass Table 36

7 Information, Product or Service Delivered Omniclass 36 Information
INPUTS & OUTCOME
202
Examples corresponding
code in Omiclass
1. (Table 34) Architect aka: 34-25 21

00
WHO (is requesting)
Actor requesting info to support a process or decision
2. (Table 32) Conception services,
1 (Authoritative Reference OMNI CLASS – Table 33 & 34) Designing, Preliminary Designing
WHY (project/process use or benefit) aka: 32-11 14 13
(Authoritative Reference OMNI CLASS- Table 32) 3. (Table 31) Conception Stage aka:
31-10 00 00
3 WHEN (stage in project)
(Authoritative Reference OMNI-CLASS-Table 31) 4. (Table 12) Building 12-11 00 00;
WHAT (Table 21) Superstructure,
Dataset in BIM that supports the request and benefit) Enclosure aka: 21-41 31 00;
4 (Authoritative Reference OMNI-CLASS Tables 11, 12,14,
21, 23, 41, 49) (Table 23) Electrical Power and
From WHOM Lighting 23-80 00 00
5 Group/Actor that provides/fullfills the information need
5. (Table 34) Engineer 34-25 31 00
OMNI-Class 33 34
HOW
6. (Table 36) Design Tools (OmniClass
6 Tools/formats/results Table 35 & 22 NA for IFC)
INPUTS & OUTCOME 7. (Table 36) Building Envelope
7 Information, Product or Service Delivered Omniclass 36
Design Information:36-21 17 21
203
• Similar idea to Project Execution Plan (PEP) procedure.
• To use BIM effectively by improving the quality of communication
between different participants in the construction process.
The components of IDM are:

• Process Map
“Provides a description of an activity (or set of activities) related to
a domain in the AEC/FM industry.”
• Exchange Requirement
“A non technical description of the information required as input to
the process and the expected source of that information together
with a description of the expected results of the process.”
• Model View Definitions
“Defines a subset of the IFC schema that is needed to satisfy one
or many Exchange Requirements of the AEC industry.”
(buildingSMART, 2015)
204
5.4.2.5 BCF – BIM Collaboration Format
markup of bim
BCF
205
5.4.2.5 BCF – BIM Collaboration Format
BCF Viewer BCF Revit Plug-in
206
5.4.2.6 OmniClass consist terminology
on the contract
• CSI OmniClass™ Construction Classification System

(OmniClass or OCCS)
• OmniClass is a multi-table faceted classification system designed
for use by the capital facilities industry.
• OmniClass aims to aid sorting and retrieval of information and
establishing classifications for and relationships between objects in
a building information model.
• In the building industry, material suppliers, specification writers,
cost engineers, and many others recognize the formats,
terminology, and concepts included within OmniClass.
• OmniClass can be used in the preparation of many types of project
information and for communicating exchange information, cost
information, specification information, and other information that is
generated throughout the facility’s lifecycle.
• References to MasterFormat and UniClass
207
208
5.4.2.6 OmniClass
• Terminologies and Acronyms, e.g. OmniClass
– Multi-table faceted classification system
– 15 inter-related OmniClass tables:
Table 11: Construction Entities by Function
Table 12: Construction Entities by Form
Table 13: Spaces by Function
Table 14: Spaces by Form Table 33: Disciplines
Table 21: Elements Table 34: Organizational Roles
Table 22: Work Results Table 35: Tools
Table 23: Products Table 36: Information
Table 31: Phases Table 41: Materials
Table 32: Services Table 49: Properties
(Download: http://www.omniclass.org/tables.asp)
(Like UniClass, UniFormat, MasterFormat)

209
5.5 Interoperability Challenges information
management
1. How to formalize your data requirements?

2. How to exchange data to another perspective?
3. How to combine the exchanged data to serve your perspective?
4. How to retrieve the combined data to be used for your
perspective?
5. How to validate the retrieved data?
6. How to manage the quality of the data?
Interoperability
is Needed!
210
Interoperability Example:
• Lifecycle Energy/Carbon Simulation generative design
Design Optimization
Gan, V.J.L., Deng, M., Tse, K.T., Chan, C.M., Lo, I.M.C.*, and Cheng, J.C.P.* (2018). "Holistic BIM framework for sustainable low
carbon design of high‐rise buildings." Journal of Cleaner Production, 195, 1091‐1104.
211
OpenBIM Project
• buildingSMART International Awards Program 2019 (Design)
• Project: Queen's Wharf Brisbane
• Company: DBM Vircon (was PDC Engineering)
212
5.5 Interoperability Challenges
• (1) Lack of Software Support
• Software interprets IFC

data models
differently.
(Interoperability)
• Not support full sets of
open standards (e.g.
BCF, MVD)
• Which is better?
Too many options.
Evaluation?
Certification?
Etc. • IFC extensions?
213
5.5 Interoperability Challenges
• (2) Lack of IFC Entities, Etc.  Look forward to IFC5
MVD (Model View More…

IFC Airport Definition)
IDM bSDD
(Information (buildingSMART Data
Delivery Dictionary)
Manual)
Specific element
• Scope (For airport)
• System
• Missing IFC entities Breakdown • Space Shared element
• Entities
(E.g. Runway, taxiway, aprons, air traffic
control buildings, pier, beacon…) Common element
214
Process: Building Information
Modeling and Management
215
6.1 Facility Lifecycle Helix
• A long-term vision of open standard-based BIM proposed in
National BIM Standard (NBIMS) published by US National Institute
of Building Sciences.
• As BIM technology and use matures, the creation of repositories of
project, organization, and/or owner BIM data will expand.
• An owner’s repository may start with one or two new projects. The
repository can be further enriched later as more information
becomes available through BIM-based information exchanges.
• Commercial developers and property managers will benefit from
the shared repository of facility information since they will be able
to maximize rents based on detailed knowledge of each physical
space.
• Tracking of maintenance activities can also be facilitated.
216
• Building processes extend throughout and beyond the life of a
facility. The building process is not a strictly linear process
• Building process is a cyclical process
• Learn and improve: each cycle has a feedback accumulation
capabilities; so each cycle should add knowledge
• The information backbone at the core is made up of integrated
repositories which provide historical and current data. Through
analysis, backbone data can provide knowledge and alternatives.
217
• Representation of the business process lifecycle as a helix with a
central knowledge core and external nodes representing process
suppliers and external consumers
• Interoperability: share and re-use information easily
218
6.2 Integrated Project Delivery (IPD) NEC: share is and
profit
• Standard building delivery process:
• Liability issues  adversary oriented

• Information hiding  hard for decision making
• Relies on standard construction practices
• How to construct worked out after full design  inefficient of time
and cost 219
• Traditional organization of a project team involves contracts
between the owner and the primary architect and builder, who in
turn maintain contracts between these organizations and sub-
consultants. It prevents the flow of information, responsibility, and
ultimately the ability to effectively use BIM tools and processes.
220
• Alternative building delivery process
• Single organization for design/construction

• Teaming/collaboration oriented
• Plan construction during design
• Faster and saving of money
221
6.2 Integrated Project Delivery
• Design-Bid-Build Project Delivery: With this method, documents
are fully developed by a designer paid by the owner before bidding
by multiple contractors. This method limits a contractor’s ability to
use BIM to its full potential as a coordination tool.
• Design-Build Project Delivery: With this method, one entity
performs both architectural/engineering and construction under a
single contract. The design-builder warrants to the contracting
agency that it will produce documents that are complete and free
from error.
• Integrated Project Delivery: This method calls for integration of a
project, and utilizes up-to-date technology to foster flexibility and
successful project outcomes. This method collaboratively draws
the talents and insights of all participants, fosters a great degree of
communication, and promotes intense collaboration among the
project team.
222
223
• Preferred design process: owners driving full collaboration through
information sharing early in the project process are most likely to achieve
the desired outcomes: fast, efficient, effective, and cost-bound buildings
 achieved by BIM
224
BIM Management
225
CIC Framework for BIM Management
226
227
PAS1192
ISO19650
check BIM accept

or not
228
7.1 Common Data Environment (CDE)
• CDE: A single source of information for any given project or built
asset, used to collect, manage and disseminate all relevant
approved files, documents and data for multidisciplinary teams in a
managed process.
• For further description of its use during a project see explanatory
to ISO 19650-2.
• Sensitive information would not normally be contained within a
CDE unless that CDE is held within a secure environment.
229
• ISO 19650-2:2018
store info system
230
4 steps
information have
not been shared
with other parties
1. WIP
2 Share
3 4
old version will be
achived
design and
construction
231
7.2 BIM Collaboration assignment 2 >>
232
7.2 BIM Collaboration
233
7.3 BIM Maturity
Define an organization level of BIM Maturity
• Strategy
• BIM uses
• Process
• Information
• Infrastructure (Mom and Hsieh 2011)
• Personnel
234
BIM Maturity Levels 2016 UK
(Bew and Richards 2008)
235
• CIFE VDC Scorecard
virtual design and
construction
involved the whole

team
236
7.3 BIM Maturity country by country
• BIM Stages:
• BIM Maturity Index Levels:
Bilal Succar
Source: (https://bimexcellence.org/resources/300series/301in/)
237

ch2 BIM 2

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

ch2 BIM 2

Uploaded by

Copyright:

Available Formats

5.2.

• IFC is a truly global effort in AEC-FM industries

• IFC has become the most recognized standard for BIM

• IFC is supported by most global CAD software vendors

• IFC is supported by many downstream applications

• IFC is currently being used on many real and pilot projects

– COBie (Construction Operations Building information

• Electrical System information exchange (Sparkie)

• Examples and Resources: https://www.nibs.org/?page=bsa_commonbimfiles

most common one

• References: https://www.nibs.org/?page=bsa_infoexchange 183

(NBIMS Part 1) 184

Name Purpose Standard

MVD Subset of IFC buildingSMART Standard

In a briefing document In a briefing document In a CAD system

Properties Properties Properties

In product catalogues In a calculation system

In classification systems In a Facility management system

In building specifications For demolition and reconstruction

Properties bSDD/IFD Properties

WHY (project/process use or benefit)

WHEN (stage in project)

INPUTS & OUTCOME

3 WHEN (stage in project) OmniClass Table 32 OmniClass Table 31

From WHOM OmniClass Table 35 OmniClass Table 22

INPUTS & OUTCOME OmniClass Table 36

1. (Table 34) Architect aka: 34-25 21

The components of IDM are:

BCF Viewer BCF Revit Plug-in

• CSI OmniClass™ Construction Classification System

(Like UniClass, UniFormat, MasterFormat)

1. How to formalize your data requirements?

• Software interprets IFC

MVD (Model View More…

• Standard building delivery process:

• Liability issues  adversary oriented

• Single organization for design/construction

check BIM accept

store info system

involved the whole

• BIM Maturity Index Levels:

You might also like