BIM Execution Plan: Chennai Metro Rail Limited Chennai Metro DDC Phase II Corridor 4 Packages 5

BIM Execution Plan
Chennai Metro Rail Limited
Chennai Metro DDC Phase II Corridor 4 Packages 5
Report no. – DDC-P2C4/05-GN-P-08-A
October 2019
BIM Execution Plan Chennai Metro DDC Phase II Corridor 4 Package 5
Prepared for:
Admin Building, CMRL Depot,
Poonamallee High Road,
Koyambedu,
Chennai – 600107,
Tamil Nadu, India
Prepared by:
ASPL+AIPL+AARVEE Consortium
VBC Solitaire
No. 47 & 49, 2nd Floor
Bazullah Road, T Nagar
Chennai 600017
Tamilnadu, India
CIN: U74210TN2002PTC049350
T: +91 44 4965 6666

aecom.com
Prepared in association with AARVEE
© 2019 AECOM Singapore Pte Limited. All Rights Reserved.

This document has been prepared by AECOM Singapore Pte Limited (“AECOM”) for sole
use of our client (the “Client”) in accordance with generally accepted consultancy
principles, the budget for fees and the terms of reference agreed between AECOM and the
Client. Any information provided by third parties and referred to herein has not been
checked or verified by AECOM, unless otherwise expressly stated in the document. No
third party may rely upon this document without the prior and express written agreement of
AECOM.
Report -08 / Rev.A ii AECOM + AARVEE

Table of Contents
1. Project BIM Execution Plan Overview 1

1.1 Purpose ...................................................................................................................... 1
1.2 Scope .......................................................................................................................... 1
2. Project Information 1
2.1 Project Owner: Chennai Metro Rail Limited .............................................................. 1
2.2 Project Name: Contract No. DDC/P2C4/05 (Phase-II, Corridor 4, Package 05) ....... 1
2.3 Project Location and Address: Chennai, India ........................................................ 1
2.4 Contract Type: Detailed Design Consultant ............................................................... 1
2.6 Project Milestones: .................................................................................................... 1
3. Key Project Contacts 2
4. Project Goals/ BIM Uses 2
5. BIM Organizational Role 4
6. BIM Modelling Scope / Elements / Level of Information Need (LOI) 5
7. Common Data Environment (CDE) 7
8. Quality Control 1
9. Technological Infrastructure Needs 2
10. Model Structure 3
11. Project Deliverables 9
12. Signatory Page 10
Appendix A 11
Abbreviation & Definition ..................................................................................................... 11
Responsibility Matrix – TIDP & MIDP .................................................................................. 11
Report -08 / Rev.A iii AECOM + AARVEE

Figures
Figure 1. BIM Delivery Team ................................................................................................ 4

Figure 2. Illustration of spatial federation strategy by discipline in a building project ............. 5
Figure 3. CDE – BIM 360 Docs with Design Collaboration module....................................... 8
Figure 4. Medium Trust Design Collaboration....................................................................... 6
Tables
Table 1. Project Schedule/ Phases/ Milestones .................................................................... 1

Table 2. CMRL Team ............................................................................................................ 2
Table 3. Design Team (AECOM + AARVEE) ........................................................................ 2
Table 4. Goals and BIM Uses ............................................................................................... 2
Table 5. LOD Milestone & Definition ..................................................................................... 6
Table 6. Meeting Procedures................................................................................................ 7
Table 7. Model Information Exchange format ....................................................................... 7
Table 8. Quality Control Checks ........................................................................................... 1
Table 9. List of Software ....................................................................................................... 2
Table 10. Hardware Configuration ........................................................................................ 2
Table 11. DISCIPLINE CODE ............................................................................................... 3
Table 12. TYPE CODE ......................................................................................................... 4
Table 13. STATIONS NAME: CORRIDOR 4, PACKAGE 05 ................................................. 4
Table 14. Model and Drawing series .................................................................................... 5
Table 15. Standard Reference.............................................................................................. 7
Table 16. Workset Naming ................................................................................................... 8
Table 17. BIM Deliverables................................................................................................... 9
Table 18. Representative ................................................................................................... 10
Report -08 / Rev.A iv AECOM + AARVEE

1. Project BIM Execution Plan Overview

