Do not distribute.

Company Name

Project Name

BIM Execution Plan

Revision
Date
2

1. Table Contents
1. Agreement.............................................................................................................................................................3

2. Overview................................................................................................................................................................ 4

Project Information...................................................................................................................................................4

Service Responsibly Matrix ...................................................................................................................................5

Coordination Meetings:...........................................................................................................................................7

3. Modeling Plan.......................................................................................................................................................9

Model Managers...................................................................................................................................................... 9

4. Design Team Software Requirements..........................................................................................................10

Authoring Software................................................................................................................................................10

Coordination Software..........................................................................................................................................10

Document Management & Exchange Formats’..............................................................................................10

Additional requirements........................................................................................................................................11

Construction Team Software Requirements....................................................................................................11

Hardware Requirements......................................................................................................................................11

5. Planned Models................................................................................................................................................. 12

Project Base Point..................................................................................................................................................12

File Naming Structure...........................................................................................................................................13

6. Design Model Structure....................................................................................................................................14

Model Element Rules, General Completeness of design..............................................................................14

Precision and Dimensioning................................................................................................................................15

Modeling Level of Detail.......................................................................................................................................15

Design Model Ownership of Elements..............................................................................................................16

8. Clash Detection Process..................................................................................................................................17

Coordination Milestone.........................................................................................................................................17

Clash Detection Guideline....................................................................................................................................18

9. Concurrent As-Built Modeling Plan................................................................................................................19

10. Design Model Update Plan.........................................................................................................................19

11. Facility Management- FM............................................................................................................................20

12. Common Data Environment.......................................................................................................................20

Oct, 2023 Project Name

3

Electronic Communication procedures............................................................................................................20

13. Document History..............................................................................................................................................21

Annexure A: BIM 360 DOCS.............................................................................................................................................22

Folder Structure Overview....................................................................................................................................22

Permission Level Overview..................................................................................................................................22

Issue Management:...............................................................................................................................................24

Annexure B: BIM 360 Build..............................................................................................................................................25

2.

Oct, 2023 Project Name

4

1. Agreement
By signature below, this BIM Execution Plan is herewith adopted and incorporated into the Agreement, dated
____________, for Professional Design Services between the Client and the professional team.

Appointment Company Name Signature

Client
Development Manager
Project Manager
Civil Engineer
Geotechnical Engineer
Surveyor
Traffic Engineer
Structural Engineer
Environmental
Engineer
Cost Estimator
Contractor
Site Supervisor
Quality Control
Safety Officer
Project Scheduler
Public Relations
Specialist
Government
Regulator/Inspector

The project plan has been agreed by the representatives of the project team as listed above
with the authority of their parent companies to accept this document as the agreed pre-
appointment BIM Execution Plan.

1. Document Status

Oct, 2023 Project Name

5

Title Rev Author Issued date

Oct, 2023 Project Name

6

2.Project Information

2.1. Preface

The intent of this BIM Execution Plan is to provide a framework that will let the parties involved deploy
building information modelling (BIM) technology and best practices on this project faster and more
cost-effectively. This plan defined the purposes of using BIM on this project, specified how the
created models will be used and notes ways of exchanging information. Roles and responsibilities of
each party and the detail and scope of information to be shared, relevant business processes and
supporting software are also included. The BEP provides a structured plan for how the informational
modelling aspect of a project will be taken in a cross discipline, collaborative environment utilising
electronic object orientated design tools.

This section defines the Core Collaboration Team, Information exchanges, project phases, and overall
communication plan throughout the project’s phases 02-04.

2.2. Project Information

Project Name:
Project Number:
Project Address:
Project Description:

Current Project
Status:
Estimated Project
Size:

Estimated Project
Value:

Project Duration:

Oct, 2023 Project Name

7

2.2.1BIM Execution Plan Ownership

This document is owned and maintained by the current Project Delivery Manager listed
below.

Project Delivery Company Contact

Manager - Name Responsible
Name
Email
Phone Number

2.3. Project Representative and Roles

The following responsibility matrix indicates specific services that falls in the scope of each discipline:

Team Role / Company Primary Contact

