Previous Year BIM Execution Plan Sample

Dolce & Gabbana New Store
University of Canterbury Department of

Engineering
19-OCT-2017
Doc No. BXP01
BIM Execution Plan

Revision 0 19-OCT-1719-Oct-2016
Prepared for University of Canterbury Department of Engineering ABN: N/A
GY Dolce & Gabbana New
Store BIM Execution Plan
BIM Execution Plan

Client: University of Canterbury Department of Engineering

ABN: N/A
Prepared by
GYBS New Zealand Limited
87 Maidstone Road, Ilam, Christchurch 8041, New Zealand T +64 3 966 6018 F +64 3 966 6001
19-Oct-2017
Job No.: 19926452
GYBS in Australia and New Zealand is certified to ISO9001, ISO14001 AS/NZS4801 and OHSAS18001.
Printed on environmentally responsible paper. Made from 100% recycled post consumer waste.
© GYBS New Zealand Limited (GYBS). All rights reserved.

GYBS has prepared this document for the sole use of the Client and for a specific purpose, each as expressly stated in the document. No other party should rely on this do
requirements and
GYBSGYBS can reasonably be expected to make in accordance with sound professional principles. GYBS may also have relied upon information provided by the Client a
Revision 0 19-OCT-17
Quality Information
Document BIM Execution Plan
19926452
Ref
i:\bim\GYBS nz bep template 2017.docx
Date 19-Oct-2017
Prepared by S ENGINEER
Reviewed by S AMMAIYAPPAN
Revision History
Authorised
Rev Revision Date Details
Name/Position Signature
0 17.10.17 S AMMAIYAPPAN BIM Lead
Table of Contents
Introduction i
1.0 Project Information 1
1.1 Project Identification 1
1.2 Project Participants 1
2.0 BIM Uses and Level of Development 1
2.1 BIM Uses and Value 1
2.2 Levels of Development (LOD) 1
3.0 BIM Roles and Responsibilities 1
3.1 Project BIM Lead 1
3.2 Project BIM Coordinator 1
3.3 Discipline BIM Lead 2
3.4 Model Element Author 2
3.5 Proposed BIM Team Structure 3
4.0 Communication, Collaboration and Coordination Procedures 4
4.1 Coordination Strategy 4
4.2 Coordination Meetings 4
4.3 Other BIM Meetings 5
5.0 Information Management and Exchange 6
5.1 Common Data Environment 6
5.2 Milestone BIM Exchanges and Deliverables 7
5.3 Design Development BIM Exchange Formats 7
5.4 Design Development BIM Exchange Frequency 7
5.5 Model and Data Verification 7
5.6 Software Versions 7
5.6.1 Model File Upgrade Mitigation 8
6.0 Modelling 8
6.1 General Modelling Strategy 8
6.2 Modelling Standards and Guidelines 8
6.3 Model File Naming 9
6.4 Phase Naming 9
6.5 Model Separation 10
6.6 Model Quality Control Checks 11
6.7 Workset Naming 12
6.8 Level of Development 12
6.9 Model Element Author Schedule 14
7.0 Specific Uses of BIM 24
7.1 Design Authoring 24
7.1.1 Design Authoring Software 24
7.2 Virtual Coordination and Issues Resolution 24
7.2.1 3D Coordination / Clash Detection Software 24
7.2.2 Model Coordination Matrix 25
7.2.3 Clash Check Summary 26
7.3 BIM based Design Reviews 26
7.3.1 Design Review Software 26
GY Dolce & Gabbana New i
Introduction
To ensure successful BIM implementation on the Dolce and Gabbana new store, GYBS in
conjunction with the design team stakeholders have developed this BIM Execution Plan.
This BIM Execution Plan defines who is responsible for what in the BIM process, when in the process
they are responsible for it, and how they will execute it.
This BIM Execution Plan has been structured to provide a framework for the creation and progression
of Building Information Models to deliver the following project outcomes:
Design:
- A reduction in errors and omissions during design through improved coordination and
clash avoidance and detection of design intent models, reducing rework.
- Enhanced stakeholder engagement through the use of static and interactive visualisations.
- Accurate integration of the new design into the existing facility to provide an as-built model at
completion.
- To provide a consistent platform to house key information to be transferred into O&M.
- Improved cost certainty during design.
- Improved Safety in Design through using the 3D model to inform the SiD conversation.
Construction:
- Improved Safety in Design through using the 3D model to inform the SiD conversation.
- An optimised construction schedule through a reduction in construction variations through
improved design intent documentation and coordination.
Operations and Maintenance:
- Reliable and complete as-built information.
- A COBie data deliverable containing key information about critical assets for input into JDE-
CAM.
This BIM Execution Plan should be considered a living document, it can be refined and further
developed throughout the project lifecycle to ensure the project remains on schedule and meets the
briefed requirements. It will however not fundamentally change the scope of each stakeholder beyond
the requirements above. This development will not take place in isolation; it will be a collaborative
effort by all contributing stakeholders.
GY Dolce & Gabbana New 1
1.0 Project Information

