Schedule 20

SCHEDULE 20
DIGITAL DATA DELIVERY
1. General Overiew:
The Digital Data Delivery Requirements prepared by The Employer is to define the level
of information that will be required by The Employer from all stakeholders for the
development of the project and for the operation of completed built assets.
The Employers’ Digital Data Delivery Requirements were developed mainly based on the
UK Standard documents. Also, International standards had been engaged within a specific
area like ISO and NBIMS.
The Employer requires all project supply chain to develop the work undertaken for the
project to achieve a partial BIM Level 3 maturity as industry-standard best practice.
Achieving BIM Maturity Level 2 as per the UK standard is a must with the application of
ISO 19650 released Standards and IDM delivery.
BIM and CIM (Building Information Modelling and City Information Modelling) are the
processes for creating and managing electronic object-oriented information on a
construction project across the project lifecycle. The object-orientated information is a
digital description of a project asset.
The intent of this schedule is to provide an outline definition of requirements to support

the implementation of Building Information Modelling and Management (BIM),
Infrastructure Information Modeling and Management (IIM) and Digital Delivery using
the up to date technology within all The Employer Projects. The contractor is required to
describe how the specifications of this schedule are to be met through the means of a Pre-
Contract BIM Execution Plan (BEP) and the details will be included within the Post-
Contract BIM Execution Plan (BEP).
The Employer requires a Pre-Contract BEP prior to the award of all contractors as part of
their proposal, regardless of scope and project phase they are involved with. The Pre-
Contract BEP is prepared by the contractors to demonstrate the approach, capability,
capacity, and competence to meet the Employer Digital Data Delivery Requirements. The
contractor has the full responsibility to ensure their sub-contractors follow the
requirements set in this schedule. The document will be part of the Contractor evaluation
criteria.
Each contractor must read this section in conjunction with their scope of work when
developing their Pre-Contract BEP. All the contractors shall use the Employer template
for the Pre-Contract BEP, the same applies to the Post-Contract BEP.
The Employer requires that the Information provided by the contractor to serve the
operations of the facility and to support the facility operators and the Employer to
anticipate the costs of operations. Full registration of assets required to support accurate
auditing and reporting as identified within COBie deliverable. Also, native files of the
information models by way of reference, federation or direct information exchange.
This schedule should be considered for use to support information provided for further
contractor appointments and will define requirements for deliverables.
Page 407 of 489
Construction Contract for Egames Arena Contractor
Qiddiya Investment Company (as Employer)
[·] (as Contractor)
CC Ref: [•] / AS&H Ref: [·]
No part of this schedule should be construed as preventing the Contractors, Specialist
Subcontracts and Specialist Suppliers from sharing their respective models at any time and
in any format if this is to be helpful to project progress and co-ordination.
This schedule shall be read in conjunction with all digital standard documents and
templates published by The Employer along with the S.O.S. for a specific project.
The delivery will be based on the requirements in this schedule, S.O.S. and based on the
Employer Digital Delivery Standards. The standards will be shared after the contract
awarding to the chosen contractor.
The Geographic Information System (GIS) Data Submission Standards are developed to
provide standards and guidelines to all developers – general engineering contractors – to
ensure compatibility with The Employer’ GIS database. Implementation of these standards
will facilitate GIS data integration with the existing The Employer GIS database.
The Employer provides a GIS data model, a Data Dictionary, a GIS Template, and a
Quality Assurance Checklist that will facilitate the work and speed up the production
process. The Employer expects all developers to start from these templates and use the QC
tools as a first-level quality control before the submission of the packages. This is applied
for BIM, IIM and GIS deliverables.
1.1 The Employer Organizational Digital Data Requirements
The Employer -as an organization- digital data requirements are part of the Information
Delivery and Management Process. So, all the deliverables shall match the requirements
to achieve the goals. This shall be reviewed and updated for each handing over process
between different projects involved stakeholders.
BIM/IIM Digital Models Management process is initiated for creating and managing
electronic object-oriented information on an AECO industry related project across its
lifecycle. The object-orientated information is a digital description of a building asset.
These models draw on information assembled collaboratively by stakeholders and will be
updated continuously in the project lifecycle. Creating a digital building information model
enables stakeholders to optimize activities, resulting in a greater whole life value for the
asset.
All the contractors shall comply with the Employer requirements specified in this schedule
to ensure the success of the digital asset. The below describes The Employer strategic
priorities:
· The Employer Projects delivery shall be with high quality to achieve high-performance
model assets.
· Efficient visual communication of the design intent as the project develops.
· Support evaluation of design iterations and improves clarification raised at The

Employer stage reviews.
· Earlier and more efficient reporting of developing design information allowing key
changes to the Project Information Models (PIM) to be made earlier, at less cost.
Page 408 of 489

· Utilize the building information modeling for simulations and analysis that allow for
design optimization and improve the performance of the design.
· Improved consistency and accuracy of design information, understand and evaluate

design options and solutions. Assuring the concept of Integrated Project Development.
· Modeling the asset to support operational decision making. Identify the expiry of
warranty periods as an example. Also, Determining the end of an asset’s economic life.
· Improved multidisciplinary design coordination and reduced variation costs during

construction. Fewer problems caused by design, coordination and construction errors.
· The use of BIM for better decision making by The Employer by optimizing and
controlling the project program.
· Improved cost certainty and predictability.
· Visual communication and optimization of construction phases and sequencing.
· Improved health and safety on-site and during operation.
· Utilize Models and information to support the operation and maintenance of the
facility.
· Improve the efficiency of the operation and maintenance using the Assets Information
Models (AIM).
· Understand the progress and optimize the construction process, utilizing beneficial
objectives on control of construction costs.
· Quality tracking of the final physical conditions of the building.
· Efficiently aid in the maintenance and operation of the facility and its assets through a
bi-directional management system.
· Efficiently manage, track and evaluate the performance and efficiency of the whole
development through a Smart City operating system.
· Locate all the data with The Employer Digital Platform as a single source of truth for
the city-data.
Contractors are expected to clearly stipulate their ability to implement BIM uses for their
scope of work including the proposed non-traditional process and deliverables associated
with the delivery of these information requirements.
1.2 Data Ownership and Reuse
The Employer owns all computerized and digital models, information, submissions, data
drops, documents, deliverables, reports, drawings, extracts, specifications…. etc.
contained within the digital development for the models and the implementation on the
Page 409 of 489

projects including all its associated copyrights. This term will include and be applied to all
project supply chain stakeholders as well as their Subs.
1.3 Terms, Definitions, Abbreviations, and Acronyms
Refer to QIC Digital Style Book for more details about this part.
2. Standards Applied and Protocols
To ensure an efficient and unified digital delivery approach and compliance with the
Digital Data Delivery Schedule and S.O.S, the following standards and protocols shall be
applied within different projects:
Standard Description
ISO 19650-1:2018 Information management using building information modeling - Part 1:
Concepts and principles
ISO 19650-2:2018 Information management using building information modeling – Part 2:
Delivery phase of the assets
ISO 19650-3:2019 Information management using building information modeling. Part 3:
Operational phase of assets
ISO 19650-4:2021 Information management using building information modeling. Part 4:
Fulfilling the Employer’s information exchange requirements using COBie.
Code of practice
PAS 1192-6:2018 Specification for collaborative sharing and use of structured health and safety
information using BIM
BS 7000-4:2013 Design management systems. Guide to managing design in construction
BS 8536-1:2015 Briefing for design and construction – Part1: Code of practice for facilities
management (Buildings infrastructure)
BS 8541-1:2012 Library objects for architecture, engineering, and construction – Part 1:
Identification and classification - Code of practice
Recommended 2D symbols of building elements for use in building
information modeling
BS 8541-3: 2012 Library objects for architecture, engineering, and construction – Part 3: Shape
and measurement. Code of practice
BS 8541-4: 2012 Library objects for architecture, engineering, and construction – Part 4:
Attributes for specification and assessment - Code of practice
Assemblies – Code of practice
BS 8541-6:2015 Library objects for architecture, engineering, and construction – Part 6: Product
and facility declarations – Code of practice
PAS 91:2013 Construction pre-qualification questionnaires
BIP 2207 Building information management. A standard framework and guide to BS
1192
Page 410 of 489

CIC CIC BIM Protocol, Best Practice Guide for Professional Indemnity Insurance
when using BIM, Outline Scope of Service for the Role of Information
Management
ISO 29481-1:2016 Building information models - Information delivery manual - Part 1:
Methodology and format
ISO 29481-2:2012 Building information models - Information delivery manual - Part 2:
Interaction framework
ISO 29481-3 Building information models - Information delivery manual - Part 3: Model
view definitions
ISO 16739-1:2018 Industry Foundation Classes (IFC) for data sharing in the construction and
facility management industries - Part 1: Data schema
CPIX Protocol (Pre-Contract BEP, Post Contract BEP, BIM, Resources and IT
Assessment)
AEC AEC UK BIM Protocol Guidelines and AEC UK BIM Protocol for BIM
Execution Plan
The Contractor shall provide the work based on the below table which is showing the
applied standards for each subject in compliance with the Employer standards and
requirements:
Applied Standards
M= Mandatory/R= Recommended Application
Standards
Object Naming
Project Stages
Classification
Collaboration
File Naming
Contracts
Guidance
Costing
COBie
MIDP
MDS
extraction
Drawing
ISO 19650-1:2018 R R R R
ISO 19650-2:2018 R R R
ISO 19650-3:2019 R R R
BS 1192-4:2014 M
Industry Standards
PAS 1192-6:2018 M
BS 7000-4:2013 M M M M
BS 8536-1:2015 M M
BS 8541-1:2012 M M
BS 8541-2:2011 M M
BS 8541-3: 2012 M M
BS 8541-4: 2012 M M
BS 8541-5:2015 M M
BS 8541-6:2015 M M
Page 411 of 489

BIP 2207 M
COBie-UK 2012 M M
Master Format 2016/Uniformat R R R R
2010/NRM1,2,3
ISO 29481-1:2016 R
ISO 29481-2:2012 R
ISO 29481-3 R
ISO 16739-1:2018 R
CIC R
CPIX R R
UK BIM Framework M M M M M M M M M M M M
QIC_CBS Classification System M M M M
QIC_WBS Classification System M M
QIC_FABS (Fixed Assets M M M
Breakdown Structure)
Classification
QIC_ATC (Assets Tagging M M
Criteria)
QIC_Aconex Project M M M M M M M M
Configuration
QIC_Information Management M M M M M M M
Guidelines
The Employer Standards
QIC_Digital Data Delivery M M M M M M

