7.2.4 Prelim. BIM Execution Plan Final 4

PT.
MASS RAPID TRANSIT JAKARTA

REPUBLIC OF INDONESIA
Construction of Jakarta Mass Rapid Transit Project

(Phase 2) (I), Underground Section - Civil 3; Contract
Package CP203
(19k+641-20k+971)
Preliminary BIM Execution Plan

DOC. NO. APPENDIX 7.2.4
OBAYASHI-WIJAYA KARYA-JAYA KONSTRUKSI JV

JV Office: Jl. Pancoran Timur II No. 3, Jakarta 12780;
Phone: +6221 7948944; Fax: +6221 7973670
Table of Contents
1. BIM Project Execution Plan Overview…………………………………………………..3

1.1 BIM References...........................................................................................3
1.2 Purpose........................................................................................................3
1.3 Abbreviations...............................................................................................4
1.4 Glossary of terms.........................................................................................4
2. Project Information………………………………………………………………………..6
2.1 Project BIM Scope.......................................................................................7
2.2 Project Schedule / Phases / Milestones.......................................................7
3. Key Project Contacts……………………………………………………………………...8
4. Project Goals / BIM Uses…………………………………………………………………9
4.1 Agreed BIM Goals / Objectives:...................................................................9
5. Organizational Roles / Staffing…………………………………………………………9
5.1 BIM Roles and Responsibilities....................................................................9
5.1 Key BIM Role Definition.............................................................................10
5.2 Model Author..............................................................................................11
5.3 BIM Organization Chart..............................................................................12
6. BIM Process Design……………………………………………………………………..12
6.1 Collaboration Strategy................................................................................12
6.2 Common Data Environment.......................................................................13
6.3 Model Revisions and Suitability Status.......................................................14
6.4 Virtual Design Review (VDR) strategy........................................................15
6.5 Model Comparison.....................................................................................16
7. BIM Information Exchanges…………………………………………………………….16
7.1 Information Exchange Strategy..................................................................16
7.2 LOD Model Responsibility Matrix:..............................................................16
7.3 Model Exchange Formats..........................................................................18
7.4 Design Authoring Model Exchange Schedule............................................18
7.5 IFC Federated Model Exchange Schedule.................................................19
8. BIM and Facility Data Requirements…………………………………………………..19
8.2 BS1192 Project Parameters.......................................................................19
8.3 COBie, Data Validation & Information Exchange.......................................20
8.4 Element Classification................................................................................20
9. Collaboration Procedures……………………………………………………………….20
9.1 Creation of Design Authoring Models.........................................................21
9.2 Sharing of BIM Models and Information.....................................................21
Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 1

9.3 BIM Project Meetings:................................................................................21
9.4 BIM Issues / Comments / Clashes.............................................................21
9.5 Clash Mitigation strategy............................................................................22
10. Quality Control……………………………………………………………………………25
10.1 Overall Strategy for Quality Control........................................................25
10.2 Project Set Out.......................................................................................25
10.3 Quality Control Checks...........................................................................25
11. Technological Infrastructure Needs……………………………………………………26
12. Standard, Methods and Procedures……………………………………………………
26
12.1 File Naming Structure.............................................................................27
12.2 3D/2D Model Geometry Naming.............................................................28
12.2.1 Model Geometry Element – With Metadata Associated......................28
12.2.2 Revit Type Naming..............................................................................28
12.2.3 Non Model Geometry Elements - No Metadata Included....................30
12.2.4 Material Name.....................................................................................31
12.2.5 Material Image File Name...................................................................31
12.3 Model Breakdown...................................................................................32
12.4 Model Size..............................................................................................32
12.5 Modelling Requirements.........................................................................32
Appendix A Model Progression Delivery Table

Appendix B COBie Data Shedule
Appendix C Clash and Spatial Coordination Strategy
Appendix D REVIT Technical Guide
Appendix E AECOsim Technical Guide
Appendix F BIM Linear Workflow

1. BIM PROJECT EXECUTION PLAN OVERVIEW
This Preliminary BIM Execution Plan (BEP) outlines the overall vision, agreed
project objectives along with implementation details for the team to follow through the
project delivery phase for the Mass Rapid Transit Jakarta Project.
To effectively integrate BIM into a project, it is important for the project team to develop
a detailed implementation. The overarching goal of the BEP is to stimulate and direct
additional communication and coordination by the project team members and client
during all phases of the project.
Each BEP is unique to the project for which it is created and is not be used for anything
other than the project and purpose for which it is intended.
This BEP provides the protocols by which all project stakeholders will deploy and
utilize best practice Building Information Modelling processes, technologies and
software throughout the life of the project. Stakeholder and individual roles and
responsibilities are defined in these protocols. The intent is to promote full
understanding by all of the BIM project processes, requirements and deliverables.
The protocols will allow the stakeholders to utilize the Building Information Model(s) as
a collaborative resource during the nominated project stages.
Standards and protocols will provide uniformity in deliverables derived from the
Building Information Model(s).
Some fields and sections of this document are deliberately left blank as the information
may not have been available at the current revision date of the document or are to be
completed at the outset.
1.1 BIM References

This document shall be read in conjunction with the following BEP reference
documents
 Mass Rapid Transit (M) Employer’s Information Requirement (EIR)
 Singapore BIM GUIDE Version 2.0
 BCAs Essential BIM Guides
 BIM Forum LOD Specification 2016
 BS1192 and PAS 1192 Parts 2 and 4 Abbreviations, Glossary of terms and
Project roles
1.2 Purpose
The intent of this Preliminary BIM Execution Plan (BEP) is to provide a framework that
will let OWJ JV, Sub-contractor, and other interfacing parties to deploy building
information modelling technology and best practices on this project faster and more cost-
effectively throughout the design phase.
The intention of this document is to continually evolve and be updated with
technological developments and as required where the project team deem appropriate
through the design phase of the works.
This plan delineates roles and responsibilities of each party, the detail and scope of
information to be shared, relevant business processes and supporting software and shall
be read in conjunction with the International Best Practice BIM Guides.
The objectives of this BIM Execution Plan are:

 To ensure that MRTJ’s BIM requirements as set out in the MRT Jakarta
Phase 2 Employer’s Requirements Appendix 5 are adhered to.
 To ensure the Building Information Model is a shared resource for reliable
and collaborative decision- making, by facilitating ease of access and
enabling clear communication of how the Building Information Model is
created and accessed throughout its project life.
 To define the standards, settings and best practices that ensure delivery of
high quality and uniform drawing output across the entire project.
 To ensure that digital BIM files are structured correctly to enable efficient