Discipline
Name
Email
Phone Number
Name
Email
Phone Number

Oct, 2023 Project Name

8

2.4. Management

2.4.1. Roles, Responsibilities and Authorities

Please refer to the project representatives and roles (Section above.) for identification of the roles and
responsibilities of the design teams for the project. This will provide a more extensive identification of
the consultants involved in the project, as well as identifying those with the key roles as the project
evolves.
The authorities/activities of the key roles related to management of information are outlined below.
These roles are in line with those identified within the ISO 19650 series for information exchange
activities. These outlines are not wholly encompassing but identify the key authorities within the
project.

Role /Function Activities Authorities

Information Enable reliable information exchange through a Accept reject information exchanges
Management common data environment. within the common data environment.
Maintain and receive information into the No design responsibility or right to
Information Model. issue instructions.
Enable integration and co-ordination of
information within Information Model.
Configure information for Project Outputs.
Populate the information exchange format for the
Information Model.
Project Delivery Assure delivery of information exchanges. Accept reject information exchanges
Management Confirm supplier’s ability to deliver information within the common data environment.
requirements.
Lead Consultant Co-ordinated delivery of all design information. Confirm status and approve
Manage information development and information information for issue within the
approvals. common data environment.
Confirm design deliverables. Approve design changes proposed to
Overall lead for configuration management resolve clashes.
Task Team Production of design outputs related to a Issue approved information within the
Manager discipline-specific, package-based or time-based common data environment
task.
Task Information Direct the production of task information in Confirm that information is suitable
Manager compliance with standards and methods. for issue within a common data
Direct the production of task information using environment.
agreed systems.
Interface Manage spatial co-ordination on behalf of a task Propose resolutions to clashes.
Manager (BIM team.
Model Propose resolutions to co-ordination clashes.
Coordinator)
Information Develop constituent parts of the information Ownership of model information.
Originator model in connection with specific tasks.
(Model Manager) Production of project outputs.

Oct, 2023 Project Name

9

2.4.2 Project Phases / Milestones

Below is a high-level proposal for the major project milestones relating to information delivery and
proposed strategy for the delivery of the Project Information Model (PIM).

Project phase/milestone Estimated start date Estimated completion date

Pre-design
Concept design
Preliminary design
Developed design
Detailed design
Construction
Handover
Operation

2.4.3. Approval of Information

Approval will initially be managed within discipline (Task) teams with overall technical approval
responsibility being held by the ….

Project Information Model (PIM) Authorisation Process

The design and construction approval process for delivery of information is outlined below. This
process is identified to integrate with the Common Data Environment solution chosen and will be
signed off by the involved parties.

Add high-level Process of approvals.

Task Team A Task Team B Lead Consultant

Oct, 2023 Project Name

10

2.4.4.Project BIM Uses