1.1 Purpose
This BIM execution plan is to provide the project team with clear guidance as to the
staffing, tools, processes, procedures and systems required to facilitate the flow of
information to support the design, procurement and construction of the CMRL,
Corridor-4 Metro Projects. This plan includes, for completeness, the use of CAD tools
(Computer Aided Design for drafting, 3D modelling and drawing production), and the
data management systems that are deployed to host the various data sources.
1.2 Scope
This plan applies to all parties and all work performed on the CMRL, Corridor-4 Metro
Project where digital design, virtual design construction tools and systems are
applicable.
2. Project Information
2.1 Project Owner: Chennai Metro Rail Limited
2.2 Project Name: Contract No. DDC/P2C4/05 (Phase-II, Corridor 4,
Package 05)
2.3 Project Location and Address: Chennai, India
2.4 Contract Type: Detailed Design Consultant
2.5 Additional Project Information:
Engagement of Detailed Design Consultant (DDC) for the works and services of the
detailed design and drawings for the Civil, Structural, Architectural, MEP, VAC & Track
works covering the Alignment, and Elevated section from Pier after Meenakshi College
UG Station to Poonamallee bye-pass (CH 10027.102 to 25829.793), including
approach to Depot and Maintenance Depot at Poonamallee, in Corridor 4 of Phase-II
of Chennai Metro Rail Project.
2.6 Project Milestones:
Brief BIM milestones provided below and to be read along with the latest version
Project Implementation Programmed
Table 1. Project Schedule/ Phases/ Milestones
Project Phase/ Milestone Start date Completion Project stakeholders
date involved
Submission of Concept Design and Design 15-08-2019 14-10-2019 Architecture, Structure, Civil,
Alternatives along with Concept Design Report E&M, Alignment
Submission of Preliminary Design based on 14-10-2019 11-02-2020 Architecture, Structure, Civil,
approved Concept Design, including E&M, Alignment
modifications if any
Delivery of Definitive Design 12-01-2020 09-08-2020 Architecture, Structure, Civil,
E&M, Alignment
Delivery of CRD Drawings 11-04-2020 06-01-2021 Architecture, Structure, Civil,
E&M, Alignment
Issue of" "Good For Construction Drawings” 08-09-2020 04-08-2021 Architecture, Structure, Civil,
E&M, Alignment
Report No. 008/Rev.A 1 AECOM + ARVEE

3. Key Project Contacts

Table 2. CMRL Team
Role Contact Name Email
CGM Mr. B S Srinivas
Contract Procurement Mr. D.Gurunath Reddy
Design Coordinator Mr. RMVMSS Rajasekharam
Architecture Mrs. S.Rajalakshmi
Architect Expert Mrs. Swati Mahajan
MEP Engineer Mr. B.Gunaseelan
BIM Lead Mr. Gautam Bhardwaj
Table 3. Design Team (AECOM + AARVEE)

Role Contact Name Email
Project Manager (AECOM) Mr. Rengasamy Selvaraju selvaraju.rengasamy@aecom.com
Design Coordinator (AECOM) Mr. Goutham Varma goutham.varma@aecom.com
Architectural Lead (AECOM) Mr. Daljit Singh daljit@absolutearchitecture.net
Station Structural Lead (AARVEE) Mr. V.Venkata Ramayya vvramayya@aarvee.net
Viaduct Structural Lead (AECOM) Mrs. Madhurima Mitra madhurima.mitra@aecom.com
MEPF Lead (AARVEE) Mr. S Soma Sundaram Somasundaram.j@aarvee.net
Alignment Expert (AARVEE) Mr. Pulithirumalaiah thirumalaiah.p@aarvee.net
BIM Manager/Coordinator Mr. Michael Daimei Michael.daimei@aecom.com
4. Project Goals/ BIM Uses

4.1 Employer’s BIM Objectives:
To procure/ produce, manage and maintain data and information for CMRL engineered
assets that is complete, consistent and can be trusted and re-used for operational
purposes and for future business intelligence. Listed below are key point summarised
from Tender Documents, Section 3 – Scope of Works, Chapter 18 – BIM
Requirements:
• Separate discipline models to be federated for drawing Production.
• Basic Quantity Extraction from the BIM Models.
• Coordination between Disciplines and Trades (clash detection) during design
development.
• To be considered for future component tagging attribute parameters in the model.
Table 4. Goals and BIM Uses

Goal Description Potential BIM Uses
Drawing Production 3D Design Authoring and Discipline Federated BIM Models
Quantity Extractions 5D
Design Visualization Walk through in BIM 360
Constructability Clash Detection and Model Reviews

4.2 Design Authoring

BIM model of the principal elements of the Civil Works scope including Viaducts and
Stations covering architectural, structural, and MEPF works will be created by the
applicable designers, in accordance with the Model Development Plan by DDC.
4.3 Drawing Generation

The main source for Drawing Generation will be from the federated discipline Revit
model. However, in early stages of the project, some of the drawings could be
generated from 2D CAD and the potential reasons that we find to make this decision
are:
• The final position of the stations is still under discussion with CMRL.
• Any third party information requirement, e.g. road layout / flyover etc.
• Design team is studying alternative solutions according to any change made to the
alignment.
• A lot of work would be required in BIM models to adapt them according to each
variation or design option.
Alignment and Geotechnical drawings will be delivered in AutoCAD.
Site or topo-surface consisting drawings will be deliver in AutoCAD and link in
Architectural street level plan.
4.4 Interference Management (Clash Checking)
The use of software that can identify spatial interferences with objects inside a model
and with objects in other models. Clash Checks are to be performed, recorded and
stored in accordance with the CMRL instruction.
Refer section 10.7 for more details on Clash Detection
4.5 Interactive design Reviews
The use of the BIM Model for design reviews to be scheduled, including formal design
reviews prior to the contractual milestone submission dates. Where conflicts are found
in the BIM, or between the BIM model and 2D drawings, regardless of the phase of the
Project, the discovering party shall promptly notify the party responsible for developing
the content (“Author”). Upon such notification, the Author(s) shall act promptly to
mitigate the conflict. Coordination meetings between disciplines will be scheduled as
required. All disciplines involved into the project take part actively. Coordination
meetings are done with models. Design Managers discuss the corresponding
interference taking technical decision. After the meeting a report is delivered to the
team with the decisions taken and the solutions to be implemented.
4.6 Quantity Take-off (QTO)