data sharing whilst working in a collaborative environment across multi-
disciplinary teams both internally and in external BIM environments.
When working as a project team, communication is paramount. This guide looks
to ensure that all parties fully understand what is expected of them and others.
1.3 Abbreviations
AIM Asset Information Model
BEP BIM Execution Plan
BIM Building Information Modelling/Management CAFM Computer-
Aided Facilities Management EDMS Electronic Document
Management System
EIR Employer’s Information Requirements (document) FM Facilities
Management
GIS Geographical Information System
IFC Industry Foundation Classes
LOD Level of Development
MPDT Model Production Delivery Table PIM Project Information Model
PM Project Manager
TBC To Be Confirmed
WIP Work in Progress
1.4 Glossary of terms
4D
A 3D representation of an asset with the element of time included to enable
simulations.
5D
A 3D representation of an asset with the element of time and cost
included/linked to enable simulations, commercial management and earned
value tracking to take place.
6D
A 3D representation of an asset which includes data which enables the
efficient management, operation and maintenance of the completed asset.

Asset Information Model (AIM)
Information model used to manage, maintain and operate the assetEP
The BEP is to demonstrate the Project Stakeholder’s proposed approach,
capability, capacity and competence to meet the EIR. It is assessed prior to
the appointment of any stakeholder
Building Information Modelling (BIM)

Process of designing, constructing or operating a building or infrastructure
asset using electronic object-oriented information
BIM Model or BIM Model file

A 3D model file containing hierarchically defined objects to which data can be
attributed
COBie (Construction Operation Building information exchange)
Structured asset information for the commissioning, operation and
maintenance of a project often in a neutral spread sheet format that shall be
used to supply data to the Employer or operator to populate decision-making
tools, facilities management and/or asset management systems
Contribution
The expression, design, data or information that a party in the Project, creates
or prepares, and shares with other parties in the Project for use in or in
connection with a BIM Model.
Data
Information stored but not yet interpreted or analyzed
Document
Information for use in the briefing, design, construction, operation,
maintenance or decommissioning of a construction project, including but not
limited to correspondence, drawings, schedules, specifications, calculations,
spread sheets
Drawing
Static, printed, graphical representation of part or all of a project or asset
EDMS
Single source of information for any given project, used to collect, manage and
disseminate all relevant approved project documents for multi-disciplinary
teams in a managed process. This is commonly a cloud-based SaaS
(Software as a Service) solution synchronized with party servers to host the
PIM.
Element or NRM1 element

A grouping of measurable objects as defined in NRM1. Elements are
categorized by grouped elements and further categorized by sub-elements
Employer’s Information Requirements (EIR)

Tender document setting out the information to be delivered, and the
standards and processes to be adopted by the Project Stakeholders as part of
the project delivery process
Exchange BIM model file

An open and neutral data format for BIM models
Federated BIM model file

A file combining all available latest BIM models into a single BIM model for
reference
Graphical data
Data conveyed using shape and arrangement in space
Model Production Delivery Table (MPDT)

Identifies the LOD required for a specific BIM object at a given project work
stage and the Model Author responsible for the object’s inclusion
Native BIM model file

The primary data format used by the BIM model authoring tool to create BIM
models
Non-geometric attribute
A specification that defines a property of an object
Object or BIM Object

A repository of information that holds data regarding 2D and 3D geometry
description of the actual product or component
Principal Agreement
The agreement or contract for services, supply and/or construction which a
party has entered into for the Project
Project BEP
The Project BEP is the document defining standard methods and procedures
adopted during the contract in order to meet the objectives and requirements
set forth
2. PROJECT INFORMATION
Project Owner: PT. Mass Rapid Transit Jakarta
Project Name: Construction of Jakarta Mass Rapid Transit Project (Phase2)
Project Location and Address: Jakarta Raya
Contract Type / Delivery Method: Design and Build
Construction of the Jakarta Mass Rapid Transit Project Phase 2 comprises ±7.8
km of twin track rail, underground and at grade, with eight stations and 1 depot.

There are three construction contracts (Design and Build) under this Bidding
Process which are CP201 ~ CP203. This technical Bid is for the Underground
Section Package CP203 (hereinafter referred to as the Project) which has the
following characteristics:
 Project start point : 19k+641
 Project end point : 20k+971
 Project length : 1,330 km
 Scope of work :
All the civil and structure works of underground section including
• 2 underground stations : Glodok Station and Kota Station; with mechanical
and electrical works associated with station building
• Bored tunnels : Twin tube tunnels:
Mangga Besar Station – Glodok Station – Kota
Station
The Project alignment key plan and stations layout are as shown below.
Kota Station.
Glodok Station.
Kota Scissors Crossing Area.
Figure 1-1 General Arrangement of CP 203
2.1 Project BIM Scope

The highlighted goals as defined in MRTJ’s ER can be further expanded upon
exploration and agreement during the initial phases of the project through BIM workshops
and alignment activities; subject to the Authority’s acceptance. What is highlighted in this
section is a description of each of the topics; it is not intended to define an agreed scope.
2.2 Project Schedule / Phases / Milestones

The following table describes the key end of stage milestones as per the overall design
programme.

PROJECT PHASE / MILESTONE MILESTONE REMARKS
DATE
Concept Stage
Preliminary Design Submissions – Part 1
Launch Shaft and Bored Tunnels
Pre-Final Design Submission
Final Design Submission
T2 Cut & Cover Tunnels, Station & Interchange
Pre-Final Design
Final-Design
T5 Station & Interchange
Preliminary Design Submissions – Part 2*

T5 Cut & Cover Tunnels and M&E Systems Design
Preliminary Design Submissions – Part 2*

Pre-Final Design Submission
Pre-Final Design
Final Design Submission
Final Design
3. KEY PROJECT CONTACTS

List of lead BIM contacts for each organization on the project. Additional contacts
can be included later in the document.
Role Organization Contact Name E-Mail
BIM Manager
C&S BIM Coordinator
MEP BIM Coordinator
Architectural BIM Coordinator

4. PROJECT GOALS / BIM USES
4.1 Agreed BIM Goals / Objectives:
The following table groups the focus and priority around various BIM Goals and
Objectives in relation to the Design and in the context of delivering the MRT project.
PRIORITY GOAL DESCRIPTION POTENTIAL BIM USES

(HIGH/ MED/ LOW)
High Greatly Improved overall Design Authoring Design Reviews
Design Coordination and 3D Coordination Model Audits
interface management Existing Conditions Modelling
Site Analysis
MEDIUM Improved Supply Chain from 3D Coordination QPD Submissions
design through to Record Modelling
LOW construction
More accurate capture of Asset Management
handover information to Space Management / Tracking
operations team
The following section details the application of BIM uses in relation to these
overarching goals described above.
5. ORGANIZATIONAL ROLES / STAFFING

5.1 BIM Roles and Responsibilities
All stakeholders have the responsibility to follow the intent and procedures as detailed
in the BEP and referenced documents to achieve the BIM goals.
The required roles and responsibilities associated with this project are defined below:
Defined Role Responsibility in BIM BIM Responsibility

