Professional Documents
Culture Documents
For
ALDAR
Issued on 13/07/2017
BIM Project Execution Plan – YAS Zone IB – Corporate Accommodation
Notice
This document and its contents have been prepared and are intended solely for Atkins’ information and use
in relation to providing a template of a BIM Project Execution Plan (PEP) for use on Atkins’ projects.
Atkins Limited assumes no responsibility to any other party in respect of or arising out of or in connection
with this document and/or its contents.
Document history
Job number: Document ref:
Revision Purpose description Originated Checked Reviewed Authorised Date
Rev 0.1 First Draft for internal review LSM MFO GLE JRO 25 Sep 2016
Rev 0.2 Draft for internal review LSM MFO GLE JRO 22 Nov 2016
Rev 0.3 Draft for final internal review LSM MFO GLE JRO 12 Dec 2016
Rev 1.0 Internal Issue LSM MFO GLE JRO 29 Jan 2017
Rev 1.1 Internal Review Issue LSM MFO GLE JRO 09 Feb 2017
Rev 1.2 Revised for final internal LSM MFO GLE JRO 02 Apr 2017
review prior to client issue
Rev 2.0 First Issue LSM MFO GLE JRO 20 Apr 2017
Rev 3.0 Updates discipline codes and LSM MFO GLE JRO 14 May 2017
drawing numbering/naming
Rev 4.0 Updated section 11.9 & added LSM MFO GLE JRO 13 Jul 2017
Project North for Plot 1 & 2
Document History
Revision
This will show the latest version of the document; digits will express it, with draft copies starting with 0.1 to
0.n and the first release starting with 1.0. Minor changes to the document will be reflected in the version
number by changes to second digit. Major changes will be reflected by changing the first digit (increasing by
a factor of one).
Reference Documents
This document must be read in conjunction with, but not limited to, other project specific manuals, plans or
procedures that are applicable to this project. The table below lists other relevant documents. Where there
are any document conflicts or discrepancies the originator of this document must be informed immediately.
Reference Documents
Preface
This PEP lists the agreed targets for responsibility, timely delivery, exchange, reuse and final handover to the
clients. It also lists all of the agreed elements as outlined in the Employers Information/Client Requirements
and Brief.
This document is owned and maintained by the current Project Delivery Manager listed below.
Document Authority:
This PEP has been agreed by the representatives of the project team as listed above with the authority of
their parent companies to accept this document for the agreed BIM Project Execution Plan (PEP).
Index
1. Project Information 10
General Project Information 10
Project Team Representatives and Role 10
Project details 11
2. Defining the Employers Information Requirements (EIR) 11
3. Roles and Responsibilities (for production information) 12
Roles and Responsibilities 12
Authorisations for security, extranet and document distribution 13
4. Project goals and Uses for collaboration and information modelling 14
How each Project Goal will be met 15
Design Authoring 15
Design Reviews 15
3D Coordination 15
STRUCTURAL ANALYSIS 15
LIGHTING ANALYSIS 16
ENERGY ANALYSIS 16
MECHANICAL ANALYSIS 16
OTHER ENG. ANALYSIS 16
SUSTAINABILITY (“Estidama”) 16
COST ESTIMATION 17
5. Project Information Model (PIM) delivery strategy 18
Volume Strategy 18
Model Strategy 18
Common Data Environment (CDE) 19
Aconex 19
File transfer Protocol 19
Model Transfer (WIP to Shared) 19
Model Transfer (Shared to Published) 20
Model Delivery Schedule 20
6. Levels of Model Detail/Information 21
Progressive Model Maturity - Levels of model information 21
Progressive Model Maturity - Levels of model detail 21
Model Production and Delivery Table (MPDT) 21
7. Co-ordination and Clash Avoidance 23
Clash Avoidance and 3D Coordination 23
Design Coordination Meetings 23
BIM Coordination Meeting Schedule 23
Navisworks Clash Avoidance 24
Clash Priorities 24
Clash Matrix 24
Analyse Report 25
Clash Report 26
8. Element Ownership - Typical BIM Elements by Discipline 28
(I) ARCHITECTURAL BIM ELEMENTS 28
(II) STRUCTURAL BIM ELEMENTS 29
(III) CIVIL BIM ELEMENTS 29
(IV) ACMV BIM ELEMENTS 29
(V) PLUMBING AND SANITARY BIM ELEMENTS 30
(VI) FIRE PROTECTION BIM ELEMENTS 30
(VII) ELECTRICAL BIM ELEMENTS 31
Element Maturity 32
9. Compliance Plan 37
Quality Control Checks 37
Model Validation 37
Splash Screen 37
Checklists 38
Check, Review, Approve and Publish 38
10. Technology Infrastructure Needs 39
Software Versions 39
Exchange Formats 39
Project Collaboration and CDE 39
11. Standard Method and Procedure 40
Standards 40
Discipline Model Responsibility Matrix 40
Anticipated Models 40
Model Origin and Orientation 40
Federated Model Strategy 41
Units 42
Project North – Plot 1 42
Project North – Plot 2 42
File Naming Convention 43
Drawing Sheet Number on the Title Block: 43
Sketch Drawing Naming: 43
Revit BIM Model Naming: 43
CAD Xref Naming: 44
Project Documents: 44
Project Code 44
Organization Code 44
Plot Code (Custom Field 1) 45
Building Code - Plot 1 (Custom Field 2) 45
List of Tables
Document History 2
Reference Documents 3
Project Delivery Manager 3
Project Information 10
Project Team Representatives and Role 10
Project information 11
Roles and Responsibilities (for production information) 12
Authorisations for security, extranet and document distribution 13
BIM Goals 14
BIM Uses 14
Levels of model information 21
Model Production and Delivery Table (MPDT) 22
Model Production and Delivery Table (MPDT) 22
BIM Coordination Meeting Schedule 23
Revit Architecture Element ownership and LOD 33
Revit Structure Element ownership and LOD 34
Revit MEP HVAC Element ownership and LOD 35
Revit Plumbing Element ownership and LOD 35
Revit Fire Protection Element ownership and LOD 36
Revit Fire Electrical Element ownership and LOD 36
Quality Control Checks 37
Software Versions 39
Exchange Formats 39
Project Collaboration and CDE 39
Standards 40
Model Responsibility Matrix 40
Model Origin 41
Drawing Sheet Numbering on the Title Block 43
Drawing in Native Format (Bound File) 43
Drawing in PDF Format (.PDF) File Naming 43
Sketch Drawings Naming 43
BIM (Model) File Naming 44
CAD Xref Naming 44
Project Documents 44
Project Code 44
Organization Code 44
Plot Code 45
Building Codes - Plot 1 (C7) 46
List of Figures
Concept Image 11
Volume Strategy 18
CDE Work Flow as per BS 1192. 19
Progressive Model Maturity 21
Clash Text Priority Matrix Sample. 24
Splash Screen (Default start up view in Revit) 37
Project Origin 41
Model Building Codes – Plot 1 (C7) 46
Model Building Codes – Plot 2 (C8) 47
Example Drawing Title Sheet 57
1. Project Information
General Project Information
Client ALDAR
Project Yas Zone IB - Corporate Accommodation
Document title BIM Project Execution Plan (PEP)
Job no. 5145326
Document reference YAS-IB-ATK-AR-PRC-00001
Project Information
Project details
Client/Employer ALDAR
Project Name Yas Zone IB - Corporate Accommodation
Yas Island Yas Island
Abu Dhabi, UAE
Project Description Yas Island Zone IB ("Yas Zone IB") is a proposed ·new
high-density residential development located on a
reclaimed waterfront land to the southeast of Ferrari
World and the new Vas Mall.
It is intended that Zone IB will incorporate residential
apartment buildings. This project will respond to the
UPC's requirements for middle income housing on Vas
Island; as well as meet future market demand for
middle income housing.
Project information
Concept Image
Information Management is part of everyone’s job. Information can be graphical, non-graphical and
documentation then any information produced on a project either in terms of the design or in terms of the
management of a project is included – thus every project team member has a role to play in information
management.
One role can be undertaken by more than one individual and an individual can undertake more than one role.
Whilst not all roles are essential – all responsibilities are and thus will need to be owned and clearly
communicated to enable efficient and effective working.
BIM Goals
SUSTAINABILITY
EVALUATION
PHASE PLANNING*
(4D MODELLING)
PHASE PLANNING CODE VALIDATION PHASE PLANNING (4D PHASE PLANNING (4D
(4D MODELLING) MODELLING) MODELLING)
BIM Uses
* note 4D modelling will be undertaken by the contractor during construction planning phase.
Design Authoring
Description
A process in which 3D software is used to develop a Building Information Model based on criteria that is
important to the translation of the building’s design. Two groups of applications that are at the core of the BIM-
based design process are design authoring tools and audit and analysis tools.
Authoring tools create models while audit and analysis tools study or add to the richness of information in a
model. Most of audit and analysis tools can be used for Design Review and Engineering Analysis BIM Uses.
Design authoring tools are a first step towards BIM and the key is connecting the 3D model with a powerful
database of properties, quantities, means and methods, costs and schedules.
Design Reviews
Description
A process in which a 3D model is used to showcase the design to the stakeholders, evaluate meeting the
program, and set criteria such as layout, sightlines, lighting, security, ergonomics, acoustics, textures and
colours, etc. Virtual mock-ups can be done in high detail even on a part of the building like a façade to quickly
analyse design alternatives and solve design and constructability issues. If properly executed, these reviews
can resolve design issues by offering different options. Additionally, design reviews reduce the cost and time
invested in traditional mock-ups considering basic construction, making modifications after reviews and final
demolition and removal expense.
3D Coordination
Description
A process in which Clash Detection software is used during the coordination process to determine field
conflicts by comparing 3D models of building systems. The goal of clash detection is to eliminate the major
system conflicts prior to installation.
STRUCTURAL ANALYSIS
Description
A process in which intelligent modelling software uses the BIM model to determine the most effective
engineering method based on design specifications. Development of this information is the basis for what will
be passed on to the owner and/or operator for use in the building's systems (i.e. energy analysis, structural
analysis, emergency evacuation planning, etc.). These analysis tools and performance simulations can
significantly improve the design of the facility and its energy consumption during its lifecycle in the future. How
goal will be met.
LIGHTING ANALYSIS
Description
A process in which intelligent modelling software uses the BIM model to determine the most effective
engineering method based on design specifications. Development of this information is the basis for what will
be passed on to the owner and/or operator for use in the building's systems (i.e. energy analysis, structural
analysis, emergency evacuation planning, etc.). These analysis tools and performance simulations can
significantly improve the design of the facility and its energy consumption during its lifecycle in the future.
ENERGY ANALYSIS
Description
A process in which intelligent modelling software uses the BIM model to determine the most effective
engineering method based on design specifications. Development of this information is the basis for what will
be passed on to the owner and/or operator for use in the building's systems (i.e. energy analysis, structural
analysis, emergency evacuation planning, etc.). These analysis tools and performance simulations can
significantly improve the design of the facility and its energy consumption during its lifecycle in the future.
MECHANICAL ANALYSIS
Description
A process in which intelligent modelling software uses the BIM model to determine the most effective
engineering method based on design specifications. Development of this information is the basis for what will
be passed on to the owner and/or operator for use in the building's systems (i.e. energy analysis, structural
analysis, emergency evacuation planning, etc.). These analysis tools and performance simulations can
significantly improve the design of the facility and its energy consumption during its lifecycle in the future.
SUSTAINABILITY (“Estidama”)
Description
A process in which a project is evaluated based on sustainable criteria. This can refer to materials,
performance, or a process. Sustainability Evaluations can be applied across all four phases of a construction
project, Planning, Design, Construction, and Operation. Sustainability evaluation is most effective when it is
done in planning and design stages and then applied in the construction and operations phase. Model all
sustainable aspects of a project throughout its life-cycle in order to obtain the desired sustainable certification
in the most efficient manner by condensing design analyses into a single database.
COST ESTIMATION
Description
A process in which a BIM model can be used to generate an accurate quantity take-off and cost estimate early
in the design process and provide cost effects of additions and modifications with potential to save time and
money and avoid budget overruns. This process also allows designers to see the cost effects of their changes
in a timely manner which can help curb excessive budget overruns due to project modifications.
The PIM will set out the volume strategy for the models. The aim of the volume strategy is to establish clear
ownership of elements and enable clear interface between disciplines.
Volume Strategy
The Yas Zone IB - Corporate Accommodation project has been divided into volumes, defined by coordinates
within the overall project model, that will be held as separate model files, allowing multiple users to work on
the project efficiently. Volumes have been allocated using cut lines to indicate their limits. The volume strategy
for drawing delivery are provided below:
The Yas Zone IB - Corporate Accommodation project volumes will combine the Plots & Buildings codes;
• 11.7.8 for Plot Codes
• 11.7.9 Building Codes Plot 1
• 11.7.10 Building Codes Plot 2
Volume Strategy
Model Strategy
The project models will be created from a series of links that will create a federated model like a Soma Cube.
Typical Architectural Building BIM Models include;
• Sheet Model
• Area Model
• Levels and Grids Model
• Work In Progress (WIP): Non-verified design data used by discipline specific design teams.
• Shared: Verified design data shared with the project team for collaboration purposes.
• Published/Issued Documentation: Coordinated and validated design output for use by the project team.
• Archive: Project history maintained for knowledge and for regulatory and requirements.
There are four key phases to CDE as illustrated below:
Aconex
Aconex will be utilised for the project data published to the client in accordance with the clients Aconex project
protocols.
All models must be checked, validated and approved prior to moving between WIP and SHARED.
• Remove all WIP views, (Sections, Elevation, Plans and Schedules etc)
• Remove all unused models and CAD files
• Retain linked models loaded to form room bounding elements.
• Preserve worksets to enable partial loading of model information
• Ensure the model has been saved as central
• Ensure the linked Model paths are updated to match the shared locations
It is anticipated the Models will be shared between Atkins and external consultants at a period no longer than
bi weekly.
Atkins will share our internal models via the CDE, the models will be shared at a period of no longer than 1
week.
More frequent model sharing may occur for critical design stages and/or decisions.
Model elements are suitable for the generation of traditional construction documents and shop
300
drawings. As such, analysis and simulation is authorised for detailed elements and systems.
BIM processes will be employed on the project during stages 4, 5 and 6 to enable better coordination,
collaboration and communication between the team.
Construction documentation
Construction
Stage Name Schematic Design Detailed Design
Documentation
Level of Detail Level of Detail Level of Detail
ARCHITECTURE 100 200 300
STRUCTURE 100 200 300
MEP 100 200 300
Clash avoidance meetings will be scheduled in accordance with the project programme. BIM project
coordinator and BIM project manager will arrange and lead the BIM design coordination meeting, it is the
responsibility of the design leads to resolve the Design issues that arise from this meeting.
Inter-discipline design
reviews with all
participating disciplines
3D Model Schematic Design Single design review within In accordance Discipline
Coordination a single discipline with the project PMM & CMM
Detailed Design
Inter-discipline design program and All PMM and
Construction reviews with all schedule CMM
Documentation participating disciplines
PEP Review Schematic Design Review PEP and update Once at each stage All PMM and
with any changes that have commencement CMM
Detailed Design been agreed by all BIM
participants
Construction
Documentation
Construction Phase
PEP Review Construction, Review PEP and update Once at All PMM
commissioning and with any changes that have commencement of All CMM
handover (schedule been agreed by all BIM BIM implementation Contractor
of rates) participants on the project Team
Clash Priorities
Clash avoidance will be completed based on clash priorities. All clashes under priority tests will be reviewed
and resolved as outlined in the Clash test priority matrix shown below. Clashes that have been resolved may
not need to be remodelled to be considered resolved.
Clash Matrix
Read the matrix along the top, and grouped by discipline, with sub-categories representing individual test
names (such as Floors, Walls etc.) containing different groups of elements. Groups of elements are selected
using search sets. Working from left to right, each vertical column is filled with coloured icons representing
clash priority as either HIGH, MEDIUM or LOW (as represented in the category key at the bottom). By reading
down the vertical selection, it is possible to read off on the left hand side, which group of elements are to be
clashed with which other group of elements. Each named test therefore, may contain more than one search
set.
Analyse Report
When all tests have completed, it is necessary to check through the results and analyse the outcome. The first
task is to group all clashes by element. First, select a clash and then click the Group button
Navisworks will put all clashes in that set which interact with either Item 1 or Item 2 (depending upon which
button is selected) into a single group. Usefully, it is also possible to update the status of multiple clashes by
changing the group heading, rather than having to change each one individually. Clashes are essentially just
about one element interacting with another, but one MEP system may consist of many different elements. To
a trained human operator, 10 clashes with one piece of machinery should really be seen as one clash
consisting of several different interactions. Therefore, by grouping clashes, what appears at first glance to be a
very large number of separate clashes, can quite quickly be reduced to a more manageable number.
Due to the way Navisworks searches and finds clashes, it is also more than likely that some of the clashes will
be “false positives”, or technical clashes which do not impact upon construction. This latter definition is open to
interpretation, but as an example may include cast-in drainage pipes, which technically clash with the
foundations or slabs, but are intentionally inside the structure. In this case, the clash result would be marked
as “Approved” by selecting it from the drop down list under the Status heading
Incorrectly identified clashes, or “false positives”, are issues picked up by Navisworks which upon closer
inspection can be proven to be false. An example would be a column to slab junction which passes a visual
inspection. Items such as this would also be marked as “Approved”. Any clashes not filling the conditions
described previously should be marked as “Reviewed” using the Status command, also described above.
Finally, the next time the clash tests are run using updated NWC files, the Resolved column will be
automatically populated with any previously identified clashes which have become obsolete. However, since
the number of Resolved clashes is included in the overall number of clashes counted, it is recommended they
are removed from the table by selecting the “Compact All” command.
Whilst checking through the test results, try different view options, such as displaying only the two clashing
objects in the selected result, or with all background objects dimmed
It is often the case the problem is not immediately obvious, and a little navigation and manipulation of the
image is necessary to understand what and where the clash is.
Clash Report
When the results of the clash test process have been reviewed, false positives and acceptable items
approved, and any resolved clashes removed, the clash report should be written. A major factor in the clash
detection process is the tracking of issues to ensure that problems are not only identified, but resolved. Do this
by using Saved Viewpoints to keep a point of reference to keep returning to and check progress on closing out
clashes.
Select the Report tab, in the Clash Detection window, and adjust the Output Settings to All Tests Combined
and As Viewpoints. Also tick the Preserve Result Highlighting box
Note - Depending upon the number of clashes in the report, this process can take a long time (30 mins+ if
many clashes). As is the case for running the initial clash tests.
Horizontal floors A U U U U U
Rainwater & storm Includes outlets, surface channels, slot channels and manholes
U U U A U U
water pipe work
Underground Public For drainage only
U U U A U U
Utilities
Drains, canals, crossings, retaining walls, and underground
Others harvesting tanks U U U A U U
Element Maturity
REVIT ARCHITECTURE LOD
Component Type/Name Requirements 100 200 300
Type/Dimensions N/A N/A N/A
Level N/A N/A N/A
Material N/A N/A N/A
Landscape or Entourage
Mark N/A N/A N/A
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dims * * *
Base Level * * *
Base Offset from Level * * *
Room Bounding * * *
Slope N/A * *
Roof
Thickness N/A * *
Material N/A N/A *
Mark N/A N/A *
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dimensions * * *
Base Constraint * * *
Base Offset * * *
Top Constraint * * *
Top Offset * * *
Height * * *
Walls or Curtain_Wall Room Bounding * * *
Structural N/A * *
Structural Usage N/A * *
Material N/A N/A *
Mark N/A N/A *
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dimensions * * *
Level * * *
Height Offset from Level N/A * *
Ceilings or Light_Fixtures or Room Bounding N/A * *
Louvers Material N/A * *
Mark N/A * *
Phase Created N/A N/A *
Phase Demolished N/A N/A *
Type/Dimensions N/A N/A N/A
Level N/A N/A N/A
Furniture or Casework or Material N/A N/A N/A
Equipment Mark N/A N/A N/A
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dimensions * * *
Level * * *
Sill Height N/A * *
Doors or Windows Material N/A N/A *
Mark N/A N/A *
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dimensions * * *
Level * * *
Height Offset from Level * * *
Room Bounding * * *
Floors Structural N/A * *
Material N/A N/A *
Mark N/A N/A *
Phase Created N/A N/A N/A
Phase Demolished N/A N/A N/A
Type/Dimensions N/A * *
Railings
Base Level N/A * *
9. Compliance Plan
Quality Control Checks
The following checks will be performed to assure adherence to the quality goals of the Yas Zone IB -
Corporate Accommodation project:
Responsible Software
Checks Definition Frequency
Party Program(S)
Model Validation
All models will require validation of the design contained within the model and the model integrity prior to being
made available to the project team through the designated project Shared Area.
Splash Screen
Splash screen, this should be the default opening view for all models in the project. The splash screen
captures details such as Model Status and Revision.
Checklists
Checklists have been provided for each discipline and should be completed by each individual performing any
check, review or approval of the model for progression to next step.
Changes which prevent the model being issued must be addressed before the model continues to next stage.
Changes that do not prevent the model from being shared must be captured in the WIP model prior to next
issuance. The Model Author should review the checklist from the previous model and note in the comments
column where changes have been updated from previous checklists.
The Model Author and all checker should review the checklist from previous issue to ensure comments have
been updated to reflect the conditions outlined.
BIM Model checklist are located in the CAD-BIM, Revit, 2017, ATK-Checklists…
O:\Standards\AEDXA\CAD-BIM\Revit\2017\ATK\Frames\ATK-Checklist
The model integrity will require validation of the data by the PMM/CMM prior to being made available to the
project team through the designated project Shared Area.
The checklists will be completed and issued with each model delivery.
Software Versions
Exchange Formats
The agreed formats for model and drawing file exchange are:
(* IFC is only issued at project Completion design stage and construction stage)
Exchange Formats
Standards
Anticipated Models
The Models are separated by Discipline, Sub-Plot, Building and volume.
Refer to the Discipline BIM Registers for all anticipated models.
Model Origin
Atkins will provide a Lisp Routine to change between Survey Grid (Geodetic) and Project (Base) Grid
Load 5145326-YAS-IB-BasePoint.LSP
Type Survey2Project to convert all CAD data from the Survey Grid to the Project Grid.
X = 258300m (E), Y = 2709300m (N) to X = 0.0mm, Y = 0.0mm
Type Project2Survey to convert all CAD data back from the Project Grid to the Survey Grid
X = 0.0mm, Y = 0.0mm to X = 258300m (E), Y = 2709300m (N)
Project Origin
Units
On this project, dimensions shall be derived automatically from the underlying CAD coordinates, using the
'associative dimensioning' function of CAD systems. Dimensions shall not be entered as 'text'.
Refer to the project drawing register MDI (Mater Document Index) for a complete list of all Drawing
Deliverables.
SI Number
Custom #1
Custom #2
Discipline
Building
Drawing
Project
11.7.15
Code
Type
Plot
SI Number
Custom #1
Custom #2
Extension
Discipline
Orig. Co.
Revision
Building
Drawing
Project
11.7.15
Code
Type
Type
Plot
File
YAS-IB - ATK - AR - 11 - C2 - DR - 151043 - DWG [A]
Custom #2
Extension
Discipline
Revision
Building
Orig Co.
Drawing
Project
11.7.15
Code
Type
Type
Plot
File
Custom #2
Extension
Discipline
Orig. Co.
Revision
Building
Drawing
Project
11.7.15
Code
Type
Type
Plot
File
SI Number
Description
Custom #1
Custom #2
Discipline
File Type
Orig. Co.
Building
Project
Model
Code
User
Plot
User
YAS-IB - ATK - AR - 12 - E1 - M3 - 122101 - Sheet
Description
Custom #1
Custom #2
Discipline
Dwg Type
Orig. Co.
Building
Table 11
Drawing
Project
Code
Plot
User
Xref
YAS-IB - ATK - ME - 11 - B2 - PL - Typical_Floor
Project Documents:
Example Project Document: YAS-IB-ATK-PM-MOM-00001[B] Minutes
SI Number
Description
Discipline
Doc Type
Document
Revision
Orig Co.
Project
Project
Code
User
Project Documents
Project Code
Code Project
YAS-IB YAS Island Development – Zone IB Plots 1 (C7) and 2 (C8)
Project Code
Organization Code
Code Organization
ALD ALDAR
ACE ACES
ATK WS Atkins & Partners Overseas
C&B Currie & Brown
DEZ Dezigntechnic
RBA RBA
VOR Vortex
Organization Code
Plot Code
File Type
Discipline Code
As per As per ALDAR Properties PJSC Project Document control and Communication Procedure for Yas
Island Development – Zone IB Table 10.
Discipline Code
Number
Number Description
000001 Number (6 digits)
Number Fields Drawing Number Fields:
1 Drawing Prefix, Refer 11.7.9 - Plot 1 & 11.7.10 - Plot 2 (2 digits)
2 Drawing Series Number, Refer to 11.7.16 (2 digits)
3 Number 01 – 99 (2 digits)
1 = Drawing Prefix = 21
2 = Drawing Series Number = 60
3 = Number = 42
21 60 42
Model Number
Number Fields Model Number Fields:
1 Plot Code. Refer to 11.7.8 (2 digits)
2 Drawing Prefix (per Building) Refer 11.7.9 & 11.7.10
3 Number 01 – 99 (2 digits)
1 = Plot Code = 12
2 = Drawing Prefix = 21
3 = Number = 03
12 21 03
Work in Progress
Shared (Non-Contractual)
AM As Maintained
Partially signed-off:
For Construction with minor comments from the Client. All minor comments should be indicated by
B
the insertion of a cloud and a statement of “in abeyance” until the comment is resolved, then
resubmitted for full authorization.
As-Built
AB
Handover documentation, PDF, native models etc.
Status Code
Revision Control
In order to maintain the consistency in the drawing issues descriptions, following are standard issue
descriptions are to be used:
The above are the most commonly used purposes of issue. However, additional purpose of issue can be
used as indicated in the Project Quality Plan and as approved by the Project Manager.
For internal purposes, all drawings are starting with revision “AV1” from the initial stage of detail design. Any
internal issues for information within the departments or any Atkins offices, the revisions should be suffixed
with “V1, V2, V3, etc.”).
Once the initial stage is completed and is ready to issue, then the revisions will change into A, B, C… and
again once detail design is completed, these drawings will be issued “For Tender”. After this stage all drawing
revisions to be changed into numerical series i.e. “00’ and ALL REVISION CLOUDS MUST BE REMOVED.
The drawing numbers will remains the “same”. The drawing revisions will continue in numerical series only for
further issues like “Contract”, “Construction”, etc.
This revisions series Continue for further issues till the “Tender” issue
Revision Code
To improve hardware performance, only the required worksets shall be opened. Revit ensures that elements
contained in closed worksets are still updated if changes made in open Worksets impact them during model
regeneration.
The definition and allocation of the worksets shall be appropriate to avoid compromising future use of the
model. Worksets and their comprising elements shall be assigned individually or by category, task allocation,
location, or as agreed by the project.
Workset organisation seeks two goals: first, it allows for collaboration of two or more people on the same
model. Second, the data can be segregated within the model to optimise performance by a single user being
able to selectively load or unload partial data. Fundamental to the success of the latter is that the information
in the model is consistently stored in the right workset, which requires the BIM team to pay special attention
when modelling, editing and linking information.
As a general rule, all projects shall be workset-enabled to enable this collaboration. When Revit Project
Sharing is enabled, elements that are not part of a standard Revit workset are assigned to a default Workset1.
The default workset, Workset1, shall always remain in the Revit model and should never be renamed or
removed/deleted from the model. Worksets should be named in a logical, consistent manner to aid navigation
through the project.
The table below offers guidance as to how zones and content can be determined.
Drawing Scales
Templates
Drawing sheet size will be ISO A0.
O:\Standards\AEDXA\CAD-BIM\Revit\2016\ATK\Templates
P:\AEDXA\5145326 – Yas Zone IB\CAD_BIM\06-Resource\Frames
Project Templates
O:\Standards\AEDXA\CAD-BIM\Revit\2016\ATK\ParameterLibrary
Appendix A
Clash rendition
Appendix A. Rendition of the native format model file to be
used specifically for spatial coordination
processes
Terms and Definitions
For the purposes of this PEP the following terms Classification
and definitions apply. Systematic arrangement of headings and sub-
headings for aspects of construction work
Archive including the nature of assets, construction
Component of the common data environment elements, systems and products
(CDE)
Drawing
Attribute Static, printed, graphical rendition representation
Piece of data forming a partial description of an of part or all of a Project or asset
object or entity
(EIR) Employer’s information
Author requirement
Originator of model files, drawings or documents Pre-tender document setting out the information to
be delivered, and the standards and processes to
(PEP) Building information be adopted by the supplier as part of the Project
modelling project execution plan delivery process
Plan prepared by the suppliers to explain how the
information modelling aspects of a Project will be Information exchange
carried out Structured collection and delivery of information at
one of a number of pre-defined stages of a Project
(BIM) Building information with defined format and fidelity
modelling
Process of designing, constructing or operating a Information management
building or infrastructure asset using electronic Tasks and procedures applied to inputting,
object-oriented information processing and generation activities to ensure
accuracy and integrity of information
(BOQ) Bill of Quantities
A bill of quantities (BOQ) is a document used in Information modelling
tendering in the construction industry / supplies in Use of data to provide information through better
which materials, parts, and labour (and their understanding, by applying logic or mathematical
costs) are itemized. functions to derive new data
Published
BIM Data that is verified design data shared with
the client through the CDE.
Rendition
A visual reproduction of the model such as
Drawings, tables, reports
Shared
BIM Data that is verified design data shared with
the design team through the CDE.
Volume
Manageable spatial subdivision of a Project,
defined by the Project team as a subdivision of
the overall Project that allows more than one
person to work on the Project models
simultaneously and consistent with the analysis
and design process.
Abu Dhabi:
Email: office.abudhabi@atkinsglobal.com
Tel: +971 2614 9100
Fax: +971 2627 0999
Dubai:
Email: office.dubai@atkinsglobal.com
Tel: +971 4405 9300
Fax: +971 4405 9301