3 Uoc Bimexecutionplan v1.1.1

Building Information Modelling (BIM)
Execution Plan
For University of Cambridge
University of Cambridge
Estate Management
Greenwich House
Madingley Road
Cambridge
CB3 0TX
United Kingdom
Insert Project Name

BIM Execution Plan
Insert Project Name
BIM Execution Plan
Insert Project Name
Rev Originator BIM Approved Date
1.0 C Hinton BIM Strategy Group 26/06/15
1.1 C Hinton Amended MPDT 03/09/15
1.1.1 C Hinton EM Address Update 03/02/16
Controlled Document Distribution
The Building Information Modelling Execution Plan (BEP) is a controlled document and shall
be reviewed, approved and distributed under controlled conditions.
This revision of the BEP is to be formally issued to:
Nr Recipient Organisation
001
002
003
004
BIM Execution Plan
Insert Project Name
Contents
1 PURPOSE OF DOCUMENT 4
2 INTRODUCTION 5
3 PROJECT OVERVIEW AND AIMS 6
4 BIM REQUIREMENTS AND PROCESSES 8
5 PROJECT PROGRAMME 9
6 PROJECT TEAM, STAKEHOLDERS AND RESPONSIBILITIES 11
7 DELIVERABLES AND OUTPUTS 12
8 COLLABORATION 13
9 STANDARD METHOD AND PROCEDURE 17
10 PROJECT CLOSE OUT 20
11 ABBREVIATIONS & GLOSSARY OF TERMS 21
APPENDIX A MODEL PRODUCTION DELIVERY TABLE (MPDT) 25
APPENDIX B DROP SCHEDULE 26
APPENDIX C PROJECT DIRECTORY 28
APPENDIX D ROLES AND RESPONSIBILITIES 29
APPENDIX E CDE FOLDER STRUCTURE 35
APPENDIX F INFORMATION EXCHANGE SCHEDULE 37
APPENDIX G MEETINGS TERMS OF REFERENCE 40
APPENDIX H QUALITY CONTROL PROCEDURES 41
BIM Execution Plan
Insert Project Name
1 Purpose of document
The Building Information Modelling Execution Plan (BEP) is a core approved document which
defines the BIM strategy and processes for the successful completion of Insert Project Name
principally as a Level 2 BIM project in line with the objectives of the University of Cambridge.
This document outlines the following to support collaborative processes to produce the
information required by University of Cambridge and provide support to the contract
coordinator throughout the entire life cycle of the project:
Responsibilities
Requirements and processes
Best practices
Methods and protocols
Relevant business processes
Supporting software requirements
This document should be considered for use to support information provided for further
consultant and contractor appointments and define requirements for consultant deliverables. For
additional project phases and further workstages outside of the scope of this document, this
information may be superseded under cover of letter distributed by the Client, but fundamental
standards and naming / data structures shall be continued throughout the project.
No part of this document should be construed as preventing the Consultants, Specialist

Subcontracts and Specialist Suppliers from sharing their respective models at any time and in
any format if this is to be helpful to project progress and co-ordination.
BIM Execution Plan
Insert Project Name
2 Introduction
2.1 Distribution
The BEP has been prepared with the support of the Client and project team, and will
enable the proper administration of the document through revision and controlled re-
issue.
The BEP will be issued (or removed) from use under cover of letter or formal project
managers instruction. Recipients of documents will be required to confirm that current
issues are held and that relevant people are holding all applicable information.
2.2 Project execution through BIM
To allow the successful implementation of BIM, the teams capability and capacity has
been assessed. In this context, requirements and processes to support the delivery of
University of Cambridge requirements are detailed in this BEP.
2.3 Applicable standards
In order to establish a consistent approach to collaboration, University of Cambridge

requires the core project team and its associated supply chain to adopt all standards,
as defined in Section 3 of the Employers Information Requirements. This in
addition to the BEP and other industry standards outlined below.
M = Mandatory
Application
R = Recommended
Object naming
Project stages
Collaboration
Classification
File naming
Contracts
Guidance
Standards
Drawing
Costing
COBie
CDE
LOD
Additional or superseding
standards
Bespoke Industry
BIM Execution Plan (BEP) M M M M M M M
Table 1: Applicable standards
In order to facilitate the effective use of BIM on this project, the CIC BIM
protocol may be appended to any appointment documentation.
BIM Execution Plan
Insert Project Name
3 Project overview and aims

3.1 Project overview
Client University of Cambridge
Project name Insert Project Name
Short project description
Project address
Correspondence address
Project value
Contract type
Plan of works RIBA Plan of Works 2013

Table 2: General project information
BIM Execution Plan
Insert Project Name
3.2 Project BIM objectives
3.2.1 Success factors
At the highest level, general project success factors provide the basis for BIM process
development and have been described in the Employers Information Requirements.
Any additional success factors will be released within further amendments of this
document.
3.2.2 Documents and mechanisms
Project processes and contractual mechanisms are as follows:
Agreed Employers Information Requirements (EIR).