Schedule
QIC_Digital Style Book M M M M M M M M M M
QIC_Post-Contract BIM M M M M M M M M
Execution Plan Template
QIC_QA/QC Checklist Templates M
QIC_Clash Detection Matrix M
Templates
QIC_Revit/Civil 3D Templates M M M
QIC_MDS Template M M M M
QIC_MIDP Template M M M M M
QIC_RACI Matrix Template M M M
QIC_PDT Templates M M
QIC_GIS Standards and M M M
Templates
QIC_Information Management M M M M
Guidelines
Page 412 of 489

3. Project Software Platform and File Formats
The software platforms and version used during the delivery of this project shall be
identified clearly in the Pre-Contract and Post-Contract BEP’s based on each project nature
and its approval with the Digital and Visual Information Management representatives. The
general software platforms and version requested by the Employer to be in use during this
project and shall be followed by the contractors are:
Activity BIM Authoring Tool/Software Version

Project Common Data Environment (CDE) Autodesk BIM 360 Cloud
Design/Coordinate
Professional BIM Buildings Services and Autodesk Revit Latest
General Drawings Production (Architecture, Version
Structure, MEP, Piping, Others)
Professional BIM External Services (Roads, Autodesk Revit/Civil 3D Latest
earthworks, Civil, Survey, Utilities, Area Version
Development, Others)
Structural Detailing Tekla Products TBD
Plant Design TBD V8i
Coordination, Clash Detection, and Visual Autodesk Navisworks Manage Latest
Check Version
Code and Integrity Compliance Check Solibri Model Checker TBD
Electronic Document Management System Aconex TBD
4D Construction Simulation Fuzor TBD
5D Cost Management Prism TBD
5D Cost Management RIB Itwo TBD
Energy and Environmental Evaluation Autodesk Insight TBD
COBie Report MS Excel TBD
Point Clouds Autodesk Recap Latest
Version
Static Images Autodesk Revit/Civil 3D Latest
Version
Virtual fly/walkthrough Autodesk Revit/Civil 3D Latest
Version
Overall Site Visualization and Aggregation Autodesk InfraWorks Latest
Version
Visualization Autodesk 3D Max/Maya Latest
Version
Page 413 of 489

Fabrication and Elements Creation Autodesk Inventor Latest
Version
Specifications e-SPECS TBD
Details of information exchange requirements are set out in the “data exchange format”
section in this schedule. Contractors shall configure their attribute data in their models to
align with the data exchange format. The Post-Contract BEP to outline requirements to
achieve the desired project exchange data format.
The contractor shall create the model(s) using suitable BIM authoring software
applications that allow the assembly of data-rich models and the production and checking
of coordinated models and documentation. The Employer may request software versions
to be updated at any point during the project. Any update or change in software versions
must be agreed by The Employer and the project team. The contractor can propose an
alternative to the specified software, then the proposal must meet all technical requirements
needed to meet the BIM uses outlined in this schedule and selected in the Pre-Contract
BEP. Each contractor is responsible for its supply chain to have the requested software no.
of licenses and professional personnel to work with it.
The contractor must have or must obtain at its own cost, sufficient software licenses, and
computer hardware to adequately perform the services required. Software license
compliance audits will be conducted by The Employer, its team and Licensors to check
the use of an organization’s BIM software assets used for the project. Compliance audits
might lead to the identification of over-deployment of software and/or the presence of
pirated or cracked software. If such a breach is detected, it should be rectified immediately
while bearing all costs to remediate this non-compliance.
Software license compliance audits will be conducted at the contractor and its
subcontractors, and other agents working on this project once per year unless information
reasonably indicating that licensees are out of compliance is received.
The file formats can be used within all the projects of Al Qiddiya City:
Format Description Format Description

3DMLW 3D Mark-up Language for Web JPEG or Joint Photographic Experts
files JPG Group (image format)
3DS Native Autodesk 3DS Studio file NWC Native Autodesk
format Navisworks file format
3DXML Native Dassault Systems file NWD Native Autodesk
format Navisworks file format
BCF BIM collaboration format NWF Native Autodesk
NavisWorks file format
BMP Bitmap (image format) ODBC Open database connectivity
CUBE Native Datacubist simplebim file PDF Portable document format
format)
DGN Native MicroStation design file PLY Polygon file format
format
Page 414 of 489
DWG Native Autodesk AutoCAD file PNG Portable network graphics
format image format
DWF Design Web Format native RCP Native Autodesk recap File
Autodesk file format Format
FBX A file format developed by RCS Native Autodesk recap file
Kaydara and now owned by Format
Autodesk
gbXML Green Building XML RFA Native Autodesk Revit
family file format
GIF Graphics Interchange format RVT Native Autodesk Revit
(image format) project file format
IAM Native Autodesk Inventor RTE Native Autodesk Revit
assembly file format template file format
IDE Native Autodesk Inventor SDNF Steel Detailing Neutral
Features file format Format
IDW Native Autodesk Inventor drawing STL Stereolithography or
file format Standard Tessellation
IFC Industry Foundation Classes STP language
The standard for the
Exchange of Product model
data
IPN Native Autodesk Inventor TIFF Tagged Image file format
presentation file format (image format)
JIF JPEG Interchange Format (image VRML Virtual reality modeling
format) language
4. Project Data Exchange Formats
Project information data exchange should be provided through an Electronic Document

Management System (EDMS) and a central exchange solution, a common data
environment (CDE). Shared information format, frequency, and responsibility between
contributors and The Employer should be defined and understood by all stakeholders. Pre-
Contract BEP shall describe in detail how the exchange methodology and frequency of
exchange is executed. This is subject to the agreement with The Employer and approval
for the Post-Contract BEP.
The table below shows an example of the exchange formats. For each information
exchange, the information will be required in the following formats:
Activity RVT DWG PDF IFC DGN NWF XLSX NWD
Design
Models
Coordination
Models
Site Survey
Drawings
Page 415 of 489

Schedules or
spreadsheets
Record
Model
COBie
Spreadsheets
Aggregated
Model
Federated
Models
5. Hardware Requirements and System Performance
The Contractor shall ensure that the hardware allocated for the Employer project supports
all the activities and applications used for the development of the project throughout the
project lifecycle covering the required scope.
The contractor shall ensure that the hardware and system performance can support all
analyses that serve the intended BIM Uses for the project. The contractors are also
responsible for its supply chain network to have the required capacity and capability for
the hardware to cover the scope.
Purchasing the required hardware is the responsibility of the contractor and its supply
chain, not The Employer.
Detailing all the existing and future hardware capability shall be done with thin the Post-
Contract BEP and digital supply chain assessment criteria.
The following hardware requirements shall support and facilitate the BIM uses agreed on
and defined in the Pre-Contract BEP.
BIM Use Specification

Design Shall support design authoring and the software manufacturer’s recommended system
Authoring requirements. The hardware shall have adequate disk storage suitable for design
authoring.
Design Shall support design reviews with a projector or screen to facilitate collaborative
Reviews coordination.
3D Co- Shall support collaborative 3D coordination using a projector or screen for
ordination collaborative 3D coordination. The hardware shall support cloud-based coordination
software allocated for the Common Data Environment (CDE) and facilitate a suitable
internet connection speed that shall meet the software manufacturers' requirements.
Phase Shall support phase planning and construction sequencing processes. The hardware
Planning shall support the software manufacturer’s recommended system requirements and
have adequate disk storage.
Page 416 of 489

Site Shall support site management applications and others, such as mobile.
Managemen
t
Cost Shall support quantity cost estimating and take-off processes. The hardware shall
Estimating support the software manufacturer’s recommended system requirements and have
adequate disk storage.
Record Shall support record modeling to depict an accurate representation of the physical
Modelling conditions, environment, and assets of a facility. The software should allow for the
culmination of all the BIM Modeling throughout the project, including linking
Operation, Maintenance, and Asset data to the As-Built model (created from the
Design, Construction, 4D Coordination Models, and Subcontractor Fabrication
Models) to deliver a record model to the owner or facility manager.
Asset Shall support an organized management system which is bi-directionally linked to a
Managemen record model to efficiently aid in the maintenance and operation of a facility and its
t assets. These assets, consisting of the physical building, systems, surrounding
environment, and equipment, must be maintained, upgraded, and operated at an
efficiency that will satisfy both the owner and users in a cost-effective manner.
Sustainabilit Shall support a process in which a BIM project is evaluated based on LEED or other
y Evaluation sustainable criteria. This process should occur during all stages of a facility's life
including planning, design, construction, and operation.
6. Training
The Employer is not responsible to provide technology training in regard to BIM authoring
tools used by the contractor or its supply chain. The contractor is requested to detail
training and support processes that they will provide to satisfy the Digital Data delivery
requirements within the Post-Contract BEP.
The contractor shall provide adequate staff/resources to meet The Employer expectations
set out in this schedule. The contractor shall be clear regarding the capability and the
capacity within the supply chain digital assessment criteria. Purchasing the licenses no. of
the software is the responsibility of the contractor and its supply chain, not The Employer.
Awareness sessions can be shared in conduction between both the contractor and the
Employer to make sure the proper understanding of the requested workflows, process…….
This can be done at any project stage/Phase and The Employer has the full authorization
to do it.
The Employer has the right at any stage of the project to request training on software
proposed by the contractor and used during project delivery for handover, model setup,
web portals, dashboards or any other purposes.
7. BIM Uses
This section contains the list of BIM uses selected by The Employer and tailored to satisfy
the project’s needs.
Page 417 of 489

All contractors shall provide a detailed process map in the Post-Contract BEP for each
BIM Use which had been requested by the Employer in the S.O.S. and as per the contractor
suggestion for the project benefits, the same shall be submitted for the Employer approval.
The below figure is a sample for guidance purposes, the contractor shall comply with the
same structure.
Each contractor shall include the Process Maps with the proper Information Exchange
either its internal or external exchanges through the Post-Contract BEP as IDM
(Information Delivery Manual) to assure the proper implementation for those selected BIM
uses for the Project Benefits.
BIM Uses
Handover & Closeout

