MIRAL BUILDING INFORMATION

MODELLING (BIM) Protocol

Version 2.5

Exchange Information Requirements

V.2.5
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Preface
This document represents MIRAL BIM Information requirements that should be followed by all project team members.
This document is part of MIRAL BIM Protocol which aims to digitize all MIRAL requirements, processes and procedures.

This document contains set of information that addresses all MIRAL requirements, these requirements are to be distributed
to all project team members and their supply chain. Information included in this document is about MIRAL VDC Goals, IT
Infrastructure, Data Management, Model Management and Resource Management.

MIRAL BIM Protocol is ultimately based on previous practical experiences and potential future applications that could be
beneficial for construction industry, some of the information that is found here had been cited from some of standards and
practical documents; all reference that had been used are mentioned in the last section in this document.

This protocol had been created in line with MIRAL VDC (Virtual Design & Construction) vision, MIRAL VDC vision is to be the
1st in a region to develop an intensive BIM Protocol that addresses all project needs and requirements to LCECs (Lead Content
Development & Experience Design Consultants), CDC (Concept Design Consultants), LDCs (Lead Design Consultants), CCs
(Cost Consultants), PMCs (Project Management Consultants), GCs (General Contractors) and their supply chain.

MIRAL requirements had been tested carefully in their projects which gives this protocol more reality and practicality than
others in the market. All MIRAL stakeholders were involved to develop this BIM Protocol and its requirements.

Document Control and Revisions

Date Doc/Version Author Description Title

Oct. 2021 MIR/2.5 MIRAL Senior BIM Manager MIRALBIM Protocol MIRAL Information Requirements

This document is issued for the party which commissioned it and We accept no responsibility for the consequences of this
for specific purposes connected with the above-captioned document being relied upon by any other party, or being used
project only. It should not be relied upon by any other party or for any other purpose, or containing any error or omission which
used for any other purpose. is due to an error or omission in data supplied to us by other
parties.

This document contains confidential information and

proprietary intellectual property. It should not be shown to
other parties without consent from us and from the party which
commissioned it.

MIR-EIR-NHM-V.2.5-21 Page 2 | 39
 Contents
1 Introduction: ................................................................................................................................................................. 10
1.1 Scope........................................................................................................................................................................ 11
1.2 Statement of Purpose .............................................................................................................................................. 11
1.3 Document Authority ................................................................................................................................................ 11
1.4 BIM Intent ................................................................................................................................................................ 12
1.5 Right of Reliance ...................................................................................................................................................... 12
1.6 Ownership and Use of BIM Model and Database .................................................................................................... 12
1.7 Deviations from Standards and EIRs ........................................................................................................................ 12
1.8 Relationship of BIM Requirements to other Requirements ..................................................................................... 12
1.9 Standards, Classifications and Specifications ........................................................................................................... 12
1.10 Approach ............................................................................................................................................................ 13
1.11 Applied Standards and Documents..................................................................................................................... 13
1.12 List of Appendices with Employers Responsibilities ........................................................................................... 14
1.13 RIBA POW 2020 with Employers Responsibilities ............................................................................................... 14
1.14 RIBA BIM Information Confidentiality and Non-disclosure................................................................................. 14
2 MIRAL BIM Goals & Objectives ..................................................................................................................................... 15
2.1 Introduction ............................................................................................................................................................. 15
2.2 MIRAL BIM Objectives .............................................................................................................................................. 15
2.3 Project BIM Objectives ............................................................................................................................................. 15
3 General Information ...................................................................................................................................................... 16
3.1 Project General Information .................................................................................................................................... 16
3.2 Project Location ....................................................................................................................................................... 16
3.3 Project Brief ............................................................................................................................................................. 17
4 IT Infrastructure ............................................................................................................................................................ 18
4.1 Hardware Requirements .......................................................................................................................................... 18
4.1.1 Model Authoring (MA):................................................................................................................................... 18
4.1.2 Design Review (DR): ........................................................................................................................................ 18
4.1.3 3D Coordination (3DC): ................................................................................................................................... 18
4.1.4 Quantity & Cost:.............................................................................................................................................. 18
4.1.5 Project Control & Monitor (PCM): .................................................................................................................. 18
4.1.6 Build & Commissioning (BC): .......................................................................................................................... 19
4.1.7 Facility Management (FM): ............................................................................................................................. 19
4.1.8 General Requirements (GR): ........................................................................................................................... 19
4.2 Hardware Platforms and Benchmarking .................................................................................................................. 19
4.3 Software Requirements ........................................................................................................................................... 19
4.3.1 Model Authoring (MA):................................................................................................................................... 20
4.3.2 Design Review (DR): ........................................................................................................................................ 20
4.3.3 3D Coordination (3DC): ................................................................................................................................... 21
4.3.4 Quantity & Cost ............................................................................................................................................... 21
4.3.5 Project Control & Monitor (PCM) ................................................................................................................... 22

MIR-EIR-PDR-V.00-19 P a g e 2 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

4.3.6 Build & Commissioning (BC) ........................................................................................................................... 23

4.3.7 Computer Aided Facility Management (CAFM) ............................................................................................. 25
4.4 Technology Compatibility ........................................................................................................................................ 25
4.5 Training Requirements ............................................................................................................................................. 25
5 Data Management ........................................................................................................................................................ 26
5.1 Collaboration Process .............................................................................................................................................. 26
5.1.1 Meetings Methodology: ................................................................................................................................. 26
5.2 Common Data Environment – CDE .......................................................................................................................... 27
5.2.1 Introduction .................................................................................................................................................... 27
5.2.2 Audit Trial ........................................................................................................................................................ 27
5.2.3 CDE Gates ........................................................................................................................................................ 28
5.3 Information Delivery Plan ........................................................................................................................................ 29
5.3.1 Master Information Delivery Plan (MIDP) ...................................................................................................... 29
5.3.2 Task Information Delivery Plan (TIDP) ........................................................................................................... 29
5.4 Folder Structure ....................................................................................................................................................... 29
5.5 File Formats and Sizes .............................................................................................................................................. 29
5.6 Exchange of Information – Timings & Procedures ................................................................................................... 30
5.7 Quality Control Strategy........................................................................................................................................... 30
5.8 Ownership of Data ................................................................................................................................................... 30
5.9 Level of Information Need ....................................................................................................................................... 30
5.10 BIM Audits .......................................................................................................................................................... 31
6 Model Management...................................................................................................................................................... 31
6.1 Introduction ............................................................................................................................................................. 31
6.2 Modelling Strategy and Data Segregation ............................................................................................................... 31
6.2.1 Starting View ................................................................................................................................................... 31
6.2.2 Project Browser ............................................................................................................................................... 31
6.2.3 Sheet Browser ................................................................................................................................................. 32
6.2.4 Naming Conventions ....................................................................................................................................... 32
6.3 Family/Element Creation and Contents ................................................................................................................... 34
6.4 Classification Systems .............................................................................................................................................. 35
6.5 Geospatial Information, Origin & Survey Point ........................................................................................................ 35
7 Resources Management.............................................................................................................................................. 355
7.1 Overview .................................................................................................................................................................. 35
7.2 Roles & Responsibilities (Organizational)................................................................................................................. 35
7.3 BIM Awareness Sessions – Project Team ................................................................................................................. 36
7.4 BIM Specific Competence Assessment (Appendix 10) ............................................................................................. 36
7.5 Project Deliverables ................................................................................................................................................. 36
7.6 Compliance Plan....................................................................................................................................................... 36
7.6.1 Pre-Contract BIM Execution Plan ................................................................................................................... 36
7.6.2 Post-Contract BIM Execution Plan .................................................................................................................. 37

MIR-EIR-NHM-V.2.5-21 Page 3 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

8 References..................................................................................................................................................................... 38

List of Figures
Figure 1 - Project Map ............................................................................................................................................................. 16
Figure 2 - CDE Illustration ........................................................................................................................................................ 28

List of Tables
Table 1 - Standards .................................................................................................................................................................. 13
Table 2 - Appendices with Employers Responsibilities ............................................................................................................ 14
Table 3 - RIBA POW 2020 with Employers Responsibilities ..................................................................................................... 14
Table 4 - MIRAL BIM Goals (Corporate) ................................................................................................................................... 15
Table 5 - MIRAL BIM Goals (Project) ........................................................................................................................................ 16
Table 6 - Project Information ................................................................................................................................................... 16
Table 7 - Project Location ........................................................................................................................................................ 16
Table 8 - MA Hardware Requirement ...................................................................................................................................... 18
Table 9 - DR Hardware Requirement ....................................................................................................................................... 18
Table 10 - 3DC Hardware Requirement ................................................................................................................................... 18
Table 11 - QCC Hardware Requirement ................................................................................................................................... 18
Table 12 - PCM Hardware Requirement .................................................................................................................................. 19
Table 13 - BC Hardware Requirement ..................................................................................................................................... 19
Table 14 - FM Hardware Requirement .................................................................................................................................... 19
Table 15 - GR Hardware Requirement ..................................................................................................................................... 19
Table 16 - Hardware Platforms ................................................................................................................................................ 19
Table 17 - MA Software Requirement ..................................................................................................................................... 20
Table 18 - DR Software Requirement ...................................................................................................................................... 21
Table 19 - 3DC Software Requirement .................................................................................................................................... 21
Table 20 - QCC Software Requirement .................................................................................................................................... 22
Table 21 - PCM Software Requirement ................................................................................................................................... 23
Table 22 - BC Software Requirement ....................................................................................................................................... 24
Table 23 - CAFM Software Requirement ................................................................................................................................. 25
Table 24 - Required Meetings .................................................................................................................................................. 26
Table 25 - File Formats & Sizes ................................................................................................................................................ 30
Table 26 - Information Exchange Log....................................................................................................................................... 30
Table 27 - File Naming (ex) ...................................................................................................................................................... 32
Table 28 - Ex. ............................................................................................................................................................................ 32
Table 29 - Object Naming (ex) ................................................................................................................................................. 33
Table 30 - Ex. ............................................................................................................................................................................ 33
Table 31 - Classification Systems ............................................................................................................................................. 35
Table 32 - Awareness Sessions ................................................................................................................................................ 36
Table 33 - Pre-Contract BEP Scoring Matrix ............................................................................................................................. 37

MIR-EIR-NHM-V.2.5-21 Page 4 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Abbreviations & Terminologies

Abbreviation Description

2D Two-dimensional

3D Three-dimensional

3DC 3D Coordination

4D Construction sequencing information

5D Cost information

6D Project lifecycle information (O&M information)

7D Information from sensors and building analytics

AB As-Built in MIR

ADQ Actual Digital Questions

AEC Architecture, Engineering and Construction

AIM Asset Information Model