Basic Quantity take off (QTO) shall be extracted from the approved BIM model. All
model objects to be measured are to contain required attribute and parameters which
are to be align with BOQ item as required for the project.

5. BIM Organizational Role

5.1 BIM Team Organization
Figure 1. BIM Delivery Team
5.2 Responsibilities
BIM Manager – The BIM Manager is responsible for the following:
• Authoring the post-contract BIM Execution Plan (BEP) for the project on behalf of
DDC
• Coordinating with CMRL BIM representative in creating the Project BIM Standard
• Attending and providing input during BIM meetings on behalf of DDC
• Coordinating with CMRL Project BIM representative
• Coordinating with DDC design lead and DDC BIM Coordinator
• Generation Master Information Delivery Plan
BIM Coordinator – The discipline BIM coordinator are responsible for the following:
• Ensuring BIM Project Execution Plan is followed through the project duration
• Performing model QA/QC checks on a fortnightly basis
• Export NWC files from the project Revit files on a weekly basis
• Leading the Clash Detection Virtual Walkthrough (CDVW) process
• Updating the Project-wide Navisworks NWF on a fortnightly basis and recording the
NWD.
• Coordinating with discipline BIM Coordinator
• Performing design QA/QC checks, including informal intra-disciplinary CDVW
checks on a fortnightly basis using the project NWF
• Coordinating with the discipline Modeller and designers.

• Generating Task Information Delivery Plan

5.3 Project BIM Role and Responsibilities
AECOM + AARVEE
• Manage Construction Document BIM process across all disciplines (Architectural,
Structural, and MEP/FP)
• Determine the facilities coordinate systems to geo-reference point(s) and assure all
technical discipline models are properly referenced. Revit files are to follow CMRL
Revit template model views and filters.
• Ensure Compliance with CMRL BIM / Project Standards and Addenda.
• Follow CMRL Shared Coordinates (See Section 10.3 for more information).
• Formal clash detection shall be done at the milestones as required.
• Confirm general coordination and clearance into the design among the discipline.
• Capture all required information in the models to produce the deliverables as
defined by CMRL.
• Provide proper model development for each discipline, in accordance to the defined
standards and as indicated within the BIM Execution Plan.
• Each team is responsible for its own content within Revit. If a team member requires
the specific use of a component or parameter for any specific purposes, that team
will inform and coordinate with the BIM Manager and applicable teams.
6. BIM Modelling Scope / Elements / Level of

Information Need (LOI)
6.1 BIM Modelling Scope
BIM Modelling scope to comply with CMRL BIM Standards. Model elements by
discipline, level of development, and any specific attributes important to the project are
documented using information exchange worksheet. Each Party shall be responsible
for any contribution that it makes to a model or that arises from that party's access to
that model. Management of BIM must be clearly stated throughout the process and in
accordance with the BEP.
Figure 2. Illustration of spatial federation strategy by discipline in a building project

Yellow: Architecture
Blue: Structure
Green, Red, Purple – MEPF
Source: ISO 19650-1:2018_Fig A.2
6.2 Level of Information Need

The creation of the design in a virtual Model to LOD 300 for Good for Construction
documents is to be deliver by DDC. LOD 350 for shop drawing coordination, LOD 400
Fabrication-installation and to LOD 500 as-built shall be delivered by the contractor.
The general LOD definition and its level of information required in the model element
at each milestone are shown in the below tables.
Table 5. LOD Milestone & Definition
LOD Milestone Description
LOD 100 Conceptual Design The Model Element may be graphically represented in the Model
with a symbol or other generic representation, but does not satisfy
the requirements for LOD 200. Elements are indicative of area,
height, volume, location and orientation. Information related to the
Model Element (i.e. cost per square metres, tonnage of HVAC, etc.)
can be derived from other Model Elements. Design performance
parameters may be attached to the Model Elements.
LOD 200 Preliminary Design The Model Element is graphically represented within the Model as a
generic system, object, or assembly with approximate quantities,
size, shape, location, and orientation. Approximate access/code
clearance requirements are modelled and required design
performance parameters are attached to the Model Element.
LOD 200 First Design -do-
LOD 300 Tender Design The Model Element is graphically represented within the Model as a
design-specified system, object or assembly and associated
components having accurate quantity, size, shape, location and
orientation. Interfaces with other building elements and systems
have been identified and coordinated; approximate allowances for
spacing and clearances required for all specified supports and
seismic control; actual access/code clearance requirements
modelled. Parameters required for procurement, including
specification, materials and performance criteria are attached to the
Model Element.
LOD 300 Final Design -do-
LOD 300 Good For -do-
Construction
Contractor
LOD 350 Shop Coordination The Model Element is graphically represented within the Model as a
design-specified system, object, or assembly having accurate
quantity, size, shape, location and orientation. Interfaces with other
building elements and systems have been identified and coordinated
and the model is compliant and coordinated with the approved Shop
Drawings and/or Shop BIM Models that are at LOD 400. An element
may not be declared as LOD 350 until the Shop Information
associated with it has been received, reviewed and approved. Non-
graphic information compliant with the shop information will remain
attached to the Model Element as per LOD 300.