Preparation &
Developed Design
Construction
Technical Design
Pre-Concept
Concept Design
Design
Brief
In Use
01 3D Design Coordination ● ● ●
02 Construction Coordination ● ● ●
03 Existing Conditions Modelling ● ● ● ● ● ● ● ●
04 Visualization ● ● ● ● ● ●
05 Record Model ●
06 Phase Planning & 4D Sequencing ● ● ● ● ● ●
07 Cost Estimation & 5D Modeling ● ● ● ● ● ● ● ●
08 Design Authoring ● ● ● ●
09 Design Reviews ● ● ● ●
10 Virtual Reality Mockups ● ● ●
11 Programming ● ● ●
12 Site Analysis and Management ● ● ●
13 Acoustic Analysis ● ● ●
14 Code Validation ● ● ●
15 Sustainability Evaluation ● ● ● ●
16 Site Utilization Planning ● ●
17 Digital Fabrication ● ●
18 Hazard Identification ● ●
19 3D Control & Planning ●
20 Structural Analysis ● ● ●
21 Lighting Analysis ● ● ●
22 Energy Analysis ● ● ●
23 Mechanical Analysis ● ● ●
24 Maintenance Scheduling ●
25 Building Performance Analysis ●
26 Asset Management ●
27 Space Management/Tracking ●
28 Disaster Planning ●
29 Design Management and Control ● ● ●
30 Site Security ● ● ● ●
31 Data Classification ● ● ● ● ● ●
32 Drawings (sheets) Creation ● ● ● ●
Page 418 of 489

The details for each BIM use process, attributes, requirements will be detailed within the
Digital Style Book.
There are mandatory BIM uses and shall be delivered with all the projects. Also, there will
be a specific BIM uses for each different project.
The Mandatory BIM Uses: Design Authoring, 3D Design Coordination, Phase Planning &
4D Sequencing, Virtual Reality Mockups, Construction Coordination, Existing Conditions
Modelling, Visualization, Asset Management, Record Model, Design Reviews, Data
Classification, Drawings (sheets) Creation, Sustainability Evaluation, Digital Fabrication
-if applicable- and Cost Estimation & 5D Modeling.
8. Delivery Strategy
The Employer tends to utilize the latest technologies in the AECO industry among all
stages of the project deliveries. This includes the Design stage by utilizing digital models
for early evaluation of the deliveries and decision making. Therefore, contractors are
requested to provide a digital model for their designs and handover stages.
The Contractor shall deliver for each project a federated Project Information Model (PIM)
in Design and Handover Phases and Asset Information Model (AIM) at the Handover
phase as specified in this section.
Asset information shall be derived as per BS 1192-4:2014 Collaborative production of

information. Fulfilling The Employer’s information exchange requirements using COBie.
(CoP) and 3D industry foundation classes (IFC4). The Employer requires the proposal to
be developed and documented in the building information modeling execution plan (Post-
Contract BEP) setting out how best to deliver asset information into the operational
management system.
Reference document, which will be part of the asset management strategy to identify data,
geometry and associated documentation required:
• COBie requirement matrix
• Attributes and parameter requirement matrix
• Model development specification (MDS)
All commissioning information should also be included to develop a full auditable

database of asset information.
The main contractor should also provide a strategy for ensuring information can be
accessed efficiently during operations.
The contractor shall be informed that all the drawings and project documents shall be
extracted from the models unless it is agreed with The Employer and documented in Pre-
Contract and Post-Contract BEP’s and approved by The Employer. This should comply
with all the project milestones gates/stages.
Page 419 of 489

8.1 Collaboration and Meetings
As a collaboration, coordination and communication are the main key pillars to achieve a
successful delivery for the projects, it is the responsibility of all the project stakeholders to
create the approaches to achieve the goal. Using technology is the enabler for executing
this. Using the CDE will collect the project data within a centralized database.
Meetings are also considered as one of the main tools to deliver the project successfully.
The contractor shall detail in both Pre-Contract BEP and Post-Contract BEP the meetings
will be held within the project execution and its frequency no. This shall follow the UK
standards for the part of the meeting. The weekly/bi-weekly BIM Coordination Meetings
are mandatory to achieve proper delivery for the projects.
8.2 Federated Model Delivery Strategy
Contractors are requested to deliver the Federated model of the project including all
volumes, parts, and disciplines. The federated model shall be in Native format if the project
file size when federated is not exceeding 900Mb. In addition to the native format (Revit or
Civil 3D), the contractors shall deliver a federated model in Infraworks, IFC, and NWD
format.
All contractors shall specify the process of generating the federated models along with the
exporting strategy in the Post-Contract BEP in compliance with The Employer Information
requirements in the Digital Data Delivery Schedule, S.O.S. and any other supporting
documentation.
The contractors are responsible to achieve a proper federated model by improving the
connections between different volumes models and take the necessary actions for a clash-
free and coordinated delivery. The Clash Avoidance Strategy shall be detailed within the
Post-Contract BEP between different supply chain involvement by the contractor.
For the IFC export, the contractor shall generate the exports using the latest IFC Scheme
settings documented in the Digital Style Book Standard, in addition to performing
optimization process through Solibri IFC optimizer. Contractors shall ensure that the IFC
and BCF do not have missing components during the export process.
The same for NWD shall follow the export settings in the Digital Style Book.
8.3 Volume, Model Division and Segregation
Volume, model division and segregation shall be managed in accordance to processes

described in ISO 19650 Standards.
The division of the project models should be established by, either asset, project zones, or
project phases.
Model segregation is driven by hardware limitations, which may affect the usability and
performance of the modeled assets. This shall be part of the delivery of Post-Contract BEP
for The Employer approval.
A main file for the Shared Levels and Grids shall be utilized and included within all the
project's model segregation criteria. This model will be considered as the federated native
Page 420 of 489
model later on to hold all the segregated models. The origin (Project Base and Survey
Points) shall be documented with a snapshot including the different sharing methodologies
(Origin by Origin, Shared Coordinates….) within the Post-Contract BEP.
Zones can be split down furthermore by individual contractor /Sub-Contractor to suit their
own internal working. However, models issued as an overall project zone file.
Diagram and table indicate model division strategy shared in the Post-Contract BEP shall
be provided by the lead contractor.
The contractor to work with The Employer and the BIM leader to establish project
segregation, e.g. zones, assets, and phases.
Effective model segregation strategies:
· BIM file size shall not exceed 150mb
· Contractors should consider file segregation if BIM file size reached 150mb
· Project information models shall contain no more than one building, disregarding
linked context and containment models.
· Project information models only contain information solely produced by the originator.
8.4 Digital Information Delivery Workflow
The below process map describes in brief The Employer workflow for the delivery of the
digital information in the project. All contractors shall comply with The Employer
workflow and in compliance with the Digital Data Delivery Requirements, S.O.S. and the
approved post-contract BEP in all delivery stages of the Digital information.
8.5 Classification
Models, documents, project information, cost information, and specifications shall all be
organized using a classification system to allow external processes such as cost planning
to take place. This classification system must provide a common terminology and structure
to which all project documents and information can be related. The use of the classification
is required in information exchange and COBie templates. As the project progresses the
specification and design information required for the project must increase in detail. The
cost plan and specification required at project gateways/stages should be progressively
defined throughout the lifecycle. The classification system must aid the co-ordination of
elemental cost and the levels of specification to be managed.
All project stakeholders shall align with the project Model Development Specification;
strategy set out in the MDS and BEP documents. The MDS document template will be
provided by the Employer in Uniformat or MasterFormat.
Classification code will be assigned for materials to be presented within the specifications
for the materials.
Page 421 of 489

8.6 Specifications
The Employer requests to utilize the latest technologies in the AECO (Architectural,
Engineering, Construction and Operations) industry among all stages of the project
deliveries related to Digital delivery. This includes the Design stage by utilizing digital
models for early evaluation of the deliveries and decision making. Therefore, all the
contractors are requested to provide a digital model for their designs.
The model’s criteria shall be initiated to simulate a virtual construction. Which means the
models will be created matching the designed specifications criteria (Product Specification
and Components Specification). Specification information is an essential component in the
information model, it describes the requirements and outcomes for the project and this
information will always be necessary and specification information which is representing
a big part of the "i" in BIM.
The contractors are requested to link all the required specifications with all the modeled
elements through the proposed solution e-specs. The Material criticality shall be mentioned
for all the proposed materials and include this in a schedule to be extracted from the BIM
Model includes all the Quality Management requirements for this area. Please check the
Quality Management Schedule.
Product specifications should relate to the systems they belong to, and both should relate
to other BIM information types such as geometry and cost.
The criticality for the materials shall be assigned for all the materials.
8.7 Project Information Model (PIM)
The Project Information Model (PIM) is the repository of all project information model
components, the Contractor shall deliver a federated PIM including all graphical, non-
graphical and documentation. The PIM shall comply with the Digital Data Delivery
Requirements, Post-Contract BEP and the Model Development specification agreed on
and approved by the Employer. The contractor shall deliver the PIM in native format (Civil
3D/Revit), Infraworks Model, NWD, and IFC formats.
8.8 Asset Information Requirement (AIR)
The AIR is part of the Information Management Process (IMP). The AIR is generated from
the Organizational Information Requirements (OIR) and informs all individual projects
Digital Data Delivery. The individual project AIR and Digital Data Delivery Requirements
will be incorporated into the tender documentation.
The AIR fundamentally specifies the deliverables of the Project Information Model (PIM)
[Capex Stage] and the Asset Information Model (AIM) [Opex Stage], both of which are
part of the IMP.
The AIR is formed of 5 sections that must be adhered to in all tender and contract
documentation. The sections comprise from:
· Legal information
· Commercial information
Page 422 of 489
· Financial information
· Technical information
· Managerial information
Each project AIR may start as descriptive text but should then be developed into a digital
plan of deliverables.
The detailing for each AIR will be delivered within the project development and this will
be in a later stage.
Asset information delivery required at handover as part of the information model.
The basic Integrated data within the COBie schema as per BS 1192-4:2014 as follow
· Space for every hosted component
· Type for every hosted component
· System for every hosted component
· Zone for every space
· Every reference to other sheets should be valid
· Every reference to picklist enumerations and classification should be valid.
· Enumerations specified in the attributes and picks lists should be adhered to.
The delivered COBie data shall be delivered by both the contractors and the Contractor for
each phase-related part.
All COBie deliverables should have Continuity with earlier deliverables cumulatively to
enable comparison, validation, and consistency. Deliverables should re-use the unique
asset names defined in earlier deliverables and external identifiers such as (GUIDs) are to
be maintained.
8.9 Asset Information Model (AIM)
The Asset Information Model or AIM is a maintained information model used to manage,
maintain and operate the asset during the operational phase.
A common structure for the exchange of information for new and existing facilities for
both buildings and infrastructure with the use of COBie.
Soft-landings processes and the involvement of the operational team at the early stage by
the contractor to create the asset information requirement (AIR) to ensure success in both
defining (OPEX) requirements and data transfer to AIM.
Mandatory information shall be provided for each data exchange point, data drops, and at
handover to support the development of an AIM:
Page 423 of 489