Contractual protocols that support the success factors and requirements.
Provision of a Common Data Environment that supports the success factors and requirements.
3.3 Key Performance Indicators (KPIs)
A set of KPIs is to be agreed and documented in the Project Execution Plan. These
require data input from the relevant project team members. Once agreed, KPIs which
affect BIM processes and deliverables are to be documented in the next revision of
the BEP.
Insert KPI 1
Insert KPI 2
Insert KPI 3
Insert KPI 4
BIM Execution Plan
Insert Project Name
4 BIM requirements and processes

4.1 Building Information Modelling (BIM) uses
Refer to Section 6.7 of the EIR for a complete list of BIM uses that have been
categorised by the client. Uses identified as High should be fulfilled for Insert Project
Name. Moderate and Low uses that are to be implemented on this project should be
agreed through team collaboration with University of Cambridge.
4.2 Level of Definition
4.2.1 Summary
Requirements for development of geometry definition and model usability are mapped
against project work stages to support the project deliverables and support BIM uses.
These requirements are to be understood by all consultants and incorporated in the

post-contract BEP. Interpretation and meaning of Level of Definition is in accordance
with the NBS BIM Toolkit Specification. Refer to Appendix D of the EIR.
4.2.2 Geometric information requirements Model Production Delivery Table
The level of development required at each project work stage (RIBA PoW 2013) and
the party responsible for delivering that information is defined in Appendix A. This
must be strictly adhered to unless explicitly agreed by all relevant parties including the
BIM Leader and University of Cambridge.
In future work stages, any amendment to Level of Definition requirements must be

explicitly agreed by all members of the project team to the benefit of the project.
Stakeholders will ensure that the Model Production Delivery Table (MPDT) is in
alignment with the project design responsibilities matrix and provide comments to this
effect.
4.2.3 Non-geometric information requirements
The following is defined in Appendix A and Appendix B of the EIR.
COBie requirements (Matrix)
Basic parameter requirements
Client specific requirements for asset data
It is important that all stakeholders familiarise themselves with the parameter

requirements and ensure that BIM object templates and component lists take into
consideration the data type required.
BIM Execution Plan
Insert Project Name
5 Project programme
5.1 Master programme
The main elements of the master programme has been developed to include BIM
processes, design, procurement, construction, commissioning and completion. The
project team is required to adhere to this programme and commit resource as
necessary to achieve the required dates.
Detailed programmes have been realised within the constraints set by the master
programme. This includes a design programme, a construction programme, an
operation programme and a BIM implementation programme.
5.2 BIM implementation programme
The BIM implementation programme has been created by the BIM Leader and
illustrates the main activities associated with initiating and monitoring BIM processes
referred to in APPENDIX J of the EIR.
Taking into account the master project programme, and through engagement with the
Client and project team, the following constraints and milestones have been identified
as impacting the BIM implementation programme:
Site conditions
Planning permission
Tender process
Key data drops
BIM data exchange trial
5.3 Project milestones
The following milestones are based on the Master Programme dated 00/00/0000:
Milestone Date
Insert project milestone 1 00/00/0000

BIM Execution Plan
Insert Project Name
Critical milestones for the execution of Insert Project Name as a fully collaborative BIM project are the data drops. The dates for these drops can be
found at Appendix B.
Figure 1: Data drops and gateway points through the project lifecycle
Refer to Section 7.3 of the EIR to more information regarding data drop management.
BIM Execution Plan
Insert Project Name
6 Project team, stakeholders and responsibilities

6.1 Overview
The various parties to the project, their roles, responsibilities and relationships are
described in this section to minimise duplication or gaps. All parties should make a
concerted effort to maintain continuity of personnel.
A full Project Directory is included in Appendix C.
6.1.1 BIM capability
Consultant teams have been assessed as to their competency to work utilising a

collaborative, iterative approach, facilitated by BIM.
Where appointed team members are identified as requiring support in this area, the
potential impact to the project should be assessed and appropriate measures, such
as training or mentoring from other team members should be undertaken.
6.2 Roles and responsibilities
BIM roles and responsibilities are described in this section. Please refer to the current
version of the project execution plan for overall scopes of services.
Notwithstanding the specific responsibilities contained in Appendix D, each

organisation is obligated to nominate a BIM coordinator to undertake the following
activities:
Coordinate all technical discipline and trade specific BIM activity within their
organisations
Manage BIM uses assigned to their organisation
Coordinate any BIM related issues with the rest of their discipline team
Support their organisation in the use of BIM tools
Create discipline specific BIM content
Coordinate discipline specific clash detection and resolution activities
Export their own organisations model for inter-disciplinary clash detection
Coordinate BIM training as required

BIM Execution Plan
Insert Project Name
7 Deliverables and outputs

7.1 Modelled information
The employer requires information to fulfil the following purposes:
A full registration of assets is required to support accurate auditing and reporting.