1.1 Project Identification
Details
Project Name Dolce and Gabbana New Store

Project Identification No. 19926452
Project Location Cathedral Square, Central Christchurch
Client University of Canterbury Department of Civil Engineering
1.2 Project Participants
Project Role Name Email

Client S AMMAIYAPPAN sam319@uclive.ac.nz
Representative
BIM Lead S AMMAIYAPPAN sam319@uclive.ac.nz
BIM Coordinator S AMMAIYAPPAN sam319@uclive.ac.nz
Architectural B CHANDRASHEKARA bch120@uclive.ac.nz
Interior
Architectural G GONG jgo74@uclive.ac.nz
Facade
Structural Y TANG yta32@uclive.ac.nz
MEP S AMMAIYAPPAN sam319@uclive.ac.nz
Fire Engineer TBC TBC
GYBS Dolce & Gabbana New Store 1
BIM Execution Plan
2.0 BIM Uses and Level of Development

2.1 BIM Uses and Value
GYBS feel that the following uses of BIM will add value to the project.
Uses of BIM
Space Management and

Construction Systems
Building Maintenance
Existing Conditions
Building Systems
Cost Estimation
Phase Planning
3D control and
Site Utilization
Sustainability
Engineering
Phase Value
Disaster
Record
Design
Design
Spatial
Digital
Asset
Code
Site
3D
Design Improved stakeholder engagement through
- - - - - - - - - - - - - - - - - - -
and static renders.
Reduced duplication of effort during design
through creating, sharing and reusing digital - - - - - - - - - - - - - - - - - - - -
information throughout the design process.
Reliable design coordination through 3D
model coordination and the sharing and - - - - - - - - - - - - - - - - - -
reuse of digital information.
Improved Safety in Design through using
the 3D model as a visual aid to inform SiD - - - - - - - - - - - - - - - - - - -
considerations.
Construction
Operation
1
2.2 Levels of Development (LOD)

Typically the following Levels of Development will apply to the project at each phase in accordance
with the green ticks in the table below. For further detail on the Levels of Development, refer to section
6.8.
Design Construction Operation
Concept Design
Detailed Design
Drawings and
Drawings and
Management
Constructio
Fabrication
Preliminar
Modelling
Modelling
Develope
Facilities
d Design
y Design
As-built
n Issue
Asset /
Model
Shop
100 100 100 - 100 - 100 - 100 - 100 - 100 -
200 - 200 200 200 - 200 - 200 - 200 - 200 -
300 - 300 - 300 300 300 300 - 300 - 300 -
350 - 350 - 350 - 350 - 350 - 350 - 350 - 350 -
400 - 400 - 400 - 400 - 400 - 400 - 400 - 400 -
500 - 500 - 500 - 500 - 500 - 500 - 500 - 500 -
3.0 BIM Roles and Responsibilities

The following section outlines our proposed BIM roles and responsibilities for this project.
3.1 Project BIM Lead
this may include but is not limited to:

Facilitating the development of the project BIM Execution Plan
Facilitating project BIM Execution Plan workshops
Clearly communicating the briefed requirements to all project stakeholders
High level model audits of models received from project stakeholders
Communicate issues back to project stakeholders
Tackling BIM related issues in a timely and efficient manner
3.2 Project BIM Coordinator