Management Plan (BEP)
BIM Manager Development
Manages and coordinates project Overall Model progression overview.
execution and BIM to meet Participation in BIM reviews. Ensure
procurement strategy and cost project team is using BIM effectively.
containment.
DDC Project BIM Coordinate BIM use on project, Oversight, Management Execution,
Manager determine schedule of use, sharing Quality and Model Exchange
activities, quality control, modelling
responsibilities and documentation
in BEP.
BIM Coordinator Assist BIM Manager Implementing BIM Manager
instructions within DDC Team.
Liaising with BIM Manager
Civil Team Engineering – formulate with BIM Data Development, Modelling and
Manager. Map BIM use for Civil Model Exchange
design – determine BIM use for
simulations, analysis and
documentation. Identify tools and
processes.

Defined Role Responsibility in BIM BIM Responsibility
Management Plan (BEP)
Structural Team Development– formulate with BIM
Engineering Modelling and Review, Model
Manager. Map BIM use for Exchange
structural design – determine BIM
use for structural simulations,
analysis and documentation
Identify tools.
MEP Team Engineering – formulate with BIM Data Development, Modelling and
Manager. Map BIM use for MEP Model Exchange
design – determine BIM use for
simulations, analysis and
documentation. Identify tools and
processes.
Architectural Design Execution – formulate with Room and Asset ID development,
Team BIM Manager. Map BIM use for Modelling and Review, Model
architectural design. Assist in Exchange
defining the data structures
required for capture of spatial
asset information.
Contractor Receive or help create BIM for Use of model, Review, Model
constructability and handover for Exchange, Capture of asset data
field use. Determine Interference requirements for handover
checking responsibility.
Subcontractor Off-Site Fabrication – formulate Use of model, Modelling and
and/or Fabricator with BIM Manger and designer. Integration. Digital fabrication
(as appropriate) Map BIM use for fabrication and
shop drawing design.
Determine BIM use for simulations
of maintenance space analysis
and documentation. Identify tools.
5.1 Key BIM Role Definition

There are three key BIM roles for the project defined above, ie the Project BIM
Manager and BIM Coordinators. The following provides a detailed description of
each of the roles.
5.1.1 BIM Manager
The project BIM manager will be responsible for the following:
 Responsible for creating and maintaining the respective Inter(D) project
BEP aligned to the Employers EIR
 Responsible for the management and delivery of a coordinated Project
Information Model. (PIM)
 Responsible for the design federated model
 Responsible for the management and delivery of a coordinated Inter
Model for integration into the PIM.
 Responsible for the coordination and integration of models by MRT direct
appointed specialist consultants
 Responsible for the design interface and coordination of models between

packages
 Responsible for confirming overall design Consortia deliverables to
enable integration and coordination of information within the PIM
 Responsible for managing information production and approvals for the
design Consortia
 Responsible for confirming status and approving BIM information issued
within the EDMS for the design Consortia
5.1.2 BIM Coordinators

The individual discipline BIM coordinators will be responsible for the
following:
 the production of design outputs related to a discipline-specific package
 issuing their team’s approved information within the project EDMS
 production of deliverables in compliance with agreed standards and
methods as defined in the EIR and Project BEP
 managing spatial coordination for their team
 Resolving and managing the removal of design clashes within the models.
 Create BIM Design Models and Documentation
 Define discipline-specific BIM uses including analysis
 Coordinate between BIM modelers and interfacing design consultants
 Coordinate with contractor and subcontractors where appropriate
 Ensure Modelling Quality Control in line with the BEP
5.2 Model Author

The model author shall be any Stakeholder’s lead team discipline modeler
involved on the project. Each Model Author’s responsibility is to facilitate the BIM
use goals of the project, including:
 Modelling elements as determined within the project BEP and associated
documents.
 Utilize internal coordination and clash detection procedures as part of the normal
modelling process.
 Communicating issues back to stakeholders.
 Manage spatial co-ordination on behalf of a task /design team
 Propose resolutions to co-ordination clashes

5.3 BIM Organization Chart
6. BIM PROCESS DESIGN
The following sections sets out the requirements for the standard workflows for
each key uses of BIM across the project as agreed in section 4.
6.1 Collaboration Strategy
The overall projects BIM collaboration strategy is developed around the
principals as defined in British Standard BS1192 with the goal of developing and
managed PIM.
 Figure 6.1 below illustrates the standard BIM collaboration process to be
adopted between disciplines.
 Bentley Project wise will form the core element of the Common Data
Environment (CDE).
 Frequency of each model exchange is detailed in the Model Exchange
Schedule section of this BEP for each discipline, indicating the Weekly shared
model requirements and scheduled Virtual Design Review (VDR) dates.
 Each discipline team shall take ownership of their Working models (WIP) and
information.
 Models are to be reviewed and checked against the requirements as set out in
the Quality Control Section of this BEP.
 The federated model will be compiled from only the models which have reached
the SHARED State. This will form the basis of all comments will created,
collated and tracked.

 All comments must follow the specific project naming convention to allow for a
managed structure and a Status to distinguish the relevance of the comment
(See Section 9.5)
Figure 6.2 below details a project wide CDE workflow based on the MRT EIR
workflow, utilizing the use of a Working, Shared, Published and Archived state,
mirroring the folders described above. This principal is to be adopted as the
standard method of sharing information across contracts.
6.2 Common Data Environment

All drawings and Models will be managed using a Common Data environment
approach which complies to the British Standard BS1192. The principals of BS1192
are further defined below.
The Following structure describes a High level BIM CDE folder structure, the
principles of which will be adopted on the project.
Folder Structure
BIM CDE Purpose Type of Discipline
Document
1_SHARED
PDF
IFC
RVT
DGN Arch
Struc
2_PUBLISHED
3_ARCHIVED
4_WIP
A Shared folder is the central repository for all the LATEST design information
and should be used for all other additional BIM uses required on the project as
defined below.
Figure - Shared area and BIM uses

6.2.1 Work in Progress (WIP)
 The WIP State / area of the CDE will be used to hold unapproved or
non- verified design data used by DDC design disciplines only.
 The organization is responsible for the quality of the WIP information
and should ensure that appropriate checking and review processes
are in place as defined later in this BEP.
 Working models should be given the correct suitability code and
version number in accordance with the Model Revision and Suitability
Status as defined in this BEP.
 As the data continues to be updated in the WIP area options should
be indexed to indicate minor revision changes, as demonstrated
below.
Example Minor Model MRT-WK-STR-3D-0001.rvt P01A P01B

Revision
6.2.2 Shared Area

 Each design team discipline will ONLY reference from the latest
Shared folder to ensure the latest design information is being used as
reference data.
 Models shall be SHARED as indicated in the model exchange table.
 All models are to be verified as defined in the BEP prior to transmitted
being copied into the SHARED Folder
 All Shared Models shall have the appropriate Model Status and
Version reported as embedded project parameters as well as CDE
metadata.
6.2.3 Weekly Information Workflow from WIP to SHARED

The following diagram shows how a native Revit BIM file transitions
from a work in progress Model (WIP) to a SHARED document for use in
Coordination.
BIM BIM WIP models

Copy into
Coordinator Shared Folder Notification to BIM Manager Checks Manager links to new
verifies IFC with correct team Files Updates shared files
and RVT version/status Federated in CDE
Model
6.2.4 Bi Weekly Information Workflow from WIP to SHARED

