CAD

Paul King
Bentley Systems
+44 (0)7966 162 695
MASDAR
CAD/BIM
Modelling and Collaboration Guide
Version 2.0.3
Date issued 15 February 2010
Document number MAS-XX-00-XX-RP-0001
Custodian Masdar
Page 1 of 224 Formatted for double-sided printing at A4 size
CAD/BIM modelling and collaboration guide
MASDAR
Foreword
The Abu Dhabi Future Energy Company, through the Masdar Initiative, is building a sustainable
zero-carbon, zero-waste city in Abu Dhabi that will rely fully on on-site renewable energy.
Masdar aims to implement best practice for building information modelling (BIM) and
collaboration. To do that it has developed processes and documentation for producing and
controlling spatial building, utilities, infrastructure and master planning information and data
throughout the life of a project, based on the UK‘s Avanti methodology which is now embodied
within British Standard 1192. This standard establishes the processes for managing the
production, distribution and quality of technical information using a disciplined process for
collaborative working and a specified naming policy. It is applicable to all parties involved in the
preparation and use of information throughout the project lifecycle, and the principles for
information sharing and modelling are equally applicable to building and civil engineering
projects.
This document describes Masdar‘s framework for producing and managing project data in a
consistent format through the life of a project. It provides guidance to create integrated designs
that will facilitate multi-disciplinary technical coordination during design and construction, and
Paul King
provide rich data that can be used through the entire life cycle of an asset.
Bentley Systems
+44 (0)7966 162 695
Compliance with the requirements of this document is mandatory for all Masdar projects.
Document history
Version Date Comment Prepared Approved

0.0.1 1 Oct 2009 First draft for comment (individual documents) Paul King Phil Jackson
1.0.1 6 Oct 2009 First issue (individual documents) Paul King Phil Jackson
1.0.2 13 Nov 2009 Final draft incorporating Masdar comments (individual Paul King Phil Jackson
documents)
2.0.1 25 Nov 2009 Previous versions issued as a suite of seven separate Paul King Phil Jackson
documents. This version combines them into a single Vivek Kale
publication. Raguram Jayaram
Phil Jackson
Chapter 6 to be completed, pending DCS implementation
Chapter 7 figure numbers to be added - awaiting

completion of chapter 6.
2.0.2 29 Jan2010 Collaboration sections completed Phil Jackson Phil Jackson
References to CAD configuration files added (appendix 7) Vivek Kale
2.0.3 15 Feb 2010 Comments from Don Davis incorporated Paul King Phil Jackson
Version 2.0.3 3 of 224

MASDAR
Contents
Chapter 1: Introduction
1 Project statement .............................................................................................................................. 8
2 Modelling and collaboration documentation ................................................................................... 9
3 Summary of requirements .............................................................................................................. 10
4 Modelling and design collaboration software ............................................................................... 12
5 Updating BIM documentation......................................................................................................... 13
6 Glossary .......................................................................................................................................... 14
6.1 Definitions 14
6.2 Abbreviations 17
6.3 References 17
Chapter 2: Information and data management strategy

7 BIM process..................................................................................................................................... 20
7.1 Introduction to BIM 20
7.2 Federated BIM approach 21
7.3 Bentley software applications 22
7.4 Benefits of using BIM 22
Paul King
Bentley Systems
+44 (0)7966 162 695 8 Collaboration process .................................................................................................................... 24
8.1 Introduction to collaboration 24
8.2 Benefits of effective collaboration 24
9 Masdar procurement process ........................................................................................................ 26
Chapter 3: Design information modelling guide

10 Modelling concept........................................................................................................................... 28
10.1 General principles 28
10.2 Modelling process 29
10.3 Types of model 29
11 Sharing project information and data ............................................................................................ 33
11.1 Design coordination and project collaboration 33
11.2 Exchanging 3D models 33
11.3 Quality assurance 35
12 Using discipline models ................................................................................................................. 36
12.1 Multiple uses for models 36
12.2 Coordination and clashing 37
12.3 Data extraction 40
12.4 Simulation and analysis 42
12.5 Visualisation 45
12.6 Drawing production 47
12.7 Configuring model outputs for analysis and exchange 48
13 Information levels ........................................................................................................................... 49
13.1 Introduction to information levels 49
13.3 Information levels for delivery 50
13.4 Information level for operation 59
13.5 Project planning using information levels 59
14 Modelling roles and responsibilities .............................................................................................. 60

MASDAR
Chapter 4: Element coding standard

15 Object classification ....................................................................................................................... 64
16 Data content of design deliverables .............................................................................................. 65
17 Layer / level structure ..................................................................................................................... 66
17.1 Introduction to layers 66
17.2 Layer naming 66
17.3 Requesting additional layers 69
18 Object structure .............................................................................................................................. 70
18.1 Introduction to object structures 70
18.2 Information levels 70
18.3 Setting up attribute data 71
Chapter 5: CAD standard

19 Modelling standards ....................................................................................................................... 74
19.1 Introduction to modelling standards 74
19.2 Setting up models 74
19.3 Dataset information 77
20 Drawing standards .......................................................................................................................... 79
20.1 Introduction to drawing standards 79
20.2 Drawing numbering 79
20.3 Drawing setup 79
Paul King 20.4 Composition technique 84
Bentley Systems
+44 (0)7966 162 695 20.5 2D detail drawings library 90
20.6 Plotting 90
21 Validation of information ................................................................................................................ 92
Chapter 6: Data management guide

22 General principles of collaborative modelling .............................................................................. 94
23 Technical coordination process..................................................................................................... 95
23.1 General requirements for collaboration 95
23.2 The common data environment (CDE) 96
23.3 CDE basics 96
23.4 Functional areas of the CDE 97
24 The Masdar collaboration environment ....................................................................................... 101
24.1 Introduction to ProjectWise 101
24.2 Structure of the collaboration system 103
25 Data structure................................................................................................................................ 108
25.1 Container folder structure 108
25.2 File identifiers 110
25.3 File naming convention 110
26 Collaboration roles and responsibilities ..................................................................................... 120
26.1 Masdar programme 120
26.2 Project Management Contractors (PMC) 121
26.3 Design partner and contractor 121
27 Delivery requirements................................................................................................................... 124
27.1 General requirements 124
27.2 Buildings 124
27.3 Site infrastructure 124
27.4 Ground surface 125
27.5 Below-ground utilities 125

MASDAR
28 Sign-off and approval processes ................................................................................................. 126

28.1 General requirements 126
28.2 Working with Primavera Contract Manger (PCM) 126
28.3 Sign-off phases 126
29 Using the collaboration system ................................................................................................... 127
29.1 Creating and editing work in progress 127
Chapter 7: Data management standard

30 Revision status ............................................................................................................................. 132
30.1 Introduction 132
30.2 Format for drawings 132
30.3 Revisioning sequence for drawings 132
30.4 Format for model files 133
30.5 Revisioning sequence for model files 133
30.6 Status 135
31 Meta-data ....................................................................................................................................... 136
31.1 Introduction 136
31.2 Data format 136
31.3 Required fields 136
31.4 Linked fields 136
31.5 Dates 136
31.6 CSV format 136
31.7 XML format 136
Paul King
Bentley Systems
+44 (0)7966 162 695
32 Transmittal of data ........................................................................................................................ 137
32.1 Electronic media 137
32.2 Referenced drawings 137
32.3 CAD files 137
32.4 Meta-data 137
Chapter 8: Education, training and support

33 Masdar’s structured approach ..................................................................................................... 140
33.1 Introduction to education, training and support 140
33.2 Education 140
33.3 Training 141
33.4 Support 142
34 Learning paths for technical training........................................................................................... 143
34.1 Introduction to learning paths 143
34.2 Training matrix 143
34.3 Basic courses 145
34.4 Architectural modelling 150
34.5 Mechanical systems modelling 152
34.6 Electrical systems modelling 155
34.7 Structural modelling 156
34.8 Infrastructure modelling 160
34.9 Project team collaboration 163

Introduction to modelling and collaboration documentation
MASDAR
Chapter 1
Introduction to modelling and collaboration
documentation

Chapter 1: Introduction to modelling and collaboration documentation
MASDAR
1 Project statement
Masdar‘s goal is to deliver a lifecycle programme using a collaborative building information
modelling (BIM) approach for design, delivery and operation through the industry‘s best teams
and processes enforced by approved standards and methodologies. This will be achieved by
engaging and supporting the supply chain to meet Masdar‘s expectations whilst delivering
tangible business benefits. Masdar‘s managed data environment will unite project teams of
architects, engineers, contractors, and other supply chain partners over the entire facility lifecycle
to ensure that:
 Tools can be integrated with each other
 Information can securely be created, shared, and synchronised with the whole project team
 People, regardless of location, time zone or discipline, have the right information in the right
format to make the best decisions for their task.

MASDAR
2 Modelling and collaboration documentation

Masdar has developed a set of standards and guides (this document) for producing and
controlling spatial information and data throughout the life of a project, based on international best
practice; methodologies are neutral regarding software products and are intended to be used by
common object-based BIM software. The document is divided into eight chapters as follows.
Chapter 1: Introduction
Introduces Masdar‘s modelling and collaboration guides and procedures, and summarises the
requirements applicable to every project.
Chapter 2: CAD/BIM information and data management strategy

Describes the principles of producing and controlling project data through the life of a Masdar
project. It describes the framework to create integrated and coordinated designs that will facilitate
multi-disciplinary collaboration, and help to ensure that project data can be used by business
systems as the foundation for operation and maintenance though the asset life cycle.

Explains the basic principles of a common coherent working method for all parties working on
Masdar projects, including the 3D modelling concept, exchanging 3D models and quality
assurance of the 3D model data.

Specifies naming conventions and the content of layers and objects. The layer structure
describes how information must be structured to be able to produce drawings from the models.
The object structure describes the rules for the objects included in models, how they are
structured, and which properties they have at a given point in the design process.

Describes how to structure and build 3D models. Guidelines are given for drawing production
and data extraction, and references to seed files and data sets.

Defines best practice in the management of design data and information, and outlines the
methods of sharing data between parties through a common data environment. It is based on the
UK‘s Avanti solution, now embodied within British Standard (BS) 1192:2007, which establishes
the methodology for managing the production, distribution and quality of technical information.

Defines the criteria to be adopted for the submission of drawing related data (such as file
numbering, meta-data and revisioning).
Chapter 8: Learning paths

On-boarding of each new Masdar partner will require a strategic approach together with a set of
appropriate resources, including training material. This chapter provides examples of suitable
role-based training for project teams.

MASDAR
3 Summary of requirements
Masdar projects consist of 2D and 3D graphical and geometric content created using different
applications and formats. The challenge facing project teams is to assemble the various pieces
of content in a single interoperable environment for downstream processes. Therefore, Masdar
has developed a design methodology and collaboration solution using Bentley‘s ProjectWise,
which will provide a controlled source of ‗shared‘ files to facilitate collaboration and a single
source of truth for all ‗issued‘ engineering content documents.
This section provides a summary of the requirements for modelling and collaboration, and further
support can be obtained from Masdar‘s BIM Solutions Team Leader.
Masdar’s methodology is designed to suit the needs of the programme as a whole rather
than the individual needs of a single designer, specialist or contractor. Masdar’s preferred
working method uses Bentley tools and formats, which will provide a common format for
federation and collaboration. Other working methods, if chosen, must demonstrate
adherence to the federated model requirements specified in Masdar’s project guides and
standards, and it is mandatory for design deliverables to be submitted to Masdar in native
Bentley DGN format.
General requirements
(a) Project teams must comply fully with the requirements of Masdar‘s modelling and
collaboration standards and guides (this document).
(b) Each organisation must appoint a Digital Design Coordinator to support and liaise with the
Masdar Collaboration System Manager, project managers and document controllers on the
delivery and use of data in the Masdar collaboration system.
(c) Project teams must follow Masdar‘s delivery phases.
Modelling
(a) All parties must use a common working method for creating building information models
(BIMs) and other information. 3D models and the 2D drawings generated from them must be
produced in a consistent format and in their correct geographical location.
(b) Al parties must use common CAD layer and object structures to ensure that information held
in 2D and 3D building models can be exchanged easily between all participants. Masdar
uses the UniFormat classification system to classify all modelling objects and drawing
features, and requires layers to be named according to the US National CAD Standard.
(c) All BIM objects will have associated attribute data. Some data will be tagged directly to the
3D object in the model while other data will be stored in an external database and linked to
the object using a unique identification reference.
(d) BIMs will undergo successive detailing through the project stages and value will be added to
the models in the form of increasingly accurate data and information that can be re-used.
Masdar uses the concept of information levels to define the content of models at a given
stage of a project. An information level expresses how fully specified and detailed the
objects are; that is, the discipline model will contain particular building elements in the form of
objects with a particular level of detailing and particular properties, suitable for particular
Version 2.0.3 10 of 224

MASDAR
uses.
(e) The BIM and CAD software versions for project deliverables are listed in Masdar‘s CAD
Standard. Where participants have appropriate access to Masdar‘s ProjectWise collaboration
system then the necessary standards will be auto-loaded for users by creating the required
configuration from within Masdar‘s preferred authoring applications (Bentley tools).
Otherwise, the suite of standards will be packaged and distributed offline.
(f) Technical design deliverables comprising CAD files and BIMs must be submitted in Bentley
MicroStation format (.DGN) together with the corresponding IFC (Industry Foundation Class)
files, version 2x3. Depending on particular contract requirements, technical project
deliverables may also be required to be submitted to Masdar in 3D PDF and Google
SketchUp formats.
(g) Project teams must provide spatially correct models in the coordinate system and datum
used throughout the project; that is: UTM, Zone 40 North, WGS84 (ITRF96), metres for the
horizontal and the New Abu Dhabi Datum for the vertical. The average scale factor is
1.000322623.
Collaboration
(a) Design teams must upload into Bentley ProjectWise all BIMs, CAD models, drawing files,
related reference files and corresponding information and meta-data with each formal
submittal.
(b) Design teams must update ‗SHARED‘ collaboration BIMs, CAD models and related meta-
data in Bentley ProjectWise at agreed collaboration milestones or other agreed points for
project collaboration.
(c) Masdar has established an approvals process to ensure that model and drawing files are
adequately checked and to enable the design teams, Masdar and the contractor to approve
and sign-off the development of the design information at appropriate points. The process
includes an automated check of submitted data to ensure compliance with Masdar‘s CAD
Standard (chapter 5) and other project requirements; files which fail to comply will be
quarantined and a non-compliance report sent to the originator.
Version 2.0.3 11 of 224

MASDAR
4 Modelling and design collaboration software

Where supply chain partners plan to work natively using Masdar‘s preferred Bentley platform then
software licenses will be provided to project teams as required. Examples of the core Bentley
products are listed in table 1.
Partners are required to produce their design solutions using building information modelling, and
to submit design deliverables in native Bentley (.DGN) format.
Table 1 Bentley software tools
Tool / files Description Version
Bentley MicroStation Bentley‘s core CAD platform. Its native file format is DGN and it can view, 08.09.04.88
reference, and edit many CAD formats, including DWG.
Bentley Architecture Architectural BIM application 08.09.04.46
Bentley Structural BIM application for creating structural systems. 08.09.04.65

Bentley Building BIM application for building-related mechanical systems. 08.09.04.72
Mechanical Systems
Bentley Building BIM application for building-related electrical systems 08.09.04.17

Electrical Systems
ProjectWise Navigator Enables teams to visualise, navigate, and interact with 3D models. 08.09.04.60
ProjectWise Navigator A plug-in for ProjectWise Navigator for performing interference analyses and 08.09.04.60
Interference Manager reviews.
ProjectWise Navigator A plug-in for ProjectWise Navigator for linking 3D models to scheduling tools 08.09.04.60
Schedule Simulator such as Primavera P6.
Bentley TriForma A suite of tools providing enhanced 3D capabilities 08.09.04.97
InRoads/Rail Application for infrastructure design, offering 3D parametric modelling and 08.08.03.06
an tools for designing civil components in the context of the whole project.
MX International Digital terrain model creation and analysis 08.09.05.11

Bentley PowerCivil Design software offering civil engineers and designers a flexible 2D/3D tool 08.09.06.31
for land development and site modelling. PowerCivil runs standalone (no
CAD platform is required.) with native DGN and DWG file formats.
Pre-requisite A set of files needed prior to installing BIM applications 08.09.04.01
Version 2.0.3 12 of 224

MASDAR
5 Updating BIM documentation

As a member of Masdar‘s supply chain you are invited to contribute to the continuing
development of the BIM document suite. If you have any points you wish to make then please
contact Masdar‘s BIM Solutions Team Leader.
Version 2.0.3 13 of 224

MASDAR
6 Glossary
This section lists and defines the terms and abbreviations used in Masdar‘s BIM documentation
and lists primary references.
6.1 Definitions
Table 2 Definition of commonly used terms
3D model A model with objects having three-dimensional properties
3D reference Empty model file containing only referenced 3D model files

model file
3D Rendered images or animations produced from a 3D model for the purpose of visualising the project (see
visualisation also ‗rendering‘).
Annotation Detailing, such as text, symbols, dimensions, and flags, added to a model for emphasis and to provide
explanation.
Archive The ‗Archive‘ section of the common data environment (CDE) is for inactive or superseded material.
Such information provides a history of information transfers, enables knowledge retention and can be
used for legal and regulatory purposes or for delivery into Masdar‘s FM system.
Attribute A modelling concept used to represent properties of, and relationships between, entities
Author The originator of a model file, drawing or document
BS 1192 British Standard 1192:2007 Collaborative production of architectural, engineering and construction
information - Code of practice. (See reference in section 23). Establishes the methodology for managing
the structure, production, distribution and quality of construction information using a disciplined process
for collaboration
CAD file CAD technical drawing that has been given a name, filename and number
Cell A collection of one or more MicroStation graphical elements that can be placed, manipulated and deleted
as a single item. A cell is usually stored in a cell library.
Cell library File containing a collection of cells
Code Sequence of characters having defined meaning when interpreted in the context of the field in which it is
entered, used to concisely convey meta-data.
Colour table A file that specifies standard colours to ensure consistency.
Common data The CDE is a means to allow 2D and 3D information and data to be shared between all the members of
environment the programme team. It enables multi-disciplinary, multi-project design teams to collaborate in a
(CDE) managed environment where the build up of information follows the design sequence. The four areas of
the CDE are WIP, Shared, Issued and Archive. See section 23.2.
Components Components are essential when producing reports and schedules. Components contain product
information including cost, units of measurement etc. They are linked to the object definitions.
Compound A compound object is an element of a model, which consists of related features that can be drawn
object together and allocated a single object name and definition. See also ‗parametric object‘.
Container Named persistent set of data within a file system or application data storage hierarchy including, but not
limited to, directory, sub-directory, data file, or distinct sub-set of a data file, such as a chapter or section,
layers or symbol.
Dataset Collection of many intelligent pieces, organised and stored in XML files
Document Container for persistent information that can be managed and interchanged as a unit.
Document A technology that provides more control and better management of computer generated files. This
management technology adds enhanced file security, revision control, file descriptions, extended file names, and user
access privileges to the basic file directory management features of the computer operating system.
Version 2.0.3 14 of 224

MASDAR
Document A ‗document repository‘ is an electronic data management system (EDMS) system, project extranet or
repository folder hierarchy on a Windows file server.
Drawing file A 2D drawing contains a view of a model that is referenced into a ‗drawing sheet template‘ (blank drawing
and title block). Such drawings must always be considered to be static documents as they are drawing
renditions or snapshots of the designs model files.
Drawing title A framework, often containing the project team‘s logos, to show the drawing title, number, purpose of
block issue, status and revision information.
Element Another word for object.
Entity Another word for object.
Extraction A slice through a model in a represented in a 2D graphical form, yet retaining the ‗intelligent‘ data of the
model from which it came.
Families Used to group ‗parts‘ into logical groups of similar characteristics
Federated A highly efficient method of creating and sharing design information using multiple object-based 3D
modelling models based on individual hierarchical sub-models created by different project team members. Each
party uses a standardised model structure, object structure and layer structure to ensure that model
information can be exchanged and the data extracted as expected.
Graphic file A file format designed specifically for representing graphical images
Industry A vendor-neutral file format for exchanging 3D geometrical information and associated data.
Foundation
Class
Information Representation of data in a formal manner suitable for communication, interpretation, or processing by
human beings or computer applications.
Instance Occurrence of an entity at a particular location and orientation within a model.
Issue The ‗Issue‘ section of the CDE contains drawings or models which are snapshots of the shared
information taken at a specific time. They are compiled by referencing the relevant approved model files
into a drawing sheet that contains a title box and associated text attributes. A drawing rendition or model
snapshot is then created in a non-changeable format, for example a PDF file. Such a drawing rendition
will contain a snapshot of the coordinated multi-authored model files in the ‗shared‘ section of the CDE
Layer An attribute given to entities within CAD files that enables their visibility to be controlled. Further values
may be assigned to the attribute to enable control whether it can be edited or deleted. See also ‗level‘.
Level See layer
Marked up A paper or electronic drawing that has been marked up with comments from other disciplines or client.
drawing
Meta-data Information that describes or supports the central data
Model file A model file is a native CAD file that can be in the form of a 2D or 3D model
Model view A model within the ‗Model File‘ containing the design elements or the ‗Title Block‘
Object An item having state, behaviour and unique identity — for example, a wall object.
Object When a feature is drawn, the object definition will allocate the correct symbology and levels in both 3D
definition and 2D. It will define the ‗look‘ of the feature drawn in all views including fills and hatchings for
extractions. It will link the feature to data to produce schedules and reports later in the project
Originator The author of the models, drawings, data and documents.
Parametric A parametric object can be allocated its own definitions so that it can be manipulated to fit its purpose. It
object is recommended that parametric objects be used when a compound object would have too many
variables (for example doors and windows). Parametric objects may also be given non-graphical data
which although not apparent in the model, are accounted for in scheduling and report generating, for
example ironmongery for doors. See also ‗compound object‘.
Part A part is a feature of a model that has been assigned a part name and part definition.
Part name The part name is allocated within the part definition. It will be the alphanumeric Uniformat code and its
worded definition.
PDF drawing Rendition of a drawing file in PDF format
Version 2.0.3 15 of 224

MASDAR
Pen table A tool for setting line weights, thicknesses and additional symbology.
Plot drivers A tool for allowing a computer to run a plotter/printer with a specific set of instructions
Published A section of the collaboration environment for drawing renditions that have been approved as fit for a
specific purpose, for example fit for construction.
Purpose of States the purpose for issuing the document.

issue
Raster file Images made up of individual square coloured pixels to form an image.
Reference file A model file associated or linked with another model file. See also sub-model.
Reference A combination of 3D CAD model files used to create extracted 2D plans and sections.
model file
Rendering Image of a 3D model that looks more realistic than a wireframe image. Includes hidden line and surface
shading (see also ‗3D visualisation‘).
Rendition Renditions are ‗publications‘ in a form that enables the information to be viewed, printed and marked up.
This means that PDF files are ‗publications‘ that are in fact snapshots in time. Such renditions are
generated each time the file is prepared for ‗sharing‘ at regular milestones.
Revision Used to identify revisions to documents, drawing and model files.
Seed file A template for a design or drawing for the content of the data
Share The ‗Share‘ area of the CDE is where data is shared with other members of the project team when it has
reached a status of ‗fit for coordination‘.
Sheet view A sheet model containing the complete drawing.
Solids 3D elements with a thickness and solid all the way through. They may be curved or planar, eg a cubed
surface would be like a cardboard box, a cubed solid would be a solid block.
Standard font An agreed set of font types and sizes to be used for the project.
Standard A common layering convention used by the project team.

layering
convention
Status Defines the ‗fitness‘ of information in a model, drawing or document; for example ‗fit for coordination‘.
Sub-model Model included as an instance in another model. See also reference file.
Symbology The assigned visual characteristic allocated to vector elements.
UniFormat Unified classification system for the construction industry (see reference in section 9.3).
Work in The ‗WIP‘ area of the CDE is where team members carry out their own work using their organisation‘s
progress (WIP) software systems. The organisation is responsible for the quality of the WIP information and should
ensure that appropriate checking and review processes are in place.
Zone A zone is a manageable spatial subdivision of a project. A zone is defined by the project team as a sub-
division of the overall project that allows more than one person to work on the project, floor plan or
staircase etc. Each zone or subdivision is a reference file. When one or more referenced files are viewed
the full floor plan or site plan may be represented.
Version 2.0.3 16 of 224

MASDAR
6.2 Abbreviations
Table 3 List of abbreviations
2D Two-dimensional
3D Three-dimensional
ACS Auxiliary coordinate systems
BIM Building information model
CAD Computer aided design
CDE Common data environment
CSV Comma separated variable (as in CSV file)
DGN Proprietary Bentley drawing format
DTM Digital terrain model
DWG Proprietary Autocad drawing format
EDMS Electronic document management system
FM Facilities management
GIS Geospatial information system
IAI International Alliance for Interoperability, now known as BuildingSMART
ICT Information and communications technology
IFC Industry Foundation Class.

Not to be confused with ‗Issued For Construction‘.
NCS National CAD Standard (see reference in section 9.3)
PDF Portable Document Format
SMP Standard method and procedure
WIP Work in progress
XML Extensible mark-up language (as in XML file)
6.3 References
National CAD Standard
http://www.buildingsmartalliance.org/ncs/
British Standard 1192

http://shop.bsigroup.com/en/ProductDetail/?pid=000000000030163398
UniFormat
http://www.uniformat.com/nistir-6389.html
Technical learning paths for Bentley software

http://www.bentley.com/en-US/Training/Products/Resources/Courses/Find+Courses.htm
Version 2.0.3 17 of 224

Information and data management strategy
MASDAR
Chapter 2
Information and data management strategy
This chapter describes the strategy for producing and controlling project data through the life of a
Masdar project. It describes the framework to create integrated and coordinated designs that will
facilitate multi-disciplinary collaboration, and help to ensure that project data can be used by
business systems as the foundation for operation and maintenance though the asset life cycle
Version 2.0.3 19 of 224

MASDAR
7 BIM process
7.1 Introduction to BIM
Building information modelling (BIM) is a way of working that can help to eliminate much of the
waste that is inherent in traditional design-build-operate processes. BIM integrates a virtual
description of a building with all the data that contribute to its ongoing function. Masdar BIM
processes will capture and manage information about a building and then present that information
back as conventional drawings or in any other appropriate way – as a 3D model, for example –
when required
There are many specialised programs that can contribute to performing parts of the construction
process, ranging from simple word processing to advanced calculations and analysis, many of
which can handle 3D construction information. Therefore, it is important that 3D models are
prepared in a format that can be exchanged between the tools used by Masdar‘s partners.
BIM is not a single software product – it is a process that uses multiple software tools that are
appropriate to the particular business processes. BIM data is stored in a format that lets it be
shared between the different applications used by project teams throughout the building life cycle
(figure 1); it is the process of piecing together intelligent virtual objects to create a model of a
building that becomes a visual database containing information about each element. The primary
features of Masdar BIM are listed in table 4.
Paul King
Bentley Systems
+44 (0)7966 162 695
Figure 1 Life cycle BIM process
Version 2.0.3 20 of 224

MASDAR
Table 4 Primary features of Masdar‘s BIM processes
Requirement Masdar BIM will . . .
3D design and Enable discipline-specific design teams to create their own 3D models effectively and efficiently,
modelling and allow the individual models to be combined into a single aggregate model. Methodologies are
neutral as to software platform and the main aim is to develop good designs – not to introduce
advanced technology.
Coordination and Allow 3D models to be combined in order to enable designers, design managers and construction
clashing teams to perform coordination and clashing checks interactively and to analyse the accuracy of
design. This will help to ensure that all components are properly spaced for installation, and to
avoid costly change orders.
Visualisation Be capable of creating images, animations, simulations and virtual reality outputs directly from 3D
models in order to convey project information to stakeholders.
Project scheduling Enable 3D models to be used to provide insight into project planning by linking to schedule
information managed in applications such as Primavera P6. Users will be able to visually explore
alternatives and create cost effective and safe construction scenarios by visualising schedule
information and animating 3D models.
Data extraction Incorporate tools that extract data for re-use in project documentation (such as specifications) and
third party applications (such as energy analysis), as well as exporting raw data to create, for
example, schedules of components and costs. At project handover facilities management data will
be exported from BIMs into the enterprise facility management system..
2D drawings Be used to generate production information, such as 2D drawings, quickly and efficiently, using
consistent representation and symbology.
7.2 Federated BIM approach

The Masdar modelling approach is not to build a single model of the whole city but to provide an
environment where individual component model files can be brought together and viewed, used
and analysed in a master model. This approached is termed ‗federated‘ and it allows data from
multiple sources to be integrated into a single view for the tasks of coordination, analysis and
drawing production, and permits models to be used across all disciplines including civil,
infrastructure and building.
Figure 2 illustrates architectural, structural, and building mechanical disciplines each created
separately through a design collaboration environment. Figure 2(d) shows a master model
composed of the separate discipline models, accurately located using real-world coordinates,
enabling the viewer to ensure that each component is correctly positioned without interfering with
other building elements.
(a) Mechanical (b) Structural (c) Architectural (d) Combined model
Figure 2 Creating federated models in a coordinated environment
Version 2.0.3 21 of 224

MASDAR
Data is finely granulated and structured to ease its reuse, and no two participants will necessarily
edit the same model. Masdar‘s CDE (based on Bentley‘s ProjectWise) brings all the pieces
together, providing the ability to produce traditional drawings or documents from multi-authored
data.
This approach is important to Masdar because it lets different people do many different things
simultaneously, no matter where they are. It is a highly efficient method of working that makes it
possible to do large, complex and detailed projects, and get good performance in the software.
7.3 Bentley software applications

Supply chain partners are required to produce their design solutions using building information
modelling, and to submit design deliverables in native Bentley (.DGN) format. Software licenses
for Bentley tools will be provided to project teams by Masdar, as required. A list of preferred
software is given in section 4.
7.4 Benefits of using BIM

BIM has two major advantages over traditional 2D CAD. Firstly, BIM creates and manages not
just graphics, but also data – data that allows the automatic generation of drawings and reports,
design analysis, schedule simulation, facilities management, and more – ultimately enabling the
project team to make better-informed decisions. Secondly, BIM supports distributed teams so that
people, tools, and tasks can effectively share information through the building lifecycle, thus
eliminating data redundancy, data re-entry, data loss, miscommunication, and translation errors.
Masdar‘s BIM approach will provide benefits for each project participant (table 5). The actual
benefits will vary according to the type and complexity of project, and the degree of integration
between design, engineering, analysis, construction, and operations activities.
Version 2.0.3 22 of 224

MASDAR
Table 5 Principal benefits of a BIM approach to project participants
Participant Typical benefits
Masdar Improved design quality

Better performing building (systems coordination, engineering analysis and sustainability)
Fewer change orders during construction
Better certainty of completion on time and opportunities for reduced timescales using digitally
assisted fabrication and off-site fabrication
More efficient handover process, with high quality digital data for operations and maintenance
Risk reduction
Design manager Better overview of the relationship between different disciplines

Ability to identify clashes while it is cheapest to resolve them
Better ability to assess whether the proposal meets the requirements for form and function
Project manager Reduced project risk

Easier to obtain approval of design from relevant statutory authorities
Make better-informed decisions earlier in the project process
CAD manager Easier to verify the coordination of submitted designs

Better coordination of building data with GIS data
Architect Can develop more solutions more quickly

Can use other disciplines‘ models
Designs can be better visualised and presented to the client
Structural engineer Better coordination of service runs and penetrations, including holes in load-bearing structures
Visualisations of details, enabling better communication of design
Ability to perform static, dynamic and fire technology simulation and design
Services engineer Greater ability to ensure consistency of all building services

Improved ability to clarify and coordinate service runs
Ability to simulate and design lighting, sound, environment, etc.
Main contractor Better construction planning, management and execution.

and sub-contractor Better logistics planning and simulation of installation
Better control of quantities and their distribution by contracts.
All participants 3D models and visualisation contribute to better communication and collaboration between all parties
3D models allow better coordination across all disciplines
Makes design changes less time-consuming and easier to quality assure across disciplines
Better decision making
2D drawings can be produced more quickly and more accurately from 3D models
The use of 3D models allows complex solutions to de developed and communicated more easily
Version 2.0.3 23 of 224

MASDAR
8 Collaboration process
8.1 Introduction to collaboration
The effective communication of high quality information between design team members,
manufacturers, constructors and operators is essential for the satisfactory realisation of Masdar‘s
projects. The principles for information sharing and common modelling are applicable to all types
of construction activities.
The project requirements are defined in chapter 6 (Data Management Guide) and chapter 7 (Data
Management Standard).
Masdar has developed processes and documentation for controlling building information and data
using Bentley‘s ProjectWise and based on British Standard 1192:2007, which requires the
following procedures to be adopted (see also section 24).
(a) A project ‗standard method and procedure‘ must be agreed and committed to by all the
relevant parties who will be involved in a project.
(b) A ‗common data environment‘ (CDE) approach will be used that allows information to be
shared between all members of the project team.
(c) A suitable information hierarchy must be agreed for each project that will support the
concepts of the CDE and the lifecycle coordination environment.
(d) Roles and responsibilities must be agreed, in particular the responsibility for coordinating the
work of the various design disciplines.
(e) The team must agree the project coordinate system and how spatial co-ordination will be
carried out (see section 19).
(f) Document naming conventions must be adopted so that relevant information can be
identified using file names, and reference codes for the status and revision of documents
must be agreed (se section 25.2).
(g) All teams must adhere to the systems, tools and standards defined for each project.
8.2 Benefits of effective collaboration

Masdar‘s collaboration system connects people and information across project teams – no matter
where they are located – to help them improve quality, reduce rework, and meet project
deadlines. The features and benefits of the system are listed in table 6.
Version 2.0.3 24 of 224

MASDAR
Table 6 Primary features of Masdar‘s technical coordination system
Requirement Masdar’s technical coordination system will . . .
Connecting - Connect multiple teams and offices

project teams - Federate all project data regardless of storage location
- Cache distributed files locally for fast access
- Provide appropriate stakeholder access
- Ensure that ownership of information remains with the originator although it is shared.
Managing - Enforce common standards for all design information across the programme
standards - Cache workspaces locally for distributed teams
Managing - Manage all reference file relationships

reference files - Enable a user to query all references attached to a drawing/model
- Automatically deliver all attached reference files when the master CAD/3D file is checked out
- Enable Any number of documents can be generated from different combinations of model files
Protecting - Share files securely across organisational boundaries

engineering - Define who can view and edit project content
content
- Manage access security
- Control group, user and document level access
Streamlining - Adopt a project-centric approach to information management

access - Index documents and engineering components
- Find documents and content using powerful search capabilities
- Create and manage file versions
- Track what happened to a document throughout its lifecycle
- Make documents available in multiple file formats
- Save time finding, validating, and accessing project information
- Enable finely granulated and structured data to be reused easily and efficiently.
Improving project - Make it easier to do things correctly rather than incorrectly

quality - Create, manage and deliver content in accordance with project requirements
- Satisfy relevant codes and standards (national and international)
- Improve the quality and consistency of all project deliverables
- Easier and better spatial coordination
- Design information can easily be reused for construction planning, estimating, cost planning,
facilities management and other downstream activities.
- Reduces the time and cost of producing coordinated information
- Reduce project risk with a single source of truth for all project information
Managing audit - Check what happened to a particular document, when it arrived, who approved it, when it was
trails deleted, who last edited it, where it is located, etc
Automated - Connection to other databases and stores

processing - Integration with third-party products
- Disaster recovery and back up procedures
Version 2.0.3 25 of 224

MASDAR
9 Masdar procurement process

Masdar‘s BIM and collaboration methodologies and documentation support the organisation‘s
procurement approach, as described below (see also section 13).
Pre-design
To allow the design team to collect all the required data for the project and present a consolidated
project design brief to Masdar.
Concept design
Divided into preliminary concept and final concept, enables the design team to cast a vision for
the project and develop a concept that responds to the key drivers of the project in a holistic and
sustainable way.
Schematic design
The design team will develop the approved concept design, investigating alternative strategies,
systems, materials and equipment. The design team may be required to accelerate early and
enabling works packages in advance of the completion of the stage. Masdar may stop the design
activities at the end of this stage and issue the project as a design-build tender package.
Detailed design
The design team will incorporate the selected systems, materials and equipment into the frozen
design and produce a detailed design package that fully describes the project to a level suitable
for tender. The design team may be required to accelerate early and enabling works packages in
advance of the completion of the stage. Masdar may stop the design activities at the completion
of this stage and issue the project as a fast-track tender package.
Construction documents
The design team will produce a full construction document package to be issued for construction
including drawings, specifications, calculations and reports fully detailing all systems, materials
and equipment.
Tender
Preparation and collation of tender documentation in sufficient detail to enable a tender or tenders
to be obtained for the construction of the project in a way that will meet project objectives.
Construction
Implementation of the building contract to practical completion. The construction team will
provide handover information and data to Masdar that is correct, consistent and complete.
Defects liability
The facility is handed over to Masdar for operations. Any defects will be tracked, managed and
rectified to ensure that the facility can be operated efficiently, effectively and sustainably.
Version 2.0.3 26 of 224

Design information modelling guide
MASDAR
Chapter 3
Design information modelling guide
This chapter explains the basic principles of a common coherent 3D working method for all
parties employed on Masdar projects. It describes the 3D modelling concept, model types and
information levels which explain the detailing of the models.
Version 2.0.3 27 of 224

MASDAR
10 Modelling concept
10.1 General principles
The Masdar methodology is based on object-based working, enabling project teams to work on
3D geometric models with associated data. It must be possible to link attribute data to objects in
building models so that they can be used for producing outputs such as 2D drawings, component
lists and room schedules. The modelling methodology adopted by Masdar creates certainty in
the consistency of disciplines‘ 3D models, helping to minimise costs and conflicts before, during
and after construction.
It should be noted that not all project information and data will necessarily be contained within the
3D models; for example, there will be some data, specifications and reports that are created and
maintained outside the model and referenced from it. Also, the design process will contain
activities that are separate from the building model or are only partly supported by it, such as the
preparation of a risk assessment.
Masdar‘s modelling approach supports project processes from initial planning through to
operation and maintenance, focusing on the following activities: 3D modelling, coordination and
clashing, exchanging information and data, data extraction, simulation and visualisation. Figure 3
illustrates the high level activities of Masdar‘s 3D working method.
Contractor
Building services
Masdar engineer
Main activities of the modelling process
Visualisation Simulation
Aggregate
3D model Architect
Paul King
Bentley Systems
Coordination Exchange +44 (0)7966 162 695
Data Documentation
Discipline model exchanged with other participants
Supplier Geospatial team
Structural engineer
Figure 3 High level view of the project modelling approach
Version 2.0.3 28 of 224

MASDAR
10.2 Modelling process

The discipline teams each model their part of the project using the 3D CAD systems agreed for
that scheme and other specialised applications they use and/or have agreed with the other
parties. The discipline models undergo successive detailing throughout the design process as
the design information is determined. The extent of object types and object attributes depends on
the information level described by the discipline model at a given time in the design process, and
thereby expresses an increasing information level during the design process.
The number of information levels can vary from project to project depending on factors such as
the type of contract and the project organisation. The project milestones, their content and
thereby the information levels of the discipline model will be agreed by the parties at the start of a
project. A detailed explanation of information levels is given in section 5 of this document.
Each party works with a standardised model structure, object structure and layer structure to
ensure that model information can be exchanged and the data extracted as expected in relation
to general performance specifications, or as otherwise agreed by the various parties at the outset
of a project.
10.3 Types of model

10.3.1 General concept
A model is an overall concept for the models that contain those of the project‘s 3D objects that
can be represented in model form. The level of detail in the models is built up successively as
data becomes fixed through the project process. The models are characterised by having a
common standardised structure described in Masdar‘s CAD Standard (chapter 5). There are two
main model types: discipline models and aggregate models (figure 4).
A discipline model is a model prepared by and containing design information associated with a
specific professional discipline such as architecture or civil engineering. As the discipline models
must be able to be exchanged and shared between the project parties, they must comply with the
requirements specified in chapter 5. An aggregate model is a one that assembles design
information from two or more discipline models. The aggregate model is an important
coordination tool for the project.
Paul King
Aggregate 3D model Bentley Systems
+44 (0)7966 162 695
Discipline models Discipline models
Discipline Discipline
sub-models sub-models
Figure 4 High level view of the project modelling approach
Version 2.0.3 29 of 224

MASDAR
10.3.2 Discipline models
10.3.2.1 General principles
Discipline models are built up within individual disciplines with a common design structure and
common rules for model building and object handling. This ensures that each party has a well-
defined discipline area of responsibility with well-defined interfaces, and that the parties can
develop and exchange design data through the project process; this will achieve the greatest
possible re-use of data and security during exchange.
Therefore, the modelling concept reflects the traditional allocation of roles and traditional
professional boundaries, and will also be able to adapt to new roles and boundaries as they
evolve.
The discipline model follows the individual party through the design process up to the time when it
is delivered, or when the responsibility is transferred to another party. The digital version of a
discipline model is as contractually valid as the drawings and other extracts from it.
Each party selects the software to be used for a given task based on the project-specific
requirements, and as agreed by all parties at the start of a project.
10.3.2.2 A master model
A master model is a particular way of using the discipline model during the initial phases of the
project. Instead of each discipline creating their early discipline models, one of the disciplines is
tasked with building the geometrical requirements of the other disciplines into its model. This will
typically be the architect, who would be given responsibility for incorporating the sizes of
structures and service zones as necessary based on information from the relevant discipline.
The purpose of the master model is to create consistency between disciplines without extensive
flow of models between the parties during the initial phases of the project. Later in the project
process the master model will be used as the basis for by individual disciplines to create their own
models (and the master model will be replaced).
10.3.2.3 Information levels
The 3D working method is founded on the principles of evolving levels of detail. Each party will
add information to the appropriate discipline model at a progressively higher level of detail
through the project and thus work with rising information levels. The starting point is the concept-
type model that could be developed at the project briefing stage, with the lowest level of detail.
The modelled objects are refined geometrically and functionally and performance-based object
attributes are added during the project stages. During construction the performance-based
attributes are replaced with specific as-installed product details that can subsequently be used for
operation and maintenance.
The discipline model is locked on transition from one project stage to the next, with appropriate
meta-data to indicate the information level. This information level is the starting point for
modelling in the next stage. The Masdar 3D working method uses eight information levels that
follow the typical Masdar project stages; these could be adapted to suit particular project
requirements but only under the direction of Masdar.
Information levels are detailed in section 5.
Version 2.0.3 30 of 224

MASDAR
10.3.2.4 Object types and attributes
The discipline model is built up of uniquely identified 3D objects. Instances of objects inherit
characteristics from the object type. Throughout the project process the objects will be given new
and/or more precise attributes corresponding to the current information level of the discipline
model; this is described in chapter 4 (Element Coding Standard). Each discipline model contains
the object types for which that discipline is responsible.
Allocation of object attributes can occur either in the CAD system‘s internal data structure or via
an external database connected to the CAD system. Detailed requirements for the scope and
content of objects are given in chapter 4.
In the early project stages there are likely to be design details that cannot be represented in a 3D
model as objects. In such cases a solid should be created to represent the object to which the
relevant attributes can be attached. This will ensure that the object (and its data) is included in
automatic extracts from the 3D model.
10.3.2.5 Format of the discipline model
The discipline model may be contained in a database, in a single file or divided into several files
that are coordinated in a reference file structure. The concept of dividing files into different zones
is addressed in chapter 6. A zone is any useful physical sub-division of the project within a level
or location into manageable sizes for data transmission and to allow a number of designers to
work on the same level at the same time. Splitting the project into zones also helps to limit the
size of model files to prevent reduced performance of software.
Individual team members may require alternative zones sympathetic to their individual needs.
Zones are not drawing areas and do not relate to the amount of the project shown on any given
drawing or model. A zone may be based on an aspect of design such as structure cores,
specialised function, building systems or elements such as cladding. Different disciplines‘ zones
can interface in different ways and one or more model files can relate to a zone.
Detailed instructions on the rules and common structure for the discipline model are given in
chapter 5.
10.3.2.6 Ownership of discipline model
Each party is responsible for the discipline model it creates. The models must be structured and
specified to an information level that ensures that it is possible to perform tasks such as
producing drawings and extracting data that correspond to the project stage. For certain types of
3D object the responsibility might need to be shared; for example, in the case of an external wall
the load-bearing inner leaf would be the responsibility of the structural engineer and the outer wall
would be the responsibility of the architect. Generally, the responsibility would be as follows.
- The party that prepares a discipline model is responsible for both structure and data content,
and for extracting data and information (such as drawings and quantities) from the model.
- The party that uses another party‘s discipline model for reference is not responsible for the
content of the reference model but is responsible for correct interfacing. For example, a
structural engineer who references an architectural floor plan to assist with designing the
column layout would not responsible for the accuracy of the architectural design. Or a
drainage engineer may use a surveyor‘s digital terrain model (DTM) as a reference for the
Version 2.0.3 31 of 224

MASDAR
levels of the drainage runs; he would maintain the drainage model (either graphics or a
database, depending on the application) but would make no changes to the DTM.
- A party to whom another party‘s discipline model is transferred takes over responsibility at that
point for the structure and content of the model. For example, a contractor who receives a
design model from Masdar will be responsible for maintaining the model during construction,
replacing performance-based data with specific product-based data at the time of installation,
and transferring a true as-built model back to Masdar at project handover.
10.3.3 Aggregate models
10.3.3.1 Overview
An aggregate model is an assembly of two or more discipline models that helps to ensure project-
wide coordination and data, and is the first step towards creating a single integrated project
model. Requirements for preparing such models will be agreed at the start of each project. They
can be prepared concurrently with discipline models and exploited to produce outputs such as
clash analyses, visualisations and schedules of components. They have two main functions.
(1) It minimises conflicts and ensures consistency between the individual parties‘ discipline
models. The aggregate model is a tool to ensure the quality of design documentation overall
and by coordination within each party.
(2) The aggregate model is a communication tool to show the structure and stage of the overall
design to the other parties, and to those who are not directly involved with modelling (such as
the project manager and City Management).
10.3.3.2 Access rights
As significant functions of the aggregate model are coordination and communication it must be
easily accessible to relevant parties. It could be held on a single server by one of the parties, on
a common project web or, most effectively, on a technical coordination system (such as
ProjectWise). Importantly, the latter system would ensure the integrity of reference files.
At the start of a project the team would create a project-specific matrix to define access rights by,
for example, user name, role, organisation and project stage.
10.3.3.3 Format of the aggregate model
The model could be prepared using the project‘s dominant proprietary CAD tool or a neutral
common format such as IFC (industry foundation class). However, at the time of writing the IFC
format is not sufficiently developed to support Masdar modelling requirements. The modelling
format must be agreed at the outset of each project.
10.3.3.4 Ownership of aggregate model
The lead consultant will be responsible for preparing the aggregate model unless agreed
otherwise. Where the model is used for analyses and extracting data and information then the
responsibility will be that of the party performing such tasks. Responsibility for the content and
modification of each constituent discipline model remains with the party that owns the discipline
model.
Version 2.0.3 32 of 224

MASDAR
11 Sharing project information and data

11.1 Design coordination and project collaboration
Masdar requires a system that delivers technical BIM information (3D models and data) in a
controlled and managed environment, permitting sharing without loss of reference file or
component integrity, and capable of referencing models of different origins and ownerships into a
single project model. The system must also be able to register and control workflow states in a
coordination environment with sharing across project participants.
It is applicable to all parties involved in the preparation and use of information throughout the
project lifecycle, and the principles for information sharing and modelling are equally applicable to
building and civil engineering projects.
This chapter should be read in conjunction with chapter 6, which describes how project data
should be produced and managed in a consistent format through the life of a Masdar project.
The methodology provides a framework to create an integrated design that will facilitate multi-
disciplinary collaboration during design and construction, and provide rich data that can be used
through the entire life cycle of an asset.
11.2 Exchanging 3D models

11.2.1 General requirements
Chapter 6 explains the process for sharing information and model files between the various
parties. Agreement must be reached at the start of a project regarding which discipline models
will be made available to others, and when, the approval procedures and quality assurance
status. The discipline model files are exchanged primarily as references for other parties, to
avoid redundant information in the project‘s discipline files. As a minimum models will be shared
at the completion of each project stage or other agreed milestones.
It is important for the parties to agree how to manage the data contained within a model during
and after the exchange process.
Each discipline model will be in a program-specific format and exchanges from program to
program must be carried out securely. If two parties conduct their modelling with the same CAD
system then the exchange should use the lowest common version number. Models could also be
exchanged in different CAD formats providing there is an appropriate translator available. If it is
agreed to use a neutral format the IFC should be used. However, at the time of writing the IFC
format is not sufficiently developed to support Masdar modelling requirements.
The greater the extent to which the parties need to exchange both 3D geometrical information
and object data, the more important will be the choice of modelling software and technical
coordination system that support intelligent exchange. At the start of each project it must be
agreed which software tools (and versions) will be used for the exchange process, and when
models will be shared. There are three main purposes for exchanging BIMs: reference,
processing and transfer and these are described below.
Version 2.0.3 33 of 224

MASDAR
11.2.2 Model for reference
In this case, a model is exchanged with another party to function as a reference file for that
party‘s modelling. This will occur frequently in a design process and can be automated by
working on a common technical coordination system (providing it can manage reference files).
The responsibility for consistency of the reference model remains with the issuer and the recipient
is responsible for working with the correct version. An example would be where the structural
engineering team provides a model to the building services team to assist the layout of
mechanical and electrical systems.
11.2.3 Model for processing
In this case, a discipline model is handed over to another party for use in a task-specific model,
such as building simulation. The issuer is responsible for the model content on handover, after
which the recipient is responsible. Examples would be when a building services engineer gives a
model to a specialist designer to perform an energy consumption analysis, or where an architect
gives a model to a specialist visualiser to create renderings or animations.
11.2.4 Model for transfer
In this case, a discipline model is transferred to another party for post-processing to create a new
discipline model. The issuer is responsible for the content on transfer, after which the recipient is
responsible. Here, the principle of ‗custodianship‘ of the model is important.
As an example, when a consultant might pass a design model to a contractor for use on site. The
contractor would become the custodian of the model until it was returned to Masdar at handover
as an as-built model for use in operations. The contractor would have to ensure that data
identified as being required for operations (added during the design process) was preserved
through the construction process. For example, a chiller might contain a piece of design data
stating its spare capacity and, although this would not help the contractor to construct the
building, it would be important to preserve the data because Masdar‘s operations team would use
it to design future modifications to the building.
Version 2.0.3 34 of 224

MASDAR
11.3 Quality assurance

11.3.1 Quality policy
Masdar‘s quality policy will help to ensure that models are maintained over their lifetimes. At the
outset of any project all aspects of the project‘s graphical database should be formulated by the
authors of the data with a view to satisfying end users. Early quality planning will help to ensure
that all demands made on the models over their life can be met effectively and realistically.
The onus is on originators to ensure that information and data comply with the necessary
standards. Model files will be checked using appropriate software, and any files which fail will be
returned to their originator with a report on non-compliance.
Models, which need to be maintained over long periods, might be subject to major and minor
updates and the same quality standards should be applied to these amendments in order to
ensure model integrity over time.
Masdar quality standards should be regularly reviewed, for example at the adoption of each new
software tool release. When models are to be extended to cover new topics then consideration
should be given to the strategy adopted for structuring the new information and the way it will be
integrated. Sustained data quality requires methodical checking at the time of input and
persistent discipline when changes are made. Systematic data quality checks will be performed
by Masdar and its supply chain partners, which should include:
a) Elimination of spurious data outside normal file extents
b) Checks on file setup parameters
c) Testing of file/layer allocations by switching on and off files/layers
d) Listing of files and layers
e) Elimination of information which is not to scale
f) Purging of all unnecessary data
g) Elimination of references to un-checkable files (such as renditions)
h) Formats that do not maintain dimensional integrity should not be used
i) Attribute validation consistency
j) Other content checks.
11.3.2 Data exchange
To avoid problems associated with data exchange, participants in the process should:
a) Follow the recommendations given in the Masdar BIM documentation and associated
publications
b) Agree as early as possible which data should be exchanged, when and in what format
c) Agree the version of format to be used for data exchange
d) Establish procedures to test, monitor and report the accuracy of data transfer, and conduct
initial data transfer trials
e) Agree a method of recording each issue and receipt of digital data, and what constitutes an
acceptable transfer.
Version 2.0.3 35 of 224

MASDAR
12 Using discipline models

12.1 Multiple uses for models
Discipline models that are prepared using a common structure with common rules for model
building and object handling enable project parties to create fully detailed and well coordinated
design solutions. Such models, and the data they contain, can be used throughout the project life
cycle to create and manage the project deliverables, and so achieve the greatest possible re-use
of data. The principal design stage outputs from 3D models on Masdar projects are shown in
figure 5 and described in the following sections. This process is equally applicable to civil
engineering and site-wide infrastructure elements.
Architecture Structural Building services Aggregate model

Discipline models
Discipline Discipline Aggregate

models models model
exchanged exchanged formed from Paul King
King
Paul
between all between all discipline Bentley Systems
Systems
Bentley
parties parties models +44 (0)7966
+44 (0)7966 162
162 695
695
Drawings generated Drawings generated Drawings generated Drawings generated

from discipline 3D model from discipline 3D model from discipline 3D model from discipline 3D model
and/or aggregate model
Drawings
Shadow analysis Structural analysis Indoor environment Project schedule

simulation
Analysis
Component and Component schedules Component schedules Aggregate project data:

space data components, quantities,
Data extract
areas, etc.
High quality rendering Interactive walk-through Interactive analysis Virtual reality using
Visualisation
(internal and external) of structural solution of plant rooms Google Earth
Architectural model Structural model M&E model Automated clash reports

from aggregate model
Coordination
Interface M&E and structural

coordination clash detection
model model
Figure 5 Typical design stage outputs from discipline and aggregate models
Version 2.0.3 36 of 224

MASDAR
12.2 Coordination and clashing

12.2.1 Overview
The purpose of coordination and clashing is to check the various discipline models for issues
such as collisions, duplication and overlaps. The process is vital to ensuring the quality of the
construction information and data. The checks must ensure that:
- there are no clashes between building elements (such as pipes clashing with steel beams)
- there are no redundant building elements (such as the same column existing in two model
files)
- building elements adjoin each other according to permitted tolerances
- clearances are sufficient to install, operate and maintain equipment and systems.
BIM clash detection tools enable designers and contractors to automatically apply highly
configurable rule-based procedures to check for clashes between building elements. For
example, it can be easily checked whether two ducts clash with each other, or whether the
mechanical system clashes with the structural system. Clash detection can be performed at any
level of detail and across any number of trades or systems, either sequentially or concurrently.
Rules can also be used to differentiate between hard clashes (such as a pipe cutting into a duct)
and soft clashes where tolerances are defined (such as an overlap between duct insulation) or to
ensure clearances around components for maintenance access.
12.2.2 Design coordination
A virtual 3D model provides an effective and efficient means of coordinating the design elements
on a scheme. Although design teams claim to perform coordination and clash detection it is a
task often left to second- and third-tier construction partners. Individual design disciplines can
check their own work for clashes and coordination problems, and the lead consultant (or other
nominated party) can check the overall design coordination. Effective design coordination using
3D models provides major benefits to design teams:
- Clash free, fully coordinated design model (saving the effort of repeated re-design)
- Lower design cost (design is done once only, and done right)
- Less burden on the design team during construction (fewer queries referred by the
contractor).
The high level process for design coordination is shown in figure 6. Although this figure shows
the process for coordinating building elements it is equally applicable to civil engineering and site-
wide infrastructure,
Version 2.0.3 37 of 224

MASDAR
Architect
Structural engineer MEP engineer Masdar
(lead consultant)
Prepare discipline Prepare discipline Prepare discipline

model(s) model(s) model(s)
Return non-
Fail Fail Fail compliant
file(s) to
QA QA QA discipline(s)
check check check for correction
Modify Modify as necessary
Modify
discipline discipline discipline
Pass model Pass model Pass model
Upload discipline Upload discipline Upload discipline Fail

model into technical model into technical model into technical
coordination system coordination system coordination system
QA
check
Prepare aggregate
Pass
model(s)
Discipline
model(s)
stored on
technical
coordination
Paul King Paul King system.
Bentley Systems Bentley Systems
+44 (0)7966 162 695 +44 (0)7966 162 695
Fail Fail
Perform master
Clash Clash
clash analysis
test test
Clash Pass Pass

Fail
test
Model version Model version

Pass signed off signed off
Model version
signed off Signed off
aggregate
model(s)
Signed off stored on
aggregate technical
model uploaded coordination
to Masdar system
Figure 6 High level generic processes for design coordination and clashing, where the architect is responsible
for preparing the aggregate model and managing overall design coordination.
Version 2.0.3 38 of 224

MASDAR
12.2.3 Construction coordination
The construction team will perform clashing as part of the process of creating shop drawings
and/or shop models. This will ensure that the construction remains clash-free as the contractor
selects particular components and systems for installation. Ideally the contractor would work
solely with 3D models and the associated project data to create shop detailing for installation.
In practice, however, most contractors use a combination of 3D and 2D working methods, as

shown at a high level in figure 7. The contractor would work traditionally to create 2D shop
drawings for construction and installation, using its knowledge and experience to create
coordinated 2D material. The contractor‘s BIM team would then create the corresponding 3D
model using outputs from the shop drawing team in to fulfil Masdar‘s requirement for a 3D as-built
model (with associated data) for handover at the end of construction.
Models must be prepared to an appropriate level of detail with sufficient details for pipes, ducts,
supports, attachments and other components so that clashes can be accurately detected and that
the contractor has the basis for a true as-built model for handover to Masdar.
Design Contractor‘s Contractor‘s shop

Masdar
consultants BIM team drawing team
Download published 2D drawings and 3D models Technical coordination

system (published
information)
Paul King
Bentley Systems
+44 (0)7966 162 695
Create 3D model for Create 2D shop drawings Upload models and

Paul King
construction based on tender drawings drawings and other
Bentley Systems
deliverables to 695
+44 (0)7966 162
technical coordination
Incorporate shop drawing Send shop drawings to system.
details into 3D model 3D modelling team
Perform coordination and

clash check
Fail
Review
Pass Pass
Amend 3D models,
QA Fail
2D drawings and Create final shop Amend 2D shop drawings
other deliverables check
drawings from 3D model
as needed and keep model current
Return non-
Submit Contractor and/or subcontractor
Who will compliant
revised
modify? deliverables
information to design
and data to Design consultants
Masdar consultants
Figure 7 High level processes for coordination and clashing during production of contractor‘s shop drawings
(where the contractor works traditionally in 2D alongside an internal BIM team)
Version 2.0.3 39 of 224

MASDAR
12.3 Data extraction

12.3.1 Data extraction methodology
All building elements in models will have associated attribute data, some of which will be tagged
directly to the 3D object and some that will be stored in an external database. This combination
of tagged and externally-referenced data is termed the ‗object data‘. Tagged data will be entered
only by the originators of the respective 3D models whereas externally-referenced data could be
added by any party with appropriate permissions. For example, during the design phase the
mechanical services modeller would tag a pump with the name of the preferred manufacturer;
during the construction phase the contractor would add specific data, such as the serial number,
to the external database.
The data requirements are detailed in chapter 4 (Element Coding Standard). Every object must
be uniquely identified (with a product-allocated reference and the file name), assigned a
classification based on the UniFormat standard and given a geometric location (x, y and z
coordinates). The data can then be used in a variety of ways to add value to project teams
through the building life cycle, for example:
- cost estimating
- calculating the quantities of building components
- populating Masdar‘s electronic facility management system with maintenance data.
Extracted data can be presented either as a detailed list or as a summary list, to suit the particular
use. A detailed list presents every occurrence of every object as a record in the extract; this
format is used when detailed information about every object is needed, such as when the data is
to be transferred to another application for analysis. A summary list presents each occurrence of
each object type as a line in the spreadsheet together with summarised quantities; this format is
suited to where the information will be used for manual processing. Masdar‘s preferred data
extract format is Microsoft Excel. Masdar also requires an industry foundation class (IFC)
extraction to be made from each model as a deliverable at the end of each project phase (IFC2x3
format), together with a native Bentley BIM model file (DGN format). Figure 8 illustrates the
typical data extraction types.
Geometry plus data in native

modelling format Concrete walls - file name
- unique ID
Data export configured to suit Wall 1 4.6m3
Wall 2 5.8m3 Paul King
Paul King - classification
intended use Bentley
Bentley Systems
Systems - overall height
Total 10.4 m3 +44 (0)7966 162 695
+44 (0)7966 162 695 - overall width
Source BIM - thickness
- etc
Sub set of data

For input to and geometry
For manual specialist from source
analysis of data analysis software BIM
Summary lists Detailed list IFC export
Figure 8 Masdar data extract types from models
Version 2.0.3 40 of 224

MASDAR
12.3.2 Quantity take off and cost estimating
Different types of cost estimate can be produced during the design and construction process,
ranging from area- and system-based calculations during early design to detailed element-based
calculations during the tender stage. Interim estimates help to identify potential problems early so
that Masdar and its design team can make informed decisions in a timely way.
Although 3D models of buildings provide accurate measurements for quantity take off they do not
replace the estimating function. Estimators play an important role in assessing the conditions that
affect project cost - such as site issues or unusual building features - that cannot be analysed
automatically by a 3D modelling tool. Information modelling helps by performing the laborious
task of extracting data (such as quantities and areas) in a way that reduces the uncertainty and
effort of measurement, thereby enabling estimators to spend more time assessing and optimising
project costs.
Masdar‘s preferred method of using information models for cost estimating is based on extracting
component data into Excel spreadsheets, which can then be used by specialist cost consultants
as part of their financial analysis. A data export will be created at the end of each project phase.
For this approach to be effective and efficient there must be a common approach to modelling
and classifying objects across Masdar‘s design and construction community. Therefore, all
parties must adhere to Masdar‘s modelling and collaboration standards.
12.3.3 Data for building life cycle
The ability to extract data from a model means that Masdar can add layers of information on top
of the model components, and store this in a relational database. Such additional data can be
added to the database alongside the project process because it is held outside the model.
The requirements for creating and managing life cycle data are described in chapter 4. The
number of objects, and the data associated with them, will increase steadily through the design
and construction process. It is important to ensure that every object is uniquely identified so that
its data, once exported to an external Masdar database, can be referenced back to the source
file. A data export will be performed at the end of each project phase as a minimum. Exported
data can then be used to conduct various analyses for sustainability, life cycle and facilities
management. A typical methodology is shown in figure 9. Project users could interrogate the
data using the BIM authoring application, the external database or a custom user interface.
Database item referenced to BIM

authoring application via unique
Model-based component Perform analyses: identification code
data extracted
Paul King by
modelling team into Excel
Bentley Systems - Facilities management Pass
spreadsheet
+44 (0)7966 -162
at end
695 of Review
- Life cycle
each project phase, or as
required - Sustainability Fail Component data
exported to
- file name relational database
- unique identification code
- classification
- overall height Re-run
Masdar
- overall width analyses Or life cycle
- thickness
database
- X, Y, Z location
- etc
Additional Masdar-
Amend model as necessary and specified asset data
re-run data extraction and analysis added by various parties
Figure 9 Extracting building component data for analysis and review
Version 2.0.3 41 of 224

MASDAR
12.4 Simulation and analysis

Discipline-specific models can be used in a variety of ways to perform analysis and simulation
tasks, for example:
- calculating the costs of operating a building
- simulating the indoor design environment
- assessing safety aspects, such as the spread of fire and building evacuation
- simulating time-based construction sequences.
12.4.2 Example of analysing indoor environment
An analytical solution is usually reached through an iterative process, in which results of analyses
lead to modified solutions which are again evaluated by new analyses, and so on. Figure 9
illustrates a typical process to analyse the internal environment using a discipline model. The
closer a discipline model can be integrated with the other discipline models, the more efficient the
process can be.
For example, if the mechanical model in figure 10 is referenced upon the architectural and/or
structural building geometry from the respective disciplines, the mechanical engineer does not
have to model those elements himself when creating a model for analysis; when those other
discipline models are changed as the design is developed, it is easier to incorporate the revised
models into the mechanical model in order to re-run the analysis. It would also be easier for the
other disciplines to amend their own models to reflect design changes arising from the
mechanical engineer‘s analysis; for example, where the size of a hole in a floor slab had to be
increased to accommodate a larger than expected ventilation duct.
Export geometry Perform

and/or data to Paul King
Paul King Exchange results
analysis
Bentley Systems
Systems
Assess Accept
Mechanical environmental Bentley with others as
+44 (0)7966
(0)7966 162
162 695
695 results
+44 appropriate
discipline analysis tool
model Reject
Mechanical Add assumptions

Configure model Yes Changes No
discipline and boundary Revise
for analysis required
sub-models conditions
Or
Input from other disciplines
(revised 3D models,
Amend constituent comments on results, etc)
models
End
Figure 10 Example iterative process of using a mechanical discipline model as the basis of analysing indoor
environmental conditions
Version 2.0.3 42 of 224

MASDAR
12.4.3 Integrated BIM and analysis tools
Some analysis tools are fully integrated with BIM applications, enabling geometrical changes to
the discipline model to be automatically transferred to the analysis tool without altering the
boundary conditions already entered. Also, the boundary conditions can first be defined in the
discipline model. When the analysis is performed then the results, such as modified sizes for
ducts or beams, can automatically update the discipline model. This process is known as round-
tripping (figure 11).
Start Mechanical
Yes Further No
discipline End
analysis
model
BIM tool
Ensure correct Model

PaulKing
Paul King Discipline Model
geometry and transferred
BentleySystems
Bentley Systems model exchanged
boundary automatically
+44(0)7966
+44 162to
(0)7966162 695
695 updated with other
conditions analysis tool automatically disciplines
Perform Design
Analysis tool
environmental informed by
analysis analysis
Model changed to reflect
analysis (geometry, data
and/or boundary conditions)
Yes Design No
End
OK?
Figure 11 Example environmental analysis process using integrated BIM and analysis tools
Where the software enables full integration it can still be difficult to achieve fully automated
updating of a discipline model based on the results of analysis because the objects to be modified
could belong to discipline areas other than those covered by the person performing the analysis
(who would not have the appropriate rights to modify another‘s model). An example would be
where a building services engineer performs an analysis of indoor air temperature and calculates
that the amount of external solar shading (the architect‘s responsibility) would need to be
increased.
12.4.4 Non-integrated BIM and analysis tools
Where the applications are not sufficiently integrated to enable round-tripping, outputs from
discipline models (such as simple geometry) might still be able to be used as the staring point for
analysis. However, the analysis results will not automatically be reflected back in the discipline
model. Depending on the configuration of the discipline model and the changes required it must
be decided whether to update the analysis model by manually transferring changes from the
discipline model, or build a new analysis model from scratch.
Version 2.0.3 43 of 224

MASDAR
12.4.5 Time-based construction simulation
Construction schedule simulation enables 3D virtual models to be linked to project planning

information held in Primavera, Microsoft Project or Excel. Project managers, planners and
contractors can visually explore alternative construction sequences and create cost effective and
safe construction scenarios by visualising schedule information and animating 3D project models
based on schedule data. They can also visually communicate the construction timeline to project
participants, and better plan site logistics and coordinate the work of subcontractors. These
construction schedule simulations are known as ‗4D models‘.
In the early project stages it is possible to create 4D models by linking high level construction
schedules to simple site plans (which could be in 2D or 3D) to illustrate project phasing. As the
design evolves the planners could begin by linking simple 3D building shells to a time line, and
progressively adding more detailed elements to suit the developing design. Figure 12 illustrates
the process of creating a 4D model.
Link components (or groups of components) Completed 4D model Stage 3

Import 3D to the activities on the project schedule
model Paul King
elements Bentley Systems Stage 2
Paul King
into 4D tool +44 (0)7966 162 695 Bentley Systems
Stage 1 +44 (0)7966 162 695
Import
construction
schedule
data into 4D
tool
Amend
No
simulation Simulation
4D simulation and analysis tool criteria Or OK?
Yes
Modify 3D model Amend

and/or project End
source
schedule inputs data
Figure 12 Creating a 4D sequence by linking a 3D model to a construction schedule
To visualise different situations, construction types can be assigned to the elements in a model to
describe their behaviour:
- Constructive elements are invisible at the start of a project, and they display at the start of the
task to which they belong. After the task is run they display until the end of the project.
- Destructive elements are visible at the start of the project, and during the task to which they
belong they display in the selected colour. They become invisible after the task is complete.
- Permanent elements are visible at the start of the project, and change colour while the task to
which they belong is run. After the task is complete, elements return to the original colour.
- Temporary elements are visible only while the task to which they belong is run.
The level of detail in the virtual model must be appropriate to the intended purpose of the
construction simulation, and objects must be grouped according to the construction methodology
so that they can be easily linked to activities in a schedule. For example, if a concrete floor slab
is to be placed in four pours then the slab must be detailed in four sections so that the
construction sequence can be planned and illustrated. Therefore, a contractor‘s knowledge is
helpful when producing a model because the contractor can provide useful feedback about
sequencing and buildability while there is still a good opportunity to influence the design solution,
thereby helping to reduce project risk and uncertainty.
Version 2.0.3 44 of 224

MASDAR
12.5 Visualisation
12.5.1 Overview
The principal benefits of visualisation include the convenient comparison, analysis and
presentation of different design solutions, increased interaction between project participants, and
support of the marketing process. Visualisation supports the work of designers, project managers
and contractors, improving the communication between the project participants and end-users.
3D models are used to create different types of visualisation material according to the needs of
each participant. Visualisations can be either still images or animations, produced to varying
levels of detail and accuracy, and can be divided into two main categories: photorealistic and
technical.
Photorealistic visualisation includes the accurate high quality rendering of materials, lighting and
the surrounding environment, and is usually produced by a visualisation specialist based on 2D
design drawings. However, where suitable 3D design models exist then these can be re-used by
the visualisation specialists as the foundation for their work, saving time, effort and cost.
Technical visualisation includes the correct information, geometry and location, and is usually
generated by the design team using native BIM tools or solutions such as 3D PDF and Google
Earth. Examples that could be generated by the designer may include:
- perspective renderings, massing models, visualisations containing materials and shadows
- urban landscape and local environment studies
- facade studies
- indoor and outdoor lighting studies, and shadow analysis
- animations or interactive 3D presentations illustrating the design solution.
Masdar‘s BIM documentation requires designers to create 3D design models in a consistent

format (DGN and IFC) such that they can be re-used easily as the basis for creating either
photorealistic or technical visualisation material.
The required number and quality of visualisations at different phases of the project will be defined
by Masdar in the contract documents for each project. Typical requirements are listed in
appendix 1.
12.5.2 High quality visualisation
Masdar‘s requirements for renderings and animations will be specified for each project, and
typical deliverables are listed in table 7 (see also appendix 1).
Table 7 Typical requirement for high quality visualisation deliverables
Concept stage Schematic design Detail design
- Four exterior perspectives - Four exterior perspectives Renderings and animations

- Two street perspectives at eye level - Two street perspectives at eye level as required to represent
significant design
- An aerial view in context of city - An aerial view in context of city modifications
- Two major Interior spaces - Two major interior spaces
- Two minute animation of computer - A fully rendered fly-through digital video
generated massing model (three-minute minimum)
Version 2.0.3 45 of 224

MASDAR
12.5.3 3D PDF
Adobe PDF is commonly used for sharing drawings and specifications in digital format, and it can
also be used to embed 3D models. Using Masdar‘s preferred BIM tools it is possible to export
models directly into a PDF document to convey 3D designs to the various project participants
regardless of which software they use. 3D models in PDF format make it easy to share
information for comment and interactive review, and to communicate issues such as construction
sequencing and walk-throughs. A recipient needs only to Acrobat Reader to be able to view a 3D
PDF.
Typically, PDF documents printed from Masdar‘s preferred BIM tools contain 3D annotations that
encapsulate everything required to visualise a design. This includes model geometry, materials,
lighting, and texture maps. 3D annotations can also contain animations, both of the model
geometry and of walk-through animations.
A powerful feature of 3D annotations is the ability to use Acrobat Professional to include them in
an existing PDF document such as a marketing brochure, a design portfolio, or a technical
manual.
12.5.4 Google Earth
Masdar‘s preferred BIM tools enable users to publish geospatially located 3D models and data
directly to the Google Earth environment. Publishing models in this way is an effective way of
communicating design solutions to a wider audience, and design options can be evaluated easily
by using switchable level structures.
Version 2.0.3 46 of 224

MASDAR
12.6 Drawing production

Drawings are two-dimensional representations of slices through the 3D model that are used to
generate snapshots of the model at a given point in time. These slices are used as the basis of
creating drawings representing plans, sections and elevations. Drawings will be extracted at
agreed stages to suit the needs of each project, although the preferred method of reviewing
design solutions will be to use the BIM authoring and review tools.
Masdar requires all parties to use a common extraction methodology so that all 2D information is
presented consistently and to ensure the interoperability of data across the project. Figure 13
illustrates the concept of slicing the model to generate 2D drawings. Although slices can be
placed anywhere in a model the team members should agree where they will be placed for each
project; BIM Coordinators will ensure that this effort is coordinated as the model evolves.
Section
Plan Paul King

Bentley Systems
+44 (0)7966 162 695
Model file Slices for Elevation

container extraction
Figure 13 Extracting model views to create drawings
Extractions should be performed at least weekly, or when major model changes have been made,
so that the master data referenced between disciplines is as accurate as possible.
Separate extractions should be made for each discipline, except where output is needed for
creating combined sheets (and certain sections). A new set of drawing definitions may be
created to take advantage of the view parameters and unification features on combined
extractions. Extractions will be generated directly from the 3D model and should never be
modified. If changes are necessary after this point then modifications must be made in the model
and new extractions generated.
For civil applications plans and sections should be extracted using the discipline-specific tools
provided for the purpose. The sections should be annotated using automated tools in order to
maintain consistency with the surface and geometry data, and to avoid the need for manual
cleaning up of extracted information.
All necessary data will be extracted from a container (a model file that holds all necessary
discipline files) simultaneously, regardless of the number of individual discipline-specific 3D
models. The extraction models of one discipline will reference the extraction models of all other
required disciplines to display the correct assembly of master data. Each discipline will produce a
set of coordinated extraction models for easy inter-discipline referencing and coordination.
Extraction output should not be copied into any other file or turned into a separately maintained
master file. Extractions in an output file should not be cleaned up until the final phases of drawing
preparation. Extraction output will be overwritten upon each new extraction.
All drawings must comply with Masdar‘s CAD Standard (chapter 5) to ensure coordination and
consistency across all project documentation.
Version 2.0.3 47 of 224

MASDAR
12.7 Configuring model outputs for analysis and exchange

Masdar‘s project participants must agree what, when and how geometry and data from discipline
models will be exchanged, and in particular:
- The content, format and quality of the base data must be agreed.
- Energy and acoustical analysis tools require correct geometrical data, so this must be present
in the originators‘ models.
- If the analysis models are to be continually updated then the participants must agree the
methodology for continually exchanging the relevant models.
- The method of exchanging the results of analyses between the parties (for modifying their
discipline models) must be agreed.
- Data should be exchanged digitally wherever possible.
Version 2.0.3 48 of 224

MASDAR
13 Information levels
13.1 Introduction to information levels
Discipline models undergo successive detailing through the project stages, similar to the process
of creating and developing traditional 2D drawings. Value will be added to the discipline models
in the form if increasingly accurate data and information that can be used by individual parties or
shared among project teams.
The concept of information levels is used to describe and define the content of the discipline
models at a given stage of a project. An information level expresses how fully specified and
detailed the objects are; that is, the discipline model contains particular building elements in the
form of objects with a particular level of detailing and particular properties, suitable for particular
uses. Masdar‘s modelling approach uses eight information levels which describe a rising degree
of detailing (table 8). Each subsequent information level builds on the previous level.
Table 8 Information levels
Masdar stage name Design effort Cumulative effort Information level
Pre-design 5% 5% 1
Concept 20% 25% 2
Schematic design 25% 50% 3
Detailed design 30% 80% 4
Construction documents 20% 100% 5
Tender - - 6
Construction - - 7
Handover + defects liability - - 8
The information levels correspond generally (but not exclusively) to the Masdar project stages.
They can be customised to other phased project processes and the allocation of roles can be
varied to suit the nature of project tasks. For example, on projects using early contractor
involvement (based on performance requirements) some activities could be transferred from the
consultant to a specialist product supplier; the information would still be detailed successively but
by parties outside the consultant design team.
The modelling approach does not assume that the discipline 3D models contain all project
information; they must be supplemented with information such as specifications, drawings, and
manufacturers‘ information (which could be linked to the 3D objects in models).
At the start of each project stage it is vital for the project participants to agree what construction
objects will be included in each 3D model and, most importantly, which components will not be
modelled.
Version 2.0.3 49 of 224

MASDAR
13.3 Information levels for delivery

13.3.1 Overview
The information levels of the individual 3D discipline models differ in how the geometry and
location of objects are detailed and specified. When the end of a project stage is reached then
the discipline models are saved with the information developed during that stage. The next stage
starts with a copy of the previous stage‘s discipline models, and the information (and value) of the
model are enhanced as the stage progresses. This process is repeated through the project,
ensuring that the history of the design is saved and that it is possible to go back and examine the
decision-making processes and responsibilities. This approach also ensures the re-use of design
information and data through the project lifecycle.
The eight information levels are described in the following sections. For each level, the particular
requirements of that level are described and two tables state the characteristics for 3D objects;
the first shows which object types are represented and the second shows the main areas in which
the properties of the current objects must be specified.
(A filled square indicates a primary area of focus and an empty square indicates a secondary
area. There will of course be overlaps and iterations in the project process, so the tables should
be treated as generalisations.)
The tables indicate the principle of developing more detailed models. Specific attribute data
requirements, by project stage, are given in chapter 4. For example, on a particular project the
Masdar facilities management team might require a detailed overview of operation and
maintenance features from the start of a project, so the project team would need to specify these
properties at the earliest information levels.
Version 2.0.3 50 of 224

MASDAR
13.3.2 Information level 1 – pre-design
Information level 1 corresponds to the detail required for the pre-design phase.
(1) Development of initial statement of requirements into the design brief by or on behalf of the
client confirming key requirements and constraints.
(2) Identification of procurement method, procedures, organisational structure and range of
consultants and others to be engaged for the project.
Table 9 Requirements for models at information level 1
Objective To clarify and formalise the different requirements and constraints for the project at the
pre-design phase and present a consolidated project design brief to Masdar
Responsibilities Masdar and/or its nominated design consultants.
Information Information level 1 is usually in advance of any 3D modelling because client initial
content client requirements cannot necessarily be represented in a discipline model. However,
where modelling is appropriate then the requirements in this table will apply.
(1) Urban and rural constraints around the building site, ground, geology and utilities
networks. The design brief may be formalised in a coarse 3D model which
describes the functions as volumes in a 3D space.
(2) Client requirements: Room schedule stating function, capacity, sizes and
relationships. Financial/resource requirements.
(3) Local requirements: Requirements of the authorities, infrastructure requirements,
resources and supply chain, environmental requirements.
Use If available, the 3D models form part of the brief and the conditions for the project, to
be tendered to consultants.
Detailing Where a model is created or used at this stage then it should be sufficiently detailed to
produce outputs listed in appendix 1 (section A1.1) and any other project-specific
requirements. The building models will link to information relevant to the project,
predominantly in document form (legal, analyses, design briefs, etc). The building
model may also contain contextual and GIS information.
Object category Object attributes 

Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 51 of 224

MASDAR
13.3.3 Information level 2 – concept
Information level 2 corresponds to the detail required for the concept design phase.
(1) Implementation of design brief and preparation of additional data.
(2) Preparation of concept design including outline proposals for structural and building services
systems, outline specification and preliminary cost plan.
Objective To clarify the overall form and functional properties of possible design solutions early
in the design process.
Responsibilities Preparing information Applying information
(i) Designers (i) Project management
(ii) Masdar (ii) Design consultants
(iii) Project manager
(iv) Local authorities
Information The discipline model contains the building‘s overall form, structure and relationships to
content the surroundings, plus rooms and their relationships. The discipline model at
information level 2 contains two overall components:
(1) Volumes that represent the building‘s external geometry in a simplified manner.
(2) Rooms that represent the building‘s usable spaces. The model contains
information on rooms but not on the adjoining building elements.
Use (1) Information level 2 is used to establish the building‘s functional and physical
properties.
(2) The architect will prepare a discipline model containing the building‘s form,
structure and relationships to the surroundings. It is also checked that the volume
envisaged can contain the rooms specified.
(3) It must be possible to extract areas and volumes, and provide an estimate of gross
and net areas by function.
(4) Information level 2 may include information that can be used for initial contact with
the planning authorities.
(5) A 3D model at information level 2 can be used for simulation of light and shade in
and around the building.
Detailing The model should be sufficiently detailed to produce outputs listed in appendix 1
(section A1.2) and any other project-specific requirements.

Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  

Version 2.0.3 52 of 224

MASDAR
13.3.4 Information level 3 – schematic design
Information level 3 corresponds to the detail required for the schematic design phase.
(1) Development of concept design to include structural and building services systems, updated
outline specifications and cost plan.
(2) Investigation of alternative strategies, systems, materials and equipment
(3) Completion of project brief.
Objective To create the basis of decisions for developing the design solution. Information level 3
must reflect the functional and building physical information and may form the basis of
early contractor involvement.
(i) Design consultants (i) Designers
(ii) Masdar
(iii) Project managers
(v) Contractors
Information Information level 3 is the first layout of rooms and building elements at a general level
content (foundations, walls, structural floors and roof).
(1) The building elements have a geometrical shape and location, and overall
performance specifications are identified at type level
(2) Rooms and building elements are given attribute data corresponding to the data
listed in chapter 4.
Use Information level 3 is used to build up the basic structure for the assessment of the
overall physical and functional properties of the building.
(1) Spatial coordination between the design disciplines

(2) Advanced dialogue with the authorities (such as fire strategy
(3) Building simulation (such as energy analysis)
(4) Communication with Masdar.

Detailing Information level 3 contains construction objects at a general level with simple
graphical representation in 3D. All openings in walls, structural floors and roofs must
be defined at a general level. The model should be sufficiently detailed to produce
outputs listed in appendix 1 (table A1.X) and any other project-specific requirements.

Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  

Version 2.0.3 53 of 224

MASDAR
13.3.5 Information level 4 – detail design
Information level 4 corresponds to the detail required for the detailed design phase.
(1) Preparation of technical design(s) and specifications, sufficient to co-ordinate components

and elements of the project and information for statutory standards and construction safety.
(2) Incorporate the selected systems, materials and equipment into the frozen design and
produce a detailed design package that fully describes the project to a level suitable for
tender.
Objective Coordination tool for the parties to the project, and the basis of consideration by the
authorities.
(i) Design consultants (iii) Masdar
(iv) Project managers
(v) Contractors
(vi) Local authorities
Information (1) Information level 4 must contain the information for consideration by the
content authorities and be detailed to the necessary extent.
(2) Building elements are given attribute data in accordance with the requirements set
out in chapter 4.
Use (1) To support the coordination of modelling work between the parties, including
coordination and clash detection.
(2) the basis for consideration by the authorities.
Detailing (1) Information level 4 consists of construction objects whose make-up has been
decided in principle.
(2) Objects must be specified and be graphically represented; for example, for a wall
this would show the division into inner leaf, cavity with insulation and outer leaf.
(3) The models should be sufficiently detailed to produce outputs listed in appendix 1
(section A1.X) and any other project-specific requirements.

Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 54 of 224

MASDAR
13.3.6 Information level 5 – construction documents
Information level 5 corresponds to the detail required for the construction documents phase.
(1) Preparation of a full construction document package to be issued for construction including
drawings, specifications, calculations and reports fully detailing all systems, materials and
equipment.
Objective Finished building design which conforms to the specification requirements, buildability
requirements, construction schedule and cost plan.
(i) Design consultants (i) Masdar
(ii) Project manager
(iii) Contractor
Information (1) Must contain the information for consideration by the authorities and be detailed to
content the necessary extent.
(2) Building elements are given attribute data in accordance with the requirements set
out in chapter 4.
Use (1) To support the coordination of modelling work between the parties, including
coordination and clash detection.
(2) It is also used as the basis for consideration by the authorities.
Detailing (1) Information level 5 consists of construction objects whose make-up has been
finalised.
(2) Objects must be specified and be graphically represented; for example, for a wall
this would show the division into inner leaf, cavity with insulation and outer leaf.
(3) The models should be sufficiently detailed to produce outputs listed in appendix 1.

Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 55 of 224

MASDAR
13.3.7 Information level 6 – tender
Information level 6 corresponds to the detail required for the tender phase.
(1) Preparation and/or collation of tender documentation in sufficient detail to enable a tender or
tenders to be obtained for the project.
Objective Preparation and collation of tender documentation in sufficient detail to enable a

tender or tenders to be obtained for the construction of the project in a way that will
meet project objectives.
(i) Designers (i) Masdar
(ii) Specialist suppliers (ii) Project managers
(iii) Specialist contractors (iii) Contractor
(iv) Specialist suppliers
Information (1) Information level 6 contains all building elements broken down as necessary to
content fulfil their purpose.
(2) All necessary information for tendering must be specified so that quantities and
drawings can be extracted.
Use (1) Information level 6 is used as part of the tender documents and to negotiate
construction price.
(2) Extracting parts lists and preparing bills of quantities for cost estimates in
connection with the invitation to tender.
(3) Creating drawings corresponding to traditionally produced drawings.
(4) Used by the contractor as the basis of production planning. Any information about
geometry and specifications necessary for production planning must be present in
the discipline models.
(5) Final coordination between the designers‘ models (which must be completed
before the information level is issued).
Detailing The model should be sufficiently detailed to produce outputs listed in appendix 1

Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 56 of 224

MASDAR
13.3.8 Information level 7 – construction
Information level 7 corresponds to the detail required for the construction phase.
(1) Letting the building contract, appointing the contractor.

(2) Issuing of information to the contractor.
(3) Arranging site hand over to the contractor.
(4) Administering the building contract to practical completion.
(5) Providing further Information to the contractor when reasonably required.
(6) Reviewing information provided by contractors and specialists.
Objective Implementation of the building contract to practical completion, including the creation
and management of handover information and data that is correct, consistent and
complete.
(i) Contractor in consultation with its design team (i) Contractor

(ii) Specialist product suppliers
Information (1) Information level 7 specifies the construction products and their properties,
content possibly supplemented by necessary materials specifications.
(2) The discipline models must be sufficiently detailed to be able to support
construction activities. Examples would include production planning and site
logistics, which are enabled by the addition of time parameters to the individual 3D
objects and associated design information.
Use (1) Information level 7 is the basis of production and may be used to simulate the
construction process and planning the flow of materials and equipment.
Detailing The models must contain sufficient information to produce the building.
Building elements from the design phase model will be replaced by specific products
during the construction process.
All components are given specific attribute data, as detailed in chapter 4, at the
appropriate point in the construction process.
The model should be sufficiently detailed to produce outputs listed in appendix 1


Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 57 of 224

MASDAR
13.3.9 Information level 8 – defects liability
Information level 8 corresponds to the detail required for the defects liability (handover) phase.
(1) Reviewing information provided by contractors and specialists.

(2) Administering the building contract after practical completion and making final inspections.
(3) Tracking, managing and rectifying defects to ensure that the facility can be operated
efficiently, effectively and sustainably.
(4) Assisting building users during the initial occupation period.
Objective Provision of the final as-built model and associated high quality handover
documentation.
(i) Contractor in association with: (ii) Defects liability team

- design consultants (iii) Masdar operations team
- specialist sub contractors
- suppliers of products and systems
Information (1) Information level 8 will vary from project to project in terms of the scope of
content handover data and information, and the level of detail.
(2) The degree to which the building model is to be updated with specific objects and
properties must be determined by the Masdar‘s requirements for data for
operation and maintenance, and must be agreed on a project-specific basis. The
object data requirements are set out in chapter 4.
Use (1) At the point of handover the building model will be complete. Level 8 records the
physically completed construction with the building elements, components and
properties that are the result of production.
(2) Data can be extracted from the discipline models for use in operation and
maintenance.
Detailing The degree of detailing will correspond to the needs of operation and maintenance,
and models should be sufficiently detailed to produce the outputs listed in appendix 1

Site   Function  
Building extents   Geometry/ location  
Building   Building physical data  
Rooms   Process data  
Building elements   Product data  
Finishes   Operation and maintenance  

Version 2.0.3 58 of 224

MASDAR
13.4 Information level for operation

Masdar intends to maintain and update the models and associated data during the operational life
of a building to reflect changes to building elements. Examples would be reconfiguration of
rooms and spaces, the replacement of mechanical equipment and the recording the actual
energy consumption of equipment.
A building may be refurbished and/or remodelled many times during its life, at the end of which it
will be decommissioned, removed from site and recycled where appropriate.
By recording operational data over the building life cycle Masdar will build up a valuable
knowledge base for future projects.
13.5 Project planning using information levels

The participants must agree a phased approach to modelling at the start of each project.
Different types of project will require different working practices and approaches to modelling. An
example of how this can be done is shown in table 17, where the project participants enter the
process at different times and the discipline models do not have the same information level at the
same time.
For example, where the success of a project is likely to depend on the realisation of one or two
key design elements – such as the public areas of a luxury hotel or the external visual impact of a
prestigious headquarters building – then those elements would need to be developed to a greater
level of detail early in the project.
Table 17 Example of project planning using information levels
Project stage Architect Structural MEP Contractor Supplier
Pre-design 1 1 1
Concept 3 3 3
Schematic design 3
Detailed design 4 4 4 5
Construction documents 5 5 5 5
Tender 6 6 6
Construction 7 7
Handover and defects liability 8 8
Note: MEP = mechanical, electrical and plumbing
Appendix 2 shows an information level matrix that should be completed by the project team at the
start of as project. It will identify the information level for each building element (using UniFormat
classification) by project phase, together with the party responsible for developing the model. A
description of the UniFormat system is given in chapter 4.
Version 2.0.3 59 of 224

MASDAR
14 Modelling roles and responsibilities

At the start of a project it is important to identify and record the roles and responsibilities of the
project team. Examples of three of the likely main roles required for Masdar projects (BIM
coordinator, lead designer and CAD manager) are described below. Project team members
within each organisation would also be categorised as ‗users‘, ‗experts‘ or ‗mentors‘ according to
their BIM skills and experience.
BIM coordinator
The BIM coordinator will act as the prime point of contact for issues related to BIM and to
Masdar‘s technical design coordination system. Table 18 lists typical key functions to be carried
out by the BIM coordinator. Each organisation or team shall have a version of this role.
Masdar‘s BIM coordinator will, in addition, coordinate and lead all other BIM coordinators on a
project, ensuring that there is a consistent approach to project modelling and CAD issues and
practices across each project. He will also coordinate project requirements for the engineering IT
systems and be responsible for managing revisions to Masdar‘s BIM documentation.
Table 18 Primary functions of the BIM coordinator (not in order of importance)
- Works with the Masdar BIM coordinator to provide education and training (see section 7 of this document)
Education and
- Performs in-house BIM technology briefings

training
- Undertakes intelligent audits to identify the specific business benefits of implementing BIM within the
organisation, and gap analyses to identify how to transition the business to where Masdar needs it to be.
- Provides and/or organises in-house BIM training and education sessions for users to advance the effective use
of BIM technology. These can be general or project-specific.
- Performs project setup in alignment with the project requirements, and applies Masdar BIM standards and
procedures.
- Provides project model management and coordinates the production of defined deliverables
- Provide continuous drawing production coordination and resolves related issues.
- Coordinates plotting, signing and sealing requirements/coordination for intermediate, project milestone, and
submittal deliverables.
Project delivery
- Performs quality checks on the models prior to uploading to the collaboration environment
- Ensures the technical coordination environment is continually updated with current and valid information.
- Manages the creation and use of BIM outputs through the project lifecycle, such as model reviews, visualisation,
simulation and engineering analysis, and interface with cost estimation, project controls and scheduling.
- Manages production deadlines with their discipline‘s team members.
- Collaborates with each project discipline to ensure that technology is maintained, advanced and correctly
configured to meet the project objectives.
- In coordination with other disciplines, ensures the completeness and reliability of data for its intended purpose for
all stakeholders through the project life cycle
- Leads the implementation of integrated BIM technologies within the discipline
- Works with discipline leads to promote and advance BIM, and to facilitate interoperability between technologies.
Support
- Coordinates with the Masdar BIM coordinator to establish and distribute new CAD layers.
- Manages changes to BIM standards and approaches, ensuring that projects maintain a common working
environment
Version 2.0.3 60 of 224

MASDAR
Lead designer
The lead designer manages the design, including information and approvals, and coordinates and
integrates the work of the specialist designers and sub-contractors. The lead designer
establishes the structural grid and floor levels, confirms the design deliverables of the design
team, and approves the documentation. In small and medium size projects a lead designer could
be the same person as the BIM coordinator, although best practice dictates that they roles should
be separated.
CAD manager
A discipline CAD manager ensures that all CAD models and drawings are prepared in
accordance with Masdar‘s BIM standards and methodologies, and delivered to the project
correctly using the agreed technical coordination system.
Version 2.0.3 61 of 224

Element coding standard
MASDAR
Chapter 4
Element coding standard
The purpose of this chapter is to provide guidelines for creating and using common CAD layer
and object structures to ensure that information held in 2D and 3D building models can be
exchanged easily between all parties to a Masdar project.
A Masdar model will be made up from virtual building objects which will be placed on specified
layers within a CAD application. Traditionally, project parties have exchanged graphical
information in the form of 2D drawings where information is identified by layer names, and layers
can be toggled on or off to change its visibility. The information is also interpreted by its graphical
appearance on screen or paper by attributes such as colour and line type.
In a BIM environment 3D models are created from a collection of objects rather than lines.
Objects are virtual elements and spaces which represent the corresponding elements and spaces
in the structure to be built, and include attribute data such as material, function and type. To
enable the efficient and effective exchange of objects between the project parties then their
creation and use must be standardised.
While Masdar‘s projects continue to use a mixture of 3D models and 2D drawings then the object
and layer structures must supplement each other. The 3D model will be created based on a
defined object structure and the model will be viewed according to the functionalities of the CAD
systems used. For producing drawings from a 3D model the defined layer structure must be used
for managing the drawing construction and layout.
Version 2.0.3 63 of 224

MASDAR
15 Object classification
Masdar requires a consistent way of classifying all modelling objects and drawing features to
ensure a fully standardised and integrated data set across all project team participants. This is
achieved using the UniFormat classification system.
The elements defined by UniFormat are major components that usually perform a given function
regardless of the design specification, construction method or materials used. Examples of
elements are foundations, exterior walls, sprinkler systems and lighting.
Using UniFormat helps to ensure consistency in the economic evaluation of building projects over
time and from project to project. It also helps to enhance project management and reporting
during planning, design, construction, operation and disposal. It facilitates economic analysis
early in the design phase before sufficient information has been developed to generate product-
based cost estimates.
UniFormat is not intended to classify elements of major civil works. However, buildings are
usually accompanied by roads, utilities, car parks and other non-building features. Therefore,
UniFormat includes the classification of building-related site work so that users do not need to
use multiple classification systems on what is primarily a building project.
A summary of UniFormat classifications is given in appendix 3.
Chapter 3 describes the level of detail required for each UniFormat element by project phase.
Bentley BIM tools use a system of ‗families and parts‘ which is based on the UniFormat
classification system (http://www.uniformat.com/nistir-6389.html) and Masdar‘s project dataset is
structured accordingly for ease of use.
Version 2.0.3 64 of 224

MASDAR
16 Data content of design deliverables

The definition of required content at each project phase is detailed in the chapter 3 (Information
Modelling Guide). Each design or construction team must populate data-rich models and upload
them to the collaboration environment throughout the programme‘s lifecycle.
It is the responsibility of each originator to monitor the quality, timeliness, accuracy and
consistency of their data relative to the design standards and modelling guides; this will ensure
interoperability with other teams and that information is current within the collaboration
environment.
Fixed and non-fixed components need to be placed into the model to generate unique identifiers
and to ensure database integrity. Fixed elements are permanent throughout the lifecycle of the
programme; non-fixed elements may be temporary items used for a limited timeframe within the
project, or items such as furniture which the programme will quantify and track, and thus must be
placed within the model and tagged with a unique identifier.
The detail to which fixed and non-fixed components are modelled will depend on the data
required. For example, If only a quantity of units is desired (such as chairs) then they should be
modelled generically in order to account for the physical space they occupy. Time should not be
spent on generating fine details which do not increase the quality or value of the data.
Conversely, if specific component information is desired then each component will need to be
modelled, along with the required data.
Version 2.0.3 65 of 224

MASDAR
17 Layer / level structure

17.1 Introduction to layers
The layering format described in this section should be used by all the parties for a unified
workflow and to improve the efficiency in information exchange between various disciplines.
Layers are used in CAD files to logically group together similar elements. It is important to ensure
that the groups can be identified quickly and easily by anyone who needs to access or use the
information. Therefore, layer names should conform to a standard naming convention; Masdar
employs automatic checking of CAD file layer names as part of the submittal process to ensure
that they comply with the necessary standards - files that do not comply will be rejected.
When using Masdar‘s preferred Bentley BIM tools, levels will be associated to part and family
definitions from the 3D models, and linked to 2D outputs from 3D data files.
17.2 Layer naming

17.2.1 General principle
Masdar requires layers to be named in accordance with the US National CAD Standard
(http://www.buildingsmartalliance.org/ncs/) which provides a unique reference to a logical
collection of CAD elements.
There are four defined layer name data fields: discipline designator (mandatory), major group
(mandatory), two minor groups (optional), and status (optional). Each data field is separated from
adjacent fields by a hyphen for clarity.
[Discipline designator] - [Major group] - [Minor group 1] - [Minor group 2] - [Status]
17.2.2 Discipline designator
The discipline designator is a two-character code that denotes the category of subject matter
contained on the specified layer. The first character is the discipline character (table 19) and the
second character is an optional modifier to further define the discipline. Examples of additional
architectural designators are listed in table 20, which would generate the discipline designator of
AI for architectural interiors.
Table 19 Discipline designators (first character)
Code Discipline Code Discipline Code Discipline
A Architectural H Hazardous materials R Resource
B Geotechnical I Interiors S Structural

C Civil L Landscape T Telecommunications
D Process M Mechanical V Survey / mapping
E Electrical O Operations X Other disciplines

F Fire Protection P Plumbing Z Contractor / shop drawings
G General Q Equipment
Version 2.0.3 66 of 224

MASDAR
Table 20 Optional discipline designators for architecture (second character)
Code Description
D Architectural demolition
E Architectural elements
F Architectural finishes
G Architectural graphics
I Architectural interiors
J User defined
K User defined
17.2.3 Major group
The major group is a four-character field that identifies a major building system. For example,
WALL denotes an architectural wall (other examples are shown in table 21). The major group
field codes shown on the layer list are logically grouped with specific discipline designators.
However, any major group may be combined with any discipline designator, provided that the
definition of the major group remains unchanged. Therefore, any reasonable combination of the
discipline designators and major groups is permitted.
User-defined major group field codes are not permitted.
Table 21 Example codes for the major group data field
Code Description
WALL Wall
CLNG Ceiling
FLOR Floor
FURN Furniture
AFLD Airfields
BRDG Bridge
17.2.4 Minor groups
The first minor group is an optional four-character code to further define the major group. For
example, A-WALL-FULL denotes an architectural wall, full-height.
The second minor group minor group may be used to further define the data contained on a layer.
For example, A-WALL-FULL-TEXT indicates an architectural wall, full height, text.
The minor group field codes shown on the layer list are logically grouped with specific major
groups. However, any minor group may be used to modify any major group, provided the
definition of the minor group remains unchanged. Therefore, any reasonable combination of the
prescribed major and minor groups is permitted.
User-defined minor group field codes are permitted. They must comprise four alphanumeric
characters and/or the ―~‖ character, and must be fully documented by the parties working on a
project.
Version 2.0.3 67 of 224

MASDAR
17.2.5 Status
The status field is an optional single-character code that distinguishes the data contained on the
layer according to the status of the work or the construction phase. The codes for this field are
listed in table 22.
Table 22 Example status codes
Code Description
D Existing to demolish
E Existing to remain
F Future work
M Items to be moved
N New work
T Temporary work
X Not in contract
1-9 Phase numbers
17.2.6 Layer name example
An example layer name is: A – WALL – FULL – TEXT – N
‗A‘ is the discipline designator with optional group ‗I‘ : architectural Interiors
‗WALL‘ represents the major group : wall
‗FULL‘ is the optional minor group : full height
‗TEXT‘ is the optional minor group : text
‗N‘ is the status : new work
Version 2.0.3 68 of 224

MASDAR
17.3 Requesting additional layers

For a complete list of variables for all level fields refer to the US National CAD Standard. If any of
the parties involved in the project require new layers then they will use Masdar‘s process for
requesting, approving and implementing additional layers (figure 14). If the new layer name is
accepted then Masdar will update the seed/template files accordingly.
Effective communication between the various BIM Coordinators is critical to ensuring that the
level creation process is efficiently and that duplication of efforts is avoided.
Consultant‘s Consultant‘s CAD Masdar MASDAR BIM

design team manager CAD team Coordinator
New CAD layer

required
Generate proposed Check that:

CAD layer Proposed layer
matches MASDAR
format
Submit new layer to
MASDAR Information requested
is not already defined
by an existing layer
Resubmit
Fail Review
Notify design Or Report Confirm that

team failure Pass information to be
shown is appropriate
Review
Report failure Reject Approve
Incorporate Report and update Approve new

update CAD template layer
Figure 14 Process for requesting new layers
Version 2.0.3 69 of 224

MASDAR
18 Object structure
18.1 Introduction to object structures
The object structure includes the specification of the general attributes data which must be
attached to all objects forming part of the virtual 3D building model. It also includes clarification of
the most important object-specific attribute data of the most common objects, such as walls and
doors. This clarification should not be taken to be a comprehensive list of the possible or relevant
attribute data but as a minimum list of data which must be given, and details of their names, in
order that all the data can be interpreted in different systems.
The object structure also specifies the information levels at which the attributes must be entered.
The concept of information levels is detailed in chapter 3. The success of a BIM approach
depends on agreement at all times as to which data can be retrieved from a given information
level. Some properties will typically not be accessible until late in the project process and will be
either undefined or entered tentatively in the first information levels.
Quality control procedures will check that all the requisite object properties have been entered at
the appropriate information level (corresponding to a particular project stage).
18.2 Information levels

The degree of detailing in 3D models will evolve over the course of a project, from rough
declarations (a wall) to detailed specifications (a load-bearing concrete wall, 240mm . . .) The
information level indicates the nature of the information held in the objects comprising the model;
Masdar uses information levels numbered from 1 (roughest) to 8 (most detailed). In some cases
the objects will hold all data at an early project stage. This may occur when, for example, the
objects are provided by a specialist manufacturer during the design development phase, although
there may be no formal decision to use that specific product. Table 23 shows how the
information levels relate broadly to project phases. Full details are given in section 13.
Table 23 Typical object characteristics by information level
Information level Construction object type Object attribute data

Building physical data
Key
Geometry/location
Building elements
Operational data
Building extents
 Primary areas of focus

Process data
Product data
 Secondary area of focus

Function
Finishes
Building
Rooms
Site
1. Pre-design            
2. Concept            
3. Schematic design            
4. Detailed design            
5. Construction documents            
6. Tender            
7. Construction            
8. Defects liability            
Version 2.0.3 70 of 224

MASDAR
18.3 Setting up attribute data

All objects will have associated attribute data. Some data will be tagged directly to the 3D object
in the model while other data will be stored in an external database and linked to the object using
a unique identification reference. This combination of tagged and externally-referenced data is
termed the ‗object data‘.
Tagged data will be entered only by the originators of the respective 3D models whereas
externally-referenced data (held in a data source outside the 3D model, such as a database)
could be added by any party with appropriate permissions for the data source. For example,
during the detailed design phase the mechanical services modeller would tag a chilled water
pump with the name of the preferred manufacturer; during the construction phase the contractor
would add specific handover data to the database, such as supplier name, serial number and
warranty details.
At the end of the project handover process – information level 8 – the model will include all
necessary object data to meet Masdar‘s requirements for operations and the data will be
uploaded to Masdar‘s enterprise facilities management system. The common data structure for
Masdar model objects is shown in figure 15, and it should be noted that most object data will be
held externally.
Object
Tagged data External data
Unique ID Object linked to an external database via the unique ID MASDAR-defined data
Application-generated data MASDAR-defined data

Asset number
Supplier name
Paul King Warranty provider
Uniquely Door width Bentley Systems Manufacturer
Paul King
identifies a +44 (0)7966 162 695 Bentley Systems Warranty start
Door height Model number
+44 (0)7966 162 695
component at Warranty expiry
Door number Cost
(generated by Annual energy use
the authoring Rough opening Description
Etc
software). Etc Etc
Figure 15 Common data structure for an object
The unique identification represents the lowest common denominator for an object‘s attribute data
– all objects will be tagged with this regardless of project stage or information level. It ensures
that a virtual object can always be uniquely identified across the whole Masdar City, and that an
object can be tracked down to its location in a 3D model file. Once assigned, an object‘s unique
identification will remain fixed through the project life cycle.
Application-specific data represents attributes that are defined by the particular CAD application.
A sample of such data, generated by Bentley‘s BIM tools, is given in appendix 4.
Tagged Masdar-defined data represents the data that should be added during design and/or
construction. The requirement is given in appendix 5.
External Masdar-defined data represents the minimum data set that has been established for
operation and maintenance through the life of an asset after project handover. Appendix 6
defines when object attributes should be assigned (by information level) and the party responsible
for entering them.
Version 2.0.3 71 of 224

CAD standard
MASDAR
Chapter 5
CAD standard
This chapter defines the requirements for preparing, creating and configuring the CAD data to be
issued to Masdar and other project participants. Its purpose is to ensure that all 3D models and
the drawings generated from them are produced in a consistent format in their correct
geographical location. The document also addresses the post-processing of drawings, such as
adding borders, dimensioning notes and revisions.
Version 2.0.3 73 of 224

MASDAR
19 Modelling standards
19.1 Introduction to modelling standards
The Masdar methodology is based on building information modelling, enabling project teams to
work on 3D geometric models with associated data. To optimise the business benefits of BIM for
all participants, all contributors should work in a managed data environment.
Masdar‘s Design Information Modelling Guide (chapter 3) addresses ‗what‘ is modelled and ‗why‘.
This section defines the requirements for preparing, creating and configuring the CAD data to be
issued to Masdar and other project participants. Its purpose is to ensure that all 3D models and
the drawings generated from them are produced in a consistent format in their correct
geographical location. The document also addresses the post-processing of drawings, such as
adding borders, dimensioning notes and revisions.
There are various methodologies and terminologies adopted by different software products and
the topics described in the following sections are universally applicable.
19.2 Setting up models

19.2.1 Federated modelling approach
Masdar‘s approach to BIM uses a federated database concept. Instead of depending on a single
model file or database, it uses a collection of different models and information sources created by
the different people involved in a project. No two participants will necessarily edit the same model
but the collaboration environment (based on Bentley‘s ProjectWise) brings all the pieces together.
Each separate CAD file should be created from a single seed (or prototype) file that will be
created and established by the project CAD manager. The following items must be noted at the
time of creating the file:
- the coordinate system of the site locale should be used

- all the settings required should be configured: grid, element snaps (O snap, tentative) and
auxiliary coordinate system (ACS)/ universal coordinate system (UCS)
- CAD model files shall be saved with the model view open and fitted
- 2D CAD drawings files shall be saved with the title block view open and fitted.
Version 2.0.3 74 of 224

MASDAR
19.2.2 Model file settings
This section provides guidelines on creating the model files. A model is a container of all the
graphical and non-graphical elements in a design file. There are two main types of model file:
design models and sheet models.
Design models primarily contain design data and are used for design, coordination, quantification
and visualisation. Sheet models contain information (such as plans and sections) extracted from
design models for drawing sheet compositions (for plotting). The following template file (with
appropriate settings preset) must be used for all building model files:
Masdar3DSeed.DGN
Except for structural models which will use
Masdar3DSTRSeed.DGN
The following template file must be used for all civil engineering modelling:
Masdar3DSeed-civil.DGN
A list of all standard project files is given in appendix 7.
19.2.2.1 Global origin
All information shall be drawn in its correct location using real-world coordinates in a 3D file. This
can be established by choosing the correct seed file to create the models.
19.2.2.2 Working units
All information shall be produced at true scale (1:1).
Metric units shall be used and the preferred working units are millimetres. Other units may be
used where recommended by Masdar‘s BIM Coordinator; for example, metres may be the
preferred unit of measurement when liaising with a road transport authority. The working units
defined in Masdar‘s seed files and the project unit definition file are:
Unit name Label

Master units: Meters (M)
Sub units: Millimetres (mm)
The coordinate readout for the CAD files shall be:
Coordinates Angles
Format: Master units Format: Decimal degrees (DD.DDDD)
Accuracy: 0.123 Accuracy: 0.123
Where units are abbreviated then the recognised standard abbreviation shall be used.
Version 2.0.3 75 of 224

MASDAR
19.2.2.3 Position / location
Design teams shall provide models in the coordinate system and datum used throughout the
project: UTM, Zone 40 North, WGS84 (ITRF96), metres for the horizontal and the New Abu Dhabi
Datum for the vertical. The average scale factor is 1.000322623.
The list of primary control monuments used throughout the project can be obtained from Masdar‘s
Site Control and GIS Manager.
The BIM Coordinator shall coordinate the locations of all facilities within the virtual environment by
providing a set of x, y, z coordinates, marking a starting point for model development.
All geometry will be drawn at the correct z position from the datum, which must be defined at the
onset of the project. Objects with unknown z positions should be drawn at an elevation of -999,
except geometry such as details, plans/sections/elevations which would be placed at elevation 0.
All sections generated from models should be correctly transposed so that different drawings can
be correctly overlaid electronically without any need to reposition or transform the level datum.
19.2.2.4 Orientation
In the case of geometries that are not orthogonal to the project global coordinate system, specific
auxiliary coordinate systems (ACSs) may be created for use across the entire project. Examples
of non-orthogonal grids would be skewed building grids and sloping walls
19.2.3 Model file setup
A model file is the base assembly of objects representing a common theme. The models for
example could be ‗ground floor plan‘ consisting entirely of ‗walls‘, ‗frames‘, ‗columns‘ and ‗floor‘.
These models should generally contain information from one discipline at one project stage.
The granularity of the models should be agreed at the onset of the project. Finer breakup of
models offers the opportunity for multiple concurrent usages.
The models must be configured based on the particular discipline.
There can be only one design per model file name; multiple designs per model file are not
permitted. Elements of different statuses must not be combined into a single model.
There shall be only one 3D instance of any object in the entire project, although the same object
could have multiple representations (such as in drawings and bills of quantities).
For further information refer to chapter 6. The following sections describe the possible
breakdown of model files by type, zone and level.
19.2.3.1 File setup by type (interior/exterior)
An example would be exterior walls on the ground floor.
Version 2.0.3 76 of 224

MASDAR
19.2.3.2 File setup by zone
To facilitate the management of models on large projects they should be divided into zones.
These zones will be established and agreed by the BIM Coordinators at the start of a project. For
example, zones could be identified based on the area to be managed, or on work package.
19.2.3.3 File setup by level (floors)
This setup is based on the traditional drawing-centric information setup. There could separate
model files for strategic floor levels. This type of model file setup would not be necessarily be
relevant to civil engineering modelling.
19.3 Dataset information

Most of the leading BIM authoring tools store and utilise pre-defined collections of objects
referred to as the dataset. Each application has a distinct structure to its databases, most of
which reside in files located in a collection of directories. The most common dataset category to
be used is ‗parts‘ (see section 18.3.2). There are other software-specific settings that require
configuration to work. For example, Bentley BIM tools use components to define and quantify
constituent cost items, and the settings to do so would be decided by the project team. Dataset
information will be updated by Masdar‘s BIM Coordinator based on outputs from ongoing
projects.
19.3.2 Parts dataset and feature sets
Leading BIM applications categorise and group building objects into ‗parts‘. The Masdar dataset
provides parts (grouped into hierarchical ‗families‘) to use with Bentley BIM tools, based on the
UniFormat classification system. An example is shown in figure 16.
Figure 16 Screen capture showing example parts defined and provided in Masdar‘s dataset.
Version 2.0.3 77 of 224

MASDAR
For civil modelling applications a preference file of features would normally be used. An example
is shown in figure 17.
Figure 17 Screen capture showing example feature set defined for roads.
Version 2.0.3 78 of 224

MASDAR
20 Drawing standards
20.1 Introduction to drawing standards
This section focuses on BIM outputs, which may include sheet models and the composed sheet
files. Sheet files are composed from one or more sheet model files (such as extracted drawings
and details) and border files, and plotted at different scales. Plan and section information must
be in separate model files, except in the case of standard details. Standards in the MicroStation
design environment are defined and managed in library files which have an extension ―dgnlib.‖
20.2 Drawing numbering

Drawing numbers use fields from the file naming convention (see section 25.3), thereby helping
to maintain consistency between the file name and the drawing number. The drawing number
and the file name will match with the exception of the extension. For example:
CAD file name: MST-1B-FPL-AX-P1-0001.DGN
Drawing Number: MST-1B-FPL-AX-P1-0001
20.3 Drawing setup

20.3.1 Layers
Layer (or drawing level) structures are defined in chapter 4 (Element Coding Standard). For
design information Masdar is using the NCS layer naming convention and the UniFormat object
classification system.
Appendix 7 lists the DGNLIB files containing these layer definitions, which must be used for all
project CAD files.
All elements should be drawn by layer for line style, colour and weight. There will be some
exceptions when additional information is required on a single layer, and this must be agreed and
documented at the project level by the BIM Coordinators. When a file is submitted to Masdar all
layers shall be switched on and any extraneous data (such as construction lines) deleted.
20.3.2 Line styles
Custom line styles must not be used, except where absolutely necessary. In such cases they
must be agreed at the onset of the project and distributed to the entire project team in a pre-
defined process.
20.3.3 Colour tables
All colours must use the Masdar default colour table. Other applications should remap to the
MASDAR_COLOR table (illustrated in figure 18 and included in the delivered workspace). The
colour of objects would be used only to graphically segregate systems, components, or other
objects into a range of colours for ease of use. There is no dependency of plotted line weights to
the colour of objects.
Version 2.0.3 79 of 224

MASDAR
Figure 18 Illustration of Masdar‘s colour table.
20.3.4 Blocks/Cells
Masdar Block/Cell libraries include standard objects that are used to denote symbols and hatch
patterns (MicroStation uses cell libraries to store the standard hatch patterns)
.
For common hatch patterns all parties should use the ANSI library shown in figure 19 (see also
appendix 7). Where large areas require hatching it is unnecessary to hatch the entire area. In
order to make drawings readable small hatching areas should be selected that will clearly identify
the entire area. Hatching should be used to indicate where materials change or terminate.
Figure 19 Hatch pattern library.
Version 2.0.3 80 of 224

MASDAR
20.3.5 Text and dimension styles
20.3.5.1 General requirements
Standard text and dimension styles are provided in the following files, which shall be used for all
dimensions in a drawing:
MasdarDimensionsStyles.DGNLIB and MasdarTextStyles.DGNLIB
Table 24 lists the standard dimension styles that appear on plots for different sizes of drawing.
Table 24 Text and dimension styles (all sizes in mm)
A0 and A1 A3 and A4 Use

Text size Line spacing Text size Line spacing
2.50 1.90 2.00 1.50 Dimensions, notes, general text
3.50 2.60 2.50 1.90 Notes of special emphasis
5.00 3.75 3.50 2.60 Titles (on drawing)
3.50 2.60 2.50 1.90 Sub-titles (on drawing)
20.3.5.2 Text placement
Notes shall be clear, concise and unambiguous and be placed using the correct dimension and
text styles. Notes on all drawings shall be in True Type Arial font written in sentence case (lower
case with only the first word, proper nouns, abbreviations and acronyms in upper case letters).
Where background mapping is used, the notes shall be boxed and have a filled arrowhead and
leader, all in line weight 1. It should be placed to avoid detail, but where this is not possible, the
detail behind the note shall be clip masked (figure 20). Notes following linear features, such as
roads, should be placed as unboxed text along the alignment of the feature (figure 21). All text
shall be aligned so that it can be read when viewed from the bottom or right hand side of the
drawing sheet (figure 22)
Building to be
demolished
Figure 20 Text placement with a background map. Figure 21 Note placement for linear features.
Figure 22 Text alignment
Version 2.0.3 81 of 224

MASDAR
20.3.5.3 Dimension requirements
Dimensions on 2D deliverable drawings shall use the concepts outlined below.
 All dimensions are to be associative, with line suppression for continuous dimension strings.
 Dimensions should be located outside the floor plan or other view being dimensioned in order
to minimise clutter and overlap with other graphics. Dimensions outside the view should be
located at the top and/or the right side of the plans whenever possible.
 Dimension lines should be offset 9.5mm from each other. When dimensions must be shown
on the interior of a floor plan or other view, the dimensions should be arranged in continuous
strings for clarity and consistency.
 Terminators define the junction between a dimension line and the extension lines leading to
the start and finish of the dimension. These terminators are to be shown as arrowheads.
 Dimension text size should match the size of the text in the drawing. Where possible, the
dimension text should be placed at the midpoint and on top of the dimension line.
 Generally dimensions less than one millimetre shall be depicted to the nearest millimetre
 Only in tight spots will slashes be used instead of filled arrowheads.
 Metric dimensions will be in millimetres. There will be some exceptions such as in civil
engineering schemes where metres are a more appropriate unit due to the large distances
involved. This should always be noted on the drawing.
 When dimensions are taken from an existing drawing, electronic file, or document and used in
a new drawing, a note ―to field verify‖ must be placed with the dimension or referred to in a
general note.
 Dimensions ―not to scale‖ shall be noted with the notation NTS directly under the dimension
text. Sections and details not drawn to scale shall be noted NTS below their title. Drawings
not drawn to scale shall be noted ―not to scale‖ in the title block.
 Horizontal dimensioning slashes are to be oriented low end to high end and left to right.
Vertical dimensioning slashes are to be oriented similarly as viewed from 90 degrees.
 Adding leader lines to dimensions in already overcrowded areas should be avoided.
 Repeated dimensions or member sizes between views should be avoided. Entering

information in only one place helps to avoid errors in subsequent editing. Where dimension
lines continue, ensure that only one line exists.
 Dimension lines should not be closed. That is, where an overall dimension is shown, a
complete string of dimension should not be shown below it.
 Tolerance dimensions should be shown when closure is necessary.
 Grid and datum dimensions on new sheets can be repeated if they will clarify important
concepts.
 The dimension datum point should be identified in all drawings.
Version 2.0.3 82 of 224

MASDAR
Table 25 shows the two dimension styles that will be used on Masdar projects and which are
included in the DGNLib files provided in the Masdar dataset.
Table 25 Dimension styles for Masdar projects
Dimension Style Description Disciplines to be used with
Metric mm Millimetres – no decimal or label style All disciplines other than civil
engineering
Metric metres Metres – decimal style Civil engineering
20.3.6 Annotations
Symbols used to annotate the drawing are provided in appendix 8, including the standard settings
for text and symbology. Broad references to specifications or other disciplines‘ drawings such as
‗see engineering drawing‘ or ‗refer to specification‘ are not permitted. References to the
specifications should provide an exact reference location within the document: for example, ‗see
specification section F10-105‘.
Refer to the NCS for additional details.
20.3.7 Line work
The intent of the drawing will determine which elements should receive major emphasis and
stand out compared with items of lesser importance. General guidelines for items requiring
specific emphasis are listed in table 26.
Table 26 Line work emphasis
Work element Line work
Major construction Medium continuous line, heavy enough to contrast with all other line work
Existing work to remain Fine line, screening or notation
Existing work to be removed Screening, hatch pattern or by notation
Existing work to be moved Medium weight line or notation
Existing work to be relocated Medium weight line or notation
Temporary work Medium weight line or notation
Confirmed work Medium weight line or notation
Field verified work Medium weight line or notation
Future work Thin phantom line or by notation
Lines such as dimension lines, leader lines and arrowheads must be simple and sharp with the
point placed so as to avoid misinterpretation. All arrowheads must be filled.
Version 2.0.3 83 of 224

MASDAR
20.4 Composition technique

20.4.1 General principles
Masdar‘s drawing sheet templates must be used as the starting point for all drawings, with the
necessary model files referenced into a view created in the drawing. The following template file
must be used for all A1 sheet files (see also appendix 7):
MasdarA1Sheet1-100seed.DGN
At the time of writing Masdar is also preparing template files for non-A1 sheets, which will be
issued when available.
There can be only one drawing per file name and multiple drawings within a file are not permitted.
Plans, sections and elevations must not be mixed on the same drawing (with the exception of
plan/profile and standard detail drawings).
Drawing files must be composed mainly of reference files. Only information that is unique to an
individual drawing (such as notes, dimensions, shading and border information) shall be ‗live‘ in
the drawing file, and the information shall be placed within the drawing sheet view.
All drawings shall be saved to the agreed project format (section 1.4 of this document) unless
explicitly agreed otherwise by the Masdar BIM coordinator.
Figure 23 shows how a typical drawing sheet might be composed.
Drawing file
Model view (key plan)
Map tiles Drawing sheet view
Saved views
Nest depth 1
at required scale
Model view
Model file
Model file
Drawing border Tag
Model file Model file Image
Figure 23 Composition of a drawing sheet file
Version 2.0.3 84 of 224

MASDAR
20.4.2 Referencing
Referencing ensures that there is only ever one instance of an object, that there is proper
coordination between disciplines, and that the correct version of information is being used by the
project team. All common CAD applications support file/model referencing.
20.4.3 Sheet layouts
Figure 24 shows a typical layout of 2D sheet files for deliverable drawings. The working area
accounts for various annotations common to each drawing, leaving a specific area for the
depiction of master data according to the drawing‘s scale. The configuration will remain constant
for all sheet sizes.
Drawing area Direction arrows

The drawing area is the portion of the sheet containing Show both North and true North
drawings, keynotes, key plans, schedules, and other arrows if the site rotation is not
graphic and text data necessary to illustrate the work. north-up, and the direction of
Mecca
The drawing area is divided into modules, the number
and size of which depend on factors such as sheet
size, drawing scale, margins, title block area, client
Notes
requirements and typical drawing blocks size.
Location of general notes
Key plan
Key plans denote specific sections of work
per sheet and can depict the scope of work
boundaries. A hatch pattern is typically used
to show work in a specific area or sector.
The key plan will usually consist of:
- composite plan
- grid pattern for the building or plan
- hatch pattern denoting area/scope of work
Graphical scales and titles

Scales and titles are placed in this area
Figure 24 2D sheet file layout
In the drawing sheet view the appropriate drawing border must be selected from the list. It must
not be scaled, and any unused drawing borders must be deleted.
The default master model (model space) shall be used to assemble all relevant reference files.
Only those model files that constitute part of a drawing shall be referenced; all non-displaying files
shall be detached in both the model view and the drawing sheet view.
Where reference files are attached, a name shall be assigned in the logical name section of the
dialog box, as well as an accurate description of the attached file in the description section.
Version 2.0.3 85 of 224

MASDAR
Reference files that are attached in any model view shall be attached in their true position
(without nesting) and must not be rotated or scaled in any way.
Raster files, such as photographs, which form part of a drawing shall be positioned in the drawing
layout as required using the standard tools. Approved raster file formats are .JPG, .TIF and
.HMR, and they can be colour, greyscale or monochrome.
To ensure that attached reference files (including raster files) are found by the Masdar technical
coordination system they shall be attached without any environmental variables and with any
‗save full path‘ option switched off.
When a submittal consists of multiple sheets referencing the same set of model files, only one
instance of that model file shall be submitted. If sheets use different states of the model file then
each instance of that model file would be named appropriately (including the revision).
Drawings created by different design disciplines for the same facility shall maintain the same
orientation and, if appropriate, the same sheet layout.
20.4.4 Borders (blocks files)
Paper sizes in the ISO A series shall be used for all drawings, using a maximum of A1 size (see
figure 25). Other sizes may be required in exceptional circumstances and their use shall be
subject to prior agreement with the Masdar BIM Coordinator. Sheet margins shall be 20mm (top,
bottom and right) and 40mm (left).
Masdar drawing sheet templates are available in A0, A1, A2, A3 and A4 sizes. Appendix 9
shows an example of a Masdar drawing sheet template.
A1 A3
841 x 594 420 x 297
A4
297 x 210
A2
594 x 420
Overall A0 size 1189 x 841 mm
Figure 25 Standard paper sizes (dimensions in mm)
20.4.5 Scales
The drawing scale is the ratio of measuring units expressing a proportional relationship between
a drawing and the true size item it represents. The selection of the proper scale determines the
readability of the drawing. The scale chosen should be large enough to allow the drawing to
display its graphic, dimensional, and textural content clearly without congestion or ambiguity.
Drawings are created at full size and plotted at the appropriate size for the project.
Version 2.0.3 86 of 224

MASDAR
Graphic elements within the drawings such as notes, leaders, dimensions, reference indicators
and other scale dependent symbols must be sized according to the scale of the final plot. Scales
should be selected from those listed in table 27.
Table 27 Sheet scales
1:1 1:25 1:500

1:2 1:50 1:1000
1:5 1:100 1:1250
1:10 1:200 1:2500
1:20 1:250 1:5000
All drawings must include a scale indicator in order to avoid misinterpretations when plotted to a
size other than that intended. If more than one scale is used on a drawing then the scale shall be
typed under each sub title (see appendix 8 for details). If a sketch or detail is not to scale then
‗NTS‘ shall be entered in the scale tag.
Where additional or non-standard scales are considered necessary then prior approval shall be
sought from the Masdar BIM Coordinator.
20.4.6 Annotation
20.4.6.1 General requirements
If the legend, notes, key plan and bills of material require their own drawing, the drawings which
relate to it shall have a relevant note detailing this drawing number.
20.4.6.2 Revision logs
Revising shall be in alphabetical order with the latest revision shown in the lowest line of the
revision history box. Previously approved revision details are added above the latest details and
shall be filled in accordingly.
The history of draft revisions is not to be recorded in the revision history box. Revisions shall
follow the A, B, C sequence. See chapter 6 for details.
20.4.6.3 Revision clouds
In addition to the information about revisions required in the title block, all latest revisions shall be
indicated by a cloud and clearly understandable revision identification at the actual parts of the
drawing which have been revised. See appendix 8. Each discipline will have its own layer for
revisioning according to the NCS layering standard, and revisions will be annotated on the
revision cloud layer.
20.4.6.4 Callouts
The requirements for callouts are given in appendix 8.
20.4.6.5 Abbreviations on drawings
Terms should be spelled out fully wherever possible. Abbreviations should be used only to
reduce space or improve clarity. The use of obscure or undefined abbreviations is not permitted.
Version 2.0.3 87 of 224

MASDAR
Where abbreviations are used in notations on drawings they shall be restricted to commonly used
and understood abbreviations. When the meaning of an abbreviation is in doubt then it should be
explained by one of the following methods.
- A reference on the drawing to the appropriate British or ISO Standard
- The abbreviation being clearly defined in a legend on the drawing
- Reference to a separate discipline-specific drawing showing the abbreviation and its meaning.
20.4.7 Title block information
The project title block shall be used on all the project specific sheet files and must contain the
following information as a minimum.
- The phrase ‗MASDAR‘
- The Masdar logo and project logo
- Originator name and logo
- Project name
- Project number
- Drawing title
- Drawing number and revision (as per the project standard)
- Date and explanatory note for each revision
- Drawing status (as per the project standard)
- Drawing submittal number (as per document numbering system)
- Drawing date (as per the project standard)
- Plotting size and scale (for example ―1:50 at A1‖)
The drawing title shall read from the top to the bottom of the box in a clear progression from the
project title through to the location and the nature of the work represented. An example Masdar
drawing title block is shown in appendix 9.
The drawing borders contain attribute/tag fields which shall be updated using the application-
specific edit and update commands. Title block attributes shall be in upper case.
20.4.8 Key plans
A key plan is to be used to locate the area of the drawing in relation overall layout and, if in a
series of drawings, also to the adjacent sheets.
All general plan drawings shall have a key plan indicating where they are located within the
particular (sub) project. All general plan drawings shall have an indicator of the direction ‗North‘
and the direction of Mecca, placed in the top right corner of the border file.
20.4.9 Other annotation
In general, annotations shall appear in sheet files only. They shall be placed on their own
approved layer and be in a True Type font, unless defined otherwise in the relevant graphics
coding (see also chapter 4).
Version 2.0.3 88 of 224

MASDAR
20.4.10 Cut lines
Where part views are shown or where there is a series of drawings, cut lines with adjacent
drawings shall be clearly shown. The annotation ‗continued on drawing number xxx‘ shall be
added between the cut line and the nearest sheet edge and rotated to the same angle as the cut
line (figure 26)
Figure 26 Cut lines
Version 2.0.3 89 of 224

MASDAR
20.5 2D detail drawings library

Each project contributor would generally have its own library of standard details for objects,
typically varying in scale from 1:1 to 1:20. They could be organised using one of the following
subtopics:
- details as blocks/cells
- details as reference files
- details specific to the project.
20.6 Plotting
20.6.1 Plot drivers
Printing for hard copy and PDF versions must be done using a standard plotting procedure and
the following Masdar plot drivers (see appendix 7).
Hard copies PDF copies

Masdar-general-A0.PLT Masdar-pdf-A0.pltcfg
For hard copies, the plotter or printer (with suitable size paper) should be set on the host machine
prior to using the ‗Masdar-general‘ plot drivers. This printer driver is a MicroStation wrapper
around the Windows printing system and will set the line weights and line-style scaling only, the
paper sizes would depend on the system Windows driver.
Drawings must be created in their native size and to the exact scale. All drawing files shall, when
plotted on the project‘s own system, produce an exact replica of the hardcopy supplied.
20.6.2 Pen tables
Pen tables should be used for text substitution for date, time and file stamps only. Rest of the
representation rule should be to use WYSIWYG (what-you-see-is-what-you-get). No colour-to-
weight mapping will be used. The on-screen colours will translate into the closest plotted
representation of each colour. Industry standard colour books or palettes could also be used to
extend colour palettes to achieve a wider range of plotted colours. The symbology of the object
can be ‗overwritten‘ using symbology overrides in the sheet model.
20.6.3 Half-size plotting
Half-size plots could be used for creating draft prints. They could be generated by plotting
drawings configured with the full-size border at half size using provided plot drivers that adjust
line weights and default ‗line types‘ to an equivalent half-size width.
20.6.4 Raster images
Raster images may be included on plots and for the purposes of simple illustration or to
represent, for example, a logo on a border. Raster images do not generally respond to efforts to
Version 2.0.3 90 of 224

MASDAR
manage the symbology on plotted output, or inherit the line weight or colour value (as it relates to
plotted output line thickness). The use of raster Images will cause problems with plotting unless
care is taken with image quality and correct density for the required use. Different output devices
will generally render the raster image similarly but care must be taken to research and test the
output on all necessary devices before the Image is used on finished documentation. The use of
raster images will also increase the size of the plot file output, resulting in much longer plot
generation and processing and production time.
20.6.5 Line weights
The line widths defined in table 28 will be sufficient for most drawings. Line widths would
decrease proportionally if the plotted drawing were reduced to half size, and the use of extra fine
line widths should be avoided in such cases.
Table 28 Line weights
Object description Weight Pen (mm)
Material indications, surface marks, hatch lines, patterns Fine 0.18
Dimension lines, leaders, extension lines, break lines, hidden objects, dotted lines, dashed
Thin 0.25
lines, setback lines, centre lines, grid lines, schedule grid lines
Object lines, property lines, text, lettering, terminator marks, door and window elevations,
Medium 0.35
schedule grid accent lines
Title, edges of interior and exterior elevations, profiling, cut lines, property lines, section
Wide 0.50
cutting plane lines, drawing borders
Match lines, large titles, footprints, title block borders, sheet borders, schedule outlines Extra wide 0.70
Major title underlining, separating portions of design XX wide 1.00
Border sheet outlines XXX wide 1.40
Cover sheet line work XXX wide 1.40
Notes: 1. NCS version 4.0 Plotting Guidelines has removed the dependency of colour for plotted line weights. There will
be no colour-to-weight mapping anywhere in the system.
2. Recommended line types are given in UDS Drafting Conventions Module page UDS-04.14
20.6.6 Re-symbolisation and text substitutions
Re-symbolisation will not be permitted, except for the text substitution of date, time and file
stamps. The printed file should come as an exact geometric copy of the electronic CAD drawing.
Masdar-Text.tbl file shall be used for text substitutions while plotting.
20.6.7 Electronic plots and 3D PDF
Innovative tools and processes will be adopted where appropriate, including the following.
- Redlining of electronic plots
- Mark-up enabled PDF plots
- 3D PDF with saved views, assembly sequences and animation.
Version 2.0.3 91 of 224

MASDAR
21 Validation of information
An approvals process must be established for each project to ensure that model and drawing files
are adequately checked, and to enable the design teams, Masdar and the contractor to approve
and sign-off the development of the design information at appropriate points. The approval
process should be specified, agreed and documented as early as possible in the project. The
process should include a full check of the data coordination and registration across the whole
data set before the design check proceeds. It should also include an assurance that the data to
be approved has been checked for compliance with this CAD Standard and project data
standards. Masdar will use appropriate software to automatically check, amongst other things,
the following items.
- Layer names comply with project standards
- Dimension text has not been overwritten or disassociated (because this could cause errors
in quantification).
- Title sheet attribute information is complete and compliant.
- All objects in the design model have a part assignment.
- All objects are assigned to their proper level based on part definition
- All objects requiring identification contain a unique identifier.
Any file which fails to comply will be quarantined and a report outlining the non-compliance will be
sent to the originator.
Version 2.0.3 92 of 224

MASDAR
Chapter 6
Data management guide
This chapter describes how project data should be produced and managed in a consistent format
through the life of a Masdar project. The strategy provides a framework to create an integrated
design that will facilitate multi-disciplinary coordination and collaboration during design and
construction, and provide rich data that can be used through the entire life cycle of an asset.
It guides the user through the basics of the Masdar collaboration system, CAD and 3D modelling,
and its interface with the Masdar GIS tools. It is applicable to all parties involved in the
preparation and use of information throughout the project lifecycle, and the principles for
information sharing and modelling are equally applicable to building and civil engineering
projects.
The success of this approach depends on adherence to the standards and content laid out in this
document.
Version 2.0.3 93 of 224

MASDAR
22 General principles of collaborative modelling

A Bentley ProjectWise system has been chosen to deliver technical information in a controlled
and managed environment, permitting sharing without loss of reference file or component
integrity, and capable of referencing models of different origins and ownerships into a single
project model. Masdar‘s technical information includes 2D and 3D CAD and BIM models,
drawings and related data such as calculations and specifications.
The system controls workflow states in a coordination environment with sharing across project
participants and provides tools for reviewing and approving data for sharing and project issue.
The modelled CAD data is structured and becomes a source of data for reference by all Masdar
users, for GIS, drawings, illustrations, visualisations, calculations, bills of quantities, clash
detection, construction sequencing, and operation.
Data is created and stored in a shared ‗single source of truth‘ environment for use and access,
and delivering data in a timely manner and preserving it for the length required by Masdar for
managing assets through the life of a facility. Figure 27 shows a simple representation of the
necessary environment.
Coordinate and collaborate

Sharing content and monitoring performance
Quality control & assurance Rules for re-use
Create Deliver
Paul King Paul King
Bentley Systems Bentley Systems
+44 (0)7966 162 695 +44 (0)7966 162 695
Get the right
Move content into content to the
data collaboration right audience in
environment for the right format
reuse, distribution at the right time
and storage
Manage location of content and access
Preserving data in its rich and

natural state for the long term Preserve
management of building assets
Figure 27 The managed coordination and collaboration environment
Created data is stored in a secured directory structure with proper protocols defining storage and
retrieval rights. When design and construction teams create project data they are required to
follow the quality control requirements to ensure the data is correct, in the proper format with
appropriate meta-data.
Delivery of data in read-only format is defined by the rules and definitions set up in ProjectWise.
The intent is to ensure that right data is available in the right format, when needed. Preserving
data in its rich and natural state is a requirement for the long term management of building assets
- operational data stored in the coordination system will ultimately reside in Masdar‘s facilities
management database.
Version 2.0.3 94 of 224

MASDAR
23 Technical coordination process

23.1 General requirements for collaboration
The effective communication of high quality information between design team members,
manufacturers, constructors and operators is essential for the satisfactory realisation of Masdar‘s
goals for the programme.
Masdar is using best practice based on the Avanti ‗Standard Method and Procedure‘ for
developing and presenting the design information and documentation. This standard has now
been embodied within a new British Standard – BS 1192:2007 ‗Collaborative production of
architectural, engineering and construction information - Code of practice‘.
BS 1192 establishes the methodology for managing the structure, production, distribution and
quality of construction information using a disciplined process for collaboration. It supports the
engineering technical content used in designing, constructing and operating the city and is
applicable to all parties involved in the preparation and use of information throughout the design,
construction, operation and deconstruction of a project. BS 1192 requires the following
procedures to be adopted.
(a) A ‗Common Data Environment‘ (CDE) which includes common origin of the coordinate
system for all data and a structured, spatially coordinated data set that allows information to
be shared between all members of the project team.
(b) A project ‗standard method and procedure‘ agreed and committed to by all the relevant
parties who will be involved in each project of the whole programme.
(c) A suitable information hierarchy that will support the concepts of the CDE and the lifecycle
coordination environment.
(d) Roles and responsibilities in particular the responsibility for coordinating the work of the
various design disciplines.
(e) A file container/folder structure that supports federation of multiple data files to combine
model information.
(f) Document naming conventions so that relevant information can be identified using file
names, and reference codes for the status and revision of documents must be agreed.
(g) All teams adhering to the systems, tools and standards defined for each project.
The data structure is designed to support the requirements of a future BIM hub and GIS.
Version 2.0.3 95 of 224

MASDAR
23.2 The common data environment (CDE)

Data within the CDE is finely granulated and structured to ease its reuse. It provides the ability to
produce traditional drawings or documents from multi-authored data and will provide the following
advantages.
(1) Ownership of information remains with the originator although it is shared.
(2) Sharing information reduces the time and cost in producing coordinated information.
(3) Any number of documents can be generated from different combinations of model files.
(4) Spatial co-ordination becomes a by-product of using the CDE and will deliver ‗right first time‘
design information.
(5) Design information can be reused for construction planning, estimating, cost planning,
facilities management and other downstream activities.
23.3 CDE basics

The CDE is a data code of practice rather than a drawing standard.
Includes all technical documentation including models, drawings, specifications and calculations.
All data is modelled in spatially correct position based on a common grid, common origin common
projection.
Data is drawn in real world 1:1 scale and drawings are publications from the model, unless they
are special details and sketches which clarify the model output.
Data is held in a ‗nested container-based‘ data hierarchy and file identifiers relate to the hierarchy
Data in files is classified according to its element type and layers/levels are based on a
classification standard (Masdar uses the Uniformat classification system).
Version 2.0.3 96 of 224

MASDAR
23.4 Functional areas of the CDE

23.4.1 Overview
The CDE is a means to allow 2D and 3D information to be shared between all the members of
the programme team. The CDE enables multi-disciplinary, multi-project design teams to
collaborate in a managed environment where the build up of information follows the design
sequence. A high-level process view of the CDE is shown in Figure 28.
SHARE WORK IN PROGRESS
Verified design data shared Non-verified design data

with the project team: used by in-house design
team only:
Reliable design data
Drafts
Ongoing design development
Development concepts
Comment and information
Minor versions
Major versions
Fit for stated purpose: Architect
- coordination Structural engineer
- information
- internal review & comment Civil Engineer
- construction approval. Other Projects
ISSUE ARCHIVE
Coordinated and validated Project history maintained
design output for use by for knowledge, and
project team regulatory and legal
requirements:
Production information fit for
stated purpose: As built drawings
- tender Change information
- costing Operation and maintenance
- contractor design details
- manufacture
Legacy data
- construction
- as built
Figure 28 Common Data Environment (CDE) Process
23.4.2 Work in progress (WIP)
The WIP section is where members of the project team carry out their own work. Such work is
likely to be stored on in-house servers with access to view or change information limited to the
owner. The design teams are responsible for the quality of the WIP information and should
ensure that appropriate checking and review processes are in place. Therefore, each model file
will only contain information for which each design team is responsible. The design team will also
include sub-contractors who develop a design based on consultants‘ designs. A 3D model file
could be considered to comprise a series of levels as shown in Figure 29.
WORK IN PROGRESS
Architect’s WIP:
Building grid
Architectural columns
Architectural walls
Figure 29 Example of the architect‘s WIP section of the CDE
Version 2.0.3 97 of 224

MASDAR
23.4.3 Share
When the models reach a status that is ‗fit for coordination‘ (S1) or at pre-agreed intervals then
the model information can be uploaded into the ‗Share‘ section of the collaboration environment.
To get to this area all model files will have to have been thoroughly peer-reviewed, fit for a
specific purpose and checked for compliance with Masdar‘s CAD Standard (chapter 5). This is
shown in figure 30(a). Once in the ‗share‘ section, model files are available to be downloaded by
the whole design team, specialist contractors and others as appropriate.
The ‗share‘ area is designed to overcome the reticence of some design team members to release
their information to others until all perceived problems had been resolved – an approach that
slows the exchange of data and extends delivery dates.
The early release of information into the collaborative ‗share‘ area assists in the rapid
development of the design solution. In order to allow this to be achieved the concept of
information ‗status‘ has been adopted; this gives ownership of the data to the design teams and
restricts access by the construction teams until information is sufficiently coordinated
The data shared with a status of ‗fit for coordination‘ should be in the native CAD model format.
Other data/information uploaded to the ‗share‘ section should be produced in non-changeable
electronic formats such as PDF. The same process can be used for all other types of documents,
such as reports and spreadsheets. These downloaded models can be used as background
information onto which the recipient can overlay their design information, as shown in figure
30(b).
Model files that are downloaded by other design teams must never be re-uploaded. When a
model file is used as background information by another design team member, as shown in figure
30(c) it is important to ensure that this does not result in, for example, objects in 3D models being
duplicated. Therefore, a procedure must be agreed that ensures that information only occurs
once in the shared area. In the example shown in figure 30(c) the structural engineer has
designed the structural member sizes and takes ownership of the structural column layer. When
the structural engineer uploads this information into the shared area the architect‘s file must be
revised and re-shared to remove the architectural ownership of the columns, as shown in figure
30(d).
Version 2.0.3 98 of 224

MASDAR
SHARE WORK IN PROGRESS
Status: fit for coordination Architect’s WIP:

Building grid Building grid
Architectural columns Architectural columns
Upload from
Architectural walls WIP Architectural walls
to
SHARE
(a) Initial upload: architects models uploaded to the ‗share‘ area, available to all
Process map
SHARE WORK IN PROGRESS WORK IN PROGRESS
Process map
Status: fit for coordination Architect’s WIP: Structural engineer’s WIP:
Building grid Building grid Building grid
Architectural columns Architectural columns Architectural columns
Architectural walls Architectural walls Architectural walls
(b) Sharing model files: architect‘s information downloaded by structural engineer

Architectural columns Architectural columns Architectural columns
Architectural walls Architectural walls Architectural walls
STRUCTURAL COLUMNS
(c) Coordinating model files: structural engineer designs columns and takes ownership of column model

STRUCTURAL columns AMENDED architectural Upload Architectural columns
columns structural
Architectural walls columns Architectural walls
AMENDED arch. columns Architectural walls from WIP to STRUCTURAL COLUMNS
SHARE
Download structural columns

from SHARE to WIP
to
SHARED
(d) Removing obsolete references and update: structural engineer uploads column model to shared area. Architect
downloads latest structural column model and amends his files accordingly.
Figure 30 Sharing model files
Version 2.0.3 99 of 224

MASDAR
23.4.4 Issue
The ‗ISSUE‘ section of the collaboration environment contains drawings or models which are
snapshots of the shared information taken at a specific time (an agreed Phase Delivery). They
are compiled by referencing the relevant approved model files into a drawing sheet that contains
a title box and associated text attributes. A drawing rendition or model snapshot is then created in
a non-changeable format, for example a PDF file. Such a drawing rendition will contain a
snapshot of the coordinated multi-authored model files in the ‗shared‘ section of the CDE as
shown in Figure 31.
SHARE Files uploaded from ISSUE

Architectural
SHARE to drawing in
Status: fit for construction DOCUMENTATION Coordinated and validated PDF format
approval design output for use by
project team
Documents published with Structural drawing
status ‗fit for construction‘ in
a suitable format M&E drawing
Figure 31 Creating drawings from shared models
23.4.5 Archive
The ‗Archive‘ section of the CDE is for inactive or superseded material. Such information
provides a history of the project information transfers, enables knowledge retention and can be
used for legal and regulatory purposes or for delivery to Masdar‘s FM system. Archiving should
be automatically managed by the coordination and collaboration systems, and a history of
superseded information will be kept available so that roll-backs can be achieved.
23.4.6 Review, checking commenting and approval
Before information can be placed in the ‗Issued‘ or ‗Shared‘ section of the collaboration
environment and made available to the wider project team, for any drawings or models must be
checked and approved.
A formal review, checking and approval procedure to move data into either the Share or Issue
area of the system has been defined by Masdar in their process document ‗Design Management
Procedure‘ This process has been incorporated into the system and includes tools to support the
review.
At agreed dates and gateways various projects and design disciplines will produce drawings
through extractions from approved model files in their respective WIP areas. These will be
checked, revised as necessary and approved by the lead designer before being submitted to
Masdar for sign off to the ‘Share‘ or the ‗Issue‘ area.
The required deliverables are defined by Masdar and listed in the chapter 3 (Design Information
Modelling Guide).
Version 2.0.3 100 of 224

MASDAR
24 The Masdar collaboration environment

24.1 Introduction to ProjectWise
Masdar‘s collaboration environment is based on Bentley‘s ProjectWise engineering content
management solution, suitably configured for Masdar‘s project workflows. ProjectWise is
designed to facilitate a scalable project data management system that provides a ‗single source
of reference‘ to designers, constructors and operators for engineering data content including CAD
and BIM models, drawings and supporting documents. It is driven by a central ProjectWise
integration server (housed at Masdar) which uses a database to catalogue all data and meta-
data, and a file server to store the files themselves. It also provides the necessary security
settings and links to other systems and services. ProjectWise offers three types of connection for
users:
 Windows Explorer style (figure 32) for those who need to create, edit and submit files
 Web client (figure 33) for general use in accessing data files.
 Web client for the design control submission, review and approval process (figure 34).
In order to overcome the problems of accessing large files for creation or editing, ProjectWise
supports a delta change mechanism so that only changes to files are transmitted to and from the
servers after initial creation. It also provides for local file caches and gateway services to be
installed at remote sites, offering the facility for remote users to work as if they are local to the
system. Unlike many ‗post and copy‘ document management systems ProjectWise offers access
to project data directly, providing and controlling a single source of project truth. Complete details
of the system architecture and how connections are made are available from Masdar‘s DDC.
Figure 32 ProjectWise Explorer (Windows Explorer type interface)
Version 2.0.3 101 of 224

MASDAR
Figure 33 ProjectWise web client (for general access to files)
Figure 34 ProjectWise web client for the design control submission, review and approval process
Version 2.0.3 102 of 224

MASDAR
24.2 Structure of the collaboration system

24.2.1 Supporting WIP, SHARE and ISSUE
ProjectWise has been set up with three distinct collaboration areas (figure 35) matching Masdar‘s
collaboration processes. It should be noted that this supersedes an early repository set up as a
first-step system.
Masdar ProjectWise collaboration system
Work in Progress SHARE ISSUE

(WIP)
Viewable and Viewable and
Secure area for a reference- able area for reference-able read
design partner or programme-wide users only area to hold data
contractor and their to hold read only data that has been reviewed
subs to work and create deemed suitable for and approved for issue
or place their collaboration but not yet to the programme at a
submissions is working issued as part of the given phase milestone.
outside the system. project deliverable.
Figure 35 Masdar‘s ProjectWise collaboration system
The WIP area is used by contractor/designer/consultant to create data information before officially
submitting and issuing it to the programme. The WIP area is private, and ProjectWise
permissions are configured in such a way that only the owner of the submittal area can see the
contents. The folder structure and meta-data stored in WIP area are described elsewhere in this
document.
Shared and Issued areas collect approved data and data that is published for sharing. It is public
area accessible by all participants of the program. Only data from Shared and Issued areas
should be used by contractors/designers/consultants when they need data produced by other
contractors/designers/consultants.
An alternative approach - external WIP (figure 36) - permits design partners and contractors to
create data working outside the system and upload it into the WIP area for submission to the
Masdar programme. Design data for WIP is loaded using a ProjectWise Excel Import/Export tool
as described elsewhere in this document.
External WIP Work in Progress SHARE ISSUE

(WIP)
Design partner or Viewable and Viewable and
contractors own Secure area for a reference- able area for reference-able read
systems for design partner or programme-wide users only area to hold data
creation prior to contractor and their to hold read only data that has been reviewed
submission to the subs to work and create deemed suitable for and approved for issue
programme for or place their collaboration but not yet to the programme at a
review, approval, submissions is working issued as part of the given phase milestone.
Sharing or Issue outside the system. project deliverable.
Figure 36 Masdar‘s ProjectWise collaboration system – external WIP
Version 2.0.3 103 of 224

MASDAR
24.2.2 Review and approval for SHARE or ISSUE
In order to move data in ‗WIP‘ to a ‗SHARE‘ or ‗ISSUE‘ status, a review and approval workflow is
required. This adds a further area to the ProjectWise system - the Design Control System (figure
37) - which provides tools for submission, distribution for review and comment, consolidation of
reviews, and return to design partner for rejection or change and agreement before approval.
DCS is used for tracking submissions, transmittals and performing review and commenting.
Once data is approved as ‗fit for sharing‘ or ‗fit for issuing‘ it is moved to the ‗Shared‘ or ‗Issued‘
area accordingly. Before data can be submitted into DCS for review it has to pass an automated
technical quality check using a software component called CAD QA. There are two review cycles
possible in DCS:
(1) Short review cycle - used to validate that data is fit for Sharing
(2) Full review - used to approve data as described in the Masdar quality assurance workflow.
DCS tracks the history of committed documents. Each committed revision of a CAD document,
and the comments provided for that revision, are stored and can be accessed at any time.
ProjectWise used two data sources to hold the different areas of the collaboration system:
(1) Masdar WIP, Shared and Issued

(2) Masdar DCS data only
REVIEW AND APPROVE

Design Control System (DCS)
Handles the review and approval of data submitted to the programme. Capable of
distributing submissions for review, capturing comments and marked up documents
and tracking the workflow of a review. Matches Masdar‘s ISO process.
External WIP Work in Progress SHARE ISSUE

(WIP)
Design partner or Viewable and Viewable and
contractors own Secure area for a reference- able area for reference-able read
systems for design partner or programme-wide users only area to hold data
creation prior to contractor and their to hold read only data that has been reviewed
submission to the subs to work and create deemed suitable for and approved for issue
programme for or place their collaboration but not yet to the programme at a
review, approval, submissions is working issued as part of the given phase milestone.
Sharing or Issue outside the system. project deliverable.
Figure 37 Design Control System for review and approval
Version 2.0.3 104 of 224

MASDAR
24.2.3 The review-approval process
The overall review process is shown diagrammatically in figure 38.
Return to revise
and resubmit
No
DCS Full cycle Review/comment,

designer response, Accepted?
approval
Short cycle Yes
Commit to DCS Publish for sharing Publish approved

Create formal Submittal
WIP Shared Issued

Designer
Reference scan,
CAD QA
Documents
CAD QA Upload to PW using XREF
(opt.) Excel Import/Export
Submittal Documents
(design data)
Designer DDC
PMC DDCl
Denotes drawings references
Figure 38 Masdar‘s review process diagram
24.2.4 Review in DCS
The review, commenting and approval of the design data will be done in DCS, as described
below and illustrated in figure 39. (The process is based on Masdar‘s Quality Assurance Design
Management Procedure.)
(1) The review starts once the designer‘s document controller commits design data from WIP
into DCS and registers a formal Submittal.
(2) DCS notifies PMC DDC about the incoming submittal. From that point the review process is
driven by the PMC document controller (DDC). The DCC uses DCS to group the submitted
data into Review Sets and distributes them to the review teams.
(3) DCS notifies the reviewers included in the distributed Review Sets. The Reviewers then use
DCS tools to provide comments (DCS allows multiple reviewers to comment simultaneously).
Comments provided by Reviewers are collated by the PMC document controller. If required,
the designer‘s response to comments is requested and collected into DCS.
(4) Finalised comments are sent back to the originator for processing.
(5) If submittal documents need to go through multiple review iterations then, after one review
iteration is finished and comments are collected, the PMC document controller would initiate
the next review iteration. Both originals and comments provided so far go into next review
iteration.
Version 2.0.3 105 of 224

MASDAR
(6) Once the review and approval is completed all outstanding comments are sent back to the
Designer regardless of whether the submittal was accepted. Then:
a. If the submittal has been accepted the PMC DDC publishes the documents into the
ISSUED area.
b. If the Designer was requested to revise and resubmit a submittal then the review cycle
starts again with newly re-submitted documents, and no data is published into the
ISSUED area.
Start Designer document control

DCS
PMC document control
Reviewers
Distribute design data for

review
Reviewer 1 Reviewer 2 Reviewer N
Provide Provide Provide

comments comments comments
Collate all reviewers

comments
Distribute comments to
contractor/designer/consultant
for response
Provide response to
reviewers comments
Distribute designer
response to reviewers
Reviewer 1 Reviewer N
Reviewer 2
Accept/reject Accept/reject Accept/reject

response response response
Collate, apply comment

status (open/closed)
Distribute final comments to

contractor/designer/consultant
Yes Yes
Next
Accepted?
review?
No No
Documents and comments
Ready to publish go to next review iteration
Revise and resubmit

needed
End End
Figure 39 Design data review process (one iteration) using DCS
Version 2.0.3 106 of 224

MASDAR
Figure 40 illustrates the mapping of Masdar‘s review procedure to the DCS review process.
Figure 40 Mapping of existing Masdar procedure to DCS review process
Version 2.0.3 107 of 224

MASDAR
25 Data structure
25.1 Container folder structure
ProjectWise uses a folder structure (that looks like the familiar Windows Explorer) to present data
housed in the database. The structure is designed to assist collaboration and works on a
hierarchical ‗Russian doll‘ container principle, tiered based on the following concept.
1) Collaboration phase (WIP, Share, Issue)

2) Delivery phase
3) Project
4) Plot / zone / locator
5) Originator
6) Agent / discipline
7) Detail folders including the following:
- Design files (2D and 3D models),
- Drawings - sheet files (2D deliverable files)
- Specifications
- Calculations
- Reports
- Sketch and photographs
8) A global folder that contains files that are global to ADFEC for example CAD seed files or
global standards
9) A site-wide folder that contains files for use across the Masdar City site
A common structure from tier 1 to 4 needs to be maintained. tier 5 (originator) is dropped after
WIP but the data referencing originator is kept in file meta-data so these can still be found by
using ProjectWise searching. Tier 6 remains common.
In tier 7 (detail folders) there is no limit to the number of folders although initially it is restricted to
the main technical data deliverable requirements. If a project requires further folders then this
should discussed with the Masdar DDC, although the first consideration should be whether files
could be identified using meta-data rather than folder location.
The respective folder structures are shown in figures 41 and 42.
Version 2.0.3 108 of 224

MASDAR
Data Source
Files/Documents
WIP
SHARE Global Project
ISSUE Phase
Project
Plot/Zone/Locator
Originator
CAD Files Models
Drawings
Global Files
Specifications
Site Wide Files Calculation
Figure 41 WIP folder structure
AFDEC
Files/Documents
WIP
SHARE
ISSUE
Masdar City
Delivery Phase 1
Masdar HQ
F08
Architecture
Global Files Structural
Site Wide Files Etc, etc
Figure 42 Folder structure after WIP
Version 2.0.3 109 of 224

MASDAR
25.2 File identifiers

25.2.1 Overview
A file naming convention is required to in order to deliver a rapid search capability for all relevant
project documents and data being managed through Masdar‘s technical coordination and
collaboration systems. Since the search facility is in place to help all project participants, the
naming convention must suit the needs of each project as a whole, not individual the needs of a
single designer, specialist or contractor. However, it does need to take account of the needs of
the individual organisations in the wider team, as well as the need to collect, manage and
disseminate data and documents within a common data environment over the life of a project.
25.3 File naming convention

25.3.1 File name structure
The following convention will be adopted when defining a file identifier for any Masdar project
document, including building information models, CAD drawings, facilities management outputs
and other site-wide data. Each file name consists of six fields plus the file extension:
[Project] - [Phase] - [Originator] - [Discipline] - [File type and level] - [Number]
The PROJECT and ORIGINATOR define the project and the owner of the file information. The
LEVEL field locates information within the building. The remaining fields are used to uniquely
identify the file. The use of hyphen delimiters between the fields enables the use of varying
length codes; for example a two or three character code could be used for the originator. Each
field should be kept to the smallest number of digits but the use of the hyphen enables the use of
variable field lengths if required.
At the start of each project a master document index must be created that lists all necessary ‗file
identifiers.‘
The revision reference number and other related meta-data will be managed using ProjectWise.
25.3.2 Project
[Project] is a three-character alphabetic code that is used by the project team to identify the
project. Table 29 lists example PROJECT codes where there are multiple sites within a project.
Alternatively, the project code could also represent the actual project number. Additional three-
letter designations can be requested.
Where an organisation needs to use their own internal project numbers, they can be indicated in
the drawing title block using a separate ‗project number‘ box.
Version 2.0.3 110 of 224

MASDAR
Table 29 Project location code examples
Code Project location Code Project location
BVL Branded villas MIN MIST neighbourhood
ENW Enabling works MST MASDAR Institute of Science and Technology
EPS External parking structures PRJ Project

INF Infrastructure PRM Piping ring mains
LND Landscaping PRT Personal rapid transit
LRT Light rail transit SAF Site administration facility

MHQ MASDAR headquarters SID Site infrastructure design concept
25.3.3 Phase
[Phase ] is a two-character alphanumeric code that identifies the phase of a project.
Table 30 Phase
Code Project phase Code Project phase
00 No phase 1B Phase 1B
01 Phase 1 AA Phase AA
02 Phase 2 AB Phase AB
03 Phase 3 BA Phase BA
04 Phase 4 BB Phase BB
1A Phase 1A
25.3.4 Originator
[Originator] is a three-character alphabetic code that represents the company responsible for that
aspect of the work. The codes represent the company name of the file owner and not the
discipline. Table 31 lists example ORIGINATOR codes that relate to the companies working on a
project; refer to Masdar for a complete list.
Version 2.0.3 111 of 224

MASDAR
Table 31 Originator code examples
Code Originator Code Originator
2GT United Tech. Serv., LLC/2getthere BV AMO Al Masood Oil Industries
A01 Originator A01 AMW Amana Walbridge
A02 Originator A02 AOL Allen & Overy LLP

A03 Originator A03 AOR Abu Dhabi Oil Refining Company
A04 Originator A04 APP ALDAR Properties PJSC
A05 Originator A05 ARC Al Ryum Contg. & Gen Transp

A06 Originator A06 ARP Ove Arup & Partners, Ltd.
A07 Originator A07 ASC Abu Dhabi Sewage Services Company
A08 Originator A08 ASG Adrian Smith + Gordon Gill Architect
A09 Originator A09 ATD Abu Dhabi Transmission & Dispatch Co
A10 Originator A10 ATH Acentech
A11 Originator A11 ATK A.T.Kearney Ltd
A12 Originator A12 AWA Abu Dhabi Water & Elect. Authority
A13 Originator A13 AWE Abu Dhabi Water & Electricity Co.
A14 Originator A14 B&C Booz & Company

A15 Originator A15 BEC Barracuda Electro Mechanical Contracting
A16 Originator A16 BMT BMT Fluid Mechanics, Ltd.
A17 Originator A17 BNP BNP Paribas

A18 Originator A18 BRD Bio Regional Development Group
A19 Originator A19 BTL Bodycote Testing, Ltd.
A20 Originator A20 CAC Canar

ACD Abu Dhabi Civil Defence CBM CICON Building Materials
ACH Al Ahmadiah Contracting and Trading and Hip Hing CCG Connaught Compliance Gulf Services
ACO Abu Dhabi Co. for Onshore Oil Op. CH2 CH2M HILL
ADC Abu Dhabi Distribution Company CLI Cini Little International
ADI Al Dhafara Insurance CMC Collaboration, Management & Control
ADM Abu Dhabi Municipality CML Cansult Maunsell Limited

ADT Abu Dhabi Department of Transport CRE Claude R. Engle
AED AEDAS DC8 dCarbon 8, Ltd.
AFE Arabian Foundation Engineers DCS DCS Group, LLC

AFR Al Falah Ready Mix LLC DES DHL Exel Supply Chain
AGI Abu Dhabi Gas Industries Ltd. DGC Derby General Contractors, LLC
AGY Agility DOR Dornier Consulting GmbH
AHC Al Husam General Contracting LLC DPC Dubai Precast
AJE Al Jaber Energy Services, LLC DPE DC PRO Engineering
AKT Adams Kara Taylor (AKT) DPG Department of General Public Gardens
ALB Al Bayda Pre-Fabricated Houses, LLC EAD Environment Agency Abu Dhabi
ALH Al Hamra Shade Industries ECL Energo Consult L.L.C
ALS Al Sultan Precast Concrete EDA Energydesign Asia

AMC Abu Dhabi Maintenance Construction Company EDW EDAW/AECOM
Version 2.0.3 112 of 224

MASDAR
Table 31 (continued) Originator code examples
EEC Eagle Electromechanical Co., LLC LSV Lancsville Consultant
EMS PA-EMS Limited MAX Maxmakers, Ltd.
ENV Enviromena Power Systems, LLC MCM Multiplex Constructions M.E.

ERN Ernst & Young, Abu Dhabi MDC Mubadala Development Company
ESD Environmental Systems Design MMD Mott MacDonald
ETA Emitrates Trading Agency LLC MME Mero Middle East LLC
ETC Emirates Telecommunications Corp. MWH MWH UK Limited
ETE EnerTech Environmental, Inc. NCC National Central Cooling Co-Tabreed
EYS Energy Management Services NIA National Inspection and Tech Testing
FAS FAHSS OCI Oman Cables Industry
FGL Faithful + Gould, Ltd. OGC Orbit Geological consultancy
FHG Fraunhofer Gesellschaft P6 Plans – Third Floor Level
FMA Fugro MAPS Aerial Survey Consultants PBI Parsons Brinckerhoff International, Inc.
FME Fugro Middle East PBU Parsons Brinckerhoff, UK
FPL Foster + Partners, Ltd. PDG Department of General Public Gardens

GCN Geothermal Consultants New Zealand PFE PF Emirates
GEO Geoconsult PHA PHA Consult
GEY Green Energy PIL Parsons International Limited

GFS Golden Falcon Pertroleum Services PLD Pivotal Lighting Design
GFT Golden Foundation Technology LLC PNG PLANAR Group
GIL Gillespies, LLP POS Positive Advertising

GLL Global Laboratory PRO ProLogis
GSI Genesis Integration PRP PRP Architects Limited
GTC Gistec PRT PRT Consulting
GWP GE Water & Process Technologies PSI Primavera Systems Inc
HAL Halcrow International Partnership REA Reem Emirates Aluminium
HDI Hamilton Design International RFD Research Facilities Design

HEG Halladay Education Group Inc RJA Rolf Jensen & Associates, Inc.
HPE High Performance Energy Systems ROY Royal Voltage Electro Mech Work
HYD Hyder Consulting Middle East Ltd. RSB Regulation and Supervision Bureau
IET International for Energy Technology RTI RTI International
JBI John Buck International RWA RW Armstrong & Associates
JIH Jacobs International Holding Inc RWD Rowan Williams Davies & Irwin, Inc. (RWDI)
KAI Kalin Associates, Inc. SAI SAKO & Associates, Inc.
KEY Key Facilities Management Consultant SBA Sandy Brown Associates, LLP
KLL Karin L. Larsen SBF S&B Fencing Fixing, LLC
LBB Lerch Bates SBH Saif Bin Hermal Drilling Est.
LBG The Louis Berger Group, Inc. SCI Stanley Consultants Inc
LBS The Louis Berger SAS SEF Schneider Electric FZE

LEO Leon Glicksman SFZ Stream FZE
LES Leslie K. Norford SGA Adrian Smith + Gordon Gill Architecture LLP
Version 2.0.3 113 of 224

MASDAR
Table 31 (continued) Originator code examples
SHI M/s. Sultan Hareb International TPD Traffic and Patrol Department
SIS Safeer integrated systems Co LLC TSM Thiess Services Middle East LLC
SJG Spektra Jeotek Geotechnical Engineer TTI Tetra Tech International Consentini Associates
SMA SMA Solar Technology AG TTT Thorton Tomasetti
SOL Soletanche-Bachy TUN TUV-NORD
SPG Sopogy TUR TUV Rheinland Group

SPS Sunpower System SA UPC Abu Dhabi Urban Planning Council
SSS Spark Security Services USG United Security Group
STS S.T.S. Abu Dhabi Electromechanical Co., LLC VES Veolia Environmental Services Emirate
SUN SunTechnics GmbH WSA WS Atkins & Partners Overseas
SYS Systematica S.p.A. WSP WSP Middle East
TCL Tower Cranes Consultants Limited XTD Xanzhou iisaw Technology development
TDM Tebodin MiddleEast LLC YAM Yamasaki International, Inc.
TEG Transsolar Energietechnik GmbH YAS YAS Contracting
TEM Toledo Elect and Mech Establishment YIA Yuanda International Aluminium Group
TKG The Kanoo Group ZBL ED Zublin AG
Version 2.0.3 114 of 224

MASDAR
25.3.5 Discipline
[Discipline] identifies the content by discipline using a two-character alphabetic code as shown in
table 32. Refer to Masdar for the latest complete list.
Table 32 Discipline codes
Code Discipline Code Discipline
AX Architectural MX Mechanical
AB Architectural laboratories MH Mechanical HVAC
AC Architectural acoustics MP Mechanical piping
AF Architectural facade NX Instrumentation and controls
AL Architectural logistics PX Plumbing
BX Geotechnical QX Equipment
CX Civil QA Equipment, athletic
CS Civil site QH Equipment, hospital
CG Civil grading QL Equipment, laboratory

CU Civil utilities RX Water
DX District cooling SX Structural
EX Electrical SP Structural piles
EP Electrical power SF Structural framing
EL Electrical lighting SS Structural substructure
FX Fire protection TX Telecommunications
FA Fire protection detection and alarm TA Telecommunications audio visual
GX GIS TY Telecommunications security
GR GIS roads UX MV distribution
HX Public health VX Survey-Mapping
IX Interiors VA Survey-mapping aerial
IF Interiors furnishings VF Survey-mapping field

JX Sustainability WX Solid waste
KX ICT YX Transportation
LX Landscape YV Transportation vertical

LH Landscape hard
Version 2.0.3 115 of 224

MASDAR
25.3.6 File type and level
[File type and level] is a two-character alphanumeric code that represents the file type and level.
Examples are listed in tables 33. Refer to Masdar for the latest complete list.
Table 33 File type and level code examples for CAD files
Code File type and level Code File type and level
3D Isometric/3D P3 Plan - podium level
AB As built P4 Plan - first floor level
CH Chart PH Photo
DR Drawing register PL Plan
DT Detail RP Report
EL Elevation SC Schematic
GE General SD Shop drawing
MD Model SE Section
P1 Plan - utility trench level SH Schedule
P2 Plan - PRT level SP Specification
25.3.7 Number
[Number] is a four-digit code. For building design each discipline starts at 0001 and allocates
numbers to suit their own needs. All file identifiers must be unique when the DISCIPLINE,
ORIGINATOR, FILE TYPE and NUMBER codes are considered. Table 34 shows examples of
how this is achieved.
Table 34 Examples of unique numbering for building projects
The NUMBER is unique when . . .
Joined with the FILE TYPE MST-1B-FPL-A-P1-0140 Enables one ORIGINATOR to have model
and and drawing files with the same NUMBER
MST-1B-FPL-A-MD-0140
Concatenated with the FILE TYPE MST-1B-FPL-A-P1-0140 Enables different ORIGINATORS to use the
and ORIGINATOR. and same FILE TYPE and NUMBER
MST-1B-HAL-A-P1-0140
Concatenated with the FILE TYPE, MST-1B-HAL-E-P1-0140 Enables different DISCIPLINES to use the
ORIGINATOR and DISCIPLINE and same FILE TYPE and NUMBER
MST-1B-HAL-M-P1-0140
Version 2.0.3 116 of 224

MASDAR
For infrastructure design [Number] refers to the site-wide grid system shown in figure 18. All CAD
sheet files related to site-wide design should correspond to the grid system and must be named
according to the grid in which they fall.
The site-wide grid begins it‘s numbering in the upper left corner with 1100 and continues to the
lower right corner with 8700. The largest grids correspond to a scale of 1:1000 and they are each
divided into four smaller grids corresponding to 1:500, which in turn are divided into four further
grids corresponding to a scale of 1:250. For example, the CAD sheet file name for the 1:1000
square highlighted in figure 43 would be:
[Project] - [Phase] - [Originator] - [Discipline] - [File type and level]-1700
1100 1200 1300 1400 1500 1600 1700

1100
2100
3100
4100
5100
6100
7100
8100
Figure 43 Site-wide grid system (with 1:1000 grid square 1700 highlighted)
Version 2.0.3 117 of 224

MASDAR
Figure 44 shows grid 1700 (scale 1:1000) sub-divided into four 1:500 grid squares numbered
1710, 1720, 1730 and 1740. For example, the CAD sheet file name for the grid square
highlighted in figure 19 would be:
[Project]-[Phase]-[Originator]-[Discipline]-[File type and level]-1740
1700
10 20
30 40
Figure 44 1:1000 grid (number 1700) divided into four 1:500 grids
Figure 45 shows each 1:500 grid further sub-divided into four 1:250 grid squares. For example,
the CAD sheet file name for the grid square highlighted in figure 45 would be:
[Project] - [Phase] - [Originator] - [Discipline] - [File type and level]-1714
1700 1700
10 20 10 20
1 2 1 2 1711 1712 1721 1722
3 4 3 4 1713 1714 1723 1724
30 40 30 40
1 2 1 2 1731 1732 1741 1742
3 4 3 4 1733 1734 1743 1744
Figure 45 1:250 site grid (in larger grid 1700) and corresponding grid numbers
Version 2.0.3 118 of 224

MASDAR
25.3.8 File extension
The file extension indicates the type of file. Examples of file extensions are listed in table 35.
Table 35 Example file extensions
Code File type
DGN Bentley MicroStation-based application (Masdar deliverable format)
DWG Autodesk AutoCAD
RVT Autodesk Revit
KMZ Google Earth
PDF Adobe portable document format
25.3.9 File naming example for a building
An example of a 2D drawing file identifier is : MST-1B-FPL-A-P1-0140.DGN

MST is the project : MIST
1B is the phase : Project phase 1B
FPL is the originator : Foster and Partners
A is the creating discipline : Architectural
P1 is the file type and level : Plan – utility trench level (sheet file)
0140 is the unique file number : 0140
DGN is the file extension : Bentley MicroStation-based file
Version 2.0.3 119 of 224

MASDAR
26 Collaboration roles and responsibilities

26.1 Masdar programme
26.1.1 First line support
First line support will be provided by Masdar‘s IT support team who will record events, such as
requests for connection, and pass on the issue to Masdar‘s Collaboration System Manager.
26.1.2 Masdar Collaboration System Manager
A System Manager will be stationed in the Masdar Programme Office to manage, support and
administer the collaboration system. The System Manager will act as the prime point of contact
for all system support and key functions:
 Liaison with Masdar IT on system issues

 Liaison with partners‘ IT representatives
 Managing the system environment
- adding new projects
- adding new users
- adding new user groups
- adding folders
- maintaining rules in CAD QA
- updating standard content
 Managing rollouts to partners
 Providing access to Bentley technology for partners
 Providing second line support (after initial IT level 1 support)
26.1.3 Lead Digital Design Coordinator (DDC)
A Lead DDC will be stationed in the Masdar programme office to lead the coordination of design
collaboration and standards use, as well as the further development or modification of the
standards and tools. The lead DDC will coordinate and communicate with DDCs from all design
partners. The Lead DDC will act as the prime point of contact for issues related to digital data
including BIM and to Masdar‘s technical design coordination system. Key functions are to:
 coordinate and lead all other DDCs on the project, ensuring that there is a consistent
approach to project modelling and CAD issues and practices across each project.
 coordinate the project requirements for IT solutions
 manage revisions to Masdar‘s CAD & BIM documentation.
 provide education and training
 perform in-house CAD, BIM and collaboration technology briefings
 perform on-boarding briefings
Version 2.0.3 120 of 224

MASDAR
 undertake intelligent audits to identify the specific business benefits of implementing the
system within the organisation, and gap analyses to identify how to transition the business
to where Masdar needs it to be.
 organise in-house training and education sessions for users to advance the effective use of
collaboration
 lead the implementation of integrated collaboration within the programme
 work with discipline leads to promote and advance collaboration to facilitate interoperability
between technologies.
26.2 Project Management Contractors (PMC)

26.2.1 PMC Responsibilities
Typical roles and responsibilities generally include but are not limited to:
 Communicate all production deadlines to technicians throughout duration of project

 PMC Document Controllers are responsible for the checking submission of files to the
collaboration systems and controlling the review processes
 They distribute submissions for review and coordinate the outputs from the review process
 Track the review process and ensure timely delivery
 Collate review comments
 Consolidate review comments
 Return consolidated comments to Design Partner
 Resolve comments, reject or approve for SHARE or ISSUE
 Ensure the collaboration environment is continually updated with current and valid
information
 In coordination with the Design Partners and Contractors, ensure completeness for intended
purpose and reliability of data for all stakeholders throughout the project life cycle.
 Responsible to transmit deliverable requirements
 They ensure that submissions are delivered in accordance with the contract milestones and
track review cycles liaising with their team.
26.3 Design partner and contractor

26.3.1 Digital Design Coordinator (DDC)
The DDC is a recommended role to be filled unique for all design partners. They will monitor the
development of design deliverables from start to finish. The focus is to check for consistency
across the design team and ensure the validity of data placed into the model and extracted to the
deliverables. A continuous quality check will be conducted to ensure data is compatible for use
throughout the life cycle of the project. Any data pushed to the collaboration environment needs
to be checked for validity and correctness; this should be done weekly at a minimum.
Version 2.0.3 121 of 224

MASDAR
On commencement of a project it is recommended that the design partner should appoint a local
DDC who will act as the point of contact with Masdar‘s DDC. Any clarifications or proposed
modifications to this document or the accompanying dataset shall be communicated via the
DDCs.
Masdar will have a lead DDC who will coordinate with all designers. The following are some of
the functions which the DDC will need to perform, be familiar with, or contribute to:
 Provide support for automation applications throughout project lifecycle. Examples of

applications include visualisation, model review, project databases, work planning, simulation
and engineering analysis, and interface with cost estimation, project controls and scheduling.
 Work with lead engineers to promote and advance automation on projects and facilitate
interoperability between technologies
 Collaborate with each project discipline to insure that technology is maintained and advanced
and customised only to the extent required to meet the project objectives
 Provide on-going informational and educational sessions for users to advance effective use
of technology
 Lead implementation of integrated automation technologies
 Apply standards as defined within this document
 Provides project model management and coordinates production of defined deliverables
 Utilises and maintains project document management system in accordance with project
requirements
 Perform project setup in alignment with the project requirements.
 Manage change requests with respect to standards and approaches, ensuring that the
project as a whole maintains a common working environment
 Perform quality checks on the models prior to uploading to the collaboration environment
 Coordinate with the Lead DDC to establish and distribute additional CAD levels.
 Coordinate with the Site Control and GIS Manager to ensure the correct coordinate system is
used throughout the project and to coordinate and distribute GIS and survey data as
specifically requested.
26.3.2 Document Controllers (DC)
Document Controllers (or other assigned persons) are responsible for checking the submission of
files to the collaboration systems and controlling the outputs of the review cycles. They ensure
that submissions are delivered in accordance with the contract milestones and track review cycles
liaising with their team. The DC will ensure that all data entered into the collaboration
environment is valid and correct; data not adhering to the standards defined within this document
will be rejected.
On commencement of a project, the design partner shall name their local Document Controller/s.
This individual shall fulfil the functions of this role as outlined within the role description and act as
the Masdar DDC‘s point of contact for the duration of the project. Specific tasks include the
following.
 Communicate all production deadlines to technicians throughout duration of project

 Provide continuous drawing production coordination and resolve any related conflicts
Version 2.0.3 122 of 224

MASDAR
 Coordinate plotting, signing and sealing requirements/coordination for intermediate, project

milestone, and submittal deliverables
 Ensure the collaboration environment is continually updated with current and valid
information
 In coordination with other discipline leads, ensures completeness for intended purpose and
reliability of data for all stakeholders throughout the project life cycle.
 Responsible to transmit deliverable requirements and ensure proper archiving of the
deliverable requirements within the collaboration system
Version 2.0.3 123 of 224

MASDAR
27 Delivery requirements
27.1 General requirements
The deliverables required for this programme support the model-centric approach and lifecycle
data described in chapters 3 and 7, and the policies of the common data environment.
Design teams shall provide spatially correct models in the coordinate system and datum used
throughout the project.
Each formal submittal shall include the native CAD files/models and corresponding drawings
delivered in PDF format and uploaded into the ProjectWise WIP area.
Design teams shall update work in progress BIM models and related meta-data within
ProjectWise and submit these for project sharing on agreed milestone dates.
Masdar‘s preferred model delivery uses Bentley tools and formats, which will provide a common
format for federation and collaboration. Other delivery formats, if chosen, must demonstrate
adherence to the required federated model standards laid out in these documents. ProjectWise
supports both Bentley DGN files and AutoCAD DWG files.
To fulfil these delivery requirements:
 All CAD files shall be delivered in Bentley MicroStation format in the current MicroStation
version utilised by the programme (see section 4).
 All BIM models along with related meta-data shall be delivered in Bentley MicroStation BIM
format in the current MicroStation version utilised by the programme (see section 4).
 Bentley software tools are available for use on the programme and can be obtained from
Masdar‘s Collaboration System Manager.
 Configuration and seed files for Bentley software that meet the Masdar standards for
modelling are available to project teams and held in ProjectWise.
The collaboration system does not directly support the BIM format data of Autodesk Revit,
Graphisoft and Tekla because these reside in unique databases that do not support the federated
model approach. However, data from these formats can be provided to Masdar by a combination
of plug-ins, IFCs of Excel spreadsheets.
27.2 Buildings
Building information models will include all necessary disciplines including architecture, structural
engineering, and mechanical and electrical systems.
27.3 Site infrastructure

Site infrastructure data should be populated within ProjectWise. Existing GIS data is collected
and applied as required to create a basis for design of the site infrastructure. When Masdar GIS
is fully operational then Bentley‘s ProjectWise GIS database connector will be implemented to
provide access to CAD-referenced GIS data that can be used for collaboration. New geospatial
Version 2.0.3 124 of 224

MASDAR
data, along with a physical three-dimensional model of the built form, are included within the
collaboration environment.
27.4 Ground surface

The ground surface model is to be created and managed throughout the design phase and
beyond. The data acquired from existing sources forms the bases for an existing physical terrain
model. Along with the terrain model, a model of the fixed and non-fixed site equipment is
developed to represent any and all items which will take up physical space onsite. These would
include items such as landscape furnishings (benches, fountains, etc.) and landscape
architectural treatments.
27.5 Below-ground utilities

All underground data pertaining to utilities will be housed in their own separate model (or series of
models). The integrity of this data is critical to ensure no interferences occur during the phased
construction of the programme.
Version 2.0.3 125 of 224

MASDAR
28 Sign-off and approval processes

28.1 General requirements
An approvals process has been established by Masdar to ensure that model and drawing files are
adequately checked, and to enable the design teams, Masdar and the contractor to approve and
sign-off the development of the design information at appropriate points. This follows and
supports the Masdar ‗Design Management Procedure Reference BP-PDU-DM-01.‘
The process includes a full check of the data coordination and registration across the whole data
set before the design check proceeds. It should also include an assurance that the data to be
approved has been checked for compliance to Masdar‘s CAD standard (chapter 5) and project
data standards (chapter 7). Masdar will use QA software to automatically check, amongst other
things, the following items. A copy of the QA software is made available to partners to enable
them to check data before submission.
- All file names match the project standard

- Mandatory meta-data is complete
- Layer names comply with project standards
- Model files are drawn or referenced to the project‘s origin and using the project spatial
projection.
- Dimension text has not been overwritten or disassociated (because this could cause errors
in quantification).
- Title sheet attribute information is complete and compliant.
- All objects in the design model have a part assignment.
- All objects are assigned to their proper level based on part definition
- All objects requiring identification contain a unique identifier.
Any files which fail to comply will be quarantined with a report outlining the non-compliance sent
to the originator.
28.2 Working with Primavera Contract Manger (PCM)

To be completed.
28.3 Sign-off phases

The principal sign-off phases for Masdar projects are listed in section 9. These procurement
phases are ‗gates‘ through which the documents, drawings and data must pass to ensure that
they are used for the specified purposes and are governed by the appropriate ‗status‘.
ProjectWise provides tools for this sign-off process, including approval procedures when the lead
designer signs off information as fit for specific design development usages (such as ‗fit for
coordination‘ or ‗fit for information‘); these have an ‗S‘ status applied to them.
Version 2.0.3 126 of 224

MASDAR
29 Using the collaboration system

29.1 Creating and editing work in progress
29.1.1 Designers and contractors working inside the system
29.1.1.1 Creating a model
Model creation can be made inside ProjectWise using the designers‘ and contractors‘ own private
WIP area. The visibility of these WIP areas can be controlled by the Masdar System Manager.
Master library and seed files are available for each major Bentley application, held in the
Common section of the ‗ISSUED‘ area. This Master library will kept current by Masdar‘s Digital
Design Coordinator (DDC).
Within the private WIP area the designer/contractor may use its own processes and data
structure. However, at the point of submission for Review, SHARING and ISSUE the Masdar
data structure rules must be followed.
29.1.1.2 CAD QA
Designers/contractors will be provided, on request, with a copy of the CAD QA application to

enable them to check files prior to submission. CAD QA will be updated by Masdar‘s DDC to
reflect evolving project standards.
29.1.1.3 Creating drawings
The creation of drawings is described in chapter 5, including methods of extracting drawings from
models. Configuration files for standard borders and title blocks are held in the Common section
of the ISSUED area of the system.
29.1.1.4 Plot to PDF
In order to ensure consistency of deliveries, standard plot drivers are held in the Common folders.
Details of these are given in chapter 5 (section 20) and appendix 7.
29.1.1.5 Design compare
For those using Bentley applications a facility is provided to compare two drawing outputs and
show the changes between different versions.
29.1.1.6 Referencing files from SHARE and ISSUE
A key feature of ProjectWise is the use of secure, reviewed data, with a known provenance, for
each project member. All data in SHARE or ISSUE is read-only with a known status and
suitability, allowing data to be safely referenced from these areas. For example, a background
map that has been reviewed and ISSUED can be safely referenced by those creating new
content.
Version 2.0.3 127 of 224

MASDAR
Therefore, a user can use these files as reference material without the ability to edit (which
remains with the file‘s original owner). Referencing is a simple matter of searching and selecting
from the ISSUED or SHARED folder structure and using the file (or files) as reference material.
At the point of submission of new content by the creator only his model files are submitted.
29.1.2 Working outside WIP
29.1.2.1 General
In many cases work will be created outside ProjectWise and submitted for inclusion at milestone
points. The collaboration system is designed to cater for this and provides appropriate tools to do
so. However, when considering model collaboration the system assumes that both the delivery of
data and the data made available to users is in a Bentley format compliant with Masdar
standards.
29.1.2.2 Creating a model
Master library and seed files are available for each major Bentley application, held in the
Common Folder of the ISSUED area of ProjectWise. This library will be kept current by Masdar‘s
DDC. Users should ensure that they have the latest versions of these files available; on
submission of data to ProjectWise it will be assumed that the latest version in use during the
submission period has been applied.
Within their own WIP areas the designers and contractors may use their own processes and data
structure. However, at the point of submission for Review, SHARING and ISSUE the Masdar
data structure rules must be followed.
29.1.2.3 CAD QA
Designers/Contractors will be provided, on request, with a copy of the CAD QA application to

enable them to check files prior to submission. CAD QA will be updated by Masdar‘s DDC to
reflect evolving project standards.
29.1.2.4 Creating drawings
The creation of drawings, including methods of extracting drawings from models, is described in
chapter 5. Sets of standard borders and title blocks are held in the Common section of the
ISSUED area of the system. Designers‘ and contractors‘ DDCs should ensure they have the
latest versions of these files available for their users.
29.1.2.5 Plot to PDF
Standard plot drivers are held in the system‘s Common folders In order to ensure the consistency
of deliveries (see chapter 5 and appendix 7). Designers‘ and contractors‘ DDCs should ensure
they have the latest versions of these files available for their users.
29.1.2.6 Design compare
Design compare Is not available to external WIP users.
Version 2.0.3 128 of 224

MASDAR
29.1.2.7 Referencing files from SHARE and ISSUE
A key feature of ProjectWise is the use of secure, reviewed data, with a known provenance, for
each project member. All data in SHARE or ISSUE is read-only with a known status and
suitability, allowing data to be safely referenced from these areas. For example, a background
map that has been reviewed and ISSUED can be safely referenced by those creating new
content.
To use these files as reference material a user should access ProjectWise and copy files to their
own Work in Progress Area. They SHOULD NOT change file names or data and should treat
these as READ ONLY
When Designers and Contractors Submit models to the system these references will be stripped
as they are deemed already available in the system
Version 2.0.3 129 of 224

Data management standard
MASDAR
Chapter 7
Data management standard
This chapter defines the criteria to be adopted for the submission of drawing-related data to
ProjectWise. It only relates to data that is finalised by the consultant, ready for contractual
delivery. Its purpose is to ensure all drawings and CAD files are correctly numbered and all
associated criteria (meta-data) relating to each CAD file is defined. This will allow the files to be
uploaded to ProjectWise, which will be the central controlled repository for all approved drawing
data. Approved drawing data can then be retrieved and issued by Masdar as required.
This standard is intended to define the requirements at the point of delivery to the project only.
For guidance on control of data prior to issue refer to chapter 6.
Version 2.0.3 131 of 224

MASDAR
30 Revision status
30.1 Introduction
The ‗revision‘ is an attribute defined in the title block of a model or drawing sheet template and
will also be defined in the coordination system (ProjectWise) when the file is uploaded. Revision
numbers are allocated by the originators and presented as meta-data when submitting to Masdar
for review, comment and approval.
When files are submitted their revision code will be checked and ProjectWise will not permit
presentation of a repeat revision code. All revisions of a file will be unique in the Shared and
Issued area. In the WIP area design partners and contractors may also find it necessary to
version the data as it is developed and used within their local task teams, before being ‗shared‘ or
‗issued‘. The revision should be indicated within the file itself as well as on the indexed database
meta-data (see section 4). This provides some security if data is inadvertently or inappropriately
shared without passing through an approval process.
The format of the revision code (detailed below) is dependent on both the type of data to be
issued and the reason for issue. Therefore, the revision code can indicate the type and the status
of the data being submitted.
The combination of revision code and drawing number uniquely identify a drawing. Therefore,
the revision code used for a PDF drawing is always the same as for the associated drawing file.
For this reason the sections below describe the revision code to be used for PDF drawings and
drawing files separately from that of model files (DGN deliverables).
On every issue to Masdar the submitted data should be archived by the consultant for future
reference.
30.2 Format for drawings

When issued for acceptance the revision code to be used on all PDF drawings and drawing files
shall consist of a letter (single or double uppercase character) followed by a double-digit number.
When issued as accepted, the revision code shall be in the simplified alphabetical form, such as
‗A‘. The revision letters ‘I‘, ‘O‘, and ‘P‘ shall not be used.
30.3 Revisioning sequence for drawings

The first issue of a PDF drawing or drawing file to Masdar shall be in revision series A followed by
a revision number, such as A01. It shall be issued to Masdar for acceptance.
For drawing changes made due to non-acceptance or comments by Masdar the alphabetical part
of the revision code shall remain the same and the numerical part shall be increased (for example
A02, A03, etc). It shall be reissued to Masdar for acceptance.
When a ‗no objection‘ notice (or equivalent) is received, the PDF drawings and drawing files shall
be reissued as ‗accepted‘ with the numerical part of the revision code removed (for example ―A‖).
When data is reissued as ‗accepted‘ it shall be an identical copy of the data that received a ‗no
objection‘ notice, except for the described change in revision code.
Following an ‗accepted‘ issue the revision letter of the PDF drawings and drawing files shall be
incremented alphabetically (for example, to B_ _, C_ _, D_ _, etc). If revision letter Z is reached,
Version 2.0.3 132 of 224

MASDAR
the next revision letter shall be AA, with the second character incrementing alphabetically
throughout the cycle with each new revision, ie AB_ _, AC_ _, AD_ _, etc. On reaching revision
letter AZ the first part shall be incremented and the second part shall cycle through the letters
once again, and so on, ie BA_ _, BB_ _, BC_ _ to BZ_ _, then CA_ _, CB_ _, CC_ _, etc. In all
cases, the letters ‗I‘, ‗O‘, and ‗P‘ shall be skipped.
The revision number shall always return to 01 when the revision letter is incremented and the
numbering shall increase sequentially with each revision, as described above.
A change to the revision number may occur without there being an issue to Masdar.
For guidance on the control of data prior to issue refer to chapter 6.
30.4 Format for model files

When issued ‗for acceptance‘ the revision code shall be in alphanumeric form: the uppercase
character ―P‖ followed by a double-digit number, for example P01.
When issued as ‗accepted‘ the revision code shall once again be in alphanumeric form: the
lowercase character ―f‖ followed by a double-digit number, for example f01.
The process by which the revision code changes over time is described in section 30.5 and
illustrated in figure 46.
30.5 Revisioning sequence for model files

On creation in WIP the first revision of a model file shall be P01.1 and subsequent revisions (in
WIP) shall be numbered P01.1, P01.2, etc. When issued to Masdar the decimal part of the
revision must be removed; for example, P01.3 would be submitted as P01. The first issue to
Masdar shall be ‗for acceptance‘.
For modifications made due to non-acceptance/comments by Masdar the numerical part of the
revision code shall be incremented, for example to P02, P03, etc. It shall be reissued to Masdar
for acceptance.
When a no objection notice (or equivalent) is received, the model file shall be reissued as
accepted, with the revision character ‘f‘ replacing the ‘P‘ and the numerical part remaining
unchanged, for example f03. When data is reissued as accepted it shall be an identical copy of
the data that received a no objection notice, except for the described change in revision code.
Following an accepted issue the revision code for the next issue of a model file shall be a ‘P‘
character followed by the accepted revision number incremented by 1; for example, if the
accepted issue revision code was f03, the next issue will be P04. The revision number shall
always be incremented when the model file is issued following a modification.
A change to the revision number may occur without there being an issue to Masdar.
For guidance on the control of data prior to issue refer to chapter 6.
Version 2.0.3 133 of 224

MASDAR
WORK IN PROGRESS SHARE PUBLISH
Model files Model files Revision A submission

Drawing PDF
Architecture P01.4 P01 file file
DGN PDF Masdar
Model files Model files
A1 A1 review
Structural P04.2 P04

Freeze Pass Fail
M&E P02.4 P02
Model files have

passed internal f01 DGN
check and become A
frozen. Revision Issue to
number becomes f04 Masdar
an integer, ie P01.4 PDF
becomes P01 A
f02
Model files revised Rejection comments added
Model files Model files Drawing PDF

Architecture
P01.4 P01 file file
No change
DGN PDF Masdar
Structural A2 A2 review
No change
P04.2 P04

M&E Freeze Pass Fail
CHANGE P03.1 P03
3D and 2D
extracted f01 DGN
files frozen A
Issue to
f04 Masdar
PDF
f03 A
Rejection comments added
Model files revised as necessary
Revision B submission
Drawing PDF
Architecture P02.1 P02.4 P02 file file
DGN PDF Masdar
Model files
P02.2 P02.3 B1 B1 review
P05

Structural Freeze Pass Fail
P05.1 P05.2 P04
Model files 3D and 2D f02 DGN

M&E P04.1 P04.6 extracted B
files frozen
Issue to
f05 Masdar
P04.2 P04.5 PDF
f04 B
P04.3 P04.4
Rejection comments added
Model files revised as necessary
Figure 46 Diagram illustrating the revisioning process on Masdar projects
Version 2.0.3 134 of 224

MASDAR
30.6 Status
Status defines the ‗fitness‘ of information in a model, drawing or document. The ‗status‘ is an
attribute defined in the meta-data that is associated with the file identifier when the file is
uploaded into ProjectWise. All models, drawings and documents will have status codes defined
as listed in Table 36.
Table 36 Status codes in the common data environment
CDE area Status Description
Work in Progress S0 Initial status (note that the ‗0‘ character is a zero)
Shared S1 Fit for coordination
Information is passed to the ‗share‘ The file is available to be ‗shared‘ and used by other disciplines as a
section once it is released by the background for their information
originator, having been thoroughly S2 Fit for information
reviewed and checked.
Drawings and model files must conform to S3 Fit for internal review and comment
Masdar‘s CAD Standard (chapter 5) S4 Fit for construction approval
S5 Fit for partial approval as noted
ISSUED D1 Fit for costing
This section of the CDE contains D2 Fit for tender
documents which are snapshots of the
‗shared‘ information. D3 Fit for contractor design
Before information in the ‗publish‘ section D4 Fit for manufacture / procurement
of the CDE is made available to the wider
project team, any drawings must be F1 Fit for design development
checked and approved. This applies
equally to subcontractors drawings. A Fit for construction
Statuses A, B and C are sign-off codes B Fit for construction but with comments
used to state the completeness of the Documents are partially signed off, with minor comments from the client.
document for contractual purposes. All minor comments should be indicated by the insertion of a cloud and a
statement of ‗in abeyance‘ until the comment is resolved.
C Comprehensive revisions needed

Archive AB As built
Purpose of status meta-data
The S0-S5 status codes are used when the information is being developed and ‗shared‘ by the
design teams and the specialist subcontractors. The information is approved for a specified use
but is not ‗approved‘ by the client
The D1-D4 status codes are used when information is needed by the contractor or client for a
specified purpose but is not approved by the client as fit for construction. These data and
documents must never be used for construction purposes or to give others an instruction to
construct. D status information can be passed from the WIP area directly to the PUBLISH area.
Version 2.0.3 135 of 224

MASDAR
31 Meta-data
31.1 Introduction
In order for the data to be entered into ProjectWise all drawing-related files delivered to the
project shall be accompanied by the related database-compatible meta-data. This data is
necessary for the project to be able to record and organise all CAD data as well as tracking the
drawing changes in accordance with Masdar procedures.
The data fields for meta-data are defined in Appendix 10.
31.2 Data format

The meta-data shall be delivered either as a comma separated text file (.CSV) or as an
Extensible Markup Language (.XML) file. The file naming convention for the meta-data file will
match that of the consultant‘s document transmittal number but with a ‗.CSV‘ or ‗XML‘ suffix.
All data will be checked for compliance with Masdar standards when it is received and any
transmittal that is deemed to be non-compliant will be returned to the consultant for correction.
31.3 Required fields

Certain fields within the data file shall contain information. These fields are identified in appendix
10 as ‗mandatory‘ and shall be populated in all cases. Other fields are classed as ‗optional‘ and
these shall contain data where appropriate — for example where the drawing has been approved.
31.4 Linked fields

There are some fields in ProjectWise that are linked to the data field values stored in the CAD
drawing title block cell. These fields shall exactly match the related meta-data.
31.5 Dates
All date fields within the meta-data shall be stored in ‗dd/mm/yyyy‘ format.
31.6 CSV format

All meta-data fields within the .CSV format file will be comma delimited and all text data fields will
be enclosed between quotation marks (―‖).
31.7 XML format

An .XML ‗schema‘ file defining all of the required field names, sizes and data types will be
supplied.
Version 2.0.3 136 of 224

MASDAR
32 Transmittal of data
32.1 Electronic media
The media used for the transmittal of files between outside consultants and the Masdar project
team shall be in accordance with the contractual terms.
32.2 Referenced drawings

PDF files of all drawings shall accompany file submissions in accordance with the contractual
terms. These shall be generated using the plot drivers supplied by Masdar.
Every drawing submitted shall be numbered as defined in section 2 and given a revision code as
defined in Section 3.
PDF drawings shall be issued as individual files. The PDF file shall be numbered identically to
the drawing number, plus the ‘.PDF extension.
32.3 CAD files

Every file submitted shall be numbered as defined in section 2 and given a revision code as
defined in Section 3.
All CAD files that comprise a package shall be submitted, including the drawing files, model files,
raster files, 3D models, 3D reference model files and all other associated files — making the
submission a standalone data set. Masdar will only extract revised information and will not
accept revisions to standard borders, mapping, etc.
32.4 Meta-data
All file meta-data shall be submitted as defined in Section 4.
Version 2.0.3 137 of 224

Education, training and support
MASDAR
Chapter 8
Education, training and support
This chapter describes the education, training and support necessary for the successful
implementation of Masdar‘s modelling and collaboration requirements.
Version 2.0.3 139 of 224

MASDAR
33 Masdar’s structured approach

33.1 Introduction to education, training and support
It is recognised that design and construction organisations can be reluctant to adopt a BIM and
collaboration approach without appropriate support. Therefore, Masdar will assist project teams
by providing education, training and support. Experience has shown that this is best done in a
staged manner, as shown in figure 47 and described below.
EDUCATION TRAINING SUPPORT
Technology briefing Project team training Deploy project - BIM Coordinator

specific content meetings
Functional BIM Coordinator

requirements analysis training PROJECT
Project definition and Project configuration Project support Project reviews

implementation plan workshop
Figure 47 Education, training and support for Masdar projects
33.2 Education
33.2.1 Technology briefing
Where parties are unfamiliar with BIM then a technology briefing introduces the concepts and
benefits to the project teams. Levels of expectation will be set; for example, what Masdar expects
and how the teams can expect to benefit from working in this way.
33.2.2 Functional requirements analysis
A functional requirements analysis is an initial overview and analysis of an organisation‘s CAD/3D

processes in order to identify the specific potential benefits of implementing a BIM approach. It
considers what they do now, and the gaps are to get them to where Masdar needs them to be.
33.2.3 Project definition and implementation plan
This is the final component of Masdar‘s BIM education and it reviews project aspects, including:
- scope and type of project (and scope of BIM solutions to be implemented)
- programme and key milestones
- Masdar and supply chain expectations
- format and quality of data sources
- project processes and procedures for BIM and technical coordination
- project deliverables (models, drawings, data, visualisations, etc)
- project team members (skills and experience, roles and training requirements).
Version 2.0.3 140 of 224

MASDAR
33.3 Training
33.3.1 Project configuration workshop
The configuration workshop follows shortly after the project definition and implementation plan,
and involves key project team members (including construction organisations) as appropriate.
The workshop addresses the implementation of Masdar‘s requirements for BIM (such as model
file naming, property data and CAD standards) and technical coordination.
33.3.2 BIM coordinator training
Masdar will identify the BIM coordinator in each organisation who provides support for the BIM
approach at a project and company level. Masdar would work with the suppliers of BIM software
tools to provide advanced training as appropriate to enhance BIM coordinators‘ knowledge prior
to the larger scale project team training (see below).
33.3.3 Project team training
Project team members must be adequately trained on BIM tools and Masdar‘s technical
coordination system (ProjectWise). It is usually most effective to provide workshop training
sessions tailored to the project, rather than sending staff on a standard scheduled course. The
preceding stages would help to formulate the content and style of the workshops for each project
and/or organisation. Training needs will vary according to the skills and experience of each user
and figure 48 shows the typical training requirements for different levels of experience. Ongoing
support would be provided by the appropriate BIM coordinator.
10 days training
Extreme
9 learning curve
5
Moderate Steep learning
4 learning curve curve
3
Minimal Small learning
2 learning curve curve
Constant Constant
No further Regular mentoring,
Occasional guidance and
1 guidance or support and guidance and
Occasional support and occasional
support guidance support
support guidance support
Highly skilled Capable 3D Basic 3D Highly skilled Capable Basic

3D modeller modeller modeller technician technician technician
Figure 48 Typical training requirements for BIM tools (in days)
Version 2.0.3 141 of 224

MASDAR
33.4 Support
33.4.1 Deploy project-specific content
In readiness for the start of a project Masdar will create, distribute and deploy project- and
organisation-specific content (such as seed files and templates). During the project Masdar
would provide additional services to help ensure that the potential benefits are realised, including
project support, project reviews and analysis, and facilitating BIM coordinator meetings.
33.4.2 Project support
To provide support through the delivery process Masdar BIM staff will visit organisations regularly
to help ensure that the technology was being used appropriately and effectively. This aspect
helps to manage the risks (to projects, organisations and individuals) of implementing a BIM
approach and helps to catch problems before they arise.
33.4.3 Project reviews
Masdar perform regular reviews to assess what goes well, and what does not. It is important to
reinforce the benefits of a BIM approach as discussed in the technology briefing and to measure
how the stakeholders‘ expectations are being met. Masdar will help to quantify the business
benefits and share that knowledge with project teams and the wider construction industry.
33.4.4 BIM coordinator meetings
BIM coordinators support project teams on a day-to-day basis, and Masdar supports their regular
meetings across the projects to help them jointly (with BIM software vendors):
- share and resolve technical issues
- review processes and procedures
- evaluate progress against project and organisation targets
- implement best practice and improvements in their respective organisations.
Version 2.0.3 142 of 224

MASDAR
34 Learning paths for technical training

34.1 Introduction to learning paths
Building information modelling (BIM) and collaboration have an important role to play in helping to
deliver Masdar City. BIM requires training, IT system configuration, templates and seed files, and
setting up of appropriate business processes. Masdar will assist its project teams by providing
appropriate education, technical training and support.
Masdar provides hands-on BIM technical training and online seminars from Bentley. Users who
take advantage of these opportunities accrue one Learning Unit for every hour of training
completed; Learning Units are Bentley Institute‘s equivalent to Professional Development Hours
and are added to a personal online transcript that demonstrates professional growth over time.
Masdar will also provide online access to educational and informative seminars about real world
infrastructure projects and the best practices and software products used to design, build, and
operate them.
Training requirements will vary according to the skills and experience of each user, and the role
they perform. This document describes BIM learning paths according to various user groups.
34.2 Training matrix

The training matrix (table 37) shows the recommended learning paths for different types of user.
For example, a Type 1 user would the following courses in the order shown:
Course 1 (4) Bentley ProjectWise Navigator essentials

Course 2 (19) ProjectWise essentials
Course 3 (5) Bentley Building advanced interference manager
Users are encouraged to discuss training requirements with Masdar as early as possible in the
project process so that appropriate training plans can be developed to suit the individual needs.
Full details of courses for technical learning paths can be seen at:
http://www.bentley.com/en-US/Training/Products/Resources/Courses/Find+Courses.htm
Version 2.0.3 143 of 224

MASDAR
Table 37 Sample learning path matrix
User type 1 User type 2 User type 3 User type 4 User type 5 User type 6
Design Planning and General CAD Discipline Content
managers and project and BIM specific BIM managers &
reviewers managers team team (note 1) Power user publishers
1 MicroStation essentials 1 1 1
2 MicroStation basics for

building design
2 2
3 Bentley building suite

Fundamentals
2 3 3
4 Bentley ProjectWise
Navigator essentials
1 1 7 5 4 3
5 Bentley Building advanced

interference manager
3 7 5
6 Bentley Building
fundamentals & architecture
3 6 7
7 Rendering for building

design
7 7 8
8 Bentley Building
fundamentals & mechanical
4 6 9
9 Drawing extraction in Bentley

Building Mechanical Systems
7 6 10
10 Bentley Building Mechanical

System fundamentals
6 11
11 Bentley Building Electrical

Systems fundamentals
6 12
12 Bentley Structural
fundamentals
5 6 13
13 Drawing extraction in Bentley

Structural 7 6 14
14 Bentley Structural - advanced

analytical modelling
7 15
15 Bentley Structural two-way

integration with STAAD.Pro
7 15
16 InRoads fundamentals 6 15
17 Drainage fundamentals using

InRoads
6 15
18 InRoads surface modelling 6 15
19 ProjectWise essentials 2 2 6 4 6 1
20 Administering ProjectWise 2
Note 1: Discipline teams would follow the learning path appropriate to their own discipline
Key Recommended Optional
Version 2.0.3 144 of 224

MASDAR
34.3 Basic courses

34.3.1 MicroStation essentials
Target audience - Drafters

- Designers
Products covered MicroStation
Course type Classroom learning, hands on
Course description This course is designed for the new MicroStation user and builds a solid foundation
in the concepts, tools and features found in the MicroStation drawing environment.
Starting with setting up a drawing and concluding with plotting, students walk
through a typical workflow using the tools and features of the latest version of
MicroStation. Interspersed throughout are real-world design problems solved using
the concepts learned to that point in the course. Various engineering disciplines
are represented in the form of hands-on exercises. This offering is taught using
MicroStation V8 XM Edition
Learning At the end of the course students will be able to:
objectives - create and edit 2D designs using established design standards in a production
environment
- have a solid understanding of MicroStation
Course topics - Course overview
- Welcome to MicroStation
- Working with views
- Drafting with MicroStation
- AccuDraw
- Element creation tools
- Additional element attributes
- The level system
- Working with existing elements
- Modifying existing elements
- Annotating designs
- Organizing design data
- Organizing project data
- Creating printed output
Prerequisites None
Learning units 32 hours
Version 2.0.3 145 of 224

MASDAR
34.3.2 MicroStation basics for building design
Target audience This course is suitable for individuals new to the Bentley design environment.
Course description This course is the starting point for the new designer specializing in architectural
design and teaches the fundamentals of MicroStation, as well as advanced
concepts and tools used everyday in architectural design and drafting.
Learning You will have immediate productivity with MicroStation in the architectural design
objectives practice. You will become familiar with the fundamental behaviour of MicroStation.
This course is recommended as the precursor to the Introduction to 3D Building
Design or 2D Architectural Drafting and Building Information Modelling courses.
Course topics - Introduction to MicroStation
- Drawing with MicroStation
- Viewing designs in MicroStation
- Drawing arcs and circles
- Working with levels
- Manipulating elements
- Modifying elements
- Additional MicroStation drawing tools
- Measuring and dimensions
- Organizing your design file
- Printing
- A design exercise
Prerequisites None
Version 2.0.3 146 of 224

MASDAR
34.3.3 Bentley building suite fundamentals
Target audience Architect; Architectural Designer; Architectural Engineer; Civil Engineer; Civil
Engineering Technician; Designer; Design Engineer; Drafter; Electrical Designer;
Electrical Engineer; Mechanical Engineer; Mechanical Engineering Designer;
Piping Designer; Piping Drafter; Planner; Structural Designer; Structural Engineer;
Structural Engineering Technician
Products covered MicroStation, Bentley Building Extension
Course description This course is intended to provide the necessary skills needed before moving into
the Building products such as Bentley Architecture, Bentley Building Electrical
Systems, Bentley Building Mechanical Systems and Bentley Structural. Topics
covered will allow the user to rotate, manipulate and view models. Review a model
and extract sections plans and elevations
Learning After this course students will be able to:
objectives - view and manipulate a model
- navigate within a 3D model
- create and place three dimensional cells
- understand the concept of building information modelling
- create and edit data in the DataGroup Definitions explorer
- use Drawing composition and drawing extraction
Course topics - Viewing and manipulating a model
- Navigating within a 3D model
- Creating and placing three dimensional cells
- Understanding the concept of building information modelling
- Creating and editing data in the DataGroup Definitions explorer
- Using drawing composition and drawing extraction
Prerequisites - A fundamental knowledge of MicroStation
- Use of AccuDraw and its shortcuts
Version 2.0.3 147 of 224

MASDAR
34.3.4 Bentley ProjectWise Navigator essentials
Engineering Technician; Designer; Design Engineer; Electrical Designer; Electrical
Engineer; Mechanical Engineer; Mechanical Engineering Designer; Naval
Engineer; Piping Designer; Piping Drafter; Plant Engineer; Product Designer;
Structural Designer; Structural Engineer; Structural Engineering Technician
Products covered - Interference Manager
- Construction Simulation
Course description Students will learn about ProjectWise Navigator V8 XM Edition which is a tool for
real-time, interactive, intelligent 3D model review, animation and simulation. It has
features for visualizing and querying both graphical and non-graphical information.
This course focuses on the basic features of ProjectWise Navigator V8 XM Edition
and its ability to navigate models from many formats, review components, visualize
with renderings and animations, as well as review interferences.
Learning After this course advanced users will be able to:
objectives - Use ProjectWise Navigator examples and a dataset to assemble a 3D model
from many sources
- Review the aspects of design, aesthetics, real- time conditions, and
environments using ProjectWise Navigator examples and a dataset
- Enrich a 3D model with redline information, rendering data, and hyperlinks to
specifications and documents using ProjectWise Navigator examples and a
dataset
- Analyse and detect 3D interferences and clashes using ProjectWise Navigator
examples and a dataset
- Analyse simulation of construction scheduling and lighting conditions using
ProjectWise Navigator examples and a dataset
- Produce output in the form of contract packages, archives, plots, PDF files,
photorealistic images, animations, web publishing and Google Earth
Course topics - Course overview
- Welcome to ProjectWise Navigator
- Reviewing designs in a single environment
- Assembling data from different sources
- Enriching design data
- Rendering and composing animations
- Detecting and reviewing interferences
- Publishing data
Prerequisites Attendees should be current users of CAD
Version 2.0.3 148 of 224

MASDAR
34.3.5 Bentley building advanced Interference Manager
Engineering Technician; Designer; Design Engineer; Electrical Designer; Electrical
Engineer; Mechanical Engineer; Mechanical Engineering Designer; Naval
Engineer; Piping Designer; Piping Drafter; Plant Engineer; Product Designer;
Structural Designer; Structural Engineer; Structural Engineering Technician
Products covered Interference Manager
Course description This half-day course will show advanced users how the Interference Manager
provides advanced methods for detecting, reviewing, and managing interferences
in 3D CAD models. Through this course users learn some of the more complex
routines that can be implemented with this solution.
Learning After this course advanced users will be able to:
objectives - understand how the interference engine calculates clashes
- create and modify an interference set file
- detect interference via the Interference Manager
- review , display and modify the interference detection settings
- mark interference as checked
- formulate a report definition to print a clash reports
Course topics - Understanding how the interference engine calculates clashes
- Creating and modifying an interference set file
- Detecting interference via the Interference Manager
- Reviewing , displaying and modifying the interference detection settings
- Marking interference as checked
- Formulating a report definition to print a clash reports
Prerequisites - Attendees must be current users of Interference Manager
- CAD experience is an advantage
Version 2.0.3 149 of 224

MASDAR
34.4 Architectural modelling

34.4.1 Bentley building fundamentals and Architecture
Target audience - Architect

- Architectural designer
- Architectural engineer
Products covered MicroStation and Bentley Architecture
Course description This two-day course will lead you through the basics of 3D modelling and then
move into the use of Bentley Architecture and the creation of detailed building
models
Learning After this course you will be able to:
objectives - understand the fundamentals of 3D modelling
- manipulate and control view display
- create simple solid models
- create detailed models and extract plans, sections and elevations
- extract reports and schedules
- review the model in it's environment and create camera views
Course topics - Understand the fundamentals of 3D modelling
- Manipulate and control view display
- Create simple solid models
- Create detailed models and extract plans, sections and elevations
- Extract reports and schedules
- Review the model in it's environment and create camera views
Prerequisites - A fundamental understanding of MicroStation
- An understanding of building design is an advantage
Version 2.0.3 150 of 224

MASDAR
34.4.2 Rendering for building design
Target audience - Architect

- Architectural designer
- Architectural engineer
- Designer
Course description This course will show you how to manipulate camera views and capture images. It
will review and demonstrate the various settings offered that can greatly affect the
model and its finishes. Techniques will be demonstrated to show how different
lighting effects and time settings can create atmospheric effects such as evening,
twilight and sunrise.
Learning After this course users will be able to:
objectives - review the rendering settings and apply to models
- create new materials and understand how they are applied to different elements
- use elevation drape to create landscape
- set-up camera views and perspective
- render the model at different times of the day
- place and manipulate lighting
Course topics - Reviewing the rendering settings and applying to models
- Creating new materials and understanding how they are applied to different
elements
- Using elevation drape to create landscape
- Setting-up camera views and perspectives
- Rendering the model at different times of the day
- Placing and manipulating lighting
Prerequisites A fundamental understanding of MicroStation model creation would be an
advantage
Version 2.0.3 151 of 224

MASDAR
34.5 Mechanical systems modelling

34.5.1 Bentley building fundamentals and Mechanical
Target audience - Mechanical engineer

- Mechanical engineering designer
Products covered MicroStation and Bentley Building Mechanical Systems (BBMS)
Course description This two day course will lead you through the basics of 3D view manipulation and
move on to creating a model to detail the mechanical route within a structure.
Plans and elevations will be extracted and new parts created.
objectives - understand the basic principles of 3D view manipulation and AccuDraw
- create a model detailing the flow and return ducting
- link ductwork to diffusers
- extract plans and sections
- extract schedules and bills of quantities
- create new parts within the BBMS to your company standards
Course topics - Understand the basic principles of 3D view manipulation and AccuDraw
- Create a model detailing the flow and return ducting
- Link ductwork to diffusers
- Extract plans and sections
- Extract schedules and bills of quantities
- Create new parts within the BBMS to your company standards
- Experience in mechanical design
Version 2.0.3 152 of 224

MASDAR
34.5.2 Drawing extraction in Bentley Building Mechanical Systems
Target audience - Mechanical engineer

Products covered Bentley Building Mechanical Systems (BBMS)
Course description Bentley Building Mechanical Systems will let you produce a variety of construction
drawings enabling you to reproduce the same drawing repeatedly without having
to redefine all the criteria and settings. When Bentley Building Mechanical Systems
processes your drawing definition, you can either create individual models that
compose a drawing or have all your drawing information in a single model.
Learning After completing this course you will be able to:
objectives - create mechanical drawing definitions
- extract different types of drawings including plans and sections
- create mechanical systems drawing re-symbolisation rules
Course topics - create mechanical drawing definitions
- extract different types of drawings including plans and sections
- create mechanical systems drawing re-symbolisation rules
Prerequisites - An understanding in how to manipulate a three dimensional model
- A fundamental knowledge of MicroStation and drawing composition
- The use of AccuDraw and its keyboard shortcuts
Version 2.0.3 153 of 224

MASDAR
34.5.3 Bentley Building Mechanical System manage (fundamentals)
Target audience - Design engineer

- Mechanical engineer
Products covered Bentley Building Mechanical Systems (BBMS)
Course description In this one-day course students will learn that Bentley Building Mechanical
Systems allows users and system administrators to customize the delivered data in
BBMS, so that it can be applied to their company standards, project standards or a
combination of both. This course is not designed to show users how to create a
network solution of BBMS.
Learning After this one-day course students will be able to :
objectives - create new parts and components for their company standards and projects
standards and projects
- analyze system connectivity
- create additional Drawing Extraction re-symbolisation rules
- schedule components from BBMS data
Course topics - Creating new parts and components for your company standards and projects
- Analysing system connectivity
- Creating additional drawing extraction re-symbolisation rules
- Scheduling components from BBMS data
Prerequisites Knowledge of: MicroStation mechanical design
Version 2.0.3 154 of 224

MASDAR
34.6 Electrical systems modelling

34.6.1 Bentley Building Electrical Systems fundamentals
Target audience - Electrical engineers

- Electrical modellers
Products covered Bentley Building Electrical Systems
Course description Students will learn to design and edit different electrical properties, connect
elements in circuits using cable manager and generate different reports and
schedules from the model. Emphasis will be on modelling electrical subsystems
including lighting and power analysis interfaces
objectives - set-up project design files, define building structure and room spaces
- create best-practice examples for lighting using different symbol placement
- create lighting design using Relux interface
- set-up user-defined properties for lighting fixtures and panels
- connect lighting and power devices into circuits
- design simple raceway layout
Course topics - Design file set-up
- Symbol placement and 3D properties
- Click and learn technology
- Lighting design using Relux application
- Circuit and cable management
- Raceway design
Prerequisites - Working knowledge of basic electrical design concepts and practices
- Attendance or review of the 2D to 3D MicroStation course
Version 2.0.3 155 of 224

MASDAR
34.7 Structural modelling

34.7.1 Bentley Structural fundamentals
Target audience - Design engineer

- Structural engineer
- Structural engineering designer
- Structural engineering technician
Products covered Bentley Structural
Course description Using Bentley Structural and its example files throughout the course, students will
be able to make a real-time, intelligent 3D model creation, review and edit the
model, annotate, extract drawings, reports and schedules from the model
objectives - create a structural model using Bentley Structural
- extract plans, sections and elevations using drawing extraction manager
- produce bills of quantities, cost reports and specifications
- export the data to other packages for analysis such as MIDAS, RAM and
STAAD
Course topics - create a structural model using Bentley Structural
- extract plans, sections and elevations using drawing extraction manager
- produce bills of quantities, cost reports and specifications
- export the data to other packages for analysis such as MIDAS, RAM and
STAAD
Prerequisites A working knowledge of 3D in MicroStation AccuDraw and its shortcuts
Version 2.0.3 156 of 224

MASDAR
34.7.2 Drawing extraction in Bentley Structural
Target audience - Structural designer

Products covered Bentley Structural
Course description Bentley Structural lets you produce a variety of structural construction drawings.
You can create foundation plans, framing plans, elevations, sections, or details.
When a drawing definition is processed, it attaches 2D drawing references to a 3D
model. Then when you make changes to the model, those changes will
automatically be reflected when you reproduce the drawing
Learning After completion of this module, you will be able to:
objectives - open and edit drawing extraction manager
- create structural re-symbolisation rules
- use drawing definition templates to define cutting planes
- define persistent text labels in the extracted drawing
- exchange forms within an extracted drawing
Course topics - Open and edit drawing extraction manager
- Create structural re-symbolisation rules
- Use Drawing definition templates to define cutting planes
- Define persistent text labels in the extracted drawing
- Exchanging forms
- An understanding of fabrication requirements and drawing production
- Knowledge of AccuDraw and its keyboard shortcuts
Version 2.0.3 157 of 224

MASDAR
34.7.3 Bentley Structural - advanced analytical modelling
Target audience Engineers and others with two years of experience of using Bentley Structural
Products covered - Bentley Structural
- STAAD.Pro
- RAM structural systems
Course description Advanced analytical modelling is positioned for long time users of Bentley
Structural who require superior knowledge and also the ability to set up Bentley
Structural for analytical analysis with STAAD, RAM structural systems, GTStrudl
and SFrame packages.
Learning At the conclusion of this two day session, students will have learnt how to use
objectives higher functionality in Bentley Structural as well as setting up case loads and styles
for analysis in four major analysis packages, and export and import the data.
Course topics - Structural AccuSnap
- Placement points
- AccuSnap hints
- User preferences
- Analytical modelling
- Analytical concepts
- Setup and preferences
- Part definitions
- Preferences
- Creating the analytical model
- Finite elements
- Member releases
- Nodes
- Manipulating and modifying the analytical model
- Moving nodes
- Boundary conditions
- Deleting or recreating
- Analytical data
- Delete analytical data
- Recreate analytical data
- Analytic modelling
- Creating load cases and applying loads
- Load cases
- Load styles
- Loads
- Connecting to analysis applications
- Exporting the analytical model
- STAAD.Pro, ram structural system GTStrudl, and SFrame
- Importing and updating data
- Connecting to analysis
- Connecting to detailing applications
Prerequisites None
Version 2.0.3 158 of 224

MASDAR
34.7.4 Bentley Structural two-way integration with STAAD.Pro
Target audience - Structural designer

Products covered Bentley Structural, STAAD.Pro
Course description This course is intended for engineers and designers who have experience in using
both the STAAD.Pro and Bentley Structural software and want to learn the two-
way integration capabilities.
objectives - Understand the file format and status of a model
- Know how to import your STAAD model into Bentley Structural
- Recognize and solve the problems that may occur as the model develops
Course topics - Beginning STAAD: file format and how to tell the status of a model
- Import to Bentley Structural
- Pitfalls when developing a model
Prerequisites Working knowledge of Bentley Structural
Version 2.0.3 159 of 224

MASDAR
34.8 Infrastructure modelling

34.8.1 InRoads fundamentals
Target audience - Civil Engineer

- Civil engineering technician
- Design engineer
Products covered InRoads with MicroStation
Course description This course introduces civil engineering designers to using InRoads software for
road design projects. This hands-on training walks students through the project
design cycle; including setting up a project, existing ground data, geometry,
volume design, and reporting.
objectives - navigate and use the InRoads interface
- create a CAD files to be used for InRoads graphics using project defaults
- display surface contours, features and triangles
- create horizontal geometry alignments from graphics
- create and edit horizontal alignments through curve definitions
- create profiles and cross sections
- create and edit vertical PIs and define alignments
- create a corridor with the Roadway Designer
- create a surface from a corridor
- create and update cross sections
- annotate cross sections
- generate end-area volumes and volumes reports
- generate an XML report and fixed format report
Course topics - InRoads interface
- Setting up an InRoads project
- Project defaults
- Surface types
- Surface features
- Creating existing ground surfaces
- Displaying surfaces
- Surface properties
- Improving surface quality
- Creating, editing, and displaying horizontal alignments
- Creating, editing, and displaying vertical alignments
- Displaying profiles and cross sections
- Annotating cross sections
- Templates and components
- Introduction to roadway designer
- Earthwork volumes
- Reports
- Productivity tools
Prerequisites Students attending should have experience designing roadways and producing
design plans, and experience with MicroStation.
Version 2.0.3 160 of 224

MASDAR
34.8.2 Drainage fundamentals using InRoads
Target audience - Civil engineer

- Civil Engineering technician
- Hydraulics engineer
Products covered InRoads Storm & Sanitary
Course description This entry-level course introduces civil engineering designers to using InRoads for
Drainage Drafting and Design. This hands-on training walks you through
introductory surface and geometry concepts, laying out drainage structures,
displaying and annotating the drainage structures in plan, profile and cross section
views, and designing the drainage structures
Learning By the end of this course, students will be able to:
objectives - Set up a project.
- Be able to use Surfaces and alignments in drainage design.
- Lay out drainage structures.
- Modify previously created drainage structures.
- Display and annotate drainage structures in plan, profile and cross section
views.
- Create drainage queries and reports.
- Know about the tools available to assist in determining the location of the
drainage structures.
- Establish drainage flows and design the drainage network.
- Make changes to the drainage network and redesign the network
Course topics - Tour of InRoads Storm & Sanitary
- Project setup
- Introduction to surfaces and alignments
- Drainage lay out
- Displaying drainage in plan, profile, and cross sections
- Annotating drainage in plan, profile, and cross sections
- Queries and reports
- Location analysis
- Drainage flows and design
- Drainage network change
Prerequisites Students should have experience designing roadways and drainage systems,
producing design plans, and a working knowledge of the Windows operating
system. Experience with appropriate versions of MicroStation equivalent to the
topics taught in the Bentley Institute Essential MicroStation or Moving to
MicroStation courses
Version 2.0.3 161 of 224

MASDAR
34.8.3 InRoads surface modelling
Target audience - Civil engineer

- Civil engineering technician
- Designer
- Design engineer
Products covered In Roads surface modelling
Course description Students should have completed the InRoads Fundamentals and InRoads
Roadway Designer courses or possess equivalent knowledge of the topics covered
in those courses. Students should have experience designing roadways, producing
design plans, and a working knowledge of the Windows operating system.
Experience with appropriate versions of MicroStation equivalent to the topics
taught in the Bentley Institute Essential MicroStation or Moving to MicroStation
courses
Learning At the completion of this course, students will be able to use the InRoads surface
objectives design and editing commands to modify and create surface models. Specifically
they will be able to:
- Enhance existing surfaces with additional data
- Improve surface quality
- Model a traffic Island
- Model a detention pond
- Model a car park
Course topics - Edit surface commands
- Design surface commands
- Surface visualisation commands
- Workflow: incorporating additional surface data
- Workflow: improving surface quality
- Workflow: modelling a traffic island
- Workflow: modelling a detention pond
- Workflow: modelling a parking Lot
- Workflow: modelling a wall
Prerequisites Students should have completed the InRoads Fundamentals and InRoads
Roadway Designer courses or possess equivalent knowledge of the topics covered
in those courses. Students should have experience designing roadways and
producing design plans. Experience with appropriate versions of MicroStation
equivalent to the topics taught in the Bentley Institute Essential MicroStation or
Moving to MicroStation courses.
Version 2.0.3 162 of 224

MASDAR
34.9 Project team collaboration

34.9.1 ProjectWise essentials
Target audience Anyone who will manage technical documents (3D models, drawings,
specifications, etc) in Masdar‘ collaboration environment.
Products covered ProjectWise
Course description This course is for individuals who need to manage documents throughout a project
cycle. It presents many aspects of document management using ProjectWise
Explorer. Users will learn that ProjectWise is a scalable collaboration system used
by architecture, engineering, and construction teams to manage, find, and share
CAD and geospatial content, project data, and Office documents
objectives - manage project data within ProjectWise
- retrieve important project data and specification information
- share content data across a distributed enterprise
- manage images and Spatial oriented data
Course topics - Course Overview
- The Managed Environment
- The Integrated Environment
- The ProjectWise Explorer Client
- Workflows, States and Messaging in ProjectWise Explorer
- Executing Searches
- Working with Shareable Documents
- Settings and Utilities
- Navigating Using ProjectWise Web Part
Prerequisites None
Version 2.0.3 163 of 224

MASDAR
34.9.2 Administering ProjectWise
Target audience ProjectWise Administrator

Products covered ProjectWise
Course description This course covers configuration and administration of the ProjectWise
Engineering Content Management solution. It is primarily focused on the day-to-
day tasks associated with document and project management in ProjectWise.
objectives - install and configure ProjectWise
- configure clients
- manage users, projects, security, and data
Course topics - Introduction to ProjectWise
- Administrator
- ProjectWise architecture
- ProjectWise components
- Storage architecture
- Document architecture
- User accounts and concepts
- Environments
- The audit trail
- Client deployment
- Security
- Workflows
- Importing legacy data
- Application integration
- Maintenance
Prerequisites ProjectWise essentials
Version 2.0.3 164 of 224

Appendices
MASDAR
Appendices
1 Typical Masdar deliverables by project phase
2 Model elements by project phase
3 UniFormat classification system
4 Application-specific data
5 Masdar-specified tagged data
6 Masdar-specified external data
7 Standard project files for Bentley software
8 Masdar standard drawing symbols
9 Drawing border and title block
10 Meta-data specification
Version 2.0.3 165 of 224

Appendix 1: Typical Masdar deliverables by project phase
MASDAR
Appendix 1
Typical Masdar deliverables by project phase
This appendix lists the typical contract design deliverables for each Masdar project phase. 3D
models produced at each phase should be sufficiently detailed to produce the outputs listed,
together with any additional project-specific requirements. Project teams must comply with the
specific deliverable requirements for each Masdar project.
A1.1 Pre-design
A1.2 Concept design
A1.3 Schematic design
A1.4 Detailed design
A1.5 Construction documents
A1.6 Tender
Version 2.0.3 167 of 224

MASDAR
A1.1 PRE-DESIGN STAGE
The Design Consultant shall submit a detailed Project

Design Brief prior to the start of the concept design stage,
including:
Project overview
To explain the purpose, background, and goals of the

project as the Design Consultant understands them.
Sustainability criteria
To describe the strategies for the achievement of set

sustainability goals (KPIs)
Design criteria
To provide a detailed description of all the design criteria

for the project including site constraints, statutory
constraints, master plan and design regulations, design
criteria and any other design parameter that will affect the
project.
Construction cost estimate
To include a preliminary cost estimate for the project

itemized by project component to the level of detail
expected at this stage as per international standards.
Version 2.0.3 168 of 224

MASDAR
A1.2 CONCEPT DESIGN STAGE Utility systems and civil works including demand
calculations for min; fire lines, potable water lines, grey
and black water lines, drainage lines, irrigation water
Architectural lines, solid waste lines, district cooling lines, electrical
and ICT lines as they interface with the buildings and
connect to main infrastructure system.
a) Neighbourhood master plan
b) Concept site plans (1:200) a) Storm water drainage system including hydrologic
c) Concept floor plans (1:200) analyses in coordination with SIDC II consultant.
d) Concept exterior elevations (1:200) Landscape

e) Concept building sections (1:200)
f) External lighting concept b) Building site Plans showing building location, access
points, pedestrian and vehicular circulation, walkways,
g) Draft fire strategy driveways, on grade parking within five metres from the
h) Room data sheets, area schedules and unit mix summary plot boundary.
c) Planting plans for environmental terraces and parks.

Structural
a) Design Criteria Interiors

The consultant will submit the design loading criteria and d) Floor Plans, Elevations, Sections and Details for public
any wind loads he has determined from wind tunnel areas.
studies. He will make comparisons and give options for e) Mood images.
the design to continue in a selection of materials suitable f) Analysis of design brief/ concept in relations to
for the design comparing the various strengths of the architecture, sustainability, Company‘s brief, cultural
materials and their comparative costs and suitability. context, etc.
g) Space planning and programming
b) Plans, Sections and Elevations. h) Colour scheme.
i) 3-D renderings of two or more major interior design
The consultant will provide structural layouts showing spaces.
floor plans with structural grids, floor to floor heights, j) FF&E Concept
beam sizes, column sizes and approximate rates of k) Conformance or non-conformance report of the concept
reinforcement expected to be achieved in the final design. according to local authority guidelines and Masdar
guidelines.
c) Structural Systems l) Material board of the two or more major interior design
The consultant will provide at least 3 options of structural spaces.
systems including steelwork and pre cast concrete .He m) Consolidated Interior Design report summarizing the
will pay close attention to sustainable methods of facility program requirements.
construction and use design ideas to maximise off site
fabrication to improve quality and productivity. He will
Specialty systems
demonstrate clearly how the construction process will be
undertaken along with temporary works that may be
n) Façade Engineering Concept
required. He will give cost and time comparisons based
o) Sustainable Design Consultation and Energy Modelling
on real events and examples within his past portfolio.
p) Intelligent Building Design Concept
q) Specialty Lighting Design Concept
r) ICT, DATA, telecommunication and security
Mechanical s) Fire and Life Safety Engineering Strategy
t) Embodied carbon calculation and Carbon action plan
a) Floor Plans showing indicative system sizes and
locations, and location and size of equipment rooms
Presentation materials
b) Riser and distribution diagrams showing pipe and duct
sizing, flow quantities and control systems u) Rendered Plans, Elevations and Sections adequate to
represent the design intent
c) Design criteria and assumptions
v) Minimum Renderings and Animations (High quality

Electrical computer generated images equivalent to those in the
Master plan)
a) Floor Plans indicating lighting types and location, power
distribution, low voltage systems, and single line riser and a) Four exterior perspectives
distribution diagrams b) Two street perspectives at eye level
c) An aerial view in context of city
b) Design criteria and assumptions d) Two major Interior spaces
e) Two minute animation of computer generated
massing model
Civil
w) Scale study model
c) Site layout showing the civil and infrastructure works.
Grading and earthworks in coordination with the master Tender / construction packages
planner, landscape architect and SIDC II consultant.
x) Enabling Works ―Issued for Tender‖
Version 2.0.3 169 of 224

MASDAR
A1.3 SCHEMATIC DESIGN STAGE p) Landscape Irrigation System (Automatic Central control
systems; sprinklers, drippers, bubblers, misters etc.)
Civil
Architectural
a) Site Location Map
a) Neighbourhood Master Plan,
b) Plot boundaries
b) Schematic Site Plan,
c) Site Plan: in collaboration with the master planner,
landscape architect and SIDC II consultant showing all c) Area and Mix Summary for each building (in the
landscape and hardscape elements and limits of work. required format),
d) Utilities Plan: location and size includes as min; fire lines, d) Floor plans/Roof Plans Scale 1:200 for each building,
potable water lines, grey and black water lines, drainage
e) Exterior Elevations for all buildings scale 1:200,
lines, irrigation water lines, solid waste lines, district
cooling lines, electrical and ICT lines as they interface f) Sections scale 1:200
with the buildings and connect to main infrastructure
system on 1:500 scale. g) Typical Interior elevation,
e) Grading and Levelling Plan: with input from master h) Basic detail sections of exterior wall including
planner, landscape architect and SIDC II consultant on a foundations curtain and/or other wall systems scale
1:500 scale with cut and fill volumes. 1:100,
f) Drainage Plan: on 1:500, showing any ditches, inlets, i) Min of four (4) cross-sections for buildings and
trench drains, storage tanks or any other drainage feature surrounded plots,
with any connections to storage tanks, landscape areas,
undercroft structures, and/or grey water lines. j) Plans and drawings at scales of 1:100/50/20 shall be
prepared for specialty systems relating to, but not
g) Drainage Report: includes as a minimum the preparation limited to:
of a hydrology and hydraulics study identifying
schematically the sizing of all drainage features, the i. Vertical transportation and elevators,
methodology used, and the integration of the concept ii. Environment Optimization / Building material
surface water into the design. Also identifies shall be the considerations,
attenuation of 100yr, how the Design Consultant iii. Graphics/Signage – Outdoors and Indoor,
proposed to protect the building under a 100 yr flood. iv. Recreational/Aquatic Design of Pools,
v. Lighting/building maintenance, and
Landscape
k) plans, sections, elevations, system schematics, etc. and
any additional drawings/sketches and perspectives that
a) Prepare Landscape Site Layout Plan (1:200)
the Design Consultant feels necessary to submit and/or
b) Schematic Planting Plan (1:200) desired by The Company for broad illustrations,
c) Level and Grading Plan (1:200) l) Suspended ceiling layout scale 1:200,
d) Schematic Lighting Plan (1:200) m) Equipment layouts such as Kitchens, pantries,

washrooms, lockers & Changing;
e) Schematic Irrigation Plan (1:200)
Rooms, Counters & woodwork scale 1:100,
f) Estimated Energy and water demand including n) Basic Staircase detail scale 1:100,
assumptions and calculations
o) Materials selection and preliminary finishing schedule,
g) Enlargement Plan for special areas (1:100)
p) Finishes and fittings designations,
h) Landscape Details (1:10, 1:20, varies)
q) Co-ordinate space programme,
i) Planting Schedule (Quantities, Types of plants including
botanical names, common names, species/varieties, r) Schedules
availability, drought or salt tolerant plants, colour photos,
i. Door Schedule
maintenance and management technique, material
ii. Window Schedule
related to planting, such as; root barriers, garden edging,
iii. Hardware Schedule
soil mixes.)
iv. Room Finish Schedule
j) Pedestrian Circulation/Pavement, Types of paving
material, colour and patterns; (precast concrete pavers, Interiors design fit out and furnishings,
textured concrete, stones, gravels, pebbles etc., material fixtures, and equipment
availability, maintenance technique, paving schedule and
distribution, sustainability) a) Develop the approved concept design, taking into
account The Company's and PMC's comments,
k) Landscape Structures (Shelters, Pavilions, Gazeboes, including authorities‘ requirements. Prepare space
arbours, pergolas) planning for the project consisting of plans, elevations,
l) Steps / Ramps / Walls Screens and Fences sections, perspectives, and outline specifications, in
sufficient detail to illustrate and establish firmly the size
m) Landscape Furnishings (Seating, benches), signage, and character of the entire project as to interior design
bins, planter boxes/vases, drinking fountains including FF&E, and any special equipment, and all
other pertinent information,
n) Water Features (Fountains, channels, pools),
b) Provide for Mock ups for typical areas upon The
o) Landscape Lighting (Pedestrian lighting, Floodlight, Company‘s request,
Decorative lighting, bollards etc.)
c) The drawings to be fully dimensioned,
Version 2.0.3 170 of 224

MASDAR
d) Cross-references indicating all finishes and equipments Structural

into drawings,
a) Piling and shoring design – pile and shoring design
e) Prepare preliminary draft of particular conditions of ready for tender, containing piles layout, pile schedules
contract, specifications, and schedules. The specifications with diameters, lengths, loading, and reinforcement,
shall be adequate to define the types and quality of
construction, specific materials, and the quality of typical b) Ground slab – 60% with building utility structures – pits,
interior finishes, types of materials and sources including tanks, etc.,
the implications for maintenance, repair, and replacement
to enable The Company to better understand their c) Podium; Superstructure Provision of schematic design
application to the project. Items of major equipment shall that includes framing,
be scheduled and defined in outline form in the
specifications, d) Foundation plans and typical details; 60% with building
utility structures – pits,tanks, etc.,
f) Review and analysis of the selected design concept and
its contents to include locality of the project, accessibility, e) Typical floor and roof framing plans,
parking, relationship between different areas, materials, f) Typical member size noted,
finishes, and heights, etc.
g) Lateral load resisting system noted,
g) Drawing deliverables:
h) Preliminary framing and foundation plans indicating
i. List of areas requiring Interior Design Treatment member; sizes, slab thicknesses,
ii. General notes
iii. List of drawings i) Reinforcement quantities per cubic or square meter for
iv. Partition layout- scale 1:100 all elements and members,
v. Furniture layout- scale 1:100
vi. Flooring layout- scale 1:100 j) Reinforcement per cubic or square meter for all
vii. Wall Finishes layout - scale 1:100 elements and members,
viii. Ceiling layout- scale 1:100 - coordinated with MEP for
all systems k) Output of the computer model indicating members and
ix. Lighting Layout- scale 1:100- with circuiting elements Stresses and forces,
coordinated with MEP, l) Produce scope of works for wind tunnel test,
x. Lighting Circuiting- scale 1:100 - coordination with MEP
xi. Small Power Layout - scale 1:100 - coordinated with m) Wind tunnel test results fully implemented at the end of
MEP this stage,
xii. Equipment layouts such as Kitchens, pantries,
washrooms, lockers & Changing Rooms, Counters & n) Outline Specifications,
woodwork scale 1:50
xiii. Interior Elevations and sections of all areas /Details & o) Geotechnical report shall be ready during this stage and
finishes showing location of all MEP fittings & accessories the output of the geotechnical report shall be
- scale 1:50 implemented at the schematic design stage,
xiv. Joinery/Millwork, Plans, Sections, Details - scale 1:20, p) Produce Scope of works for the Geotechnical
1:5 and 1:1 Investigation,
xv. Interior Door Schedule- scale 1:50
xvi. Interior Window Schedule- scale 1:50 q) In the case of pile foundation the designer shall also
interpret in coordination with the geotechnical report the
The interior design should incorporate all of the following items results obtained from the testing of the preliminary piles,
and include schedules when necessary. Cross disciplinary
coordination is required. (Note: All documents need to be r) Final pile design containing piles layout, pile schedules
supported with technical specifications & sustainable material with diameters, lengths and reinforcement,
evaluation with predicted carbon footprint calculation.)
s) The designer shall allow for storage and conservation of
the soil samples until required by The Company,
i. AV equipments,
ii. CCTV- Security and surveillance systems, t) Final pile design containing piles layout, pile schedules
iii. Ironmongery schedule including access control, with diameters, lengths and reinforcement,
iv. FF&E, including fixed and loose furniture- custom made u) Load data sheet,
and ready made,
v. Soft finishes i.e. Fabrics or similar for furniture, wall v) General notes drawing, and
panelling, curtains etc.,
vi. Sanitary ware equipments, w) Differential shortening of the columns assessment and
vii. Acoustic treatments, creep assessment.
viii. Kitchen Equipments to include wet, dry and cold stores for
all food and beverage facilities,
ix. Gymnasium equipment (if applicable),
x. Home automation system, Mechanical systems
xi. Curtain rail (automatic or manual),
xii. Graphics/Signage, Schematic descriptions and design of mechanical
xiii. Interior doors, glazed screens, partitions, access panels, systems, to the extent applicable for each building,
fire hose cabinets, etc., details and schedules, including energy sources, District Cooling Company
xiv. Hard Finishes Schedule, considerations, HVAC loads, energy conservation
xv. Retail Design Consultant‘s details regarding outlets, factors, special mechanical and process systems,
xvi. Recreation/Aquatic Design of Pools, Water and Drainage, fire fighting, systems descriptions
xvii. Stairs and handrails, and hourly /daily demand, impact on other disciplines
xviii. Lighting both architectural and decorative, and and special code requirements and any other system
xix. Accessories including office equipments, waste bins, recommended by the Company for the proper
planters and plants, artwork etc. operation. This includes but not limited to the following:
Version 2.0.3 171 of 224

MASDAR
Air conditioning system g) Fire Fighting Monitoring and Alarm Systems,
Ducting, method of air- chilled water distribution, type of h) Vertical transportation control system,
A/C, etc. Comparative evaluation of different HVAC i) Leak detection system in the chilled water pipes
systems and techniques to be presented based on life (Alarm),
cycle costing to demonstrate the viability of the proposed
system. j) Automatic chemical treatment system of chilled water
(Alarm),
a) Air conditioning design report including preliminary heat
load calculation, HVAC design criteria, k) Motorized Damper / Fire Damper,
b) Interface with all utilities detail, Energy Transfer Station, l) Water Pump Sets (Domestic + filtration unit),
equipment plans, and controls schematics,
m) Water Tanks,
c) Chilled water system,
n) Water filtration system,
d) Equipment schedule (unit ref, capacity, etc.)
o) Drainage Pumps (Sewage + Storm water),
e) Air distribution duct layouts indicating positions of volume
control dampers and fire/smoke dampers, air outlets p) Fire Pump set,
f) Piping layouts and schematic diagram, with size and flow q) Generator Sets,
rates, distribution of equipment, at each floor. r) LV Main Switchgear,
g) Fresh air intake and ventilation and smoke extraction s) Emergency Lighting System,
details and riser diagram.
t) Fire Alarm and Clear Agent system,
h) General details and sections
u) Access Control System,
i) Geothermal system, schematic layout, specification
v) Amenities, Gym sports and Steam room equipments,
Fire protection and
Fire-fighting system including active and passive fire w) Vertical transportation system.
strategy and plan, hydraulic calculations, smoke exhausts
managements system with related calculations. Electrical power
a) Design brief including system description and standards a) Finalize the applicable Codes and Standards,
reference used in design,
b) Power Supply and Power Distribution,
b) Compartmentalization and egress plans,
c) Substation and HV Distribution Scheme,
c) Hydraulic calculations,
d) LV distribution Scheme,
d) Pipe work network plans, and sprinkler layout plan
e) Power supply to HVAC and mechanical equipment,
e) Fire Water supply schematic diagram, and
f) Final circuit power supply,
f) Sections and details.
g) Hotel management system,
Plumbing h) Fire detection and alarm system,
a) Drainage pipe work network plans, i) ELV Systems,
b) Domestic water supply piping plans, j) CATV, SMATVICT systems,
c) Water supply schematic diagram, k) PA System,
d) Grey water and black water schematic system, and l) ICT.
e) Section and details. m) Security and Surveillance systems,
f) Plumping &drainage isometric riser drawings n) Telecom/Voice /Data Systems, including IT systems,
o) Raceway and Containment,

Building management system (BMS)
p) Stand by and backup system
BMS shall cover but not limited to the following systems:
q) Lightning protection system,
a) Security (CCTV) and access control systems,
r) Earthing system,
b) Emergency Diesel Generators,
s) Electrical rooms size & location,
c) Lighting Control System,
t) Electrical load estimation,
d) HVAC control systems (Chilled Water pumps, FCU. AHU,
Ventilation Fans…etc.), u) Emergency load estimation,
e) Water Supply Control Systems, v) Transformer sizes
f) Irrigation Control Systems, w) Any other system recommended by the Company for
the proper operation.
Version 2.0.3 172 of 224

MASDAR
Lighting
a) General Lighting
b) Emergency lighting
c) Façade lighting
d) External lighting
e) Special feature lighting
f) Obstruction lighting
g) BOH lighting
h) FOH lighting
Specialty systems
a) Vertical transportation and elevators,
b) Retail Design Consultant details regarding outlets,
c) Environment Optimization / Building material

considerations,
d) Telecom/Voice /Data Systems, including IT Design

systems,
e) Security and Surveillance systems,
f) Graphics/Signage – Outdoors and Indoor,
g) Recreational/Aquatic Design of Pools,
h) Lighting/building maintenance
i) ICT.
Presentation materials
1. Rendered Plans, Elevations and Sections adequate to

represent the design intent
2. Marketing Package including overall plans, unit plans, unit

mix summary and other documentation required to
support the development of marketing brochures by The
Company.
3. Minimum renderings and animations (high quality

computer generated images equivalent to those in the
master plan)
a) Four exterior perspectives

b) Two street perspectives at eye level
c) An aerial view in context of city
d) Two major interior spaces
e) A fully rendered fly-through digital visualization Video
(3 minute minimum)
4. Physical model at 1:200 scale showing the detail of the

buildings
Tender / construction packages
1. Piling package ―Issued for Tender‖
2. Other designated packages ―Issued for Tender‖

OPTIONAL (as determined by The Company)
3. Design-build package ―Issued for Tender‖ OPTIONAL (as

determined by The Company)
Version 2.0.3 173 of 224

MASDAR
A1.4 DETAILED DESIGN STAGE e) Prepare Planting Plan and Preliminary Details Scale
1:100/50/ 20/10) - Names, sizes, plant list or schedule,
Civil quantity, botanical name (genus, species and variety),
common name, size (height, spread, caliper) spacing,
a) General Notes and special requirements, (multistem, first branch
height). Other information needed on the plan:
b) Site Location Map
i. Property lines, match lines, and limit of contract
c) Plot boundaries
ii. Buildings and overhangs
d) Utilities i. General Notes iii. Paved areas, terraces, and walls
ii. Schedules iv. Surface and sub-surfaces utilities
iii. Plans v. Location and size of existing plant material
iv. Riser Diagrams vi. Location, type, and size of proposed plant material
v. Details vii. Areas to receive seed or sod
viii. Planting list or schedule
e) Site Plan: Detailed Site plan showing all surrounded ix. Existing and proposed topography
areas and plots and in collaboration with the master x. Location of decorative lighting fixtures
planner, landscape architect and SIDC II consultant xi. Irrigation plan
detailing all landscape and hardscape elements and limits
of work. Provide Geometric coordinates to all elements f) Irrigation Plan and Preliminary Details (Scale
with northing and easting based on NADD (New Abu 1:500/200)
Dhabi Datum). Scale 1:100
g) Prepare Water feature design drawings (1:500/200/100)
a) Utilities Composite Plan: location and size, plan and
profile include as minimum; fire lines, potable water lines, h) Prepare Lighting Plan and Preliminary Detail
grey and black water lines, drainage lines, irrigation water (1:500/200/100/50)
lines, solid waste lines, district cooling lines, electrical and i) Prepare Enlargement Plan, Preliminary Site details and
ICT lines as they interface with the buildings and connect sections (1:200/100/50/20)
to main infrastructure system on 1:100 scale. Geometric
coordinates shall be provided to connection points to the i. Earthwork sections
main infrastructure system. 3D drawings shall be ii. Pavements, curbs and edgings
prepared wherever necessary. iii. Shelters, decks and other structures;
iv. Screens, decks and other structures;
b) Preliminary Grading and Levelling Plan of finish floor v. Furnishing and features;
elevations finished grades, curb grades, pad elevations, vi. Utilities;
drainage pattern, slopes, retaining walls location, and vii. Plant Installation.
paving as related to the project. Scale 1:100. Earthwork
cut and fill volume quantities should be given at this stage j) Prepare Preliminary Hardscape Details;
as well with clarifications of assumptions on soil removal,
undercut assumptions, trench or podium volumes k) Landscape Specifications (Hard landscape, Soft
assumed. 3D drawings shall be prepared wherever landscape and Irrigation);
necessary.
l) Maintenance Specifications and Schedules (Hard
c) Preliminary Drainage Plan 1:100, detailing including plan landscape, Soft landscape and Irrigation)
and profile of ditches, inlets, trench drains, storage tanks
or any other drainage feature with any connections to Architectural
storage tanks, landscape areas, undercroft structures,
and/or grey water lines. Geometric coordinates shall be s) Cover title sheets
provided to all drainage features. 3D drawings shall be
prepared wherever necessary. t) General Notes
f) Drainage Report: includes all updates from the Schematic u) Plan drawings for all floors and all buildings showing:
Stage.
i. Building perimeter exterior wall type and thickness;
ii. Structural grid including column location;
Landscape iii. All interior fixed spaces including building core
elevators, stair, shafts, toilets, equipment rooms and
a) Cover or Index Sheet; interior partition including door swings;
iv. Dimensions, all space designation, all floor
b) Overall Landscape Plan (1:500); elevations, wall types, door types and cross reference
to detail sheets;
c) Prepare Layout and Materials Plan (1:200) - Shows the v. Built in furniture and equipment location;
proposed landscape features superimposed on the plan. vi. Indicate all finish material of spaces.
i. Plot lines with bearings and distances, station offsets
v) Reflected ceiling plans for all floors at scale 1:100
and coordinate point easement, setbacks, match lines,
indicating: lighting layout, softies, coves, furring‘s,
limit of contract lines and benchmarks;
skylights (if any), ceiling materials, acoustical treatment,
ii. Buildings and other structures;
and relationship with partitions, interface with window
iii. Outdoor lighting locations;
details, sprinklers, access panels and exposed
iv. Other site features (walls, water features, walks, steps,
structure;
benches and planters) and other material distribution.
w) Lift stop diagram schedule for each building & Podium;
d) Finish Grading / Drainage Plan (Scale 1: 200);
x) Enlarged plans at scale 1:20 including built in furniture
and equipment layouts, floor treatments requirement,
wall cladding for typical areas, public spaces and
special spaces depending on the nature of the project;
Version 2.0.3 174 of 224

MASDAR
y) Detail plans and sections at scale 1:20 of core elements, Interiors design fit out and furnishings,
identifying clearances, shaft requirements, dimensions, fixtures, and equipment
and special details for: (1) stairs (2) elevators and (3)
toilet facilities; a) Develop the approved Schematic Design, taking into
z) Elevation at scale 1:200 indicating:
including authorities‘ requirements. Prepare space
i. Full height of elevations including roof structures and planning for the project consisting of plans, elevations,
mechanical equipment spaces; sections, perspectives, and outline specifications, in
ii. Fenestration, brise soleil, curtain wall, cladding sufficient detail to illustrate and establish firmly the size
surfaces and clarify relation to interior walls and slabs; and character of the entire project as to interior design
iii. Overall floor height and floor slab elevation; including FF&E, and any special equipment, and all
iv. Column line and axes; other pertinent information,
v. Setbacks, building profiles and expansion joints;
vi. Finishes and surface patters (if any).
Company‘s request,
aa) Detail elevations at scale1: 50/1:20 to clarify key elements c) Participate in workshop upon The Company‘s request,
including
d) Arrange for factory visits locally and abroad upon The
i. Recesses; Company‘s request,
ii. Typical bay;
iii. Building entry and exits including ramps; e) Prepare vender / supplier list, the proposed list shall
iv. Masonry patterns and coursing (if any); include the following:
v. Plaster joint and texture.
i. Specified products/items are available, on a
bb) Building sections at scale 1:200 to explain changes in competitive basis, from a minimum of 3 to 4 sources.
grade, overall floor to floor to ceiling dimensions and ii. Contact details of vendors/suppliers are current.
clearances, vertical dimensions and label major spaces; Please note that it is much preferable to engage local
suppliers / vendors
cc) Detail wall sections at scale 1:50 / 1:20, major different
conditions at wall sections to convey basic building f) The drawings to be fully dimensioned,
construction systems and materials clearly dimensioned
to show: g) Cross-references indicating all finishes and equipments
into drawings,
i. Foundation and below grade construction;
ii. Typical wall construction; h) Prepare final draft of particular conditions of contract,
iii. Abutting floor systems; specifications, and schedules. The specifications shall
iv. Window type and location; be adequate to define the types and quality of
v. Exterior finishes, insulation and interior finishes; construction, specific materials, and the quality of
vi. Mechanical penetration and block outs; typical interior finishes, types of materials and sources
vii. Parapet and roof construction; including the implications for maintenance, repair, and
viii. Key and interface all construction to elevations and replacement to enable The Company to better
floor plans. understand their application to the project. Items of
major equipment shall be scheduled and defined in
dd) Large scale details (scale as required) for major clarifying outline form in the specifications,
plan details, keyed to
i) Options for project procurement and recommendations
floor plans for: on the proposed option.
i. Window types, sill, mullions, jams and head details,
j) Drawings
glazing type and
venting; i. List of areas requiring Interior Design Treatment
ii. Hollow metal; ii. General notes
iii. Frame type; iii. List of drawings
iv. Metal and glass walls; iv. Partition layout- scale 1:100
v. A special detail for surface trims and finishes. v. Furniture layout- scale 1:100
ee) Ground floor plans for al floors indicating flooring, vi. Flooring layout- scale 1:100
materials, kinds and types of patterns at scale 1:100/1:50 vii. Wall Finishes layout - scale 1:100
viii. Ceiling layout- scale 1:100 - coordinated with MEP
ff) Detailed elevations and sections at scale 1:50 for interior
for all systems
spaces interfaced and cross referenced floor and
ix. Lighting Layout- scale 1:100- with circuiting
reflected ceiling indicating suspended ceiling lines, floor
coordinated with MEP,
elevation, wall treatment and materials, pertinent notes
x. Lighting Circuiting- scale 1:100 – coordination with
and dimensions;
MEP
gg) Schedules xi. Small Power Layout - scale 1:100- coordinated with
MEP
v. Door Schedule xii. Equipment layouts such as Kitchens, pantries,
vi. Window Schedule washrooms, lockers & Changing Rooms, Counters &
vii. Hardware Schedule woodwork scale 1:50
viii. Room Finish Schedule xiii. Interior Elevations and sections of all areas /Details
& finishes showing location of all MEP fittings &
accessories - scale 1:50
xiv. Joinery/Millwork, Plans, Sections, Details - scale
1:20, 1:5 and 1:1
xvi. Interior Window Schedule- scale 1:50
xvii. General details- coordination between different
surfaces / materials. Scale 1:2 and 1:1
Version 2.0.3 175 of 224

MASDAR
The interior design should incorporate all of the following k) Details indicating accommodation with
items and include schedules when necessary. Cross mechanical/electrical at area of major interface@ 1:25
disciplinary coordination is required.
l) Technical specifications that include all necessary
(Note: All documents need to be supported with technical contractual and technical information to assure
specifications & sustainable material evaluation with adherence to the contract documents specifications
predicted carbon footprint calculation.) shall follow the CSI master format
m) Particular conditions (if any)

a) AV equipments,
b) CCTV- Security and surveillance systems, Fire implementation strategy

c) Ironmongery schedule including access control, a) Plans at scale 1:100 for all floors to indicate:
d) FF&E, including fixed and loose furniture- custom made i. Fire alarm and smoke zones location of water supply;
and ready made, ii. sprinkler layout and pipe distribution Standpipes;
iii. Fire extinguisher cabinets;
e) Soft finishes i.e. Fabrics or similar for furniture, wall iv. Exit paths from each zone;
panelling, curtains etc., v. Distances to the stair;
f) Sanitary ware equipments, vi. The occupancy of each area;
vii. Fire proofing of structural members.
g) Acoustic treatments, viii. Equipment room @1:50 scale with size, flow rates
and dimensions.
h) Kitchen Equipments to include wet, dry and cold stores
for all food and beverage facilities, b) Final plans at same scale as architectural to indicate:
i) Gymnasium equipment (if applicable), c) Types, features, age reliability, capacity, zoning,
supervision control panel and power supplies, initiating
j) Home automation system, devices and auxiliary function for fire alarm system;
k) Curtain rail (automatic or manual), d) Coordinated floor plans and site layout by system at
l) Graphics/Signage, same scale as architecture showing single line
distribution system; locating major equipment and size
m) Interior doors, glazed screens, partitions, access panels, clearance requirements; shafts (dimension chases;
fire hose cabinets, etc.details and schedules, mechanical rooms and required wall /floor penetrations
and block outs);
n) Hard Finishes Schedule,
e) Riser diagram for fire alarm system indicating
o) Retail Design Consultant‘s details regarding outlets, interconnection with paging and communication
systems;
p) Recreation/Aquatic Design of Pools,
f) Details to include:
q) Stairs and handrails,
i. Door and window schedule indicating fire rating and
r) Lighting both architectural and decorative, and whether fire rated glazing (in coordination with
s) Accessories including office equipments, waste bins, architecture);
planters and plants, artwork etc. ii. Interconnection of lift controls & fire alarm system;
iii. Interconnection with kitchen fire extinguishing and
Structural fire pump system to the fire alarms system (if any);
iv. Reference note to HVAC drawings that indicate
interconnection HVAC system (dampers, fans) with duct
a) General Notes
smoke detectors and / or fire alarm system;
b) Schedules v. Technical specs. shall follow CSI MasterFormat;
vi. Itemized BOQ with measure per each item;
c) Final design calculation for foundation and superstructure; vii. Particular conditions (if any);
viii. Detailed cost estimates.
d) Foundation plan @ scale 1:50 / 1:100; ix. Hydraulic calculations / authority approval.
e) Pile arrangement layout sheet (if required) @ scale
1:50/1:100 – 90% ready for permitting and construction Plumbing
f) Foundation details including (1) reinforcement details and a) Floor Plans / elevations indicating plumbing
sections and (2) reinforced concrete walls and core requirements, sizes and distribution, including hot and
starter details at scale 1:25 - ready for tender, with cold water distribution and drainage systems collection
building utility structures – pits, tanks, etc systems, scale 1:100;
g) Coordinated floor plans showing column axes and b) Floor Plans / elevations of toilets and bathrooms,
dimension (including column reinforcement details) @ indicating location of fixtures, piping, valves and
scale 1:100/1:50 connections, scale 1:50;
h) Typical floor framing plans, including sizing of beams, c) Plans indicating size and location of major equipment
slab openings, thickness and depression of block outs @ and clearances required for maintenance, shafts, and
scale 1:100/1:50 equipment rooms, including water storage
requirements;
i) Non typical framing scheme were required @ scale 1:25
d) Riser and Distribution Diagrams, for domestic hot and
j) Details of major unique conditions (core, stairs, ramp, cold water supplies and drainage collection systems,
basement reinforced concrete wall) @ scale 1:25 showing Schematic pipe sizes, flow quantities, control
systems;
Version 2.0.3 176 of 224

MASDAR
e) Visual impact of system elements, where required (e.g. Power and lighting
roof mounted equipment);
Final electrical lighting and power layout plans of
f) Calculations and assumptions per final design; different floors in at scale 1:100 including:
Mechanical systems a) Layout plans of lighting systems
a) Air-conditioning system b) Layout plans of power systems
− HVAC floor plans @ scale 1:100 for typical areas c) Single line diagrams for mains and emergency supplies
showing
d) Layout plans, sections and details of electrical
equipment room and risers at scale 1:50 & 1:25
b) Main supply, return and exhaust air ductwork with sizes
based on the updated calculations; e) Layout plan and details of earthing and lighting
protection systems;
c) Cross sections indicating clearances between piping, duct
work, sprinklers, bus duct, lighting fixtures, diffusers/grills f) Primary distribution including duct lines and manholes,
etc. indicating coordination with structural, architectural cable details, switchgear, physical location and layout,
and electrical features; core layouts (unit substation plan layouts), and
equipment units;
d) Plans and sections @ scale 1:50 to indicate individual
room air distribution and temperature control arrangement g) Secondary distribution including switchboard and or
for a representative sample of typical spaces, and special switch gear floor plans and layouts, core area, and
spaces according to the nature of the project @ scale utility closet, power and lighting panel locations, motor
1:50 showing routing and sizing of all piping and duct control centre layouts and locations, bus duct routing
works; and rating, space allocated for feeder cables and
propped routing, and equipment type;
e) Coordinated sections (typical) including all services (MEP
& Fire) h) Lighting including fixtures layout for each area (specify
type of fixtures used) site lighting, typical switching,
f) Coordinated floor plans and site layout by system at same decorative and architectural lighting and lighting fixtures
scale as architecture showing single line distribution details;
system; locating major equipment and size clearance
requirements; shafts (dimension chases; mechanical
rooms and required wall /floor penetrations and block Telephone systems, data system, audio
outs); visual, access control, building management
system, ICT systems
g) Provide updated @ scale 1:50; typical mechanical
equipment room plans with resolution of review
a) Final low current system layout plans of different floors
comments made during previous submission;
at scale 1:100 including:
h) Final riser diagrams for air handling systems and i. Layout plans of telephone and paging system;
hydraulic systems by providing quantities and sizes to
ii. Layout plans of data network system (showing the
reflect the latest engineering calculations;
data network passive components);
i) Results for sounds/acoustic analysis to ensure that the iii. Layout plans of access control and time keeping
noise generated by the air handling units and the fans; system;
iv. Layout plans of CCTV system;
j) Schematic control diagrams for each type of typical air v. Layout plans of audio / visual systems for meeting
and hydraulic system used for development in previous room.
submission; b) Final layout plan of elevators indicating arrangement,
risers, details of shafts and machine rooms and
k) Equipment schedules upon which design is based schedule of elevators;
including pumps, fans, filters, coils, radiators, diffusers,
chillers, attenuators, cooling towers, air handling units, fan c) General arrangement layout plans and details of low
coil units, VAV boxes etc. current systems control rooms indicating arrangement
of different equipments such as:
l) Schedules of equipment indicating capacity and
performance characteristics. All details and section − PABX, consoles, PC, MDF, IDF etc.
requirements for a comprehensive presentation of the − Data network patch panels, risers etc.
design and installation requirements including − Access control computer, printer etc.
coordination with architectural, structural and electrical − CCTV monitors, VCRs, Printers etc
features; - ICT Systems
m) The specifications including all necessary contractual and d) Low current systems riser diagrams including systems
technical information to assure adherence to the contract chart and distribution in each floor;
documents;
e) Preliminary General and specific installation details of
n) Written description of the sequence of operation on the low current systems equipments, issuers, raceways and
floor plans explaining clearly the function and role of each interfacing with other systems such as elevators, HVAC,
control device and describe the safety/alarms and normal fire pumps, access control etc.
/fire operating controls of each system.
− Technical specifications for different low current
o) Geothermal system plan, layout, riser diagram ,sequence systems and elevators;
of operation, control schematic, specification, − Particular conditions if any;
manufacturer, supplier list etc − Itemized BOQ with measures per each item in the
design works.
Version 2.0.3 177 of 224

MASDAR
Specialty systems Presentation and other materials
Design, report, drawings and specification relating to 1. Leasing Drawings for each individual tenant‘s space
specialty system may need to incorporated into the above that will be used as part of the lease agreement with
mentioned Tender packages relating to, but not limited tenants. These drawings should include a plan for the
to:- tenant space with dimensions and areas for the space
and an overall plan for the building and floor showing
Intelligent Building Management and Control System of the location of the tenant space within the plot and
the following systems: building.
a) Emergency Generators 2. Rendered Plans, Unit Plans and Elevations adequate

for marketing purposes
b) Lighting Control System
3. Minimum Renderings and Animations as required to
c) HVAC system (Chilled Water pumps, CHW Pressurization represent significant design modifications (High quality
Units, FCU. AHU, Ventilation and Extract Fans, Fresh Air computer generated images equivalent to those in the
Handling Units …etc). Master plan).
d) Water Supply System 4. Models, as required to represent significant design

modifications
e) Irrigation System
f) Fire Fighting system (Monitoring only. Control shall be Tender / construction packages
through Fire Control Panel).
1. Full Package ―Issue for Tender‖
g) Leak detection system in the chilled water pipes (Alarm).
2. Piling Package ―Issued for Construction‖
h) Automatic chemical treatment system of chilled water
(Alarm).
i) Motorized Damper / Fire Damper
j) Water Pump Sets (Domestic + filtration unit)
k) Water Tanks
l) Water filtration system
m) Drainage Pumps (Sewage + Storm water)
n) Fire Pump set
o) Generator Sets
p) Lifts
q) LV Main Switchgear
r) Emergency Lighting System
s) Fire Alarm and Clear Agent system
t) Access Control System
u) CATV System
v) Amenities, Gym sports and Steam room equipments
w) Vertical transportation system.
x) Coordinated floor plans at same scale as architecture

showing single line distribution system; locating major
equipment and size clearance requirements; shafts
(dimension chases; mechanical rooms and required wall
floor penetrations and block outs);
y) Plans of special floors (basement, lobby, technical gallery

if required showing equipment locations, clearance
requirements etc.
z) Building Management and Control System riser diagrams

etc.
aa) Standard general miscellaneous details for typical

installations of Building Management and Control System;
bb) Complete material and equipment specifications for all

Building Management and Control System Technical
specifications including all necessary contractual and
technical information to assure adherence to the contract
documents.
Version 2.0.3 178 of 224

MASDAR
A1.5 CONSTRUCTION DOCUMENTS STAGE d) Finish Grading / Drainage Plan (Scale 1: 200);
e) Prepare Planting Plan and Details Scale 1: 100/50/ 20) -

Construction drawings shall be based on The Company‘s
Names, sizes, plant list or schedule, quantity, botanical
approval of all applicable Detailed Designs, cost studies,
name (genus, species and variety), common name, size
and/or modified designs authorized by The Company.
(height, spread, caliper) spacing, and special
Additional submittals may be required.
requirements, (multistem, first branch height). Other
information needed on the plan:
Civil
i. Property lines, match lines, and limit of contract
d) General Notes ii. Buildings and overhangs;
iii. Paved areas, terraces, and walls;
e) Final Site Location Map iv. Surface and sub-surfaces utilities;
f) Plot boundaries v. Location and size of existing plant material;
vi. Location, type, and size of proposed plant material;
g) Utilities i. General Notes vii. Areas to receive seed or sod;
ii. Schedules viii. Planting list or schedule;
iii. Plans ix. Existing and proposed topography;
iv. Riser Diagrams x. Location of decorative lighting fixtures;
v. Details xi. Irrigation plan.
h) Final Site Grading f) Irrigation Plan and Details (Scale 1: 200);
i) Final Site Plan: Detailed Site plan showing all surrounded g) Prepare Water feature (1: 200/100);
areas and plots and in collaboration with the master
planner, landscape architect and SIDC II consultant h) Prepare Lighting Plan and Detail (1: 200/100/50);
detailing all landscape and hardscape elements and limits i) Prepare Enlargement Plan, Site details and sections (1:
of work. Provide Coordinate Geometry to all elements 100/50/20)
with northing and easting based on NADD (New Abu
Dhabi Datum). Scale 1:100 i. Earthwork sections;
ii. Pavements, curbs and edgings;
j) Detailed Utilities Composite Drawings: detail design iii. Shelters, decks and other structures;
drawings includes as minimum; fire lines, potable water iv. Screens, decks and other structures;
lines, grey and black water lines, drainage lines, irrigation v. Furnishing and features;
water lines, solid waste lines, district cooling lines, vi. Utilities;
electrical and ICT lines as they interface with the buildings vii. Plant Installation.
and connect to main infrastructure system on 1:100 scale. j) Prepare Hardscape Details;
Geometric coordinates shall be provided to connection k) Prepare and Submit Construction Documents;
points to the main infrastructure system. Final 3D l) Landscape Specifications (Hard landscape, Soft
drawings shall be prepared wherever necessary. landscape and Irrigation);
k) Final Grading and Levelling Plan of finish floor elevations m) Maintenance Specifications and Schedules (Hard
landscape, Soft landscape and
finished grades, curb grades, pad elevations, drainage
Irrigation);
pattern, slopes, retaining walls location, and paving as
related to the project. Scale 1:100. Earthwork cut and fill
volume quantities should be given at this stage as well Architectural
with clarifications of assumption on soil removal, undercut
assumptions, trench or podium volumes assumed. Final hh) Cover title sheets
3D drawings shall be prepared wherever necessary.
ii) General Notes
l) Detailed Drainage Drawings 1:100, detailing ditches,
jj) Plan drawings (A1 size) for all floors and all buildings @
inlets, trench drains, storage tanks or any other drainage
scale 1:100/200 indicating:
feature with any connections to storage tanks, landscape
areas, undercroft structures, and/or grey water lines. i. Building perimeter exterior wall type and thickness;
Geometric coordinates will be provided to all drainage ii. Structural grid including column location;
features. 3D drawings shall be prepared wherever iii. All interior fixed spaces layout like building core
necessary. elevators, stair, shafts, toilets, equipment rooms and
interior partition including door swings;
m) Final Drainage Report: includes all the hydrological and
iv. Dimensions, all space designation, all floor
hydraulic analyses and calculations.
elevations, door type indication and cross reference to
detail sheets;
Landscape v. Built in furniture and equipment location;
vi. Indicate all finish material of spaces.
a) Cover or Index Sheet; kk) Lift stop diagram schedule for each building & Podium;
b) Existing Conditions Plan (1:200); ll) Blow up plans at scale 1:20 including built in furniture
and equipment layouts, floor treatments requirement,
c) Prepare Layout and Materials Plan (1:200) - Shows the
wall cladding for typical areas, public spaces and
proposed development superimposed on the existing
conditions plan. special spaces depending on the nature of the project;
mm) Detail plans and sections at scale 1:20 of core

i. Properties lines with bearings and distances, station
elements, identifying clearances, shaft requirements,
offsets and coordinate point easement, setbacks, match
lines, limit of contract lines and benchmarks; dimensions, and special details for: (1) stairs (2)
elevators and (3) toilet facilities;
ii. Buildings and other structures;
iii. Outdoor lighting locations;
iv. Other site features (walls, walks, steps, benches and
planters) and other material distribution.
Version 2.0.3 179 of 224

MASDAR
nn) Elevation at scale 1:200 indicating: Interiors design fit out and furnishings,
fixtures, and equipment
i. Full height of elevations including roof structures and
mechanical equipment spaces;
a) Develop the approved Schematic Design, taking into
ii. Fenestration, brise soleil, curtain wall, cladding
surfaces and clarify relation to interior walls and slabs;
including authorities‘ requirements. Prepare space
iii. Overall floor height and floor slab elevation;
planning for the project consisting of plans, elevations,
iv. Column line and axes;
sections, perspectives, and outline specifications, in
v. Setbacks, building profiles and expansion joints;
sufficient detail to illustrate and establish firmly the size
vi. Finishes and surface patters (if any).
and character of the entire project as to interior design
including FF&E, and any special equipment, and all
oo) Detail elevations at scale1: 50/1:20 to clarify key elements
other pertinent information,
including
i. Recesses;
ii. Typical bay;
iii. Building entry and exits including ramps; c) Participate in workshop upon The Company‘s request,
iv. Masonry patterns and coursing (if any);
v. Plaster joint and texture. d) Arrange for factory visits locally and abroad upon The
pp) Building sections at scale 1:200 to explain changes in
grade, overall floor to floor to ceiling dimensions and e) Prepare vender / supplier list, the proposed list shall
clearances, vertical dimensions and label major spaces; include the following:
qq) Detail wall sections at scale 1:20, major different i. Specified products/items are available, on a
conditions at wall sections to convey basic building competitive basis, from a minimum of 3 to 4 sources.
construction systems and materials clearly dimensioned ii. Contact details of vendors/suppliers are current.
to show: Please note that it is much preferable to engage local
suppliers / vendors
i. Foundation and below grade construction;
ii. Typical wall construction; f) The drawings to be fully dimensioned,
iii. Abutting floor systems;
iv. Window type and location; g) Cross-references indicating all finishes and equipments
v. Exterior finishes, insulation and interior finishes; into drawings,
vi. Mechanical penetration and block outs;
h) Prepare final draft of particular conditions of contract,
vii. Parapet and roof construction;
specifications, and schedules. The specifications shall
viii. Key and interface all construction to elevations and
be adequate to define the types and quality of
floor plans.
construction, specific materials, and the quality of
typical interior finishes, types of materials and sources
rr) Large scale details (scale as required) for major clarifying
including the implications for maintenance, repair, and
plan details, keyed to floor plans for:
replacement to enable The Company to better
i. Window types, sill, mullions, jams and head details, understand their application to the project. Items of
glazing type and venting; major equipment shall be scheduled and defined in
ii. Hollow metal; outline form in the specifications,
iii. Frame type;
i) Options for project procurement and recommendations
iv. Metal and glass walls;
on the proposed option.
v. A special detail for surface trims and finishes.
j) Drawings
ss) Ground floor plans for all floors indicating flooring,
materials, kinds and types of patterns at scale 1:100/ i. List of areas requiring Interior Design Treatment
1:50; ii. General notes
iii. List of drawings
tt) Detailed elevations and sections at scale 1:50 for interior iv. Partition layout- scale 1:100
spaces interfaced and cross referenced floor and v. Furniture layout- scale 1:100
reflected ceiling indicating suspended ceiling lines, floor vi. Flooring layout- scale 1:100
elevation, wall treatment and materials, pertinent notes vii. Wall Finishes layout - scale 1:100
and dimensions; viii. Ceiling layout - coordinated with MEP
ix. Lighting Layout- scale 1:100- with circuiting
uu) Reflected ceiling plans for all floors at scale 1:100
coordinated with MEP,
indicating: lighting layout, softies, coves, furring‘s,
x. Lighting Circuiting- scale 1:100
skylights (if any), ceiling materials, acoustical treatment,
xi. Small Power Layout - scale 1:100
and relationship with partitions, interface with window
xii. Equipment layouts such as Kitchens, pantries,
details, sprinklers, access panels and exposed structure;
washrooms, lockers & Changing Rooms, Counters &
vv) Schedules: i. Door Schedule woodwork scale 1:50
ii. Window Schedule xiii. Interior Elevations and sections of all areas /Details
iii. Hardware Schedule & finishes showing location of all MEP fittings &
iv. Room Finish Schedule accessories - scale 1:50
xiv. Joinery/Millwork, Plans, Sections, Details
xvi. Interior Window Schedule- scale 1:50
xvii. General details- coordination between different
surfaces / materials. Scale 1:2 and 1:1
The interior design should incorporate all of the

following items and include schedules when necessary.
Cross disciplinary coordination is required.
Version 2.0.3 180 of 224

MASDAR
(Note: All documents need to be supported with technical m) Particular conditions (if any);
specifications & sustainable material evaluation with predicted
carbon footprint calculation.) Mechanical services (plumbing and fire
protection)
a) AV equipments,
a) Plans at scale 1:100 for all floors to indicate:
b) CCTV- Security and surveillance systems,
i. Fire alarm and smoke zones location of building water
c) Ironmongery schedule including access control,
supply;
d) FF&E, including fixed and loose furniture ii. Interior sprinkler supply lines;
iii. Standpipes;
e) Soft finishes iv. Fire extinguisher cabinets;
v. Exit paths from each zone;
f) Sanitary ware equipments, vi. Distances to the stair;
vii. The occupancy of each area;
g) Acoustic treatments,
viii. Fire proofing of structural members.
h) Kitchen Equipments to include wet, dry and cold stores
for all food and beverage facilities, b) Final plans at same scale as architectural to indicate:
i) Gymnasium equipment (if applicable), c) Types, features, age reliability, capacity, zoning,
j) Home automation system, devices and circuits and auxiliary function for fire alarm
system;
k) Curtain rail (automatic or manual),
d) Coordinated floor plans and site layout by system at
l) Graphics/Signage, same scale as architecture showing single line
m) Interior doors, glazed screens, partitions, access panels, distribution system; locating major equipment and size
fire hose cabinets, etc. details and schedules, clearance requirements; shafts (dimension chases;
mechanical rooms and required wall /floor penetrations
n) Hard Finishes Schedule, and block outs);
o) Retail Design Consultant‘s details regarding outlets, e) Riser diagram for fire alarm system indicating
interconnection with paging and communication
p) Recreation/Aquatic Design of Pools, systems;
q) Stairs and handrails, f) Details to include:
r) Lighting both architectural and decorative, and i. Door and window schedule indicating fire rating and
whether fire rated glazing (in coordination with
s) Accessories. architecture);
ii. Interconnection of elevator controls with fire alarm
Structural system;
iii. Interconnection with kitchen fire extinguishing and
a) General Notes fire pump system to the fire alarms system (if any);
iv. Reference note to HVAC drawings that indicate
b) Schedules interconnection HVAC system (dampers, fans) with duct
c) Final design calculation for foundation and superstructure; smoke detectors and / or fire alarm system;
v. Technical specifications that include all necessary
d) Foundation plan @ scale 1:50 / 1:100; contractual and technical information to assure
adherence to the contract documents specifications
e) Pile arrangement layout sheet (if required) @ scale shall follow the CSI master format;
1:50/1:100 – 90% ready for permitting and construction vi. Itemized BOQ with measure per each item;
vii. Particular conditions (if any);
f) Foundation details including (1) reinforcement details and viii. Detailed cost estimates.
sections and (2) reinforced concrete walls and core
starter details at scale 1:25 - ready for tender, with Fire implementation strategy
building utility structures – pits, tanks, etc
g) Coordinated floor plans showing column axes and a) Plans at scale 1:100 for all floors to indicate:
dimension (including column reinforcement details) @
i. Fire alarm and smoke zones location of building water
scale 1:100 /1:50;
supply;
h) Typical floor framing plans, including sizing of beams, ii. Interior sprinkler supply lines;
slab openings, thickness and depression of block outs @ iii. Standpipes;
scale 1:100/1:50; iv. Fire extinguisher cabinets;
v. Exit paths from each zone;
i) Non typical framing scheme were required @ scale 1:25; vi. Distances to the stair;
vii. The occupancy of each area;
j) Details of major unique conditions (core, stairs, ramp, viii. Fire proofing of structural members where
basement reinforced concrete wall) @ scale 1:25; applicable.
k) Details indicating accommodation with
b) Final plans at same scale as architectural to indicate:
mechanical/electrical at area of major interface @ 1:25;
c) Types, features, age reliability, capacity, zoning,
l) Technical specifications that include all necessary
contractual and technical information to assure adherence
devices and circuits and auxiliary function for fire alarm
to the contract documents specifications shall follow the
system;
CSI master format;
Version 2.0.3 181 of 224

MASDAR
d) Coordinated floor plans and site layout by system at same i. Coordinated floor plans and site layout by system at
scale as architecture showing single line distribution same scale as architecture showing single line
system; locating major equipment and size clearance distribution system; locating major equipment and size
requirements; shafts (dimension chases; mechanical clearance requirements; shafts (dimension chases;
rooms and required wall /floor penetrations and block mechanical rooms and required wall /floor penetrations
outs); and block outs);
ii. Provide updated @ scale 1:50; typical mechanical
e) Riser diagram for fire alarm system indicating equipment room plans with resolution of review
interconnection with paging and communication systems; comments made during previous submission;
iii. Final riser diagrams for air handling systems and
f) Details to include:
hydraulic systems by providing quantities and sizes to
i. Door and window schedule indicating fire rating and reflect the latest engineering calculations;
whether fire rated glazing (in coordination with iv. Results for sounds/acoustic analysis to ensure that
architecture); noise generated by the air handling units and the fans;
ii. Interconnection of elevator controls with fire alarm v. Schematic control diagrams for each type of typical
system; air and hydraulic system used for development in
iii. Interconnection with kitchen fire extinguishing and fire previous submission;
pump system to the fire alarms system (if any); vi. Equipment schedules upon which design is based
iv. Reference note to HVAC drawings that indicate including pumps, fans, filters, coils, radiators, diffusers,
interconnection HVAC system (dampers, fans) with duct chillers, attenuators, cooling towers, air handling units,
smoke detectors and / or fire alarm system; fan coil units, VAV boxes etc.
v. Technical specifications that include all necessary vii. Schedules of equipment indicating capacity and
contractual and technical information to assure adherence performance characteristics. All details and section
to the contract documents specifications shall follow the requirements for a comprehensive presentation of the
CSI master format; design and installation requirements including
vi. Itemized BOQ with measure per each item; coordination with architectural, structural and electrical
vii. Particular conditions (if any); features;
viii. Detailed cost estimates. viii. The specifications including all necessary
contractual and technical information to assure
Plumbing adherence to the contract documents;
ix. Written description of the sequence of operation on
the floor plans explaining clearly the function and role of
a) Floor Plans indicating plumbing requirements, sizes and
each control device and describe the safety/alarms and
distribution, including hot and cold water distribution and
normal /fire operating controls of each system.
drainage systems collection systems, scale 1:100;
x. Geothermal system plan, layout, riser diagram
b) Floor Plans of toilets and bathrooms, indicating location of ,sequence of operation, control schematic, specification,
fixtures, piping, valves and connections, scale 1:50; manufacturer, supplier list etc
c) Plans indicating size and location of major equipment and Power and lighting
clearances required for maintenance, shafts, and
equipment rooms, including water storage requirements; Final electrical lighting and power layout plans of
different floors in at scale 1:100 including:
d) Riser and Distribution Diagrams, for domestic hot and
cold water supplies and drainage collection systems, a) Layout plans of lighting systems;
showing Schematic pipe sizes, flow quantities, control
systems; b) Layout plans of power systems;
e) Visual impact of system elements, where required (e.g. c) Single line diagrams for mains and emergency supplies;
roof mounted equipment);
d) Layout plans, sections and details of electrical
f) Calculations and assumptions per final design; equipment room and risers at scale 1:50 & 1:25;
Mechanical systems e) Layout plan and details of earthing and lighting

protection systems;
a) Air-conditioning system
f) Primary distribution including duct lines and manholes,
− HVAC floor plans @ scale 1:100 for typical areas cable details, switchgear, physical location and layout,
showing core layouts (unit substation plan layouts), and
equipment units;
b) Main supply, return and exhaust air ductwork with sizes
g) Secondary distribution including switchboard and or
based on the updated calculations;
switch gear floor plans and layouts, core area, and
c) Cross sections indicating clearances between piping, duct utility closet, power and lighting panel locations, motor
work, sprinklers, bus duct, lighting fixtures, diffusers/grills control centre layouts and locations, bus duct routing
etc. indicating coordination with structural, architectural and rating, space allocated for feeder cables and
and electrical features; propped routing, and equipment type;
d) Plans and sections @ scale 1:50 to indicate individual h) Lighting including fixtures layout for each area (specify
room air distribution and temperature control arrangement type of fixtures used) site lighting, typical switching,
for a representative sample of typical spaces, and special decorative and architectural lighting and lighting details;
spaces according to the nature of the project @ scale
i) Calculation sheet of the following:
1:50 showing routing and sizing of all piping and duct
works; i. Voltage drop on main and sub feeders;
ii. Load of lighting, power, mechanical, HVAC, etc.
e) Coordinated sections (typical) including all services (MEP
iii. Short circuit calculations;
& Fire)
iv. Technical specifications for different electrical
systems, material and equipment;
Version 2.0.3 182 of 224

MASDAR
v. Itemized BOQ with measures per each; Intelligent building management and control
vi. Cost estimate; system
Telephone systems, access control, building a) Security (CCTV) and access control systems
management system and elevators b) Emergency Generators
c) Lighting Control System
a) Final low current system layout plans of different floors at d) HVAC system (Chilled Water pumps, CHW
scale 1:100 including: Pressurization Units, FCU. AHU, Ventilation and Extract
Fans, Fresh Air Handling Units …etc).
i. telephone and paging system; e) Water Supply System
ii. data network system (showing the data network f) Irrigation System
passive components); g) Fire Fighting system (Monitoring only. Control shall be
iii. access control ICT Systems and time keeping system; through fire Control Panel).
iv. CCTV system; h) Leak detection system in the chilled water pipes
v. audio / visual systems for meeting room. (Alarm).
i) Automatic chemical treatment system of chilled water
b) Final layout plan of elevators indicating arrangement, (Alarm).
risers, details of shafts and machine rooms and schedule j) Motorized Damper / Fire Damper
of elevators; k) Water Pump Sets (Domestic + filtration unit)
l) Water Tanks
c) General arrangement layout plans and details of low
m) Water filtration system
current systems control rooms indicating arrangement of
n) Drainage Pumps (Sewage + Storm water)
different equipments such as:
o) Fire Pump set
i. PABX, consoles, PC, MDF, IDF etc. p) Generator Sets
ii. Data network patch panels, risers etc. q) Lifts
iii. Access control computer, printer etc. r) LV Main Switchgear
iv. CCTV monitors, VCRs, Printers etc. s) Emergency Lighting System
t) Fire Alarm and Clear Agent system
d) Low current systems riser diagrams including systems u) Access Control System
chart and distribution in each floor; v) CATV System
w) Amenities, Gym sports and Steam room equipments
e) Telecom/Voice/Data systems, including IT Design x) Vertical transportation system.
systems; y) Coordinated floor plans at same scale as architecture
showing single line distribution system; locating major
f) Security and surveillance systems; equipment and size clearance requirements; shafts
(dimension chases; mechanical rooms and required
g) ICT Systems.
wall floor penetrations and block outs);
h) General and specific installation details of low current z) Plans of special floors (basement, lobby, technical
systems equipments, issuers, raceways and interfacing gallery if required showing equipment locations,
with other systems such as elevators, HVAC, fire pumps, clearance requirements etc.
access control etc. aa) Building Management and Control System riser
diagrams etc.
i). Technical specifications for different low current systems bb) Standard general miscellaneous details for typical
and elevators; installations of BMCS;
cc) Complete material and equipment specifications for all
j). Particular conditions if any; Building Management and control System Technical
specifications including all necessary contractual and
k). Itemized BOQ with measures per each item.
technical information to assure adherence to the
contract documents. Specifications shall follow the CSI
Specialty systems format and be coordinated with the Chief Specifications
Writer;
Design, report, drawings and specification relating to specialty
system may need to incorporated into the above mentioned
Tender packages relating to, but not limited to:- Presentation and other materials
a) Vertical transportation and elevators; Tenant Drawing Package for each individual tenant
space to be supplied to the tenant for use in the
b) Retail Design Consultant‘s details regarding outlets; development of their fit-out drawings. All drawings
should be supplied in PDF format (A3 or A4) and as a
c) Food & beverage Design Consultants regarding CAD file.
restaurant and kitchen provision and layout;
a) Plan, with overall running dimensions, indicating
d) Hospitality Design Consultant on hotel design;
incoming service locations and their height above the
e) Environmental optimization / building material; slab level and structural features eg lift pits, soft spots,
reinforced areas.
f) Telecom/Voice/Data systems, including IT systems;
b) External elevations, with overall running dimensions, of
g) Security and surveillance systems; all walls/shop fronts relevant to the demised unit.
h) Graphics/Signage – Outdoors and Indoor; c) Reflected ceiling plan, indicating all downstands and
their underside level and suspended landlords service
i) Recreation/Aquatic Design of Pools; locations and their levels and type.
j) Solid Waste d) Cross section through unit, usually to pass through the
main shop front, with overall running dimensions.
k) Lighting/building maintenance.
l) ICT Systems.
Version 2.0.3 183 of 224

MASDAR
e) No spec sheet is required. General finishes and/or

materials should be noted on the drawing. A key location
plan showing the unit position is preferred on the plan
drawing.
f) No signage zones or any other design intent/controls

should be indicated on the drawings.
g) Appropriate scales would be 1:50/1:20 dependent on unit

size.
Rendered plans, unit plans and elevations adequate for

marketing purposes, as required to represent significant
design modifications
Tender / construction packages
Full Package ―Issue for Construction‖
A1.6 TENDER STAGE

Preparation and collation of tender documentation in sufficient
detail to enable a tender or tenders to be obtained for the
construction of the Project.
The Design Consultant shall revise ―Tender Documents‖, to

incorporate changes arising from value engineering,
clarifications identified during the tender, and/or tenderer
proposed alternates, and reissue the affected Tender
Documents.
Version 2.0.3 184 of 224

Appendix 2: Model elements by project phase
MASDAR
Appendix 2
Model elements by project phase
This appendix shows and information level matrix that should be completed by the project team at
the start of as project.
It would be used to list the party responsible for creating each main element in a model, and
define the point by which they should be produced.
Table A2.1 should be read in conjunction with chapter 4 of this document (Element Coding
Standard) which describes the additional requirements for application-specific and Masdar-
defined data.
Version 2.0.3 185 of 224

MASDAR
Table A2.1 Responsibilities for model delivery by information level
Fill in each square to denote the required information level at each project stage, and the party
Schematic design
responsible.
Concept design
Detailed design
Construction
Construction
For example, the code A3 could represent information level 3 created by the architect
documents
Pre-design
Handover
Tender
A Substructure A10 Foundations A1010 Standard foundations
A1020 Special foundations
A1030 Slab on grade
A20 Basement construction A2010 Basement excavation
A2020 Basement walls
B Shell B10 Superstructure B1010 Floor construction
B1020 Roof construction
B20 Exterior B2010 Exterior walls
enclosure B2020 Exterior Windows
B30 Roofing B2030 Exterior doors
B3010 Roof covering
B3020 Roof openings
C Interiors C10 Interior C1010 Partitions
construction
C1020 Interior doors
C1030 Fittings
C20 Stairs C2010 Stair construction
C2020 Stair finishes
C30 Interior C3010 Wall finishes
finishes C3020 Floor finishes
C3030 Ceiling finishes
D Services D10 Conveying D1010 Elevators & lifts
D1020 Escalators & moving walks
D1090 Other conveying systems
D20 Plumbing D2010 Plumbing fixtures
D2020 Domestic water distribution
D2030 Sanitary waste
D2040 Rain water drainage
D2090 Other plumbing systems
D30 HVAC D3010 Energy supply
D3020 Heat generating systems
D3030 Cooling generating systems
D3040 Distribution systems
D3050 Terminal & package units
D3060 Controls & instrumentation
D3070 Systems testing & balancing
D3090 Other HVAC systems & equipment
D40 Fire protection D4010 Sprinklers
D4020 Standpipes
D4030 Fire protection specialties
D4090 Other fire protection systems
D50 Electrical D5010 Electrical service & distribution
D5020 Lighting and branch wiring
D5030 Communications & security
D5090 Other electrical systems
Version 2.0.3 186 of 224

MASDAR
Table A2.1 (continued) Responsibilities for model delivery by information level
Fill in each square to denote the required information level at each project stage, and the party
Schematic design
Concept design
Detailed design
responsible.
Construction
Construction
documents
Pre-design
Handover
For example, the code A3 could represent information level 3 created by the architect
Tender
E Equipment E10 Equipment E1010 Commercial equipment
and
furnishings E1020 Institutional equipment
E1030 Vehicular equipment
E1090 Other equipment
E20 Furnishings E2010 Fixed furnishings
E2020 Movable furnishings
F Special F10 Special F1010 Special structures

construction construction
and F1020 Integrated construction
demolition
F1030 Special construction systems
F1040 Special facilities
F1050 Special controls and instrumentation
F20 Selective building F2010 Building elements demolition

demolition
F2020 Hazardous components abatement
G Site building G10 Site G1010 Site clearing

work preparation
G1020 Site demolition and relocations
G1030 Site earthwork
G1040 Hazardous waste remediation
G20 Site G2010 Roadways

improvements
G2020 Parking lots
G2030 Pedestrian paving
G2040 Site development
G2050 Landscaping
G30 Site mechanical G3010 Water supply

utilities
G3020 Sanitary sewer
G3030 Storm sewer
G3040 Heating distribution
G3050 Cooling distribution
G3060 Fuel distribution
G3090 Other site mechanical utilities
G40 Site electrical G4010 Electrical distribution

utilities
G4020 Site lighting
G4030 Site communications & security
G4090 Other site electrical utilities
G9010 Service and pedestrian tunnels
G90 Other site construction G9090 Other site systems & equipment
Version 2.0.3 187 of 224

Appendix 3: UniFormat classification system
MASDAR
Appendix 3
UniFormat classification system
This appendix describes the UniFormat classification system for building elements and building-
related site work.
On Masdar projects UniFormat will be used to classify all modelling and drawing features, in order
to enable a fully standardised and integrated data set across all project team participants.
UniFormat notations for elements consist of a single capital letter followed by numerical digits.
The notation is hierarchical. For example, D2010 and D2020 are sub-classes of D20, which in
turn is a sub-class of D.
The parent-child relationship allows an element to be classified with additional degrees of

granularity to suit project requirements.
In practice, the degree of granularity is dependent on what level of detail can be exposed at any
given time in the project. For example, the definition of an element at the conceptual design
stage would generally be at a high level of notation because of the generic nature of the design;
in later design stages the availability of additional information may dictate that extra granularity
would be necessary. Therefore, the Uniclass classification system is fully expandable to meet
progressive project requirements.
Reference should always be made to the latest UniFormat document.
Bentley BIM tools use a system of ‘families and parts’ which is based on the UniFormat
classification system and Masdar’s project dataset is structured accordingly for ease of
use.
Version 2.0.3 189 of 224

MASDAR
Table A3.1 Classification for building elements
A Substructure A10 Foundations A1010 Standard foundations

A1020 Special foundations
A1030 Slab on grade
A20 Basement construction A2010 Basement excavation
A2020 Basement walls
B Shell B10 Super structure B1010 Floor construction
B1020 Roof construction
B20 Exterior enclosure B2010 Exterior walls
B2020 Exterior Windows
B2030 Exterior doors
B30 Roofing B3010 Roof coverings
B3020 Roof openings
C Interiors C10 Interior construction C1010 Partitions
C1020 Interior doors
C1030 Fittings
C20 Stairs C2010 Stair construction
C2020 Stair finishes
C30 Interior finishes C3010 Wall finishes
C3020 Floor finishes
C3030 Ceiling finishes
D Services D10 Conveying D1010 Elevators & lifts
D1020 Escalators & moving walks
D1090 Other conveying systems
D20 Plumbing D2010 Plumbing fixtures
D2020 Domestic water distribution
D2030 Sanitary waste
D2040 Rain water drainage
D2090 Other plumbing systems
D30 HVAC D3010 Energy supply
D3020 Heat generating systems
D3030 Cooling generating systems
D3040 Distribution systems
D3050 Terminal & package units
D3060 Controls & instrumentation
D3070 Systems testing & balancing
D3090 Other HVAC systems & equipment
D40 Fire protection D4010 Sprinklers
D4020 Standpipes
D4030 Fire protection specialties
D4090 Other fire protection systems
D50 Electrical D5010 Electrical service & distribution
D5020 Lighting and branch wiring
D5030 Communications & security
D5090 Other electrical systems
E Equipment and furnishings E10 Equipment E1010 Commercial equipment
E1020 Institutional equipment
E1030 Vehicular equipment
E1090 Other equipment
E20 Furnishings E2010 Fixed furnishings
E2020 Movable furnishings
F Special construction and F10 Special construction F1010 Special structures
demolition F1020 Integrated construction
F1030 Special construction systems
F1040 Special facilities
F1050 Special controls and instrumentation
F20 Selective building F2010 Building elements demolition
demolition F2020 Hazardous components abatement
Version 2.0.3 190 of 224

MASDAR
Table A3.2 Classification for building-related site work
G Site building work G10 Site preparation G1010 Site clearing

G1020 Site demolition and relocations
G1030 Site earthwork
G1040 Hazardous waste remediation
G20 Site improvements G2010 Roadways
G2020 Parking lots
G2030 Pedestrian paving
G2040 Site development
G2050 Landscaping
G30 Site mechanical utilities G3010 Water supply
G3020 Sanitary sewer
G3030 Storm sewer
G3040 Heating distribution
G3050 Cooling distribution
G3060 Fuel distribution
G3090 Other site mechanical utilities
G40 Site electrical utilities G4010 Electrical distribution
G4020 Site lighting
G4030 Site communications & security
G4090 Other site electrical utilities
G90 Other site construction G9010 Service and pedestrian tunnels
G9090 Other site systems & equipment
Version 2.0.3 191 of 224

Appendix 4: Application-specific data
MASDAR
Appendix 4
Application-specific data
This appendix shows the application-specific data that would typically be attributed to 3D objects
in building information models when using the relevant Bentley BIM application. Data should be
entered by the originator (owner) of the design file.
The data table should be defined at the start of each project and agreed by all parties before
commencing design work.
Version 2.0.3 193 of 224

MASDAR
Table A4.1 Architectural application-specific object data
Element Data required Element Data required

Roll-up door hoods w/head - Part identifier Partial walls - Part identifier
- Door number - Height
- Width - Area
- Height
- Frame depth
- Leaf thickness
- Undercut
- Material (frame/leaf)
- Hardware set
Spaces - Part identifier Roof drain overflow - Part identifier
- Room number nozzles/spill outs - Material
- Area
- Height
- Finishes
Doors/door swings - Part identifier Floor access hatches - Part identifier
- Door number - Area
- Width - Material
- Height
- Frame depth
- Leaf thickness
- Undercut
- Material (frame/leaf)
- Hardware set
Windows - Part identifier Skylights - Skylight number
- Window number - Part identifier
- Width - Area
- Height - Frame depth
- Frame depth - Material & finish
- Material - Glass type
- Finish
- Manufacturer
- Model number
- Glass type
Louvers - Part identifier Interior soffits - Part identifier
- Louver number
- Width
- Height
- Frame depth
- Material
- Finish
- Manufacturer
- Model number
Roof hatches - Part identifier Planters and similar - Part identifier
- Hatch type elements
- Area (length & width)
- Material & finish
CMU/block module/brick - Part identifier Furniture and appliances - Part identifier
veneer - Material
- Width
- Height
- Area
- Volume
Sound panel acoustical tile - Part identifier Tile or other flooring - Part identifier
- Area - Area
Suspended ceilings - Part identifier Exterior guard post - Part identifier
- Area
Penetrations larger than - Part identifier Lockers and fixed benches - Part identifier
minimum size (300 mm) - Area
- Volume
Version 2.0.3 194 of 224

MASDAR

Roof drains - Part identifier Wall access hatches - Part identifier
- Area
- Material
Fixtures (toilets, sinks, etc.) - Part identifier for fixture Stair nosing - Part identifier
type - Length
- Material
Cabinets, lab casework - Part identifier for fixture Exterior soffits - Part identifier
type - Area
Fascia - Part identifier Gutters - Part identifier
- Area (cross section)
- Linear length
Roof curbs/equipment - Part identifier Flashing/coping - Part identifier
supports - Volume - Linear length
Concrete aprons - Part identifier Door & window hardware N/a
- Volume
- Area
Interior guard post - Part identifier Flat roof slopes N/a
Hatches - Part identifier Scupper/conductor heads N/a
- Area
- Material
Drinking fountains - Part identifier Control joints less than N/a
minimum size (50 mm)
reveals
Toilet partitions - Part identifier Toilet and bath accessories N/a
- Linear length
- Area
Partition walls -- must show - Part identifier Veneer ledger angles N/a
accurate height - Height
- Area of assembly
- List of components
Version 2.0.3 195 of 224

MASDAR
Table A4.2 Structural application-specific object data

Handrail/safety rail/guard - Part identifier All equipment pads (HVAC - Part identifier
rail - Linear length (of equip included) - Area
assembly) - Volume
- Parametric spacing
between vertical and
horizontal members
Stairs - Part identifier Containment curbs - Part identifier
- Component lengths - Area
- Area of treads - Area (cross section)
- Rise-run parametric detail - Volume
Walkways - Part identifier Sumps/trenches - Part identifier
- Area - Linear length
- Component lengths - Area
- Volume
Ladders - Part identifier Grout lines larger than - Part identifier
- Height minimum size (300 mm) - Area
- Distance between rungs - Volume
Actual grating - Part identifier Roof deck/floor deck - Part identifier
- Area - Material
- Area
- Depth
- Volume
All major steel framing - Part identifier Depressed slab for tile - Part identifier
- Type of member - Area
- Section name - Volume
- Mark
- Material
- Type
- Grade
All penetrations greater - Area Ledger angles N/a
than minimum (300 mm) - Volume
Hatch openings - Area Rebar N/a
- Volume
All concrete (slab, walls, - Part identifier Bolts/anchors N/a
footers, beams, etc) - Material
- Width
- Height
- Area
- Volume
Pipe encasement (on - Part identifier Floor/roof slopes N/a
separate level) - Material
- Volume
Monorails/hoist runway - Part identifier
beams, bridge crane - Material
- Component lengths
- Type of member
- Section name
- Mark
- Material
- Type
- Grade
Version 2.0.3 196 of 224

MASDAR
Table A4.3 Mechanical application-specific object data

All equipment - Part identifier Motorized dampers - Part identifier
- Equipment number w/actuators - Damper number
- Equipment type
All piping larger than - Part identifier Thermostats - Part identifier
minimum size (75 mm) - Flow stream - Thermostat number
- Diameter
- Material
- Length
Process drains - Part identifier Duct supports - Part identifier
- Material - Area (cross section)
- Volume
Control panels - Part identifier Plumbing backflow - Part identifier
- Panel number preventers
Pipe supports and hangers - Part identifier Any tanks - Part identifier
- Material - Volume
- Volume - Area
Hose bibs and hose racks - Part identifier Roof drain pipes - Part identifier
- Material
- Diameter
- Length
Valve/gate operators - Part identifier Floor drain pipes - Part identifier
- Valve/gate number - Material
- Diameter
- Length
Instrumentation - panels, - Part identifier Water heater - Part identifier
hand switches - Panel number - Heater number
Piping smaller than N/a Safety showers - Part identifier
minimum size (75 mm) - Shower number
unless required showing
design intent
All ducts - Part identifier Fire pipe riser - Part identifier
- Flow stream - Material
- Diameter - Diameter
- Area (cross section) - Area (cross section)
- Material - Length
- Length
- Insulation
- Lining
- Air flow properties
- Status
- Pressure
- Flow rate
- Flow velocity
- Pressure drop
HVAC panels - Part identifier Fire sprinkler heads/piping N/a
- Panel number
Version 2.0.3 197 of 224

MASDAR
Table A4.4 Electrical application-specific object data

Electrical cabinets - Part identifier Duct banks - Part identifier
- Cabinet number - Material
- Length
Light fixtures - Part identifier Switchgear - Part identifier
- Fixture particulars - Panel number
- Type
- Model
- Material
- Bulb requirements
Conduits larger than - Part identifier Control panels - Part identifier
minimum size (75 mm). - Material - Panel number
- Diameter
- Length
Version 2.0.3 198 of 224

Appendix 5: Masdar-specified tagged data
MASDAR
Appendix 5
Masdar-specified tagged data
This appendix shows the Masdar-defined data that should be tagged to 3D objects in building
information models. Data should be entered by the originator (owner) of the design file.
The data table should be defined at the start of each project and agreed by all parties before
commencing design work. The example shown is for illustration only.
Version 2.0.3 199 of 224

Appendix 5: Masdar-specified tagged data
MASDAR
Table A5.1 Attributes for Masdar-specified tagged data
Project stages
Schematic design
Concept design
Detailed design
Construction
Construction
documents
Pre-design
Handover
Tender
Asset element Description Field name Data example
1 Asset Code A_CODE CHW-PUMP-04 D
2 Asset Description A_DESCRIPTION Chilled water pump D
3 Asset Product code A_PRODUCT_CODE P-27-CW C
4 Asset Manufacturer A_MANUFACTURER Grundfoss C
5 Asset Tag A_TAG Circulating pump D
6 Asset Model type A_MODEL_TYPE 6-2/5 D
7 Asset Serial number A_SERIAL NUMBER 1000035648 C
8 Asset System A_SYSTEM Media suite cooling system D
9 Supplier Name S_NAME GB Mechanical Services D C
10 Location Description L_DESCRIPTION Conference suite 4
11 Location Floor L_FLOOR 1 D
12 Location Room number L_ROOM_NUMBER 1.00.004 D
13 Building group Site B_SITE Masdar City D
14 Building group Building B_BUILDING MIST D
Codes for last eight columns (responsible party for creating the data): D-designer, C-contractor. Additional codes can be used as necessary.
Data to be entered only by owner of file.
Version 2.0.3 200 of 224

Appendix 6: Masdar-specified external data
MASDAR
Appendix 6
Masdar-specified external data
This appendix provides a template for listing Masdar-defined data that will be stored outside of
the 3D model (in a spreadsheet or database for example). At the start of each project the
participants would agree the data to be captured and assign responsibility for its creation by
project phase.
Masdar attribute requirements are being defined by Masdar at the time of writing.
Version 2.0.3 201 of 224

Appendix 6: Masdar-specified external data
MASDAR
Table A6.1 Attributes for Masdar–specified object data (stored outside the virtual 3D model)
Project stages
Schematic design
Concept design
Detailed design
Construction
Construction
documents
Pre-design
Handover
Tender
Asset element Description Field name Data example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Codes for last eight columns (responsible party for creating the data): D-designer, M-Masdar, C-contractor. Additional codes can be used as necessary.
Data to be entered by anyone with appropriate permissions to the data source.
Version 2.0.3 202 of 224

Appendix 7: Standard project files for Bentley software
MASDAR
Appendix 7
Standard project files for Bentley software
This appendix lists the standard project files that shall be used for any CAD files produced for
Masdar projects. These will be supplied to project team members in an appropriate format and
they must not be modified in any way.
Version 2.0.3 203 of 224

MASDAR
Table A7.1 Seed files
Name Description Location
Masdar3DSeed.dgn Design model seed file <drive>:\MasdarWorkSpace\System\Seed
Masdar3DSTRSeed.dgn Structural model seed file <drive>:\MasdarWorkSpace\System\Seed
Masdar3DSeed-civil.DGN Civil engineering seed file <drive>:\MasdarWorkSpace\System\Seed
MasdarA0-LandscapeSheet1-1Seed.dgn A0 Landscape 1:1 Sheet model seed file <drive>:\MasdarWorkSpace\System\Seed
MasdarA0-PortraitSheet1-1Seed.dgn A0 Portrait 1:1 Sheet model seed file <drive>:\MasdarWorkSpace\System\Seed
Table A7.2 Drawing borders
MasdarA0_Landscape.dgn A0 Landscape drawing borders <drive>:\MasdarWorkSpace\System\Borders
MasdarA0_Portrait.dgn A0 Portrait drawing borders <drive>:\MasdarWorkSpace\System\Borders
Table A7.3 Block folders/cell libraries
Architecture Cells Directory of architectural cell libraries <drive>:\MasdarWorkSpace\TriForma\MasdarArchDataset\cell
Electrical Cells Directory of electrical cell libraries <drive>:\MasdarWorkSpace\TriForma\MasdarElectricalDataset\cell
HVAC Cells Directory of HVAC cell libraries <drive>:\MasdarWorkSpace\TriForma\MasdarHvacDataset\cell
Structural Cells Directory of structural cell libraries <drive>:\MasdarWorkSpace\TriForma\MasdarStructuralDataset \cell
General cells For ANSI standards etc <drive>:\MasdarWorkSpace\System\Cell
Version 2.0.3 204 of 224

MASDAR
Table A7.4 Layers
Architecture Layers Directory of architectural layer libraries <drive>:\MasdarProjects\MasdarArchProject\dgnlib
Electrical Layers Directory of electrical layer libraries <drive>:\MasdarProjects\MasdarElectricalProject\dgnlib
HVAC Layers Directory of HVAC layer libraries <drive>:\MasdarProjects\MasdarHvacProject\dgnlib
Structural Layers Directory of structural layer libraries <drive>:\MasdarProjects\MasdarStructuralProject\dgnlib
Civils layers Directory of civils layer libraries
General Layers For other disciplines etc <drive>:\MasdarWorkSpace\System\dgnlib
Tabled A7.5 Colour table
MasdarColor.tbl Default Masdar colour table <drive>:\MasdarWorkSpace\System\Data
Table A7.6 Plot Drivers
Masdar-general-A1.PLTCFG Plot driver for use with all A1 prints and plots <drive>:\MasdarWorkSpace\System\Plotdrv
Masdar-general-A1.PLTCFG Plot driver when printing directly to PDF at A1 <drive>:\MasdarWorkSpace\System\Plotdrv

size

size

size
Table A7.7 Datasets
MasdarArchDataset Default Architectural Dataset <drive>:\ MasdarWorkSpace\TriForma
MasdarElectricalDataset Default Electrical Dataset <drive>:\ MasdarWorkSpace\TriForma
MasdarHvacDataset Default HVAC Dataset <drive>:\ MasdarWorkSpace\TriForma
MasdarStructuralDataset Default Structural Dataset <drive>:\ MasdarWorkSpace\TriForma
MasdarTfDataset For Structural components <drive>:\ MasdarWorkSpace\TriForma
Version 2.0.3 205 of 224

Appendix 8: Masdar standard drawing symbols
MASDAR
Appendix 8
Masdar standard drawing symbols
This appendix lists standard Masdar drawing symbols.
Version 2.0.3 207 of 224

MASDAR
A8.1 Overview
The use of standard symbols helps to ensure clear and concise communication between the
different users of drawings. Symbols are classified in three categories;
1. Reference symbols which are used for cross references and annotation on a drawing (refer
to section 2 of this document)
2. Material indications which are used to graphically indicate the material of an object (for
example, hatching and patterning)
3. Discipline specific symbols used to represent objects not fully illustrated on the drawing.
Where material indications or industry specific symbols are used which are not approved by
Masdar then the symbol shall be defined by either:
- reference on the drawing to the appropriate NCS standard

- the symbol being clearly defined in a legend on the drawing upon which the symbol appears
- reference to a separate discipline-specific drawing clearly showing the symbol and its
meaning.
A8.2 Annotation
The Windows True Type font Arial shall be used for all annotations. The text styles in table A8.1
will be set up within the Masdar dataset.
Table A8.1 Masdar text styles
Text Style Description Font Colour Metric Plotted Height
STANDARD Notes and all common text needs Arial ByLevel 2.5 mm
SUBTITLE General Note and Detail Headers Arial ByLevel 3.5 mm
MAIN Title Blocks and to call out Objects Arial ByLevel 5.0 mm
TITLE Title Blocks and to call out Objects Arial ByLevel 7.0 mm
The following guidelines shall be followed when creating general or keyed notes on deliverable
drawings.
 Notes shall be located on the right side of the drawing.

 Use capital letters for all notes and titles.
 Keyed notes shall be used on plans.
 Do not use keyed notes on sections and details unless specified at the project level.
 Specification information shall not be duplicated by drawing notes, except where the
information facilitates interpretation of the drawings. When possible, refer to notes on other
drawings to avoid repetition.
The following guidelines shall be followed when creating general notes:
 Use text style ―Subtitle‖ for the title of general notes on a drawing. The title is not underlined,
and no symbol is used after the title.
Version 2.0.3 208 of 224

MASDAR
 Use text style ―Standard‖ for all notes.

 General notes are indicated with letters, not with numbers. The letter designation is separate
from the body of the note.
 Lines of general notes may consist of single entities of text or multi line text.
 If single entities/lines of text: Start 1st string at least a 6mm from border, Left justified note
letter, then gap of at least 3mm then start new left justified text string for body of note.
 If multi line text: all text objects are contained inside its boundary. Try to keep the same
spaces as above.
 No period is used after each note's letter.
 General notes are single spaced, and a double space is placed between each new note.
The following guidelines shall be followed when creating keyed notes:
 Keyed notes follow the same rules as general notes except they are indicated with a number
value instead of a letter value.
Figure A8.1 Annotation guidelines
Version 2.0.3 209 of 224

MASDAR
A8.3 Reference symbols

A8.3.1 Drawing sub title
When sub titles are required within the drawing sheet then they shall have a number, title, written
scale and scale bar, as detailed.
Figure A8.2 Drawing sub title
A8.3.2 Section callout
To be used for representing building sections.
Figure A8.3 Section callout
A8.3.3 Section callout option
To be used on short sections and where space restricts the use of the ‗Building Section Callout‘
as detailed in image below.
Figure A8.4 Short section callout
Version 2.0.3 210 of 224

MASDAR
A8.3.4 Detail section callout
To be used for representing detail section.
Figure A8.5 Detail section callout
A8.3.5 Elevation callout
To be used for representing an elevation.
Figure A8.6 Elevation callout
A8.3.6 Detail callout
To be used for indicating plan, elevation and section areas that are enlarged (larger plot scale)
and found elsewhere in the project set.
Figure A8.7 Detail callout
A8.3.7 Interior elevation callout
To be used for representing interior elevation.
Figure A8.8 Interior elevation callout
A8.3.8 Spot elevation
To be used for representing a spot elevation or work point.
Figure A8.9 Spot elevation callout
Version 2.0.3 211 of 224

MASDAR
A8.3.9 Floor transition
To be used for representing floor transitions.
Figure A8.10 Floor transition
A8.3.10 Break line
To be used to indicate a break line in the current drawing.
Figure A8.11 Break Line
A8.3.11 Coded notes
Coded notes shall be contained within a hexagon. Terminators shall be as appropriate: either a
filled arrow, filled circle, filled square or as detailed.
Figure A8.12 Coded notes
A8.3.12 Revision cloud
Revision clouds shall be placed around changes between revisions, with the revision note.
Figure A8.13 Revision cloud
Version 2.0.3 212 of 224

Appendix 9: Drawing border and title block
MASDAR
Appendix 9
Drawing border and title block
This appendix describes the standard Masdar drawing border and title block.
Version 2.0.3 213 of 224

MASDAR
A9.1 Overview
For any sheet size all borders will include the following: project information, client information,
drawing information, approval information, revision information, package information, and plot
information. This information will be included within the digital border files as tag sets within
MicroStation. Masdar provides a border file for A0, A1, A2, A3 and A4 in both landscape and
portrait sheet sizes. The following data will be entered into every border in every deliverable
drawing.
A9.2 Title block

A9.2.1 Plot information
This tag set contains printing information.
Figure A9.1 Screen shot for plot information tag set
Table A9.1 Plot information tag set
Name Editable if final Required Unique Access Visible
PlotDate No No No Edit Yes

PlotFileName No No No Edit Yes
PlotTime No No No Edit Yes
PlotUserName No No No Edit Yes
A9.2.2 Drawing information
This tag set contains information regarding content of the sheet.
Figure A9.2 Screen shot for drawing information tag set
Version 2.0.3 214 of 224

MASDAR
Table A9.2 Drawing information tag set
DesignedBy No No No Edit No
Discipline No Yes No Edit Yes
DrawnBy No Yes No Edit Yes
DrawnDate No Yes No Edit Yes
NameVariable No Yes No Edit Yes
Originator No Yes No Edit Yes
Sheet_Type No Yes No Edit Yes
Title1 No No No Edit Yes
Title2 No Yes No Edit Yes
Status No Yes No Edit Yes
Scale No Yes No Edit Yes
RevisionNumber No Yes No Edit Yes
A9.2.3 Package
This tag set contains information regarding the sheet contract number and seal.
Figure A9.3 Screen shot for package information tag set
Table A9.3 Package information tag set
ContractNumber No Yes No Edit No

SealDate No No No Edit No
SheetNumber No No No Edit No
Version 2.0.3 215 of 224

MASDAR
A9.2.4 Project information
This tag set contains information regarding the project name and location.
Figure A9.4 Screen shot for project information tag set
Table A9.4 Project information tag set
Project No Yes No Edit Yes

ProjectLocation No Yes No Edit No
ProjectPhase No Yes No Edit Yes
ProjectDescription No Yes No Edit No
ProjectNumber No No No Edit No
A9.2.5 Revision
This tag set contains information on drawing revisions. Revisions are tracked as alphanumeric
characters representing the review cycle, and a numeric character represents the design cycle.
Revision block information is intended to track and display chronological changes to the sheet.
This tag set contains information regarding the project name and location.
Figure A9.5 Screen shot for revision information tag set
Version 2.0.3 216 of 224

MASDAR
Table A9.5 Revision information tag set
RevisionApproved1 No No No Edit No
RevisionApprover1 No No No Edit No
RevisionDate1 No No No Edit Yes
RevisionDescription1 No No No Edit Yes
RevisionNumber1 No No No Edit Yes
RevisionDrawn1 No No No Edit Yes
RevisionChecked1 No No No Edit Yes
Version 2.0.3 217 of 224

MASDAR
A9.2.6 Client information
This area will contain information related to the client. This tag set contains information regarding
the project name and location.
Figure A9.6 Screen shot for client information tag set
Table A9.6 Client information tag set
ClientLocation No No No Edit No
ClientName No No No Edit No
A9.2.7 Approvals
This tag set contains signature information for the sheet as follows:
Figure A9.7 Screen shot for approvals information tag set
Table A9.7 Screen shot for approval information tag set
ApproveDate No Yes No Edit No

Approved No Yes No Edit Yes
CheckDate No Yes No Edit No
Checked No Yes No Edit Yes
ApproveDate No Yes No Edit No
Version 2.0.3 218 of 224

MASDAR
A9.2.7 Masdar title block
Copyright: MASDAR. All rights reserved. Except as permitted by the

Copyright, Designs and Patents Act 1998 no part of this document may be
reproduced, stored, transmitted or distributed in any form or by any means,
whether electronic, mechanical, by photocopy, recording or otherwise,
without the prior written permission of a director. Except where otherwise
expressly agreed in writing MASDAR shall have no responsibility or liability
for any loss (direct, consequential or otherwise) which may arise from
reliance on or use of this document or the information contained in it.
DO NOT SCALE THIS DRAWING.

NOTES:
NO DESCRIPTION DRN N DATE

Rev Description Drawn Chk‘d Date
Client
Programme Manager
Creator
ORGANISATION
Project title
PROJECT TITLE
Drawing title
TITLE-1
TITLE-2
TITLE-3
TITLE-4
Drawn Checked Approved
Scale (A4) Date Status
Drawing No. Rev.
DRAWING NUMBER 00
Figure A9.8 Masdar standard title block
Version 2.0.3 219 of 224

Appendix 10: Meta-data specification
MASDAR
Appendix 10
Meta-data specification
This appendix specifies the data fields required for technical design files
Version 2.0.3 221 of 224

Appendix 10: Meta-data specification
MASDAR
Table A10.1 Data fields for technical design files
Item Field name Data type Required* Description

Reference to the consultant‘s document management
1 dms_uid varchar(40) M
system
2 drawing_number varchar(40) MT Drawing number — to Masdar standard
3 filename varchar(80) M CAD file name — to Masdar standard
4 sheet_number varchar(4) O Sheet number
5 file_format varchar(12) M Data format
6 revision varchar(5) MT Drawing revision
7 revision_date datetime M Date of drawing revision
8 created_by varchar(20) M File created by
9 create_date datetime M Date file created
10 approved_by varchar(20) O Drawing approved by
11 approved_date datetime O Date drawing approved
12 issued_by varchar(20) O Drawing issued by
13 issued_date datetime O Date drawing issued
14 title_line1 varchar(60) MT Drawing title
17 revision_desc varchar(60) MT Revision description
18 modified_date datetime M Date drawing last modified
19 scale varchar(40) MT Plot scale
20 size varchar(40) MT Plot page size
21 project varchar(40) MD Project Identifier
22 subject varchar(40) MD Work package number
23 topic varchar(40) MD Topic
24 sub_topic varchar(40) MD Sub topic
25 area varchar(40) MD Area
26 line varchar(40) MD Line
27 item varchar(40) MFD ‘M‘
28 location varchar(40) MD Location
29 type varchar(40) MD Type
30 sub_type varchar(40) MD Sub-type
31 stage varchar(40) MFD ‘D‘
32 provider varchar(40) M Contract No and company name
33 transmittal_no varchar(40) M Consultant transmittal number
34 d_revision varchar(5) M Consultant draft revision
35 d_revision_date datetime M Consultant draft revision date
36 d_revision_desc varchar(60) M Consultant draft revision description
Key M = Mandatory field

O = Optional field
T = Title block field
D = Derived from drawing number
F = Fixed value
U = Field not used (null value)
Version 2.0.3 222 of 224

Paul King
Bentley Systems
+44 (0)7966 162 695
MASDAR
Khalifa A City
Opposite the Presidential Flight
Abu Dhabi
Page 224 of 224 UAE

CAD

Uploaded by

Document Information

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

CAD

Uploaded by

Copyright:

Available Formats

Paul King

Version Date Comment Prepared Approved

Chapter 7 figure numbers to be added - awaiting

Version 2.0.3 3 of 224

Chapter 2: Information and data management strategy

Chapter 3: Design information modelling guide

Version 2.0.3 4 of 224

Chapter 4: Element coding standard

Chapter 5: CAD standard

Chapter 6: Data management guide

Version 2.0.3 5 of 224

28 Sign-off and approval processes ................................................................................................. 126

Chapter 7: Data management standard

Chapter 8: Education, training and support

Version 2.0.3 6 of 224

Version 2.0.3 7 of 224

Version 2.0.3 8 of 224

2 Modelling and collaboration documentation

Chapter 2: CAD/BIM information and data management strategy

Chapter 3: Design information modelling guide

Chapter 4: Element coding standard

Chapter 5: CAD standard

Chapter 6: Data management guide

Chapter 7: Data management standard

Chapter 8: Learning paths

Version 2.0.3 9 of 224

(c) Project teams must follow Masdar‘s delivery phases.

Version 2.0.3 10 of 224

Version 2.0.3 11 of 224

4 Modelling and design collaboration software

Table 1 Bentley software tools

Tool / files Description Version

Bentley Architecture Architectural BIM application 08.09.04.46

Bentley Structural BIM application for creating structural systems. 08.09.04.65

Bentley Building BIM application for building-related electrical systems 08.09.04.17

MX International Digital terrain model creation and analysis 08.09.05.11

Pre-requisite A set of files needed prior to installing BIM applications 08.09.04.01

Version 2.0.3 12 of 224

5 Updating BIM documentation

Version 2.0.3 13 of 224

3D model A model with objects having three-dimensional properties

3D reference Empty model file containing only referenced 3D model files

Author The originator of a model file, drawing or document

Cell library File containing a collection of cells

Colour table A file that specifies standard colours to ensure consistency.

Version 2.0.3 14 of 224

Element Another word for object.

Entity Another word for object.

Families Used to group ‗parts‘ into logical groups of similar characteristics

Instance Occurrence of an entity at a particular location and orientation within a model.

Level See layer

Meta-data Information that describes or supports the central data

Originator The author of the models, drawings, data and documents.

PDF drawing Rendition of a drawing file in PDF format

Version 2.0.3 15 of 224

Purpose of States the purpose for issuing the document.

Revision Used to identify revisions to documents, drawing and model files.

Sheet view A sheet model containing the complete drawing.

Standard A common layering convention used by the project team.

Symbology The assigned visual characteristic allocated to vector elements.

Version 2.0.3 16 of 224

ACS Auxiliary coordinate systems

BIM Building information model

CAD Computer aided design