project objectives and BIM uses are achieved and that models are integrated and coordinated, this
may include but is not limited to:
- Coordination of federated models
- Clash detection, clash resolution and clash report generation and circulation
- Facilitate model management and coordination meetings
- Communicate coordination issues back to project stakeholders
2
- Participate in the BIM Execution Planning process
3.3 Discipline BIM Lead

Each discipline (architect / structural engineer / services engineer, quantity surveyor, etc) will appoint a
BIM
- Participate in the BIM Execution Planning process
- Participating in design review and model coordination meetings
- Facilitate the use of the BIM Execution Plan within their organisation / team
- Ensure model files are developed in accordance with the project BIM Execution Plan
- Validate Levels of Model Development at each project stage
- Perform detailed model audits before issue to the wider team
- Communicate issues to model element authors
- Implement internal coordination and clash detection procedures
- Model transfer and version control
- Discipline leads require an overall knowledge of BIM in relation to their discipline
3.4 Model Element Author

The Model Element Author is any project stakeholder who will be developing the Building Information
Model throughout the project delivery process. The Model Element Author responsibilities include
but are not limited to:
- Modelling elements in accordance with the project BIM Execution Plan to meet briefed
requirements
- Modelling elements at the appropriate Level of Development as defined in the BIM
Execution Plan at each project stage
- Ensuring design coordination using internal coordination processes as models develop
- Communicating any model related issues to appropriate project stakeholders
GYBS Dolce & Gabbana New Store 3
BIM Execution Plan
3.5 Proposed BIM Team Structure

The following diagram shows the proposed BIM org chart and lines of reporting for this project.
Project BIM Lead
GYBS LTD
Project BIM
Coordinator
GYBS LTD
Architecture Interior Building Architecture Facade

Structural BIM Lead
BIM Lead Services BIM BIM Lead
Lead
TANG LTD BHARGAVA LTD GINO LTD
GYBS LTD
Model Element Model Element Model Element Model Element

Author Author Author Author
Y TANG B CHANDRASHEKARA S AMMAIYAPPAN G GONG

4
4.0 Communication, Collaboration and Coordination Procedures

4.1 Coordination Strategy
Successful model coordination relies on the different disciplines understanding their roles and only
modelling what they are responsible for in accordance with the Model Element Author schedule in
section 6.9. Coordination is much more than just clash detection; the key to successful coordination is
identifying issues, assigning relevant project stakeholders to the issues and tracking the issues until
they are resolved.
General coordination will take place via visual inspection of the model; this includes single discipline
coordination and coordination with other discipline models. General coordination is the responsibility of
all of the Discipline BIM Leads.
Clash detection (3D coordination) is the responsibility of the Project BIM Coordinator and will centre on
the Federated Model. At intervals as defined in Table 1: BIM Coordination Meetings, the Project BIM
Coordinator will create a federated model and perform clash detection in accordance with the model
coordination matrix in section 7.2.2. The Project BIM Coordinator will issue the coordination reports to
each Discipline BIM Lead and the BIM Manager prior to each scheduled coordination meeting.
The Project BIM Coordinator will facilitate a project coordination meeting via videoconference using
the federated model. Major clashes and coordination issues will be highlighted during this meeting in
an open forum to allow opportunity for their resolution during the meeting. The federated models will
be displayed on-screen to help visualise the clash.
Any outcomes, including minor clashes and other coordination issues will be assigned to relevant
project team members. The Project BIM Coordinator will track the progress of each clash until it is
resolved.
4.2 Coordination Meetings

Table 1: BIM Coordination Meetings
Meeting Type Facilitator Project stage Required attendees

50% Developed
GYBS
Design
100% Developed
3D Coordination and Clash GYBS Design Design team
Detection / Resolution
GYBS 50% Detailed Design
GYBS 75% Detailed Design
5
Figure 1: Typical BIM Coordination, Clash Detection and Design Review Cycle
4.3 Other BIM Meetings

We have identified the following BIM meetings for the project.
Meeting Type Facilitator Project stage Required attendees
Post Contract BIM GYBS Within 4 weeks of All BIM stakeholders
Execution Plan contract award.
Development
On-going BIM Execution GYBS As required All BIM stakeholders
Planning
3D Design Reviews The graphical models will be used in client and design team
meetings to communicate and review the design intent.
6
5.0 Information Management and Exchange

