Ashghal-Bpd-Standard Eir Design & Build-V2.0 - R

Building Information Modelling (BIM)
Exchange Information Requirements (EIR) for

Building Projects (Tender for Design & Build)
Version: 2.0
Last updated: 24th November 2019
STATE OF QATAR BUILDING INFORMATION MODELLING (BIM)
ASHGHAL EXCHANGE INFORMATION REQUIREMENTS
Document Properties
Building Information Modelling (BIM)-

Document Title Exchange Information Requirements (EIR)
for Building Projects (Delivery Phase)
Buildings Projects Department

Department
Public Works Authority, Ashghal
Technical Contacts 1. Obaid rashid H M AL-Athbi

Head Of Building Projects Engineering Support Section
oalathbah@ashghal.gov.qa
2. Mostafa Ismail Mostafa Darwish

Construction Management Advisor
midarwish@ashghal.gov.qa
3. Suchet Babaria
Design Engineer- 2
sbabaria@ashghal.gov.qa
Version Control
Version Purpose / Modification Author Date
2.0 Updated as per TO comments PWA- BPD- ESS 24th November 2019
Project ID: BO 2019 S 036 G Page 2 of 35 Version: 2.0

The Public Private Partnership For The West
Bay And Doha Central Car Parking
TABLE OF CONTENTS
1 Introduction ....................................................................................................................... 4
2 Definitions ......................................................................................................................... 5
3 BIM Goals and Uses.......................................................................................................... 7
3.1 Project BIM Use Requirements .................................................................................. 7
3.2 BIM Process Design................................................................................................... 8
3.3 General BIM Requirements ........................................................................................ 9
3.4 Specific BIM Requirements .......................................................................................13
4 Technical ..........................................................................................................................14
4.1 BIM Execution Planning ............................................................................................14
4.2 Software and Data Exchange File Formats ...............................................................15
4.3 Initial Test Cases.......................................................................................................16
4.4 Technological Infrastructure ......................................................................................17
4.5 Levels of Information Need .......................................................................................18
4.6 Coordinate System....................................................................................................18
4.7 Training Requirements ..............................................................................................18
5 Management .....................................................................................................................19
5.1 Standards and Guidance Documents ........................................................................19
5.2 Organisational Roles and Staffing Plan .....................................................................21
5.3 Model Structure and Volume Strategy .......................................................................23
5.4 Collaboration Procedures ..........................................................................................23
5.5 BIM Compliance Plan ................................................................................................24
5.6 Delivery Strategy for Asset Information .....................................................................25
5.7 BIM Ownership .........................................................................................................25
6 Commercial ......................................................................................................................26
6.1 Project BIM Deliverables ...........................................................................................26
6.2 Payment Milestones ..................................................................................................29
6.3 BIM Tender Response ..............................................................................................29
List of Tables ...........................................................................................................................30

1 INTRODUCTION
Building Information Modeling (BIM) is an intelligent three-dimensional model-based process that

gives architecture, engineering, construction (AEC) consultants and owners the insight and tools to
more efficiently plan, design, construct, and manage buildings and infrastructure. A true BIM model
consists of the virtual equivalents of the actual building parts and pieces used to build a building.
These elements have all the characteristics – both physical and logical - of their real counterparts.
These intelligent elements are the digital prototype of the physical building elements that allow to
simulate the building and understand its behavior in a computer environment before the actual
construction starts. With the integrated model approach, BIM offers significant productivity increase
and also serves as the basis for better-coordinated designs and a reliable computer model based
building process.
Building Information Modelling (BIM) has been identified as a fundamental process for ensuring
efficiency, quality and certainty of all Public Works Authority (PWA) projects. The PWA strategic
purpose for the application of BIM on this project is contained in Chapter 3.

2 DEFINITIONS
i. Building Information Modeling (BIM): use of a shared digital representation of a built asset
to facilitate design, construction and operation processes to form a reliable basis for decisions.
ii. BIM Execution Plan (BEP): Plan that explains how the information management aspects of
the appointment will be carried out by the delivery team.
iii. Pre- appointment BEP: The pre-appointment BIM Execution Plan focuses on the delivery
team’s proposed approach to information management, and their capability and capacity to
manage information. It is utilised prior to the appointment of any stakeholder.
iv. Post- appointment BEP: The post-appointment BIM Execution Plan is the document defining
standard methods and procedures adopted during the contract in order to meet the objectives
and requirements set forth in the EIR. It is utilised following the appointment of project
stakeholders and in particular the main contractor.
v. Building Information Model: A BUILDING INFORMATION MODEL is a digital representation
of the project, or a portion of the project, and is referred to in this document as the “BIM Model”.
Additional information is assigned to model elements.
vi. Asset Information Model (AIM): data and information that relates to assets to a level required
to support an organization’s asset management system.
vii. BIM Environment: A BIM Environment is a context enabled by BIM platforms and tools that
facilitate 3D information model based collaboration between project teams. A subset of BIM
Environment is the Common Data Environment (CDE) which is the single source of information
used to collect, manage and disseminate documentation, the graphical model and non-
graphical data for the whole project team.
viii. Model Element: A Model Element is a part of the Model representing a component, system or
assembly within a building or building site.
ix. Authoring: The action of creating and developing specific content of a model or a model
element to the level of detail required for a particular purpose.
x. Model Element Author: The entity or individual responsible for generating a Model
Component or set of components in a Building Information Model.
xi. 4D Scheduling: The fourth modelling dimension (4D) refers to 3D + time. In this model or
workflow, time is added to model objects to allow Construction Scheduling
xii. 5D Estimation: The fifth modelling dimension (5D) refers to 4D + cost. In this model or
workflow, cost is embedded within BIM Models and Model Components. 5D is used for the
purposes of generating Cost Estimates.
xiii. Level Of Development (LOD): LOD describes the minimum dimensional, spatial, quantitative,
qualitative, and other data included in a model or model element.
a. LOD 100: The model element may be graphically represented in the model with a
symbol or other generic representation, but does not satisfy the requirements for
LOD 200.

b. LOD 200: The Model Element is graphically represented within the Model as a
generic system, object, or assembly with approximate quantities, size, shape,
location, and orientation. Non-graphic information may also be attached to the Model
Element.
c. LOD 300: The Model Element is graphically represented within the Model as a
specific system, object or assembly in terms of quantity, size, shape, location, and
orientation. Non-graphic information may also be attached to the Model Element.
d. LOD 350: The Model Element is graphically represented within the Model as a
specific system, object, or assembly in terms of quantity, size, shape, location,
orientation, and interfaces with other building systems. Non-graphic information may
also be attached to the Model Element.
e. LOD 400: The Model Element is graphically represented within the Model as a
specific system, object or assembly in terms of size, shape, location, quantity, and
orientation with detailing, fabrication, assembly, and installation information. Non-
graphic information may also be attached to the Model Element.
f. LOD 500: The Model Element is a field verified representation in terms of size,
shape, location, quantity, and orientation. Non-graphic information may also be
attached to the Model Elements.
xiv. Master Information Delivery Plan (MIDP): Primary plan for when project information is to be
prepared, by whom and using what protocols and procedures, incorporating all relevant TIDPs.
xv. Task Information Delivery Plan (TIDP): Federated lists of information deliverables by each
task, including format, date and responsibilities.
xvi. Common Data Environment (CDE): agreed source of information for any given project or
asset, for collecting, managing and disseminating each information container through a
managed process.
xvii. COBie: Construction Operations Building Information Exchange (COBie) is a non-proprietary
data format for the publication of a subset of Building Information Models (BIM) focused on
delivering asset data as distinct from geometric information (www.thenbs.com).