LOD Milestone Description

LOD 400 Fabrication and The Model Element is graphically represented within the Model as a
Installation specific system, object or assembly having accurate size, shape,
(Shop Drawings) location, quantity, and orientation suitable for fabrication and
installation. Required non-graphic detailing, fabrication, assembly,
and installation information is attached to the Model Element.
LOD 500 As-Built The Model Element is a field verified representation with actual
installed and accurate size, shape, location, quantity, and
orientation. Non-graphic information as installed and required for
operation and maintenance is attached to the Model Elements.
7. Common Data Environment (CDE)

7.1 Collaboration Strategy
CMRL Project Design Team will be collaborating within cloud service in a live-design
environment. Team members external to CMRL will be invited to participate in the
collaboration solution provided by CMRL. BIM 360 DOCS (Next Generation) will serve
as the document management solution along with BIM 360 Design collaboration module
to coordinate and synchronize project data to the Common Data Environment.
Table 6. Meeting Procedures
Meeting Type Project Stage Frequency Participants Location
BIM Kick-Off Pre Conceptual Design Once CMRL + DDC Conference Room, War
Room, WebEx
BIM Preliminary Design, Definitive Per Project DDC Conference Room, War
Coordination Design, CRD and GFC Schedule Room, WebEx
Clash Detection Preliminary Design, Definitive Per Project DDC Conference Room, War
Design, CRD and GFC Schedule Room, WebEx
Table 7. Model Information Exchange format

Information Exchange Model Software Native File Type File Exchange
Type
Design authoring 3D Coordination Revit/ .RVT .RVT
Alignment / Topo Surface AutoCAD .DWG .DWG
Clash Detection Navisworks .NWC .NWC
Project Common Data Environment (CDE) invitation shall be provided by CDE Manager to the project team member

Figure 3. CDE – BIM 360 Docs with Design Collaboration module.

8. Quality Control
8.1 Overall Strategy for Quality Control
Each participating team will be responsible for the integrity of their models / drawings
as well as compliance with the established CMRL BIM Standards.
8.2 Quality Control Checks

The following checks should be performed to assure quality. Note that the Quality
Control check shall be conducted by the discipline designer and BIM coordinator. Any
issues findings shall be addressed by the discipline BIM Coordinator.
Table 8. Quality Control Checks
Checks Definition Responsible Software Frequency
Party
Visual Check Review so there are no unintended model Each Discipline Revit Fortnightly
components and the design intent has
been followed
Interference Detect problems in the model where two Each Discipline Navisworks Per Project
Check building components are clashing including Schedule
soft and hard
Standard Check Review to ensure that the CMRL BIM Each Discipline Revit Fortnightly
Standard have been followed (fonts,
dimensions, line styles, levels/layers, etc.)
Note: Models should be detached and re-saved as centrals at certain frequencies,

usually at the time of milestones and archiving of submissions. This helps to reduce
the size of the models and keep performance as efficient as possible.
Obsolete or not compliant views should be fixed or deleted. Reference planes that
are not named or placed in a special workset should be deleted as well.
Due to the collaborative nature of BIM, each party needs to rely on the content
submitted for use on the project. Each discipline is responsible to police their files in
accordance to their internal QA/QC programs.
Report -08 / Rev.A 1 AECOM + AARVEE

9. Technological Infrastructure Needs

9.1 Software
Table 9. List of Software
BIM Use Discipline Software Version
Architectural Modelling Architecture Revit 2019.2
Structural Modelling Structure Revit 2019.2
Structural Analysis Structure STAAD Pro V8i(Select Series 6)
MEPF Modelling MEPF Revit 2019.2
Alignment Alignment Power Rail Track (Bentley) V8i (Select Series 2)
Clash Detection All Discipline Navisworks 2019
Collaboration All Discipline BIM 360
2D Extraction All Discipline AUTOCAD 2014
Any change of version should be in agreement with all the team. No team member should upgrade files to newer
versions without approval from Project BIM Manager.
9.2 Computer & Hardware

Understanding the hardware specifications becomes valuable once information
begins to be shared between several disciplines organizations. It also becomes
important that the downstream hardware is not less powerful than the hardware used
to create the information (i.e. equal or higher). In order for such not to occur, choose
the hardware that is in the highest demand and most appropriate for the majority of
BIM Uses. Below are the minimum hardware specifications for the Revit (BIM)
workstation within CMRL Projects.
Please consider this a benchmark also a minimum for this project, and alert the
discipline BIM coordinator if there are any concerns in meeting this requirement. To
avoid format incompatibilities and potential of corruption of BIM elements caused by
importing information from different BIM software packages, BIM software packages
shall be determined, and agreed by all parties, prior to the commencement of the
Project.
Table 10. Hardware Configuration
Hardware Description
Processor i7-6700K CPU @ 4.00GHz 4.00GHz
RAM 32GB Solid State Drive
Storage 32GB DDR3 SDRAM
Graphics 8.0GB NVIDIA Quadro M4000, 24” Dual Monitor
Above configuration is as per current AECOM standard workstation configuration.