The process is the same as above except that the models are to be
transmitted via EDMS to MRT, the Project Manager and interfacing contracts.
6.2.5 Published
This folder / State is for validated design output issued to the Client for
specific end of stage milestones for example Pre-Final, Tender or
Construction.
6.2.6 Archived

This folder / State will maintain the project history for knowledge and
regulatory and legal requirements. Access to this folder will be read only to all.
6.3 Model Revisions and Suitability Status

To help facilitate the sharing of models in the CDE the use of a model Version
and “Suitability” parameter as described in BS1192 will be implemented. This allows
any given user the ability to instantly understand the context with which a model has
been issued or shared with them.
Descriptor Code Description

Suitability S0 S1 S2 S3 S4 D1 D2 Initial Status of a Working Model Issued
D3 A B AB for Coordination
Issued for Information
Issued for Internal Review and
Comment Issued for Construction
Approval (Submission) Issued for
Costing
Issued for Tender
Issued for Contractor Design Issued for
Construction
Partial Sign Off (for construction with
A1 A2 A B1 B2 B TBC minor comment)
of As-Built Handover
Revision 1st Version a Working Model 2nd
TBC Version of a Working Model 1st Shared
Model (pre-construction) Next Version of
Working Model
2nd Shared Model (pre-construction)
1st Version of Working Model (post-
construction) 1st Shared Model (post-
construction)
2nd Construction Issue
 All models in the CDE must contain a model Version and “Suitability” A, B, C
parameter embedded in the native file, in the IFC export and as meta data
within the CDE and EDMS.
 All models should have the correct suitability set to ensure models are shared
Fit for purpose.
6.4 Virtual Design Review (VDR) strategy

In addition to the collaborative sharing of native design authoring files the
project will compile and maintain a Master federated VDR model. This model is to
be iteratively created, revised and used throughout its lifecycle. It will form the basis
for all milestone VDRs as outlined further below.
The aim of the federated VDR model is to provide a single common view of the
design in which all models are collated and reviewed collectively with a view to
resolving any design coordination issues that may arise prior to issue of a drawing
deliverable package.
The following workflows describes the standard process that will be adopted.

Figure 6.4 Master Virtual Design Review
The Federated VDR model will be submitted to MRT via the EDMS as:
 Autodesk Navisworks NWD file format and;
Both these models will be compiled on the IFC file exports of the native design
authoring models.
6.4.1. VDR Clash Migration Strategy
Clashes are inevitable. It is our requirement as a project team develop a
Coordinated Services Model for use in the construction phase of the project.to
identify key areas of design that require further coordination in order to work.
 Clashes or coordination Issues shall be created using the Arup JIRA system
in the design authoring platforms or via a specific model check as part of a
VDR.
 A VDR with appropriate level of Clash mitigation check is required every two
weeks and at least one week prior to an end of stage milestone. Further
VDRs will be incorporated into the design program to align with the CSD
model development and sign off.
 All Issues are to be uploaded and assigned appropriately within in the Arup
JIRA.
 Our target is for any Assigned Issue to be responded to within 3 working
days.
6.5 Model Comparison

At each stage of the above two processes that require a comparison between both
the Record Model and As-Built Contractor model, a Comparison will be conducted using the
Published IFC deliverables. This will provide a comparison against the physical volumetric
geometry differences as well as any agreed data fields such as defined in this BEP.
7. BIM INFORMATION EXCHANGES

7.1 Information Exchange Strategy
 The frequency of model exchanges to the shared area is as per the Model
Exchange Schedule detailed in this section.
 Models are to be exchanged in both native and IFC format.

 Prior to being exchanged, models are required to be validated and approved by
the designated individuals (See Section 10).
7.2 LOD Model Responsibility Matrix:

The Level of Development (LOD) Model Progression Development Matrix (MPDT) in
Appendix A describes our standard project delivery.
Collaborative model development:
Model Element Authors (MEA) are responsible for developing each Model
Element, at the end of each phase of the project, to a minimum Level of
Development (LOD) as described in the BIM Forum Level of Development
Specification 2016. At different stages of the project there is a Level of
Development (LoD) required in the modelled elements to accurately describe
the Building Information Model/s at that stage. It is important to note that LOD’s
are not defined by design stage and that at any given stage a model may
consist of multiple elements all of which are at differing stages of development.
A summary of LOD and definitions is set out in the table below. If there is
conflict between the table below and BIM Forum Level of Development
Specification (2016) the latter takes precedence:
LOD Example – Floor Structural Frame

The Model Element may be graphically LOD100
represented in the Model with a symbol or other Optional 2D geometry, generic column
generic representation, but does not satisfy the element with cost/m3
requirements for LOD 200. Information related to
the Model Element (i.e. cost per square metre,
tonnage of HVAC, etc.) can be derived from other
Model Elements.
The Model Element is graphically represented LOD200

within the Model as a generic system, object, or Generic geometry, generic/approximate
assembly with approximate quantities, size, size/shape/location
shape, location, and orientation. Non-graphic
information may also be attached to the Model
Element. At this LOD elements are generic
placeholders. They may be recognizable as the
components they represent, or they may be
volumes for space reservation. Any information
derived from LOD 200 elements must be
considered approximate.
The Model Element is graphically represented LOD300
within the Model as a specific* system, object or Design Intent geometry, specific
assembly in terms of quantity, size, shape, size/shape/location
location, and orientation. Non-graphic information
may also be attached to the Model Element. The
quantity, size, shape, location, and orientation of
the element as designed can be measured
directly from the model without referring to non-
modeled information such as notes or dimension
call-outs. The project origin is defined and the
element is located accurately with respect to the
project origin. *
Specific as per the extent required to fully
communicate the final design intent.

LOD Example – Floor Structural Frame
The Model Element is graphically represented LOD350 Shop Detailing geometry,
within the Model as a specific system, object, or specific size/shape/location
assembly in terms of quantity, size, shape,
location, orientation, and interfaces with other
building systems. Non- graphic information may
also be attached to the Model Element.
Parts necessary for coordination of the element
with nearby or attached elements are modelled.
These parts will include such items as supports
and connections. The quantity, size, shape,
location, and orientation of the element as
designed can be measured directly from the
model without referring to non-modelled
information such as notes or dimension call-outs.
The Model Element is graphically represented LOD400 Fabrication geometry, Actual
within the Model as a specific system, object or model used for direction fabrication.
assembly in terms of size, shape, location,
quantity, and orientation with detailing,
fabrication, assembly, and installation
information. Non-graphic information may also be
attached to the Model Element.
An LOD 400 element is modelled at sufficient
detail and accuracy for fabrication of the
represented component. The quantity, size,
shape, location, and orientation of the element as
designed can be measured directly from the
model without referring to non-modelled
The Model Element is a field verified LOD500 Record geometry, modelled as
representation in terms of size, shape, location, constructed, specific size/shape/location,
quantity, and orientation. Non-graphic information with required COBie parameters.
may also be attached to the Model Elements.
7.3 Model Exchange Formats
Deliverable Stakeholder Software Version Native Format Exchange