AIR Asset Information Requirements

ARG Asset Registry

BC BIM Coordinator

BC BIM Consultant in MIR

BCF BIM Collaboration Format

BCIS Building Cost Information Services of RICS

BEP BIM Execution Plan

BIM Building Information Modelling

BMO BIM Management Office

BOM Bills of Materials

BOQ Bills of Quantities

BS British Standards

BSDD Building SMART Data Dictionary

BUA Build-up Area

CAD Computer Aided Design

CAFM Computer-Aided Facility Management

CAPEX Capital Expenditure

CC Cost Consultant

CD Concept Design

CDE Common Data Environment

MIR-EIR-NHM-V.2.5-21 Page 5 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Abbreviation Description
CIC UK Construction Industry Council

CIC BIM Protocol The Construction Industry Council Building Information Modelling Protocol

CMMS Computerized Maintenance Management System

COBie Construction Operations Building Information Exchange

CPI Construction Project Information

CPIC Construction Project Information Committee (UK)

CPIc Construction Project Information Committee

CPIx Construction Project Information Xchange

CR Clash Rendition

CS Construction Stage

CSG Constructive Solid Geometry

DD Design Development

DGN MicroStation and Intergraph file format

DR Design Review

DWF AutoCAD Design Web Format

DWG AutoCAD file format

DXF Interchange file format

EIR Employer’s Information Requirements

ERC Employer Representative Consultant

eS Electronic Snagging in MIR

FAR Floor Area Ratio

FF&E Furniture Fixture and Equipment

FM Facility Management

GC General Contractor - Main Contractor

GIS Geographic Information System

GSL Government Soft Landings

H&S Health and Safety

HVAC Heating, Ventilation, and Air Conditioning

iBIM Integrated Building Information Model, or Level 3 BIM

ICT Information and communications technology

IDM Information Delivery Manual

IDP Information Delivery Plan

IFC Issued for Construction

MIR-EIR-NHM-V.2.5-21 Page 6 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Abbreviation Description
IFC Industry Foundation Classes

IFC2x Industry Foundation Class version 2x

IFD International Framework for Dictionaries

IFT Issued for Tender

IMP Information management process

IT* Issue Tracking in MIR

IT Information Technology

ITP Inspection Test Plan

LCEC Lead Content Development & Experience Design Consultant

LDC Lead Design Consultant

LOD Level of Development

LOD Level of model detail

LOI Level of model information

LOIN Level of Information Need

MA Model Authoring

MC Main Contractor

MEP Mechanical, Electric, Plumbing Engineering

MIDI Master Information Document Index

MIDP Master Information Delivery Plan

MIR MIRAL Information Requirements

N/A Not Applicable

NCR Non-Conformance Reports

NLA Net Leasable Area

NPV Net Present Value

NRM New Rules of Measurement

NSA Net Sales Area

O&M Operation and Maintenance

OIR Organizational Information Requirements

OPEX Operating Expenditure

PAS Publicly Available Specification

PCM Project Control & Monitor

PEP Project execution plan

PIM Project information model

MIR-EIR-NHM-V.2.5-21 Page 7 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Abbreviation Description
PIMS Project Information Management System

PIP Project Implementation Plan

PIP Project implementation plan

PLQ Plain Language Questions

PM Project Manager

PMC Project Management Consultant

PMO Project Management Office

POMI Principals of Measurement (International)

PQ Pre-Qualification

QA/QC Quality Assurance, Quality Control

QCC Quantity Crosscheck in MIR

QTO Quantity Takeoff

RIBA Royal Institute of British Architects

RFI Request for Information

RFI Request for Inspection

RFP Request for Proposal

RICS Royal Institute of Chartered Surveyors

SC Sub-Contractor

SCCS Supply Chain Capability Summary

SD Schematic Design

SFCA Standard Form of Cost Analysis

SMP Standard Method and Procedure

SW Software

TBD To Be Determined

TIDP Task Information Delivery Plan

VDC Virtual Design & Construction

VO Variation Order

VPCM Virtual Project Control & Monitor

WBS Work Breakdown Structure

WI Work Inspection

WIP Work in progress

WIR Work Inspection Report

WO Work Order

MIR-EIR-NHM-V.2.5-21 Page 8 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Abbreviation Description
XML Extensible Markup Language

MIR-EIR-NHM-V.2.5-21 Page 9 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Terminology Definition
2D CAD Model File CAD file containing CAD data in two dimensions X and Y
coordinates
3D CAD Model File CAD file containing CAD data in three dimensions X, Y and Z
coordinates
BEP A document used to capture all project specific standards,
workflows and procedures.
BIM Author A term used to define a person within a specific discipline
responsible for authoring the project using the nominated BIM
authoring software.
BIM Coordinator A term used to describe the nominated person within a specific
discipline who is responsible for maintaining the BIM health and
coordination of that discipline.
BIM Manager A term used to describe a person within a specific organization
tasked with maintaining the health, vision implementation and
maintenance of BIM within that organization.
CAD File/s A collective name for files created utilizing CAD software; CAD
model, CAD container, CAD drawing file/s
Common Data Environment A collective name for a system or, systems that are connected
or, utilized to manage and govern control of data and
information while provided accessibility and collaboration
functionality
Consultant(s) or Contractor(s) Organizations contracted to the Employer/Appointing Party to
deliver project contract/Appointment requirements required to
satisfy Project Stage deliverables.
Data Files File consisting purely of coded information i.e. Binary for the use
in a device or physical machine. Also defined as an ‘Information
container’.
Deliverable A document or asset required, in a format stated in the EIR or
contract/Appointment documentation to satisfy the completion
of the requirements of the Employer’s/ Appointing Party’s
project.
Digital Asset A graphical/geometrical representation of a physical asset also
referred to within Autodesk Revit as a Family or a Type of a
Family.
Discipline A term used to identify a group of individuals that are specialists
in their field of work. For example, architects, interior designers,
mechanical engineers, structural engineers, etc.
Document The common name given to a file that is not recognized as CAD
file format. Also defined as an ‘Information container’.
Drawing A CAD or PDF rendition file containing multiple spaces where
referenced 2D CAD model file(s) are required to produce a
project drawing deliverable. Reference file(s) are scaled and
positioned within the Employer’s/ Appointing Party’s approved
border inclusive of title block information pertaining to the CAD
or PDF rendition drawing file
Level of Asset Definition (LOAD) Definition of the stages contained within the lifecycle of the
Employer’s project(s) inclusive of the associated digital asset
Level of Development (LOD) and Level of Information (LOI)
required to satisfy and inform the delivery of the relevant
project stage digital assets.
Level of Development (LOD) Definition of the graphical/geometrical detail of digital assets at
a level appropriate to the current Project Stage.

1 Introduction:
MIRAL requires all CCs/GCs/LDCs to work to the principals of BIM (Building Information Modelling) as defined by the British
Standard which is the UK implementation of EN ISO 19650-1:2018 together with BS EN ISO 19650-2:2018. (It supersedes
BS 1192:2007+A2:2016 and PAS 1192-2:2013, which are withdrawn).

MIR-EIR-NHM-V.2.5-21 Page 10 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

• The intent of this document is to provide an outline definition of Exchange Information Requirements (MIRs) to support
the implementation of Building Information Modelling (BIM) on [Project Name] Project.

• This document outlines the following to support collaborative processes and produce the information required by MIRAL
during design, construction, and handover:

1) Responsibilities
2) Requirements and Processes
3) Best Practices
4) Supporting Software Requirements
5) BIM Uses & Data Requirements
6) Project Deliverables

1.1 Scope
This document describes which BIM uses are implemented on the project and what methods, tools and standards the BIM
uses require. A BIM use is a method of applying building information modelling during a facility's lifecycle to achieve one or
more specific objectives (NBIMS 2012) (10). This document specifies the technology and process requirements for the BIM
uses, as well as the model content requirements on the project. It introduces how model data shall be delivered, specifies
the model and data management solution and defines how project teams shall collaborate by means of BIM. Finally, the BIM
organization of the project including expected roles and responsibilities is outlined.

The following BIM design disciplines shall provide models of their design and follow the EIR and the design scope/intent:

• Infrastructure and Civil

• Landscape, Earth works, & Roads
• Architectural
• Structures
• Mechanical
• Electrical
• Plumbing
• Fire Fighting
• Power and Utilities
• Audio Visual Systems
• Interior Design
• Lighting
• Vertical Transportation
• Kitchen Laundry and Waste
• Theming
• Special Systems “i.e., Security System…etc.”
This list is not limited and disciplines can be added/removed depending on each project.

1.2 Statement of Purpose

This document outlines the following to support collaborative processes and produce the information required by MIRAL
during all project stages.

The EIR (or MIR – same meaning) is an important element of Project BIM Implementation and is used to set out clearly the
required information within the Project Information Models (PIMs).

The Exchange’s Information Requirements shall be embedded within the Employer’s Project Contractual documentation
issued to a Project Consultant(s) and, or Contractor(s).

Consultant(s) and, or Contractor(s) contractually engaged by Miral shall develop in response to the EIR a contractually binding
BIM Execution Plan. Amendments to the EIR shall be reflected in the Deviation from Standards and EIRs section of the
document, after being reviewed and approved by the Programme BIM Manager appointed by Miral.

1.3 Document Authority

This document will define the requirements of different stakeholders that will become part of the project delivery team at
different stages of the development of the project. The acceptance of this document by the Consultant(s) and or
Contractor(s), confirms that the relevant supply chains personnel have read and understood its requirements.

MIR-EIR-NHM-V.2.5-21 Page 11 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

The document will provide a structure and specification for the development of the BIM Execution Plan and associated
documents and the delivery of the Project Information Model (PIM) in accordance with the Employer’s requirements and
subsequent hand back of Information to the Employer’s team.

The EIRs are applicable to the entire project team and all project-related data. Project data should be stored in a secure
manner and managed in a consistent and structured framework. Data must be protected against unauthorized access,
alteration, disclosure, and modification and managed with relevant procedures.

1.4 BIM Intent

Building Information Model (BIM) or “Model” is a parametric, computable representation of the project design developed
by the LDC and the LCEC and the construction model will be developed by the contractor (in this case only – for Project
NHM and for specific zones). As used in this BIM specification, references to Building Information Model, BIM, or the
Model, include the primary design model or models and all linked, related, affiliated or subsidiary models developed for
design, analysis, estimating, detailing, fabrication, construction, operation or maintenance of the project, or any portion or
element of the project.

1.5 Right of Reliance

