Information Requirements for Building Information ...

Document control

EMPLOYER’S INFORMATION REQUIREMENTS (EIR)

The Shared Estates Service (SES) Cluster: Project Control Framework

STD/BIM/P005 (G0200) Information Requirements for Building Information Modelling

& Data-Sets

Version v1.4 March 2016

MoJ / SES Cluster Employers Information Requirements (EIR) STD/BIM/P005

MoJ Estate Directorate, Technical Standards of 31

Version

No.

Date of first

issue

Purpose of issue Name Amendment summary

v1.0 08 Dec 2015 Draft for comment Voegt, N MW First draft

v1.1 15 Jan 2016 Draft for comment Voegt, N;

Munkley, J

MW additional content and feedback comments incorporated

v1.2 31 Jan 2016 For Information Watchorn,

M; Voegt, N

Reordered to align with MoJ Maturity KPIs, KPI cross references added, new content and formatting for

BIM2AIM SIG release as part of the MoJ OIR, AIR, EIR suite of documents.

V1.3 16 Mar 2016 Sharing Watchorn, M Amendments to naming convention section, and other minor changes.

V1.4 28 Mar 2016 Sharing Watchorn, M References to other standards amended in line with OIR-AIR-EIR suite changes



CONTENTS

1 BIM PROCUREMENT AND EMPLOYER ENGAGEMENT 5

1.0 Document Purpose 5

1.1 Document Structure 6

1.2 Responding to this document 7

1.3 BIM Vision and Objectives 8

2 BIM DELIVERY REQUIREMENTS 10

2.0 Information Exchanges and Project Deliverables 10

2.1 Information Delivery Plan 10

2.2 Level of Definition, Detail and Information 11

2.3 Health & Safety and Construction Design Management 11

3 MANAGEMENT 11

3.1 Applicable Standards 12

3.2 Information Management Roles and Responsibilities 12

3.3 Collaborative Working 13

3.4 Discipline Based Model Authoring and Data Segregation 14

3.5 Security 15

3.6 Coordination and Clash Detection 17

3.7 Compliance Plan 18

3.8 Delivery Strategy for Asset Information 18

3.9 Template Provision (MIDP and Project Plan) 19

3.10 Training 20



4 TECHNICAL 21

4.0 Software Platforms 21

4.1 System Performance 21

4.2 Data Exchange Format 22

4.3 Coordinates 22

5 COMMERCIAL 23

5.0 BIM Execution Plan 23

5.1 BIM Specific Competence Requirements 23

5.2 Confirmation of BIM Toolset 23

5.3 Details of BIM Workload and Resourcing 24

5.4 Principal Supply Chain 24



1 BIM PROCUREMENT AND EMPLOYER ENGAGEMENT

1.0 Document Purpose

1.0.1 This document confirms the Employer’s Information Requirements (EIR) as a sub-set of the Employer’s Requirements or equivalent contract

documentation and introduces information requirements, reasons and purpose to the Project Team or Supplier, along with software and commercial

particulars that need to be addressed to support the implementation of Building Information Modelling (BIM) and Government Soft Landings (GSL) for The

Ministry of Justice.

1.0.2 The EIR is an important element of Project BIM Implementation and is used to set out clearly to the Project Team or Supplier what information (models,

documents and data) is required generally and at each project stage via a stage based Information Delivery Plan (IDP).

1.0.3 This document is part of the MoJ Technical Standards and forms a part of a suite of data standards and specifications for the use of BIM and to be read

in conjunction with those standards.

1.0.4 For a number of MoJ BIM projects STB/BIM/P006 BIM Maturity KPI System will apply from tender stage onwards. Within this document the KPI references

have been highlighted [in square brackets] to assist with compliance with those measures in the initial bidder’s responses to tender and BIM execution

planning and during the duration of the project. If the EIR-IDP shows the delivery reference ‘G0600’, then the KPI system will apply to the project.

1.0.5 Nothing in this document is intended to relieve the Constructor or its Specialists of responsibility to comply with The Ministry of Justice standards

including those relating to handover procedure.

1.0.6 The final details for consultant and contractor deliverables are to be included in the agreed project BIM Execution Plan (BEP), and this will inform the

production and delivery of a Project Information Model and data-set which meets the requirements of The Ministry of Justice. The Project Information

Model and data-set is the end product to be delivered by the supply chain in addition to the physical asset itself.

1.0.7 Any references to the Employer or The Ministry of Justice within this document, shall be taken to mean the Client as defined in PPC2000 and NEC3

Family of Standard Partnership Contracts.



1.1 Document Structure

1.1.1 The Ministry of Justice define their Information Requirements using the following:

1.1.2 The Employer’s Information Requirements and IDP relate to all information deliverables (models, documents and data) including traditional project

documents, surveys, reports and appraisals and are included in the IDP where required by the Employer.