Every identifiable internal or external space shall be captured within the BIM and /
or associated data sets in addition to every distinct floor containing them. Zones
shall also be identified within the COBie deliverable.
Facility, Floors (regions), Zones and Spaces (locations) shall be documented with
their net and gross areas. The method of measurement used shall be documented
on the Facility sheet of the COBie deliverable. This is to enable accurate space
planning and to ensure that the complete asset meets the intended purpose.
Information necessary for the normal operations of the facility shall be provided to
support the facility operators and the employer to anticipate costs of operations.
During the life cycle of the project the plain language questions, specified in
Appendix M of the EIR, are presented and the project team must provide sufficient
information to adequately satisfy the questions.
7.2 Two-dimensional outputs
Information cross sectioned from the model will be shared using traditional drawing
conventions. Drawings, renders, reports and schedules shall provide the following:
Information only for the purpose of the intended use
Minimise repetition of illustrated details and no duplication of drawings
Logical and accessible arrangement of information
Note: Consultants will comply with all Space Numbering and Measuring specified in
Appendix F and G of the EIR. If an instance occurs where this is not feasible /
possible, consultants will bring this to the attention of the project team and endeavour
to resolve issues during the next BIM workgroup meeting.
BIM Execution Plan
Insert Project Name
8 Collaboration
8.1 Approved software and versions
Software versions shall be agreed at the outset and not deviated from. Please note
any changes to software and upgrades to versioned software to be used on the
project must be agreed by all parties prior to actioning any upgrade.
Only tools identified below shall be used to author, coordinate and validate BIMs. This
is to facilitate interoperability between software platforms and enable the successful
execution of the interoperability strategy.
Discipline Software & Version
Architectural Insert Software 1 & Version

Interior Designer Insert Software 2 & Version
Landscape Architect Insert Software 3 & Version
Structural Insert Software x & Version
Building Services
Insert Software x & Version
Engineer
Civil Engineer Insert Software x & Version
Structural Engineer Insert Software x & Version
Cost Manager Insert Software x & Version
Facilities Manager Insert Software x & Version
Collaboration Insert Software x & Version
Table 3: Software and Version
8.2 Common Data Environment (CDE)
To support BIM workflows, communication must be controlled and methodical. Team

members should communicate frequently and interactions (including digital
communication and records of meetings) should be stored on a CDE and made
available to appropriate members of the project team. Access to information should
be determined through engagement between the Information Manager, University of
Cambridge and other project stakeholders.
CDE for this project Insert CDE name & Version
Contact details Insert name and contact details
Table 4: Common Data Environment (CDE)

BIM Execution Plan
Insert Project Name
8.2.1 Responsibility
It is the responsibility of all stakeholders to store and maintain a copy of all project
information in a secure stable location within their own organisation. Stakeholders will
make information available to the project team and University of Cambridge over
the CDE in accordance with this document. University of Cambridge shall have
access to native models to be issued within three working days of a Client Request for
Information (RFI).
As a minimum, all BIM coordinators and the BIM Leader should be notified via the
CDE when BIM data is distributed.
If any issues arise or if information has been uploaded incorrectly, stakeholders

should inform the Information Manager for resolution. All documentation and design
information, including models, drawings, associated data and RFIs will be shared via
the CDE without exception. Email or alternative forms of electronic / physical
transmission are not to be utilised unless required for contractual compliance.
8.2.2 User privileges
For security, user access and change privileges for workspace folders and information
should be carefully considered and agreed with the Client, Information Manager and
BIM Leader in collaboration before implementing the CDE. Any change to user
privileges must be agreed by the Client or Clients representative. Access privileges
are detailed in Appendix E.
8.2.3 Structure / Purpose
All BIM information will be exchanged in the CDE using the folder structure as
outlined in PAS1192-2:2013 see Figure 2. To support security and accessibility of
information, folder locations and upload purposes must be strictly adhered to.
Any amendments to the naming or structure of the CDE workspace must be explicitly
agreed with the project team and University of Cambridge, including the Information
Manager. For native and exchange formats please see the exchange schedule,
Appendix F.
BIM Execution Plan
Insert Project Name
Figure 2: CDE collaboration process
8.2.4 Data exchange protocol
8.2.4.1 Methodology
Consultants will adhere to the following:
All data is to be exchanged via the CDE.
Model naming should be in accordance with University of Cambridge CAD

Standards.
All significant, known errors with the model should be declared to recipients by the
originating consultant.
All models are to be uploaded in their native format and also in the agreed file
sharing format/s for use by others, refer to Appendix F.
BIM Execution Plan
Insert Project Name
All previous versions are to remain on the CDE.
8.2.4.2 Schedule
The use and responsibility, format and frequency of shared information should be
understood by all project team members. It is crucial that this is agreed and recorded
in the Information Exchange Schedule, Appendix F.
8.2.4.3 Trial
The Lead Designer will facilitate a trial of data exchange over the CDE, which
includes the linking of project models. This process will help identify any unknown and
unique issues with collaboratively exchanging information amongst the appointed
consultants, thereby potentially mitigating errors and increasing efficiency of
information exchange.
8.3 BIM workgroup meeting (BWM) and BIM workshops
The frequency of BIM workgroup meetings (BWM) and BIM workshops, as defined in
Appendix G, should reflect the intensity and complexity of scheduled BIM processes,
in alignment with the project programme. Scheduled BIM workgroup meetings will be
included in the programme.
Meetings are to be chaired and recorded by the BIM Leader unless otherwise agreed
in advance. Where possible, to encourage shared information and optimise
resourcing, meetings should coincide with design team or Client meetings.
BIM Execution Plan
Insert Project Name
9 Standard method and procedure