The BIM Model produced by the project stakeholders associated with the Lead Content Development & Experience Design
Consultant (LCEC) will serve as the basis of design and is considered a Design Model. The model prepared by the LDC/LCEC
shall be used by [Contractor] to prepare a Construction model. This Right of Reliance pertains to all models and
applications associated with the model and associated applications.
The [Contractor] may rely on the accuracy of the model(s) prepared by the LDC/LCEC in accordance with traditional
Standard of Care provisions that apply and govern the design and construction of comparable buildings in two (2)-
dimensional design formats and methods.

Conversely, the LDC/LCEC may rely on the accuracy of the model(s) prepared by the [Contractor] in accordance with
traditional Standard of Care provisions that apply and govern the preparation of shop drawings, fabrication drawings,
sequencing and other instruments used to convey the means and methods under the control of [Contractor], its
subcontractors, consultants and other agents working on this project.

1.6 Ownership and Use of BIM Model and Database

The BIM Model is an instrument of service and is considered to be a component of Design and Construction Documents.
The [Appointing Party (Employer)] has ownership of and to all CAD files, BIM Models, and Facility Data developed for the
project, the data contained within it and all copyrights. The [Appointing Party] may make use of this data following any
deliverable. Each Model Element Author (MEA) contributing to the BIM model(s) and database agrees to provide all project
stakeholders and [Appointing Party] a non-recoverable, exclusive license to utilize any and all intellectual property
provided by each MEA contained within this BIM for the sole purpose of completing the design, construction, and other
uses as stipulated and/or implied by the executed Appointing Party/Design Consultant Agreement.

1.7 Deviations from Standards and EIRs

Any deviations from the Standards, Classifications, Specifications and EIRs must be clearly highlighted in the Request for
Proposal (RFP) and agreed on by all project stakeholders and Programme BIM Manager.

1.8 Relationship of BIM Requirements to other Requirements

To the greatest extent practicable, the BIM should describe the project as it will be designed and constructed, except for
elements that cannot be practicably modelled because of software limitations or that are smaller than elements normally
modelled on similar projects. All limitations to the extent of modeling must be identified in the BIM Execution Plan and
agreed in writing by Miral. Those project elements that are not modelled must be constructed in accordance with
supplementary design information prepared by the Contractor that has been fully coordinated with the modelled
information.

1.9 Standards, Classifications and Specifications

A BIM execution philosophy is mandated for all portfolios under the Miral’s Programme. To produce information to the
same form and quality, the below Standards and Codes associated with BIM will, therefore, form the basis of the Miral
execution strategy. Consultants and Contractors should utilize the below standards to develop their BIM execution plans
as applicable and required.

MIR-EIR-NHM-V.2.5-21 Page 12 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

BS EN ISO 19650:2018 sets out a method for managing the production, distribution, and quality of construction
information. This method includes construction information produced using CAD systems.

Uni-class is a unified classification system developed for the UK construction industry covering all sectors of the industry.
Uni-class is used for the naming of all components (content) on the MIRAL Programme. Modelled elements will be
populated with accurate Uniformat information through-out the design phase of the project and fully complete for all
elements at the close-out of the final design stage. This will allow for the successful export and identification of modelled
elements. E.g. in Revit authoring tool, the assembly code for all family types will be populated with Uniformat information.

COBie (Construction Operations Building Information Exchange) is an international standard for building data exchange. Its
most common use is in product data handover from construction to operations AM/FM (Asset Management and Facilities
Management). The COBie specifications and guidelines capture industry knowledge and best practices “used version to be
agreed with the Employer in each project”.

Geographic Information System (GIS) ISO 19115:2014 extends the value of BIM data through visualization and analysis by
importing BIM information into GIS tools. To ensure this, optimal integration and standardization of metadata must be in
place. The ISO 19115 standard is a metadata standard and defines how to describe geographical information and
associated services, including contents, spatial-temporal purchases, data quality, access, and rights to use. GIS applications
should use data format standards to store geospatial as this will enable the transfer of data between systems through
integration. The below identifies the information exchange gates:

Work in progress
The “WIP” section of the CDE is used to store unapproved information such as non-verified design data for each
organizational role such as architecture. To pass through the Approval Gate (Gate 1) a check, review and approval process
shall be carried out before being issued to the Shared area.
Shared
The “Shared” section of the CDE is used to store Information which has been approved for sharing with other organizations
to use as reference material for their own design development. When the design has been completed, the information
shall be placed for authorization in the Appointing Party (Employer) Shared Area. To pass through the Authorized Gate
(Gate 2) in the information in the Appointing Party (Employer) Shared Area, shall be authorized by Miral or their
representative.
Published
The “Published Documentation” section of the CDE shall be used to hold published information such as co-ordination and
validated design outputs for use by the total project team, e.g. production information suitable for tender or construction.
This section concludes with the Verified Gate 3 which represents the transition to “archive”.
Archived
The “Archive” section of the CDE shall store a record of the project history including all transaction and change orders.

1.10 Approach
The approach used for establishing the EIR is based on RIBA plan of work 2013 & the British Standard which is the UK
implementation of EN ISO 19650-1:2018 together with BS EN ISO 19650-2:2018.

The EIR are issued as part of the Request for Proposal (RFP) and a response from prospective bidders is required through the
means of a Pre-Contract BIM Execution Plan (BEP) that describes how the specifications and requirements are to be
implemented.

MIRAL requires a BEP prior to the award of all bidders along with their Project Implementation Plan (i.e. a Pre-Contract BEP)
as part of their proposal, regardless of their scope of work and the design phase they are involved, setting out the suppliers
proposed approach, capability, capacity and competence to meet the EIR.

This Pre-Contract BEP is then refined by the selected bidder onto a Post-Contract BEP in two weeks’ time after the award of
the appointment (contract), detailing the agreed processes and procedures.

1.11 Applied Standards and Documents

Name Category Year
ISO 19650-1: 2018 2018
Standards (BSI & ISO)
ISO 19650-2: 2018 2018
RIBA Plan of work Practicing Standards 2020

MIR-EIR-NHM-V.2.5-21 Page 13 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

NBS BIM Object Standards 2014

Table 1 - Standards

1.12 List of Appendices with Employers Responsibilities

No. Title CDC LCEC PMC LDC CC GC
Appendix 2 LDC BIM Requirements Responsible Responsible Manage Responsible Consulted Informed
Appendix 2a LCEC BIM Requirements Responsible Responsible Manage Responsible Consulted Informed
Appendix 2b CDC BIM Requirements Responsible Consulted Manage Responsible Consulted Informed
Appendix 4 CC BIM Requirements Informed Informed Manage Informed Responsible Informed
Appendix 5 GC BIM Requirements Consulted Consulted Manage Consulted Consulted Responsible
Appendix 6 PMC BIM Requirements N/A N/A Responsible N/A N/A N/A
Appendix 7 Level of Information Need Responsible Responsible Manage Responsible Informed Responsible
Appendix 10 BIM Competence Assessment Responsible Responsible Responsible Responsible Responsible Responsible
Table 2 - Appendices with Employers Responsibilities

1.13 RIBA POW 2020 with Employers Responsibilities

RIBA POW 2020 CDC LCEC PMC LDC CC GC
Stage 0: Strategic Definition N/A N/A N/A N/A N/A N/A
Stage 1: Preparation and Brief N/A N/A Manage N/A N/A N/A
Stage 2: Concept Design Responsible Responsible Manage Informed Consulted Informed
Stage 3: Spatial Coordination Consulted* Responsible Manage Responsible Consulted Informed
Stage 4: Technical Design Consulted* Responsible Manage Responsible Consulted Consulted
Stage 5: Manufacturing and
Consulted* Consulted Manage Consulted Consulted Responsible
Construction
Stage 6: Handover Consulted* Consulted Manage Consulted Consulted Responsible
Stage 7: Use Informed Informed Informed Informed Informed Consulted
Table 3 - RIBA POW 2020 with Employers Responsibilities

KEY:
Manage: Responsible for managing all tasks to ensure the compliance of requirements.
Responsible: Responsible for undertaking all tasks to ensure compliance of requirements.
Consulted: Consulted to provide input and assistance.
Informed: Informed with no need for input.
NA: Not Applicable.
*: As defined in the Scope of Services agreement.

1.14 BIM INFORMATION CONFIDENTIALITY AND NON‐DISCLOSURE

Reference is made based on the confidentially clauses of the Professional Services Agreement signed by the
Consultant/ Contractor and the non-disclosure agreement (NDA) signed by the Consultant/ Contractor for a
Miral project, the BIM design data and documentations “BIM Information” for the project including but not
limited to; all BIM related deliverables, 3d models, non-graphical data, renders, drawings, reports, and
diagrams in any stage of Miral project will be considered as a Confidential Information, where Miral is the sole
authorized entity to the ownership of these information. Any rights (including but not limited to the copyright
or the intellectual property rights or design rights) subsisting in the material and any proprietary work
contained in the material shall vest in Miral.
For the duration of the project, Miral will grant to the consultant/ contractor an access to the project’s BIM
information for the permitted project purposes. Additionally, All the involved parties under the consultant/
contractor “affiliates” shall use BIM Information solely to the limited extent necessary for the purpose, the
consultant/ contractor and their affiliates shall prevent and not allow any BIM Information to be disclosed.
The consultant/ contractor will maintain in strict confidentiality and not to present, share with, and/or disclose
to any third party or in any event any BIM information generated by the consultant/ contractor and its affiliates,
or by its representatives that contains and/or reflects the project’s BIM Information.

MIR-EIR-NHM-V.2.5-21 Page 14 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

the consultant/ contractor shall not, at any time during the term of their scope in this project and after its
completion, disclose or use any BIM deliverable “i.e. BIM deliverables, 3d models, non-graphical data, renders,
drawings, reports, and diagrams”.
Subject to the restrictions contained in the above clauses, the consultant/ contractor agrees to preserve as
Confidential Information any information learned by their teams as a result of their involvement in the BIM
implementation process in this project.
the consultant/ contractor agrees to transmit the BIM Information only to such of its representatives who need
to know the BIM Information for the sole purpose of assisting the implementation or carrying out the assignment
and who are made aware of the obligations of BIM information confidentiality.

2 MIRAL BIM Goals & Objectives

2.1 Introduction
MIRAL aims to digitize all the design & construction work through the project life cycle, also to become leader in paperless
collaboration and work environment. MIRAL vision is to minimize project impacts for all parties by depending on VDC and its
tools.
MIRAL general objectives of the VDC process is to:
• Ensure the success of construction project delivery through the use of integrated digital technologies that provide
scheduling and project management capabilities for the dynamic construction operations environment.
• Real time visualization that adds new and exciting ways for project participants to plan - by enabling all participants
the ability to see into the future, to understand the past and to know current conditions as they happen.
• Contribute to a clear communications and shared understanding amongst the entire project delivery team.
• Enable performance on a much higher level across all aspects of the delivery process, from safety, workspace
utilization and productivity, quality, and reliability, to project cost competitiveness.
• Assure on performance improvement without compromise and the typical constraining trade-offs between time,
cost, and quality.