5.1 Common Data Environment
The Common Data Environment is defined as a single source of information for any given project. It
will function as a digital hub within which project stakeholders can collect, manage and disseminate all
relevant approved project data in a managed environment.
GYBS propose to use Dropbox for all project communication and the transmittal of model files. A
shared location will be set up, invitations and instructions for use will be sent out to all team members.
All project parties will provide contact details for all team members likely to require access to the shared folder location.
Please note, this is not setup as a storage site, each party is responsible for the downloading and saving of transmitted
All transmitted models are to be saved to the shared folder, replacing the previously issued model; therefore model nam
The image below outlines our approach to adopting Dropbox as a CDE to support the sharing of BIM data.
Figure 2: Common Data Environment Workflow
7
5.2 Milestone BIM Exchanges and Deliverables

Project Stage BIM Milestone Date Deliverable
Client Review and concept

Concept Design 18.10.17 Concept design sketches
design approval
Preliminary Client review and Preliminary design drawings
25.10.17 Preliminary design Revit
Design preliminary design approval
models
Client review and Developed design drawings
Developed Design 15.11.17 Developed design Revit
developed design approval
models
Detailed Design Issued for construction 6.12.17 Detailed design drawings
Detailed design Revit models
Construction
Operation
5.3 Design Development BIM Exchange Formats

The following table details the file format for model exchanges to support on-going design
development and coordination.
Purpose / Use Details Format
Design Models Autodesk Revit for design authoring and on- .RVT
going coordination purposes
Federated (Coordination) TEKLA BIMsight for detailed coordination and .IFC
Model clash detection purposes.
Documentation Work in progress or milestone documentation to .PDF
support design development.
5.4 Design Development BIM Exchange Frequency

The following table details the frequency of model exchanges to support on-going design development
and coordination.
Discipline Concept Preliminary Developed Detailed Construction Operation
Design Design Design Design
Architecture - Weekly Weekly Weekly TBC TBC

Structure - Weekly Weekly Weekly TBC TBC
Services - Weekly Weekly Weekly TBC TBC
5.5 Model and Data Verification

-
within their model. This will contain a written log that identifies key amendments since the preceding
issue. This will be updated prior to upload to the Common Data Environment.
5.6 Software Versions

The software versions that will be used for the duration of the project in relation to specific uses of BIM
can be found in section 7.0.
8
5.6.1 Model File Upgrade Mitigation

Where possible, Revit model files should remain the same version for the duration of the project. If
there is a requirement to upgrade the model files to a newer release of the software, the BIM Manager
will be informed and a strategy for file upgrades will be developed alongside the discipline BIM leads.
6.0 Modelling
6.1 General Modelling Strategy
As a minimum each discipline in the project team is required to model to industry proven best practice
methodology in conjunction with complying with in-house modelling standards and procedures.
The following points have been considered as part of the overall modelling methodology for this
project:
- Model setup including how models are divided
- Project and view templates that control 2D and 3D output and appearance (i.e. line
weights on drawings, element shading, etc.)
- Model naming conventions
- Model element naming conventions and classification
- Materials and finishes naming conventions
- Model element parameters
6.2 Modelling Standards and Guidelines

The following modelling standards and guidelines will be used throughout this project.
Type Document Title
Modelling Standards GYBS internal modelling standards
Modelling Standards BIM Forum Level of Development Specification, October 2015.
BIM Guidelines New Zealand BIM Handbook, November 2016
9
6.3 Model File Naming

To ensure consistency model file naming will be as follows:
Field 1 Field 2 Field 3 Field 4

Project Document Type Discipline Version
FPH - BIM - MEP R16
3 Characters 3 Characters
3 Characters 3 Characters
Max Max
Field 1 Project
Project Code Description
FPH4 Dolce and Gabbana New Store
Field 2 Document Type

Code Description
BIM BIM Model
Field 3 Discipline
Code Description
ARC Architectural
STR Structural
CIV Civil
ELE Electrical
MEC Mechanical
FIR Fire Protection
HYD Hydraulics
FED Federated Model
Field 4Software Version
Code Description
R16 Revit Version 2017
N16 BIMsight Version 2016
Issued models file names must not be changed without prior discussion and agreement between the
Project BIM Leads.
6.4 Phase Naming