· Revit, Bentley, Civil 3D, Infraworks and Naviswork format native design authoring
models
· COBie-UK-2014 Export V2.4
· 3D Industry foundation classes (IFC4)
· PDF files of project deliverables
· Schedule documentation in.PDF and/or .xlxs formats.
· DWG exports of project deliverables from the BIM authoring software.
Any Inconsistencies in data are to be addressed by the originating consultant, or contractor.

Post-Contract BEP shall record the responsibilities for providing this information.
Contractors shall ensure that all model components are uniquely tagged with their
corresponding tag number as per the Facility Management requirements.
8.10 Asset Tagging System
All the Employer assets shall be tagged for easy tracking and monitoring later. The
methodology for assets tagging will be described in the Digital Style Book.
8.11 Quality Check and Coordination Documentation Delivery
The contractors shall deliver all the history of the clash resolution to reach full coordinated
and constructible PIM Models and Products. This will be used for Analysis form the
Employer and for Quality Control and Management Purposes.
8.12 Scan to BIM
The contractors shall deliver in the post BEP the way for performing scanning to BIM to
cover the following items:
Scanning Method Description
Laser Scanning Point Scans Quantity

Cloud
Point Cloud Color Mode (Colorized or not Colorized)
Point Cloud Density
Point Cloud Registration Status (Registered or not registered)
Point Cloud Coordinate System (without alignment or aligned with

the model)
Photo geometry point Source (camera, Drone or other)

cloud
Scans Quantity
Page 424 of 489

Point Cloud Color Mode (Colorized or not Colorized)
Point Cloud Density
Point Cloud Registration Status (Registered or not registered)
Point Cloud Coordinate System (without alignment or aligned with

the model)
Also, this shall include the deliverables:
· Modified point cloud data (Registration, alignment, cleaning, Density reduction or

other).
· The 3D Model output format (Revit, Civil 3D, IFC, NWD or other).
· Modeling tolerance (±30, ±20, ±15 or other)
This will cover in the MDS which categories and in which LOD will be used within this
scope.
8.13 Health and Safety and Construction Design Management (CDM) Compliance
The Employer requires details of how BIM information will be utilized to support the
employer’s and supplier’s H&S obligations to demonstrate capability and experience.
Contractor and the supply chain are required to submit the following information:
· Overview of key H&S deliverables against each work stage.
· Confirmation on how deliverables will be shared and accessed.
· Requirements for disaster planning.
· Approach to design authoring and model auditing.
Information is to be made available to the contractor for identifying residual risks at the
construction stage and monitored throughout the construction stages. Contractors are
obligated to inform of potential hazards/risks etc. This should be communicated within the
model where feasible and communicated via the Common Data Environment (CDE).
The Contractor will be responsible for acquiring this information. This list is not
exhaustive, further definition will be provided by the PD and defined in the Post-BIM
execution Plan.
8.14 Model Authoring for Use with Cost Management
The contractor will continue the detailing for the models received from the contractors. All
components with cost significance must be modelled as an instance of a 3D object within
the BIM models. The BIM Models are considered the main sources for extracting the cost
elements. The cost consultant may be required to support in describing how the contractor
Page 425 of 489

team can best facilitate the cost objectives on the BIM project. Building and Infrastructure
elements must be authored using the correct construction category, or Industry Foundation
Classes (IFC) mapping settings to allow accurate IFC type mapping during export
processes. This means the proper assignment and the accurate modelling for achieving the
requirements for cost extractions for different components within the projects. Elements
and layered BIM objects must be modelled in inaccurate locations, with accurate
dimensions in alignment with the construction detailing intent.
Model error logs should be regularly checked, and issues should be resolved (e.g. duplicate
objects are prohibited). Layered or composite BIM objects should comprise of correct
materials in line with the construction detailing intent. BIM objects are to have the agreed
property set associated with them, and parameters should be filled in at the required project
stage. Cost data must be extracted using the QIC measurement codes and Requirements.
Those extractions shall be matching the main two objectives: Cost Estimations and Fixed
Assets Classification Costing. Specific Attributes shall be filled to cover the requirements
to be easily extracted. All the attributes shall be assigned and filled by the contractor to
cover both scopes. Following the extraction forms for the Cost and Fixed Assets Purposes
is mandatory. Room objects will contain accurate data regarding finishes, room function,
name, and intended occupancy. This process shall be documented clearly in the Post-
Contract BEP as it is considered as a mandatory BIM Use. The contractor is requested to
extract two Actual B.O.Q. schedules from the Models arranged by the Codes Assignment
(One is including the CBS and the other is Including FABS). Also, the contractor is
requested to extract Actual M.T.O. schedule from the Models arranged by the Codes
Assignment of the CBS classification. The schedules shall include the ability to group by
BUILDING NO./ZONE/LEVEL. Sharing this information will be on a bi-weekly basis
including the actual information and the proposed one on the CDE before the official
submissions.
9. Common Data Environment (CDE) and Collaboration Methodology
The Employer will use CDE tailored to comply with The Employer requirements. In
addition to that, the contractors shall follow the use of the agreed CDE platform to be used
in compliance with this section. This shall be specified in the Pre-Contract and Post-
Contract BEP, and the Contractor’s Project Information Manager shall ultimately manage
the proposed CDE platform.
The CDE should provide the following functionality:
· Include licenses to access the CDE for all task team members and The Employer team.
· Provide a secure login system.
· Provide a means of recording metadata for files. At a minimum, the CDE should record
the revision and suitability code for each file exchanged.
· Allow current and previous revisions/versions to be viewed and downloaded.
· Provide a system for approval of documents, in accordance with ISO Standards.
· The CDE should include a viewer for the federated model which can be accessed by
registered and authorized users.
Page 426 of 489

· Provide an audit trail for files sufficient to determine:
§ Individual and organization who shared the document
§ Date and time when the document were shared
§ List of recipients and individuals who viewed, downloaded and approved

documents.
9.1 CDE Areas
The Employer has established customized CDE areas that are aligned with The Employer
information management and collaboration process. The Employer CDE workflow and
data exchange process is based on information management standards, but it is customized
to meet The Employer requirements. The CDE workflow consists of 5 sections as listed
below:
· Work in Progress [WIP]: This phase includes data generated at the Designers,
Specialists and contractors CDE -or share folders-, which is not part of The Employer
CDE, this is considered as WIP Private section.
· Shared Work in Progress [SHWIP]: The Employer SHWIP section holds unapproved
information of all parties involved in the project, The Employer at the same time has
complete visibility on this section to execute any required reviews or design check
prior to moving the data to the shared section, this section is considered as WIP Shared
section. The main concept for this is to enable The Employer to take proactive actions
while dealing with different supply chain members. The sharing of the information
here will be based on the agreement with The Employer if it is weekly or Bi-weekly
according to each individual project nature.
· Shared [SHRD]: This section shall be used to hold information that has been approved
for sharing with other organizations to use as reference material for their own Design
Development. All information in the Shared section shall pass the first check, review
and approval process. The checks shall include:
Ø Model suitability check (Suitability code shall be reflected as an attribute in the

CDE, and as well in the model files as either attribute for Civil3D models or
Parameter in the Splash Screen for Revit models)
Ø SMP check.
Ø Technical content check (in compliance with The Employer quality checklist).
Ø COBie completeness check (Where requested).
Ø Drawings extract checks along with any additional documentation that is shared as
a coordinated package of information.
Ø Approval by the task team manager.
Shared Models/Information shall include as well revision sequence for the archiving
process over the CDE and Aconex as well. The revisions will be reflected as an attribute
Page 427 of 489
in the CDE, and as well in the model files as either attribute for Civil3D models or
Parameter in the Splash Screen for Revit models)
· Published [PBLSHD]: This section will include Project Outputs required at defined
The Employer Stage Deliveries. All models and information issued for this section
shall comply with The Employer Digital Data Requirements, The Employer Digital
style Book and Plain Language Questions (PLQ’s). All Documentation and models
issued for the PUBLISH section are considered ready for The Employer
review/approval.
· Archive: The Archive section of the CDE is used to record all progress as each project
milestone deliveries and information requirements are met and will hold a record of all
transactions and change orders to provide an audit trail in the event of a dispute. In
addition, as-constructed information shall be checked and verified in the Published
section to allow transition through the Verified Gate to the Archive section. All models,
documentation, and information issued to the Archive section will be recorded in the
CDE and Aconex as well based on The Employer document management requirements
and standards.
The below diagram is a brief description of The Employer CDE behavior and the flow of
information. The CDE workflow was customized to serve The Employer requirements.
The Employer is considering the implementation of Autodesk BIM 360 Design within its
all CDE implementation for all the projects either it is building, Plant or infrastructure ones
Collaboration for Plant 3D, Civil 3D and for Revit).
In this case, all the project stakeholders will have user access to the system and in this case,
the Two areas will be one area on CDE -which matches the ISO 19650 Standards. The
licenses will be provided by The Employer to the teams to enable this kind of collaboration
on The Employer Account on the platform and based on the assigned workspaces.
Page 428 of 489

9.2 CDE Security
The contractor must prepare a Security Plan that describes the procedures and safeguards
that will be used to preserve the confidentiality and integrity of the BIM and to demonstrate
compliance with The Employer mandates for data security and integrity. This plan shall
be agreed upon and approved with The Employer Security Manager.
For security, user access and change privileges for workspace folders and information
should be carefully considered and agreed with The Employer, Information Manager and
BIM Managers in collaboration before implementing the CDE.
The Employer must agree on any change to user privileges. The user privileges must be
tabled in the Pre-Contract and Post-Contract BEP’s and managed throughout the project
cycle.
The integrated team must maintain adequate security by the correct application of control
privileges.
Security of exchanged information must follow BS ISO/IEC 27001:2005, Information

technology, Security techniques, Information security management systems Requirements.
The administrator should include the Information Manager and another person designated
by the Information Manager, which could be a Document Controller.
9.3 CDE Uploads
The contractor is responsible to manage the Folder structure on the CDE for the contractor
and his supply chain to provide the client an insight to monitor the digital deliverables on
a BI-Weekly basis Uploads for the Models and drawings also for the following information
to be shared:
· Proposed BOQ Bi-Weekly
· Proposed FAS Bi-Weekly
· Proposed MOT Bi-Weekly
· Actual BOQ Bi-Weekly
· Actual FAS Bi-Weekly
· Actual MOT Bi-Weekly
10. Information Exchange and Stage Delivery Management
Key stage delivery dates should be outlined in a Master Information Delivery Plan. On the
agreed dates, all parties will submit the data as agreed. This information must be based on
models which shall be coordinated by the contributors and clash detected. The Employer
and the Information Manager will use Stage Deliveries to validate:
· The progression of the design and design information.
Page 429 of 489

