The document discusses key aspects of an effective BIM specification including structure, communication strategies, and common issues. An effective BIM specification should have four main sections: general requirements, technical requirements, management standards, and commercial requirements. Each section addresses important elements such as software, data exchange formats, naming conventions, and more. Common issues include specifications being too generic, ambiguous, or unrealistic. The presentation provides examples of proper specification language and structure.

1. Session
2.2
-­‐
BIM
Specifica2on:
A
Recipe
for
BIM
Project
Success
Rexter
Retana
RSP
Architects
Planners
&
Engineers

2. Source: www.outsourcing-today.com
How the client
explained it
How the Architect
understood it
How the Designer
designed it
How the QS
estimated it
How the Specialist
described it
How the Engineer
analyzed it
How it was
constructed
How Client was
billed
What the Client
really needed
How the requirements
documented

3. Rexter Retana MSEI, AMASCE
BSc Civil Engineering (Philippines)
MSc BIM Management (UK, London)
@realRetana #RTC_Asia
h=ps://www.linkedin.com/in/rexterretana
BIM Manager – RSP Architects Planners &
Engineers
Contributing Member – C&S BIM Manager
Workgroup for C&S BIM Essential Guide
Co-Founder – BIM Exchange User Group
Singapore founded November 2014

4. BIM
Implementa2on
Failure
Factors
1 Lack of right skills and
capabilities to achieve the
desired goal and objectives.

5. BIM
Implementa2on
Failure
Factors
1
Lack of right skills and capabilities to achieve the desired goal and
objectives.
Source: www.weirdnutdaily.com

6. BIM
Implementa2on
Failure
Factors
1
2
Lack of right skills and
capabilities to achieve the
desired goal and objectives.
Lack of visibility over project
objectives and no proper
communication strategy.

7. BIM
Implementa2on
Failure
Factors
2
Lack of visibility over project objectives and no proper communication
strategy.
Source: www.dna.com.vn

8. Key
Learning
Objec2ves
1
2
3
Understand the structure of a BIM
Specification
Understand the required strategies and
information management practices
Write a clear and consistent BIM
Specification with confidence

9. What
is
a
Specifica2on
- a documented set of requirements
to be satisfied by a material, design,
product or services.
- define the qualitative requirements
and administrative procedures for
product, material, and workmanship
upon which the contract is based.
(Construction Specification Institute, 2011)

10. 4
C’s
of
Effec2ve
Communica2on
(Construction Specification Institute, 2011)
1
4
2
3
CLEAR
CONCISE
CORRECT
COMPLETE

11. 4
C’s
of
Effec2ve
Communica2on
1 CLEAR
Use proper grammar and simple sentence
construction to avoid ambiguity.
Common Clause:
4.3.1 Omniclass is a classification system for the
construction industry. It provides structure for electronic
data for the purpose of identifying the same object in
different applications. For this project, Omniclass shall
be the classification system to be used.

12. 4
C’s
of
Effec2ve
Communica2on
Common Clause:
4.3.1 Omniclass is a classification system for the construction
industry. It provides structure for electronic data for the
purpose of identifying the same object in different
applications. For this project, Omniclass shall be the
classification system to be used.
Proper Clause:
4.3.1 Omniclass shall be the classification system to be used
for this project. The Consultant and/or Contractor shall make
sure that the relevant asset and COBie data fields described
in Appendix D of this document shall be classified using the
Omniclass classification system.

13. 4
C’s
of
Effec2ve
Communica2on
2 CONCISE
Eliminate unnecessary words, but not to the
expense of clarity, correctness, or completeness.
Common Clause:
4.3.2 The project model data can be stored directly in
the model and/or external database. However, when
the data is stored externally, it has to be linked with the
model and not simply entered manually unless such
data is not available from the model.

14. 4
C’s
of
Effec2ve
Communica2on
Common Clause:
4.3.2 The project model data can be stored directly in the
model and/or external database. However, when the data is
stored externally, it has to be linked with the model and not
simply entered manually unless such data is not available
from the model.
Proper Clause:
4.3.2 The Consultant and/or Contractor shall ensure that the
minimum asset information requirement described in
Appendix J shall be embedded into the model or expressed
in COBie format.

15. 4
C’s
of
Effec2ve
Communica2on
3 CORRECT
Present information accurately and precisely.
Carefully select words that convey meanings.
Common Clause:
4.3.3 The Consultant and/or Contractor shall ensure
that the IFC file shall be the main information
exchange format to be used for this project, unless
otherwise agreed in the BIM Execution Plan.