9.1 Model units of measurement
All models and associated design information will be produced and communicated
using:
The metric system
RICS New Rules of Measurement 1 (NRM1) 2013
Models will be drawn at 1:1 (full size) in millimetres to ensure accuracy.
9.2 Coordinates system
A common building grid shall be established and used by all members of the design
team. It is common practice to define a building origin at the bottom left-hand corner
of the building using a datum marker. Due to certain software limitations with
geospatial coordinates this point should be 0, 0, 0.
A datum marker of a 1m x 1m x 1m box set centrally at the geospatial coordinates

point of 0, 0, 0 which allows position, scale and rotation confirmation upon import of
linked models, shall be used.
If accurate survey information is available it should be used as a basis to correctly

define project coordinates. Gridlines should be obtained from survey data by the lead
designer, and redistributed in native BIM format via the CDE for use by other project
team members. This should include project datum, Northings and Eastings. All team
members are requested to adopt coordinate settings, project datums and grids from
the lead designers information.
9.3 BIM Use Processes
The BIM Leader/Information Manager is to include and document the detailed

processes for all BIM uses, as set out in Section 6.7 of the EIR.
9.4 Design authoring and model set up
To enable project team members to work individually, the following models are being
created in parallel based on a common structure developed and agreed by the design
team:
Author
Architectural model Insert Lead Design
Building services model Insert MEP Engineer
Structural model Insert Civil and Structural Engineer

BIM Execution Plan
Insert Project Name
Site management model Insert Contractor
Landscape model Insert Landscape Architect

Table 5: Models
The model segregation strategy for each design discipline is to be agreed with the
Lead Designer and BIM Leader, and recorded in the next revision of this
document.
9.5 Area and quantity calculation
Refer to Section 4.13 of EIR.
9.6 Model authoring best practice
Refer to Section 4.14 of EIR.
9.7 Model validation protocols
All internal model validation protocols should be issued to the Lead Designer for
review following appointment.
BIM coordinators and stakeholders responsible for producing BIM information should
adhere to the following:
Validation procedures defined in this BEP should be undertaken in accordance

with Appendix H. Completion of this task should be recorded via the CDE through
a short report, issued when uploading models to the Shared folder
A model segregation plan should be agreed with the BIM Leader. Segregation
protocols and wayfinding should be recorded in the next iteration of the BEP.
Before sharing models they should be purged of any obsolescent objects or CAD
imports
Models should be closed in plan view or disclaimer view if available to avoid

additional time opening the document
Rogue, random or misplaced objects shall be corrected or omitted
Naming of the project file should be checked and approved before uploading to the
CDE
All dependant, parent or central files shall be disassociated prior to upload

providing access to model processors
BIM Execution Plan
Insert Project Name
9.8 Resolution of conflicts
The federated BIM will take precedence over any and all documents where conflicting
information has been issued.
The Lead Designer is still responsible for overall design coordination, irrespective of
the BIM process or digital tools used.
10 Project close out
Obtaining feedback and sharing lessons learned is an essential part of the project
which enables continuous improvement.
The project shall be reviewed in terms of the project success criteria and key
objectives and performance indicators, at each of the project stages identifying both
the successful and less successful aspects of the process.
10.1 BIM handover
Asset information should be delivered in the COBie UK 2012 format, as prescribed in

the data drop detail and in accordance with requirements to be developed for the
Asset Information Model through further engagement with the Facilities Manager. This
information should reflect the data structure defined for the project (see Appendix A
and Appendix B of the EIR), which is to be developed further through engagement
with the facilities management team.
Elements of the Soft Landings approach are being considered by University of

Cambridge. If required, these are to be incorporated into this document and agreed
by the project team.
20 ma k in g th e di f f er en c e
11 Abbreviations & Glossary of Terms
11.1 Abbreviations
BEP BIM Execution Plan
BIM Building Information Modelling
BWM BIM workgroup meeting
CDE Common Data Environment
EIR Employer Information Requirement
IFC Industry Foundation Classes
LOD Level Of Detail
LOI Level Of Information
MPDT Model Production Delivery Table
WIP Work In Progress
11.2 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 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.
Building Plan prepared by the suppliers, facilitated by the Client or

information the Clients BIM representative to explain how the
modelling information modelling aspects of a project will be carried out
execution plan
(BEP)
Building Process of designing, constructing or operating a building or

information infrastructure asset using electronic object-oriented
modelling (BIM) information
BIM Coordinator A BIM Coordinator is the nominated BIM person for that role
on the project, for example the Architecture/Interior/Civil and
Structural teams will each put forward a BIM Coordinator as
the contact point for the BIM aspect of the project.
BIM Leader The BIM Leader is usually a client representative

overseeing the implementation of BIM on the project
CIC Scope of Multi-disciplinary scope of services published by the

Services Construction Industry Council (CIC) for use by members of
the project team on major projects
COBie Structured facility information for the commissioning,