2.2 MIRAL BIM Objectives

Objectives Priority Project Phase

Use BIM to inform the design & construction programme and to review the design at
High RIBA Stage 2>>6
key project phases to ensure compliance to programme.
Vendor information to be present in BIM, subject to vendor contractual obligations. High RIBA Stage 2>>6
Management of all project information, procedures and correspondences to be
High RIBA Stage 2>>6
through BIM environment using models and CDE.
QA/QC to ensure data integrity throughout all project phases. High RIBA Stage 2>>6
Ensure integrity of design data and value through BIM processes. High RIBA Stage 2>>6
BIM to remain as single source of truth – information to derive from BIM. High RIBA Stage 2>>6
BIM is kept up to date throughout project duration. High RIBA Stage 2>>6
Use appropriate tools and methods to address clash control and omitting it. High RIBA Stage 2>>6
To have LOD 300 at the end of IFC – project handover to contractor. High RIBA Stage 4
Information exchanges shall be in BIM. High RIBA Stage 2>>6
BIM to inform design & construction progress. High RIBA Stage 2>>6
To verify quantities for costing purposes. High RIBA Stage 3>>6
Digital site management and controlling to de conducted using BIM and CDE. High RIBA Stage 5>>6
Fabrication and drawings to be approved using BIM extractions and CDE gates. High RIBA Stage 5>>6
To have LOD 500 at the end of project – Project handover to FM. High RIBA Stage 6
Table 4 - MIRAL BIM Goals (Corporate)

2.3 Project BIM Objectives

Objectives Priority Project Phase

Project tasks and procedures should be managed through BIM environment and design
High RIBA Stage 2>>6
BIM models & progress to be totally utilized on a daily basis.
Facilitate decision making process for any changes or major issues. Medium RIBA Stage 2>>6
Clash renditions and discrepancies to be fast highlighted and resolved. High RIBA Stage 2>>6

MIR-EIR-NHM-V.2.5-21 Page 15 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Objectives Priority Project Phase

Facilitate quantity extraction/validation and drawings production. High RIBA Stage 2>>6
To have virtual models for all project disciplines and facilities. High RIBA Stage 2>>6
To enable the transfer of project data into data management during operation. High RIBA Stage 2>>6
Utilize building project data during building operations and facility management
High RIBA Stage 2>>6
activities.
To have better collaboration and communication using CDE among all project
High RIBA Stage 2>>6
stakeholders.
To have better quality for extracted data which facilitate all project works & activities. High RIBA Stage 2>>6
To have change management for all project aspects. High RIBA Stage 2>>6
To have energy analysis and sustainability consideration for better facility management
High RIBA Stage 3>>4
and preventive maintenance.
To have better visualization for all required data like analysis and constructability. High RIBA Stage 2>>6
Use VR for a better understanding of project spaces and for constructability review. Medium RIBA Stage 3>>6
Table 5 - MIRAL BIM Goals (Project)

3 General Information
3.1 Project General Information
No. Item Description
1 Employer MIRAL
2 Project Title TBA
3 Project Code TBA
4 Architect TBA
5 Civil Engineer TBA
6 MEP TBA
7 Landscape TBA
8 ID TBA
9 PMC TBA
10 Total Built Up Area TBA
11 Planned Start Date TBA
12 Planned Finish Date TBA
Table 6 - Project Information

3.2 Project Location

Project Address TBA

Project Coordinates TBA
Table 7 - Project Location

Figure 1 - Project Map

MIR-EIR-NHM-V.2.5-21 Page 16 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

3.3 Project Brief

As per Request for Proposal (RFPs) main document.

MIR-EIR-NHM-V.2.5-21 Page 17 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

4 IT Infrastructure
This section clarifies in detail all MIRAL hardware and software requirements to assure flowing and work integrity, also it
gives the freedom for the project teams to propose any compatible solutions in which final product and MIRAL VDC goals
should be achieved.
4.1 Hardware Requirements
MIRAL requires proper hardware specs to achieve its VDC goals, all bidders should propose their workstations that shall be
used in their work within MIRAL projects.

4.1.1 Model Authoring (MA):

Code Description Specifications

G.1 General Hardware shall support all model authoring processes, synchronization and collaboration.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.1.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.1.2 Display 2 screens with a minimum of 24.3”.
Table 8 - MA Hardware Requirement

4.1.2 Design Review (DR):

Code Description Specifications

G.1 General Hardware shall support all design review processes, synchronization and collaboration.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.2.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.2.2 Display 2 screens with a minimum of 24.3”.
Table 9 - DR Hardware Requirement

4.1.3 3D Coordination (3DC):

Code Description Specifications

Hardware shall support all 3d coordination processes, clash detection & discrepancies
G.1 General
resolution.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.3.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.3.2 Display 2 screens with a minimum of 24.3”.
Table 10 - 3DC Hardware Requirement

4.1.4 Quantity & Cost:

Code Description Specifications

G.1 General Hardware shall support all quantity crosscheck processes & validation.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.4.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.4.2 Display 2 screens with a minimum of 24.3”.
Table 11 - QCC Hardware Requirement

4.1.5 Project Control & Monitor (PCM):

Code Description Specifications

Hardware shall support all project control and monitor processes, animations, simulations,
G.1 General
analysis and collaboration.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.5.1 Workstation
7740x (x299) – 64 GB RAMs.
HR.5.2 Display 2 screens with a minimum of 24.3”.

MIR-EIR-NHM-V.2.5-21 Page 18 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

HR.5.3 VGA Card NVIDIA GTX Titanium or Quadro Tesla/P5000 VGA Card, 8 GB.
Table 12 - PCM Hardware Requirement

4.1.6 Build & Commissioning (BC):

Code Description Specifications

G.1 General Hardware shall support all build & commissioning processes.
Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.6.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.6.2 Display 2 screens with a minimum of 24.3”.
A proper Tablet/iPad with a minimum of 32 GB memory and 8 GB RAMs or equivalent with
HR.6.3 Tablet a durable case for site circumstances, this is for use of comparing models with as-built,
crosscheck with MEP & handing over and snagging lists.
Table 13 - BC Hardware Requirement

4.1.7 Facility Management (FM):

Code Description Specifications

G.1 General Hardware shall support all facility management processes.

Strong workstation (i.e. HP Z series, Dell T series, equivalent) with a minimum of Core i7
HR.7.1 Workstation
7740x (x299) – 32 GB RAMs.
HR.7.2 Display 2 screens with a minimum of 24.3”.
A proper Tablet/iPad with a minimum of 32 GB memory and 8 GB RAMs or equivalent with
HR.7.3 Tablet a durable case for site circumstances, this is for use of checking defects, periodical checks &
incidents.
Table 14 - FM Hardware Requirement

4.1.8 General Requirements (GR):

Code Description Specifications

G.1 General Hardware shall support all build & commissioning processes.
SMART Board, Projector with white sheet, Smart TV Touch, for the use of workshop
HR.8.1 Smart screen
meeting & collaboration.
Printers/copy Adequate number of printers should be provided only for the most-paper users like
HR.8.2
machines secretaries & DCs, central printers & copy machines also to be provided.
A minimum of 1 color plotter to be provided to support colored printouts in case of
HR.8.3 Plotters
coordinated MEP drawings and sophisticated drawings.
Table 15 - GR Hardware Requirement

4.2 Hardware Platforms and Benchmarking

This section highlights on the hardware platforms that should be used in general to support the work collaboration and
communication between MIRAL & CC/GC/LDC/LCEC.

Code Description Specifications

A powerful server should be fixed at the project office with a capability of

HP.1.1 Server
download/upload data in a maximum speed from the shared folder.
A high-speed internet should be provided to MIRAL & project team to facilitate work
HP.1.2 Internet
collaboration.
Table 16 - Hardware Platforms

4.3 Software Requirements

This section is about all software that will be used during whole project life cycle and about which platforms should be
utilized. All bidders should propose their IT infrastructure plan and propose for any equivalent/alternative software with
illustrations.

MIR-EIR-NHM-V.2.5-21 Page 19 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

4.3.1 Model Authoring (MA):

Code Tool as example Description

Used for preliminary sketches, single line diagrams, export CAD from Revit for
SR.1.1 Autodesk AutoCAD
printouts.
Used as a modelling tool in the project, Landscape add-in should be installed for
SR.1.2 Autodesk Revit
purpose of Landscape modelling.
SR.1.3 Autodesk 3D Civil Used as a modelling tool for infrastructure utilities, roads & bridges.
SR.1.4 Trimble Tekla Used as a modelling tool for steel structure or any steel buildings.
SR.1.5 Trimble Sketchup Used as a sketching tool for concept designs and illustrations.
Used for Revit collaboration along the teams.
Is accessible from mobile devices and tablets.
SR.1.6 Autodesk BIM 360 Design
Work sharing should be through it within project teams.
MIRAL should have access anytime to all the WIP models.
• The software used for model authoring shall provide all the 3D
modelling capability, adding new attributes, linking different models
and formats, exporting/importing IFC formats and assuring on
achieving all needed model management requirements.
• Distributed teams need to be able to access models created by the
SR.1.7 General requirements
software for model authoring over the internet.
• The software shall support most of publicly add-ins to help/facilitate
model authoring.
• The software shall support multi-location work (cloud-based) and not
be attached to a specific server in a specific location.
Table 17 - MA Software Requirement

4.3.2 Design Review (DR):

Code Tool as example Description

SR.2.1 Autodesk Revit Provide visual checks and review.

SR.2.2 Autodesk 3D Civil Provide visual checks and review.
Used as a clash detection tool, provide tabulated reports about the clashes
SR.2.3 Autodesk Navisworks
locations and their attributes and support intensive visual checks.
Used for Revit collaboration along the teams.
Is accessible from mobile devices and tablets.
SR.2.4 Autodesk BIM 360 Design
Work sharing should be through it within project teams.
MIRAL should have access anytime to all the WIP models.
• The software shall provide viewing capability on mobile devices as
specified.
• Distributed teams need to be able to access models created by the
software for design review over the internet.
• The software for design review can save comments and markups in
the 3D model that were collected through the design review.
• The software shall provide capability to communicate the issues
registered in the software. The software for design review provides
functionality that can be used to distribute comments. This can either
be done through a file that can be distributed, or by uploading it on a
SR.2.5 General Requirements
web-based platform.
• A desirable feature is that the status, (e.g. issued, approved, rejected),
can be tracked within the software for design review.
• The software for design review provides functionality that can
measure distance on screen in the model that is being reviewed by
snapping to elements in it.
• The software shall provide capability to access object properties when
clicking on an object.
• The software shall provide secure and authenticated access to up-to-
date, multidisciplinary BIM projects.