Format To CDE
Design BIM Architecture Revit 2017 .rvt .rvt, IFC
Authoring
Structures Revit 2017 .rvt RVT, IFC
Building Services Revit 2017 .rvt RVT, IFC
Civil – Bored Open Building Bentley .dgn DGN, RVT, IFC,

Tunnel OpenRail iModel
Civil - Cut and .dgn
Cover
Alignment Bentley Open rail, Open .dgn DGN, IFC, iModel
Building

Deliverable Stakeholder Software Version Native Format Exchange
Format To CDE
BIM Design All disciplines Naviswork 2017, Bentley IFC IFC, NWD,
Coordination Navigator NWF, NWC imodel
iModel
BIM Checking / All disciplines Naviswork 2017, Bentley IFC N/A

Review / Navigator NWF, NWC
Validating iModel
models for CDE
Asset & All disciplines .XLS

Facilities
Management
7.4 Design Authoring Model Exchange Schedule

Discipline Concept Prelim Pre-Final Final Tender / Contract Construction
Design Design
Alignment Fortnightly Fortnightly Weekly (Monday) Weekly Weekly (Monday) As Required

(Monday) (Monday) (Monday)
Structures Fortnightly Fortnightly Weekly (Monday) Weekly Weekly (Monday) As Required
Building Fortnightly Fortnightly Weekly (Monday) Weekly Weekly (Monday) As Required
Services (Monday) (Monday) (Monday)
Civil Fortnightly Fortnightly Weekly (Monday) Weekly Weekly (Monday) As Required

7.5 IFC Federated Model Exchange Schedule
Discipline Concept Prelim Pre-Final Final Tender / Construction

Design Design Contract
Alignment Fortnightly Fortnightly Weekly Weekly Weekly As Required

(Monday) (Monday) (Monday) (Monday) (Monday)
Structures Fortnightly Fortnightly Weekly Weekly Weekly
(Monday) (Monday) (Monday) (Monday) (Monday) As Required
Building
Services Fortnightly Fortnightly Weekly Weekly Weekly As Required
Civil Fortnightly Fortnightly Weekly Weekly Weekly As Required


8. BI
M AND FACILITY DATA REQUIREMENTS
The section defines the overall master project data requirements.
8.1 LOD Information / Data Definition
The following project specific data requirements will be required to be added at an
elemental level to help verify audit development of model objects in isolation to the
model itself. This will provide useful in the context of managing the development of
the BIM through Construction.
These requirements are in addition to the COBie data requirements defined in the
following sections.
Parameter Name Defined Values Notes

Element LOD 100, 200, 300, 350, 400, Exported From Revit using correct IFC
500 Mapping
ST Number ST01 Submitted as part of which package and
amendment submission
Element Suitability A (Issued for construction) Suitability as per model codes
Is Constructed True / False
RFI Number Using project coding To track elements to associated RFIs
Each of the above parameters are to be added to ALL authoring platforms and be
included in the IFC export.
8.2 BS1192 Project Parameters

As part of utilizing the BS1192 method of Sharing design information the following
project parameters will be required to be present in ALL authoring platforms and
IFC files that are Shared.
Parameter Name Revit / AECOsim IFC
Model Name Added as Shared Parameter in Exported From Authoring

Project Information. platform using correct IFC
Mapping
Model Version As Above As Above
Model Suitability As Above As Above
BIM Coordinator As Above As Above
For more information on the process required to implement this capability refer to
Appendix D.
8.3 COBie, Data Validation & Information Exchange

All Models are required to be setup to export IFC COBie Parameter Sets as
defined in the EIR and described in detail in Appendix B– COBie Schedule.
Appendix B will detail what data is required, at which stage, who is the originating
author and whom will be responsible to update throughout the projects lifecycle.
8.4 Element Classification

Each model element must include the correct classification code as defined in UniClass
2015. Use of this classification system as part of the Model delivery matrix will be adopted.

However there maybe additions that need to be proposed to further describe the projects
overall scope.
This information is intended to assist in model validation and identification,
potential costing as well as assist in any COBie data drops.
All Models are required to be setup to export IFC COBie Parameter Sets as defined
in the EIR and described in detail in Appendix B– COBie Schedule.
Appendix B will detail what data is required, at which stage, who is the originating
author and whom will be responsible to update throughout the projects lifecycle.
Classification Project Minimum required Example

System Stage Level
Uni Class 2015 Prelim Level Two EF_20_05 Substructure
EF Elements Table
Level Three EF_20_20 Beams
Level Three EF_25_10 Walls
Sy Systems Table Pre Final Level Two Ss_20 Structural Systems
Onwards
Level Three Ss_20_05 Substructure Systems
Level Four Ss_20_05_65 Piling Systems
Level Five Ss_20_05_65_24 Precast Driven
Piles
Pr Products Table Final Level Two Pr_20 Structure and General Products
Onwards
Level Three Pr_20_76 Sectional Products
Level Four Pr_20_76_70 Rail Track and
Ancillaries
Level Five Pr_20_76_70_12 Check Rails
Pr_20_76_70_15 Conductor Rails
9. COLLABORATION PROCEDURES
The following section sets out the key steps or procedures required to meet the
projects overall collaboration strategy and approach as define above.
9.1 Creation of Design Authoring Models
All models should be created using the specific requirements set out in this BEP
and accompanying technical appendices. Particular attention should be paid to the
following:
 Project Set Out
 Project Parameters
 IFC Export Setup
 Linking of SHARED BIM information only. (As Shared within the CDE)
9.1.1 Discipline Specific Coordination Views

Coordination Views help assist each discipline in respect to what
information has been specifically shared with a purpose of coordination. Please
refer to the settings in the technical appendices.
9.1.2 Auditing of BIM Models and Information

All design authoring Models and IFC Models should be regularly audited

prior to Sharing with other parties for coordination. Key aspects to audit for are:-
 Correct Model Version and Suitability
 Close / Save View Set correctly
 Model Element Classifications Set
 Coordination Views Defined as agreed
 IFC Model Exported Correctly
 Required data for each stage is present
 All models elements present as defined in Model matrix.
9.2 Sharing of BIM Models and Information

The sharing of BIM Models as part of the projects BIM Strategy is intended to
be controlled and fit for its intended use. A model issued for Information should be
clearly specified so. The following steps should be followed in order to help
facilitate this aim.
 Design Authoring Files to have the correct Version and Suitability added
prior to uploading and transmitting via the project EDMS platform
 IFC models to have the correct Version and Model Suitability added via the
project parameters as defined in this BEP and verified they are correct in the
IFC export.
9.3 BIM Project Meetings:
MEETING TYPE FREQUENCY PARTICIPANTS

BEP Kick-off Workshop ALL
BEP Review Meetings As Required ALL
VDR Design Review As Set out in the VDR Program below ALL
Meetings
BIM Workgroup Meeting Monthly BIM Leaders
Project wide BIM Task Monthly or as defined by MRT Project BIM