3 BIM GOALS AND USES
PWA adopts Building Information Modeling (BIM) on the project to achieve the following goals:
a) Deliver intelligent 3D models for building and infrastructure projects to be used throughout
the lifecycle of the Programme
b) Facilitate collaboration, design proofing, and constructability reviews
c) Ensure a coordinated design by clash avoidance to reduce errors in the field
d) Streamline planning, progress reporting, and cost control
e) Improve commercial and contract management
f) Enhance visualization for communication and decision-making
g) Support operation & maintenance with handover of reliable and accurate asset data
3.1 Project BIM Use Requirements

BIM Use is a method or strategy of applying Building Information Modeling (BIM) during a project’s
lifecycle to achieve one or more specific objectives.
The Contractor shall develop appropriate strategies to achieve the required BIM uses and
associated deliverables at each stage of the project. The CONTRACTOR shall define these
strategies in BIM Execution Plan (BEP) with the help of hierarchical process maps explained in
Chapter 3.2 BIM Process Design.
The CONTRACTOR shall deliver the following minimum BIM uses to achieve tangible benefits in
line with the BIM goals:

CONSTRUCTION
CLOSURE (G6)
PRE- DESIGN
INITIATION
PROJECT
DESIGN
S. No.
(G1)
(G2)
(G3)
(G5)
BIM USE
1. Existing Site Conditions Modelling 🗹

2. Design Reviews
2.a  Site Analysis 🗹
2.b  Design Options 🗹
2.c  Accessibility Studies 🗹 🗹
3. Design Coordination
3.a  3D Coordination, & Clash Analysis 🗹 🗹
3.b  Interface Coordination 🗹
3.c  Virtual Mock- Up 🗹
3.d  Visual Method Statements 🗹
3.e  Sustainability Compliance (GSAS) 🗹 🗹
4. Drawing Production 🗹 🗹 🗹 🗹
5. Measurement
5.a  Quantity Takeoff 🗹 🗹
5.b  Material Inventory & Procurement Management 🗹
6. Construction Planning
6.a  Phase Planning 🗹
6.b  Schedule Compliance (4D) 🗹
6.c  Progress Monitoring 🗹
6.d  Constructability Review 🗹
6.e  Logistics Planning 🗹
6.f  Health & safety Support 🗹
7. Cost Management
7.a  Cost Estimation (5D) 🗹 🗹
7.b  Value Engineering 🗹 🗹
8 Engineering Analysis
8.a  Structural Analysis 🗹 🗹
8.b  Lighting Analysis 🗹 🗹
8.c  Energy Analysis 🗹 🗹
8.d  Mechanical Analysis 🗹 🗹
8.e  Other Engineering Analysis 🗹 🗹
9. Asset Handover
9.a  As- Built BIM 🗹 🗹
9.b  Field BIM (Site Forms & Asset Tagging) 🗹 🗹
10. Emergency Response 🗹
11. Asset Management
11.a Asset Information Modelling 🗹
11.b COBie (V2.4) Integration 🗹 🗹 🗹
Table 1: BIM Use Requirements

3.2 BIM Process Design

The CONTRACTOR shall develop implementation process for each BIM Use identified in Chapter
3.1 and the BIM implementation process of the project as a whole. The process maps shall be
developed to understand the overall BIM process, identify the information exchanges, and define
the various processes to be performed for the identified BIM Uses. The CONTRACTOR shall first
develop an overview map which shows how the different BIM Uses will be performed. Then, detailed
BIM Use Process Maps shall be developed to define the specific BIM implementation at an
increased level of detail. To implement this two-level approach, a Business Process Modeling
Notation (BPMN) shall be adopted to maintain consistent formatting of the process maps. The
CONTRACTOR shall include the BIM process maps in BIM Execution Plan.
i. Level 1: BIM Overview Map: The Overview Map shall be developed to show the relationship of
BIM Uses which will be employed on the project. This process map also contains the high level
information exchanges that occur throughout the project lifecycle.
ii. Level 2: Detailed BIM Use Process Maps: Detailed BIM Use Process Maps shall be created for
each identified BIM Use on the project to clearly define the sequence of various processes to
be performed. These maps shall also identify the responsible parties for each process,
reference information content, and the information exchanges which will be created and shared
with other processes.
3.3 General BIM Requirements
3.3.1 The consultant shall carry out Design authoring and any other representation of engineering
solutions using BIM tools in the BIM environment and shall cover without exception all
facility’s designed elements above and underground including but not limited to roads,
landscape, infrastructure and its connection to the main network.
3.3.2 The CONTRACTOR shall create and maintain a consolidated, multi-disciplinary, fully
integrated and verifiable three (3) dimensional solid, digital project BIM Models covering the
entire scope until completion. Models shall consist of qualified 3D solid elements reflecting
real world construction components.
3.3.3 Design drawings (example plans, elevations, sections, details etc.) shall be composed in
appropriate sheet views within the model authoring software. 2D CAD drawings shall be
extracted from authoring software in appropriate coordinate system and scale relevant to
the Design Stage and as agreed by Ashghal.
3.3.4 The CONTRACTOR shall develop BIM models for each engineering discipline, specialist
elements and subcontract including following categories, without limitation:
a) Architectural
b) Structural
c) Interior Design
d) Mechanical
e) Electrical
f) Plumbing
g) Fire Fighting and Fire Protection
h) ELV systems
i) Civil
j) Infrastructure
k) Landscaping
3.3.5 The CONTRACTOR shall carry out model authoring and any other representation of
engineering solutions in BIM environment and shall cover without exception all facility’s
designed elements above and underground including but not limited to building structures,
civil, roads, sidewalks, landscape, infrastructure and its connection to the main network.
3.3.6 The CONTRACTOR shall submit for Engineer’s approval federated and fully coordinated
Building Information Models developed to the specified Level of Development (LOD) at each
stage of the project or upon request by PWA. Non-graphical information shall be tailored to
allow seamless import into PWA’s project database.
3.3.7 The models submitted by CONTRACTOR at each project stage shall include all activities
directly or indirectly related to design, construction and documentation of the project all as
required by PWA from time to time.
3.3.5 The CONTRACTOR shall implement a whole life cycle approach to the adoption of Building
Information Modeling (BIM) for the project in line with international BIM standards and
ensure that BIM data drops are managed effectively throughout the project phases /
gateways.
3.3.8 The CONTRACTOR shall adopt necessary model organization and breakdown strategy to
allow automatic update of model- based Bill of Quantities in PWA’s BOQ format upon any
design changes carried out in the models at all stages of the project.
3.3.9 The CONTRACTOR shall ensure that BIM models and outputs are maintained and utilised
for all evaluations and assessments in relation to works measurements and variations. The
CONTRACTOR shall support submissions with relevant extracts of the BIM models to
demonstrate quantification of differences.
3.3.10 The CONTRACTOR shall perform 3D Design Coordination including identification,