· Compliance with performance requirements set out in contractual agreements.
· The development, completeness, and validity of Facilities Management (FM) data and
other data as specified.
· The Contractor will agree on protocols with the Information Manager to confirm that
the model is current, and all parties are working to the latest model.
· Actions will be disseminated by the contractor to all parties via Common Data
Environment (CDE) and errors or non-compliance will be corrected as a priority with
agreed timescales.
· In addition to the information exchange dates, the parties will download the BIM for
coordination and formal review.
Some data drops will be used as information support for Gateway the Employer -or
representatives- reviews, leading to the instruction to proceed to the next stage if the
information is satisfactory.
Note that all production views and sheets shall be generated in separate model “Production
Model”, no sheets shall be generated in the 3D model files. Sheet views are not permitted
from being deleted from authoring software models to ensure a smooth handover and to
assist in the review process.
10.1 Project Stages
No. Stage Description Core BIM Activities

Strategic Identify the Employer’s
Definition Business Case and
Strategic Brief and other
core project requirements.
1 Preparation Develop Project Objectives, · Advise the Employers on the purpose
& Brief including Quality Objectives of BIM including benefits and
and Project Outcomes, implications. Agree level and extent of
Sustainability Aspirations, BIM including 4D (time), 5D (cost)
Project Budget, other and 6D (FM) following software
parameters or constraints assessment. Advise the Employer on
and develop Initial Project Integrated Team scope of service in
Brief. Undertake Feasibility totality and for each designer
Studies and review of Site including requirements for specialists
Information. and appointment of a BIM Model
Manager.
· Define long-term responsibilities,
including ownership of the model.
Page 430 of 489

· Define BIM Inputs, Outputs, and
scope of post-occupancy evaluation
(Soft Landings).
· Identify the scope of, commission
BIM surveys, and investigation
reports.
2a Pre-Concept Prepare Concept Design, · BIM pre-start meeting.

2b Design including outline proposals · Initial model sharing with Design
Concept for structural design, Team for strategic analysis and
Design
building services systems, options appraisal.
outline specifications, and
· BIM data used for environmental
preliminary Cost
performance and area analysis.
Information along with
· Identify key model elements (e.g.
relevant Project Strategies
prefabricated component) and create
in accordance with Design
concept level parametric objects for all
Program. Agree with
major elements.
alterations to brief and issue
Final Project Brief. · Enable design team access to BIM
data.
· Agree on the extent of performance
specified work.
3 Developed Prepare Developed Design, · Data sharing and integration for
Design including coordinated and design co-ordination and detailed
updated proposals for analysis including data links between
structural design, building models.
services systems, outline · Integration/development of
specifications, Cost generic/bespoke design components.
Information, and Project
· BIM data used for environmental
Strategies in accordance
performance and area analysis.
with Design Program.
· Data sharing for design coordination,
technical analysis, and addition of
specification data.
· Export data for Planning Application.
· 4D and/or 5D assessment.
4 Technical Prepare Technical Design in · Export data for Building Control
Design accordance with Design Analysis.
Page 431 of 489

Responsibility Matrix and · Data sharing for the conclusion of
Project Strategies to include design co-ordination and detailed
all architectural, structural analysis with subcontractors.
and building services · Detailed modeling, integration, and
information, specialist analysis.
subcontractor design, and
· Create production level parametric
specifications, in accordance
objects for all major elements (where
with Design Program.
appropriate and information exists this
may be based on tier 2 supplier’s
information).
· Embed specification to model.
· Final review and sign off of the model.
· Enable access to BIM model to
contractor(s).
· Integration of subcontractor
performance specified work model
Information into BIM model data.
· Review construction sequencing (4D)
with the contractor.
5 Construction Offsite manufacturing and · Agree on the timing and scope of ‘Soft
onsite Construction in Landings’.
accordance with · Co-ordinate and release of ‘End of
Construction Program and Construction’ BIM record model data.
resolution of Design Queries
· Use of 4D/5D BIM data for contract
from the site as they arise.
administration purposes.
6 Handover & Handover of building and ·
Closeout conclusion of Building
Contract.
7 In Use Undertake in Use services in · FM BIM model data issued as asset
accordance with Schedule of changes are made.
Services. · Study of parametric object information
contained within BIM Model data.
10.2 Model Development Specification (MDS)
Building information content managed from model development specification (MDS).

Template document provided by The Employer, refer to Appendices in the QIC Digital
Style Book to have the template.
Page 432 of 489

The template and classification summary report formalizes the level of definition (LOD)
required at each stage and project Delivery. Each delivery shall align with specifically
agreed data exchange in the Pre-Contract and Post-Contract BEP’s.
MDS document can be considered as a live document through the project life cycle, which
establishes the maturity of modeled components for each data exchange.
All project stakeholders shall align with the Project Model Development Specification;
strategy set out in the MDS document.
Contractors are to review the LOD and geometry specifications within the MDS to confirm
that they are enough to support their process of carrying out the required BIM uses.
· Frequency of collaboration and information exchange.
· Details of proposed model review workshops and other collaborative working

practices.
· Details of the proposed method of collaboration with stakeholders / The Employer

utilizing the model.
· Agreed processes will be defined in the Pre-Contract and Post-Contract Building

Information Modelling Execution Plan (BEP).
The Post-Contract BEP shall provide a high-level overview of their methodology for
collaborating to coordinate PIMs.
10.3 Master Information Delivery Plan (MIDP) and Task Information Delivery Plan
(TIDP)
MIPD is the core plan, used to manage the information delivery during the project life
cycle.
MIPD managed through change control and list the information deliverables for the
project, including but not limited to models, drawings, specifications, room data sheets,
and equipment schedules.
The lead contractor shall issue the MIDP along with the Post BEP. MIDP issued is
considered as the primary plan to detail the information to be contained in the building
information model at any point in time, which must be aligned with the project stages and
milestones.
TIDP is defined as federated lists of information deliverables by each task, including

format, date, and responsibilities.
Digital Data Delivery Requirements extends the specification of IDP's in accordance with
Information Management Standards. In addition, the TIDP shall include a plan of the
content of the model deliverables detailing what geometry, data and other information shall
be in the model at each stage.
MIDP template is provided by the Employer for the contractor to use.
Page 433 of 489

11. Information Management
11.1 Level of Definition (LOD)
The LOD provided will be subject to the scope of services and may vary to suit The
Employer/project-specific requirements. The LODs are defined based on UK BIM
framework for each of The Employer delivery stages however this does not specifically
define the graphical and non-graphical content for the model at these stages.
Level of Definition must comprise of the degree to which the elements geometry (Level of
Detail) and attribute information (Level of Information) has been considered. The
Employer deliver stages requirements shall be aligned to the MDS execution. LOD must
be defined for each of The Employer Stage delivery. The LOD outlines the reliance that
can be placed on model elements and the information they contain. All the below is in
reference to UK BIM framework uses the Level of Model Definition to describe the
modeling requirements of The Employer.
LOD specifications shall be reflected in the Deliverables requirements and shall be aligned
with the MDS execution. Each level of The Employer LOD’s shall be covering the
requirements of all lower LOD’s (example: a component at LOD3 shall include the
requirements mentioned in LOD0,1 and 2). LOD’s development is a progressive process.
The Design Consultation Models shall at least reach to LOD3. The contractor is
responsible to deliver the models for the handover process to LOD5.
For the Infrastructure disciplines, LOD4 is considered as the starting level of definition for
components unless specified in the Post-Contract BEP and approved by The Employer.
The Latest BIM Forum Model Development Specification can be considered the reference
specification for the graphical development for the modeled elements. The mapping
criteria for the LOD’s levels shall be considered as below:
LOD100 = LOD1
LOD200 = LOD2
LOD300 = LOD3
LOD400 = LOD4
LOD500 = LOD5 (This LOD500 form AIA definition not BIM Forum Specification)
LEVEL of DEFINITION (LOD)

LOD LOD Description
LOD0 No models are generated. The available data is text, sketched, drawings, lines, etc.
Page 434 of 489

LOD3 The Model Element is graphically represented within the Model as a specific system,
object or assembly in terms of quantity, size, shape, location, and orientation. Non-graphic
information may also be attached to the Model Element. The quantity, size, shape,
location, and orientation of the element as designed can be measured directly from the
model without referring to non-modeled information such as notes or dimension callouts.
The project origin is defined, and the element is located accurately with respect to the
project origin.
This level is considered as a technical design model. The model shall be ready for
generating the project documentation.
LOD4 A LOD4 element is modeled at sufficient detail and accuracy for the fabrication of the
represented component. The quantity, size, shape, location, and orientation of the element
as designed can be measured directly from the model without referring to non-modeled
information such as notes or dimension call-outs.
The model is considered an accurate representation of all assets in the project before the
construction process. Components shall hold all the required information related to
construction, fabrication, manufacturers, costing and sequencing. The model shall be
ready for the generation of virtual mock-ups and extraction of all shop drawings.
Models shall be updated during construction to incorporate any modification occurring
during construction.
LOD5 An accurate record model of project assets as constructed at handover including all
information required for operation and maintenance.
The same shall include all COBie requirements as specified by The Employer or the
facility manager.
11.2 Level of Information (LOI)
Contractors shall comply with the required information of all objects throughout the
project life-cycle, the same shall comply as well with the required information for each
BIM Use and milestone delivery.
· Level of Information (LOI) provide enough information to allow the selection of the
manufacturer product to meet requirements.
· Objects shall include properties and values that are consistently named through all
disciplines collaborating on the project.
· Construction operation building information exchange (COBie) information shall be

provided at the agreed The Employer delivery project stage and to be specified in the
Post-Contract BEP.
· The COBie information is to simplify the work required to capture, record and
disseminate project information for handing over to The Employer.
· The design team shall add space and equipment locations to the model COBie subsets.
Contractors and their appropriate subcontractors, including the commissioning
manager or company shall provide manufacturers information, installed product data,
warranty, and maintenance information.
Page 435 of 489
11.3 COBie Requirements Matrix
It is the responsibility of all object authors to ensure that the following parameter headings
are attributed to the object being authored. This is to be undertaken irrespective of the data
for that parameter field is required at that stage or not. This is to enable data to be included
at the predefined The Employer delivery stage later in the project cycle. Each phase has its
own required COBie attributes to be filled. It is very important to include all the fields
prior moving to the second phase.
All project Contractors shall align with the project COBie Requirements Matrix.
11.4 Attributes and Parameters Requirements Matrix
Project Contractors should develop and agree on the Attributes/Parameters that will be
included in the Model files and to be listed in Post-Contract BEP for record and The
Employer approval.
All Attributes/Parameters naming shall be consistent and following the below-naming