16. 4
C’s
of
Effec2ve
Communica2on
Common Clause:
4.3.3 The Consultant and/or Contractor shall ensure that the
IFC file shall be the main information exchange format to be
used for this project, unless otherwise agreed in the BIM
Execution Plan.
Proper Clause:
4.3.3 The Consultant and/or Contractor shall ensure that the
IFC 2x3 Coordination View 2.0 shall be the main information
exchange format to be used for this project, unless otherwise
agreed in the BIM Execution Plan.

17. 4
C’s
of
Effec2ve
Communica2on
4 COMPLETE
Do not leave out important information.
Common Clause:
4.3.4 The Consultant and/or Contractor shall deliver a
single consolidated COBie spreadsheet in XML format
at every information exchange described in Section
4.4.

18. 4
C’s
of
Effec2ve
Communica2on
Common Clause:
4.3.4 The Consultant and/or Contractor shall deliver a single
consolidated COBie spreadsheet in XML format at every
information exchange described in Section 4.4.
Proper Clause:
4.3.4 The Consultant and/or Contractor shall deliver a single
consolidated COBie spreadsheet in XML format at every
information exchange described in Section 4.4 and shall use
US COBie 2.4 template that can be downloaded from the
COBie means and methods page. (http://www.nibs.org)

19. How
is
the
structuring?
Clause 4.3.1
Clause 4.3.2
Clause 4.3.3
Clause 4.3.4
Classification System
Information Requirement
Exchange Format
Commercial Requirement
Poorly Structured!!!

20. 3
Common
Issues
in
BIM
Specifica2on
1
2
3
Generic
Ambiguous
Unrealistic

21. 3
Common
Issues
in
BIM
Specifica2on
1 Generic
Single generic clause that is devoid of
justification and detail.
Common Clause:
3.2 This project will be undertaken utilizing BIM design
tools and processes and is to be at Level 2 standard in
line with BS1192. The Architect is expected to
undertake the BIM Manager role. (full stop)

22. 3
Common
Issues
in
BIM
Specifica2on
1 Generic
Common Clause:
2.6.2 The Contractor shall procure the Building
Information Model (BIM), a powerful three-dimensional
computer modelling tool, to help in the built
environment around the world to improve productivity
and save cost by reducing wastage of resources and
time.

23. 3
Common
Issues
in
BIM
Specifica2on
2 Ambiguous
Does not convey obvious meaning and is
open to more than one interpretation.
Common Clause:
3.4 All files submitted by the Contractor must be in file
format interoperable with .dwg.
6.1 All models to be submitted by the Contractor shall
be at minimum in Level of Detailing Standard 3
inclusive of all M&E disciplines.

24. 3
Common
Issues
in
BIM
Specifica2on
2 Ambiguous
International BIM Dictionary Website

25. 3
Common
Issues
in
BIM
Specifica2on
3 Unrealistic
Not achievable or inappropriate to reality.
Common Clause:
5.1 The Consultant and/or Contractor shall make sure
that the model is zero clashes prior to submission as
described in Section 6.2.

26. What
comprise
a
good
BIM
Specifica2on?

27. BIM
Specifica2on
Framework
1 2
3 4
General Requirement Technical Requirement
Management Standards Commercial Requirement

28. General
Requirement
1
General Requirement
BRIEF OVERVIEW
HOLISTIC
GENERIC SUMMARY OF ALL
THE REQUIREMENTS

29. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

30. Management
Standards
A ROLES & RESPONSIBILITIES
B BIM EXECUTION PLAN
C COMMON DATA ENVIRONMENT
D MODEL SEGRAGATION STRATEGY
E QUALITY CONTROL
F PROJECT REVIEWS
3
Management Standards

31. Commercial
Requirement
A ASSET INFORMATION
B COBie
C DATA DROPS
D LASER SCANNING
E MILESTONES & DELIVERABLES
F ELECTRONIC DATA EXCHANGE
G RISK & IP
4
Commercial Requirement

32. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

33. Technical
Requirement
A SOFTWARE
Common Clause:
2.1 All primary BIM authoring tool to be used for
Architecture, Structure, Mechanical, Electrical,
Plumbing & Sanitary modelling shall be on the same
platform and version. Every software application shall
be IFC certified by the buildingSmart.

34. Technical
Requirement
A SOFTWARE
Proper Clause:
2.1 It is envisage that the Consultant and/or
Contractor will use multiple BIM platforms, therefore all
model authoring tool to be used should have passed
the IFC2x3 Coordination View 2.0 certification with
minimum export certification.
(http://www.buildingsmart-tech.org/certification)

35. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

36. Technical
Requirement
B DATA EXCHANGE FORMAT
Common Clause:
3.1 The Consultant and/or Contractor shall make sure
that the latest IFC file shall be the main information
exchange format to be used for this project.

37. Technical
Requirement
B DATA EXCHANGE FORMAT
Proper Clause:
3.1 The Consultant and/or Contractor shall ensure that
the IFC 2x3 Coordination View 2.0 shall be the main
information exchange format to be used for this
project, unless otherwise agreed in the BIM Execution
Plan.

38. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

39. Technical
Requirement
C GEOSPATIAL REFERENCING
Proper Clause:
4.1 The Consultant and/or Contractor shall coordinate
and collaborate using a single agreed coordinate
point. This agreed coordinate point shall be clearly
specified in the BIM Execution Plan.

40. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

41. Technical
Requirement
D Level of Detail
Common Clause:
5.1 Each BIM element shall be modelled according to its
size, shape, location and quantity. At early stages of the
project, element properties are more generic and
approximate, but become more specific and increases
in accuracy as the project progresses.
5.2 The model shall be developed in level of detail that is
fit purpose and as recommended in the Singapore
Modelling Guidelines.

42. Technical
Requirement
D Level of Detail
- the granularity of an element
or the completeness and
accuracy of the virtual shape
representation compared to
the physical and functional
characteristics of the actual
object.
- it is not the same as Level of
Development

43. Technical
Requirement
D Level of Detail
At Schematic level of detail
(Grade 1) – the object should be
characterised by key connections
& connectivity, using either wire-
line representation or specific
connection points.
- this level of detail can be used to
present the extent of the object
and its connectivity through a 3D
bounding box, so its location, size
and adjacencies are visible.

44. Technical
Requirement
D Level of Detail
At Coordinating level of detail
(Grade 2) – the object should be
characterised by more detailed
shape sufficient to recognise the
object to ensure it has sufficient
space allocated.
- the purpose of coordinating
level of detail includes object
recognition, spatial allocation &
clash detection. This detail is useful
for space use & construction
processes.

45. Technical
Requirement
D Level of Detail
At Visualization level of detail
(Grade 3) – the object should be
characterised by more detailed
shape sufficient to create a
recognisable image to envisage
its operation and use.
- the use-case for visualisation
level of detail include rendering,
and visualisation of the usability of
e q u i p m e n t , i n c l u d i n g t h e
simulation of connections on
equipment through name ports.

46. Technical
Requirement
D Level of Detail
Proper Clause:
5.1 It is envisage that the models produced by the
Consultant and/or Contractor contain elements of
varying level of details, therefore the Consultant and/
or Contractor shall make sure that the desired level of
detail is incorporated into the model in order not to
overload the model with unnecessary details.

47. Technical
Requirement
D Level of Detail
Proper Clause:
5.2 For minimum definition of level of detail, the
Consultant and/or Contractor shall refer to the
illustration below, unless otherwise agreed in the BIM
Execution Plan. (Reference: BS 8541-3:2012 Library objects
for architecture, engineering and construction)

48. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

49. Technical
Requirement
E Level of Development
Common Clause:
6.1 The Consultant and/or Contractor shall ensure that all
models to be submitted shall be in the level of
development/detail described in Table 2 of the
Singapore BIM Guide Version 2.0.

50. Technical
Requirement
E Level of Development
Source: Singapore BIM Guide Version 2

51. Technical
Requirement
E Level of Development
- A framework in which the
project team can rely on the
element’s geometry and the
attached information at
specific project stage when
using the model.
- A reliable output of both
graphical & non-graphical
information.
Level of Detail
Level of Information
+

52. Technical
Requirement
E Level of Development
LOD 100 Definition
what it is: The model element is graphically represented in the
model with a symbol or other generic representation.
Overall building massing indicative of are, height, volume,
location and orientation maybe modeled in 3 dimension.
associated project phase: Conceptual Design
model content: Massing or 2D-line representation
level of detail: n/a
asset information: n/a
model can be relied for: Outline Planning Permission, Project Feasibility

53. Technical
Requirement
E Level of Development
LOD 200 Definition
what it is: The model element is graphically represented within the
model as generic system, object or assembly with
approximate quantities, size, shape, location and
orientation.
associated project phase: Schematic or Preliminary Design
model content: see Appendix B – Model Content Requirement
level of detail: Grade 1
asset information: see Appendix C – Asset Information Requirement
model can be relied for: Planning Approval, Tender Drawing Documentation

54. Technical
Requirement
E Level of Development
LOD 300 Definition
what it is: The model element is graphically represented within the
model as a specific system, object or assembly in terms
of quantity, size, shape, orientation, and interfaces with
other building systems.
associated project phase: Detailed Design
model content: see Appendix B – Model Content Requirement
level of detail: Grade 2
asset information: see Appendix C – Asset Information Requirement
model can be relied for: Building Plan Approval, Tender or Contract Drawing
Documentation

55. Technical
Requirement
E Level of Development
LOD 400 Definition
what it is: The model element is graphically represented within the
model as specific assemblies that are accurate in terms
of size, shape, location, quantity and orientation with
complete fabrication, assembly and detailing information
associated project phase: Construction
model content: see Appendix B – Model Content Requirement
level of detail: Grade 3
asset information: see Appendix C – Asset Information Requirement
model can be relied for: Construction, Fabrication, Shop Drawing Creation

56. Technical
Requirement
E Level of Development
LOD 500 Definition
what it is: The model element is a field verified representation in
terms of size, shape, location, quantity and orientation.
associated project phase: As-Built
model content: see Appendix B – Model Content Requirement
level of detail: Grade 3
asset information: see Appendix C – Asset Information Requirement
model can be relied for: Operations & Maintenance

57. Technical
Requirement
E Level of Development

58. Technical
Requirement
E Level of Development
Level of Detail
Level of Information
+
Ceiling Mount Projector

59. Technical
Requirement
E Level of Development
LOD 100 – Concept Design
Level of Detail Level of Information
Name: Ceiling Mount Projector
Type: Projector 303
Classification: 23-37 15 19 Video Projectors
Location: Room 328

60. Technical
Requirement
E Level of Development
LOD 200 – Schematic / Preliminary Design
Name: Ceiling Mount Projector
Type: Projector 303
Classification: 23-37 15 19 Video Projectors
Location: Room 328
Dimension: L0.6m x W0.5m x H0.7m
Description: Short Throw Projector
Level of Detail Level of Information

61. Technical
Requirement
E Level of Development
LOD 300 – Detailed Design
Name: Ceiling Mount Projector
Type: Projector 303
Classification: 23-37 15 19 Video Projectors
Location: Room 328
Dimension: L0.6m x W0.5m x H0.7m
Description: Short Throw Projector
Sustainability Performance: Low-energy consumption
Level of Detail Level of Information

62. Technical
Requirement
E Level of Development
LOD 400 – Construction
Name: Ceiling Mount Projector
Type: Projector 303
Classification: 23-37 15 19 Video Projectors
Location: Room 328
Dimension: L0.55m x W0.485m x H0.67m
Description: EPSN-CW Short Throw Projector
Sustainability Performance: Low-energy consump
Manufacturer: ESPSON PTE LTD
Material: Plastic
Color: White
Finish: Glossy
Voltage: 120 V
Constituents: Remote Control
Code Performance: Comply ISO 2118 Standards
Model No.: EP-LZ370
Serial No.: 15DEC1479397772
Barcode.: 7529982
Level of Detail Level of Information

63. Technical
Requirement
E Level of Development
LOD 500 – As-Built
Name: Ceiling Mount Projector
Type: Projector 303
Classification: 23-37 15 19 Video Projectors
Location: Room 328
Dimension: L0.55m x W0.485m x H0.67m
Description: EPSN-CW Short Throw Projector
Sustainability Performance: Low-energy consump
Manufacturer: ESPSON PTE LTD
Material: Plastic
Color: White
Finish: Glossy
Voltage: 120 V
Constituents: Remote Control
Code Performance: Comply ISO 2118 Standards
Model No.: EP-LZ370
Serial No.: 15DEC1479397772
Barcode.: 7529982
Level of Detail Level of Information
Installation Date: 2015-09-11 25T10:00:00
Warranty Start Date: 2015-09-11 25T10:00:00
Warranty Duration: 3 years
Asset Identifier: Property of Rex Institute
Tag No: F34G9
Expected Life: 15 years
Warranty Description: EPSON projectors are
warrantied against failure due to defects in
materials, workmanship for a period of
3years depending on model number and
number of hours

64. Technical
Requirement
E Level of Development
Proper Clause:
6.1 The Consultant and/or Contractor shall agree on a
specific Level of Development that will be integrated
to every project phase and shall be clearly defined in
the BIM Execution Plan.

65. Technical
Requirement
E Level of Development
Proper Clause:
6.2 For minimum definition of Level of Development,
the Consultant and/or Contractor shall refer to the
description stated in Table 1, unless otherwise agreed
in the BIM Execution Plan.

66. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

67. Technical
Requirement
F Model Content
Proper Clause:
7.1 Architectural. It is envisaged that the architectural
system in the model may vary in different level of
detail per individual element. The Consultant and
Contractor shall ensure that the minimum architectural
elements and its corresponding asset information listed
in Appendix B and Appendix C respectively shall be
included in the model.

68. Technical
Requirement
2
Technical Requirement
A SOFTWARE
B DATA EXCHANGE FORMAT
C GEOSPATIAL REFERENCING
D LEVEL OF DETAIL
E LEVEL OF DEVELOPMENT
F MODEL CONTENT
G NAMING CONVENTION

69. Technical
Requirement
G Naming Convention
Proper Clause:
8.1 The Consultant and/or Contractor shall adhere to
the following standard naming convention set in
Section 8.1.2 to 8.1.3, unless otherwise agreed in the
BIM Execution Plan. All naming standards are derived
from the Singapore BIM e-submission guidelines.

70. Technical
Requirement
G Naming Convention
File Naming Standard
Source: Singapore BIM e-Submission Guideline

71. Management
Standards
A ROLES & RESPONSIBILITIES
B BIM EXECUTION PLAN
C COMMON DATA ENVIRONMENT
D MODEL SEGRAGATION STRATEGY
E QUALITY CONTROL
F PROJECT REVIEWS
3
Management Standards

72. Management
Standards
A ROLES & RESPONSIBILITY
Proper Clause:
9.1 The Consultant and/or Contractor shall appoint a
qualified full time BIM Manager who will ensure full
compliance of all the standards and requirements
stated in this document.
9.2 The appointed BIM Manager shall have at least
three (3) years of relevant BIM management and
coordination experience.

73. Management
Standards
A ROLES & RESPONSIBILITY
§ BIM Coordinator (Architecture)
§ BIM Coordinator (Structure)
§ BIM Coordinator (M&E)
§ Information Manager
Source: Construction Industry Council 2013

74. Management
Standards
A ROLES & RESPONSIBILITIES
B BIM EXECUTION PLAN
C COMMON DATA ENVIRONMENT
D MODEL SEGRAGATION STRATEGY
E QUALITY CONTROL
F PROJECT REVIEWS
3
Management Standards

75. Management
Standards
B BIM Execution Plan
§ Pre-Contract BEP
Source: British Standard Institute 2013
- is a document to be submitted
by the bidder detailing their
approach to project and asset
information management,
sufficient to demonstrate the
supplier’s proposed approach,
capability, capacity and
competence to meet the
information requirements.

76. Management
Standards
B BIM Execution Plan
§ Pre-Contract BEP
Source: British Standard Institute 2013
ü BIM use and objectives for
collaboration and information
modelling
ü Major project milestone
consistent with the project
programme
ü Project and Asset Information
Delivery Strategy
ü Project Implementation Plan

77. Management
Standards
B BIM Execution Plan
§ Post-Contract BEP
ü An updated and consolidated version of the BIM
Execution Plan submitted by the supply chain after
the contract award
ü Outline the overall workflow and procedures of the
supply chain in the creation, management and
delivery of information requirements.
ü Controls the overall implementation, management
and execution of BIM in a project

78. Management
Standards
B BIM Execution Plan
Source: British Standard Institute 2013 (Credit: Bew & Richards)

79. Management
Standards
B BIM Execution Plan
Proper Clause:
10.1 Pre-Contract BEP. As part of the tender selection
process, the Contractor shall submit an agreed Pre-
Contract BEP detailing their approach to project and
asset information management, and stating their
capabilities and competencies to meet the
information requirements. The Pre-Contract BEP at
minimum shall contain the following:

80. Management
Standards
B BIM Execution Plan
Proper Clause:
10.2 Post-Contract BEP. Within thirty (30) days after the
contract award, the Contractor shall re-submit an
amended, verified and agreed version of the BEP that
reflects all the standards, detailed deliverables and
intended workflows & procedures, and ensure full
compliance to the information requirements stated in
this document. The Post-Contract BEP at minimum shall
contain the following:

81. Management
Standards
A ROLES & RESPONSIBILITIES
B BIM EXECUTION PLAN
C COMMON DATA ENVIRONMENT
D MODEL SEGRAGATION STRATEGY
E QUALITY CONTROL
F PROJECT REVIEWS
3
Management Standards

82. Management
Standards
C Common Data Environment
Source: British Standard Institute 2013
ü A m e a n s o f p r o v i d i n g a
collaborative environment for
sharing production information
ü CDE can either be an extranet
system, a web-based system or
cloud based system accessible
by authorised parties
ü Drawing Management System +
Document Management System

83. Management
Standards
C Common Data Environment
Source: British Standard Institute 2013 (Credit: Bew & Richards)

84. Management
Standards
C Common Data Environment
Source: British Standard Institute 2013 (Credit: Bew & Richards)

85. Management
Standards
C Common Data Environment
Source: Autodesk 2015

86. Management
Standards
C Common Data Environment
Proper Clause:
11.1 During construction stage, the Contractor shall
set-up and managed the Common Data Environment
(CDE) that will be accessible by all authorised parties
at all time necessary.
11.2 The Contractor shall create a shared folder
accessible by all parties to hold the project
information that is approved for sharing among the
members of the project team.

87. Management
Standards
A ROLES & RESPONSIBILITIES
B BIM EXECUTION PLAN
C COMMON DATA ENVIRONMENT
D MODEL SEGRAGATION STRATEGY
E QUALITY CONTROL
F PROJECT REVIEWS
3
Management Standards

88. Management
Standards
D Model Segregation Strategy
E Quality Control
F Project Reviews
ü Model Subdivision and Work sharing mechanism
ü Model Check, Parameter Check, CAD Standards Check
ü Clash Analysis and Spatial Coordination, Construction
Schedule, Health and Safety, Cost Estimates Extraction

89. Commercial
Requirement
A ASSET INFORMATION
B COBie
C DATA DROPS
D LASER SCANNING
E MILESTONES & DELIVERABLES
F ELECTRONIC DATA EXCHANGE
G RISK & IP
4
Commercial Requirement

90. Commercial
Requirements
A Asset Information
Source: British Standard Institute 2013
d a t a a n d i n f o r m a t i o n
requirements of the organisation
(Employer) in relation to the
asset(s) that is to be managed
and maintained
Note: when asset management
processes is to be taken into
consideration for a new project, then
the appropriate AIR forms part of the
employer’s requirements

91. Commercial
Requirements
A Asset Information
Source: British Standard Institute 2013

92. Commercial
Requirements
A Asset Information
Proper Clause:
12.1 The Contractor and its supply chain shall ensure
that the minimum asset information requirements
described in Appendix D shall be embedded into the
model.

93. Commercial
Requirements
A Asset Information
Fire Protection System Asset : PUMP
Appendix D.

94. Commercial
Requirements
A Asset Information

95. Commercial
Requirement
A ASSET INFORMATION
B COBie
C DATA DROPS
D LASER SCANNING
E MILESTONES & DELIVERABLES
F ELECTRONIC DATA EXCHANGE
G RISK & IP
4
Commercial Requirement

96. Commercial
Requirements
B COBie
Construction-Operations Building information exchange

97. Commercial
Requirements
B COBie
- A performance based
specification for facility
a s s e t i n f o r m a t i o n
delivery.
- Two type of assets are
included in COBie:
equipment and spaces

98. Commercial
Requirements
B COBie
DESIGN CONSTRUCTION OPERATION
“Transporter of information”
…..because it is structured, it ensures that the information exchange can
be reviewed and validated for compliance, continuity and completeness

99. Commercial
Requirements
B COBie
Common Clause:
13.1 The Contractor shall ensure that the model
complies to the COBie requirements and submitted in
compliance to the commissioning and FM
requirements. The COBie data to be submitted shall be
in the form of COBie Excel Spreadsheet.

100. Commercial
Requirements
B COBie
Proper Clause:
13.1 The Consultant and/or Contractor shall deliver a
single consolidated COBie spreadsheet in XML format
at every data drop described in Section 14.1 and shall
use US COBie 2.4 template that can be downloaded
from the COBie means and methods page.
(http://www.nibs.org/page=bsa_cobiemm)

101. Commercial
Requirement
A ASSET INFORMATION
B COBie
C DATA DROPS
D LASER SCANNING
E MILESTONES & DELIVERABLES
F ELECTRONIC DATA EXCHANGE
G RISK & IP
4
Commercial Requirement

102. Commercial
Requirements
C Data Drops(UK Context)

103. Commercial
Requirements
C Data Drops
COBie
Data Drop 1
COBie
Data Drop 2
COBie
Data Drop 3
COBie
Data Drop 4
Preliminary
Design
Detailed
Design
Construction As-Built
DESIGN
BIM SPECIFICATION (Retana, 2015)
• Facility
• Floor
• Space
• Zone
• Contact
• Type
• Component
• System
• Assembly
• Connection
• Attribute
• Document
• Type
• Component
• Impact
• Document
• Issue
• Spare
• Resource
• Job
• Document
(Singapore Context)

104. Commercial
Requirements
C Data Drops
Proper Clause:
14.1Preliminary Design Phase. At preliminary design,
the COBie data to be extracted shall reflect the
spaces and scheduled products & equipment assets as
presented on the corresponding deliverables. The
Consultant shall be responsible to correct all deviations
in the content between the associated preliminary
design drawings and the information deliverable
described in table below.

105. Commercial
Requirements
C Data Drops

106. General
Requirement
1
General Requirement
BRIEF OVERVIEW
HOLISTIC
GENERIC SUMMARY OF THE
REQUIREMENTS

107. General
Requirements
General Requirement
2.1 The Consultant and/or Contractor shall leverage
the used of Building Information Modelling (BIM),
ensure proper synchronisation and management of
the information requirements and shall adhere to all
the standards stated in this document. Any deviation
and/or exclusion must receive approval from the
Employer.

108. General
Requirements
General Requirement
2.2 The Consultant and/or Contractor shall ensure that
all requirements stated in this document shall be met
and properly defined in the BIM Execution Plan (BEP).
Any deviation and/or exclusion must be clearly stated
in the BEP for approval.

109. General
Requirements
General Requirement
2.3 The Consultant and/or Contractor shall produce
Project Information Models (PIM) than clearly states the
intent and extent of construction work for this project
as indicated in Appendix A – BIM Objectives and
Responsibility Matrix.

110. General
Requirements
BIM Objectives & Responsibility Matrix
Source: Singapore BIM Guide Version 2

111. BIM
Specifica2on
Framework
1 2
3 4
General Requirement Technical Requirement
Management Standards Commercial Requirement

112. Consequences
of
Unclear,
Inconsistent
and
Ambiguous
BIM
Specifica2on
1 BIM Scope Creep
(Demand-side)
incremental expansion of
the project’s scope without
the necessary adjustment of
the other two elements
Source: www.bimthinkspace.com

113. Consequences
of
Unclear,
Inconsistent
and
Ambiguous
BIM
Specifica2on
2 Gold Plating
(Supply-side)
the process of adding
functionality, feature or effort
beyond what is covered in
the requirements that adds
no value to the project
Source: www.goldplating.ie

114. 64 Cannons
Hundreds of Sculptures
Flagship of Swedish Navy
Swedish Warship Vasa
1626 1628 – Aug 10
Original
Design
Main
Voyage
32
Cannons
Cannons
Added
Cannons
Added
Cannons
Added
Cannons
Added
Cannons
Added
Cannons
Added
Sculpture
Added
Sculpture
Added
Cannons
Added
Sculpture
Added
Sculpture
Added
Cannons
Added
Sculpture
Added
Sculpture
Added
Cannons
Added
Sculpture
Added
SANK LESS THAN 1 MILE OF TRAVEL
SCOPE CREEP
+
GOLD PLATING

115. Rexter
Retana
RSP
Architects
Planners
&
Engineers
Session
2.2
–
BIM
Specifica2on:
A
Recipe
for
BIM
Project
Success
@realRetana
h4ps://www.linkedin.com/in/rexterretana