coordination, and resolution of clashes between all trades based on the latest drawings /
model available and submit clashes resolution report for PWA’s review before proceeding
with respective construction work.
3.3.11 The CONTRACTOR shall adopt appropriate model collaboration procedures to perform
clash analysis (intra- discipline, inter- discipline) and 3D Coordination reviews to ensure that
design and model elements are free from hard and spatial conflicts at all stages of the

project. Minimum clearance criteria between design and model elements shall be followed
as required by relevant Authorities.
3.3.12 The CONTRACTOR shall perform 3D Interface Coordination of utilities (wet and dry) within
package and with adjacent packages for continuity, connection, and clash resolution; submit
interface coordination report for PWA’s review before proceeding with respective
construction work. Adjacent work elements outside limit of works and existing facilities shall
be modelled by the CONTRACTOR to support the coordination.
3.3.13 The 3D Models shall include temporary structures, machinery, stock piles areas, storage
yards, portable cabins, dewatering pipes, refuge areas and other such arrangements while
performing 3D Coordination and constructability reviews.
3.3.14 All 2D shop drawings shall be extracted from coordinated and federated BIM Models
developed up to LOD 400 stage. The shop drawings shall at all times reflect the coordinated
3D pre-construction Model. Any changes in design need to be verified within the 3D pre-
construction Model through clash analysis.
3.3.15 Any amendments to the project BIM models that are resultant of utilising models to derive
BIM uses such as design reviews, design options, 3D coordination (clash analysis), etc.
shall be deemed to be aspect of BIM Coordination. Such amendments shall not be
considered as changes to the scope of services and thus not constitute grounds for
additional time or cost.
3.3.16 The CONTRACTOR shall develop BIM content libraries, objects and blocks necessary for
development and detailing of project models. The created BIM content shall contain
necessary geometry and attributes to support the BIM use intended at each stage of the
project.
3.3.17 The CONTRACTOR shall incorporate any updates to the models in case of design changes
including changes after delivery of the final model or during construction stage.
3.3.18 The CONTRACTOR shall implement a 4D Progress Monitoring procedure which shall be to
enable visual and numerical analysis of completed, planned and in progress activities of
construction including photo documentation.
3.3.19 The CONTRACTOR shall link all activities of the construction schedule to Model Elements
using specialised software such as Autodesk Navisworks or similar. The intent is to look
ahead at Construction sequences within a meeting forum to look at options and
opportunities to optimise workflows and minimise risks.
3.3.20 The CONTRACTOR shall develop a structured database to store project-related data
including but not necessarily limited to the following:
a) Model Element data;

b) Construction schedule including progress and forecast information;
c) Bill of Quantities;
d) Site progress photos;
e) Inspection check sheets and approvals;
f) Labor, material and plant resourcing;
g) Other information as required by PWA
3.3.21 The CONTRACTOR shall develop LOD 500 As-Built Model as per modelling guidelines
defined in approved Project BIM Manual and in continuation of the LOD 400 Model. The
CONTRACTOR through re-measurements as commissioning progresses shall continually
update the model and its appended documentation.
3.3.22 The 3D As-built Model shall always reflect the current as-built situation on-site and shall be
continuously updated with all available site information during the construction stage. The
CONTRACTOR shall demonstrate and verify on site that As-built models delivered reflect
actual construction installation.
3.3.23 The CONTRACTOR shall adopt necessary procedures to align project models for delivery
of COBie datasheets at each stage of the project. The CONTRACTOR shall collect, capture
and record project data at the point of origin thereby documenting the attributes of the facility
as the project.
3.3.24 The CONTRACTOR shall utilise BIM models for construction H&S management and
planning including the use of Contractor developed site logistic model for site inductions as
well as development of visual method statements.
3.3.25 Site forms shall be implemented on mobile devices with automated workflows leading to
effective close out of requests and better reporting. Tagging of maintainable assets shall be
done using mobile devices.
3.3.26 The CONTRACTOR shall produce digital renderings and animations as required by the
Engineer for the purposes of reporting and presentations with various stakeholders.
3.3.27 The CONTRACTOR shall perform regular QA/QC of modelled information to ensure data
integrity.
3.3.28 The CONTRACTOR shall continue the development of Issued for Construction Room Data
Sheets and update BIM models during the construction stage and extract data to the room
data sheet template prior to completion.
3.3.29 The CONTRACTOR shall submit a BIM Validation Report with the final submissions of BIM
models at completion. This report to include the following but not limited to: BIM delivery,
model structure, validation methodology, geometry and data validation (using Solibri or
similar software), Level of Development, QA/QC, As-Built Models etc.

3.4 Specific BIM Requirements
3.4.1 PWA may provide design stage project BIM models to the CONTRACTOR in addition to 2D
drawings. In the event of discrepancy, divergence or gaps between BIM models and 2D
drawings, 2D drawings take precedence and such discrepancy shall not constitute design
inconsistency or grounds for additional time or cost. The CONTRACTOR shall incorporate
2D Issued for Construction information into the project BIM models and resolve gaps,
conflicts or clashes.
3.4.2 The CONTRACTOR shall update, or build from new, BIM models to comply with the
submittal requirements of the Contract
3.4.3 The facility’s site and existing conditions shall be surveyed through Laser Scanning
technologies up to required details and geo-referenced to local datum. Point cloud data
generated form the Laser Scans shall be processed and registered to develop an Existing
Conditions site model with solid 3D geometry.
3.4.4 The CONTRACTOR shall develop further and extract model information in the form of
geometry and data to meet project sustainability requirements including providing evidence
for submissions to QSAS requirements.
3.4.5 For developing 3D As- Built Model at LOD 500, the on-site situation shall be verified by 3D
Point cloud captured through 3D Laser Scanning technologies up to required details and
geo-referenced to local.

4 TECHNICAL
4.1 BIM Execution Planning

The successful CONTRACTOR shall prepare and submit a detailed Post- appointment BIM
Execution Plan (BEP) within 14 days from the commencement date. The BEP defines uses for BIM
on the project along with a detailed design of the process for executing BIM throughout the project
lifecycle in line with requirements stated in this EIR. The BEP shall reflect CONTRACTOR’s BIM
strategy, collaboration procedures to deliver project in the Common Data Environment (CDE) and
BIM management strategy for other appointed parties such as subcontractors. The BEP shall be
updated by CONTRACTOR as required or as instructed by the Engineer. The BEP shall include,
but not be limited to the following:
a) BIM Execution Plan Overview