Group Meetings Manager

9.4 BIM Issues / Comments / Clashes
BIM WIKA’s BCF based MRT Issue Tracker will be used to hold the projects
master list of Issues and Comments. This will provide functionality to link both
design authoring and model review tools together around a single project database
of design issues and clashes associated to the development of the BIM Model.
A PDF report along with a Master BCF zip file will be available to review
progress at key points in the programme.
All issues and comments will have specific naming conventions to allow for a
managed structure and a Status to distinguish the relevance of the comment.
Comments will be captured up to and including the appropriate VDR in the program.
This will allow tracking of all comments throughout the project. The following is
the format in all comments will be captured.
Type Organization. Date Initials Seq. No.

CLS - XXX - 17.08.25 - CV - 01*
Example: CLS-BIMWIKA-17.08.25-CMP-01
* indicates that the sequence number resets to zero each day
The table below defines the specific types of comment which will be captured.
Type Description Notes
RFI Request For Information EG Usually created via an EDMS RFI Mail type. A BIM
Used to query an aspect of Issue can be attached as part of the RFI
the model
REV Review Comment Used to capture general overview of a model /
discipline review.
DSG Design Comment Used if Issue requires design/engineering solution or
Input
NON Non Compliance Used to notify areas of the model which do not meet
specific project checks/audits.
CLS Clash All general Spatial / coordination conflicts will be given
this type code.
9.5 Clash Mitigation strategy

The shared models are to be combined together into a federated project model
file to aid confirmation and coordination of the design development and to provide a
platform for clash detection activities and tracking of progress and project
comments within a 3D environment. These federated models will be used in the
scheduled VDR’s in section 9.4 of this BEP.
The requirements set out below define the level of accuracy to which the
models will be reviewed during the VDR process. This approach is centred on
refining the overall spatial coordination such that when we reach Contract
documentation there is an acceptable CSD Model.
Following a review each collision will be assigned a rating and owner who will
be required to provide an adequate response prior to the next review. The level of
collision reporting carried out during each VDR will be as specified within the
schedule and should be appropriate to the stage of the design development.
9.5.1 Tier One Clashes and Spatial Coordination Strategy

The first phase of the coordination process will focus on the definition of
clear spatial strategy that ensures that clear volumes are allocated in the BIM
to provide clear direction and containment for the MEP model to be developed

against. This will also provide future proofing for system wide contracts such
as Baggage Handling that will not be determined until long after the tunnels
contract is complete.
Tier One Clashes are reported clashes that are considered critical to the
design and construction process. These clashes have been assigned the
highest priority and have the biggest impact in either design or construction. In
addition to physical clashes at this stage there are also a series of key spatial
coordination principals that will be reviewed.
This Tier will be used as the expected minimum level of coordination
within the BIM at the completion of Preliminary:
 All Architectural Structural elements and the Structural Consultants
Structural Model
 All MEP systems are to be checked for Self Clashing. Ie a duct clashing
with a duct
 Major Mechanical Ductwork and Piping vs. Structure (Columns, Beams,
Framing, etc.)
 All Beam clashes to be reviewed by Structural engineer
 All Equipment and their applicable Clearances vs. Structure (Columns,
Beams, Framing, etc.)
 Plumbing Piping vs. Electrical Equipment (ie Water pipes running over
Boards)
 Clear Space Requirements vs. Door
Concept Prelim Pre-final Final Contract

Stage
Item
Arch Struc Vs Struc √ √ √ √
Ductwork vs √
Ductwork
Pipework vs √
Pipework
Cable Tray vs Cable √
Tray
Spatial Zones √ √
Defined
Bespoke Clash √ √
Analysis
All elements with √
correct zones
For a full Clash Matrix refer to Appendix C in the Technical appendices.
9.5.2 Tier Two Clashes

Tier Two Clashes are reported collisions that are considered next level
in respect to granularity of inspection. These collisions have been assigned a
greater priority in respect to the overall quality of the coordination at the end of
Design and should be rectified where practically possible:
This Tier will be used as the expected minimum level of coordination
within the BIM at the completion of Final Design:
 Mechanical Ductwork and Piping vs. Plumbing, Sanitary & Drainage Piping
 Mechanical Ductwork and Piping vs. Ceilings

 Mechanical Ductwork and Piping vs. Rated Walls (For coordination of
Dampers and other mechanical equipment needs)
 Mechanical Ductwork and Piping vs. Electrical Cable Tray
 Mechanical Ductwork and Piping vs. Floors and Walls
 Mechanical Equipment and Fixtures vs. Electrical Equipment
 Plumbing Piping and accessories vs. Mechanical Equipment, Fixtures, and
Devices
 Plumbing Piping and accessories vs. Mechanical Ductwork and Piping
 Plumbing Piping and accessories vs. Electrical Cable Tray
 Plumbing Piping and accessories vs. Ceilings
 Clear Space Requirements vs. Major MEP equipment, Walls and Structure
Note: - All of the above checks are in addition to the Tier 1 checks
9.5.3 Tier Three Clashes

Level Three Clashes are reported collisions that while considered
important to the correctness of the model will generally be changing on a
regular basis throughout the design and construction process.
These collisions have been assigned a lower level of priority and should
be rectified before the final submission of the fabrication models:
 Casework/ Joinery vs. Walls
 Casework/ Joinery vs. Electrical Fixtures and Devices
 Clear Space Requirements vs. Fixtures, Walls, Structure
 Furnishings vs. Electrical Fixtures and Devices
9.5.4 All Other Clashes

While the above clashes have been assigned priorities other collisions
will exist within the models. These clashes are not at all ignorable nor should
they be discarded. Some clashes will exist because the software available is
not yet mature enough to support the modelling efforts.
The intention should be to have a model that is understood at each
submission phase with documented proof that the all known issues are tracked
and that the design team are addressing issues as they are raised.
9.5.5 Model Review Colour Definitions

BIM Models shall have specific Colour definitions for use through model
collaboration within the Solibri, Navisworks and other environments. The table
below describes two separate colour schemes.
1. Simple Coordination for use in 3D Coordination Views for example or
Federated models
Discipline Colour
Architecture Blue (80% Transparent)
Structure Grey
Mechanical Cyan
Electrical Yellow
Fire Red
Hydraulics Magenta

Civil Grey
2. Full Coordination for use in the Master Federated Model
Discipline Colour Discipline Colour

Architecture White Communication Light Blue
Conduit
Structural Steel Red Electrical Cable Tray Dark Orange
Concrete Yellow Electrical Lighting Yellow
HVAC Equipment Cyan Plumbing Water Cyan
HVAC Supply duct Green Plumbing Sewer Magenta
Hydraulics Magenta Plumbing Storm Drain Green

Civil Grey Fire Protection Red
HVAC Equipment Gold Pneumatic Tube Dark Green
HVAC Supply Blue Equipment (Medical) Light Green

Duct/Diffuser
HVAC Return Magenta Medical Gas Light Green