1.1.3 The IDP schedules required information deliverables across the RIBA Plan of Work 2013, to enable the Employer to answer the project stage Plain

Language Questions (PLQ), make project gateway decisions and to engage with the other project stakeholders.

1.1.4 The IDP shall be drafted by the Employer, and the requirements to be adopted by the Project Team or Supplier as part of their BIM Execution Plan

(BEP). The development of this information throughout the project lifecycle is known as the Digital Plan of Works, and will form the basis of the Master

Information Delivery Plan and Task Information Delivery Plan.

1.1.5 Information referenced (or the inadvertent omission of information delivery references) within this document or the AIR-IDP STD/BIM/P004 schedule do

not obviate the roles and responsibilities within the project team to achieve compliance with the appropriate statutory regulations. If there are any gaps

in the set of requirement, please bring them to the attention of the project sponsor.

Employer's Information Requirements (EIR) STD/BIM/P005

This describes the management standards and collaborative processes

needed to produce information required by The Ministry of Justice, and

includes:

Responsibilities

Requirements and processes

Methods and protocols

Relevant business processes

Supporting software requirements

Information Delivery Plan (AIR-IDP) STD/BIM/P004 The IDP details the tasks and deliverables responding to The Ministry of Justice's Plain Language Questions for each work stage, as well as associated roles and responsibilities. This will include:

Tasks and Information Deliverables

Level of Definition for each deliverable, including;

o Level of Detail (LOD)

o Level of Information (LOI)

The intended role or appointed supplier for the information deliverable



1.2 Responding to this document

1.2.1 An EIR or EIR/IDP combination should be responded to using the MoJ’s template BIM Execution Plan (BEP) as provided at STD/BIMP005.1. The BEP

sections will constitute a direct response to the EIR, and reference numbers for each section of the response should correspond those of the EIR.

1.2.2 If the project is subject to the STD/BIM/P006 BIM Maturity KPI System then the BEP (Pre and Post Contract) will need to consider and respond to the

following eight cross-UK.Gov headings as a minimum within that system and where appropriate the underlying BIM maturity KPI measures:

1.2.3 The BEP (Pre and Post Contract) will need to include the following content as a minimum:

1.2.3.1 Project Information Model delivery strategy [KPI 2.10]

1.2.3.2 A response to each section of the EIR, as indicated by BEP guidance notes, shown in the dashed highlighted boxes (as above) [KPI 2.3].

1.2.3.3 Specific response to the IDP, confirming ability to deliver information requirements, in the requested format, and to the correct LOI [KPI2.13]

1.2.3.4 Project goals for collaboration and information modelling and management [KPI5.1]

1.2.3.5 Major project milestones consistent with the construction programme and IDP [KPI 2.2]

1.2.3.6 Comments where deliverables are over or under specified, or impractical to deliver with alternative delivery proposals.

1.2.4 A compliant BEP in support of a project tender will demonstrate how the requirements of each section of this EIR and IDP will be met. The BEP and its

response to the EIR will form part of tender scoring system using the MoJ BIM Maturity KPIs (see STD/BIM/P006 BIM Maturity KPI System) and these

measures will be consistently used throughout the life of the project through to Stage 07 handover and in use.

1.0 BIM PROCUREMENT / EMPLOYER ENGAGEMENT

2.0 BIM DELIVERY

3.0 DATA, VERIFICATION AND VALIDATION

4.0 COLLABORATIVE WORKING

5.0 VISUALISATION / STAKEHOLDER ENGAGEMENT

6.0 DISCIPLINE BASED MODEL AUTHORING

7.0 CONSTRUCTION

8.0 MODEL BASED ESTIMATING AND CHANGE MANAGEMENT



1.3 BIM Vision and Objectives

1.3.1 BIM as a concept is ‘the adoption of information rich Building Information Modelling (BIM) technologies, process and collaborative behaviours that will

unlock new more efficient ways of working at all stages of the project life-cycle’. The Government Construction Strategy has mandated the

implementation of BIM to Level 2 maturity for Government Departments by 2016. UK BIM Task Group describe two of the key features of that

challenging mandate:

1.3.1.1 All projects by April 2016 are to be commissioned with an bespoke EIR (Employers Information Requirements) instruction and

1.3.1.2 By October 2016 all Government Departments are to have the ability to validate the structured data received in response to the EIR.

1.3.2 Delivery partners of The Ministry of Justice shall fully utilise the Employer’s suite of BIM policy documents, data templates, KPI system and graphical

components in the MoJ BIM Component library developed for the purpose of building a model or data-set of the asset(s) the project seeks to deliver. A

Client Sketch Model may also be provided during the early stages of a project if the requirements are already configured in a massing or more detailed

model format. The Ministry of Justice and Supply Chain Partners will retain a high level of transparency on the geometry / scale of the design and

stages of progress delivering greater cost certainty and methods of communication as a result.

1.3.3 The shared objective is to use BIM methodologies to enable The Ministry of Justice and Supply Chain Partners to receive the required information