b) Project Information
c) Contract Information & Milestones
d) Key Project Contacts
e) Project BIM Goals and Uses
f) Organizational Roles and Staffing Plan (BIM Manager(s), BIM Coordinator(s), BIM
Engineers, sub-contractor BIM personnel & others)
g) BIM Process Design
h) Process Overview Map- Level 1
i) Detailed Process Maps for each BIM Use- Level 2
i. 3D Coordination process
ii. 2D shop drawing extraction process
iii. As- Built verification and drawing extraction process
iv. Separate process maps for other BIM Use processes applicable to the project
j) Level Of Information Need (LOIN)
k) Model Element Table
l) Collaboration Procedures
i. Collaboration Strategy
ii. Meeting Procedures
m) BIM Information Exchanges
i. Master Information Delivery Plan (MIDP)
ii. Task Information Delivery Plan (TIDP)
n) Technological Infrastructure (hardware, software & storage)
o) Model Structure and Volume Strategy
p) Project BIM Deliverables
q) Delivery strategy
r) Standards and Guidance Documents (to be further detailed in Project BIM Manual)
s) BIM Quality Management Overview (to be further detailed in BIM Quality Management Plan)
t) Delivery Strategy for Asset Information (to be further detailed in Project BIM Manual)
u) BIM Progress Reporting
v) Training Plan

Note: Refer Chapter 6.3 BIM Tender Response for requirements of pre- appointment BIM Execution
Plan
4.2 Software and Data Exchange File Formats

The CONTRACTOR shall submit BIM deliverables prescribed in Chapter 6.1 “Project BIM
Deliverables” as per file formats mentioned in table below. However, PWA shall rely on Initial test
cases as specified in Chapter 4.2 to determine the most appropriate file formats for information
exchange. The CONTRACTOR shall specify in detail each software use in the Project BIM Manual.
If required, the CONTRACTOR shall propose additional or alternative software platforms for PWA’s
No- objection.
DELIVERABLE FILE
BIM DELIVERABLE SOFTWARE TOOL
FORMATS
A. LOD 350 / LOD 400 / LOD Autodesk Revit 2018 or later .RVT
500 BIM Models .NWC
(Architecture, Structure, AND / OR .NWD
Mechanical, Electrical, .DWG (for Civil 3D)
Plumbing, Firefighting, Civil, Civil 3D 2018 or later
Infrastructure and others)
B. Analysis models Autodesk Revit 2018 or later .RVT

OR OR
To be proposed by To be proposed by
CONTRACTOR and obtain CONTRACTOR and obtain
No -objection No -objection
C. Analysis reports Document .XLS, .PDF, XML
D. 3D Coordination Model Autodesk Navisworks 2018 .NWD

(Clash analysis) or later
E. Coordination reports Document .XLS, PDF
F. 4D Scheduling model Autodesk Navisworks 2018 .NWD

or later OR
OR To be proposed by
To be proposed by CONTRACTOR and obtain
CONTRACTOR and obtain No -objection
No -objection

G. 4D Reports Document and Schedule .XLS, PDF, .XER, .MSP

Microsoft Project or
Primavera P6 for schedules
H. Animations and Export from Native or Video formats, JPEG,
Visualizations Analysis software Interactive graphics
I. 5D Cost/Quantity model Autodesk Navisworks 2018 .NWD

or later OR
OR To be proposed by
To be proposed by CONTRACTOR and obtain
CONTRACTOR and obtain No -objection
No -objection
J. 5D Reports Document Excel, PDF
K. Model-extracted coordinated Autodesk Revit export to .DWG, .DWF, .PDF

drawings target file formats
L. COBie spreadsheets COBie v2.4 plugin for .XLS, .PDF

Autodesk Revit
OR
To be proposed by
CONTRACTOR and obtain
No -objection
M. Laser scan data (Point Native software of the Laser Registered laser scans in
cloud) scanner native file format
AND AND
Autodesk recap .RCP
AND
.NWD
N. BIM Database including Microsoft Access .ACCDB, .XLS, .PDF
Asset Information Model OR
(AIM) Links Excel
OR
To be proposed by
CONTRACTOR and obtain
No -objection
O. Quality check reports Document XLS, .PDF
Table 2: Software & Data Exchange File Formats
4.3 Initial Test Cases

The CONTRACTOR shall actively participate in initial data exchange test scenarios to verify the full
functionality of PWA’s BIM processes and seamless import of information into the PWA Data Store.
The CONTRACTOR shall prepare sufficient test data including, but not necessarily limited to,
Models, attributes, documents and databases as may be required by PWA from time to time.
4.4 Technological Infrastructure

The CONTRACTOR shall define their collective strategy regarding IT systems performance
including hardware and software and propose it within the BEP. Further consideration needs to be
made for accommodating PWA’s IT performance capabilities, especially when it comes to
reviewing, sharing and issuing BIM information to PWA.
i. The CONTRACTOR shall provide necessary specialised BIM computer hardware and
software required by The Engineer or PWA’s representative to review BIM models and
related information as required from time to time.
ii. The CONTRACTOR shall provide adequate meeting space on site for model review and
coordination meetings. The meeting space shall be equipped with suitable hardware and
software including at least 1 No. 60-inch monitor or projector dedicated for BIM use.
iii. The CONTRACTOR shall make considerations for system performance to ensure that all
members of the project team, even those with hardware limitations, can access the
information efficiently. To achieve this, the CONTRACTOR shall adopt appropriate volume
strategies with the following general requirements:
a. The individual models (native and IFC) shall not exceed 200MB.
b. The federated Model size shall not exceed 500MB.
iv. The CONTRACTOR shall provide the necessary software and IT facilities needed at their
own cost including hardware, software and servers, which shall be based in the State of
Qatar. This includes the following but not limited to:
Function System Architecture
The Contractor to propose their Common Data Environment

a) BIM Management
(CDE) and collaboration procedures required to achieve BIM
(Software)
goals, objectives and uses specified for the project. The BIM
Environment shall consist of atleast the following licensed
softwares and tools subject to PWA’s approval:
 Model Authoring platforms
 Model Viewer
 Analysis software and tools
 Additional Plugins as required to extract required
outputs
 Point cloud / laser scan data review software
 Field Asset Tagging & management software
 Model Management platform and servers
 Other requirements stated under Electronic
Communications Systems

Function System Architecture
b) Hardware /  High performance Computer systems

Equipment  Laptops
 Monitors
 Projectors
 Servers
 Tablet / Mobile devices
 Laser Scanners
 Equipment for site access including PPE
Table 3: BIM Management System Architecture
4.5 Levels of Information Need