(Construction operation and maintenance of a project often in a neutral
Operation spread sheet format that will be used to supply data to the
Building client or operator to populate decision-making tools, facilities
information management and asset management systems
exchange)
Common data Single source of information for any given project, used to
environment collect, manage and disseminate all relevant approved
(CDE) project documents for multi-disciplinary teams in a managed
process. This is commonly a cloud based Software as a
Service (SaaS) solution synchronised with party servers to
host the information model
Data Information stored but not yet interpreted or analysed
Design intent Initial version of the project information model (PIM)
model developed by the design suppliers
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 have a

project or asset
Employer Individual or organization named in an appointment or

building contract as the employer
Employers Pre-tender document setting out the information to be

information delivered, and the standards and processes to be adopted
requirements by the supplier as part of the project delivery process
(EIR)
Federated Model When each individual model for each role is hosted into one
single model, this is the federated model.
Graphical data Data conveyed using shape and arrangement in space
Lead Designer The Lead Designer (usually the architect) works with the
BIM Leader and Coordinators to deliver the BIM aspect of
the project
Level of Definition Collective term used for and including level of model detail
and the level of information detail
Master Primary plan for when project information is to be prepared,

information by whom and using what protocols and procedures,
delivery plan incorporating all relevant task information delivery plans
(MIDP)
Pre-contract BEP The pre-contract BEP is to demonstrate the suppliers

proposed approach, capability, capacity and competence to
meet the EIR. It is utilised prior to the appointment of any
stakeholder.
Post-contract The post-contract BEP is the document defining standard

BEP methods and procedures adopted during the contract in
order to meet the objectives and requirements set forth in
the EIR. It utilised following the appointment of project
stakeholders and in particular the main contractor.
Project Statement relating to the suppliers IT and human resources

implementation capability to deliver the EIR
plan (PIP)
Standard method Set of standard methods and procedures covering the way
and procedure information is named, expressed and referenced
(SMP)
Volume Manageable spatial subdivision of a project, defined by the
project team as a subdivision of the overall project that
allows more than one person to work on the project models
simultaneously and consistent with the analysis and design
process
APPENDIX A Model Production Delivery Table (MPDT)
UniversityofCambridge LOD&ModelProductionDeliveryTable
TheModelProductionandDeliveryTable(MPDT)isakeydocumentasitbothallocatesresponsibilityforpreparationoftheModelsandidentifiestheLevelofDefinitionthatModelsneedtomeetatthe
Originator Reference
projectstagesordatadropsstatedinthetable.
CoreModels
Architecture ARC
Structural CSE
Modeloriginatorandresponsibleparties,mustbenamed. UniversityofCambridge
MEP MEP
ModelsshouldbeaddedasrequiredandagreedbytheprojectPIM. InsertProjectName
Contractor CON
ModelProductionDeliveryTable
AdditionalModels CostdatashouldbeproducedatNRM3forlaterstages(levels1&2shownbelowforclarity).
Eg.Landscaping Eg.LAR
LODandLOIaredeliverablesforeachstage.(ForLODandLOIdefinition,seeUniversityofCambridgeEIR,AppendixE.)
Consult Implementation&Delivery AssetOperation
RIBA2013(CIC)Workstage 1 2 3 4 5 6 7
Preparation&Brief Concept DevelopedDesign TechnicalDesign Construction Handover&Closeout InUse
LOD LOI RespParty LOD LOI RespParty LOD LOI RespParty LOD LOI RespParty LOD LOI RespParty LOD LOI RespParty LOD RespParty
Elements,Materials&Components(NRM1)
1Substructure
1Substructure 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
2Superstructure
1Frame 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
2Upperfloors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
3Roof 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
4Stairsandramps 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
5Externalwalls 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
6Windowsandexternaldoors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
7Internalwallsandpartitions 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
8Internaldoors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
3Internalfinishes
1Wallfinishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
2Floorfinishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
3Ceilingfinishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
4Fittings,furnishingsandequipment
1Fittings,furnishingsandequipment 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
5Services
1Sanitaryinstallations 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
2Servicesequipment 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
3Disposalinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
4Waterinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
5Heatsource 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
6Spaceheatingandairconditioning 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
7Ventilation 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
8Electricalinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
9Fuelinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
10Liftandconveyorinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
11Fireandlightningprotection 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
12Communication,securityandcontrolsystems 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
13Specialistinstallations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
14Buildersworkinconnectionwithservices NA NA NA NA 2 2 MEP 3 3 MEP 3 3 CON 5 5 CON TBC FMA
8Externalworks
1Sitepreparationworks NA NA NA NA NA NA 4 4 ARC 4 4 CON NA NA NA NA
2Roads,paths,pavingsandsurfacings 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
3Softlandscaping,plantingandirrigationsystems 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
4Fencing,railingsandwalls 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
5Externalfixtures 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
6Externaldrainage 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
7Externalservices 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
8Buildersworkinconnectionwithexternalservices NA NA NA NA 2 2 MEP 3 3 MEP 3 3 CON 5 5 CON TBC FMA
APPENDIX B Drop Schedule
Additional discipline models and the parties responsible are to be added to all required
data drops.
Data Date Project File submitted Format Responsible party

drop stage
1 Dd/mm 1 COBie drop .XLS Architect name

/yy
Architectural Model .IFC Architect name
2 Dd/mm 2 COBie drop .XLS All design consultants

/yy
Structural & Structural .IFC Civil & Structural