deliverables (models, documents & data-sets) at the appropriate time in the right formats. To engage with the appropriate stakeholders, drive project

delivery and efficiency, and make the right project gateway decisions, and to supply appropriate information at handover to operate, maintain and

assess the performance of the delivered asset, and to integrate the delivered asset and its information into the Employer’s asset estate, creating content

once and in the right format for multiple uses thereafter. Overview of MoJBIM/GSL

https://prezi.com/moxixwmcvj78/moj-ppd-end-to-end-process-overview-with-bim-and-gsl-elements/



1.3.4 The Ministry of Justice have defined their Organisational Information Requirements (OIRs) and BIM to AIM (Asset Information Requirement)

objectives within the following documents:

STD/BIM/P001 MoJ Building Information Modelling (BIM) / Government Soft Landings Handbook (Protocol)

STD/BIM/P001.1 MoJ BIM2AIM Quick Start Guide

STD/BIM/P002 OIR Organisational Information Requirements

STD/BIM/P003 MoJ Plain Language Questions

STD/BIMP004 AIR Asset Information Requirements

STD/BIMP005 Employers Information Requirement (this document)

STD/BIMP005.1 BIM Execution Plan Template

STD/BIM/P006 BIM Maturity KPI System

STD/BIM/L001 MoJ BIM Component Library



2 BIM DELIVERY REQUIREMENTS

2.0 Information Exchanges and Project Deliverables

2.0.1 This section communicates the timing and content of information exchanges between the Project Team / Supplier and the Employer and how

information exchanges are aligned to work stages. Information may flow both ways.

2.0.2 The Ministry of Justice work to the RIBA Plan of Work 2013. At a project level, the frequency of required information exchanges will be defined within

the project IDP.

2.0.3 Whilst information can be shared at any time during the course of a stage, formal published information deliverables should be exchanged prior to the

end of a stage to advise the decision gateways, as indicated by the project IDP. These published exchanges are referred to as Information Exchanges.

2.0.4 Information deliverables required at each information exchange will be as defined by the project IDP, and STD/BIM/P004 Data Specifications. In general

those information deliverables range from files that may consist of any of the following:

2.0.5 COBie as a transmittal sheet (project directory, facility, docs and component tabs as a minimum).

2.0.6 Native and PDF documents (reports, schedules)

2.0.7 3D Models – in their native discipline (un-federated) and in open standard IFC format.

2.0.8 Drawings – cut from the models, and other documents, in PDF and DWG format

2.0.9 Structured data – manual input or from models, in BS1192-4 format, all exchanged as files and referenced in the COBie transmittal sheet, to be issued

in both IFC and XLS format.

2.1 Information Delivery Plan

2.1.1 An Information Delivery Plan will be produced by The Ministry of Justice on a project specific basis, and is interrelated to the EIR. The Design Team or

Supplier should review this plan and confirm its ability to provide the information from the appropriate resources, in the appropriate formats at the

appropriate stage decision gates.

2.1.2 It is intended that this Employer’s Information Delivery Plan will form the basis of the Suppliers Master Information Delivery Plan for preparation and

submission of information to the Employer at the appropriate stages.

2.1.3 The IDP and data specifications will include the following:

2.1.3.1 A listing of information deliverables to answer Employers ‘Plain Language Questions’ [KPI 1.1]

2.1.3.2 Format requirements, constraints or scope for each deliverable [KPI 2.3]

2.1.3.3 The Level of Definition, including Level of Detail (LOD) and Level of Information (LOI) for each deliverable



2.1.3.4 The intended role or appointed supplier for the information deliverable [KPI 2.6]

2.1.3.5 Any sensitive information to which specific security requirements will apply [KPI 2.12]

2.2 Level of Definition, Detail and Information

2.2.1 Level of Definition is a term used to define both the Level of Detail (LOD) and Level of Information (LOI) of a given element. Defining LOD and LOI

informs the degree to which suppliers can rely on the information when using the model.

2.2.1.1 LOD refers to the element’s geometry

2.2.1.2 LOI refers to the associated information

2.2.2 Where applicable, the maximum expected LOD and LOI for sensitive assets and systems will be described at each work stage, in accordance with the

Built Asset Security Information Requirements (BASIR) [KPI 2.2].

2.2.3 Guidance as to what LOI is required for each element, and the corresponding information attributes which will be expected in the corresponding COBie

(BS1192-4 compliant) data can be found at STD/BIM/P004. [KPI 3.2, 3.3].

2.3 Health & Safety and Construction Design Management

2.3.1 Information deliverables in respect of H&S/CDM are detailed in the Information Delivery Plan. The supplier should confirm how their obligations under

the Construction (Design and Management) Regulations 2015 will be supported by implementing a BIM approach for the project. [KPI 2.11].

3 Management

3.0.1 This section deals with setting the standards to be used for the definition and delivery of the project, along with how the co-ordination and review