10. Model Structure

10.1 File Naming Structure
As more and more information is shared digitally, the use of structured, consistent
and understandable naming conventions for information becomes vital.
File naming convention determine and list the structure for models file names.
It is recommended that base model sizes shall be of less file size (300mb), and if a
model is expected to become large file size, the model is to be separated in a logical
manner into separate models.
It is also recommended that the models be separated into functional worksets by all
teams for the development of a coordinated set of contract documents. Coordination
between disciplines may require a new workset be created.
All BIM models and drawings shall have a unique name. It consists of 7 fields and
shall be formatted in the following manner:
(ISSUING ENTITY) (PROJECT) (PACKAGE) (DISCIPLINE) (FILE TYPE) (LOCATION) (NUMBER)
DDC P2C4 05 Table No.11 Table No.12 Table No.13 Table No.14
ISSUING ENTITY: Issuing entity for all the documents and drawings will be Detailed
Design Consultant (DDC). It is abbreviated as DDC.
PROJECT: The code for the project is a combination of phase 2 and Corridor 4. It is
abbreviated as P2C4.
PACKAGE: This package as per contract is under package no. 05 (Power House at
Damro to Poonamallee Bypass). It is abbreviated as 05.
DISCIPLINE: Refer below Table for full list of codes:
Table 11. DISCIPLINE CODE
Code Discipline
GEN General
ALN Alignment
GEO Geotechnical
TEM Temporary Works
CIV Civil
ARC Architecture
STN Stations (structure)
STR Structure
VIA Viaducts
TRK Track work
MEP Mechanical, Electrical & Plumbing
VAC Ventilation and Air Conditioning
Project BIM Manager may update the code as per required
FILE TYPE: This element is a two (2) alphanumeric character field. Refer below
Table for full list of codes:

Table 12. TYPE CODE

Code Discipline
AF Animation file of a model
CM Combined Model (Multi-disciplinary model)
CR Specific for the clash process
DR 2D drawing
M2 2D Model file
M3 3D Model file
MR Model rendition file for other renditions (Analysis etc)
VS Visualization file of a model
BX BIM extract file
File Type for Documents

GN General
AL Alignment
GT Geotechnical
TW Temporary Works
ST Station
VA Viaduct
DE Depot
Project BIM Manager may update the code as per required
LOCATION: The location code has a maximum of three (3) alphabet characters and is
used to associate documents with geographic areas within the design and construction
region. They are in sequence starting from Power House station to Poonamallee Bypass
Stations. The code is derived by discussing among the Project team members.
Refer Table below for the full list of location codes:
Table 13. STATIONS NAME: CORRIDOR 4, PACKAGE 05
Station No. Station Name Station Code
01 POWER HOUSE AT DAMRO SPH
02 VADAPALANI SVP
03 SALIGRAMAM SSG
04 AVICHI SCHOOL SAS
05 ALWARTHIRU NAGAR SAN
06 VALASARAVAKKAM SVV
07 KARABAKKAM SKM
08 ALAPAKKAM JUNCTION SAJ
09 PORUR JUNCTION SPJ
10 CHENNAI BYPASS CROSSING SCB
11 RAMCHANDRA HOSPITAL SRH
12 IYAPPANTHANGAL BUS DEPOT SID
13 KATTUPAKKAM SKP
14 KUMANANCHAVADI SKI
15 KARYANCHAVADI SKC
16 MULLAITHOTTAM SMT

Station No. Station Name Station Code

17 POONAMALLEE BUS TERMINUS SPT
18 POONAMALLEE BYPASS SPB
CORRDIDOR CODE
Corridor-4 Elevated C4E
Depots DEP
SEQUENCE NUMBER: For drawings, dedicated range of numbers will be given for
all the following discipline:
Table 14. Model and Drawing series
Drawing No. Discipline
From 10001 to 19999 Alignment
From 20001 to 29999 Architectural
From 30001 to 39999 Geotechnical
From 40001 to 46999 Stations (structure)
From 47001 to 49999 Structure
From 50001 to 59999 Viaducts
From 60001 to 68999 MEPF
From 69001 to 69999 VAC
From 70001 to 79999 Track Works
From 80001 to 89999 Civil (Traffic, Utilities & etc.)
From 90001 to 99999 General
REVISION: Revision filed shall be one alphabetic letter. The first issue of a complete
drawing package to Employer shall be revision 'A’ and shall not be left blank. Any
resubmissions of the same drawing package shall continue will alphabetic B, C, D ...
In term of contractual tender package, Revision shall be one alphabetic letter when
issued to Employer for the first time. Any resubmissions of the same drawing
package shall continue will alphanumeric A1, A2, A3, A4 . . . . . . . .
BIM models Revision will be used based on the BIM 360 model version for WIP,
Shared and Published.
Therefore, the file naming convention of this project is as follows:
(ISSUING ENTITY) - (PROJECT) - (PACKAGE) - (DISCIPLINE) - (FILE TYPE) -
(LOCATION) - (NUMBER)
• Power house station Architectural BIM model example: DDC-P2C4-05-ARC-M3-