Phase Name Description
Existing Existing building elements
1
Phase Name Description
New Construction Proposed new building elements
6.5 Model Separation

Building Information Models will be separated by discipline as a minimum. This diagram will be revised
following project award to reflect model separation by zone, building, etc.
Figure 3: Model Separation and Federation

To maintain system performance and ensure that model files are accessible by all parties, if model files become unman
1
6.6 Model Quality Control Checks

The following checks will be performed to assure quality within models and non-geometric information,
to eliminate errors and achieve the desired project outcomes.
Check Definition Responsible Party
Check for unintended model Discipline BIM Lead, Model

Visual check components and that design intent has Element Author
been followed
Check for object clashes within discipline Discipline BIM Lead
Single Discipline specific models
Clash Detection
Review the on-going development of the Design Team
Design review model against the design intent
Review and resolve model warnings Discipline BIM Lead
Authoring software within the design authoring software
warnings
1
6.7 Workset Naming

Work-sharing using Autodesk Revit is enabled through the use of Worksets. To facilitate the seamless
exchange and re-use of BIM data in a Worksharing environment using Autodesk Revit the following
Workset naming convention will be adopted on this project.
Care is required when creating Model Elements, ensuring that they are hosted on the correct Workset.
This will maintain an effective modelling environment for all project team members.
Workset Name Description
Architecture Primary architectural elements

FF&E Fixtures, fittings and equipment
Shared Levels and Levels and grids
Grids
Structural Placeholder Structural elements modelled by the architect as placeholders
Structure Structural elements
Electrical Electrical elements
Lighting Lighting elements
Mechanical Mechanical elements
Hydraulics Hydraulic elements
6.8 Level of Development

Model Element Authors (MEA) is responsible for developing each Model Element at the end of each
phase of the project to a minimum Level of Development (LOD) in accordance with the BIM Forum
Level of Development Specification October 2015.
A summary of LOD definitions is described in the following table. If there is conflict between the table
below and the BIM Forum Level of Development Specification October 2015, the latter takes
precedence:
Level of
Description Example (Structural Column)
Development
LOD 100 The Model Element may be graphically represented LOD100 2D or 3D geometry, generic
in the Model with a symbol or other generic column element with cost/m3
representation, but does not satisfy the
requirements for LOD 200. Information related to the
Model Element (i.e. cost per square foot, tonnage of
HVAC, etc.) can be derived from other Model
Elements.
Note: LOD 100 elements are not always geometric
representations. Examples are information attached
to other model elements or symbols showing the
existence of a component.
LOD 200 The Model Element is graphically represented within LOD 200 Generic 3D geometry,
the Model as a generic system, object, or assembly approximate size, shape and location.
1
Level of
Development
with approximate quantities, size, shape, location,

and orientation. Non-graphic information may also
be attached to the Model Element.
Note: 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.
LOD 300 The Model Element is graphically represented within LOD 300 3D design intent geometry,
the Model as a specific system, object or assembly specific size, shape and location.
in terms of quantity, size, shape, location, and
orientation. Non-graphic information may also be
attached to the Model Element.
Note: The quantity, size, shape, location, and
orientation of the primary elements as designed that
are shown on drawings at a scale of 1:50 or above
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 within LOD 350 3D actual design geometry,
LOD 350
the Model as a specific system, object, or assembly specific size, shape, location and
in terms of quantity, size, shape, location, interface with other elements.
orientation, and interfaces with other building
systems. Non-graphic information may also be
attached to the Model Element.
Note. 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 primary elements as
designed that are shown on drawings at a scale of
1:50 or above can be measured directly from the
model without referring to non-modelled information
such as notes or dimension call-outs.
LOD 400 The Model Element is graphically represented within LOD 400 3D fabrication geometry
the Model as a specific system, object or assembly including member coping, end plates,
in terms of size, shape, location, quantity, and washers, nuts, etc.
orientation with detailing, fabrication, assembly, and
installation information. Non-graphic information may
also be attached to the Model Element.
Note. 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 information such as notes
or dimension call-outs.
1
Level of
Development
LOD 500 The Model Element is a site verified representation LOD 500 verified as built model
in terms of size, shape, location, quantity, and geometry.
orientation. Non-graphic information may also be
attached to the Model Elements.
Note: The graphical representation of
The BIMForum LOD Specification does not address
LOD 500 necessarily need to be as detailed as
LOD 400.
An LOD 200 or LOD 300 element could
be verified as built through either a
measured or visual as built verification
process.
6.9 Model Element Author Schedule