List BIM Uses for specific project:

 Design Authoring
 Design Review
 Visualization
 Green Building (Building Performance)
 3D Coordination
 Construction work Analysis (4D)
 Cost Analysis (5D
 Digital Fabrication
 3D As Built
 Operation, Maintenance & Facilities Management

BIM Use Responsible parties Notes

2.4.4. Survey Strategy

Surveys, either completed or to be completed, of the existing site are identified below

Survey Method Delivery Format Survey Origin Details Notes

Point Cloud .RCP

Oct, 2023 Project Name

11

3. Planning & Documentation

Modeling Plan

Advance planning around which models will need to be created during the different phases of the
project, which will be responsible for updating models and distributing them and predetermining the
content and format of models as much as possible, will help your project run more efficiently and
cost-effectively during every phase.

The available software, and in particular platform versions across the supply chain are
identified in this section. This table provides a reference to the available systems across the
project team, from which conclusion on the required project platforms are identified within
section 6 of this document. Considering the available software platforms, there is
identification of possible exchange formats against the relevant BIM uses. The prescribed
exchange formats to be used within the project are identified in the table below.

BIM Use Supplier Software Version Native File Exchange

(Authoring Platform Type File Type
Team)
Planning & Team A Infraworks 2023
Feasibility Team B
Design
Authoring
Design
Review
Visualization

3d
Coordination
Construction
Simulation

Oct, 2023 Project Name

12

BIM Model Roles & Functions

Each party—such as the architect, engineers, contractor, or sub-consultants—that is responsible for

contributing modelling content should assign the function of Interface Manager/ BIM Model
Coordinator and Primary Information Originator (Model Manager) to an individual.

Interface Manage spatial co-ordination on behalf of a task Propose resolutions to clashes.

Manager (BIM team.
Model Propose resolutions to co-ordination clashes.
Coordinator)
Information Develop constituent parts of the information Ownership of model information.
Originator model in connection with specific tasks.
(Model Manager) Production of project outputs.

These functions have several responsibilities. They include, but are not limited to:
 Transferring modeling content from one party to another
 Validating the level of detail and controls as defined for each project phase
 Validating modeling content during each phase
 Combining or linking multiple models
 Participating in design review and model coordination sessions
 Communicating issues back to the internal and cross-company teams
 Keeping file naming accurate
 Managing version control
 Properly storing the models in the collaborative project management system

These responsibilities are supported by the other roles/functions mentioned in section 2.

Interface Manager (BIM Model Coordinator)

Stakeholder Company Name Email Phone

Name

Oct, 2023 Project Name

13

Information Originator (Model Manager)

Stakeholder Company Name Email Phone

Name

Authoring Software

The Design Team is required to use parametric BIM Authoring software for this project. All architects,
engineers, and specialty consultants are required to use the following design authoring software:

1. Autodesk Revit 2024

2. Autodesk Civil 3D 2024

All AE teams should be able to use the following software in its native file format in its current version
and latest service for communication with the Project Team.

New service packs will be communicated, also refer to link below:

Add link

Coordination Software

All final internal and external model coordination and conflict detection are required to use the
following software in its native file format:
1. Autodesk Revit 2024
2. Autodesk Navisworks 2024
Autodesk BIM Collaborate

Oct, 2023 Project Name

14

Document Management & Exchange Formats’

Information in the form of documents, drawings, models and Requests for Information (RFI’s)
are to be uploaded / logged via the chosen Common Data Environment. This process will
ensure consistent and accessible information is provided to the wide project team and,
accountability can be determined. These communications should not be delivered by email
or similar means, although notifications/links to the Common Data Environment is
appropriate.

Autodesk BIM 360 Docs will be used as the document sharing & Managing platform.
Please refer to detail regrading BIM 360 Docs in Annexure A.

Final Drawing Schedules/

Models Drawings
Format Spreadsheets
DWG x x x
DWFx x
IFC
RVT x
NWC x
PDF x x x
Excel x
Other

Additional requirements

As-Built Modeling Plan

As-built modelling will be a collaborative effort between the consultants and contractor. During the
construction process, the design team will incorporate changes triggered by requests for information
(RFIs) and change orders in into the models. At specified dates during the construction process, the
construction team will provide the design team with necessary changes due to shop drawings,
coordination drawings and change orders. As required, the completed form of the construction will
also be verified at these specified dates using laser scanning. The design team will then incorporate
the changes reported by the construction team into the models. At the end of construction, it will be
the updated Architectural and Consultant models that are used for facility management.

Oct, 2023 Project Name

15

Construction Team Software Requirements

1. Client & Contractor will use BIM 360 Docs to access data & manage model deliverables from the
Design Team.
2. Sub-contractors will author 3D shop drawings and as-built models in a platform, compatible with
Navisworks
3. Autodesk Revit 2021 will be used throughout the life of the project, for the entire design team.

Hardware Requirements

Design and Construction Team members shall utilize computer hardware that is sufficient to
effectively handle single model files up to 750 MB and aggregate models of up to 2 GB. Design team
should refer to the table below for recommended hardware specifications.

Stable internet connection is also required to utilise the document management system.

For more information about hardware requirements please view:

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/System-requirements-
for-Autodesk-Revit-2019-products.html
https://knowledge.autodesk.com/support/bim-360/learn-explore/caas/sfdcarticles/sfdcarticles/
System-requirements-for-Autodesk-BIM-360-Docs.html

Oct, 2023 Project Name

16

4.Standard Method and Procedures

Planned Models

The project will be broken down into processes and then again by building groups. Each model file
will contain all drawings and information relating to the buildings within it only.

In the table below, you will find the models that will be created for the project. The model name,
model content, project phase when the model will be delivered, the model’s authoring company, and
the model-authoring tool that will be used.

Model Name Model Contents Project Phase Authoring Authoring Tool

Company
Road Design Model Civil 3D
Topographic Model InfraWorks
Visualization Model 3ds Max
Construction Model Navisworks
GIS (Geographic
Information System) AutoCAD Map 3D
Model
Point Cloud Model ReCap

Water Services Model Civil 3D

Sewer Services Model Civil 3D
Stormwater Drainage Civil 3D
Model
BIM for Infrastructure InfraWorks
Model

The project will be subdivided into volumes or systems to reduce the impact of technical
limitations. How the model is subdivided and the process for any further subdivisions is
outlined below.

Oct, 2023 Project Name

17

Project Information Model Origin and Orientation

Project Base Point

Each team shall maintain the following coordinates for the Project Base Start Point and Survey Point:
Bench Mark:
Project Base Point:
N/S
E/W
ELEV
ANGLE

Coordination Responsibility
The lead appointed party (lead designer) is responsible for creating and issuing the site setup file. This
file is to be issued to all relevant disciplines and xyz coordinates will be acquired from this file.
All stakeholders are responsible for ensuring that their own information and models are coordinated
correctly to the prescribed coordinate system as outlined above before issuing to the Common Data
Environment.

File Naming Structure

The file naming structure is used to aid usability during future phases of the project, to specify content,
level of detail, appropriate file naming structure of your models and to help achieve consistency in
producing and viewing technical drawings.
Determine and list the structure for model file names and data format.
BIM file naming will be in based on with ISO 19650 or BS 1192 guidelines

The below must be used as the template for file naming:

Project Originator Volume/ Level/ Type Role Number

System Location
VP _ BSW _ 00 _ GF _ M3 _ A

Project:

The agreed alphanumeric project code (between 2 and 6 characters) for the project
specified below:

Code Project
SDP Sunninghill Office Park

Oct, 2023 Project Name

18

Originator:

A unique identifier attributed to each organisation as they join the project and recorded
below:
Code Organisation
BKB Baker Baynes

Each organisation will have their own unique identifier, consisting of 3 to 6 characters

Volume/System
Each individual team will provide a copy of their volume strategy in the form of a drawing of
each floor layout, section or site with volumes clearly marked named and inserted below.

Example:
When planning complex projects and determining the number of model files required, it is
commonplace and good practice for the project to be divided into volumes defined by
coordinates within an overall project model that will be held as separate model files. This
enables multiple users to work on the project efficiently. Volumes should be allocated using
cut lines to indicate their limits. Volume boundaries could be structural joints or grid lines; for
road projects they could be chainage distances; or they could be defined by use e.g. a
vertical distribution shaft.

Each team will provide a copy of their volume strategy in the form of a drawing of each floor
layout with volumes clearly marked and inserted below.

The Volume/System code is a 2-character identifier for use within the project, their related
codes are outlined below:

Standard Codes Description

ZZ All volumes/systems
XX No volume/system applicable

Level/ Location

Code Description
STA Stationing
CL Centerline
ROW Right-of-Way
EP Edge of Pavement
CG Curb and Gutter
SH Shoulder

Oct, 2023 Project Name

19

INT Intersection

Type
A unique identifier should be established for each type of information to identify the type of
information held within the information container and fixed within the project information
standard. The code should comprise 2 characters. The following standard codes should
apply.
Code Description
DR Drawing
M2 Two-dimensional model
M3 Three-dimensional model
VS Visualisation
SC Schedule or table
SP Specification
BQ Bill of Quantities
DC Document
CA Calculation
MS Method Statement

Role:
Each organisation role is mapped against their codes below, some organisations may fulfil
multiple disciplines specified in which case they will utilise the code assigned them in the
project information standard. The code can be x characters long.

Code Description Organisation

A Client
B Development Manager
C Project Manager
D Civil Engineer
E Geotechnical Engineer
F Surveyor
G Traffic Engineer
H Structural Engineer
J Environmental Engineer
K Cost Estimator
L Contractor
M Site Supervisor
N Quality Control
P Safety Officer

Number

Oct, 2023 Project Name

20

A sequential number that is assigned to each information container when it is one of a

series, not distinguished by any of the other fields. The number should be fixed within the
project information standards.
The code used will be between 4 to 6 integer numeric digits in length, used sequentially and
including leading zeroes.

Each discipline is to develop their own series of drawings in line with information packages

Layer Naming

Each discipline should provide the Design Manager and the CAD manager with a full list of all layer
names to be used on the project. This list should be published to all members of the project team for
information.

Field Discipline Classification Presentation Description

Name A - G23 - M2 _ Stairs
Example Architect Stairs (Uniclass) Model graphics (2D)

Drawing Sheet Templates

The drawing sheet templates to be used within the project are identified below along with their
storage location. All 2-dimensional deliverables provided will included the appropriate sheet template.
The quantity of drawing or schedule sheets should be kept to a minimum and arranged in a logical manner.
Drawing sheet names included within the model will be appropriate enough to derive the file naming
convention identified above.

Annotation, Dimensions, Abbreviations and Symbols

A list is included below of the agreed units of measurement to be used on the project by the involved
disciplines as is appropriate to each type of information.
Type of Length Area Volume Angle Currency Weight
Information

Dimensions must be automatically derived from the models created. Dimensions must not
be created as ‘text’ with no relationship to the underlying coordinates being measured.

Model Element Rules, General Completeness of design

All physical building elements within the project are to be modelled (except those listed and agreed
upon) and are to represent the full and complete design of each level and element of the building.
For example, if a single level of a building is identical to another level, each level is to be distinctly and
completely represented in the Design and Construction models. The same applies to identical partial
floor layouts.

Oct, 2023 Project Name

21

Items Excluded from modelling requirement:



Control Elements
LOCATION AND Link models by "Shared Coordinates". All models must align.
ORIENTATION
GRIDS Check in any floor plan if grids align in all models
LEVELS Check if levels align in all models. (Note: it is acceptable for SFL to be
different from FFL provided the difference in drops between both is
logical and consistent, and there is a corresponding SFL for every FFL.)

Precision and Dimensioning

Models should include all appropriate dimensioning as needed for design intent, analysis, and
construction.
Agreed construction tolerances for all disciplines:
Discipline Element Tolerance

Modeling Level of Development

Model elements by discipline, Level of Development (LOD) and any specific attributes important to the
project are documented below.

LOD by phase and discipline

Model Name Stage 03 Stage 04 Authoring Authoring Tool

Company
LOD LOD
Road Design Model
Topographic Model
Visualization Model
Construction Model
GIS (Geographic
Information System)
Model
Point Cloud Model

Water Services Model

Sewer Services Model
Stormwater Drainage
Model
BIM for Infrastructure
Model

Oct, 2023 Project Name

22

Road Design Model

Topographic Model

Collaborative model development: At each project milestone, Model Managers are responsible for
developing each Model Element to the Level of Development (LOD) shown in the LOD table

LEGEND FOR LOD TABLE

LOD Level of Development
100 Conceptual The Model Element may be graphically represented in the Model with a symbol or
other generic representation but does not satisfy the requirements for LOD 200.
200 Approximate The Model Element is graphically represented within the Model as a generic
geometry system, object, or assembly with approximate quantities, size, shape, location, and
orientation. Non-graphic information may also be attached to the Model Element.
300 Precise The Model Element is graphically represented within the Model as a specific
geometry system, object or assembly in terms of quantity, size, shape, location, and
orientation. Non-graphic information may also be attached to the Model Element
400 Fabrication The Model Element is graphically represented within the Model as a specific
system, object or 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.
500 As-built The Model Element is a field verified representation (i.e., as-built) in terms of size,
shape, location, quantity, and orientation. Non-graphic information may also be
attached to the Model Elements.

https://bimforum.org/resources/Documents/BIMForum_LOD_2019_reprint.pdf

Design Model Ownership of Elements

A – Architect; M – Mechanical; P – Plumbing; E – Electrical, F- Fire Engineer, S-Structural

Model Element Discipline Owner
Grids Architectural
Steelwork & Columns Structural
Exterior Architectural
Ramp slabs/stair steps & stair landing slabs Architectural
Floor slabs Structural
Foundation walls- retaining, stair/ramp walls, entry foundations Structural
Roof Deck Architectural & Structural
Finish (floor) Architectural
Wet Services Mechanical
HVAC Mechanical Layouts Mechanical

Oct, 2023 Project Name

23

Electrical Layouts Electrical

Fire Safety Fire Engineer
Ceilings Interior
Hose Reels Fire
Façade Architects /Façade Engineer
Scanner & Security Equipment Data
Custom Joinery Interior
MCC Panels Electrical

Design Authoring
It is essential that during onerous programme requirements pressure is not given to technical staff to
revert to “offline” traditional 2D working to hit deadlines, as this can have a negative effect on the final
delivery of a coordinated design.

Design Reviews (BIM Enabled)

It is recommended there are regular BIM co-ordination/workgroup meetings attended by BIM

coordinators and designers from each design discipline. These should take place directly before
design team meetings if possible. The active use of models during design team meetings is also
essential and meeting facilities should include provision for a projector, screen and laptop/PC.

This section contains the dates of the design reviews (BIM enabled) and workgroup meetings;

5.Common Data Environment

The chosen Common Data Environment for the project is XX

The CDE will be managed by ##### however it will be the responsibility of each stakeholder
to upload and manage their information within the provided sections of the CDE; those
responsible for management of the CDE within each discipline are identified below.

Oct, 2023 Project Name

24

Team Role / Company Primary Contact

Discipline
Name
Email
Phone Number
Name
Email
Phone Number

The prescribed process for uploading and maintaining the sections within the CDE are
included below, along with the required standards to be complied with within the CDE.

Annexure A – BIM 360 CDE User Guide.

Electronic Communication procedures

Communication protocol should be established between all project team members to ensure smooth
collaboration.

With a potentially large number of disciplines and contractors working on the project, ensuring the
various forms of information and communication utilised within the project are transferred in the most
effective way possible is critical. The chosen methods of communication and information transfer are
detailed within this section and kept up to date.

 Email communication should be used where appropriate for discussion or general

communication, unless it stipulated to bring these within the common data environment.
Email communication should be kept to a manageable level and suitable solutions should be
used for tracking and email storage.

 Information in the form of documents, drawings, models and Requests for Information (RFI’s)
are to be uploaded / logged via the chosen Common Data Environment. This process will
ensure consistent and accessible information is provided to the wide project team and,
accountability can be determined. These communications should not be delivered by email

Oct, 2023 Project Name

25

or similar means, although notifications/links to the Common Data Environment is

appropriate.

 Communication by phone is appropriate for situations requiring quick short responses or

general communication; however, any decisions established should be clarified in written
form on the Common Data Environment or within email as appropriate.

It is expected that the below get’s communicated via Autodesk BIM 360:
 List Here

Oct, 2023 Project Name

26

6.Coordination & Clash Detection Process

The use of 3D collaborative BIM technologies and processes to ensure a fully co-ordinated design is
delivered at the end of each project stage. The lead appointed party (designer / contractor) will
ensure that coordinated models form each design discipline (including subcontractor design
elements) are regularly checked using coordination tools, with a written report demonstrating that all
spatial conflicts have been identified and resolved. Model and report files to be uploaded to specified
repository in native and IFC format for third party review.

All traditional design documentation such as drawings and schedules must be derived directly from
3D building information models, not produced as separate work streams.

Models are audited by the BIM Leader to report to the client on compliance with the BEP, and other
standards reference in this document.

Clash Detection

A Clash detection is done to check for interferences between the designs of one or many models. To
reduce change orders during construction, clash detection checking should be performed early and
continue throughout the design process. For Clash detection to work properly, your project’s models
need to have a common reference point and they must be compatible with Navisworks Manage/BIM
Collaborate Pro.

Clash detection will be carried out at two levels. All disciplines will be responsible for developing their
models in a coordinated manner. This involves ensuring they have the latest version of the available
models referenced into their design models to provide the ability to coordinate; updating of referenced
models will be carried out following each of the agreed model upload intervals. The process for
coordination and the requirements to be checked are outlined below:

The lead appointed party (lead consultant) or their appointed representative, identified in Section
Roles, Responsibilities and Authorities, will carry out coordination reviews including clash detection to
identify any key issues with the quality of the work being produced. These reviews are to develop a
coordinated model and will inform project review meetings. These will be carried out at key stages
identified below.

Oct, 2023 Project Name

27

Coordination Milestone

Coordination Review Date Associated Milestone Clash Detection Protocols/Requirements to be

Checked
##/##/## #### Visual Check – Ensure there are no unintended model
components and the design intent has been followed
##/##/## #### Interference Check / Clash Detection - Detect problems
in the model where two building components are
clashing including soft and hard
##/##/## #### Standards Check - Ensure that the project BIM
Standard have been followed (fonts, dimensions, line
styles, levels/layers, etc)
##/##/## #### Model Data Check - Process used to ensure that the
project data set has no undefined, incorrectly defined
or duplicated elements and the reporting process on
non-compliant elements and corrective action plans
##/##/## #### Automated BIM Validation - Automated process
carried out by software, implementing specific rule
sets designed to identify issues relating to the quality
of geometry and data which may lead to inaccurate
data driven from analytics and cost management
processes.
##/##/## #### Model Audit - Manual and automated audit of models
and process against BEP and referenced standards

Oct, 2023 Project Name

28

Clash Detection Guideline

Service 1

Stormwater
Structural

Electrical
Fire
Civil
Structural
Civil
Stormwater
Fire
Service 2

Electrical

Service 1 move
Service 2 move
Both Review

Clash Assignment and resolution process

The above matrix should be used as a guideline there will be exceptions. It is expected that common
clashes are resolved prior to coordination meetings and only exceptions and complicated clashes are
discussed in coordination meetings.

Coordination Meetings
a. Coordination meetings will typically occur each <day> at <time> at <location>.
b. Weekly model submittals are due two days prior to the coordination meeting ( <day and time>).

Oct, 2023 Project Name

29

Oct, 2023 Project Name

Do not distribute.

Annexure A: BIM 360 DOCS

Folder Structure Overview

Permission Level Overview

Permission definitions:
31

Oct, 2023 Project Name

32

Issue Management:

Used by teams to identify and communicate areas of concern or improvement with the project
documents.

The ability to create, assign, track, and respond to issues on any device is critical to making
sure your project is completed on time and on budget. Put context around the issue resolution by
dropping pins on designs, adding photos in the field, and collaborating on comment threads. With a
central view of all project issues, tracking status and analyzing root causes has never been easier.

Issue Status definitions

There are 2 statues sets that Control the workflow of issues:

1. Basic Issues:
a. Draft – The issues is still in the process of being created
b. Open – The issue has been created for review and sent to responsible party
c. Answered - Responsible party has responded to the issue
d. Closed – The issue has been resolved

2. Field issues
a. Work Complete – Work has been completed on the issue
b. Waiting for Inspection – Awaiting inspection of issue on site
c. Not Approved – The reviewer has rejected the work completed on the issue
d. In Dispute – The issue has not been settled with either party
e. Void – The issue does not have any value or is invalid

Markups
An essential tool for drawing revisions and corrections and Models and PDF drawings with mark-up
annotations such as text, lines, boxes, circles, and arrows.

Markups speed up the decision-making process with the ability to instantly communicate questions,
changes, and other information regarding the project drawings and models. The measurement tools
enable project team members to accurately verify dimensions and areas. Document managers can
organize project drawings and link them to other project drawings or documents, ensuring that the
project team has a complete and easy-to-navigate package of construction documents.

Workflow setup Overview

Oct, 2023 Project Name

33

Annexure B: BIM 360 Build

Oct, 2023 Project Name