SPH-20001.rvt
• Power house station Structural BIM model example: DDC-P2C4-05-STR-M3-SPH-
40001.rvt
• Power house station MEPF BIM model example: DDC-P2C4-05-MEP-M3-SPH-
60001.rvt
10.2 Model Storage – BIM 360 Docs
All party involved in the project should have Autodesk credential account. This is
mandatory for the team member (Non AECOM Employee) to be invited and access

to the project. AECOM.COM or consultants.aecom.com are the only recognised

email addresses that are associated to the AECOM Enterprise Business Agreement
(EBA) and do not require Autodesk registration account.
Once the folder structure is finalised and the platform is ready to use by all the party,
CDE Manager will invite the Design team member to Project BIM 360 Docs. All party
involved in the project should provide their team name list and their role/function to
CDE Manager.
All Models shall be stored in BIM 360 Docs and named in accordance to the “File
Naming Structure” convention as outlined in section 10.1 of this procedure. BIM
Models shall be stored in BIM 360 Docs and located in the specific discipline folder
within the BIM Model folder of the design package. The diagram below illustrates the
method of working on Revit Models where the Central Files are stored on the cloud
servers, edited using Revit, synchronized, shared and consumed as required for
publishing in BIM 360; the CMRL-C4 Common Data Environment (CDE). Models are
to be linked from BIM 360 to the specific discipline folder from cloud server by using
BIM 360 Design collaboration process (see Figure below.)
Figure 4. Medium Trust Design Collaboration
There are three option available in the process of model linking under BIM 360
design collaboration module. They are mentioned below:
1. High Trust Design Collaboration
2. Medium Trust Design Collaboration
3. Low Trust Design Collaboration
We will follow option No.2 Medium Trust Design Collaboration for this project. That is
linking the discipline shared models from the shared folder and not from the
‘CONSUME’ folder. Also, CONSUME folder is not to be deleted or rename.
10.3 Shared Coordinates

A master coordination model file (Master_Coordination_Model.RVT) will be located at

the common reference point in Common Data Environment (CDE). This file will be
developed using the alignment file coordinate system, which will be provided by
CMRL. All involving party should acquire the coordinate system from the master
coordinate model.
All models will use an established Shared Site coordinate system defined by the
Master coordination model. The shared coordinate system will be used for checking
clash detection in Navisworks and for establishing the correct absolute and relative
positions. This will also be used for Geo-referencing the model in real world
coordinates.
Each station project-based point coordinates and its True North Angle will be
established for the stations that are final in term of location with reference to
alignment/Land and will be informed to the team member. They will also be available
in common reference point in BIM 360 Docs.
10.4 Measurement & Symbology System

Basic Architectural Revit template will be available in BIM 360 along with Project Title
block Revit family.
Project will be established using the Metric Units measuring system.
Models shall be linked using the Shared Coordinates set by the project Monument.
Dimensioning tolerances should be set by the CMRL standards or default to industry
standards.
10.5 BIM & CAD Standards
BIM & CAD Standard to comply with CMRL-C405 Standards
Table 15. Standard Reference
Standard Description Uses
BIM Standard DDC-P2C4-05-GN-P-008-A BIM Project Execution Plan
CAD Manual DDC-P2C4/05-GN-P-007-A Project CAD Standard
Procedure Manual TBC Modelling Consistency
British Standard BS EN 19650 – 1 & 2: 2018 Developing Project BEP
International Standard ISO 19650-1 & 2 Developing Project BEP
BIM Forum LOD Specification Guide Developing Project BEP
Source: Various Source
10.6 Workset Naming Convention

Each discipline is responsible to create and place all the model element in the correct
workset before sharing the file. Each discipline should name their worksets for each
model element with their specific discipline code initiated (Refer section XXX) e.g.
Architectural Door = A-Door
Structural Wall = S-DWall
Each discipline will place linked CAD and Revit files into their own worksets. The
worksets should follow CMRL standards (see reference below). The worksets name
should reflect the name of the file being linked. Only one linked model/drawing
should reside in each of the following worksets.

Table 16. Workset Naming