The following table assigns responsibilities to Model Elements via an Author (MEA) and defines the
Level of Development of model elements across the project stages.
MEA Discipline Level of Development (LOD)
Architectural Consultant ARC 100 Conceptual
STR 200 Approximate Geometry

Structural Consultant
MEC 300 Precise Geometry

Mechanical Consultant
ELE 350 Actual Geometry
Electrical Consultant
Plumbing & Drainage PLU 400 Fabrication and Assembly

Consultant
Fire Consultant FIR 500 As Constructed
1
Model Element Author Key Architectural Consultant Structural Consultant Mechanical Consultant Electrical Consultant Plumbing & Drainage Consultant Fire Consultant
Project Phase Concept Preliminary Developed Detailed Construction Operation Notes

design design design design design
Model Element MEA LOD MEA LOD MEA LOD MEA LOD MEA LOD MEA LOD
SPATIAL
Site boundaries, setbacks ARC - ARC - ARC - ARC -
Grids ARC - - - -
Levels ARC - ARC - ARC - ARC -
Zones ARC - ARC - ARC - ARC -
Spaces, rooms ARC - ARC - ARC - ARC -
SITE
Topography - - - - - 2D CAD
SUBSTRUCTURE
Foundations - - STR 200 STR 300 STR 300
1

Retaining walls ARC 100 STR 200 STR 300 STR 300
STRUCTURE
Floors ARC 100 STR 200 STR 300 STR 300
Steel beams ARC 100 STR 200 STR 300 STR 300
Concrete beams ARC 100 STR 200 STR 300 STR 300
Shaft openings ARC 100 STR 200 STR 300 STR 300
Wall openings load bearing ARC 100 STR 200 STR 300 STR 300
Steel stairs Arch to model accurate

ARC 100 STR 200 STR 300 STR 300
stairs for support
Concrete stairs Arch to model accurate

ARC 100 STR 200 STR 300 STR 300
stairs for support
1

Ramps Arch to model accurate

ARC 100 STR 200 STR 300 STR 300
ramps for support
Walls load bearing ARC 100 STR 200 STR 300 STR 300
Steel columns ARC 100 STR 200 STR 300 STR 300
Concrete columns ARC 100 STR 200 STR 300 STR 300
Insitu Concrete Elements ARC 100 STR 200 STR 300 STR 300
Masonry Elements ARC 100 STR 200 STR 300 STR 300
Secondary Steel Elements - - - - STR 300 STR 300
ENCLOSURE
Roofing ARC 100 ARC 200 ARC 200 ARC 300
Concrete Roofing ARC 100 STR 200 STR 300 STR 300
1

Cladding ARC 100 ARC 200 ARC 200 ARC 300
Column cladding ARC 100 ARC 200 ARC 200 ARC 300
Curtain walls ARC 100 ARC 200 ARC 200 ARC 300
Windows ARC 100 ARC 200 ARC 200 ARC 300
External doors ARC 100 ARC 200 ARC 200 ARC 300
Wall openings non struct ARC 100 ARC 200 ARC 200 ARC 300
INTERIOR
Partitions ARC 100 ARC 200 ARC 200 ARC 300
Internal doors ARC 100 ARC 200 ARC 200 ARC 300
Internal openings non

ARC 100 ARC 200 ARC 200 ARC 300
struct
1

Internal openings structural Applicable to masonry

ARC 100 STR 200 STR 300 STR 300 wall and other structural
openings
Ceilings ARC 100 ARC 200 ARC 200 ARC 300
Flooring ARC 100 ARC 200 ARC 200 ARC 300
Balustrading ARC 100 ARC 200 ARC 200 ARC 300
F, F & E
Casework, Joinery - - ARC 100 ARC 200 ARC 300
Fixtures - - ARC 100 ARC 200 ARC 300
Fittings - - ARC 100 ARC 200 ARC 300
Furniture - - ARC 100 ARC 200 ARC 300
2