When developing the Master and Task Information Delivery Plans, for inclusion in the BEP, the
CONTRACTOR shall comply with the PWA Level of Information Need requirements for the project,
or propose alternatives for approval. The CONTRACTOR shall comply with Level of Development
(LOD) requirements stated in Chapter 6.1 Project BIM deliverables.
4.6 Coordinate System

All models shall be set up to match true world coordinates in relation to QND95 grid and shall Cross-
reference to the project guidelines.
4.7 Training Requirements

The CONTRACTOR shall undertake training of project staff, at their own cost, in the relevant
software and management processes if skills gaps are identified. The training plan shall be
explained in BIM Execution Plan (BEP) proposed by the CONTRACTOR.

5 MANAGEMENT
5.1 Standards and Guidance Documents
5.1.1 International Standards
The CONTRACTOR shall develop the project BIM Execution Plans, Processes and Guidelines in
line with the following standards and specifications:
Document Description
Organisation and digitisation of information about buildings and

civil engineering works, including building information modelling
BS EN ISO 19650-1:2018
(BIM) – Information management using building information
modelling – Part 1:Concepts and principles
Organisation and digitisation of information about buildings and

civil engineering works, including building information modelling
BS EN ISO 19650-2:2018
(BIM) – Information management using building information
modelling – Part 2: Delivery phase of assets
BS EN ISO 11442:2006 Technical product documentation. Document management.
Industry Foundation Classes (IFC) for data sharing in the

ISO 16739:2013
construction and facility management industries.
ISO 55001:2014 Optimise your assets and improve performance
Specification of information management for the operational phase

PAS 1192-3:2014
of assets using building information modelling.
Collaborative production of information – Part 4: Fulfilling

BS 1192-4:2014 employer’s information exchange requirements using COBie –
Code of practice.
Specification for security-minded building information

PAS 1192-5:2014 management, digital built environments and smart asset
management.
Specification for collaborative sharing and use of structured Health

PAS 1192-6:2018
and Safety information using BIM
AIA Document E202 -

Building Information Modelling Protocol Exhibit
2008

Library objects for architecture, engineering and construction.

BS 8541 Part 1 to 6
Shape and measurement
Unified classification for the UK industry covering all construction

Uniclass2015
sectors for classifying items, from facility to product.
Table 4: International Standards
5.1.2 Project BIM Manual
In addition to the international standards, the CONTRACTOR shall use the following general
specifications as minimum requirement to author and submit for No- Objection a Project BIM
Manual within 14 days from the commencement date. Whenever available, the CONTRACTOR
shall make use of information and standards from Design stage. The Project BIM Manual shall be
maintained and implemented by the CONTRACTOR through all stages of the project.
a) Each model element shall be classified at least by the following information:

i. Location according to work breakdown structure
ii. Name of trade/ service;
iii. Type of component
b) The structure of the Models shall be consistent with and reflect the following project data
structures:
i. Planning (Work breakdown structure)
ii. Surveying (Quantity take off)
iii. Cost breakdown (Bill of Quantities)
c) Model file and model element naming conventions shall be in accordance to PWA BIM
Naming Convention and Uniclass 2.0 classification codes for construction elements. The
CONTRACTOR shall include an example of a project file naming strategy in compliance
with PWA BIM Naming Convention.
d) Model and model elements shall follow Level of Development (LOD) based on AIA G202-
2013 (www.aia.org/digitaldocs). If required, reference shall be made to Level of
Development Specification (BIM Forum-www.bimforum.org/lod/) of BIM elements of
different building systems at different stages of their development and use in the design and
construction process.
e) Extraction of CAD drawings from the models shall follow PWA’s CAD standards
f) Model standards shall be defined in the Project BIM Manual to include:
i. Project browser organization, views, sheets and visibility settings
ii. Annotation, dimensions, abbreviations and symbols
iii. Color scheme for all model elements
iv. Attribute data definitions and shared parameters
v. Interoperability between different file formats
vi. Model units
g) Perform clash detection using dedicated software, Navisworks, Solibri Model Checker or
equivalent.
h) Use Federated model containing all relevant engineering disciplines and subcontracts.
i) Describe nature of each clash and identify clash types:

 Hard clashes: objects occupying the same space (generally automatically detected
by the software). Tolerance to be set for minimum at zero.
 Soft clashes (Clearance Clash): objects that fail to meet certain spatial/geometric
tolerances or require clearances for safety, maintenance, accessibility, installation
or other reasons.
j) All clashes to be reviewed in meeting format by relevant discipline engineer, BIM Manager,
BIM Coordinator and the Engineer.
k) Rate clashes by criticality and resolve most critical clashes as a priority.
l) Prepare detailed clash detection report at each review including list of clashes, description,
date of run, current status, proposed and final resolution and submit report to the Engineer
m) The following chapters shall be included as minimum in Project BIM Manual pertaining to
3D Clash avoidance, detection and resolution:
i. Model settings and export procedure for clash analysis
ii. Clash test settings, rules and definitions
iii. Clash Detection Matrix
iv. Intra-disciplinary and Interdisciplinary clash detection
v. Reviewing, grouping and categorizing clash detection results
vi. Standard formats for clash reports
vii. Clash resolution strategy
viii. Target coordination levels for each stage
ix. Frequency of clash detection & schedule of interdisciplinary workshops
n) 4D Modelling (Construction scheduling) Procedures and standard formats
o) 5D Modelling (Cost Estimation & Planning) Procedures and standard formats
p) Asset Information Modelling
i. COBie V2.4 Integration Procedures
ii. Employer As- Built requirements
iii. End User FM requirements
iv. Submittal formats
v. Product data integration process
vi. Additional integration process
5.2 Organisational Roles and Staffing Plan

The CONTRACTOR shall assign qualified and experienced personnel to ensure the effective
utilization and the required quality, as defined in the QA/QC plan, of all BIM deliverables. The roles
and responsibilities of BIM staff shall be clearly defined in the BIM Execution Plan (BEP) to cover
the management and delivery of information requirements in accordance with this EIR. The
CONTRACTOR shall submit detailed CV’s and certificates of proposed BIM staff for PWA’s No-
objection. The CONTRACTOR shall propose BIM staffing plan in BEP with the necessary number
of BIM personnel required to cover the project scope
i. BIM Manager:
The head of the CONTRACTOR’S BIM team shall be designated by the CONTRACTOR as the
BIM Manager. The BIM Manager shall be responsible for overall BIM management including
planning, implementation, production, coordination, approvals, training and documentation

procedures. The BIM Manager shall also undertake the role of Information Manager to carry out
BIM procedures wherever required. The BIM Manager must have the following minimum
qualifications:
a) Academic degree (e.g. engineering or architecture) from recognized institute

b) Minimum 7 years of work experience in building projects in design, engineering or
construction
c) Minimum 5 years hands-on experience of managing BIM projects of similar nature
d) Certificate in BIM Management
ii. BIM Coordinators:

The CONTRACTOR shall appoint qualified and experienced BIM Coordinators for the project.
The BIM Coordinators shall have the following minimum qualifications:
a) Academic degree (e.g. civil engineering, architecture) from recognized institute

b) Minimum 5 years hands-on experience as BIM Coordinator in specified discipline
c) Certificate in BIM Authoring tools
iii. BIM Engineers:

The CONTRACTOR shall appoint qualified and experienced BIM Engineers for the project. The
BIM Engineers shall have the following minimum qualifications:
a) Academic degree (e.g. civil engineering, architecture) from recognized institute

b) Minimum 3 years hands-on experience as BIM Engineer in specified discipline
c) Certificate in BIM Authoring tools
iv. BIM Specialist Subcontractors (Optional):

a) In cases where the CONTRACTOR does not possess in- house BIM expertise, competent
BIM Specialist Consultants / Subcontractors shall be proposed by the CONTRACTOR for
PWA’s approval. The CONTRACTOR shall submit pre- qualifications related to proposed
Consultant’s / Subcontractor’s qualifications, experience and other relevant details for
PWA’s review prior to appointment.
b) The CONTRACTOR shall undertake BIM supply chain capability assessments for key
subcontracts prior to appointment to ensure subcontractor BIM models are developed
according to the requirements of the BEP. The CONTRACTOR shall include assessment
using including "BIM Assessment form" and "BIM Resources Assessment form" with
request for approval of the Engineer to appointment of the subcontractor.
c) In an unlikely event of default by a subcontractor on its BIM obligations, it shall not relieve
the CONTRACTOR of responsibility and duties under the contract to perform in due time
and at his own cost all necessary BIM services to compensate for the subcontractor’s
default.

5.3 Model Structure and Volume Strategy

i. Information shall be managed in accordance with the processes described in ISO 19650-
1:2018 and ISO 19650-2:2018.
ii. File naming for models and extracts for models should be in accordance with PWA BIM
Naming Convention. The CONTRACTOR shall determine and list the structure for model file
names in the BEP.
iii. The CONTRACTOR shall provide a methodology for how models will be managed. This shall
be coordinated by the BIM Manager.
iv. The CONTRACTOR shall provide a methodology for dividing the project into manageable
volumes and how these volumes shall be defined and managed for all model authors.
v. The CONTRACTOR shall define composition of model elements contained within each
volume and ensure that all project elements are included.
5.4 Collaboration Procedures
5.4.1 Collaboration Strategy
The CONTRACTOR shall provide, implement and manage a Common Data Environment (CDE)
for the project as described in BS EN ISO 19650-2:2018 to collaborate and share information with
the project team.
i. CONTRACTOR’s BIM Manager shall undertake the role of Information Manager and shall
be responsible for managing the operation, standards and culture of CDE in accordance with
the scope of works.
ii. The CONTRACTOR shall manage BIM information in native and specified formats via project
CDE.
5.4.2 Information Exchange
i. The CONTRACTOR shall provide a schedule identifying the frequency of collaboration and
information exchange.
ii. The exchange of information should be optimised to ensure that meeting participants have
sufficient information to collaborate for both the purpose and maturity of the process e.g.
clash reports for the areas being discussed, completed COBie and other FM data required
by the employer for review prior to completion of a data drop. The CONTRACTOR shall
indicate when information is exchanged prior to meetings.
iii. The CONTRACTOR’s BIM submissions or data drops shall follow the project submission
protocol. BIM deliverables specified in Chapter 6.1 shall be submitted to “Supervision
Consultant” for approval and to PWA “For Information”.
5.4.3 Meeting Procedures

The CONTRACTOR shall provide a schedule of meetings / workshops for project collaboration
identifying the frequency, participants, location and stage at which meeting is required for each type
of meeting.
i. A BIM Kick-off meeting shall be conducted at commencement of project to agree roles,

responsibilities and authorities.
ii. The CONTRACTOR shall organise regular review meetings to demonstrate progress of BIM
deliverables. The meetings shall be conducted on monthly basis or as required by PWA from
time to time.
iii. The CONTRACTOR shall conduct regular coordination workshops as required for clash
resolution process defined in BIM Use Process for 3D Coordination. The meeting shall
include trade contractors and suppliers in addition to the project team.
iv. The CONTRACTOR shall conduct constructability review meetings including virtual mock
ups as required to support BIM Use processes.
5.5 BIM Compliance Plan
5.5.1 QA / QC Responsibilities
The CONTRACTOR shall assume full responsibility for QA/QC of BIM process and project BIM
models. The CONTRACTOR shall Implement QA on the BIM process and perform regular QC on
BIM models and other relate documents as detailed in the BEP. The CONTRACTOR shall include
QA/QC checks on following without limitation:
i. BIM models
ii. BIM Process
iii. BIM interdisciplinary collaboration process including with subcontractors
iv. BIM Data management
v. Production and extracted of co-ordinated shop drawings
vi. Clash detection configuration process and reports
vii. Field BIM use
viii. Other BIM Data.
5.5.2 BIM Quality Management Plan
The CONTRACTOR shall prepare and submit for No- Objection a BIM Quality Management Plan
within 14 days from the commencement date. The BIM Quality Management Plan shall be specific
to the project, applicable to all construction stages and shall include at minimum:
i. The overall BIM Quality Assurance and Quality Control (QAQC) processes
ii. QAQC ownership and responsibilities of the CONTRACTOR’s BIM Personnel team
iii. Checklists with description of checkpoints in compliance with the agreed CAD/BIM
specifications for each discipline
iv. Final checklist for handover of BIM submissions or deliverables to PWA
v. A monthly BIM QAQC report shall be included in CONTRACTOR’s Monthly Progress report
vi. Design quality assurance methods

vii. BIM Compliance reporting procedures

viii. Model audit procedures
A QAQC report shall be included in CONTRACTOR’s Monthly BIM Progress report.
5.6 Delivery Strategy for Asset Information
i. The asset information should be delivered in the COBie format to PAS 1192-4:2014 standards
as part of the Information Exchanges identified in the Responsibility Matrix. Assets identified
in the Employers Asset Model should be populated with data appropriate to the level of Model
Definition for each Data Exchange. Assets shall include Uniclass 2015 codes.
ii. A mandatory field is required which provides a link from the assets identified in the Asset
Information Model to the relevant documents of the Operations and Maintenance manual. In
additional, a field is also required which includes a Unique Asset Identifier.
iii. The CONTRACTOR shall develop and submit ‘Delivery Strategy for Asset Information’
overview as a part of the BIM Execution Plan. This chapter shall be detailed in Project BIM
Manual to include procedures and methodology for preparing and validating the Asset
Information Model (AIM) and Construction Operations Building Information Exchange
(COBie).
iv. An ‘AIM Manual’ shall be submitted as part of the AIM documentation and will be the key to
understanding and utilising the AIM.
v. A detailed AIM Validation Report shall also be submitted as part of the handover process.
vi. The CONTRACTOR shall prepare and submit close-out documentation to be used for
information hand-over to CGIS / CMMS/ FM and other local authorities, and to prepare
operation and maintenance of built assets.
vii. The CONTRACTOR shall participate in requirements collection workshops for the purpose of
capturing end- user facility management requirements and recording the asset data required
for FM functions.
5.7 BIM Ownership
i. BIM in its entirety (including the BIM Models, information contained therein, and
documentation derived from it) shall remain the property of the PWA on whose behalf it will
be authored.
ii. PWA reserves the right to grant permission to third parties to utilise BIM content for project
related purposes. The CONTRACTOR shall obtain No- objection from PWA prior to sharing
any BIM content with third parties.
iii. PWA shall transfer authorship of the BIM model content from one party to another at various
project stages while ensuring that only a single party is responsible for authoring a BIM model
component at any point of time.

