Professional Documents
Culture Documents
BIM Manual
BIM Manual
BIM Manual
TABLE OF CONTENTS
1.1.1. The request for provision of As-Built BIM documents does not relieve the Contractor
from providing also “Traditional” As –Built Documents.
1.1.2. The type of “traditional As-Built documents” required from the Contractor are
referenced – but not limited to - in the following documents:
The As-Built BIM SOW requirements shall be coordinated and consolidated with:
BIM Execution C1
FM Requirements TBA
1.2.1. The purpose of the As-Built BIM documents is to ensure that the Facility
Management firm appointed by the Employer is provided with an optimized,
robust, well aggregated future - proofed and interoperable and user-friendly set
of As-Built data and documents in order to be able to efficiently manage the
facility.
1.2.2. The As-Built BIM deliverables shall be specifically tuned to consolidate and provide
the Employer with:
b) provide collision detection and visualization and simulation solutions for Facility
Management teams;
d) provide room polylining information for efficient space and maintenance tasks
management;
f) provide As-Built BIM Model form a laser scanning reflecting the exact and real
condition of the facility condition on field;
CASE 3
CASE 4
CASE 1
CASE 2
CASE 3
CASE 4
CASE 1
CASE 2
-COBie2 (version 2.40 )XML format & (windows excel) worksheets ,
Del.2 integrated in AS-BUILD BIM models as electronic native and X X
separate as hardcopy report.
Augmented BIM model (from SCAN & BIM “light model) ) with
localized (data rich/Attributes) additional BIM modeling as per
Del.8 shop drawings (LOD400/500) and data processing of traditional X X
AS-Built documents. Including embedded FM
information/Attributes and link to O&M Shop drawing.
CASE 3
CASE 4
CASE 1
CASE 2
Configuration/augmentation of BIM model in order to have
effective linkage of BIM model to:
Del.10
• Employer controlled Security systems to assist with
access control, closed circuit TV and fire detection.
3.1.2. The Contractor shall note that the usage of the COBIe 2 (including V2.40) templates
developed for the UK is not accepted. The COBie V2.40 templates to be used shall
be the original US version developed around the OMNICLASS classification (and not
the NBS classification used for the template developed for the UK) .
3.1.3. The Contractor shall submit to the Employer, a fully extended COBIE2.4 data set
listing all Worksheet. FM Service provider “QF FM in Education City project” will have
different template and additional information to be added and integrated to the
COBie 2.4.
3.1.4. The Contractor is responsible to identify all required information and updated
templates form FM service provider “QF FM in Education City project” and
integrated in early stage to generate an Extended Full COBie data.
3.1.5. In Education City Project, the Contractor must request from QF FM latest updated
Excel Template to be integrated to COBie. This shall include, but not be limited to:
a) PM Procedures
c) PM Schedules.
d) PM Procedures' Steps
f) Equipment Standards
3.1.6. Tag numbers for valves, controls, or other "tagged" items shall be individually
identified in the "Component" worksheet. The following worksheets shall be
provided and fully integrated on COBie 2.4 worksheets.
i) (21) Material – Special materials needed for a given Job Plan Task
j) (22) Tool – Special tools needed for a given Job Plan Task
k) (23) Training – Special training needed for a given Job Plan Task
3.1.7. Minimum of data & information for a regular CAFM use must create and integrated
as per COBie Standards FM Service provider requirements. This shall include at
minimum COBie V2.40- US Template Standards and all information requested by FM
service provider (QF FM in case of Education City Projects), as per list of asset
template (latest version of this list must be requested by the (Sub) Contractor
officially on the KOM.
3.1.8. The Tag Number must be created by the Contractor as per FM Service Provider (QF
FM in case of Education City Projects) latest Codding Protocol.
3.1.9. Excel Sheet with list of all tag must be submitted in early stage to Client for
approval.
3.1.10. In case where the Tag numbering in regular As-Built Document is different from FM
Service Provider Coding Protocol requirements (QF FM in case of Education City
Projects), in this case the Contractor must follow the FM Service Provider Codding
protocol (QF FM) and create crossing reference table in COBie.
3.2.1. The FM software used by the Employer’s FM provider (Archibus v18.2 used as CAFM
for QF FM for Education City projects) has strict requirements for:
3.2.4. Those requirements shall be strictly followed by the Contractor for the As-Built BIM
deliverables Del.3 and Del.4 which consist of:
3.2.5. The method statement used by the Contractor shall ensure the early and proper
configuration of his end result BIM models in order to ensure DWG polylines of
rooms/spaces/segments/zones as per QF FM requirements will be extracted
automatically.
3.2.6. For other projects the Contractor must request and confirm Area Calculation
3.3.1. These BIM models are As-Built BIM models and are elaborated by the Contractor all
along the construction of the project, with iterative modifications and optimization
brought to the Execution BIM models.
3.3.2. These As-Built BIM models shall be real “Full” BIM models, not “Light” BIM models.
3.3.3. It is strictly forbidden for the Contractor to use, for this deliverable, a 2D As-built
drawing and process and transform them into “Light” BIM models by use of specialist
software such as ZIGGURAT or equivalent.
a) ZIGGURATT
b) KANBIM
c) is strictly forbidden for any activity (even work-in-progress internal check in-house
by the Contractor or one of his sub-contractor) related to the project.
3.3.5. The Contractor shall note that the Execution BIM Model (LOD400) is planned &
performed for construction process and As-Built BIM Model (LOD500) is planned &
performed for FM/CAFM uses, consequently each BIM model must be optimized for his
specific use.
3.3.6. The Contractor shall make a clear distinction on his BIM Execution Plan between
Recorded Execution BIM Models part of Vol 3 - Appendix C and deliverables and As-
Built BIM part of Volume 3 – Appendix C2. The Contractor shall refer to the Execution
BIM requirements.
3.4.1. On project case 1&2, 3D laser scanning must be as per the Execution BIM requirements
Volume 3 – Appendix C1 related clauses (as 8.2 3D Laser Scanning & sequencing & 9.1
Verification of Construction work by 3D laser scan). In case of uncompleted, incorrect
laser scanning on Execution BIM the Contractor shall perform a new 3D laser scanning
as per Case3&4 requirements with no additional cost or/and time impact.
3.4.2. In all 4 cases 3D laser Scanning technology used shall ensure an integrated high
definition 3D photos capture and coloured (photo pixels) Point clouds data capture.
The data process to the BIM Models must be set with automated registration process
through Recap Autodesk, RealWorks Trimble or equivalent to ensure a full integration
and a straightforward data consolidation.
3.4.3. The final photo pixelated point clouds Models shall have active all captured 3D photos
as per the positioning of the tripod 3D Laser scanners.
3.4.4. Deliverable 6, must include the processing of the scanned data to the BIM Model by
using Recap Autodesk or equivalent.
3.4.5. The Contractor shall deliver the full native format of the 3D laser scan, the final
3.4.6. 3D Laser scanning includes indoor and outdoor elements inside of the project site
boundary including additional 15 meter beyond site boundary
3.4.7. The Contractor shall always use reflector-less 3D laser scanners to ensure safety and
minimize impact on site.
3.4.8. The Contractor shall ensure his 3D laser scanning (and subsequent modelling from the
cloud of points) includes the following:
a) Existing site grading surface modelling of the entire property. The surface model
shall extend 15 meters beyond the property line in all directions to provide site
context to the BIM model.
b) Elements to include in the basic (LOD 200 as per BIM Forum) site plan BIM model
are:
b.3 Driveways
b.5 Walkways
3.6.1. NA
3.7.1. The Contractor shall develop the As-Built BIM Model LOD500 exclusively from
Approved 3D laser Scan Model.
3.7.2. The Contractor shall generate a deviation report on dedicated software to highlight
all deviation out of tolerance (300 mm or as agreed) between the Execution Model
LOD400 and 3D laser Scan Model
3.8.1. The FM provider of the Employer is especially interested in being able to: extract
automatic schedules from the As-Built BIM model, visualized directly in the BIM model
the scheduled equipment:
3.8.1.1. (for example, all systems having a warranty of 5 years expiring in 2018 when handed
over in 2013)
3.8.2. The Structure and discipline of the BIM modelling of the Contractor requires to be very
thorough in order for this scheduling and visualization to be effective.
3.8.3. The Contractor’s attention is brought upon existence of BIM modelling protocols
allowing for easy scheduling:
3.8.3.1. (for example: NATSPEC BIM Scheduling guidelines – Standardised Australian Practice
for the Exchange of Digital Building Information. December 2010)
3.8.4. In the absence of information form the FM provider of the Employer, the following
building “special equipment” shall be scheduled – at minimum - from the BIM models:
a) Doors
b) Manhole covers
e) FCUs
f) AHUs
g) VAV boxes
h) Air curtains
k) Smoke detectors
l) CCTV cameras
o) Pumps
q) Valves
r) Escalators
s) Lifts
t) Travellators
u) Solar panels
bb) Extra-long lead items with lead time superior or equal to 8 months
3.8.5. The Contractor shall ensure all links to O&M Manuals and As-Built Drawings shall be fully
integrated to the BIM Model element and extracted on COBie files with a live link.
3.8.6. The Contractor shall ensure the proper file structure of all linked data & documents.
3.9. BIM DEL.10 &DEL.11 / SPECIAL LINKAGE OF BIM MODEL TO EMPLOYER CONTROLLED
SYSTEMS
3.9.1. N/A
3.10.1. The training shall ensure FM provider of the Employer (2 staff) and one Employer
representative (one staff) are:
a) aware of the content of the As-Built BIM deliverables submitted to the Employer.
b) trained on how to use all the deliverables provided for specific Facility
Management purposes and interface with the FM software used by the
Employer’s FM provider.
3.10.2. The training shall be based on Case studies exercises. The content and method of the
training shall be detailed in Del.0.
3.11.1. The BIM Company must ensure a successful import of All BIM Data including COBie
and BIM Models to the CAFM used by FM service provider (ArchiBus in case of QFFM
projects in Education City).
3.11.2. The Contractor is responsible for any needed configuration of As-Built BIM data to
ensure a complete population of the CAFM system (Archibus for EC projects).
3.12.1. The Contractor shall deliver to the Employer the following software and hardware
a) BIM for FM software licenses (at minimum with the functionality of Ecodmus,
or equivalent) for 1 year plus 2 annual Upgrades, Maintenance & support.
This must include full set of all needed license for an efficient implementation,
data population and integration with selected CAFM System, this must include
a.3 Two (2) Field-Mobile license. (with all needed Modules Viewers)
b) BIM for FM software packages must include also all needed services with
minimum of 24H (Hours) Onsite training & maintenance plus 60H Hours of
remote maintenance & Tech support. The Software vendor proposal as
d) The Contractor shall supply and install BIM software license (1 year plus 2
annual Upgrades license) on the provided laptops as follows:
3.12.1.2 Hardware
a.2 Two (2) field BIM device (tablet) with all needed configuration and
software.
b) The 3 laptops will be fully handed over to the Employer with software and all
softcopies of the required deliverables as per this attachment plus reading
software compatible with native file of those deliverables (all native file form
Deliverable 0 (Del.0 (to Deliverable 15 (Del.15)).
c) The 3 laptops shall be used during the training. A Field BIM device shall be used
during the training and the exact applications and characteristics of the Field
BIM devices (including necessary applications / software to be used) shall be
communicated during the training.
3.13.1. N/A
4.1.2. Refer to Volume 3 Appendix M - Plant, Machinery and Equipment Coding Protocol.
4.1.3. The Contractor shall request from the Employer the correct coding protocol and
template to ensure the correct FM tagging number in all handover documents, this
shall include but not be limited to Shop Drawing, O&M Manuals, Equipment list
Schedules, BIM Models, COBie files, …etc.
4.1.5. Room numbering system and room polylining protocol / method shall be submitted
well in advance for the Engineer’s SONO to ensure homogeneity/coordination with
solutions adopted for other facilities managed by the Employer.
4.2.2. In the present document LOD means Level of Development, not Level of Detail (LoD).
The definition of LOD required shall be as per;
4.2.2.1. USA BIM FORUM LOD Specification Version April 30, 2015 or latest Edition.
4.2.2.2. For LOD 500 the specification on the BIM Forum Document is as per AIA LOD definitions
4.2.3. The required LOD shall be applicable for all type of EXECUTION BIM. Any LOD specified
on the project must be at minimum as per the USA BIM FORUM LOD Specification
Version April 30, 2015 or latest Edition (this include the use of BIM FORUM LOD Element
Attributes Tables).
4.3.1. N/A
4.4.1. Survey point as per QND95 is applicable, this must be set form the approved surveyor
Plan, should be clearly set and looked in the BIM Model.
4.4.2. The project base point shall define on the project coordinate system. It will be used to
position the building on the site.
4.4.3. This origin must not be moved throughout the course of the Project.
4.4.4. Building models shall always start from this point with Project north pointing up. The
Project base point shall be submitted to the Engineer for SONO and located (N/E
coordinates) inside the latest available site plan (Education City Masterplan for
Education City works).
4.4.5. The As-Built BIM documents Method Statement Report shall provide this information.
4.5.1. The Contractor shall provide a clear responsibility matrix in order to collect and
consolidate all handover information and data this shall include but not limited to
COBie data, O&M Manual, Material submittal, As-Built Drawings warranties, Specs and
all data needed for FM service provider.
4.6.1. The Quality Control of the handover data aggregation, 3D laser scanning and BIM
Modelling shall be set from the beginning of the Project for the entire process.
4.6.2. The Final As-Built BIM Models geometry shall be as per the situation on site. The
positioning of 3D scanned cloud points (or generated geometry) is always the truth
reference, in all cases the accepted tolerance difference between 3D laser scan
and the BIM models generated from As-Built drawing shall not exceed 25MM.
4.6.3. The Contractor shall demonstrate a consequence quality control on all the collected
data.
4.6.4. The Contractor shall implement a clear and efficient QA on the BIM process, and
perform regular Quality control of the BIM Models during the Works.
4.6.5. The Contractor shall configure, use and implement a specific BIM QA/QC software
(such as Solibri MSV9 or equivalent) to archive the full check of the BIM Model
deliverables (including the IFC files).
4.6.6. The Contract shall provide mature BIM Modelling Guidelines (MGL). The complete
MGL document must be included on BEP (attached as an annexure) for information
only
4.7.1. The Contractor shall progressively collate and organize the O&M manual information
and documentation during the Construction stage and link it to the BIM Models and
COBie database.
4.7.2. The Contractor shall set the O&M Manual collection process in early construction
stage with all related stakeholders in dedicated Software as OMtrak, Aconex or
equivalent.
4.7.3. The Contractor shall demonstrate the QA/QC process for all collected and updated
“Electronic Smart O&M manual” information and documentation.
4.7.4. “Electronic Smart O&M Manual” include but not limited to Electronic Manuals, Asset
Data & maintenance schedules.
4.7.5. “Electronic Smart O&M Manual” must be linked to COBie database and As-Built BIM
Models Assets and equipment.
4.7.6. Creation of O&M Manual by compilation of scanned PDF document is not allowed.
5.1. The Contractor shall map clearly the overlap and sequential (if any) activities (start
/end) for each of its proposed durations for each deliverable.
5.2. COBie deliverables (Employer approved quality checked version) shall be provided at
the beginning of the training,
6.1. The Contractor is responsible to use only authorized license for his own team and his
Sub-Contractors. This includes all BIM Software license provided to the Employer and
Engineer.
7. ANNEXURE 1
7.1.1. Part of handover document Latest version to be requested during the preparation of
the as-built deliverables.