Signage - - ARC 100 ARC 200 ARC 300
MECHANICAL
Plant external - - MEC 100 MEC 200 MEC 300
Plant internal - - MEC 100 MEC 200 MEC 300
Louvers - - ARC 100 200 300
Ductwork - - MEC 100 MEC 200 MEC 300
Registers - - MEC 100 MEC 200 MEC 300
Pipework
- - MEC 100 MEC 200 MEC 300 Minor pipes <50mm dia
LOD 200
Controls - - MEC 100 MEC 200 MEC 200
2

ELECTRICAL
Electrical fixtures - - - - ARC 200 ARC 300
Power outlets - - - - ARC 200 ARC 300
Switches - - - - ARC 200 ARC 300
Distribution boards - - - - ARC 200 ARC 300
Cable trays - - - - ELE 200 ELE 300
Lighting - - ELE 200 ELE 200 ELE 300
Light switches, light controls - - - - ELE 200 ELE 300
Communications - - - - ELE 200 ELE 300
Security - - - - SS 200 SS 300
2

PLUMBING & DRAINAGE
Sanitary fixtures - - ARC 200 ARC 200 ARC 300
Plant - - PLU 100 PLU 200 PLU 300
Equipment - - - - PLU 200 PLU 300
Pipework Minor pipes <50mm dia

- - - - PLU 200 PLU 300
LOD 200
FIRE
Sprinklers - - - - FIR 200 FIR 200
Sprinkler penetrations - - - - 200 200
Pipework (main) - - - - FIR 200 FIR 200
Pipework (branch) - - - - FIR 200 FIR 200
2

Detection - - - - FIR 200 FIR 200
Alarm systems - - - - FIR 200 FIR 200
Hydrants - - - - FIR 200 FIR 200
Extinguishers - - - - FIR 200 FIR 200
CONVEYING
Lifts - - ARC 100 ARC 200 ARC 300
Penetrations - - ARC 100 ARC 200 ARC 300
2
7.0 Specific Uses of BIM

7.1 Design Authoring
7.1.1 Design Authoring Software
For the duration of the project the following software will be used for design authoring of the building
and building systems.
Discipline Software Version
Architecture Autodesk Revit 2017

Structure Autodesk Revit 2017
Mechanical, Electrical & Plumping Autodesk Revit 2017
7.2 Virtual Coordination and Issues Resolution

Our Virtual Coordination and issue resolution process defines accountability and monitors progress.
Models develop at different rates during design development, regular Virtual Coordination and Issue
Resolution meetings offer an opportunity to discuss the current state of play and discuss any issue
that require resolution.
The Project BIM coordinators role will be to identify issues and assign responsibility of resolution to the
relevant project stakeholder.
3D coordination and clash detection on the federated model is supplementary to the on-going
coordination that will be taking place within each discipline on a daily basis during design / model
development.
7.2.1 3D Coordination / Clash Detection Software
Task Software Version

3D Coordination / Clash TEKLA BIMsight 2016
Detection
2
7.2.2 Model Coordination Matrix

The following matrix shows the Selection/Search Sets that have been defined and the Sets that are
Clash Checked against each other.
Notes
Architectural
1 - ARCHBuilding Model Structural Model 0
Hydraulic Services Sanitary Services Mechanical Ductwork
1 - STRL
Mechanical Pipework Y Y Y Y Y Y Y Y 8
2 - HY
Hydraulic SANI Water Services Fire
Services S Protection
Y Y Services
Y Y Y Y Y 7
Electrical Containment
3 - ME DUCT ( Inc. Equipment) S
Electrical
Y Y (Fixtures,
Y YLighting,
Y Y ETC..) Architectural
6 Building Model Architectural Facade Model
4 - ME PIPE S Y Y Y Y Y 5
Keyincluding the self intersect
4 - HY WATER S Y Y Y Y 4
Y = Selection/Search Sets are check
5 - FIRE S Y Y Y 3 N = Selection/Search Sets are not clash check
6 - EL CONT S Y Y 2 S = Selection/Search Sets are the same, self int
7 - EL FIX S Y 1
Figure
8 -4: Model Coordination Matrix
ARCH 0
The project BIM Coordinator is responsible for creating a federated
0 model in BIMsight and performing Clash Detection o
36
43
2
7.2.3 Clash Check Summary