6 COMMERCIAL
6.1 Project BIM Deliverables

The CONTRACTOR, upon completion of each stage of the project or upon request shall deliver the
following minimum deliverables for approval:
PROJECT STAGE DELIVERABLES
A. PROJECT INITIATION 1. BIM Execution Plan

2. BIM Quality Management Plan
3. Project BIM Manual
B. PRE-DESIGN 1. Existing conditions Laser scan data

2. Existing site conditions model
3. Analysis models
4. Pre- Design models and reports
5. BIM Database
6. Model, drawing & document register
7. Quality check reports
C. CONCEPT DESIGN 1. Design models of each discipline up to

agreed LOD
2. Analysis models and reports
3. 3D Coordination model and reports including
proof of clash free design
4. 4D Phasing/Scheduling model and reports
5. Animations, interactive graphics and
Visualizations
6. 5D Cost/Quantity model and reports
7. Model extracted coordinated drawings
8. COBie spreadsheets
9. BIM database
D. SCHEME DESIGN 1. Design models of each discipline up to

agreed LOD (minimum LOD 200)
2. Analysis models
Visualizations
7. Model-extracted coordinated drawings
9. BIM database

E. TECHNICAL DESIGN 1. Design models of each discipline up to

agreed LOD (up to LOD 300)
Visualizations
7. Model-extracted coordinated drawings
9. BIM database
F. PRODUCTION INFORMATION 1. Updated Design models of each discipline up

to agreed LOD (up to LOD 350)
Visualizations
7. Model-extracted coordinated drawings in
CAD & PDF format
9. BIM Database
G. CONSTRUCTION 1. LOD 400 Models of each discipline

3. BIM Use Analysis models and reports
4. 4D Scheduling model
5. 4D Progress monitoring reports / graphics
Visualizations
8. Model extracted coordinated drawings
10. BIM database

H. HANDOVER, TESTING & 1. LOD 500 Models of each discipline

COMISSIONING 2. As- Built Laser scans
3. Laser scan verification reports
(As per project Handover Strategy) 4. As- Built drawings extracted from verified
models
5. Federated Asset Information Model (AIM)
6. AIM Manual
7. BIM Validation Report
10. BIM database
I. MONTHLY BIM SUBMISSION 1. Monthly BIM Progress report

PACKAGE a. Project Particulars
b. Introduction
(To be submitted by end of each c. Overview of BIM Model Files
calendar month) d. BIM Model Development status
e. Collaboration
f. Current BIM related issues
g. Key BIM actions Items
h. BIM Project Lessons Learnt
2. Coordination Data- Summary of clash analysis
and coordination workshops
3. Current Work In Progress Data including:
a. LOD 100 / 200/ 300/ 350 / LOD 400 / LOD
500 Models
b. BIM Use Analysis Models
c. 4D Phasing & Scheduling data
d. 4D Progress monitoring reports / graphics
e. 5D Cost & quantity data
f. Laser scan verification reports & data
4. Two (02) Months BIM Look ahead Plan
5. BIM Key Performance Indicators (KPIs)
6. BIM Database
Table 5: Project BIM Deliverables
Note:
i. The CONTRACTOR shall incorporate BIM deliverables and associated activities into the
Project Baseline Schedule with logical links to project activities and in line with the
requirements stated above.
ii. The BIM deliverables specified in this chapter does not relieve the CONTRACTOR from
disregarding any other requirements specified in other chapters of the Tender document.

6.2 Payment Milestones

Each stage- wise BIM deliverables specified in Table 5 of chapter 6.1 Exchange of Information shall
form the payment milestones of BIM scope of works as follows:
Percent (%) of Total amount

S.n Payment Milestone
for BIM as per BOQ
Submission of deliverables specified in

1. 5%
A. BIM PRELIMINARIES
Approval of deliverables specified in

2. 5%
A. BIM PRELIMINARIES

3. 15 %
B. PRE- CONSTRUCTION

4. 15 %
B. PRE- CONSTRUCTION

5. 15 %
C. CONSTRUCTION

6. 15 %
C. CONSTRUCTION

7. 15 %
D. HANDOVER, TESTING & COMISSIONING

8. 15 %
D. HANDOVER, TESTING & COMISSIONING
Table 6: Payment Milestones
6.3 BIM Tender Response

The tenderer is required to submit completed competence assessment forms as stipulated in the
following appendices:
i. APPENDIX H- BIM EXECUTION PLAN (PRE- APPOINTMENT)
ii. APPENDIX H-1: BIM GATEWAY QUESTIONS
iii. APPENDIX H-2: BIM PROJECT EXPERIENCE SUMMARY
iv. APPENDIX H-3: EVALUATION OF BIM APPLICATION
v. APPENDIX H-4: BIM PERSONNEL EXPERIENCE SUMMARY SCHEDULE

LIST OF TABLES
Table 1: BIM Uses ......................................................................... Error! Bookmark not defined.

Table 3: Software & Data Exchange File Formats ....................................................................... 16
Table 4: BIM Management System Architecture ......................................................................... 18
Table 5: International Standards ................................................................................................. 20
Table 6: Project BIM Deliverables ............................................................................................... 28
Table 7: Payment Milestones ...................................................................................................... 29

6.3.1 APPENDIX H: BIM EXECUTION PLAN (PRE- APPOINTMENT)
The Tenderer shall prepare and submit a pre- appointment BIM Execution Plan (BEP) for delivery
of the Scope of Services. This plan shall demonstrate compliance with respect to the BIM
requirements set out in BIM Exchange Information Requirements (EIR) other Sections and Contract
Documents of the PSC. The proposal BEP shall address the following minimum chapters:
a) BIM Execution Plan Overview