MIR-EIR-NHM-V.2.5-21 Page 20 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Code Tool as example Description

• If the software is standalone, this requirement can be handled by

authentication of the operation system and the data management
solution. If the software is cloud-based, authentication needs to be
provided and access rights are granted dependent on the role.
Table 18 - DR Software Requirement

4.3.3 3D Coordination (3DC):

Code Tool as example Description

Autodesk Navisworks Used as a coordination software to view, comment & markup the clashes and
SR.3.1
Manage coordination issues.
Should be used with a predefined rule set to highlight on design compliance,
SR.3.2 Solibri Model Checker
codes, and regulations.
• Used for Revit collaboration along the teams.
• Is accessible from mobile devices and tablets.
SR.3.3 Autodesk BIM 360 Design • Work sharing should be through it within project teams.
• MIRAL should have access anytime to all the WIP models.
• Collaboration between all stakeholders should be under this platform.
• The software shall be able to detect, identify and manage clashes. The
software can automatically detect clashes between elements in
different 3D models. Identifying clashes is achieved by highlighting
them in the 3D model. Clashes are managed by saving them in the
model and being able to track their status.
• The software shall provide capability to create clash reports. The
software can create a report which gives the opportunity to explore
details of the clash results or to share that data with others. It shall be
able to include an image and the status of the clash, (e.g. new, active,
reviewed, approved and resolved) and export the report in XML, HTML
and TXT format.
• The software shall provide capability to import and export clash tests.
The software shall be able to import and export clash tests in XML
SR.3.4 General requirements
format that contains the settings, names and selected items to save
time setting up clashes across projects.
• When clicking on an object in the software for 3D coordination it
shows the properties attached to it.
• Distributed teams need to be able to access models created by the
software for 3D coordination remotely over the internet.
• The software shall integrate multiple 3D models and multi-format data
and aggregate it into one model, a single model to be published as a
distributable file. This can either be done through a file that can be
distributed, or by uploading it on a web-based platform.
• The software shall provide capability to group objects, (e.g. based on
properties or naming convention) to clash-test subsets of the model.
The software can be set up to filter and group for certain objects.
Table 19 - 3DC Software Requirement

4.3.4 Quantity & Cost

Code Tool as example Description

• Provides a simple interface for the extraction of dimensions from BIM

files.
• Can be tied with a costing library to provide instant budget or valuation
SR.4.1 General requirements of buildings.
• Provide cost planning options.
• Ability to work on building projects separately and merge the work into
one building project.

MIR-EIR-NHM-V.2.5-21 Page 21 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Code Tool as example Description

• Supports standard drawing formats (DWG, DXF and DWF).

• Supports (PDF., cBIM, IFC, etc.) formats.
• Supports electronic dimension extraction from paper drawings using
scanning technology.
• Ability to add views and import dimension information from BIM
Models.
• Full measurement capability including area, length and count modes.
• Dimensions can be broken down into zones (representing functional
areas/levels/units etc. or stages of construction).
• Fully supports scaled drawings (including separate X and Y scales) and
Quantification
SR 4.2 allows calibration of scanned drawings.
requirements
• Ability to add measurements during session.
• Quick and easy measurements of reinforced steel using measurements
from standard reinforced steel drawings.
• Export of measurements to Microsoft Excel.
• Overlay comparisons between two drawings/models in a building, (e.g.
electrical and lighting drawings).
• Revisioning system for drawings/models.
• Tied in with the revisioning capability of BIM Models, drawing
comparison mode graphically shows the changes between the models’
revisions.
• Provide automatic cost plan generation from dimension information.
• Provide full data import capability from systems such as enterprise
resource planning (ERPs).
• Ability to 'tweak' cost plan elements, rates, quantities etc.
• Backwards linking and display. (For a quantity in a workbook cell, the
option exists to display the referenced dimension on the drawing).
• Provide free form hierarchical spreadsheet capability (workbooks).
• Provide full workbook templates capability with live links to dimension
groups and rate libraries.
• Rate libraries and price lists can be manually entered or imported.
SR 4.3 Costing requirements • Standard reports such as Elemental Summary, Bill of Quantities, and
Trade Breakup amongst others can be created for cost plans.
• Export of costing information to Excel.
• Enhanced revisioning system for workbooks including ability to create a
new workbook based on the previous revision.
• Rates can be broken down using a spreadsheet per rate which can link
back to other rate libraries/price lists.
• Offer the possibility of fully customizable reports.
• Ability to do a workbook reorder (sort) based on code. For example,
convert from Elemental to Trade etc.
• Offer automatic synchronization with BIM models.
Table 20 - QCC Software Requirement

4.3.5 Project Control & Monitor (PCM)

Code Tool as example Description

• Main 4D simulation software should be integrated with project

primavera schedule.
SR.5.1 Synchro
• Daily, weekly & monthly report should be extracted and to be in line
with Synchro data.
• To be used for safety simulations, erections simulation, Logistics and
SR.5.2 Fuzor
planning.
• Can be used also for Cost estimation/control along with its capability
SR.5.3 CostX of quantity extraction.

MIR-EIR-NHM-V.2.5-21 Page 22 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Code Tool as example Description

• Cash flow should be demonstrated and integrated with software used

for VPCM.
• Payment validation should be linked with the software and integrated
with the electronic WIR.
• Any plan mitigations, updates and modifications should be applied on
VPCM software pack.
• Cost comparison between versions and submission should be carried
out on VPCM software pack.
• The software shall provide the ability to integrate or import Primavera
SR.5.4 General requirements
P6, MS Project or to import a project schedule in csv-format.
• The software shall provide capability to group objects, (e.g. based on
properties or naming convention). The software shall provide ability to
filter and group certain objects to enable easier selection of objects in
the model.
• The software shall provide ability to assign an activity with different
task types, (e.g. construct, demolish or temporary).
• The software should provide ability to run a simulation of a workflow
or sequence.
Table 21 - PCM Software Requirement

4.3.6 Build & Commissioning (BC)

Code Description

The software shall enable the user to record issues that could affect project quality, health and safety,
environment, or scheduled delivery. The software shall enable the user to record the following information:
• A description of the issue.
• A responsible organization for resolution or the issue.
• A location of the recorded issue.
• The issue type:
SR.6.1 • NCR (Non-conformance report).
• Site observation notice.
• Safety non-conformance.
• Safety Incident.
• Material inspection non-conformance.
• Design query.
• Housekeeping.
The software shall enable the user to manage issues. The software shall:
• Display the resolution status of the issue, (e.g. open, work complete, closed).
• Enable the user to update the status of an issue which will automatically notify the responsible
SR.6.2
organization.
• Enable the user to filter issues based on: resolution status, location, company, issue type as well as
text-based search on issue description.
The software shall be able to add photographic evidence to an issue or inspection. The software shall enable
SR.6.3 the user to add a photograph or other file document to the issue or inspection record in order to provide a
better understanding and visual context to an issue or inspection.
The software shall enable the user to record and manage quality, and health and safety inspection checklists.
The software shall enable the user to record the following information on a checklist:
• A record of Pass, Fail, or Not Applicable, against each check point test on the checklist.
SR.6.4 • Location of the check that has been conducted.
• Additional descriptive information.
• Assign an issue to a responsible organization when a check point test registers as a fail.
• Photographic evidence.
The software shall enable the user to add markups. The software shall enable the user to add markups to a
picture or document attached to an issue or inspection. Markups shall include the ability to add lines, arrows,
SR.6.5
shapes and textual graphics or user selected color to the picture of document. The user shall also be able to
take measurements by snapping to a surface or point in the model.

MIR-EIR-NHM-V.2.5-21 Page 23 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Code Description

The software shall enable 3D model viewing capability. The software shall enable the mobile field tablet user
SR.6.6
to navigate a 3D model.
The software shall enable viewing of 2D drawings and documents. The software shall enable the user to view
SR.6.7
2D drawings and documents in the following file formats: PDF, DOCX, and XLSX via an Apple iPad tablet.
The software shall enable the user to modify and add object properties as specified. The Site management
application shall support the update of the following ‘as-built’ properties for objects required for operational
management of the building:
• Manufacturer.
• Manufacturer Contact.
SR.6.8 • Model.
• Serial number.
• Installation date.
• Warranty start date.
• Expected life.
• Location.
The software shall provide email notification of new issues and status change on existing issues to the relevant
SR.6.9 parties. Immediate email notification is valuable in reducing time to resolve an issue so that it doesn’t affect
project delivery quality and schedule.
The software shall provide an administrative interface to enable configuration of the system. The software shall
provide an administrative interface to enable the following:
• Management of users and responsible organizations.
SR.6.10
• Roll based access to the system and its functional capability.
• Configuration of issue types and root causes.
• Configuration of Quality Assessment/Quality Control-QA/QC safety checklists.
The software shall provide role-based access to the Site management tool. The specified roles to include:
• Contractor.
• Subcontractor.
• Architect.
SR.6.11
• Engineer.
• Owner.
• Inspector.
Role-based access shall be provided to enable/restrict functional access to the system based on user role.
The software shall provide reporting capability. The software shall enable users to create reports as follows:
• A list of issues including description, location, responsible company and status which can be
grouped by company, location or issue type. This list shall allow for an option to include photos,
documents, and markups.
• A summary of issue status including average time to close and overall project trend.
SR.6.12
• A list of QA/QC checklists with responses, comments and any issues generated as a result of the
inspection. This list shall allow for an option to include drawings or documents.
• A summary of safety activities including number of inspections conducted and their conformance.
The reporting function shall enable the user to create filtered reports based on resolution status, location,
company, and issue/checklist type.
The software shall enable the user to create automated scheduled, (e.g. daily, weekly, monthly) reports. The
SR.6.13
software shall enable scheduled reports in PDF or XLS format to be sent to recipients via email.
The software shall provide an iPad tablet interface to the Site management tool. The software shall enable Site
management via an iPad that does not require network connectivity to function.
SR.6.14
The software shall enable work to be uploaded and synchronized when a WIFI is in range or a 3G/4G Mobile
connection is available.
The software shall provide a desktop web-based interface to the Site management tool. The software shall
SR.6.15
enable site management via a web portal for office-based staff and any user not using an iPad.
Table 22 - BC Software Requirement

MIR-EIR-NHM-V.2.5-21 Page 24 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

4.3.7 Computer Aided Facility Management (CAFM)

Code Description