structure
[The Employer]-[ROLE]-[PARAMETER-NAME]
Note: Do not use spaces, for separate between words use underscore “-”
The following list are considered mandatory with the ones related to the BIM Uses ones:
CBS Code, FABS Code and WBS Code.
Attributes Requirement Matrix
Attribute/Parameters Components containing this Type, Description, and purpose

Parameter of use
11.5 Roles and Responsibilities
Contractors shall indicate and outline roles and responsibilities for each assigned project
based on UK BIM framework.
Contractors to produce a full list of names, roles and responsibilities in the Pre-contract
BEP for The Employer approval.
The table below shows a sample of the major project roles, responsibility and tasks.
Page 436 of 489

Role Responsibility/Tasks
Project Enable reliable Information Exchange (IE) through a (CDE)
Information Maintain and receive information into the information model
Management
Enable integration and co-ordination of information model
Configure information for project outputs
Populate the (IE) format for the information model
Accept reject (IE) within the (CDE)
No design responsibility or right to issue instructions
Project Assure delivery of information exchanges
Delivery Confirm supplier’s ability to deliver (IR)
Manager
Accept/reject information exchanges within the (CDE)
Consultant / Co-ordinated delivery of all design information
Constructor Manage information development and information approvals
Confirm design deliverables
Overall lead for configuration management
Confirm status and approve information for issue within the (CDE)
Approve design changes proposed to resolve clashes.
Task Team Production of design outputs related to a discipline-specific, package-based or
Manager time-based task
Issue approved information within the (CDE)
Task Direct the production of task information in compliance with standards and
Information methods
Manager Direct the production of task information using agreed systems
Confirm that information is suitable for issue within a (CDE)
Interface Manage spatial coordination on behalf of a task team
Manager Propose resolutions to co-ordination clashes
Ownership of model information
Contractors shall provide Responsible, Accountable, Consulted and Informed Matrix

(RACI Matrix) for the project based on the roles of the project team and tasks that will be
handled thought the project life cycle. The RACI Matrix shall be developed based on the
below sample. It will be shared within the Standards once the contract is awarded.
Page 437 of 489