processes will be managed.



3.1 Applicable Standards

3.1.1 The purpose of this section is to define the BIM Standards that are incorporated into the Information Requirements. The core documents and standards

that The Ministry of Justice will adopt for its projects are:

3.1.1.1 PAS 1192-2:2013 [KPI 4.1]

3.1.1.2 PAS 1192-3:2014

3.1.1.3 PAS 1192-5:2015

3.1.1.4 BS 1192:2007+A1:2015

3.1.1.5 BS 1192-4:2014

3.2 Information Management Roles and Responsibilities

3.2.1 The purpose of this section is to bring to the attention of the project team the allocation of roles associated with the management of the model and

project information.

3.2.2 The roles themselves are addressed in specific appointments and ERs. The current version of the Project Execution Plan should define the overall

responsibility and scope of appointments.

3.2.3 The following roles in connection with BIM may be taken on directly by the employer:

3.2.3.1 Employer Information Manager (EIM)

3.2.3.2 Employer Project Manager (EPM)

3.2.3.3 Built Asset Security Manager

3.2.4 The Supplier shall confirm the parties and named persons who will be responsible for information modelling and management for the project, describing what activities will be performed and what authorities will be held by each individual. [KPI 4.4]



3.3 Collaborative Working

3.3.1 The purpose of this section is to define how, where and when project information will be shared.

3.3.2 The Project Team or Supplier is expected to manage the Project Common Data Environment for each stage of the project. The management and

system providing this service may change with the appointment of different Project Teams or Suppliers for different stages or phases. There will only be

one Project CDE in operation at any one time, to avoid duplicate information.

3.3.3 Details of the collaboration process sufficient to demonstrate competence and capability must be provided in the Pre-Contract BIM Execution Plan. It is

expected that full details of the process will be included within the completed Post BIM Execution Plan.

3.3.4 The BEP should include details of:

3.3.4.1 Frequency and format of milestone information exchanges [KPI 2.2]

3.3.4.2 Proposals to manage restrictions around the sharing of data and information in connection with the Employer’s security requirements [KPI

2.12]

3.3.4.3 How the requirements of the Information Delivery Plan will be met and tracked [KPI 3.2]

3.3.4.4 Details of model review workshops and other collaborative working practices e.g. use of model federation and coordination at design and/or

site meetings [KPI 5.1]

3.3.4.5 The proposed frequency and methods for design / MoJ client team reviews using federated model/data [KPI 5.1]

3.3.4.6 How all pertinent GSL activities will be captured and recorded throughout the project, and shared at the required data exchange points [KPI

5.2]

3.3.5 The Supplier shall confirm their proposed collaboration tool and how they intend it to operate in support of the Common Data Environment in accordance with PAS 1992-2:2013 and BS 1192:2007+A1:2015. This should include details confirming how the Archive information will be transferred to the Employer upon the Practical Completion of the construction works and installations [KPI 2.10]



3.4 Discipline Based Model Authoring and Data Segregation

3.4.1 The purpose of this section is to set out requirements for the bidder’s proposals for the management of the modelling process.

3.4.2 Information should be managed in accordance with the processes described in PAS 1192-2:2013, PAS 1192-5:2015 and BS 1192:2007+A1:2015

3.4.3 Where The Ministry of Justice has specific requirements for work management, including security aspects, the requirement and request for proposals

should be identified on a project specific basis or as part of the Information Delivery Plan (IDP).

3.4.4 The Information Delivery Plan confirms the information delivery, information packaging and information exchange requirements for models, documents

and data. All published transmittals shall will be accompanied by a COBie spreadsheet confirming the included exchange files.

3.4.5 The following are required and should be confirmed in the BEP:

3.4.5.1 Model Management

Detail of quality assurance processes [KPI 3.1]

3.4.5.2 Volumes, Zones and Areas

Definitions of zones and the management of adjacency within the discipline models

Confirmation of the definition of the project volume structure

Confirmation of the volume or space naming convention to be adopted

Requirements in connection with the use of separate project volumes for sensitive assets and systems [KPI 2.12]

3.4.5.3 Naming Conventions

Consistent adoption of the MoJ asset naming convention will be applied before handover, where each building asset, MoJ BIM Space and

Component / System will be categorised and allocated with a unique reference for the purposes of utilising structured data during design,

construction and operational in use stages

There will be an agreed and consistent space naming convention for space type (MoJ BIM Library) and project-specific nomenclature.

The Ministry of Justice File Classification and Naming Convention will be adopted for all projects as described in STD/BIM/P001.1 Quick Start

Guide.

The file naming convention shall be used for all document types in line with BS1192:2007+A1 2015 which supports the CDE and AIM workflows.

The MoJ Client CDE has a number of fields and ‘meta-data tags’ available to assist with upload and future identification purposes. When uploading

information, the two critical identity fields to complete are ‘Name*’, and ‘Description’.