Model Engineer
MEP Model .IFC MEP Engineer name

/yy

Model Engineer

/yy

Model Engineer
5 Dd/mm 5 COBie drop .XLS Contractor name

/yy
Project Information .IFC Contractor name
Model
Specialist designer .IFC Specialist name

model
6 Dd/mm 6 COBie drop .XLS Contractor name
Data Date Project File submitted Format Responsible party
drop stage
/yy Asset Information .IFC Contractor name

Model
7+ Dd/mm 7 COBie drop .XLS Facilities Manager

/yy
Asset Information .IFC Facilities Manager
Model
APPENDIX C Project directory
Insert ALL details of ALL roles. Ensure details are kept up to date throughout the project life
cycle.
Mobile Office
Role Company Contact Address Phone Phone Email
No. No.
Company Contact
Client Address Phone Phone Email
Name name
BIM Leader
Information
Manager
Architect
Interior
Designer
Landscape
Architect
Building
Services
Engineer
Civil and
Structural
Engineer
Project
Manager
Cost
Manager
Facilities
Manager
CDM
Coordinator
Contractor
APPENDIX D ROLES AND RESPONSIBILITIES
BIM roles and responsibilities are described in this section. Please refer to the current
version of the project execution plan for overall scopes of services.
R = Responsible (Undertaking task)
A = Approving Authority (Delegating tasks and validating compliance)
C = Consulted (Providing input to achieve the task)
I = Informed (Kept informed about the tasks and/or outputs)
*= as required
Information Manager
Specialist Contractor
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
CDE
Advise on a CDE A I C R
Provide a CDE R I I I I I I I I I
Set up the CDE A C C C C C R C C C
Maintain the CDE C I C C R C
Download/upload all project

R R R R R R R R R
information from/to the CDE
Resources
Appoint consultants, including

R C
Information Manager
Ensure that the necessary software

and hardware are in place within the
R R R R R R R R R R R
organisation to support efficient
delivery of the project
Assess all sub-contracted

organisations (design or construct)
according to the BIM assessment I I R R R R R R
criteria contained in the Capability
Assessment
Report any emerging skill gaps within

I R R R
the team
Information Manager
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
Provide guidance to assist in

procuring the right type of training I I I I I R I I I I I
from credible industry professionals
Co-ordinate training for your own

R R R R R R R R R R R
organisation
Project strategy
Establish BIM requirements for the

C I R
project, long term
Develop, implement and update as

necessary the post-contract BEP,
A I C C R
which all project team members need
to agree to and use
Agree and implement the data

structure and maintenance standards C I C C C C R C
for the information models
Acquire and update as necessary the

post-contract BEP to include I I I I R I
construction responsibilities
Develop and implement the

information delivery plan, sufficient to
C I I R I
ensure all deliverables are accounted
for
Acquire and update the MPDT

indicating model progression in
respect of work packages including R
Level Of Definition with dates of
delivery
Develop and implement the BIM

A R C
implementation programme
Develop and implement the

I C R
information exchange protocol
BIM guidance and monitoring of the

I C I R
project team
Information Manager
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
Responsible for ensuring that all sub-

contracted organisations (design or
C R R R
construct) meet the requirements set
forth in the EIR
Provide any existing information

including historical data and existing R R I
conditions models.
Geometry
Create a site set-up model with

coordinated, measurements and
I R I
bearings to be used disseminated to
all design team members
Provide a virtual model according to

the Levels of Development, the MPDT R R R R
and the non-geometric requirements
Share information models for

R R R R
coordination
Implement the BEP within the

R R R R R R R R R R
organisation
Full coordination of the design and

C R
design team
Provide energy analysis model(s) for

R R
evaluation by the project team
Provide structural analysis model(s)

R
for evaluation by the project team
Create clash detection reports of the

R
federated models
Ensure the implementation of BIM

acknowledges Facilities Management
I I I R C C
(FM) and operation and maintenance
deliverables
Incorporate sub-contract (design and

R R R R
construct) models
Information Manager
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
Ensure that all drawings are derived

I R R R R
from the information models
Export and publish files according to

I R R R R
file data exchange schedule
Data
Specify data requirements including

the purpose for the information A I C C C R I C C C C
required and the timing of its delivery
Provide data about facility in both its

spatial and physical aspects according I R R R I R
to the COBie requirements of the EIR
Provide data specific to a particular

system or component in line with R
individual scope of works C
Delegate aspect of the EIR

I R R R R
downwards to the next tier
Create, acquire and store required

R R R R R R R
information
Review and approve the data

I R R C R R R
deliverable prior to submission
Construction management
Provide 4D construction phasing I R C
Provide 4D construction sequencing I R I C
Provide 4D logistics simulations

I R I R
including crane strategy
Update all 4D simulated models to

reflect current project conditions and I R I
to illustrated progress C
Report on residual risks within the

I I C C I C R C
model space and share via the CDE
Compile a digital health and safety file

I C R R C R I C R
as per the instructions in 3.9
Information Manager
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
Quality assurance and control
Adhere to the QA/QC procedure

R R R R
contained within the EIR
Ensure all dataset requirements are

completed in full according to the
C R R I R R
Level Of Definition stage for use in
CAFM
Report on changes to budget, cost