• Manual entry of data from drawings, manufacturers documents, and so on into computerized
maintenance management system (CMMS) files. This is tedious, error prone, and significantly
delays the use of CMMS systems after turnover of the building. It cannot be seriously considered for
SR.7.1 modern buildings of moderate and larger size.
• Transfer of data from a BIM model to a CMMS system using some standard format such as COBie.
• Direct integration of the BIM and the facility management system.
• Use of a middleware system that integrates with both the BIM authoring system and the CMMS.
SR.7.2 Ability of full BIM integration with any platform (Autodesk, Bentley, Trimble, etc.).
Operation & Maintenance (O&M) and all related elements/equipment data should be embedded inside the
SR.7.3
software and to be available offline.
Software should enable the following:
• General inspections scheduler.
• Room inspections scheduler.
• Facility scheduler.
• Integration with Building Management System (BMS) and sensor control.
• Event scheduler.
SR.7.4 • GIS solutions for infrastructure assets.
• BIM interface.
• Mobile capability.
• Asset management.
• Maintenance schedule.
• Move & space management.
• Real estate & leasing management.
Table 23 - CAFM Software Requirement

4.4 Technology Compatibility

Any compatible software/hardware that could meet MIRAL requirements should be communicated with the responsible
team (TBD) and to arrange Proof of Concept (POC) for the project team.

4.5 Training Requirements

Any software shall be used in MIRAL project. All the bidders should detail their training plan in case of awarding to satisfy
and achieve all MIRAL BIM needs and requirements.

MIRAL may call for a training for any software used in the project, Consultant/Contractor shall ensure on the training
commencement not more than two weeks from the training request.

MIRAL is not responsible for any training requirements or technology providing for external parties in the project.

Find below the main training fields needed:

• Software trainings
• Any technology requirements
• Any other/s TBD according to MIRAL needs

MIR-EIR-NHM-V.2.5-21 Page 25 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

5 Data Management
5.1 Collaboration Process
The purpose of this section is to define how, where and when project information will be shared. It will highlight also on how
the project team should communicate with each other.

The consultant, contractor or subcontractor should identify in detailed processes and procedures how project data and
information will be exchanged and shared in each project stage/phase. All collaboration processes should be created and
carried out through an approved CDE which will be addressed in section 5.2.

5.1.1 Meetings Methodology:

Meetings are to be conducted periodically and whenever needed, below are some mandatory meetings and not limited to:
Meeting Name Occurrence Participants Location

BIM Initiation Meeting (Kick Off) Once TBA TBA

BEP Demonstration As requested TBA TBA
BIM Workshop Meeting As requested TBA TBA
BIM Coordination Meeting Bi-monthly TBA TBA
BIM Validation Meeting As requested TBA TBA
Table 24 - Required Meetings

5.1.1.1 BIM Initiation Meeting

Meeting to establish the principles of BIM adoption, scope and ambition on the proposed project and to setup the post
contract-award BXP. Establish when and where future meetings will be held. The purpose of the meeting is to:
• Determine the BIM goals and aspiration of the project
• Define the BIM Execution Plan
Agenda: The agenda for the BIM kick-off meeting can be based on the headings covered in the Project BIM Execution Plan
as a basic measure.
• Purpose of meeting
• Introductions
• Project Information
• Project team
• Project goals / BIM objectives
• Model standards
• Software & Compatibility
• Meetings
• Model organization
• Spatial coordination
• Project Key Performance indicator (KPI)
• Supporting documentation
• Any other business
• Next Meeting schedule

5.1.1.2 BIM Execution Plan Demonstration

After the initial kick-off meeting, the organizations should clearly understand who will be responsible for the defined tasks,
and in what sequences the BIM Uses will be executed. The responsible party for the Level One map should clearly document
and distribute it to the project team for review prior to the following meeting. Each responsible party for the specified BIM
Uses should also draft their workflow prior to the Design Project BIM Execution Process meeting.

5.1.1.3 BIM Workshop Meeting

Meeting to track the progress of BIM implementation on the project in the context of the BXP. This meeting should be used
as a mechanism to identify forthcoming challenges and agree a proactive solution. Agenda:
• BIM processes
• Data requirements within the project model requirements within the project CDE requirements
• Models
• Common Data Environment
• Next Meeting

MIR-EIR-NHM-V.2.5-21 Page 26 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

5.1.1.4 BIM Coordination Meeting

• After the Design Project BIM Execution Process meeting, the team must focus on developing the information
exchanges. Each responsible party for an exchange should take the lead in developing the information exchanges.
• The authors of the information exchange will need to coordinate with the information receivers to ensure that
they have developed consistent information exchanges with minimal inconsistencies to discuss.
• The team members should also prepare for the discussions regarding infrastructure requirements which will occur
in Meeting Three. Team members should compile examples of typical methods that they have used or wish to use
on the project to share with the team. Once the meetings are complete, the Project BIM Execution Plan should be
distributed to all parties and approved as appropriate for the project and contracting structure.
• Team members should ensure that the plan monitoring and updating procedure is implemented into the project
controls system.
• Meeting to review and allocate responsibility to clashes found during clash detection process undertaken by the
BIM Validator. Agenda:
o Clash investigation
o Next meeting

5.1.1.5 BIM Validation Meeting

Meeting to review and discuss deficiencies in model geometry and data identified during the model validation checks
undertaken by the BIM Validator. Agenda:
• Modelling progress, where everyone is and what they have been doing in terms of modelling
• Go through outstanding actions from previous minutes
• Collaboration
• Technical, dealing with any technical issues the team are experiencing
• Scopes and contracts, finalizing and reviewing progress against the BXP (BIM Execution Plan)
• Validation, go through checks and assign responsibility and timescales to resolve issues
• Ascertaining whether the design teams need any additional support going forward to help them compete required
tasks
• Next Meeting

5.2 Common Data Environment – CDE

5.2.1 Introduction
MIRAL will provide the CDE (Aconex + BIM 360) to its project team members as needed, all project team members shall be
obliged with MIRAL CDE and its specifications and requirements.

The Common Data Environment (CDE) is the place where to hold all project information, data, processes & procedures. It
has access rights for all CC/GC/LDC/LCEC, it acts as a single source of truth at any time of project, it enables to control and
monitor data changes, history and revisions.
The CDE should contain:
• Graphical Data (models, drawings, PDF’s, IFC, photographs, renders, videos, …etc.)
• Non-Graphical Data (Schedules, data-bases, COBie, …etc.)
• Documents (Contracts, minutes, correspondance, request for information (RFI’s), brief, Specifications, reports,
BOQ, Inspection Plans & Reports, Commissioning Certificates, Product data Sheets, user O&M Manuals, …etc.).
5.2.2 Audit Trial
An audit trial is a standard requirement for all documentation regardless of whether external quality assurance systems
require it. All files that are shared with third parties should have a record of when, who and what reason they were shared.
Any subsequent revisions should be tracked also ensuring that all recipients of the previous version understand that the
previous version is superseded.

Any requirements that were mentioned in Appendices 2,3,4,5 & 6 BIM Requirement should have a trial procedure with start
and end point, this should be carried out to assure on the process/task flow without any interference or discrepancies.

MIR-EIR-NHM-V.2.5-21 Page 27 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

5.2.3 CDE Gates

Figure 2 - CDE Illustration

Work in Progress
The “WIP” section of the CDE is used to store unapproved information such as non-verified design data for each
organizational role such as architecture. To pass through the Approval Gate (Gate 1) a check, review and approval process
shall be carried out before being issue to the Shared area.
Shared
The “Shared” section of the CDE is used to store Information which has been approved for sharing with other organizations
to use as reference material for their own design development. When the design has been completed, the information shall
be placed for authorization in the Appointing Party (Employer) Shared Area. To pass through the Authorized Gate (Gate 2) in
the information in the Appointing Party Shared Area, shall be authorized by MIRAL or their representative.
Published
The “Published Documentation” section of the CDE shall be used to hold published information such as co-ordination and
validated design outputs for use by the total project team, e.g. production information suitable for tender or construction.
This section concludes with the Verified Gate 3 which represents the transition to “archive”.
Archived
The “Archive” section of the CDE shall store a record of the project history including all transaction and change orders.

MIR-EIR-NHM-V.2.5-21 Page 28 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

5.3 Information Delivery Plan

5.3.1 Master Information Delivery Plan (MIDP)
The Master Information Delivery Plan (MIDP) is a primary plan which is used to manage the delivery of information during
the project lifecycle. It should be developed by the project delivery manager in collaboration with the task team managers
and then used by the project delivery manager to assist in the delivery of project information during the project. It should
be addressed on Post-contract BIM Execution Plan.

Information deliverables which may be listed in the MIDP include (but are not limited to):
• Models
• Drawings or renditions
• Specifications
• Equipment schedules
• Room data sheets
• Procurement packages
• Reports
• Schedules

5.3.2 Task Information Delivery Plan (TIDP)

The Task Information Delivery Plan (TIDP), is a federated list of information about deliverables by each task, including format,
date and responsibilities.

It is the responsibility of each task team manager to compile their own TIDP which then assist in the development of the
MIDP. Each task shall have a corresponding milestone that aligns to the overall design and construction programme, taking
into consideration any sequencing requirements to produce information.

Each task shall also detail the responsibility of each appointed party (supplier)’s information and show how responsibility for
the preparation of project documents transfer from one team to another.

5.4 Folder Structure

The defined structure shall follow the principles of British Standard which is the UK implementation of EN ISO 19650-
1:2018 together with BS EN ISO 19650-2:2018: ‘Work In Progress (WIP)’, ‘Shared’, ‘Published’ and ‘Archived’ segregation of
data within a designated set of folders.

When a project comprises of several separate elements such as multiple buildings, zones or areas, the BIM structure shall
be maintained within a set of designated sub-folders representing the various project elements.

All project data shall be held within the standard project folder structure located on central network servers or appropriate
Document Management technology. This includes all WIP components or assemblies.

All bidders shall submit their folder structure and highlight how the data will be segregated within it, also to be highlighted
on the main 4 gates for CDE as per EN ISO 19650-1/2:2018.

5.5 File Formats and Sizes

All BIM models should be divided and segregated in a proper way with alignment of project site zones and levels.
The maximum file size that should be used is 300 MB, also it depends on LOD & LOI embedded within the models.

Type Examples Format Version Size

BEP Docx, Pdf. N/A

Documents TBA
Reports Docx, Pdf, Xlsx N/A
Design drawings 10 mb
Shop drawings Native file format, 10 mb
2D drawings TBA
Illustrations & Pdf, DWFx
10mb
sketches
Design model Native file format, 250 mb
3D Models TBA
Construction model DWFx, IFC 250 mb

MIR-EIR-NHM-V.2.5-21 Page 29 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

Type Examples Format Version Size

Asset model 300 mb