Element Workset Applied Workset Name
Revit Link One Workset per Discipline Revit Link +Links--Revit File Name
CAD Link All DWG Links in a single Workset +Links-DWG
Levels & Grids All Levels & Grids in a single WorkSet +Levels and Grids
IFC One workset per IFC Link +Links--IFC File Name
“Rename ‘WorkSet 1’ to ‘0’ and relocate model objects to the new/appropriate project
worksets.”
‘WorkSet 1’ is a default WorkSet that Revit generates when worksets are first
enabled. When enabling worksharing in a Revit file, Revit creates a system workset.
This workset can never be deleted, only renamed. If this workset is used to contain
model objects, it will cut down on the flexibility of editing and consolidating worksets.
Consider renaming the workset to ‘0’ so that it appears at the top of the workset list.
Use workset ‘0’ as a temporary storage for model objects when it is uncertain to
which workset it needs to be assigned.
Create Link discipline specific worksets. Do not use default Revit Shared Levels and
Grids.
10.7 Clash Detection
Navisworks clash detection is required at project milestones but should only be used
for this purpose or when trackable clash reports are required as part of the project
requirement.
Each discipline will be responsible for exporting their most recent Revit model into an
NWC (Navisworks Cache) file for Navisworks clash detection. This file will not
contain any linked models or CAD links. The file(s) will be saved in the “CDE –
Folder Structure (TBC)” folder with the same naming convention as the parent Revit
file. The NWC file will be created by each discipline’s lead at the request of the BIM
Coordinator. The BIM Coordinator will append these files to create an NWF
(Navisworks Working File) and will provide an NWD (Navisworks Document File) for
all disciplines’ use. Each discipline design teams will be responsible for uploading
their NWC file (as required) to the CDE at the request of the Project BIM Coordinator.
Clash Grades: Clashes found by the software are to be analysed, reviewed and
approved as hard clashed (or major clashes), soft clashes (or minor clashes) and
acceptable clashes in accordance with following and resolved or approved
appropriately.
Grade One Clashes: Grade One Clashes are reported clashes that are considered
critical to the design and construction process as they impact on major design
(structural) elements. These clashes should be rectified within the model as soon as
possible. Grade 1 clashes must be resolved, not approved. Clashes with the
following few example elements are Grade 1:
STRUCTURAL
• Sub-Structure
o Foundations
• Super-Structure
o Structural Columns & Primary Beams
o Structural Floors ( including slabs on grade)
o Structural stairs
o Roof Construction
o Core & Shear Walls

o Shafts & Lift Shafts

MEPF
• Main pipework and ductwork

• Main ducting and cable trays/ladders
• Major MEPF Equipment
• Transportation – elevators, escalators
Civils
• Retaining Walls
• Existing Utilities
• Sub-surface utility ducts & pipe
• Utility Manholes
• Sub-Grade enclosures (e.g. Underground pump-rooms)
Grade Two Clashes: Grade Two Clashes are reported clashes that are considered
important to the design and construction process. These clashes should be rectified
during project progress meetings. Grade 2 clashes may be approved but must be
resolved prior to GFC design issue. Clashes with the following example elements are
Grade 2:
STRUCTURAL
• Secondary structural beams

• Secondary Openings
• Structural bracing
MEPF
• Secondary pipework and ductwork

• Secondary ducting and cable trays/ladders
• Minor MEPF Equipment
ARCHITECTURAL
• Walls
• Doors, Windows, louvres
• Roofing
• Casework
Grade Three Clashes: Grade Three Clashes are reported clashes that while
considered important to the correctness of the model will generally be able to be
resolved in the field and that therefore do not require resolution in the BIM Model.
Grade 3 clashes may remain at approved status.
11. Project Deliverables

BIM models and drawing extracted from the approved BIM models will be delivered
to CMRL as final deliverables.
Table 17. BIM Deliverables
Submittal Item Milestone Due Date Format Notes
All Discipline Models Good For Construction As per Project Schedule RVT DDC
All Discipline Sheets Good For Construction As per Project Schedule PDF DDC
Source: For details on submittal, refer Tender Documents – Section 3 -Scope of Work, Chapter 14 Design Document
Submission requirement (Design Deliverables)

12. Signatory Page

This BIM Execution Plan Guidelines may not be amended except in writing signed by
all parties and shall be executed by authorized representatives of each party. Where
conflicts are found in the BIM, regardless of the phase of the Project, the discovering
party shall promptly notify the party responsible for developing the content (“Author”).
Upon such notification, the Author(s) shall act promptly to mitigate the conflict.
In contributing content to BIM, the Author does not convey any ownership right in the
content provided or in the software used to generate the content. Unless otherwise
granted in a separate license or master agreement, any subsequent Author’s and
BIM user’s right to use, modify, or further transmit the BIM is specifically limited to the
design and construction of the Project, and nothing contained in this Agreement
conveys any other right to use the BIM for another purpose.
Parties to this BIM Execution Plan waive consequential damages, including but not
limited to damages for loss of profits, damages due to errors in the BIM
process/information, loss of revenues, loss of business and of business
opportunities, for claims, disputes or other matters in question arising out of or
relating to this Agreement.
Notwithstanding anything in this Agreement, Architect shall not have control or
charge of and shall not be responsible for construction means, methods, techniques,
sequences or procedures.
Any use of, or reliance on, a portion of the BIM inconsistent with the intent of the
Project or the Author(s) or shall be at their sole risk and without liability to the
Author(s). No party shall have liability from use of BIM beyond uses set forth within
the BIM Execution Plan
Table 18. Representative
Name Role/Function Company Signature
Project Manager AECOM
Project Coordinator
Architecture BIM Coordinator
ST Station BIM Coordinator
ST Viaduct BIM Coordinator
MEPF BIM Coordinator
Michael Daimei DDC BIM Manager AECOM

