building information modelling (bim) execution plan · pdf filebuilding information modelling...
TRANSCRIPT
University of Cambridge Estate Management Greenwich House Madingley Road
Cambridge CB3 0TX United Kingdom
Insert Project Name
Building Information Modelling (BIM) Execution Plan
For University of Cambridge
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
Contents1 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 manager’s 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 team’s 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 Employer’s Information Requirements. This in addition to the BEP and other industry standards outlined below.
M = Mandatory R = Recommended Application
Standards
Gui
danc
e
Col
labo
ratio
n
Pro
ject
sta
ges
File
nam
ing
Obj
ect n
amin
g
Dra
win
g
Cla
ssifi
catio
n
LOD
CD
E
Cos
ting
CO
Bie
Con
tract
s
Indu
stry
Additional or superseding standards
Bes
poke
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
Success factors 3.2.1
At the highest level, general project success factors provide the basis for BIM process development and have been described in the Employer’s Information Requirements. Any additional success factors will be released within further amendments of this document.
Documents and mechanisms 3.2.2
Project processes and contractual mechanisms are as follows:
Agreed Employer’s 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
Summary 4.2.1
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.
Geometric information requirements – Model Production Delivery Table 4.2.2
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.
Non-geometric information requirements 4.2.3
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
Insert project milestone 2 00/00/0000
Insert project milestone 3 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.
BIM capability 6.1.1
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 organisation’s 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 Engineer Insert Software x & Version
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
Responsibility 8.2.1
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.
User privileges 8.2.2
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 Client’s representative. Access privileges are detailed in Appendix E.
Structure / Purpose 8.2.3
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
Data exchange protocol 8.2.4
Methodology 8.2.4.1
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.
Schedule 8.2.4.2
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.
Trial 8.2.4.3
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, Northing’s and Easting’s. All team members are requested to adopt coordinate settings, project datums and grids from the lead designer’s 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.
making the difference 20
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.
making the difference 21
11 Abbreviations & Glossary of Terms
11.1 Abbreviations
BEP
BIM
BWM
CDE
EIR
IFC
BIM Execution Plan
Building Information Modelling
BIM workgroup meeting
Common Data Environment
Employer Information Requirement
Industry Foundation Classes
LOD
LOI
MPDT
WIP
Level Of Detail
Level Of Information
Model Production Delivery Table
Work In Progress
making the difference 22
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 information modelling execution plan (BEP)
Plan prepared by the suppliers, facilitated by the Client or the Client’s BIM representative to explain how the information modelling aspects of a project will be carried out
Building information modelling (BIM)
Process of designing, constructing or operating a building or infrastructure asset using electronic object-oriented 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 Services
Multi-disciplinary scope of services published by the Construction Industry Council (CIC) for use by members of the project team on major projects
COBie (Construction Operation Building information exchange)
Structured facility information for the commissioning, operation and maintenance of a project often in a neutral spread sheet format that will be used to supply data to the client or operator to populate decision-making tools, facilities management and asset management systems
Common data environment (CDE)
Single source of information for any given project, used to collect, manage and disseminate all relevant approved project documents for multi-disciplinary teams in a managed process. This is commonly a cloud based 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)
making the difference 23
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
Employer’s information requirements (EIR)
Pre-tender document setting out the information to be delivered, and the standards and processes to be adopted by the supplier as part of the project delivery process
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 information delivery plan (MIDP)
Primary plan for when project information is to be prepared, by whom and using what protocols and procedures, incorporating all relevant task information delivery plans
Pre-contract BEP
The pre-contract BEP is to demonstrate the supplier’s proposed approach, capability, capacity and competence to meet the EIR. It is utilised prior to the appointment of any stakeholder.
Post-contract BEP
The post-contract BEP is the document defining standard 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 implementation plan (PIP)
Statement relating to the suppliers’ IT and human resources capability to deliver the EIR
Standard method and procedure (SMP)
Set of standard methods and procedures covering the way information is named, expressed and referenced
making the difference 24
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
making the difference 25
APPENDIX A Model Production Delivery Table (MPDT)
Originator Reference
Architecture ARC
Structural CSE
MEP MEP
Contractor CON
Eg. Landscaping Eg.LAR
LOD LOI Resp Party LOD LOI Resp Party LOD LOI Resp Party LOD LOI Resp Party LOD LOI Resp Party LOD LOI Resp Party LOD Resp Party
1 Substructure 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
1 Frame 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
2 Upperfloors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
3 Roof 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
4 Stairs and ramps 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
5 External walls 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
6 Windows and external doors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
7 Internal walls and partitions 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
8 Internal doors 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
1 Wall finishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
2 Floor finishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
3 Ceiling finishes 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 5 4 CON 5 5 CON TBC FMA
1 Fittings, furnishings and equipment 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
1 Sanitary installations 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
2 Services equipment 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
3 Disposal installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
4 Water installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
5 Heat source 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
6 Space heating and air conditioning 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
7 Ventilation 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
8 Electrical installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
9 Fuel installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
10 Lift and conveyor installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
11 Fire and lightning protection 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
12 Communication, security and control systems 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
13 Specialist installations 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
14 Builder’s work in connection with services NA NA NA NA 2 2 MEP 3 3 MEP 3 3 CON 5 5 CON TBC FMA
1 Site preparation works NA NA NA NA NA NA 4 4 ARC 4 4 CON NA NA NA NA
2 Roads, paths, pavings and surfacings 1 1 ARC 2 2 ARC 3 3 ARC 4 4 ARC 4 4 CON 5 5 CON TBC FMA
3 Soft landscaping, planting and irrigation systems 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
4 Fencing, railings and walls 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
5 External fixtures 1 1 LAR 2 2 LAR 3 3 LAR 4 4 LAR 4 4 CON 5 5 CON TBC FMA
6 External drainage 1 1 CSE 2 2 CSE 3 3 CSE 4 4 CSE 4 4 CON 5 5 CON TBC FMA
7 External services 1 1 MEP 2 2 MEP 3 3 MEP 4 4 MEP 4 4 CON 5 5 CON TBC FMA
8 Builder’s work in connection with external services NA NA NA NA 2 2 MEP 3 3 MEP 3 3 CON 5 5 CON TBC FMA
8 External works
5 Services
4 Fittings, furnishings and equipment
3 Internal finishes
2 Superstructure
LOD & Model Production Delivery Table
Elements, Materials & Components (NRM1)
RIBA 2013 (CIC) Workstage
1 Substructure
University of CambridgeThe Model Production and Delivery Table (MPDT) is a key document as it both allocates responsibility for preparation of the Models and identifies the Level of Definition that Models need to meet at the
project stages or data drops stated in the table.
Model originator and responsible parties, must be named.
Models should be added as required and agreed by the project PIM.
Cost data should be produced at NRM3 for later stages (levels 1 & 2 shown below for clarity).
LOD and LOI are deliverables for each stage. (For LOD and LOI definition, see University of Cambridge EIR, Appendix E.)
Core Models
Additional Models
7
Preparation & Brief
Consult Implementation & Delivery Asset Operation
In Use
1 2 3 4 5 6
Concept Developed Design Technical Design Construction Handover & Closeout
University of CambridgeInsert Project NameModel Production Delivery Table
making the difference 26
APPENDIX B Drop Schedule
Additional discipline models and the parties responsible are to be added to all required data drops.
Data drop
Date Project stage
File submitted Format Responsible party
1 Dd/mm/yy
1 COBie drop .XLS Architect name
Architectural Model .IFC Architect name
2 Dd/mm/yy
2 COBie drop .XLS All design consultants
Architectural Model .IFC Architect name
Structural & Structural Model
.IFC Civil & Structural Engineer
MEP Model .IFC MEP Engineer name
3 Dd/mm/yy
3 COBie drop .XLS All design consultants
Architectural Model .IFC Architect name
Structural & Structural Model
.IFC Civil & Structural Engineer
MEP Model .IFC MEP Engineer name
4 Dd/mm/yy
4 COBie drop .XLS All design consultants
Architectural Model .IFC Architect name
Structural & Structural Model
.IFC Civil & Structural Engineer
MEP Model .IFC MEP Engineer name
5 Dd/mm/yy
5 COBie drop .XLS Contractor name
Project Information Model
.IFC Contractor name
Specialist designer model
.IFC Specialist name
6 Dd/mm 6 COBie drop .XLS Contractor name
making the difference 27
Data drop
Date Project stage
File submitted Format Responsible party
/yy Asset Information Model
.IFC Contractor name
7+ Dd/mm/yy
7 COBie drop .XLS Facilities Manager
Asset Information Model
.IFC Facilities Manager
making the difference 28
APPENDIX C Project directory
Insert ALL details of ALL roles. Ensure details are kept up to date throughout the project life cycle.
Role Company Contact Address Mobile Phone No.
Office Phone No.
Client Company Name
Contact name Address Phone Phone Email
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
making the difference 29
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
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
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 information from/to the CDE R R R R R R R R R
Resources
Appoint consultants, including Information Manager R C
Ensure that the necessary software and hardware are in place within the organisation to support efficient delivery of the project
R R R R R R R R R R
R
Assess all sub-contracted organisations (design or construct) according to the BIM assessment criteria contained in the Capability Assessment
I I R R R R
R R
Report any emerging skill gaps within the team I R R R
making the difference 30
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
Provide guidance to assist in procuring the right type of training from credible industry professionals
I I I I I R I I I I I
Co-ordinate training for your own organisation R R R R R R R R R R R
Project strategy
Establish BIM requirements for the project, long term C I R
Develop, implement and update as necessary the post-contract BEP, which all project team members need to agree to and use
A I C C R
Agree and implement the data structure and maintenance standards for the information models
C I C C C C R C
Acquire and update as necessary the post-contract BEP to include construction responsibilities
I I I I R I
Develop and implement the information delivery plan, sufficient to ensure all deliverables are accounted for
C I I R I
Acquire and update the MPDT indicating model progression in respect of work packages including Level Of Definition with dates of delivery
R
Develop and implement the BIM implementation programme A R C
Develop and implement the information exchange protocol I C R
BIM guidance and monitoring of the project team I C I R
making the difference 31
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
Responsible for ensuring that all sub-contracted organisations (design or construct) meet the requirements set forth in the EIR
C R R R
Provide any existing information including historical data and existing conditions models.
R R I
Geometry
Create a site set-up model with coordinated, measurements and bearings to be used disseminated to all design team members
I R I
Provide a virtual model according to the Levels of Development, the MPDT and the non-geometric requirements
R R R R
Share information models for coordination R R R R
Implement the BEP within the organisation R R R R R R R R R R
Full coordination of the design and design team C R
Provide energy analysis model(s) for evaluation by the project team R R
Provide structural analysis model(s) for evaluation by the project team R
Create clash detection reports of the federated models R
Ensure the implementation of BIM acknowledges Facilities Management (FM) and operation and maintenance deliverables
I I I R C C
Incorporate sub-contract (design and construct) models R R R R
making the difference 32
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
Ensure that all drawings are derived from the information models I R R R R
Export and publish files according to file data exchange schedule I R R R R
Data
Specify data requirements including the purpose for the information required and the timing of its delivery
A I C C C R I C C C C
Provide data about facility in both its spatial and physical aspects according to the COBie requirements of the EIR
I R R
R I R
Provide data specific to a particular system or component in line with individual scope of works
R
C
Delegate aspect of the EIR downwards to the next tier I R R R R
Create, acquire and store required information R R R R R R R
Review and approve the data deliverable prior to submission I R R C R R R
Construction management
Provide 4D construction phasing I R C
Provide 4D construction sequencing I R I C
Provide 4D logistics simulations including crane strategy I R I R
Update all 4D simulated models to reflect current project conditions and to illustrated progress
I R I
C
Report on residual risks within the model space and share via the CDE I I C C I C R C
Compile a digital health and safety file as per the instructions in 3.9 I C R R C R I C R
making the difference 33
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
Quality assurance and control
Adhere to the QA/QC procedure contained within the EIR R R R R
Ensure all dataset requirements are completed in full according to the Level Of Definition stage for use in CAFM
C R R I R R
Report on changes to budget, cost and design A R R
Audit and coordinate virtual models, including full intermittent clash detection according to the BIM programme
I C R C C
Report on general model quality in terms of geometry, materiality and metadata
I R
Report on adherence to the project BEP with regards to model Level Of Definition, model completeness and BIM standards compliancy
I I R
Report on functionality of the model for 4D and 5D use by other consultants
I C R C
Review of received data against the EIR data requirements R R R R R
Support the Lead Designer by undertaking third party 3D coordination and clash detection processes to assist design coordination reviews
I C R C C
Meetings
Make use of information models during design team and the Employers team meetings
R R
Hold BIM workgroup meetings C C* C R I I
making the difference 34
Responsibilities
Em
ploy
er
Pro
ject
Man
ager
Cos
t man
ager
Des
ign
team
Lead
Des
igne
r
BIM
Lea
der
Info
rmat
ion
Man
ager
Mai
n C
ontra
ctor
CD
M-C
Faci
litie
s m
anag
er
Spe
cial
ist C
ontra
ctor
Hold key work stage BIM steer meetings C C C C C R R C C
Hold lessons learned meeting following completion of phases I R R R R R R R R R R
Reporting and Governance
Provide monthly status reports of BIM development using project pro-forma I C R R R R R R C C R
Provide monthly procurement model highlighting work packages which have been let and/or procured
I I R C
Provide monthly model showing actual programme progress against planned I I R C
Report on supply chain performance during construction I I R C
making the difference 35
APPENDIX E CDE folder structure
W Write
Clie
nt
AR
C -
Org
anis
atio
n
ME
P -
Org
anis
atio
n
CS
E -
Org
anis
atio
n
LAR
- O
rgan
isat
ion
LEA
- O
rgan
isat
ion
INF
- Org
anis
atio
n
CM
A -
Org
anis
atio
n
PM
A -
Org
anis
atio
n C
ON
O
rgan
isat
ionL
S
ubC
ON
O
rgan
isat
ion
FMA
- O
rgan
isat
ion
R Read N No access
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
Reports
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 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 WAR
Models
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 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
Drawings
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 Published R W R R R R W R R R R R Archived R N N N N R W N N N N N
Documents Clash reports - R W N N N R W N N N N N 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
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 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
Drawings
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 Published R R W R R R W R R R R R Archived R N N N N R W N N N N N
Documents Clash reports - R N W N N R W N N N N N 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
making the difference 36
CSE
Models
WIP R R R W R R W N N N N NShared R R R W R R W R R R R RPublished W R R R R R W R R R R RArchived R N N N N R W N N N N N
Drawings
WIP R R R W R R W N N N N NShared R R R W R R W R R R R RPublished R R R W R R W R R R R RArchived R N N N N R W N N N N N
Documents Clash reports - individual R N N W N R W N N N N NRFIs R R R W R R W R R R R ROther documents R R R W R R W R R R R R
LAR
Models
WIP R R R R W R W N N N N NShared R R R R W R W R R R R RPublished W R R R R R W R R R R RArchived R N N N N R W N N N N N
Drawings
WIP R R R R W R W N N N N NShared R R R R W R W R R R R RPublished R R R R W R W R R R R RArchived R N N N N R W N N N N N
Documents Clash reports - individual R N N N W R W N N N N NRFIs R R R R W R W R R R R ROther documents R R R R W R W R R R R R
CON
Models
WIP R N N N N R W N N W N NShared R R R R R R W R R W R RPublished R R R R R R W R R R R RArchived R N N N N R W N N N N NAs-built R R R R R R W R R W R R
Drawings
WIP R N N N N R W N N W N NShared R R R R R R W R R W R RPublished R R R R R R W R R R R RArchived R N N N N R W N N N N N
Documents
Clash reports - individual R N N N W R W N N N R NClash reports - CON and R N N N W R W N N N R NRFIs R R R R W R W R R R R ROther documents R R R R W R W R R R R R
making the difference 37
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 version
Native format
Exchange format
Frequency
3D design coordination
ARC
INT
LAR
MEP
CSE
CON
Insert Software & Version
Insert format Insert Exchange format
Insert frequency
Asset management FMA
Assurance and data validation
INF
Construction sequencing and simulation
ARC
CON
Construction system design
CON
Cost estimation CON
Cost management CMA
Data classification ARC
INT
LAR
MEP
CSE
CON
Design (BIM) authoring
ARC
INT
LAR
MEP
CSE
CON
making the difference 38
BIM Use Consultant Software and version
Native format
Exchange format
Frequency
Design reviews ARC
INT
LAR
CON
Digital fabrication CON
Drawing generation ARC
INT
LAR
MEP
CSE
Energy analysis (engineering analysis)
MEP
Existing conditions modelling
CSE
Field management tracking
CON
Health and safety CON
Lighting analysis ARC
Pedestrian simulation
ARC
Planned maintenance
FMA
Possessions and permit to work
CON
Procurement analysis
CON
Record modelling CON
Space management and tracking
FMA
Spatial planning and optimisation
ARC
Structural analysis CSE
making the difference 39
BIM Use Consultant Software and version
Native format
Exchange format
Frequency
Visualisation and communication
ARC
ARC = Architect CSE = Civil & Structural Engineer
INT = Interior Designer LAR = Landscape Architect
MEP = Mechanical & Electrical Engineer
CON = Main Contractor FMA = Facilities Manager
making the difference 40
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
making the difference 41
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 unintended model components and the design intent has been followed
All design consultants
Native
Intersection and Clash Detection
Detect problems in the model where two building components are clashing including soft and hard
All design consultants
Native and other – TBC
Standards Check
Ensure that the project BIM Standard have been followed (fonts, dimensions, line styles, levels / layers, etc)
All design consultants
Native
Model Data Check
Process used to ensure that the project data set has no undefined, incorrectly defined or duplicated elements, including object classification and the reporting process on non-compliant elements and corrective action plans
All design consultants
Native
Automated BIM Check
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.
All design consultants
Other TBC
Solibri