CDE File ‘Name*’ Using MoJ specific identifiers as part of the BS1192:2007 naming convention the ‘Name*:’ should be entered as below:

Project (ePIM-BPRN)-Originator-Volume/System-Level/Location-Type-Role-Number-Suitability*-Revision*-#DeliveryReference

Graphical Information such as a 3D native PIM (model) on a MoJ HQ project should be file named as:



‘403005-2889-PCS-SHB-ZZ-M3-Y-000-S1-P01.01-D0600’

When uploading to a Client CDE, metadata for status and #DelRef should be used and a fuller recognisable description entered in the File name

description which is free test and allows a fuller explanation of the file. It is blank by default and will need to be completed for each file.

An example of File name description field:

‘HMP Stocken-Civic-House Block-All Levels-Number 000-Suitable for Co-ordination-Revision P01.01’

Suitability status For WIP & Shared issues use BS1192:2007+A1:2015 Table 3 WIP & Shared status codes

3.4.5.4 Publishing processes

The contents of stage Information Exchanges are defined in the Information Delivery Plan

These will be published by the Supplier Information Manager from the appropriate CDE to complete the particular delivery stage.

Data delivered at key work stages will be accompanied by a COBie file which will be used to validate the delivery.

The Supplier Information Manager will notify the Employer Information Manager once all required data deliverables have been uploaded to the

CDE.

The Employer Information Manager will validate the data and produce a Red Amber Green (RAG) acceptance report to the Supplier Information

Manager.

Green packages will be published into the Employer CDE Published file area and the COBie data and file linkages published into the Employer CDE

data area for onward use.

Amber or Red packages should be remedied by the Supplier.

Acceptance of failure and resubmission of deliverables in accordance with the Information Delivery Plan is unlikely to cause a

variation/compensation event.

Confirmation of these procedures should be confirmed in the Pre-Contract BIM Execution plan.

3.5 Security

3.5.1 The purpose of this section is to communicate the security measures required to protect personal and commercial information on behalf of The Ministry

of Justice. Government Document Security Classification should be adopted, balancing the project-specific needs of Confidentiality, Integrity and

Accessibility with the consequences of any loss or unauthorised release of the information. As a guide, the majority of MoJ project data-sets will be

typically categorised as ‘OFFICIAL’ unless stated otherwise. Security is defined in accordance with business impact levels defined in the HMG Security

Policy Framework and Government Security Classifications April 2014.

3.5.2 For all built assets, specific security measures related to information exchange will be identified on a project specific basis, and communicated to the

supply chain accordingly. The IDP will communicate specific requirements related to sensitive assets, work packages or data drops. For built assets



requiring more than baseline ‘OFFICIAL’ security measures, the details of the Employer’s security requirements as derived from the BASS, BASMP and

BASIR will be implemented accordingly.

3.5.3 Any file when uploaded to the Supplier CDE or otherwise disclosed, shared, published or exchanged is to be secure in accordance with the standards

described in PAS1192-5.

3.5.4 The submission should demonstrate the supplier’s compliance with any mandated security systems. The completed BIM Execution Plan will set out

compliance processes and the means by which compliance is monitored and managed to deliver against these security requirements.

3.5.5 Where applicable, in the case of sensitive asset data as identified by the employer, the bid response should set out how the requirements of the BASIR

will be achieved in respect of software platforms, their configuration, operation and maintenance [KPI 2.12]



3.6 Coordination and Clash Detection

3.6.1 The purpose of this section is to ask the supplier to define their co-ordination process, in order to meet employer requirements for quality control.

3.6.2 The following details of the clash detection process should be detailed in the Pre-Contract BIM Execution Plan:

3.6.2.1 Associated Software

3.6.2.2 Process overview

3.6.2.3 Responsibilities

3.6.2.4 Outputs

3.6.2.5 Proposed workflow and systems for verifying generated and received project data [KPI 3.2]

3.6.2.6 Proposed workflow and systems for validating generated and received project data [KPI 3.3]

3.6.2.7 Tolerance strategy

3.6.2.8 Clash resolution process

3.6.2.9 Verifying technical queries to the supplier (files and data in place) [KPI 3.4], validating suitability of data content with supplier [KPI 3.5]

3.6.2.10 Proposal for quality assurance and liaison with the Client / end users when incorporating PIM data into an Asset Information Model (for FM

Operations, and other MoJ Asset Management purposes) [KPI 3.1]

3.6.2.11 How this process will align with the employers contractual and process requirements, such as ongoing / periodic technical review.

3.6.3 The Supplier shall confirm coordination and clash avoidance processes, with reference to:

3.6.3.1 Volume strategy

3.6.3.2 Tolerance strategy

3.6.3.3 Technical query workflows

3.6.3.4 Responsibilities for coordination and clash avoidance

3.6.3.5 Software to support coordination and clash avoidance