Duct/Diffuser
HVAC Pipe Gold Security Systems Orange
Electrical Equipment Dark Yellow Fire Alarms Fuchsia
Electrical Conduits Light Yellow
10. QUALITY CONTROL

10.1 Overall Strategy for Quality Control
All disciplines are to use the same shared coordinate system to ensure that
shared models align when referenced into any BIM authoring tool for the next stage
of coordination. Individual models will be checked continuously to ensure the
design intent, model suitability and correct standards are followed. Issues that arise
from an interdisciplinary level will be discussed in the milestone VDR meetings and
resolved accordingly.
10.2 Project Set Out

The overall project coordinate system is to follow the Indonesian Datum. In
addition use of MRTs project grid coordinate system is also to be incorporated. The
following diagram describes the main project set out point and required transpose
points. The Diagram below defines the relationship between project coordinates
system and software coordinates to allow for accurate positioning of all project
models.
10.3 Quality Control Checks

The following diagram defines how each Task Team member for each
discipline will manage the flow of information before entering the shared area of the
common data environment and the appropriate checks required for each stage.
Each CDE role is defined in the Role and Responsibilities section of this BEP,
defining each member for each individual stakeholder.
The following criteria are to be checked for in all models that are to be shared.
 All redundant linked files have been removed

 All drawings sheets not deemed to be a deliverable are removed from the
model
 All BIM models contained within the BIM model file but not present in the
design have been removed
 File format and naming conventions conform to the nomenclature of this
project and remain constant for the life span of the project
 Model splitting conforms to project requirements
 3D model and 2D drawings are up to date
 2D content is derived from the 3D model
 All BIM objects in the BIM model have been made visible
 All ownership of any shared work sets has been relinquished
 All BIM models are using the defined sharing coordinate system
11. TECHNOLOGICAL INFRASTRUCTURE NEEDS

11.1 Software
The following software platforms and versions have been identified:-
BIM use Discipline software version

(if applicable)
Design Authoring ALL Autodesk Revit 2017 17.0.416.0
OpenBuilding Connect 10.06.03.04
Bentley OpenRail.
Microstation Connect 10.08.01.33
Design ALL Autodesk Navisworks TBC
Coordination 2017
Bentley Navigator 10.02.01.124
Scheduling ALL Primavera TBC
Syncro Pro 06.02.01.03
CDE ALL Bentley ProjectWise 08.11.11.590
Connect
Open Standards ALL IFC IFC2X3
Passanger LEGION 10.01.01.01
Simulation Flow
Asset Management Assetwise TBC
11.2 Field Access

Platform requirements to provide field access to the federated model for the
Contractor are not a requirement of the MRT tunnel project but further
consideration that maybe impact the development of the federated model will be
required to be reviewed and captured in this BEP at a later date.

12. S
TANDARD, METHODS AND PROCEDURES
Project naming structures are to be in line with MRT requirements. It is most likely
that each organization will have its own bespoke company standard, however, a
standard naming structure is recommended for efficient collaboration. The naming
structure is summarised in the following.
12.1 File Naming Structure