Federated model Native file format, 500 mb
DWFx, IFC
Coordination model Native file format, 400 mb
DWFx, IFC
Quantity takeoff Design Qty model Native file format, TBA 250 mb
TBA
Construction Qty Native file format, 250 mb
model TBA
Schedules Xlxs N/A
Project Control 4D model Native file format, TBA 250 mb
TBA
5D model Native file format, 250 mb
TBA
Site management model Logistics planning Native file format, TBA 100 mb
TBA
Crane movement Native file format, 100 mb
TBA
Table 25 - File Formats & Sizes

5.6 Exchange of Information – Timings & Procedures

This should be specific for each project and to be addressed in Post-contract BIM Execution Plan.

Due
Model/ File
Information File File Date or
Frequency File/ Software Format Exchange
Exchange Sender Receiver Start
Document Type
Date
TBD TBD TBD TBD TBD TBD TBD TBD TBD
Table 26 - Information Exchange Log

Contractor/Consultant shall document all the information exchange and file transfers that will occur on the project.
The schedule of deliverables is subjected to change and shall be updated based on coordination. Validation meetings which
shall be agreed by Project BIM Manager.

5.7 Quality Control Strategy

Contractor/Consultant are requested to submit/attach their Quality Control Plan/Strategy along with their BIM Execution
Plan to show their process of how the manual & the automated quality control procedures “checklists & compliance Model
checker” will be performed.

5.8 Ownership of Data

Please refer to the main RFP document.

5.9 Level of Information Need

According to BS EN 17412:2020 Level of Information Need LOIN is used to determine both the level of geometry detail, level
of Information and the documentation for any given model element at an agreed project work stage, it is structured to:

• Geometrical Information that is responsible for the graphical representation of the modeled element in which
the following will be taken into consideration:
• Details: from simple to detailed.
• Dimensionality: 1D, 2D and/or 3D
• Location: Absolute or relative
• Appearance: Monochromatic, Materialistic, Realistic, etc.
• Parametric Behavior: Explicit, Constructive and/or Parametric
• Alphanumerical Information that is responsible for the information and data that shall be associated with
modeled elements, the following shall be taken into consideration:

MIR-EIR-NHM-V.2.5-21 Page 30 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

• The identification of the element: name, type, classification, index, etc.

• Information content that shall contain all the data which will be shared from suppliers and project
parties.
• Documentations that shall be embedded within the modeled elements during the handover phase for the sake
of the facility management and operation, these documents are and not limited to:
• Reports.
• Manuals.
• Data Sheets
• Schedules
• Photos.
• Catalogues.
• Etc.
All project team members Consultants/Contractors shall follow Appendix 7, Level of Information Need during their BIM
Execution.

5.10 BIM Audits

The Project Manager and/or Agent of Record (AOR) may, at any time during the Appointment period and without notice,
perform audits on the Project BIM models and associated processes to determine the accuracy of the Project BIM
information and adherence to the Contractor’s approved/current BIM Plan.

The Contractor is obliged to facilitate these reviews and resolve any issues which the Project Manager or Agent of Record
(AOR) find to be non-compliant.

6 Model Management
6.1 Introduction
The Model Management formalizes the level of information need (level of development-LOD) required at each project stage
/ data drop and defines which discipline is responsible to produce what project output and when. Model Management
establishes an overall design level of maturity that does not apply to individual design elements but to the delivery.

Information mentioned below is to be used as a minimum, all bidders should submit their modelling strategy, model handing-
over and model management plan.

6.2 Modelling Strategy and Data Segregation

The main purpose of segregating models is driven by performance. (Models shall be split by building, levels and disciplines)
and according to project size and complexity.
Models shall consist of objects that resemble the building elements they represent at the given level of detail.
Rooms and spaces shall be modelled as objects.
The Lead Consultant/Contractor shall account for the model strategy and data segregation in the Pre-Contract BEP taking
the MIDP and TIDP into account as well as requirements of the design team, (e.g. software to analyze a MEP system might
require an unbroken system).

6.2.1 Starting View

A starting view/splash screen should be created for all WIP BIM models. The starting view should state the following:
• Project Information (location, name, title, built up area (BUA), etc.)
• Consultant/Contractor name
• Model discipline
• Project/sheet browser definitions
• Message center for updates and publishing dates
• Any notes that could be important and crucial
Consultant/Contractor should submit a sample of starting view with Post-contract BIM Execution Plan.

6.2.2 Project Browser

Project browser shall be segregated according to the project phases and CDE gates, at the same coordination views should
be created for the purpose of disciplines coordination and collaboration. Consultant and Contractor shall provide their
browser categorization structure in BEP.

MIR-EIR-NHM-V.2.5-21 Page 31 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

6.2.3 Sheet Browser

Sheet browser shall follow MIDP & TIDP that will be submitted with BEP.

6.2.4 Naming Conventions

Object and attribute naming conventions ensure that data can be reused for different applications in different software
platforms. Consistent naming of attributes ensures reuse of data, automation of tasks, rule-based data extraction and the
identification of the same object in different applications. All spaces shall be named consistently in all discipline models.

6.2.4.1 General Naming Conventions

• Use only letters A-Z, hyphen, underscore and numbers 0-9 for all fields.
• All fields shall be separated by a hyphen character “-”. Do NOT use spaces.
• Within a field, either Camel Case or an underscore “_” shall be used instead of a space to separate words.
• A single period character "." shall be used to separate the file name from the extension. This character should not
be used anywhere else in the file name.
• The file extension shall not be amended or deleted.
• An “XX” shall be used if the file does not refer a single specific zone or level.
• The scheme for zone and level sub-division shall be agreed with the other project professionals at the outset and
defined in the Project BIM Execution Plan document.
• Elements where a naming convention is not explicitly defined by this Standard shall adopt the naming convention
of existing elements and prefix with a 3-character abbreviation to identify corporate author.
6.2.4.2 Model File Naming (Example)
Naming of model files shall be based on EN ISO 19650:2018. For full compliance, recommended character restrictions should
be adopted.
For a more accessible and simpler naming convention, all fields are optional. To maintain compliance, any variations should
be clearly stated in the Project BIM Execution Plan.

1 2 3 4 5 6 7

Project Originator Zone/System Level Type Role Revision

WBH SPML CZ1 L02 3DC AR R00

Table 27 - File Naming (ex)

• Field 1: Project
An abbreviated code or number identifying the project.
• Field 2: Originator Code (Recommended 3 characters)
An abbreviated code identifying the originating stakeholder.
• Field 3: Zone/System (Recommended 2 characters)
Identifier of which building, area, phase or zone of the project the model file relates to if the project is sub-divided by zones.
• Field 4: Level (Recommended 2 characters)
Identifier of which level, or group of levels, the model file relates to if the project is sub-divided by levels.
• Field 5: Type (Recommended 2 characters)
Document type, which will be M3 for 3D model files.
• Field 6: Role (Recommended 2 characters)
2-character discipline identifier code
• Field 7: Revision (Recommended 3 characters)

EN ISO 19650:2018 Examples:

Model File Name Description

FTR-ACM-XX-XX-M3-S-
Acme structures model for School project at Stage E – no zones or segregation of floors.
School_Stage_E.rvt
102-ACM-Z1-XX-M3-ME-
Acme Building Services model for job 102, Zone 1 all levels.
School.dgn
G322-DoorInternal-826-P Internal door of 826mm wide, intended for plan use at up to 1:50 scale.
Table 28 - Ex.

MIR-EIR-NHM-V.2.5-21 Page 32 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

6.2.4.3 Objects (Example)

The naming of spaces and objects shall follow the NBS BIM Object Standard: Section 5 (1), or similar equivalent standard.
The consultant/contractor shall provide their naming conventions matrix for all model elements to facilitate work
categorization and filtering. All BIM model elements should follow the implemented matrix during all project stages and
phases.
1 2 3 4 5 6

Role Classification Description Originator Size/item code Type

WBH SPML CZ1 L02 3DC AR

Table 29 - Object Naming (ex)

• Field 1: Role (Optional)

Identifies the owner of the object. Normally this would be omitted as objects are generic; ownership is inferred by
file/layer containing the object.

• Field 2: Classification
Uniclass code to classify the object. This is positioned at the start of the name to allow easier listing of all specific
object types. E.g. all furniture regardless of manufacturer.

Note: where the classification is applied as a property of an object, it can be omitted from the object name.
However, the ability to search and organize objects should be carefully considered before dropping this field. The
classification must be included in either the object name or its metadata.

• Field 3: Description
Camel Case description based on Uniclass/AEC descriptions, e.g. ExternalFinishCladdingConcrete.

• Field 4: Originator/Manufacturer (Optional)

Used if a proprietary object is required to represent specific manufacturer.

• Field 5: Size / Originator item code (Optional)

Used to further define the object type by specifying dimensions or the manufacturer’s item code. The latter can be
used to help link objects directly to a specification, brochure or procurement.

• Field 6: Type
This field uses a code to describe the intended “view” of the object.
Examples:
Object File Name Description

Brick wall, 102.5mm wide, 3-dimensional, grade suitable for up to 1:50 models, (e.g.
G25-WallBrick-102.5-M3
no brick bond defined or wall ties).
Generic internal door, not specifically sized, 3-dimensional, grade for schematic
DoorInternal-M3 modelling purposes of ~1:200.
Classification included as a property of the object.
G322-DoorInternal-826-P Internal door of 826mm wide, intended for plan use at up to 1:50 scale.
Table 30 - Ex.

6.2.4.4 Parameters and Attributes

The naming of attributes shall follow the NBS BIM Object Standard: Section 2.4 and 5.1, or similar equivalent standard.
Accordingly, the bidder is to provide a list of attributes with their agreed naming as part of the Pre-Contract BEP. Parameters,
or object properties, should be named in a consistent and logical manner to aid clarity and usability. Unique names should
always be used.

6.2.4.5 Model Contents

All model contents as and not limited to (worksets, views, levels, filters, system families, loadable families, nominations, etc.)
should follow a proper nomination structure such as The NBS to have a better categorization and filtering options.

6.2.4.6 Sheet Naming

Sheet naming shall be based on the document and drawing numbering protocols established for the project. These names
automatically match the text as it appears in the title block and any schedules.

MIR-EIR-NHM-V.2.5-21 Page 33 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

6.3 Family/Element Creation and Contents

For a proper file management and family creation, important steps and conditions should be followed while creating families
and loaded to BIM models:
• Have no warnings or exceptions
• Have intuitive and neat parameters
• Include standard types or type catalogs
• Contain Uniform Resource Locator (URL) parameters
• Have the right amount of data
• Have data with thoughtful organization
• Include materials
• Differentiate appropriately between Type and Instance Parameters
• Be of minimal file size
• Appropriately consider the Level of Detail (LOD) – as per the model will be loaded into
• Include shared parameters
• Include helpful options specific to the scenario
• Be modelled in a version of Revit from a few years ago
• Be placed under an appropriate category
• Not some other file type dropped into Revit
• Can be complex, but not complicated
• Contain all appropriate parameters as per appendix 7, Level of Information Need