3.6.3.6 Outputs from coordination and clash avoidance processes



3.7 Compliance Plan

3.7.1 The purpose of this section is to enable the supplier to communicate how the integrity, and hence quality, of the model and other data sources will be

maintained.

3.7.2 All published information exchanges will be validated using the included COBie-BS1192-4 file against the Information Delivery Plan for the stage

information exchange. Only compliant exchanges will be accepted.

3.7.3 The supplier should confirm his own internal model file and data standards and compliance procedures including references to standards and

compliance software in the BIM Execution Plan.

3.7.4 This should refer to:

3.7.4.1 Quality assurance/control procedure

3.7.4.2 Associated software

3.7.4.3 Period of aftercare (the number of years that the model should be managed for)

3.7.4.4 Security and information assurance requirements

3.7.5 The Employer or Employer Project or Information Manager should be given reasonable access to the Supplier CDE to enable compliance monitoring

and audits.

3.7.6 The Supplier shall confirm their quality assurance processes for Data, Models and Documents [KPI 3.1]

3.7.7 If aftercare is required, the contractor must specify the period of aftercare (the number of years that the model should be managed for) following

handover.

3.8 Delivery Strategy for Asset Information

3.8.1 This section defines the information exchange standard for asset information and enables the employer to obtain proposals with regards to asset

information delivery into the employer’s FM environment.

3.8.2 The information exchange format for provision to the Asset Information Model (AIM) will be as defined in the Information Delivery plan transmitted and

contained in the published information exchange COBie file together with associated exchange information files.

3.8.3 Where practicable, COBie-BS1192-4 excel sheet data structure shall be used as the default exchange format for all project related information whether

3D modelling is involved or otherwise. For all mandated projects the expectation shall be for the following COBie-BS1192-4 tabs to be completed as a

minimum:

3.8.3.1 ‘Facility’ the named location of the change project. Usually just a single line on this tab.

3.8.3.2 ‘Contacts’ for full Project Directory / contact sheet

3.8.3.3 ‘Components’ and ‘Systems’ for the project Asset Schedule



3.8.3.4 ‘Documents’ for Packages of information issued, whether 3D models, 2D data, data tables, schedules, Operations and Maintenance guidance

3.8.3.5 ‘Impact’ use this tab for recording pertinent GSL activities at the required GSL data exchange points, typically Stage 3 and Stage 6, 7

3.8.3.6 Asset information is to be delivered in accordance with the details described in BS1192-4:2014 and PAS 1192-5:2015. The integrity of data,

included within the COBie scheme, should be ensured as follows:

3.8.3.7 Every Component should be assigned to at least one Space.

3.8.3.8 Every Component should be assigned to one Type.

3.8.3.9 Every Component should be assigned to at least one System.

3.8.3.10 Every Space should be assigned to at least one Zone.

3.8.3.11 Every reference to other sheets should be valid.

3.8.3.12 Every reference to Pick List enumerations and classifications should be valid.

3.8.3.13 Enumerations specified in the Attributes and Pick Lists should be adhered to.

3.8.3.14 Documents deliverable information requirements are defined in STD/BIMP004 AIR series of data specifications to be read in combination with

the Information Delivery Plan.

3.8.3.15 Object Information detail is defined in the RIBA / Digital Plan of Works and can be downloaded from thenbs.com.

3.9 Template Provision (MIDP and Project Plan)

3.9.1 The following approach should be used by the Supplier to ensure information coordination and consistency:

3.9.2 Master Information Delivery Plan (MIDP). This should be prepared by the supplier in response to the Information delivery Plan and should follow a

similar or related format.

3.9.3 Project Plan (PP). This will be provided to the Supplier to allow an appreciation of the strategic programme intent for the project and to enable the

development of the Suppliers programme proposal.

3.9.4 In the absence of the Project Plan the Information Delivery Plan will be used by all team members to manage and monitor progress and information

delivery for the duration of the project.



3.10 Training

3.10.1 The purpose of this section is to provide bidders with details of training that will be provided in connection with project systems, or training requirements

which the bidder will be required to deliver as part of their appointment/contract.

3.10.2 The Supplier shall confirm the training that they will provide for their tools and systems that the Employer and others will be expected to use which will

include, but not be limited to the BIM Execution Plan and Supplier’s collaboration tools

3.10.3 The supplier will be responsible for maintaining and delivering appropriate information handling and access training to all interfacing parties including

any Employer staff, for the operation and access to the Supplier CDE.

3.10.4 Training for access and operation to the Employer CDE will be provided by the Employer to interfacing Supplier staff as required. If proprietary model

viewing software is proposed in variance to that shown as held by the Employer in this document then reasonable access and training is to be provided

by the Supplier at no cost.

3.10.5 Any general security awareness and induction requirements, as well as any role-based security requirements, will be highlighted to the Supplier on a

project specific basis, and set out in the Employer’s Built Asset Security Management Plan (BASMP).