The MRT EDMS and Information management protocol document are to be used,
along with the project specific file naming terms and revision/status conventions and
folder structure.
Contract Stage Author/Discipline Location Type Code Status+Seq Revision Field
No. Code (Revised CAD Code (Revised Software+ No. (Not (Not applicable
(Revised) Std Annex M) (CAD Std CAD Std Version Applicable for WIP and As-
Annex P) Annex Q) for As-Built, Built)
For Info
W100R F PWAY NEL xxx dgn8i Exchange
WIPO1 A
MODEL NAMING:
Project Model name example:

W100R_F_PWAY_NEL_xxx_dgn8i_WIP01_A
12.1.1 BIM Stage Codes:

Code Stage
L Land Transport Authority (For LTA Use or
G Reserved
General only)
R Prefinal Design
F Final Design
T Tender
C Contractor's
W Working
A As-Built
TW Temporary Works
S Shop by Contractor
E Site Sketches by Engineer (For LTA Internal use)
M Manufacturing / Fabrication
X Future Installation Work
Z Submission to other Authorities
FCD Final Contract Document Delivery
PMF Procurement, Manufacturing & Fabrication
T&C Telecommunication/signal
12.1.2 BIM Discipline Codes:

Code Discipline
A Architectural
G Geotechnical
C Civil
ELL Electrical LV

Code Discipline
PS Power Supply
FPS Fire Protection
ECS Environmental Control
TVS Tunnel Ventilation
P&S Plumbing and Sanitary
LFT Lift
ESC Escalator
L Land Surveyor
R Regulatory Authority
S Structural
PWA Permanent Way /
COM Telecommunications
ISCS Integrated Sequential
PSD Platform Screen Doors
SIG Signalling
V Other Disciplines
1.. BIM Type Codes:
Code Type
STN Civil and Structural - Station
ENT Civil and Structural - Entrance [No.]
ES Civil and Structural - Escape Shaft
2.. BIM State Code:
Code State
WIP Work in
PUBL Published
SUB Submission
APP Approved
12.2 3D/2D Model Geometry Naming

Object naming is to be BS 8541-1:2012
12.2.1 Model Geometry Element – With Metadata Associated
For object created in BIM software which can have a classification code
added as additional metadata, the following conventation is to be used :
Source Type Subtype/ Product

_ _
code
Note: All main filed are all separated by the underscore character
This is to be used for object such as Revit Familied
Field Definition
Source Library author or manufacturer.
Even if the object is generic please include this field.
Type First level of specialization. Taken from IFC Type.

Sub Type / Product code Used to convey additional specialization information (e.g.
External or Internal) Taken from IFC Pre-defined Type (If not
relevant use the Uniclass2015 description).
BIM object example:

BoilersLtd_Boiler_GasFired
12.2.2 Revit Type Naming
For consultants using Revit, loadable family type names will depend
on how family has been created and the type of element.
Use an underscores character “_” to delimitate between fields and a
hyphen character “-” within fields. No spaces or punctuation to be
used. Use the descriptors which change due to parametric
programming to distinguish between types, this would generally
include size and materials.
Words are abbreviated in the SubType and descriptor field.
Term Abbreviation
External Ext
Internal Int
Ground Floor GrFlr
Upper Floor UpFlr
Pitched Ptchd
Flat Flat
Suspended Susp
Raised Access RsdAccs
Ground Bearing GrdBrng
Aluminium Alum
Asphalt Asph
Battens Bttns
Bitumen Btumn
Block Blck
Boarding Brd
Bonded Bndd
Brick Brk
Brick Slips BrkSlp
Cavity Cav
Cassette Cass
Cement Cmnt
Cement Particle Board CPBrd
Ceramic Cermc
Cladding Clad
Composite Panel CmpPnl
Concrete Conc
Concrete Pre-Cast ConcPrc
Concrete In-Situ ConcISt
Cross Laminated Timber CLT

Term Abbreviation
Damp Proof Course DPC
Damp Proof Membrane DPM
Dot and Dab DtDb
Furrings Furr
Galvanised Galv
Generic Gen
Glulam Glulm
GRP GRP
Insulation Ins
Insulation Full Fill InsFF
Insulation Partial Fill InsPF
Membrane Mmbrn
Metal Mtl
Metal Cladding MtlCld
Metal Frame MtlFrm
Metal Sections (Metsec) Metsec
Metal Standing Seam MtlSs
Pedestal Pedstl
Plaster Plstr
Plasterboard Pb
Plywood Ply
Polyethylene Polyeth
Purlins Purl
Orientated Strand Board Osb
Render Rndr
Screed Scrd
Screen Scrn
Sheeting Sht
Steel Stl
Stone Stne
Structurally Insulated SIPs
Panels
Stud Std
Suspended Grid SuspGrd
Tile Tle
Vapour Control Layer Vap
Vinyl Vnyl
Abbreviations can be amalgamated where needed (e.g. Metal Tile =
MtlTle)
Revit Type Name example:
400x350x1000 (Always use Width x Depth x Height)
12.2.3 Non Model Geometry Elements - No Metadata Included

For objects created in CAD based software which cannot have a
classification code added as metadata, it is recommended that the following

convention is to be used.
This is to be used for objects such as AutoCAD blocks
Note: All main fields are all separated by the underscore character “_”
Field Definition
Role Role of the object owner.

To be taken from the codes in section 1.1
Classification A functional or product classification code.
Uniclass 2015 is to be used
Presentation Indicating intended presentation. To be taken from the
presentation table below.
Even if the object is generic please include this field.
Type First level of specialisation. Taken from IFC Type.
SubType / Product code Used to convey additional specialisation information (e.g.

External or Internal) Taken from IFC Pre-defined Type (If not
relevant use the Uniclass2015 description).
Presentation
Code Description Comments
A Annotation Tags, arrows, symbols etc.
D Dimensions
H Hatch/Shadows
IL Invert Levels For services
M Model related graphics For elements exported from
modelling software such as Revit
M2 2D model graphics (elements in 2D) Element drawn in 2D
M3 3D model graphics (elements in 3D) Element modelled in 3D
P Plot/sheet related elements Title blocks/Viewports
T Text Text
Non BIM Object example:

Y_ Pr_60_60_08_33_ M3_ BoilersLtd_ Boiler_ GasFired
12.2.4 Material Name
Source_Material_SubType_Differentiator
Field Definition
Even if the object is generic please include this
field
Material Used to identify the material type, e.g. plastic

SubType/Product Used to convey additional specialisation
Code (optional) information (e.g. External or Internal)
Differentiator Field to add any additional information about the

(optional) content, for ease of locating.
12.2.5 Material Image File Name
Source_Type_SubType_Differentiator_ImageType
Field Definition
Source Material manufacturer (for generic
materials this shall be omitted)
Type Material type e.g. Carpet Tile
Sub Type / Product Used to convey additional information
code / Product Range such as product range. Can also be used
to capture the sub type
Differentiator Used to convey additional specialization
(optional) information not captured in attribute data
e.g. Matte
Image Type Used to convey the image type e.g.
bump, cutout, render
12.3 Model Breakdown

In order to maintain a manageable model size it is proposed that the following
model setup be used. This will assist in meeting the EIR requirement to keep
models below the 250mb maximum. This is the initial proposal for model splits
which follows discipline then zones; this may change over time.
Model Author Scope of Model Model Breakdown Software
Alignment Geometry Control Bentley OpenRail

Structures BIM Design Model 1 Model Per APM Revit 2017
Station
1 Model Per Cut and
Cover Section Revit 2017
1 Model Per Launch
Shaft
Revit 2017
12.4 Model Size

It is recommended that all models are kept to a reasonable size. With regard

to Revit the recommended limit in which performance can vary between disciplines
but for structures and MEP and for the purposes of the MRT project the limit has
been agreed to be 250mb. It is requested that all BIM coordinators monitor
performance when models start to exceed this limit. Similar, especially large DGN
files can also have an impact on performance, such a recommended limit of 30mb
is advised upon.
12.5 Modelling Requirements

Below is a summary of the key modelling requirements –
 Where practically possible all elements are to be split as they would be
constructed
 All required data is present at each stage
 Space/Room validation – There shall be no space gaps. Bounding boxes
used to represent spaces and zones shall match with architectural
requirements and data values
 All walls shall be properly joined to prevent spaces being incorrectly defined.
Bounding boxes of spaces shall not conflict.
 Spatial data shall be generated and associated with bounding elements
(walls, doors, windows, floors, columns, ceilings)
 BIM models from other disciplines shall be used as linked files and
placeholder objects previously representing aspects of these models are to
be deleted. BIM object instances shall not appear in more than one mode

7.2.4 Prelim. BIM Execution Plan Final 4

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

7.2.4 Prelim. BIM Execution Plan Final 4

Uploaded by

Copyright:

Available Formats

PT.

MASS RAPID TRANSIT JAKARTA

Construction of Jakarta Mass Rapid Transit Project

Preliminary BIM Execution Plan

OBAYASHI-WIJAYA KARYA-JAYA KONSTRUKSI JV

1. BIM Project Execution Plan Overview…………………………………………………..3

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 1

Appendix A Model Progression Delivery Table

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 2

1.1 BIM References

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 3

1.4 Glossary of terms

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 4

Building Information Modelling (BIM)

BIM Model or BIM Model file

Element or NRM1 element

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 5

Exchange BIM model file

Federated BIM model file

Model Production Delivery Table (MPDT)

Native BIM model file

Object or BIM Object

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 6

Kota Scissors Crossing Area.

Figure 1-1 General Arrangement of CP 203

2.1 Project BIM Scope

2.2 Project Schedule / Phases / Milestones

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 7

Pre-Final Design Submission

Final Design Submission

T2 Cut & Cover Tunnels, Station & Interchange

T5 Station & Interchange

Preliminary Design Submissions – Part 2*

Preliminary Design Submissions – Part 2*

3. KEY PROJECT CONTACTS

Role Organization Contact Name E-Mail

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 8

PRIORITY GOAL DESCRIPTION POTENTIAL BIM USES

5. ORGANIZATIONAL ROLES / STAFFING

Defined Role Responsibility in BIM BIM Responsibility

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 9

5.1 Key BIM Role Definition

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 10

5.1.2 BIM Coordinators

5.2 Model Author

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 11

6. BIM PROCESS DESIGN

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 12

6.2 Common Data Environment

Figure - Shared area and BIM uses

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 13

Example Minor Model MRT-WK-STR-3D-0001.rvt P01A P01B

6.2.2 Shared Area

6.2.3 Weekly Information Workflow from WIP to SHARED

BIM BIM WIP models

6.2.4 Bi Weekly Information Workflow from WIP to SHARED

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 14

6.3 Model Revisions and Suitability Status

Descriptor Code Description

6.4 Virtual Design Review (VDR) strategy

Obayashi-Wijaya Karya-Jaya Konstruksi JV Page 15

6.5 Model Comparison

7. BIM INFORMATION EXCHANGES