A R R
and design
Audit and coordinate virtual models,

including full intermittent clash
I C R C C
detection according to the BIM
programme
Report on general model quality in

terms of geometry, materiality and I R
metadata
Report on adherence to the project

BEP with regards to model Level Of
I I R
Definition, model completeness and
BIM standards compliancy
Report on functionality of the model

for 4D and 5D use by other I C R C
consultants
Review of received data against the

R R R R R
EIR data requirements
Support the Lead Designer by

undertaking third party 3D
coordination and clash detection I C R C C
processes to assist design
coordination reviews
Meetings
Make use of information models

during design team and the R R
Employers team meetings
Hold BIM workgroup meetings C C* C R I I
Information Manager
Facilities manager
Project Manager
Main Contractor
Lead Designer
Cost manager
Design team
BIM Leader
Employer
CDM-C
Responsibilities
Hold key work stage BIM steer

C C C C C R R C C
meetings
Hold lessons learned meeting

I R R R R R R R R R R
following completion of phases
Reporting and Governance
Provide monthly status reports of BIM

I C R R R R R R C C R
development using project pro-forma
Provide monthly procurement model

highlighting work packages which I I R C
have been let and/or procured
Provide monthly model showing actual

I I R C
programme progress against planned
Report on supply chain performance

I I R C
during construction
APPENDIX E CDE folder structure
W
CMA - Organisation
MEP - Organisation
PMA - Organisation
FMA - Organisation
ARC - Organisation
Write
CSE - Organisation
LAR - Organisation
LEA - Organisation
INF - Organisation
R Read
OrganisationL
N
Organisation
No access
Sub CON
Client
CON
CDE Structure
Organisation
Standards W R R R R W W R R R R R
Cost plans R R R R R R W W R R N R
Programme R R R R R R W R W R R R
Monthly PM report R N N N N N W N W N N R
Clash reports - R W R R R W W R R R R R
Reports
COBie drops R W R R R R W R R W R R
TBC R W
Meetings W W W W W W W W W W W W
AR
WIP R W R R R R W N N N N N
Shared R W R R R R W R R R R R
Models
Published W R R R R R W R R R R R
Archived R N N N N R W N N N N N
WIP R W R R R R W N N N N N
Shared R W R R R R W R R R R R
Drawings
Published R W R R R R W R R R R R
Clash reports - R W N N N R W N N N N N
Documents RFIs R W R R R R W R R R R R
Other documents R W R R R R W R R R R R
ME
WIP R R W R R R W N N N N N
Shared R R W R R R W R R R R R
Models
WIP R R W R R R W N N N N N
Shared R R W R R R W R R R R R
Drawings
Published R R W R R R W R R R R R
Clash reports - R N W N N R W N N N N N
Documents RFIs R R W R R R W R R R R R
Other documents R R W R R R W R R R R R
CSE
WIP R R R W R R W N N N N N
Shared R R R W R R W R R R R R
Models
WIP R R R W R R W N N N N N
Shared R R R W R R W R R R R R
Drawings
Published R R R W R R W R R R R R
Clash reports - individual R N N W N R W N N N N N
Documents RFIs R R R W R R W R R R R R
Other documents R R R W R R W R R R R R
LAR
WIP R R R R W R W N N N N N
Shared R R R R W R W R R R R R
Models
WIP R R R R W R W N N N N N
Shared R R R R W R W R R R R R
Drawings
Published R R R R W R W R R R R R
Clash reports - individual R N N N W R W N N N N N
Documents RFIs R R R R W R W R R R R R
Other documents R R R R W R W R R R R R
CON
WIP R N N N N R W N N W N N
Shared R R R R R R W R R W R R
Models Published R R R R R R W R R R R R
As-built R R R R R R W R R W R R
WIP R N N N N R W N N W N N
Shared R R R R R R W R R W R R
Drawings
Published R R R R R R W R R R R R
Clash reports - individual R N N N W R W N N N R N
Clash reports - CON and R N N N W R W N N N R N
Documents
RFIs R R R R W R W R R R R R
Other documents R R R R W R W R R R R R
APPENDIX F Information exchange schedule
The following software choices are capable of delivering required BIM uses. Changes to any
information in this schedule must be explicitly agreed by the design team and BIM Leader.
Where project team members are required to upgrade software versions, it is advised that this is
done across the team in unison to provide a consistent understanding of skills and requirements.
Consultants should consider a joint approach to undertaking software training where possible.
BIM Use Consultant Software and Native Exchange Frequency

version format format
3D design ARC Insert Software & Insert format Insert Insert

coordination Version Exchange frequency
INT
format
LAR
MEP
CSE
CON
Asset management FMA
Assurance and data INF

validation
Construction ARC
sequencing and
CON
simulation
Construction system CON

design
Cost estimation CON
Cost management CMA
Data classification ARC

INT
LAR
MEP
CSE
CON
Design (BIM) ARC

authoring
INT
LAR
MEP
CSE
CON
Design reviews ARC

INT
LAR
CON
Digital fabrication CON
Drawing generation ARC

INT
LAR
MEP
CSE
Energy analysis MEP

(engineering
analysis)
Existing conditions CSE