3.10.6 Information should be progressively shared and published from the Supplier CDE to the Employer CDE so that in normal circumstances the Employer

will not need access to the Supplier CDE other than for compliance purposes.



4 Technical

4.0 Software Platforms

4.0.1 The purpose of this section is to communicate software platforms and versions where these are known and where they might influence the preparation

of a bid. For public bodies OJEU rules preclude specification and selection based on proprietary systems use.

4.0.2 Platforms and versions used by The Ministry of Justice for MoJ BIM Library Elements across the programme of projects include the following:

4.0.2.1 Common Data Environment for Information Exchanges 4Projects/Viewpoint Core 3G

4.0.2.2 Autodesk Revit 2015 for MoJBIM Library v3.0

4.0.2.3 Solibri Model Viewer / Solibri Model Checker

4.0.2.4 COBie-UK-2012

4.0.2.5 Industry Foundation Class (IFC) 2x3

4.0.3 The ability of the bidder to work with these platforms should be made clear in the response.

4.0.4 Designers and Constructors should align their model attribute data to be consistent with the data exchange format BS1192-4. However the COBie data

takes precedent.

4.0.5 The BEP should confirm the process of data compilation between models and COBie.

4.0.6 The Supplier shall confirm how data and information from their authoring tools will be prepared and published so that it can be used with the software

platforms outlined.

4.1 System Performance

4.1.1 The purpose of this section is to communicate to bidders any constraints in the employer’s systems or specific IT requirements which may need

additional resources or non- standard solutions.

4.1.2 The BEP will confirm adoption of system performance requirements. [KPI 2.14]

4.1.3 The following employer-side IT system restrictions and requirements need to be taken into account when developing the BIM Execution Plan:

4.1.4 Model size - no physical size restriction but practically 100Mb max

4.1.5 Software uses - IFC federated model visualisation can be viewed in the Employer CDE and The Ministry of Justice IFC CDE Viewer

4.1.6 Security issues - as required in the security section of this document



4.2 Data Exchange Format

4.2.1 The purpose of this section is to define the formats used to deliver the Information Exchanges. At a project level, information will be required in a format

as defined in the Information Delivery Plan and subject to project specific requirements, which may include any of following outputs:

4.2.1.1 Native – 3D discipline (un-federated) model files for all design and analysis models

4.2.1.2 Common file format - IFC model files, including both individual and federated

4.2.1.3 PDF files – no older than version 7.0 as a default

4.2.1.4 COBie – BS1192-4 compliant, complete with reference to the exchanged documents and files

4.2.1.5 On projects where PAS 1192-5:2015 is applied, information about sensitive assets and systems will be required in the format specified in the

BASIR.

4.3 Coordinates

4.3.1 The purpose of this section is to encourage the adoption a common coordinate system for all BIM data with consistent adoption for all models. Defines

requirements for the common coordinate system for all BIM data.

4.3.2 The minimum requirement is spatial coordination stated as follows:

4.3.2.1 Intersection of grids XX and YY - xxxxxx.xxxE and xxxxxx.xxxN

4.3.2.2 Intersection of grids AA and BB - xxxxxx.xxxE and xxxxxx.xxxN

4.3.2.3 Ground floor FFL = xxx.xxx

4.3.3 Other coordination standards defined in the BIM Execution Plan should include:

4.3.3.1 Origin rotation

4.3.3.2 Offsets

4.3.3.3 Datum information

4.3.3.4 Units to be used

4.3.4 3D geo-location co-ordinates to be shown to no less accurate than 10mm (0.01m) in all directions.



5 Commercial

5.0 BIM Execution Plan

5.0.1 The Supplier shall prepare, deliver and maintain a BIM Execution Plan (BEP) for the project that responds to this Employer Information Requirements

with responses directly correlating to the section references within this document and guided response BEP headings (STD/BIM/P005.2).

5.0.2 The Supplier shall review their BEP regularly and additionally when there is any change to their contract.

5.0.3 Pre and Post Building Information Modelling Execution Plans are to be provided in response to the Employer’s Information Requirements identifying the

Supplier proposals clause by clause. The Pre-Contract BIM Execution Plan will be scored as part of the tender submission.

5.1 BIM Specific Competence Requirements

5.1.1 This section details the information that a bidder should be required to provide as part of a bid submission, to demonstrate BIM capacity and experience.

5.1.2 Responses will need to describe how mature an organisation is, and what capabilities are held specifically where this is in accordance with the

standards sighted in this EIR.

5.1.3 Tenderers should include the following detail:

5.1.3.1 Approach to BIM – organisational culture with regards to BIM

5.1.3.2 BIM experience – organisational capability and personnel. Level of skill and competency

5.1.3.3 BIM capabilities – examples of previous projects delivered in accordance with the standards sighted in this EIR

5.1.3.4 Security understanding, capability, competence and experience