MIR-EIR-NHM-V.2.5-21 Page 34 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

6.4 Classification Systems

Classification systems are to be mapped/implemented with all applicable project elements and all international and MIRAL
codes:

No. Project BIM Uses Standards/codes

MIRAL WBS
1 Construction Schedules
Activity ID
MIRAL CBS
2 Cost Information NRM – RICS code
POMI
NRM – RICS code
3 Quantifications POMI Standards
POMI
Uniformat Class
4 Elements Coding – Design Phase CSI code
NBS Code
Uniformat Class
5 Elements Coding – Construction Phase CSI code
NBS code
COBie
6 Elements Coding – Assets
MIRAL Assets code
Uniformat
7 Design Stages Information
MIRAL Asset code
Table 31 - Classification Systems

6.5 Geospatial Information, Origin & Survey Point

The purpose of this section is to define requirements for the common coordinate system for all BIM data. A coordinate
origin/system of 3 dimensions (X, Y, Z) is to be used to place graphical models, for example Ordnance Survey locators, with
respect to an agreed origin. Using the same coordinate system, avoids having to move and transpose models when federating
them, e.g. for 3D Coordination.

MIRAL requires that all models use an agreed coordinate system. All models shall overlay one another without having to
apply any additional relocation or conversion activities. The coordinate system shall be agreed upon and documented in the
BEP.

7 Resources Management
This section describes the roles and responsibilities in relation to BIM on Darwin. Bidders must provide a proposed
Organizational Chart for their BIM Teams along with CVs and roles and responsibilities in their Pre-Contract BEP.

In case that Consultant/Contractor outsourced some/all of their BIM work, this shall be mentioned clearly in the Pre-contract
BIM Execution Plan, compliance assessment should be carried out also for the outsourced BIM companies.

7.1 Overview
Information Requirements specify the minimum requirements and specifications for BIM on Darwin. The requirements are
authorized by MIRAL BIM lead, supported by the MIRAL BIM Committee which will review/support the implementation of
BIM on the project.
The Lead Consultant and later the Main Contractor will lead the BIM application by conducting and leading the BIM uses,
and update the Post-Contract BEP and MIDP/TIDPs. The Lead Consultant, Cost Consultant, Main Contractor, as well as the
tier 3 suppliers, all need to participate in BIM by contributing to the Post-Contract BEP, providing models and conducting
BIM use related activities as specified in this EIR document.

7.2 Roles & Responsibilities (Organizational)

Bidders must include their BIM team in an organizational level, Bidders are requested to provide their expected BIM team
for Darwin and to define the roles and responsibilities for each team member.

MIR-EIR-NHM-V.2.5-21 Page 35 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

7.3 BIM Awareness Sessions – Project Team

Awareness sessions are to be conducted and to be separated from BIM Meetings (section 5.1.1), awareness sessions will be
conducted by Contractor, Consultant and/or third party if needed.

Awareness Session Occurrence Participants Demonstrator Location

General BIM Awareness Once TBA TBA TBA

BIM uses across the project Once TBA TBA TBA
BIM Common Data Environment Once TBA TBA TBA
Site Management Platform As requested, TBA TBA TBA
Collaboration Platform As requested, TBA TBA TBA
VR/AR As requested, TBA TBA TBA
iPad usage for BIM collaboration/site manage As requested, TBA TBA TBA
Table 32 - Awareness Sessions

7.4 BIM Specific Competence Assessment (Appendix 10)

The bidder’s submission shall account for their organizations’ as well as their Consultants’ competences and experiences
related to:
• BIM capability and experience
• Evidence of BIM execution planning
• Confirmation of BIM applications used
• Details of BIM workload and resourcing
• Total number of BIM resources (details and curriculum vitae)

Assessment forms will be sent with bidding documents at time of bidding (Appendix 10).

7.5 Project Deliverables

Each (LCEC, LDC, CC, GC & PMC) are responsible for their project deliverables that were mentioned in appendences attached
with EIR/MIR.

All project deliverables for Master Information and Task Information shall be filled in Appendix 8, Information Delivery Plan.

7.6 Compliance Plan

7.6.1 Pre-Contract BIM Execution Plan
Before award of the appointment all bidders must provide a Pre-Contract BEP in response to the requirements mentioned
in this document.
Failure to do so will result in providing a zero score in the Tender Assessment. The Pre-Contract BEP enables MIRAL to
determine if the requirements within the EIR are achievable, reasonable and allows for adjustment and negotiation of the
supply chain’s capabilities if necessary. It shall demonstrate the bidder’s proposed approach to BIM as well as his capability
and capacity to meet the EIR.

At this stage, bidders are advised to use the attached template for Pre-Contract BEP, otherwise bidders could use their BEP
template which will follow the scoring matrix.

Below is the scoring matrix:

EIR
Section Requirements

Bidders acknowledge on the document scope and include all needed disciplines to be implemented
1.1
within BIM

1.2 Bidders submitted their Pre-contract BEP

1.3 Bidders addressed their understanding and knowledge about the standards that shall be implemented

MIR-EIR-NHM-V.2.5-21 Page 36 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

2.0 Bidders showed their capability to achieve MIRAL BIM Goals

4.1 Bidders submitted their IT Infrastructure proposal and hardware are to be used during project execution

Bidders submitted their full knowledge and capability of the software that are to be used during project
4.3 design/execution, bidders to submit any compatible software that could be equivalent for what MIRAL
proposed

4.5 Bidders acknowledged about the training requirements and addressed their training plan

5.1 Bidders confirmed their adherence to collaboration process and meetings schedules

Bidders acknowledged their full awareness and understanding of CDE and demonstrated their capability
5.2 of managing it and managing all documentation, processes and procedures through CDE

5.2.2 Bidders confirmed their willing to run a trial for any correspondences through CDE

Bidders acknowledged their full awareness about Information Delivery Plan and how it will be processed
5.3 through (MIDP & TIDP)

5.5 Bidders confirmed their adherence to file sizes and formats

5.7 Bidders demonstrated their Quality Control Plan (for Manual and automated procedures)

6.2 Bidders demonstrated their plan for model management, model handing over plan and segregation

6.3 Bidders acknowledged their full awareness and following for family creation guidelines

6.4 Bidders acknowledged their full awareness and following for industry classification

Bidders submitted their BIM organization chart and their proposed Project BIM Team along with CVs
7.2
and the proposed durations for each one of them in the project
Bidders Confirmed that they will give all awareness sessions needed according to project requirement
7.3
and needs
Appendix 2, Bidders confirmed their full capability to implement BIM uses and illustrate their capabilities by case
Section 2 studies
Appendix 2, Bidders illustrated their way of management for design requirements using BIM, showing their best
Section 2 ways of implementation and putting their knowledge to MIRAL BIM Goals (Corporate & Projects)

Appendix 2, Bidders illustrated their capability of implementing all BIM processes are to be using during the project
Section 2 execution, showing examples and case studies will be a plus
Table 33 - Pre-Contract BEP Scoring Matrix

7.6.2 Post-Contract BIM Execution Plan

In case of award Consultants/Contractors should submit a full detailed Post-contract BEP in which all EIR should be addressed
and highlighted accordingly in 2 weeks-time from the date of signing the contract.

MIR-EIR-NHM-V.2.5-21 Page 37 | 39
 MIRAL Information Requirements
Project NHM- Abu Dhabi

8 References
1- BIM Committee AEC UK BIM Protocol. Implementing UK BIM Standards for the Architectural, Engineering and Construction
industry. [Online] V.2.2.1, June 2015 [Cited June 23, 2019]
https://aecuk.files.wordpress.com/2015/06/aecukbimtechnologyprotocol-v2-1-1-201506022.pdf

2- British Standards. PAS 1192-2 Specification. [Online] [Cited: 02 June 2019.]

http://shop.bsigroup.com/en/forms/PASs/PAS-1192-2/.

3- Autodesk. BIM Transformation Services: Customer Stories. Autodesk Consulting. [Online] 2018. [Cited: 15
May 2019.]
http://www.autodesk.com/services-support/consulting/bim/case-studies.

4- RIBA, Royal Institute of British Architects. RIBA Plan of Work [Online] 2013 / 2020, [Cited 28 April 2019]
https://www.architecture.com/-/media/gathercontent/riba-plan-of-work/additional-
documents/ribaplanofwork2013overviewfinalpdf.pdf

5- RIBA, Royal Institute of British Architects. BIM-RIBA overlay [Online] May 2012, [Cited 03 May 2019]
https://www.architecture.com/-/media/gathercontent/riba-plan-of-work/additional-
documents/ribaplanofwork2013overviewfinalpdf.pdf

6- Autodesk. AEC products specifications & description. [Online] May 2019. [Cited 14 May 2019]
https://www.autodesk.com/products

7- Chuck Eastman, BIM Handbook 3rd Edition. August 2018, [Cited 28 May 2019]
https://www.amazon.com/BIM-Handbook-Information-Designers-Contractors/dp/1119287537

8- Building and Construction Authority, Singapore, Singapore BIM Guide V2. [Online] August 2013, [Cited 04 May 2019]
https://www.corenet.gov.sg/media/586132/Singapore-BIM-Guide_V2.pdf

9- RIAI, Royal Institute of Architects of Ireland, RIAI BIM Pack. [Online] 2019, [Cited 15 June 2019]
https://www.riai.ie/uploads/files/RIAI_BIM_Pack_2019.pdf

10- NBS, National BIM Standards, Knowledge Section. [Online] 2019, [Cited 9 June 2019]
https://www.thenbs.com/knowledge

11- CIC, Construction Industry Council, BIM Protocol 2nd Edition. [Online] 2018, [Cited 27 April 2019]
http://cic.org.uk/admin/resources/bim-protocol-2nd-edition-2.pdf

12- RICS, Royal Institute of Chartered Surveyors, BIM for Cost Managers: requirements from BIM model 1 st edition. [Online]
August 2015, [Cited 30 June 2019]
https://www.rics.org/mena/upholding-professional-standards/sector-standards/construction/bim-for-cost-managers-
requirements-from-the-bim-model/

13- Charles Pankow Foundation, Project Execution Planning V.2.0. [Online] April 2010, [Cited 30 April 2019]
https://www.engr.psu.esu/bim/PxP

14- British Standards. EN ISO 19650-1/2:2018. [Online]

https://www.bsigroup.com/en-AE/iso-19650-BIM/

MIR-EIR-NHM-V.2.5-21 Page 38 | 39