12. Compliance Plan and Risk Mitigation
Data quality has direct impacts on profitability, services, products and customer
experience.
Good quality data exploited well will help deliver the best products/services/performance
possible.
Poor quality data will lead to reduced efficiency and profitability, poorer decision making.
Poor data exploitation will lead to reduced efficiency through increased time and effort
required to deliver outcomes.
As BIM Modeling and Management is a major tool for risk mitigation within the AECO
industry, The Employer is expecting the contractor to deal with the compliance and
QA/QC activities as a must to achieve KPI’s.
12.1 Pre-Contract Execution
All contractors must provide Pre-Contract BEP information models in response to (S.O.S.)
and this schedule. Pre-Contract BEP outlines protocols and standards used (e.g. UK BIM
framework) to achieve Level 2 building information models.
Pre-Contract BEP shall outline response to the requirements mentioned in this document
(standards, classification, asset information requirements AIM, non-graphical data
requirements “BS1192-4”, data security requirements, Briefing for design and
construction - (CoP) for facilities management (Buildings infrastructure) “BS8536-
1:2015”.
Page 438 of 489

Pre-Contract BEP demonstrates contractors’ proposed approach to BIM as well as
capability and capacity to meet Digital Data Delivery Requirements and will be part of the
digital assessment methodology as it is describing the proper understanding of the scope
and the requirements.
Model (QA), control procedures, associated validation of workflows and software shall be
demonstrated by contractors in the Pre-Contract BEP for approval by The Employer.
12.2 Post-Contract Execution
Awarded Contractor shall provide Post-Contract BEP confirming all Contractors’

agreements and commitment to the BIM execution plan. Post-Contract BEP should
facilitate information management and delivery through the project life cycle. This
document considered a live document and shall be revised as the project progresses.
Contractor responsibility to ensure all sub-contractors are following both the Digital Data
Delivery Requirements and the Post-Contract BEP. The appointment of the project
information manager must be incorporated.
The contractor shall deliver the first release of the Post-Contract BEP after the project
started with 30 calendar days. This will be subject to approval from The Employer.
Comments shall have complied prior to moving forward with BIM execution in the project.
The delivery for the Post-Contract BEP will be on both the CDE (Autodesk BIM 360) and
EDMS (Aconex) systems.
Awarded contractor shall detail project standards and requirements, below list including
but not limited to:
· Implementation of (CDE)
· The defined digital plan of work incorporation (list of participants, roles, The Employer
delivery stages, task, deliverable, level of details, level of information)
· Utilization of the (TIDP) & (MIDP) in the Post-Contract BEP.
· Detailed RACI Matrix for each person involved within the BIM Process.
· Workflows, drawing & schedule outputs derived from BIM.
· Adherence to model review & model checking practices and procedure. Reports of
such reviews part of project delivery and quality checks.
Post-Contract BEP shall describe the use of a federated model for 3D co-ordination and
clash detection using sequencing, programming, and planning. The Post-Contract BEP
must address how BIM uses meet The Employer requirements.
Any deviations from the UK BIM framework and The Employer Digital Requirements and
specifications must be clearly highlighted in the contractors' post-contract BEP and agreed
on by all project stakeholders and The Employer BIM representative.
Page 439 of 489

12.3 Quality Checks and Reviews
The (PIM) and Asset Information Model (AIM) Shall be developed in compliance with
The Employer requirements at each The Employer Delivery Stages.
All the contractor’s internal checks outcomes shall be documented and kept available for
The Employer review at any time. This includes clashes reports.
The following is considered as a guide of the minimum checks that need to be performed
by the contractor prior to sharing the models with other parties or with The Employer.
Similar checks will be performed by The Employer for approval on received models.
QA Assurance / Control procedure Level of

Role Associated
Assurance
Responsible Software
Checks Definition /Frequency
Model suitability checks

TBD in the
Task
Model Check that the model is fit for BIM Authoring Post-Contract
Information
Integrity coordination. Software BEP
Manager
(by Contractor)
TBD in the
Validate models issued as Task
Model BIM Authoring Post-Contract
Shared are complete and Information
Validation Software BEP
correct. Manager
(by Contractor)
Every Issue.
Level ofValidate model with the (PIM) Task audit prior to
BIM Authoring
Model with the Model Information Information each The
Software
Definition Delivery Plan (MIDP). Manager Employer
Deliver Stage
Standard Method and Procedure (SMP) Checks
Volum Check that the volume strategy TBD in the
Task
e defined in the Post-Contract BEP BIM Authoring Post-Contract
Information
strateg adheres to the proper project Software BEP
Manager
y requirements. (by Contractor)
TBD in the
PIM origin Check that coordinates defined in Task
BIM Authoring Post-Contract
and the Post-Contract BEP adhere to Information
Software BEP
orientation the proper project requirements. Manager
(by Contractor)
File Check file naming and metadata TBD in the

Task (CDE), Splash
naming are completed correctly in Post-Contract
Information Sheet with each
conventio accordance with Post-Contract BEP
Manager model.
n BEP. (by Contractor)
Page 440 of 489

Layer TBD in the
Check layer naming is correct and Task
naming BIM Authoring Post-Contract
in accordance with Post-Contract Information
convention, Software BEP
BEP. Manager
where used (by Contractor)
Agreed Task
BIM Authoring TBD in the
construction Check those construction Information
Software, Clash Post-Contract
tolerances tolerances are in accordance Manager, Task
Detection BEP
for all with Post-Contract BEP. Interface
software (by Contractor)
disciplines Manager
TBD in the
Drawing Check that drawing sheet Task
sheet templates used are in accordance Information
Software BEP
templates with Post-Contract BEP. Manager
(by Contractor)
Annotation, Check that annotation,
TBD in the
dimensions, dimensions, abbreviations, andTask
abbreviatio symbols used are in accordanceInformation
Software BEP
ns, and with standards defined in the Post-Manager
(by Contractor)
symbols Contract BEP.
Check that agreed shared
attributes/parameters are used
and that the naming and type of
attribute is correct. All the TBD in the
Task
Employer requirements and BIM Authoring Post-Contract
Attribute data Information
project team attributes should be Software BEP
Manager
defined or referenced from the (by Contractor)
Post-Contract BEP. (Refer to
COBie completeness checks
also).
Technical Content Checks
Ensure there are no unintended TBD in the

Task Team
model components in the model BIM Authoring Post-Contract
Visual Manager,
and that the model conveys software BEP
Contractor
design intent. (by Contractor)
Detect issues in the model

Task Interface
Clash where two components are Clash Detection Coordination
Manager,
Detection clashing including hard and software Reviews
Contractor
soft clashes.
COBie Completeness Checks
Check COBie data exists and is Task BIM Authoring TBD in the
correct and is suitable for the Information software, Post-Contract
COBie data Manager, Specialist data BEP
Data Drop as defined in the
Digital data Delivery Schedule. Information software e.g. (by Contractor)
Manager Solibri Model
Drawings Extract Checks
Page 441 of 489

Check that all linked models and
appropriate geometry and TBD in the
Task
Drawings information are included. BIM Authoring Post-Contract
Information
/ Sheets Include revision clouds/tags software BEP
Manager
where required. Check sheet (by Contractor)
number, revision, and suitability.
Check that all linked models are

included prior to the information TBD in the
Task
being generated. Include revision BIM Authoring Post-Contract
Schedules Information
clouds/tags where required. software BEP
Manager
Check sheet number, revision, and (by Contractor)
suitability.
Check that all linked models and
TBD in the
appropriate geometry and
Visualization Task Post-Contract
information are included. Check BIM Authoring
s Information BEP
materials for objects. Check sheet software
Manager (by Contractor)
number, revision, and suitability.
Approval by the task team manager
TBD in the
Viewing software-
Check that all information is Task Team Post-Contract
Shared Issue defined in Post-
issued as Shared. Manager BEP
Contract BEP.
(by Contractor)
Other Checks
Excel / Asta /
Primavera /
TBD in the
Review the (PIM) Microsoft Project
Project Project Delivery Post-Contract
progression against the or other agreed
Program Manager BEP
(MIDP) software for
(by Contractor)
project
programming.
12.4 Models Validation Checklist
The contractor shall provide the model validation checklist as part of the delivery at each
Milestone, The Employer has developed a checklist that will be shared with the contractor
upon Post-Contact. A template will be provided once the contract is awarded.
12.5 Compliance with The Employer GIS Platform Data Requirements
All the delivered PIM models shall have complied with the requirements for delivery of
The Employer GIS Platform Data Submission and CDE Metadata requirements.
Page 442 of 489

12.6 Compliance with The Employer Contractual Quality Requirements
All the delivered information shall follow schedule#13 from this document to cover all
related quality management issues related to the hardware, software, process, security,
training, ….
The high-risk issues shall be addressed, and the risk mitigation process shall be delivered
for The Employer approval within the Post-Contract BEP. The high risks from the digital
data delivery perspective are not matching the proper origin coordinates for the models,
the extraction process for all the drawings from the models, the compatibility with the
required attributes list for the platforms…….
The contractor shall employee a BIM specialized third-party organization to run and check
the delivered digital models before its final submittal to The Employer. The proposed third-
party organization associated with their candidates’ CVs shall be submitted and approved
by The Employer 90 days before the final submission date.
13. Infrastructure Services Modeling and Management
The infrastructure information model process is the outcome of federated models

collecting references, objects, property data, and existing conditions. These models shall
host all utilities, connections, and land development data throughout the life cycle of The
Employer project.
Infrastructure models shall be utilized to serve The Employer intended BIM uses.
Page 443 of 489

13.1 Interface Management (IM)
Mainly interfaces occur when a project divided into several sub-projects undertaken by
different scopes. These interfaces can be soft or hard, and external or internal. Information
exchanges between project participants such as design criteria, clearance requirements, or
utility needs between engineering delivery teams or between a delivery team and an
external party are examples of soft interface deliverables. Examples of hard interfaces
include physical connections between two or more components or systems such as
structural steel connections, pipe terminations, or cable connections. An interface within a
single scope of work would be an internal interface, whereas if it occurs between contracts
or scopes of work, then it would be an external interface.
The Interface Management (IM) for the project will focus mainly on the Physical Interface
Points Data Management.
The hierarchical structure of and IM system consist of three elements which are namely,
interface points (IPs), interface agreements (IAs), and interface agreement deliverables
(IADs). An IM system may include many IPs. Each IP can include many IAs, and each IA
can include many IADs. A typical megaproject may include tens of thousands of IADs.
This will be done within three levels:
· The interface between the Master Plan Infrastructure and the boundaries of the cores
· The interface between the master Plan Infrastructure and core Infrastructure and the
boundaries of the plot.
· The interface between the plot’s infrastructure and buildings tie-in points.
13.2 Project Location and Coordinates
All the models shall use an agreed coordinate system when federated there shall be no
additional relocation activity. Project Location, True North and Project North will be set
by the contractor. All project stakeholders shall align model information to ensure the
Page 444 of 489

coordination of project information. To assist a project ‘template model’ file, based on the
project survey information, shall be circulated by the contractor to provide the base point
for all parties to align with. The shared coordinates shall derive from only one file.
All parties shall use shared coordinates based on the master model file provided with all
models produced at true location and elevation above datum, where survey information
has been provided. The internal model Survey Point will be set to a site datum or boundary
line and all models Project Base Points located to a central building grid as a reference.
World Global Coordinate System will then be assigned to the datum to match the
surveyor’s coordinates to eliminate any potential confusion and model misalignment.
The following outlines the procedure for establishing model location and origin
considering location and weather data to enable energy analysis were required as a
deliverable:
· Building and/or site location on the architectural model shall be set at the correct
longitude and latitude, northing and easting, or defined reference point.
· The true north of the building and/or site location on the architectural model shall be
set accurately. This is to be consistent with the existing site model.
· All the models produced in Revit shall use a shared coordinates system.
· Contractors will share information in Industry Foundation Classes (IFC) format and
3D coordination exchange formats to ensure that information is correctly and
consistently aligned. The agreed process is to be documented in the project Pre-
Contract and Post-Contract Building Information Modelling Execution Plans (BEP’s)
to provide consistency of methodology.
· The measurement and coordinate systems are to be confirmed and shall comply with
the Employer GIS Standards and requirements.
14. Integration with GIS Database
One of the key benefits of using BIM models is that data and models can be easily
transferred to GIS platforms for The Employer visualization, Analysis and data storage
purposes.
An extra delivered BIM model shall be provided for the use of GIS Integration. The
contractor shall take into consideration the models' segregation criteria and management
to provide at each stage a light federated BIM Model that includes: Infrastructure related
services, Structural Components, Outer Skin, and MEP tie-in Points. No-fine details shall
be delivered within this model.
The following quality checks are part of the BIM models quality check items and must be
performed before transferring objects and data from BIM to GIS platforms:
· The coordinate system shall be defined correctly to ensure direct transfer of data to
GIS for visual checking and ensuring that the correct coordinates system has been used
before issuing the BIM-GIS transferring process.
Page 445 of 489

· All BIM Lighted -Version models objects exist and modeled correctly and satisfy the
level of details and level of information required.
The following workflow can be used as a guide for BIM – GIS integration process.
In the case if the BIM enabled GIS Models will be delivered, No need for full GIS Package
delivery.
15. GIS Data Standards
Implementation of GIS data standards will facilitate GIS data integration with the existing
The Employer GIS database.
The Employer provides a GIS data model, a Data Dictionary, a GIS Template, and a
Quality Assurance Checklist that will facilitate the work and speed up the production
process. The Employer expects all developers to start from these templates and use the QC
tools as a first-level quality control before the submission of the packages.
15.1 Spatial Reference
All Geospatial Data, Images, and Control Points provided to or produced for The Employer
needs shall be in the UTM (Universal Transverse Mercator-UTM Zone 38) coordinate
system having below parameters:
Parameter Description
Name WGS 1984 UTM Zone 38N
Projection Transverse Mercator
False_Easting: 500000.0
False Northing 0.0
Central Meridian 45.0
Scale Factor 0.9996
Latitude Of Origin 0.0
Page 446 of 489

Linear Unit Meter (1.0)
Geographic Coordinate System GCS WGS 1984
Angular Unit Degree (0.0174532925199433)
Prime Meridian Greenwich (0.0)
Datum D WGS 1984
Spheroid WGS 1984
Semimajor Axis 6378137.0
Semiminor Axis: 6356752.314245179
Inverse Flattening 298.257223563
The Z coordinate system shall be WGS_1984.
15.2 Units of Measurements
Measurement Unit
Linear Meter
Measurement
Area Measurement Square Meter
Angular Decimal Degree

Measurement
Time Time format: 24 hour clock hh:mm:ss (example

21:46:26)
Date format: DD-MM-YYYY (example: 18-02-

2019)
Gregorian calendar
Time Zone: Coordinated Universal Time (UTC)
Currency Saudi Riyal (SAR)
The Employer requires that all coordinate values be reported in units of Meter. This
requirement applies to all ground survey data as well, which must be submitted with
equivalent WGS 1984 UTM Zone 38N values for all points, if the points were not
originally captured in WGS 1984 UTM Zone 38N.
Page 447 of 489

15.3 Character Encoding
Unicode Text shall be encoded using UTF-8 as character encoding. This ensures that all
linguistic texts can be encoded in any language, in particular, Arabic and English.
The use of UTF-8 aligns with INSPIRE requirements.
Reference: http://www.unicode.org/reports/tr17/
15.4 Accuracy Requirements
Data submitted to The Employer must be accompanied by a full description of the

processing used to create said data, and of its accuracy. This description should include
information on both the positional accuracy (horizontal and vertical), and the accuracy of
any attribute information captured.
Positional accuracy values shall be reported in ground distances. The number of significant
places for the accuracy value shall be equal to the number of significant places for the
dataset point coordinates. Accuracy reporting in ground distances allows users to directly
compare datasets of different scales or resolutions.
Base information used to create geospatial data must at least as specified in The Employer
Survey documents, and as listed in the following table:
Area Type Topographic Data Land & Cadastral Mapping
Description Topographic data consist of Cadastral parcels, buildings,

Ground Control Points, DSM, roads, infrastructure, utilities, etc.
DEM, topographic/base map,
map features such as Wadis,
Stormwater ponds, power lines,
green areas, fences, barriers, etc.
Level of Detail High Very High
Accuracy ± 5cm ± 3cm
15.5 Data Format
All GIS data shall be submitted as File geodatabase compatible with Esri’s ArcGIS version
10x or higher.
16. GIS Data Model Standards
16.1 Dataset Themes
The Employer has categorized spatial data into themes. Each theme has an abbreviation
that is used as a prefix to all feature classes and tables belonging to that theme.
Page 448 of 489
The following table The Employer data model themes and the abbreviations:
Theme Abbreviation Description
Administrative Units AU This theme represents the Administrative Units

theme. It represents the units of division at all levels
of the administrative hierarchy in the Kingdom of
Saudi Arabia.
Buildings BU This theme represents the theme of the building. It

consists of the following feature types; Building,
Building Part, Other Constructions and Building
units.
While the Master Plan includes buildings, this theme

represents the as-is building features.
Cadastral Parcels CP This dataset represents the Cadastral Parcels theme.

It consists of the following feature types; Plot (Point,
Line, Polygon) and Parcel Zoning.
While the Master Plan includes plots, this theme

represents the as-is plot features.
Elevation EL The Elevation of a terrain surface describes the

Earth's morphology. The Elevation theme consists of
terrestrial elevation.
Environmental EF This theme represents environmental monitoring

monitoring Facilities facilities that record observations and measurements
on specific aspects of the environment (e.g. air
quality, atmospheric conditions, water quality).
Geographical Names GN Names of areas, regions, localities, cities, suburbs,

towns or settlements, or any geographical or
topographical feature of public or historical interest.
Hydrography HY Hydrographic elements, including marine areas and

all other water bodies and items related to them,
including river basins and sub-basins.
Internal Building IB The internal building theme represents internal

building features needed to represent 3D buildings in
GIS and to conduct analysis.
Land Cover LC Land cover data is a physical or biological

description of the earth's surface. In this way, it is
different from the land use data dedicated to the
description of the use of the Earth's surface.
Page 449 of 489

Master Plan MP This theme represents the Master Plan theme.
Supportive Structure SS This theme represents the supportive structures in

Qiddiya. Example: barriers, gates, entrances, etc.
Transport Network TN This theme represents the road network in Qiddiya

and its related infrastructure.
Utility Services – USEL The electric utility services theme provides basic
Electricity information of the Electrical Network: Node-link-
node structured networks for collection,
transmission, and distribution of electricity.
Utility Services Fire USF The fire system is an active fire protection method,
consisting of a water supply system, providing
adequate pressure and flowrate to a water distribution
piping system, onto which fire sprinklers are
connected.
Utility Services - USHVAC HVAC (heating, ventilation and air conditioning)

HVAC refers to the system used in indoor settings such as
homes and offices that need environmental regulation
to improve comfort.
Utility Services - USI The irrigation utility services theme provides basic
Irrigation information of the Irrigation Network: Node-link-
node structured networks for collection,
transmission, and distribution of irrigation.
Utility Services Oil USOGF The fuel utility services theme provides basic
Gas Chemical-Fuel information of the Fuel Network: Node-link-node
structured networks for the distribution of fuel.
Utility Services Oil USOGG The gas utility services theme provides basic
Gas Chemicals-Gas information of the Natural Gas Network: Node-link-
node structured networks for transmission and
distribution of natural gas.
Utility Services - USSW The sewage utility services theme provides basic
Sewer information of the Sewage Network: Node-link-node
structured networks for collection, transmission, and
distribution of sewage.
Utility Services - UST The telecommunication utility services theme

Telecommunication provides basic information of the
Telecommunication Network: Node-link-node
distribution of telecommunication.
Page 450 of 489

Utility Services - USTC The district cooling utility services theme provides
Thermal-Cooling basic information of the District Cooling Network:
Node-link-node structured networks for distribution
of cooling capacity in the form of chilled water or
another medium from a central source to multiple
buildings through a network of underground pipes for
use in space and process cooling.
Utility Services USTW The treated water utility services theme provides
Treated Water basic information of the Treated Water Network:
Node-link-node structured networks for the
distribution of treated water.
Utility Services - USWA The water utility services theme provides basic
Water information of the Water Network: Node-link-node
distribution of water.
16.2 Data Model Diagrams
All GIS data shall be submitted in The Employer database schema. Refer to the latest
version of The Employer GIS Data Dictionary document for the data model diagrams.
16.3 Data Dictionary
The Employer GIS data dictionary is a comprehensive document that includes detailed
descriptions of all the elements of The Employer data model.
Refer to the latest version of The Employer GIS Data Dictionary document.
16.4. Potential Changes to The Employer Data Model

It should be noted that the data model is a living document that may be modified from time
to time, based on new data received by The Employer.
After reviewing the Data Dictionary, if you can’t find the layer or attribute, you’re looking
for in The Employer GIS schema, you have the following options:
· Contact the Employer for clarification.
· If you believe that The Employer data model needs modification, fill The Employer
Data Model Change Request Form. The form will be delivered once the contract is
awarded.
· In the meantime, add your data to The Employer GIS schema into a new dataset.
Note: In the event that The Employer does not approve your request for data model change,
The Employer will inform you of the reason and will come back to you with further
instructions.
Page 451 of 489

17. GIS Metadata
Metadata is data about the data. Metadata can help users know what's in your services,
who created them, and what usage restrictions they might carry. Including metadata can
help ensure that your services are found, used, and attributed correctly.
The Employer geospatial data shall follow the INSPIRE Metadata Directive.
INSPIRE metadata is described in ArcGIS as the following example:
Meta Data Element Content / Description / Example
Topics and Keyword
Content-Type Type of included data
Citation
Title The ordinary name of the dataset.
Presentation Format Ex. Digital Map
Resource Details
Dataset Language Ex. English
Spatial Presentation Type Ex. Vector
Processing Environment Ex. Windows 7 / ARCGIS 10.4
ArcGIS Item Properties
Name Data set name
Location Path of Data set on the hard drive
Access protocol Ex. Local Area Connection
Spatial Reference
Type Geographic or Projected
Geographic Coordinate Reference Geographic Coordinate System
Coordinate Reference Details Geographic Coordinate System Details
Page 452 of 489

Reference System Identifier Value
Codespace
Version
Spatial Data Properties
Vector Level of topology for this data set (Ex. Geometry Only)
Feature class name Object Type
Object Count
ArcGIS Feature class Properties Feature Type
Geometry type
HAS Topology
Feature Count
Spatial Index
Linear Preference
Distribution Format Name (Ex. File Geodatabase Feature class)
Metadata
Metadata details Language
Character Set
Scope of the data described by the metadata
Scope Name
Last Update
Metadata format
Metadata style
Created on date
Page 453 of 489

last Modified on date
Automatic Updates Has been Performed
Automatic Updates Last Update Date
Fields
Details for Object Type
Row Count
Field Alias
Data Type
Width
Precision
Scale
Field Description
Description Source
Description Of Values
Enumerated Domain Value
(if applicable) Definition
Definition Source
Range Domain Minimum
(if applicable) Maximum
18. GIS Data Quality
Data submitters shall be responsible for the quality assurance and quality control (QA/QC)
of all GIS data, even when converted from other drawing formats.
The following minimum topology rules must be followed:
· Features shall not be duplicated.
Page 454 of 489

· Coincident boundaries shall be correct: features that share boundaries with features in
other feature classes.
· Linear features shall not overlap; i.e., all lines intersecting in the real-world shall
require a node
· Linear features shall maintain correct arc directionality for any data set with flow
directions.
· Linear features shall not have pseudo-nodes unless they are required to maintain a
change in the arc.
· Polygons shall be closed.
· Polygons shall have no overshoots or dangles.
· Polygons shall not overlap.
· Polygons sharing edges shall not have gaps.
· Moreover:
· The XY tolerance shall be at least 0.001 Meter. (A closer tolerance may be used where
the accuracy of the data supports it, such as that collected with a survey-grade GPS).
· The XY resolution shall be at least 0.0001 Meter.
A Quality Assurance Checklist must be filled and submitted with every data package. The
Quality Assurance Checklist is part of the GIS Data Submission Form. The form will be
shared once the contract is awarded.
19. GIS Data Delivery Packages
19.1 GIS Data Package Submission Requirements
Data delivery is usually by the project at each gateway or end of the phase. The GIS data
package shall be submitted in electronic form. The package should follow the following
folder structure:
Every GIS submission package shall consist of the following:
Page 455 of 489

Project No-Project Name A folder named after the Project number and/or Project
Name.
01 Data Submission Form The Data Submission Form duly filled and signed by the
Project Manager.
Data Model Change Request Form duly filled, if

applicable.
02 GIS Template Original the Employer’s GIS template shared with the
data submitter
03 Source Data Usually, Consultants and Contractors create the data in a

non-GIS format, such as CAD or BIM, and later convert
the data to GIS format.
When this is the case, the source data should be placed in

this folder.
04 GIS Data The submitter’s GIS file geodatabase using The

Employer’s geodatabase schema.
19.2 File Naming Convention
The file geodatabase naming convention shall follow The Employer’s document
numbering schema.
19.3 Delivery Media
The delivery media shall be in conformance with The Employer’s rules and regulations.
Page 456 of 489

SCHEDULE 21
PHOTOGRAPHIC AND AUDIO-VISUAL RECORDING
1. The Contractor shall create and maintain photographic and audio-visual recordings to
document the progress of the construction, installation and commissioning deliverables
under this Contract in sufficient detail to inform the Employer of all aspects of the Works
over the period set out in Sub-Clause 4.21.2 of the Construction Contract and to give an
up-to-date and clear picture of the progress so that Employer can directly confirm whether
the Works are on schedule.
2. The Contractor shall register the recordings in a database and link the electronic files to
the relevant daily, weekly and monthly Progress Reports.
3. The preferred image format for photographs is JPEG and shall include georeferencing,
date stamps and any additional attributes required by the Employer.
4. The preferred image format for audio-visual recordings is MP4 and shall include
georeferencing, date stamps and any additional attributes required by the Employer.
5. All linked electronic files shall be provided on thumb drives, SD cards, or CD-ROM. The
Contractor shall deliver the photographic and audio-visual recordings to the Employer in
either hard copy or electronic format on a weekly and monthly basis and as and when
requested by the Employer.
Page 457 of 489


Schedule 20 - Digital Data Delivery

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Schedule 20 - Digital Data Delivery

Uploaded by

Copyright:

Available Formats

DIGITAL DATA DELIVERY

The intent of this schedule is to provide an outline definition of requirements to support

1.1 The Employer Organizational Digital Data Requirements

· Efficient visual communication of the design intent as the project develops.

· Support evaluation of design iterations and improves clarification raised at The

Page 408 of 489

· Improved consistency and accuracy of design information, understand and evaluate

· Improved multidisciplinary design coordination and reduced variation costs during

· Improved cost certainty and predictability.

· Visual communication and optimization of construction phases and sequencing.

· Improved health and safety on-site and during operation.

· Quality tracking of the final physical conditions of the building.

1.2 Data Ownership and Reuse

Page 409 of 489

1.3 Terms, Definitions, Abbreviations, and Acronyms

2. Standards Applied and Protocols

Page 410 of 489

Page 411 of 489

QIC_Digital Data Delivery M M M M M M

Page 412 of 489

Activity BIM Authoring Tool/Software Version

Page 413 of 489

Format Description Format Description

4. Project Data Exchange Formats

Project information data exchange should be provided through an Electronic Document

Activity RVT DWG PDF IFC DGN NWF XLSX NWD

Page 415 of 489

5. Hardware Requirements and System Performance

BIM Use Specification

Page 416 of 489

Page 417 of 489

Handover & Closeout

Page 418 of 489

Asset information shall be derived as per BS 1192-4:2014 Collaborative production of

• COBie requirement matrix

• Attributes and parameter requirement matrix

• Model development specification (MDS)

All commissioning information should also be included to develop a full auditable

Page 419 of 489

8.2 Federated Model Delivery Strategy

8.3 Volume, Model Division and Segregation

Volume, model division and segregation shall be managed in accordance to processes

Effective model segregation strategies:

· BIM file size shall not exceed 150mb

8.4 Digital Information Delivery Workflow

Page 421 of 489

8.7 Project Information Model (PIM)

8.8 Asset Information Requirement (AIR)

Asset information delivery required at handover as part of the information model.

· Space for every hosted component

· Type for every hosted component

· System for every hosted component

· Zone for every space

· Every reference to other sheets should be valid

· Every reference to picklist enumerations and classification should be valid.

8.9 Asset Information Model (AIM)

Page 423 of 489

· COBie-UK-2014 Export V2.4

· 3D Industry foundation classes (IFC4)

· PDF files of project deliverables

· Schedule documentation in.PDF and/or .xlxs formats.

· DWG exports of project deliverables from the BIM authoring software.