5.1.3.5 Out-sourced roles – any BIM related roles which are outsourced

5.2 Confirmation of BIM Toolset

5.2.1 Responses will describe the processes and procedures that make up the bidder’s BIM and information management toolkit specifically where this is in

accordance with the standards cited in this EIR

5.2.2 Tenderers should include the detail on procedures aligned with core project stages as follows:

5.2.2.1 BS1192:2007+A1:2015

5.2.2.2 PAS1192-2:2013

5.2.2.3 BS1192-4:2014



5.2.2.4 Other bespoke processes

5.2.3 The information requested in this section is detailed further in PAS 1192-2:2013.

5.3 Details of BIM Workload and Resourcing

5.3.1 Responses will describe the resources (and what levels) that are available to the project


5.3.2.1 Resource matrix with level, number, utilisation

5.3.2.2 Outsourcing details or services etc.

5.3.2.3 The content of the assessment is described as the supplier BIM assessment form described in PAS 1192-2:2013.

5.4 Principal Supply Chain

5.4.1 Responses will describe the supply chain’s ability to link into the process and how will this be assessed


5.4.2.1 Key supply chain partners

5.4.2.2 Expected outputs

5.4.2.3 Assessment process

5.4.3 The information requested in this section is detailed further in PAS 1192-2:2013.

>End



Glossary of Abbreviations and Terms

BEP BIM Execution Plan

BIM Building Information Modelling

BSRIA Building Services Research and Information Association

BWM BIM workgroup meeting

CIC Construction Industry Council

CDE Common Data Environment

EIR Employer Information Requirement

IFC Industry Foundation Class

LOD Level of Detail

LOI Level of Information

MPDT Model Production Delivery Table

NBS National Building Specification

WIP Work In Progress



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.

Building

information

modelling

execution plan

(BEP)

Plan prepared by the suppliers, facilitated by the Employer or the

Employer’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

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 employer 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 SaaS solution synchronised with party servers to host the

information model

Data

Information stored but not yet interpreted or analysed

Design intent

model

Initial version of the project information model (PIM) 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 A federated model is an assembly of distinct models or design

disciplines, to create a single complete model of the building. Eg



Architectural, Structural and Mechanical models may be viewed in a

single ‘federated’ model.

Graphical data

Data conveyed using shape and arrangement in space

Level of Definition

Collective term used for and including “level of model detail” and the

“level of model information”

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 is 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



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



Other sources of Information available:

STD/BIM/P001.1 MoJ BIM2AIM Quick Start Guide

STD/BIM/P002 OIR Organisational Information Requirements

STD/BIM/P003 MoJ Plain Language Questions

STD/BIMP004 AIR Asset Information Requirements AIR-IDP

STD/BIM/004.1 Data Categories

STD/BIM/P004.2 COBie Data Matrix

STD/BIM/P004.3 Performance Attribute Data

STD/BIMP005.1 BIM Execution Plan Template

STD/BIM/P006 BIM Maturity KPI System

STD/BIM/L001 MoJ BIM Component Library



Acknowledgements Principle contributors to the development and production of the MoJ BIM2AIM suite of documents:

Matthew Watchorn Chris Barker Head of BIM - UK Ministry of Justice Regional BIM Manager - Wates Group Client Lead (OIR/PLQ/KPI) - MoJ BIM2AIM Special Interest Group Chairman / Group 3 (AIR) - MoJ BIM2AIM Special Interest Group

Special thanks to: Chris Barker and SIG Syndicate Leads, Belinda Mather-Derek Alex Lubbock, Paul Lee, John Ford, Graeme Tapenden, Mobeen Minai, Philip Tandy and all contributing members of BIM2AIM SIG

Nick Voegt BIM Consultant & Information Manager - Arcadis Group 1 (EIR/IDP) - MoJ BIM2AIM Special Interest Group

Special thanks to Group 1 members: James Burke, Guilio Castorina, Edonis Jesus, Alex Jones, Paul Lee, Etienne Leroux, Tom Loader, Fiona Moore, Andrew Moulds, Duncan Mulholland, Andy Radley, Ian Rye

Johnathan Munkley BIM Director - WYG Group Group 2 (BEP) - MoJ BIM2AIM Special Interest Group

Special thanks to Group 2 members: Kevin Bell, Owen Cockle, Keith Dight, Barry Farmer, Mark Hughes, Jaimie Johnson, Laurice Peverett, Philippe Sauvageot, Martin Noble

Dean Hunt Associate / BIM Manager - Stride Treglown Group Group 3 (AIR) - MoJ BIM2AIM Special Interest Group

Special thanks to Group 3 members: Catharine Dass, Simon Gilbert, Jonathan Harrison, David Jellings, Mobeen Minai, Martin Noble, Jeff Stephens, Anna Thompson, Nick Tune, Anthony Walsh

Information Requirements for Building Information ...

Documents

Transcript of Information Requirements for Building Information ...