b) Project Information
c) Key Project Contacts
d) Project BIM Goals and Uses
e) Organizational Roles and Staffing Plan (BIM Manager(s), BIM Coordinator(s), BIM
Engineers, sub-contractor BIM personnel & others)
f) BIM Process Design
g) Process Overview Map- Level 1
h) Detailed Process Maps for each BIM Use- Level 2
i. 3D Coordination process
ii. 2D Shop drawing extraction process
iii. As- Built verification and drawing extraction process
iv. Separate process maps for other BIM Use processes applicable to the project
i) Level Of Information Need (LOIN)
j) Model Element Table
k) Collaboration Procedures
i. Collaboration Strategy
ii. Meeting Procedures
l) BIM Information Exchanges
i. Master Information Delivery Plan (MIDP)
ii. Task Information Delivery Plan (TIDP)
m) BIM Quality Management Overview
n) Technological Infrastructure (hardware with configurations, software & storage)
o) Model Structure and Volume Strategy
p) Project BIM Deliverables
q) Delivery Strategy
r) Standards and Guidance Documents
s) Delivery Strategy for Asset Information
t) BIM Progress reporting
u) Training Plan

6.3.2 APPENDIX H-1 – BIM GATEWAY QUESTIONS
Supporting Evidence or
S.No. Question Answer Explanation
(if applicable)
1. Do you follow any national or
international BIM Standard? If
yes, please specify
2. What measures do you have in

place to ensure compliance with
your BIM Standard?
3. Do you understand the ‘Level of

Information’ required at each of
the project delivery stages?
4. Do you understand the ‘Level of

Development’ required at each
of the project delivery stages?
5. How do you carry out 3D

Coordination using BIM?
6. Explain in brief your experiences

with development of Building
Information Model through
various stages of Project
7. Explain in brief the composition

of Common Data Environment in
your organization

6.3.3 APPENDIX H-2 – BIM PROJECT EXPERIENCE SUMMARY
Provide details of minimum three recent projects delivered by your company using BIM. Attach
supporting evidence from each project to explain how BIM execution and implementation was
carried out
Project Details Project 1 Project 2 Project 3
1. Project Title
2. Location
3. Sector
4. Client
5. Contractor
6. Project value
7. BIM Delivered in- house

or by appointment of
subcontractor / BIM
Consultant
8. Contract duration
9. Scope of BIM Services
10. Benefits realised by BIM
11. Challenges faced in

achieving BIM objectives
of the project
12. Lessons learnt &
Measurable Benefits to
Authority
6.3.4 APPENDIX H-3 – EVALUATION OF BIM APPLICATION

Provide brief description about your understanding on uses of BIM at various stages of the project
as per table below. Provide supporting evidence from his organization’s past experience wherever
applicable.
Supporting
Stage BIM Uses / Application areas Understanding
Evidence
CONSTRUCTION 1. Constructability Review

AND HANDOVER
STAGE
2. Logistics Planning
3. Visual method statements
4. Quantity takeoff and Cost

Estimation (5D)
5. Value Engineering
6. Progress Monitoring
7. 3D Coordination, clash
analysis and resolution
8. Health & Safety support
9. Energy & Engineering

Analysis
10. Sustainability compliance

(GSAS)
11. Disaster Planning
12. Schedule Compliance (4D)
13. Shop drawing production

from models
14. As Built BIM and Asset

Information Models
6.3.5 APPENDIX H-4 – BIM PERSONNEL EXPERIENCE SUMMARY SCHEDULE

Provide the following BIM –specific details of personnel proposed for the project. Provide complete
CVs and certificates as separate attachment.
Years of No. of
BIM Years of
CV Position Highest BIM Profession BIM
Name Certific- experience
# & Firm Education Role al Projects
ation in BIM
experience completed


Ashghal-Bpd-Standard Eir Design & Build-V2.0 - R

Uploaded by

Copyright:

Available Formats

Ashghal-Bpd-Standard Eir Design & Build-V2.0 - R

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

Ashghal-Bpd-Standard Eir Design & Build-V2.0 - R

Uploaded by

Copyright:

Available Formats

Building Information Modelling (BIM)

Exchange Information Requirements (EIR) for

Building Information Modelling (BIM)-

Buildings Projects Department

Technical Contacts 1. Obaid rashid H M AL-Athbi

2. Mostafa Ismail Mostafa Darwish

Version Purpose / Modification Author Date

Project ID: BO 2019 S 036 G Page 2 of 35 Version: 2.0

Project ID: BO 2019 S 036 G Page 3 of 35 Version: 2.0

Building Information Modeling (BIM) is an intelligent three-dimensional model-based process that

Project ID: BO 2019 S 036 G Page 4 of 35 Version: 2.0

Project ID: BO 2019 S 036 G Page 5 of 35 Version: 2.0

Project ID: BO 2019 S 036 G Page 6 of 35 Version: 2.0

3 BIM GOALS AND USES

3.1 Project BIM Use Requirements

Project ID: BO 2019 S 036 G Page 7 of 35 Version: 2.0

1. Existing Site Conditions Modelling 🗹

Project ID: BO 2019 S 036 G Page 8 of 35 Version: 2.0

3.2 BIM Process Design

3.3 General BIM Requirements

3.3.10 The CONTRACTOR shall perform 3D Design Coordination including identification,

Project ID: BO 2019 S 036 G Page 10 of 35 Version: 2.0

a) Model Element data;

Project ID: BO 2019 S 036 G Page 12 of 35 Version: 2.0

3.4 Specific BIM Requirements

Project ID: BO 2019 S 036 G Page 13 of 35 Version: 2.0

4.1 BIM Execution Planning

a) BIM Execution Plan Overview

Project ID: BO 2019 S 036 G Page 14 of 35 Version: 2.0

4.2 Software and Data Exchange File Formats

B. Analysis models Autodesk Revit 2018 or later .RVT

D. 3D Coordination Model Autodesk Navisworks 2018 .NWD

E. Coordination reports Document .XLS, PDF

F. 4D Scheduling model Autodesk Navisworks 2018 .NWD

Project ID: BO 2019 S 036 G Page 15 of 35 Version: 2.0

G. 4D Reports Document and Schedule .XLS, PDF, .XER, .MSP

I. 5D Cost/Quantity model Autodesk Navisworks 2018 .NWD

K. Model-extracted coordinated Autodesk Revit export to .DWG, .DWF, .PDF

L. COBie spreadsheets COBie v2.4 plugin for .XLS, .PDF

Table 2: Software & Data Exchange File Formats

4.3 Initial Test Cases

4.4 Technological Infrastructure

Function System Architecture

The Contractor to propose their Common Data Environment

Project ID: BO 2019 S 036 G Page 17 of 35 Version: 2.0

Function System Architecture

b) Hardware /  High performance Computer systems

4.5 Levels of Information Need

4.6 Coordinate System

4.7 Training Requirements

Project ID: BO 2019 S 036 G Page 18 of 35 Version: 2.0

5.1 Standards and Guidance Documents

5.1.1 International Standards

Organisation and digitisation of information about buildings and

Organisation and digitisation of information about buildings and

BS EN ISO 11442:2006 Technical product documentation. Document management.

Industry Foundation Classes (IFC) for data sharing in the

ISO 55001:2014 Optimise your assets and improve performance

Specification of information management for the operational phase