modelling
Field management CON

tracking
Health and safety CON
Lighting analysis ARC
Pedestrian ARC
simulation
Planned FMA
maintenance
Possessions and CON

permit to work
Procurement CON
analysis
Record modelling CON
Space management FMA

and tracking
Spatial planning and ARC

optimisation
Structural analysis CSE
Visualisation and ARC

communication
ARC = Architect CSE = Civil & Structural INT = Interior Designer LAR = Landscape
Engineer Architect
MEP = Mechanical CON = Main Contractor FMA = Facilities Manager

& Electrical
Engineer
APPENDIX G Meetings terms of reference
Meeting title BIM workgroup meeting
Description Meeting to track the progress of BIM implementation on the project in the
context of this document. The BIM workgroup meeting should be used as a
mechanism to identify any forthcoming challenges and agree a proactive
solution.
Participants Client, BIM Leader, Information Manager, Project Manager, Cost Manager,
Lead BIM Coordinator, BIM Coordinators
Frequency TBC
Meeting title BIM workshop
Description At key project stages, the project team should evaluate their performance
and hold a workshop to develop and improve collaboration and working
methodology.
Workshops should also be used to re-evaluate working methodology to
respond to advances in (and new) technology which can be utilised to the
benefit of the project.
The outputs from these workshops may be used to inform any alterations
or developments of the Building Information Modelling Execution Plan
(BEP) in later stages of the project.
Participants Client, BIM Leader, BIM Information Manager, Project Manager, Cost
Manager, Lead BIM Coordinator, BIM Coordinators
Frequency TBC
APPENDIX H Quality control procedures
The table below defines validation checks to be carried out by the project team. Additional third
party model checks may be required at key increments. In this instance, the BIM Leader, Client
and project team will agree a strategy to obtain an impartial model status and validation report.
Checks Definition Responsibility Software Frequency
Visual Ensure there are no All design Native

unintended model consultants
components and the design
intent has been followed
Intersection Detect problems in the All design Native and

and Clash model where two building consultants other
Detection components are clashing TBC
including soft and hard
Standards Ensure that the project BIM All design Native

Check Standard have been consultants
followed (fonts, dimensions,
line styles, levels / layers,
etc)
Model Data Process used to ensure that All design Native

Check the project data set has no consultants
undefined, incorrectly
defined or duplicated
elements, including object
classification and the
reporting process on non-
compliant elements and
corrective action plans
Automated BIM Automated process carried All design Solibri

Check out by software, consultants
implementing specific rule
Other TBC
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.

3 Uoc Bimexecutionplan v1.1.1

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

3 Uoc Bimexecutionplan v1.1.1

Uploaded by

Copyright:

Available Formats

Building Information Modelling (BIM)

Insert Project Name

Rev Originator BIM Approved Date

1.0 C Hinton BIM Strategy Group 26/06/15

1.1 C Hinton Amended MPDT 03/09/15

1.1.1 C Hinton EM Address Update 03/02/16

Controlled Document Distribution

This revision of the BEP is to be formally issued to:

Requirements and processes

Methods and protocols

Relevant business processes

Supporting software requirements

No part of this document should be construed as preventing the Consultants, Specialist

2.2 Project execution through BIM

2.3 Applicable standards

In order to establish a consistent approach to collaboration, University of Cambridge

BIM Execution Plan (BEP) M M M M M M M

Table 1: Applicable standards

3 Project overview and aims

Client University of Cambridge

Project name Insert Project Name

Short project description

Plan of works RIBA Plan of Works 2013

3.2 Project BIM objectives

3.2.1 Success factors

3.2.2 Documents and mechanisms

Project processes and contractual mechanisms are as follows:

Agreed Employers Information Requirements (EIR).

3.3 Key Performance Indicators (KPIs)

4 BIM requirements and processes

4.2 Level of Definition

These requirements are to be understood by all consultants and incorporated in the

4.2.2 Geometric information requirements Model Production Delivery Table

In future work stages, any amendment to Level of Definition requirements must be

4.2.3 Non-geometric information requirements

The following is defined in Appendix A and Appendix B of the EIR.

COBie requirements (Matrix)

Basic parameter requirements

Client specific requirements for asset data

It is important that all stakeholders familiarise themselves with the parameter

5.2 BIM implementation programme

Key data drops

BIM data exchange trial

5.3 Project milestones

Insert project milestone 1 00/00/0000

Insert project milestone 2 00/00/0000

Insert project milestone 3 00/00/0000

6 Project team, stakeholders and responsibilities

A full Project Directory is included in Appendix C.

6.1.1 BIM capability

Consultant teams have been assessed as to their competency to work utilising a

6.2 Roles and responsibilities

Notwithstanding the specific responsibilities contained in Appendix D, each

Manage BIM uses assigned to their organisation

Support their organisation in the use of BIM tools

Create discipline specific BIM content

Coordinate discipline specific clash detection and resolution activities

Export their own organisations model for inter-disciplinary clash detection

Coordinate BIM training as required

7 Deliverables and outputs

The employer requires information to fulfil the following purposes:

A full registration of assets is required to support accurate auditing and reporting.

7.2 Two-dimensional outputs