Use the Clash Check Manager tool to find parts, bolts, reinforcement, or reference model objects that collide.
Clashes of objects that only touch one another are not included in the clash check results. Use the clash check
settings to define clearances between different model objects. You can also use the sections and floors created in
Organizer to run a controlled clash check. If you want to use another Tekla Structures model as a reference
model, you must export it in IFC format to be able to use it in clash checking.
Figure 5: Example coordination report
7.3 BIM based Design Reviews

All disciplines will coordinate their models as they are being developed. As models are developed at differing rates, des
7.3.1Design Review Software
For the duration of the project the following software will be used for design reviews.
Software Version
TEKLA BIMsight 2016
2
This page has been left blank intentionally.
P LANNED SCHEDULE (WEEKLY)
Person Monday Tuesday Wednesday Thursday Friday

am pm ampm ampm ampm ampm
S Ammaiyappan Meet Ind Ind Up Merge
B Chandrashekara Ind Meet Ind Meet

Up Check
G Gong Meet Ind Meet Ind Up Up
Y Tang Meet Ind Ind
Ind Work on separated model

Up Upload model at current stage to cloud storage
merge merge models at check clash detections
Meet Collaboration meeting
Check Clash detection, model checks

Previous Year BIM Execution Plan Sample

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

Previous Year BIM Execution Plan Sample

Uploaded by

Copyright:

Available Formats

Dolce & Gabbana New Store

University of Canterbury Department of

BIM Execution Plan

BIM Execution Plan

Client: University of Canterbury Department of Engineering

Job No.: 19926452

© GYBS New Zealand Limited (GYBS). All rights reserved.

0 17.10.17 S AMMAIYAPPAN BIM Lead

1.0 Project Information

Project Name Dolce and Gabbana New Store

1.2 Project Participants

Project Role Name Email

2.0 BIM Uses and Level of Development

Space Management and

2.2 Levels of Development (LOD)

200 - 200 200 200 - 200 - 200 - 200 - 200 -

300 - 300 - 300 300 300 300 - 300 - 300 -

350 - 350 - 350 - 350 - 350 - 350 - 350 - 350 -

400 - 400 - 400 - 400 - 400 - 400 - 400 - 400 -

500 - 500 - 500 - 500 - 500 - 500 - 500 - 500 -

3.0 BIM Roles and Responsibilities

3.1 Project BIM Lead

this may include but is not limited to:

3.2 Project BIM Coordinator

- Participate in the BIM Execution Planning process

3.3 Discipline BIM Lead

3.4 Model Element Author

3.5 Proposed BIM Team Structure

Project BIM Lead

Architecture Interior Building Architecture Facade

Model Element Model Element Model Element Model Element

Y TANG B CHANDRASHEKARA S AMMAIYAPPAN G GONG

4.0 Communication, Collaboration and Coordination Procedures

4.2 Coordination Meetings

Meeting Type Facilitator Project stage Required attendees

4.3 Other BIM Meetings

5.0 Information Management and Exchange

Figure 2: Common Data Environment Workflow

5.2 Milestone BIM Exchanges and Deliverables

Client Review and concept

5.3 Design Development BIM Exchange Formats

5.4 Design Development BIM Exchange Frequency

Architecture - Weekly Weekly Weekly TBC TBC

5.5 Model and Data Verification

5.6 Software Versions

5.6.1 Model File Upgrade Mitigation

6.2 Modelling Standards and Guidelines

6.3 Model File Naming

Field 1 Field 2 Field 3 Field 4

Field 2 Document Type

6.4 Phase Naming

Existing Existing building elements

Phase Name Description

New Construction Proposed new building elements

6.5 Model Separation

Figure 3: Model Separation and Federation

6.6 Model Quality Control Checks

Check Definition Responsible Party

Check for unintended model Discipline BIM Lead, Model

6.7 Workset Naming

Architecture Primary architectural elements

6.8 Level of Development

with approximate quantities, size, shape, location,