Appendix A
Abbreviation & Definition
Attribute Non-graphical information associated with objects or data within a Model,
e.g. Specification References, Tag Codes, and Classification Codes.
BEP BIM Execution Plan
BIM Building Information Modelling / Building Information Management
BIM Model -A digital representation of the physical and functional characteristics of a
facility created using BIM software as an object-based 3D Model
BoQ Bill of Quantities
CAD Computer Aided Design
CAD Model 2D or 3D CAD files that contain full-size geo-referenced discipline
specific designs
CDE [Common Data Environment] The single source of information for the project,
used to collect, manage and disseminate all relevant approved project documents for
multidisciplinary teams in a managed process
IFC Industry Foundation Classes. A non-proprietary data interchange format
LOD Level of Detail
LOIN Level of Information Need
MDP Model Development Plan
MEPF Mechanical, Electrical, Plumbing and Fire Protection discipline specialties
within engineering
MIDP Master Information Delivery Plan
Model Generic reference to both BIM Models and CAD Models.
NWC Navisworks Cache File, a cached copy of geometry from native BIM model files
(e.g. .rvt) created on the fly when native geometry is opened in Navisworks; can only
be opened with Navisworks Simulate, Review, and Manage
NWD Navisworks Data File. An NWD is a snapshot of the models in the NWF at the
time of Publishing. It saves all the geometry, overrides, transforms, viewpoints, clash
data, everything. NWD files are small, as they compress
NWF Navisworks File Set. An NWF file contains links to the original native files (as
listed on the Selection Tree) together with Navisworks-specific data, such as review
mark-ups. No model geometry is saved with this file format
TIDP Task Information Delivery Plan
Responsibility Matrix – TIDP & MIDP

Each discipline to generate high level TIDP and DDC BIM Manager to compile the
information to submit to CMRL as MIDP

BIM Execution Plan: Chennai Metro Rail Limited Chennai Metro DDC Phase II Corridor 4 Packages 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BIM Execution Plan: Chennai Metro Rail Limited Chennai Metro DDC Phase II Corridor 4 Packages 5

Uploaded by

Copyright:

Available Formats

BIM Execution Plan

Chennai Metro Rail Limited

Chennai Metro DDC Phase II Corridor 4 Packages 5

Report no. – DDC-P2C4/05-GN-P-08-A

T: +91 44 4965 6666

Prepared in association with AARVEE

© 2019 AECOM Singapore Pte Limited. All Rights Reserved.

Report -08 / Rev.A ii AECOM + AARVEE

1. Project BIM Execution Plan Overview 1

Report -08 / Rev.A iii AECOM + AARVEE

Figure 1. BIM Delivery Team ................................................................................................ 4

Table 1. Project Schedule/ Phases/ Milestones .................................................................... 1

Report -08 / Rev.A iv AECOM + AARVEE

1. Project BIM Execution Plan Overview

Report No. 008/Rev.A 1 AECOM + ARVEE

3. Key Project Contacts

Table 3. Design Team (AECOM + AARVEE)

4. Project Goals/ BIM Uses

Table 4. Goals and BIM Uses

Report No. 008/Rev.A 2 AECOM + ARVEE

4.2 Design Authoring

4.3 Drawing Generation

4.6 Quantity Take-off (QTO)

Report No. 008/Rev.A 3 AECOM + ARVEE

5. BIM Organizational Role

Figure 1. BIM Delivery Team

Report No. 008/Rev.A 4 AECOM + ARVEE

• Generating Task Information Delivery Plan

6. BIM Modelling Scope / Elements / Level of

Figure 2. Illustration of spatial federation strategy by discipline in a building project

Report No. 008/Rev.A 5 AECOM + ARVEE

6.2 Level of Information Need

Report No. 008/Rev.A 6 AECOM + ARVEE

LOD Milestone Description

7. Common Data Environment (CDE)

Table 7. Model Information Exchange format

Report No. 008/Rev.A 7 AECOM + ARVEE

Figure 3. CDE – BIM 360 Docs with Design Collaboration module.

Report No. 008/Rev.A 8 AECOM + ARVEE

8.2 Quality Control Checks

Note: Models should be detached and re-saved as centrals at certain frequencies,

Report -08 / Rev.A 1 AECOM + AARVEE

9. Technological Infrastructure Needs

9.2 Computer & Hardware

Report -08 / Rev.A 2 AECOM + AARVEE

10. Model Structure

(ISSUING ENTITY) (PROJECT) (PACKAGE) (DISCIPLINE) (FILE TYPE) (LOCATION) (NUMBER)

Report -08 / Rev.A 3 AECOM + AARVEE

Table 12. TYPE CODE

File Type for Documents

Report -08 / Rev.A 4 AECOM + AARVEE

Station No. Station Name Station Code

• Power house station Architectural BIM model example: DDC-P2C4-05-ARC-M3-

Report -08 / Rev.A 5 AECOM + AARVEE

to the project. AECOM.COM or consultants.aecom.com are the only recognised

Figure 4. Medium Trust Design Collaboration

10.3 Shared Coordinates

Report -08 / Rev.A 6 AECOM + AARVEE

A master coordination model file (Master_Coordination_Model.RVT) will be located at

10.4 Measurement & Symbology System

10.6 Workset Naming Convention

Report -08 / Rev.A 7 AECOM + AARVEE

Table 16. Workset Naming