30
Building Information Modelling for Network Rail (BIM4NR) Process Original Document Ref: NR-IP-EN-2517 Version: 4.0 Transitional Ref: BIM4NR-001 April 2021

Building Information Modelling for Network Rail (BIM4NR

  • Upload
    others

  • View
    56

  • Download
    1

Embed Size (px)

Citation preview

Building Information Modelling for Network Rail (BIM4NR) Process

Original Document Ref: NR-IP-EN-2517

Version: 4.0

Transitional Ref: BIM4NR-001

April 2021

OFFICIAL OFFICIAL

TRANSITIONAL DOCUMENT: This document is in the process of being

updated.

This document was produced by the BIM4NR (formerly BIM4IP) Change Programme to enable

NR Infrastructure Projects to effectively implement Building Information Modelling (BIM)

according to BS1192 suite of standards using Governance of Railway Investment Projects (GRIP)

stages.

Since publication: the operating model used by Network Rail has transformed into a devolved

organisation of 5 regions supported by services and functions; the BS1192 suite of standards are

being superseded by the ISO19650 suite; and GRIP stages are being replaced by Project

Acceleration in a Controlled Environment (PACE) Phases.

For inflight projects using these materials following the GRIP Stages no change is needed and this

document can be used as is.

For new projects using PACE and/or ISO19650 this material can be used as reference in

conjunction with advice from the NR Regional BIM Lead (https://nrbimportal.co.uk/contact-us/).

OFFICIAL OFFICIAL

1 Purpose The purpose of this document is to set-out how Network Rail Capital Delivery shall proceed with a

common approach to information, to enable the delivery of the benefits associated with Information

Management in a broader Network Rail context and in partnership with our Contractors.

Figure 1.1 Re-use of Data Figure 1.2 Asset Information remains Constant

This process defines what is required in order to ensure the Information policies within the NR Engineering

Governance and Operating Model NR-IP-EN-1832 are easily and consistently embedded within the NR

Regions programme and project teams.

2 Scope The processes and arrangements described in this document are mandatory for all projects undertaken by NR. This includes where the design for a project is undertaking BIM4NR Projects.

When other Programmes or teams within NR, Asset Management or Infrastructure Maintenance, deliver works on behalf of NR then the Project Manager must formally agree with these parties how the requirements are met.

The scope of this process applies to projects ‘Information Model’ (Figure 1.3) which is a collective term used to describe the various types of information produced and managed on any given project. This includes but is not limited to:

• Graphical Data (a graphical representation of the asset)

o Vector and coordinate based graphics, typically contained within a single file or relational

database; for example, 2D/3D CAD or GIS file. This includes graphical data that is required

to be stored within a managed system and follow a defined workflow;

• Structured Data (the physical and functional characteristics of the asset)

o Data contained within a machine-readable structure, such as a database; spreadsheet or

textual (XML etc.);

• Documentation (any record documents associated to the asset)

OFFICIAL OFFICIAL

o A body of material on a subject or asset, typically in the form of drawings, images,

calculations, manuals etc.; and for example, Health & Safety or CDM documentation etc.

This includes documentation that is required to be stored within a managed system and

follow a defined workflow; for example, the authorisation process for GRIP products,

Document Review Notice, Requests for Information, Technical Queries, transmittal or

meeting minutes etc.;

Each element of the project’s Information Model is contained in separate files within the Common

Data Environment (CDE).

Figure 1.3 Information Model

2.1 Types of Information Model There are three main types of Information Model, which follow the typical lifecycle of an asset (Figure

1.4):

1. Design Information Model (GRIP 1-4)

2. Construction Information Model (GRIP 5-6)

3. Asset Information Model (GRIP 7)

Figure 1.4 Types of Information Model

OFFICIAL OFFICIAL

2.2 Responsibility and Accountability

Accountable, Responsible, Consulted, Informed Process Step

Spo

nsor (E

mplo

yer)

Route

/Reg

ion P

roje

ct In

form

atio

n M

an

ager

(Em

plo

yer)

Pro

ject M

anag

er (E

mplo

yer)

Desig

nate

d P

roje

ct E

ngin

eer (D

PE

)

Pro

ject D

eliv

ery

Ma

na

ger (C

ontra

cto

r)

Desig

n C

onstru

ctio

n L

ead (C

ontra

cto

r)

Pro

ject In

form

atio

n M

anag

er (E

mp

loyer)

Com

merc

ial M

ana

ger (E

mp

loyer)

Pro

gra

mm

e C

on

trols

Mana

ger (E

mplo

yer)

Stage Section Nr. Process

High Level 5.1 Start

A R C C I I I

High Level 5.2 BIM4NRP Dashboard

A R C C I I I

High Level 5.3

Project Information Requirements Tool (PIRT)

C R A C I I I

High Level 5.4 GRIP Stage 1

C C A C R R R I I

High Level 5.5 GRIP Stages 2-3

C C A C R R R I I

High Level 5.6 GRIP Stage 4

C C A C R R R I I

High Level 5.7 GRIP Stage 5

C C A C R R R I I

High Level 5.8 GRIP Stage 6

C C A C R R R I I

High Level 5.9 GRIP Stages 7-8

C C A C R R R I I

High Level 5.10 Finish

A C R C I I C C C

GRIP Stage 1 (See Section 5.4)

5.4.1 Start A R C C I I I

5.4.2 Project Information Requirements Tool (PIRT)

C R A C I I I

5.4.3

Determine Information Management and Common Data Environment Strategy

C R A C C C I I

5.4.4 Determine Team Roles and Responsibilities

C R A C C C I I I

5.4.5 Determine BIM, GIS and AIS Strategy

C R A C C C C I I

5.4.6 Determine the Built Asset Security Strategy

C R A C C C C I I

5.4.7

Complete Sponsors Handbook Steps For Early GRIP Stages

A C R C C I I

5.4.8 Follow GRIP / IELCP Process Map

C R A R R R R R R

5.4.9 Update GRIP Stage Gate C R A C C I I

5.4.10 Update IELCP Phase Gate C C C A/R C I I

OFFICIAL OFFICIAL

Accountable, Responsible, Consulted, Informed Process Step

Spo

nsor (E

mplo

yer)

Route

/Reg

ion P

roje

ct In

form

atio

n M

an

ager

(Em

plo

yer)

Pro

ject M

anag

er (E

mplo

yer)

Desig

nate

d P

roje

ct E

ngin

eer (D

PE

)

Pro

ject D

eliv

ery

Ma

na

ger (C

ontra

cto

r)

Desig

n C

onstru

ctio

n L

ead (C

ontra

cto

r)

Pro

ject In

form

atio

n M

anag

er (E

mp

loyer)

Com

merc

ial M

ana

ger (E

mp

loyer)

Pro

gra

mm

e C

on

trols

Mana

ger (E

mplo

yer)

Stage Section Nr. Process

5.4.11

Complete BIM4NRP GRIP Stage 1 Checklist

A R C C C I I

GRIP Stages 2-3 (See Section 5.5)

5.5.1 Start A R C C I I I

5.5.2 Review BIM4NRP Checklist From Previous GRIP Stage

C R A C C I C

5.5.3 Validate Project Information Requirements

A R C C I I I

5.5.4 Create Employer Information Model

C R A C C C R I I

5.5.5 Develop Employers Information Requirements

C R A C C C R C C

5.5.6

Determine Project Technology and Systems Integration

C R A C C C R C C

5.5.7 Review Team Roles and Responsibilities

C R A C C C R C C

5.5.8 Produce BIM Contract Requirements - Technical

C R A C C C R R C

5.5.9 Assess Supply Chain Capacity and Capability

I C A C R R C I I

5.5.10 Update GRIP Stage Gate C R A C C I I

5.5.11 Update IELCP Phase Gate C C C A/R C I I

5.5.12 Complete BIM4NRP GRIP Stages 2-3 Checklist

A R C C C I I

GRIP Stage 4 (See Section 5.6)

5.6.1 Start A R C C I I I

5.6.2 Review BIM4NRP Checklist From Previous GRIP Stage

C R A C C C C I C

5.6.3 Validate Project Information Requirements

C R A C I I I

5.6.4

Supply Chain BIM Execution Plan (Pre-Contract)

C C C C A R I I I

5.6.5 Prepare MIDP / TIDP / Responsibility Matrix

I C C C A R I I I

5.6.6 Prepare and Issue BIM Protocol & MPDT

I C A C A R C I I

5.6.7

Determine and Implement PIM Data Exchanges and Validation

I R A C A R C I C

5.6.8 Update GRIP Stage Gate C R A C C I I

OFFICIAL OFFICIAL

Accountable, Responsible, Consulted, Informed Process Step

Spo

nsor (E

mplo

yer)

Route

/Reg

ion P

roje

ct In

form

atio

n M

an

ager

(Em

plo

yer)

Pro

ject M

anag

er (E

mplo

yer)

Desig

nate

d P

roje

ct E

ngin

eer (D

PE

)

Pro

ject D

eliv

ery

Ma

na

ger (C

ontra

cto

r)

Desig

n C

onstru

ctio

n L

ead (C

ontra

cto

r)

Pro

ject In

form

atio

n M

anag

er (E

mp

loyer)

Com

merc

ial M

ana

ger (E

mp

loyer)

Pro

gra

mm

e C

on

trols

Mana

ger (E

mplo

yer)

Stage Section Nr. Process

5.6.9 Update IELCP Phase Gate C C C A/R C I I

5.6.10 Complete BIM4NRP GRIP Stage 4 Checklist

A R C C C I I

GRIP Stage 5 (See Section 5.7)

5.7.1 Start A R C C I I I

5.7.2 Review BIM4NRP Checklist From Previous GRIP Stage

C R A C C I C

5.7.3 Validate Project Information Requirements

C R A C I I I

5.7.4

Supply Chain BIM Execution Plan (Post-Contract)

C C C C A R I I I

5.7.5 Undertake Model Review at IDC/IDR Meetings

C I C C A R C I I

5.7.6 Review MIDP / TIDP Progress

C C A R A R C I I

5.7.7 Review BIM Protocol & MPDT

I C A C A R C I I

5.7.8 Review PIM Data Exchanges and Validation

I R A C A R C I C

5.7.9 Update GRIP Stage Gate C R A C C I I

5.7.10 Update IELCP Phase Gate C C C A/R C I I

5.7.11 Complete BIM4NRP GRIP Stage 5 Checklist

A R C C C I I

GRIP Stage 6 (See Section 5.8)

5.8.1 Start A R C C I I I

5.8.2

Review BIM4NRP Checklist from the Previous GRIP Stage

C R A C C I C

5.8.3 Validate Project Information Requirements

C R A C I I I

5.8.4 Undertake Model Review at IDC/IDR Meetings

C I C C A R C I I

5.8.5 Review PIM Data Exchanges and Validation

I R A C A R C I C

5.8.6 Update GRIP Stage Gate C R A C C I I

5.8.7 Update IELCP Phase Gate C C C A/R C I I

5.8.8

Complete BIM4NRP GRIP Stage 6 Checklist

A R C C C I I

5.9.1 Start A R C C I I I

OFFICIAL OFFICIAL

Accountable, Responsible, Consulted, Informed Process Step

Spo

nsor (E

mplo

yer)

Route

/Reg

ion P

roje

ct In

form

atio

n M

an

ager

(Em

plo

yer)

Pro

ject M

anag

er (E

mplo

yer)

Desig

nate

d P

roje

ct E

ngin

eer (D

PE

)

Pro

ject D

eliv

ery

Ma

na

ger (C

ontra

cto

r)

Desig

n C

onstru

ctio

n L

ead (C

ontra

cto

r)

Pro

ject In

form

atio

n M

anag

er (E

mp

loyer)

Com

merc

ial M

ana

ger (E

mp

loyer)

Pro

gra

mm

e C

on

trols

Mana

ger (E

mplo

yer)

Stage Section Nr. Process

GRIP Stages 7-8 (See Section 5.9)

5.9.2 Review Checklist From Previous GRIP Stage

C R A C C I C

5.9.3 Validate Project Information Requirements

C R A C I I I

5.9.4 Complete Sponsors Handbook Steps

A C R C C I I

5.9.5

Data Transfer to Asset Information Management / Custodian

I C A C C C R I I

5.9.6

Transmit Source Records / As Constructed / As-Built to NRG

I C A C C C R I I

5.9.7

Transmit Health & Safety / Technical File to Custodian / Owner

I C A C C C R I I

5.9.8 Update GRIP Stage Gate C R A C C I I

5.9.9 Update IELCP Phase Gate C C C A/R C I I

5.9.10 Complete BIM4NRP GRIP Stages 7-8 Checklist

A R C C C I I

3 Document History Please see version history on NR IMS which includes comments relating to changes made, by whom

and when. From the documents library, right click on the document title and select ‘version history’.

OFFICIAL OFFICIAL

4 Definitions, Abbreviations and Referenced Documents

4.1 Definitions Term to be defined Concise definition of term

BIM The term ‘BIM’ is defined as Building Information Modelling. Within Infrastructure Projects, the BIM4NRP process will be utilised to support and underpin enhanced and efficient methods of briefing, designing, procuring, delivering and maintaining physical built assets, as well as managing the digital information which is a valuable asset in itself. It will make our delivery of rail enhancements and renewals safer, better, faster, more collaborative, more innovative and cheaper for our clients, stakeholders and Contractors and enable our future digital railway.

Employer’s Project Information Manager

A role, working on behalf of Network Rail (the client), is responsible for defining the Information Requirements, and is accountable for the vast majority of tasks relating to Information Management. This is an Infrastructure Projects role that is likely to be undertaken by a combination of Project Sponsors, Project Managers, Senior Engineers, Designated Project Engineers and/or Departmental Engineering Managers.

Information Model The term ‘Information Model’ is a collective term used to describe a complete set of information relating to specific asset. An Information Model contains graphical data, structured data and documentation that have been fully coordinated with each other.

Project Information Requirements

The term ‘Project Information Requirements’ is a collective term used to describe the various requirements for information throughout the appointment, including, but not limited to: • requirements for information from Network Rail to operate and

maintain the asset; • requirements for information from Infrastructure Projects to manage

the project; • requirements for information from internal and/or external

stakeholders; • requirements for the data standards, methods and procedures that

need to be applied; • requirements for the standard library objects to be used for

production; • requirements for the information technologies that need to be

adopted; • requirements for the information protocol (contractual

arrangements) to be used; and • the information (handover) to be provided by Infrastructure Projects

at the start.

4.2 Abbreviations Abbreviation Full terminology

ADEP Asset Data Exchange Plan

BIM4NRP BIM for Network Rail Projects

CDE Common Data Environment

DPE Designated Project Engineer

GRIP Governance for Railway Investment Projects

IELCP Integrated Engineering Lifecycle for Projects

LoC Level of Control

MIDP Master Information Delivery Plan

MPDT Model Production and Delivery Table

PCAT Project Characterisation Tool

PIRT Project Information Requirements Tool

P3M3 Portfolio, Programme and Project Management Maturity Model

TIDP Task Information Delivery Plan

OFFICIAL OFFICIAL

4.3 Process References and Referenced Documentation Documents cross referenced in this document are listed in alpha-numeric order, in the following table:

Reference Number Title Owning Profession

NR-IP-EN-1832 NR Engineering Governance and Operating Model

Engineering

NR/L2/INI/P3M/101 Governance for Railway Investment Projects (GRIP) – Projects

Programme Management

NR/L2/INI/P3M/102 [Issue: 2]

Governance for Railway Investment Projects (GRIP) – Programmes

Programme Management

NR/L2/INI/0300 Integrated Engineering Lifecycle for Projects (IELCP)

Engineering

NR/L2/INI/02009 Engineering Management for Projects (NR/SP/BUS/02009/ RT/E/P/02009)

Head of Quality Assurance

NR/L2/ADG/003 [Issue 1] Asset Data Exchange Plan Asset Data Governance

NR/L3/MTC/089 [Issue: 1] Asset Management Plan (formerly NR/L3/EBM/089)

Maintenance

AIS Hub Asset Information Services Hub (accessed October 2018)

AIS

NR/GN/INI/P3M/150 [Issue 1] Sponsor’s Handbook Sponsorship

NR/L2/INI/P3M/104 [Issue: 2] Network Rail requirements (formerly NR/L1/INI/CP0095)

Programme Management

NR/L2/INF/02220 Document and Records Management Information Management

NR/L2/INF/02202 Records management of Health and Safety Files Information Management

NR/L3/INF/02222 Metadata for Documents and Records Head of Business Operations

NR/L2/INI/EDT/CP0091 Specification for Computer Aided Design Engineering

GRIP Product Index GRIP Product Index Programme Management

BIM4NRP Project Information Requirements Tool

Project Information Requirements Tool Engineering

Project Characterisation Tool (PCAT)

Project Characterisation Tool (PCAT) is used to output an indicative project specific deliverables list. The tool output is used to support the relevant engineering phase.

Engineering

Project Characterisation Tool (Guidance on Usage)

PCAT Guidance on how to use the tool Engineering

CIC BIM Protocol Construction Industry Council’s BIM protocol Engineering

CIC MPDT Model Production and Delivery Table Engineering

4.4 Supporting Process Information L3 Process name: Define and implement the NR Engineering Governance & Operating

Model. L3 Process reference: 2-3-1 Strategic Objective: We safely and sustainably deliver infrastructure projects ‘On Time’ /

‘On Spec’ / ‘On Cost’ for our Route Clients. Critical Success factor: Engineering Expertise.

OFFICIAL OFFICIAL

5 Requirements The process representation of the BIM4NRP process steps is shown below:

The BIM4NRP process supports the policy outlined in the NR Engineering Governance and Operating

Model (NR IMS Ref: NR-IP-EN-1832, Section 8).

Input

1. Projects that are receiving late or non-compliant information;

2. Projects that do not have a defined list of deliverables for the current or future GRIP Stages; or

3. Projects that have risks in their risk register relating to the capability and/or capacity of their

Contractors to deliver the required information in a timely and/or complaint manner.

OFFICIAL OFFICIAL

5.1 Start Project is approved and initiated.

5.2 BIMNRP Dashboard The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

use the BIM4NRP Dashboard via the Network Rail BIM Portal (see 2-3-1-3-2 BIM4NRP Data

Lifecycle GRIP Stage Diagram). The BIM4NRP Dashboard provides a structured interface to BIM

Information and processes required to deliver a project and is aligned with the project data lifecycle

and GRIP stage. The BIM4NRP Dashboard also provides:

• The Engineering phase and the key BIM tasks for each stage

• Access to templates documents, standards and plain language questions

GRIP stage activities will be dependent on the GRIP stage the project is starting from, the Level of

Control of the individual project, whether the project is single or multi-discipline and whether the

previous GRIP stage checklist items have been included.

• Complete an assessment using the PIRT tool

• Complete all previous GRIP stage checklists

• Action any requirements identified

NOTE: the order of each task at each GRIP stage is not mandated and the timeline is indicative and

shall be dictated by the immediate project needs.

5.3 Project Information Requirements Tool (PIRT) The BIM4NRP Project Information Requirements Tool provides a method to assess a project to

establish what Information requirements the Project shall adopt. The tool uses a questionnaire format

that is designed to identify the appropriate information requirements.

OFFICIAL OFFICIAL

5.4 GRIP Stage 1

5.4.1 Start The process for GRIP Stage 1 starts here.

5.4.2 Project Information Requirements Tool (PIRT) Project Information Manager with the Project Manager (or equivalent) to complete 5.3 (above) and

proceed to 5.4.3

5.4.3 Determine Information Management and Common Data Environment

Strategy Where a collaborative project-based approach is required, the Project Information Manager (or

equivalent) shall ensure an appropriate Common Data Environment (CDE) is in place to allow

information to be shared between all members of the project team. Projects shall manage all (project)

information within the CDE and information within the CDE shall be:

• Named in accordance with the NR Document Referencing Procedure Tagged with standard obligatory metadata

• Reviewed and approved only by persons identified as competent and authorised to do so

• Available to those who are identified in the CDE as being authorised to access information

• Created, approved, maintained and delivered in an appropriate electronic format to its intended use

• Information within the CDE may be tagged with standard optional metadata

The official CDE for Network Rail is the NR BIM CDE.

5.4.4 Determine Team Roles and Responsibilities Throughout each of the procedures defined within the process, the following three key areas of

Information Management remain persistent:

• Information Requirements Management (the ‘what’)

• Information Delivery Management (the ’when’)

OFFICIAL OFFICIAL

• Information Production Management (the ‘how’)

At the NR Region or Route Capital Delivery level, the focus is on the ‘what’ and the ‘how’, whilst at the

project level the focus is on the ‘when’ and ‘how’. This is to ensure our IM and BIM approach is

efficient, cost effective and aligned with our Route requirements. The remit of the team is therefore, is

to gain efficiencies from the improved procurement, production and delivery of information within NR

Regions.

Key Information Area Competencies Associated

Information Requirements Management (the ‘what’)

a. Interpret the requirements for information to meet the

needs of a project

b. Interpret the requirements for information to meet the

needs of a project stakeholder

c. Differentiate between information and technical

requirements

d. Construct a clear acceptance criteria for an information

requirement

e. Validate an information requirement against its cost and

benefit

f. Verify the completeness of information against an

acceptance criteria

g. Manage information requirements within a requirements

management tool

Information Delivery Management (the ‘when’)

h. Program the delivery, review and acceptance of information

within a project schedule

i. Coordinate the delivery, review and acceptance of

information

j. Assess the risk of late delivery to a project schedule

k. Appraise a Contractor’s performance against a project

schedule

l. Evaluate the impact that changes to a project schedule

may have on the delivery of information

Information Production Management (the ‘how’)

m. Assess the standards, methods and procedures required to

support the production of information

n. Examine the information exchanges between an Employer

and Contractor

o. Verify the compliance of information against a set of

standards

p. Evaluate the impact that changes to standards, methods

and/or procedures may have on a contract.

q. Extrapolate a projects functional and non-functional

requirements for information technology to support the

production of information

r. Evaluate information technology against a defined set of

functional and non-functional requirements

OFFICIAL OFFICIAL

The extent to which the competencies need to be applied on a given project, and who is best placed

to undertake the associated tasks, should be determined by the projects value and level of risk. The

risk profile would be aligned with other existing assessments of level of control and level of complexity

on a project, as well as the PIRT output in 5.3 (above).

• For low value / risk projects, it is likely that the respective Project Managers will be responsible for

undertaking the tasks associated to all three functions;

• For medium value / risk projects, the responsibility for undertaking the tasks within each function may

be given to other (existing) project roles, although the accountability would remain with the respective

Project Managers;

• For high value / risk projects, one or more of the functions may be delegated to a dedicated (and

competent) Project Information Manager; although the project roles identified below would retain

responsibility and the respective Project Managers would retain accountability.

Level of

Risk

Information

Management

Function

Employer (NR) Contractor Support

Low

Information

Requirements

Management

Information Manager /

Project Manager

Contractor’s Engineering

Manager

Regional Project

Information

Manager

Information

Delivery

Management

Project Manager Contractor’s Project

Manager

Regional Project

Manager

Information

Production

Management

CAD/BIM/GI/DC Manager

(NR)

CAD/BIM/GI/DC

Manager (Contractor)

Regional Project

Information

Manager

Medium

Information

Requirements

Management

Information Manager /

Project Manager

Contractor’s Engineering

Manager

Regional Project

Information

Manager

Information

Delivery

Management

Project Manager Contractor’s Project

Manager

Regional Project

Manager

Information

Production

Management

CAD/BIM/GI/DC Manager

(NR)

CAD/BIM/GI/DC

Manager (Contractor)

Regional Project

Information

Manager

High

Information

Requirements

Management

Project Information

Manager (PIM)

Contractor’s

Information Manager

(CIM)

Regional Project

Information

Manager

Information

Delivery

Management

Project Information

Manager (PIM)

Contractor’s

Information Manager

(CIM)

Regional Project

Information

Manager

Information

Production

Management

Project Information Manager

(PIM)

Contractor’s Information Manager (CIM)

Regional Project

Information

Manager

For single projects, the Project Information Manager role is normally undertaken by the Lead

Consultant. However, dependent on complexity and scale of the delivery, with multiple projects and

OFFICIAL OFFICIAL

programmes, and a business that requires a measurable level of quality, consistency and

standardisation, then this role is undertaken by a discipline specific Engineer or Information Manager

(BIM lead, Document Control Managers, CAD Managers and/or GIS Managers). Network Rail have

defined that the Project Information Manager’s role is to provide skilled and capable resources to

projects that require it, supporting the drive to improve information management, modelling and

quality.

5.4.5 Determine the BIM, GIS and AIS Strategy The Project Information Manager with the Project Manager (or equivalent) shall determine the Asset

Information Specifications by using NR/L2/ADG/003 to define the Asset Information Requirements.

The Asset Data Exchange Plan (ADEP) standard NR/L2/ADG/003 includes a recommended flowchart

of data related tasks and those responsible. A project shall conduct a review of existing and current

practices within the route, against these standards, to identify the gaps or differences.

A project shall use a risk based approach established on the asset information available and gaps / differences

within NR/L2/ADG/003 and decide upon appropriate and proportionate mitigation measures.

A project shall use a risk-based approach to determine where Geographic Information Systems (GIS) could

add value/provide efficiencies and, decide on appropriate and proportionate mitigation measures.

A project shall input to a BIM4NRP Benefit(s) and Missed Opportunities Impact register. The register

shall include the programme / project details, dates, nature of the benefit or missed opportunity, the

benefit impact i.e. risk mitigation, safety, times, quality, cost, the cost saving and, raking (high,

medium or low).

5.4.6 Determine the Built Asset Security Strategy Asset security is defined at a Corporate level in Network Rail, therefore compliance to the security

standards is essential. NR/L2/INF/02242 Information Security Manual.

• Information it creates

• Information the project is given (asset records, third party information etc)

• Support information e.g. user accounts etc that contain personal information

• Therefore, a project shall complete the following: -

1. Assess the security risk to the built asset

2. Decide on appropriate and proportionate mitigation measures

3. Implement appropriate and proportionate NR policies, processes and procedures

Further Information

PAS 1192-5:2015 - Specification for security-minded building information modelling, digital built

environments and smart asset management

BS EN ISO 19650-5 – Organization and digitization of information about buildings and civil

engineering works, including building information modelling (BIM) — Information management using

building information modelling - Part 5: Security-minded approach to information management.

Key things to consider

• Apply a Security Triage Process (see the PAS 1192-5:2015, soon to be replaced by BS EN

ISO 19650-5)

• Develop a Built Asset Security Management Plan (BASMP), including a security Breach /

Incident Management Plan (SB/IMP)

OFFICIAL OFFICIAL

• Develop on enforce Built Asset Security Information Requirements (BASIR)

5.4.7 Complete Sponsors Handbook Steps For Early GRIP Stages

The Project Manager in conjunction with the Sponsor shall implement a robust procurement strategy

which shall define the on-boarding of Contractors. Attention should be given to testing, commissioning

and entry into service, training and handover documentation and consideration of an aftercare period,

for high risk deliverables.

5.4.8 Follow GRIP / IELCP Process Maps Collectively, the project management team which could include the following roles (or equivalent)

shall use the Network Rail Plan of Work GRIP Stage Gate and Engineering Lifecycle IELCP Phase

Gate process

• Project Information Manager

• Designated Project Engineer

• Project Delivery Manager,

• Design Construction Lead,

• Commercial Manager

• Project Control Manager

• Project Manager.

The BIM4NRP process supports and feeds into both.

5.4.9 Update GRIP Stage Gate The Project Manager and Sponsor shall undertake the GRIP Stage Gate Checklist. The checklist

items shall be loaded into the CDE.

5.4.10 Update IELCP Phase Gate The Designated Project Engineer shall use the Integrated Engineering Lifecycle for Projects Phase A

information to understand the relationship between the engineering activities in order to document the

change to the railway infrastructure / system.

5.4.11 Complete the BIM4NRP GRIP Stage 1 Checklist The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

review the BIM4NRP GRIP Stage 1 / IELCP Phase A Checklists to ensure all relevant items have

been undertaken. The Checklist itself shall be loaded into the CDE as a record of what was done, and

the checklist deliverables, where applicable, shall also be loaded into the CDE as evidence of what

was done. See BIM4NRP Checklist.

OFFICIAL OFFICIAL

5.5 GRIP Stages 2-3 The project shall determine as part of the activities for this stage, what information it needs to

realise successful outcomes and how BIM4NRP can support / facilitate the Contractor Procurement

process.

5.5.1 Start The BIM4NRP process for GRIP Stages 2-3 starts here.

5.5.2 Review BIM4NRP Checklist from the Previous Stage The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP 1 checklist to assess what steps and activities they need to complete. See

BIM4NRP Checklist.

5.5.3 Validate Project Information Requirements The Project Information Manager with the Project Manager (or equivalent roles)shall check the output

of the Employers Information Requirements to ensure the information requirements are still valid.

5.5.4 Create Employer Information Model The Project Information Manager and Project Manager (or equivalent roles) shall follow

NR/L3/MTC/089 (links to NR standards)

• Where possible information will be handed over, processed and handed back in an appropriate

digital format, to the agreed specification

• There are data requirements included in accordance with the ADEP Standard, within the

projects Route Requirement Document (RRD), in addition to the performance requirements

OFFICIAL OFFICIAL

• Any changes made to information requirements associated with the finalised AIS, shall be

proposed by the Route and the cost implications quantified and agreed with a project, before

any amendment to an EIR document is made

• Any time factors related to the Information shall be identified, such as the date at which

information has been produced, and any time constraints on its use

• Enough information metadata shall be provided in line with the AIS.

5.5.5 Create Employer’s Information Requirements

The Project Information Manager with the Project Manager and Designated Project Engineer (or

equivalent roles) shall produce and maintain an Employers Information Requirements (EIR) document

detailing the information requirements for the project, prior to contracting at the end of GRIP Stage 3

but preferably before the end of GRIP Stage 2.

The EIR shall be developed with use of the BIM4NR Project Information Requirements Tool and

contain only the information requirements listed in the CR-T Module 2 Building Information Modelling

CR-T/M2/SY/04, which have been defined as required by the project. For project specific information

requirements, the contents of the EIR shall mirror the contents of the CR-T Module 1 Building

Information Modelling document.

Contract Requirements Technical (CR-T) Module 1 – Project Specific Requirements

Module 2 – Standard Contract Requirements

5.5.6 Determine Project Technology and Systems Integration The Project Information Manager, Project Manager and Designated Project Engineer should focus on

the stage deliverables and outcomes from the BIM4NRP process, and for the Contractors to use the

CDE for its intended purpose.

5.5.7 Review Team Roles and Responsibilities The Project Information Manager and Project Manager (or equivalent roles) shall review the team and

information management Roles and Responsibilities and the projects responsibility matrix required for

the delivery of this GRIP Stage, considering the recommendations included in the PIRT output.

5.5.8 Produce BIM Contract Requirements - Technical BIM4NRP requirements shall be addressed in the design appointment and contracts; Employers

Information Requirements (EIR) shall be developed prior to contracting, at any GRIP Stage, which

establishes information to be delivered and the standards and processes the Contractor should adopt.

• CR-T Requirements CR-T/M2/SY/04

• Employers Information Requirements (made up from PIRT output)

• CIC BIM Protocol

• Pre- and Post-Contract BIM Execution Plan (BEP)

5.5.9 Assess Supply Chain Capacity and Capability The Project Delivery Manager and Design Construction Lead in conjunction with the Project Manager

(or equivalent roles) shall ascertain and understand Contractors information management approach,

capability, capacity and competence, from all appropriate organisations within the Delivery Team. The

capability assessment will incorporate the:

• Contractor BIM Competence Assessment Form to provide a meaningful method of assessing

a Contractor BIM competence, understanding and maturity.

OFFICIAL OFFICIAL

• Contractor Information Technology (IT) Assessment Form, undertaken by all appropriate

organisations in the supply chain to demonstrate their information exchange capability and IT

maturity.

• Contractor Resource Assessment Form used to assess an organisations current resource

capability and capacity.

5.5.10 Update GRIP Stage Gate The Project Information Manager and Project Manager (or equivalent roles) shall undertake a review

the GRIP Stage Gate Checklist. The GRIP Stage Gate Checklist items shall be loaded into the CDE.

5.5.11 Update IELCP Phase Gate The Designated Project Engineer shall use the IELCP phase B information to understand the

relationship between the engineering activities in order to develop various technical options to meet

the Employer Requirements Document.

5.5.12 Complete BIM4NRP GRIP Stages 2-3 Checklist The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

review the BIM4NRP GRIP Stages 2-3 / IELCP Phase B-C Checklists to ensure all relevant items

have been undertaken. The Checklist itself shall be loaded into the CDE as a record of what was

done, and the checklist deliverables, where applicable, shall also be loaded into the CDE as evidence

of what was done. See BIM4NRP Checklist.

OFFICIAL OFFICIAL

5.6 GRIP Stage 4 At this stage of the project there is a clear focus on a preferred design option used to support the

business case. Any models for the preferred design will be dimensionally correct and deliver the

required outcomes set out within the brief. The model can be used for initial analysis and any early

contractor engagement on programme and construction methodology.

5.6.1 Start The process for GRIP Stage 4 starts here.

5.6.2 Review BIM4NRP Checklist from Previous Stage The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP Stages 2-3 Checklist to assess what steps and activities they need to complete. See

BIM4NRP Checklist.

5.6.3 Validate Project Information Requirements The Project Information Manager with the Project Manager (or equivalent roles) shall check the

output of the BIM4NRP Project Information Requirements Tool to ensure the information

requirements are still valid.

5.6.4 Supply Chain BIM Execution Plan (Pre-Contract) The Design Construction Lead and Project Delivery Manager (or equivalent roles) require the

Contractor (on behalf of their supply chain) to produce;

• a BIM Execution Plan (BEP) detailing how the Information Requirements shall be met; to

explain how the information modelling aspects of the project will be carried out and confirm

the Contractor’s proposed task teams have the capability and capacity to meet the

requirements. NOTE: The BEP details Project team roles and responsibilities, Standards,

methods and procedures

• Produce and maintain resourced Task Information Delivery Plan (TIDP) aligned to the project

programme

OFFICIAL OFFICIAL

• Produce information in a suitable data exchange format to minimise data exchange effort and

risk.

• Ensure that designs (irrespective of discipline) shall be produced in a format which allows for

continual multi-disciplinary review in a digital information model.

• Identify the intended or permitted use of information in the metadata.

For Information Models in particular, there are two tasks that are fundamental in minimising the

potential waste produced throughout the appointment. These are:

1. Establishing the proposed Level of Definition

2. Establishing the proposed Volume Strategy.

Both tasks are relatively new to the construction industry and it will take time for Contractors to

develop the capability of undertaking them.

5.6.5 Prepare MIDP, TIDP and Responsibility Matrix Following a contract award, it is important that there is clarity of roles, responsibilities, and authority

for effective information management.

• Models

• Drawings or renditions

• Specifications

The Contractor Design Construction Lead and Project Delivery Manager (or equivalent roles) shall

ensure a TIDP is produced by each task team manager, to provide federated lists of information

deliverables by each task including format, date and responsibilities.

5.6.6 Prepare and Issue BIM Protocol & MPDT The Design Construction Lead and Project Delivery Manager (or equivalent roles) shall prepare and

incorporate the CIC BIM Protocol to their contract/appointment documentation.

5.6.7 Determine and Implement PIM Data Exchanges and Validation The Design Construction Lead and Project Delivery Manager (or equivalent roles) shall define data

exchange points where the Contractor will use the CDE to deliver, through information exchanges,

the required information deliverables.

5.6.8 Update GRIP Stage Gate The Project Information Manager and Project Manager (or equivalent roles) shall undertake the GRIP

Stage Gate Checklist. The GRIP Stage Gate Checklist items shall be loaded into the CDE.

5.6.9 Update IELCP Phase Gate The Designated Project Engineer shall use the IELCP Phase D information to understand the

relationship between the engineering activities in order to develop the design further to a level of

detail that allows the Detailed Route Requirements Document to be developed.

5.6.10 Complete BIM4NRP GRIP Stage 4 Checklist The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

review the BIM4NRP GRIP Stage 4 / IELCP Phase D Checklists to ensure all relevant items have

been undertaken. The Checklist itself shall be loaded into the CDE as a record of what was done, and

the checklist deliverables, where applicable, shall also be loaded into the CDE as evidence of what

was done. See BIM4NRP Checklist.

OFFICIAL OFFICIAL

5.7 GRIP Stage 5 During this stage, the designs and models will now be further refined to provide technical definition of

the project and the level of definition produce.

5.7.1 Start The process for GRIP Stage 5 starts here.

5.7.2 Review BIM4NRP Checklist from t Previous GRIP Stage The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP Stage 4 Checklist to assess what steps and activities they need to complete. See

BIM4NRP Checklist.

5.7.3 Validate Project Information Requirements The Project Information Manager with the Project Manager (or equivalent roles) shall check the output

of the BIM4NRP Project Information Requirements Tool to ensure the information requirements are

still valid.

5.7.4 Supply Chain BIM Execution Plan (Post-Contract) The Contractor Design Construction Lead and Project Delivery Manager (or equivalent roles) shall re-

submit their BEP to show all relevant parties have agreed and committed to the post-contract BEP.

The post-contract BEP will develop in detail over time as more members of the supply chain are

appointed. It should include:

• A response to the requirements of the Employers Information Requirements

• Revised Project Implementation Plan

• Project Responsibility Matrix

• Details of Management Planning and documentation

OFFICIAL OFFICIAL

• Methods and Procedures

• A Task Information Delivery Plan (TIDP) Template

• A Master Information Delivery Plan (MIDP) Template

5.7.5 Undertake Model Review at IDC/IDR Meetings The Design Construction Lead and Project Delivery Manager (or equivalent roles) shall ensure there

are regular reviews of models and associated stage deliverables. At a minimum, this shall be as

required by NR/L2/INI/02009, though regular reviews are encouraged.

5.7.6 Review MIDP and TIDP Progress The Design Construction Lead, and Project Delivery Manager in conjunction with Project Information

Manager and Project Manager (or equivalent roles) shall review progress on the Master Information

Delivery Plan (MIDP) and Task Information Delivery Plan (TIDP)

5.7.7 Review BIM Protocol & MPDT The Design Construction Lead and Project Delivery Manager in conjunction with the Project

Information Manager (or equivalent roles) shall review and update the MPDT.

5.7.8 Review PIM Data Exchanges and Validation The Design Construction Lead and Project Delivery Manager in conjunction with the Project

Information Manager (or equivalent roles) shall ensure that information exchange and validation

(including structure, format and content) is being undertaken, at the agreed handover points, for the

graduated handover of project deliverables, data and information.

5.7.9 Update GRIP Stage Gate The Project Information Manager and Project Manager(or equivalent roles) shall undertake the GRIP

Stage Gate Checklist. The GRIP Stage Gate Checklist items shall be loaded into the CDE.

5.7.10 Update IELCP Phase Gate The Designated Project Engineer shall use the IELCP Phase E information to understand the

relationship between the engineering activities in order to develop the design further to a level of

detail that allows the construction / installation of the railway change.

5.7.11 Complete BIM4NRP GRIP Stage 5 Checklist The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

review the BIM4NRP GRIP Stage 5 / IELCP Phase E Checklists to ensure all relevant items have

been undertaken. The Checklist itself shall be loaded into the CDE as a record of what was done, and

the checklist deliverables, where applicable, shall also be loaded into the CDE as evidence of what

was done. See BIM4NRP Checklist.

OFFICIAL OFFICIAL

5.8 GRIP Stage 6 A key objective of this stage is to ensure “As constructed” models, data and documentation is

delivered especially the capturing of operation and maintenance data from manufacturers.

5.8.1 Start The process for GRIP Stage 6 starts here.

5.8.2 Review BIM4NRP Checklist from t Previous Stage The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP 5 checklist to assess what steps and activities they need to complete. See BIM4NRP

Checklist.

5.8.3 Validate Project Information Requirements The Project Information Manager with the Project Manager (or equivalent roles) shall check the output

of the BIM4NRP Project Information Requirements Tool to ensure the information requirements are

still valid.

5.8.4 Undertake Model Review at IDC/IDR Meetings The Design Construction Lead and Project Delivery Manager (or equivalent roles) shall ensure there

are regular reviews of models and associated stage deliverables.

5.8.5 Review PIM Data Exchanges and Validation The Design Construction Lead and Project Delivery Manager in conjunction with the Project

Information Manager (or equivalent roles) shall ensure that information exchange and validation

(including structure, format and content) is being undertaken, at the agreed handover points, for the

graduated handover of project deliverables, data and information.

OFFICIAL OFFICIAL

5.8.6 Update GRIP Stage Gate The Project Information Manager and Project Manager (or equivalent roles) shall undertake the GRIP

Stage Gate Checklist. The checklist items shall be loaded into the CDE.

5.8.7 Update IELCP Phase Gate The Designated Project Engineer shall use the IELCP Phase E information to understand the

relationship between the engineering activities in order to develop the design further to a level of

detail that allows the construction / installation of the railway change.

5.8.8 Complete BIM4NRP GRIP Stage 6 Checklist The Project Information Manager in conjunction with the Project Manager (or equivalent roles) shall

review the BIM4NRP GRIP Stage 6 / IELCP Phase F Checklists to ensure all relevant items have

been undertaken. The Checklist itself shall be loaded into the CDE as a record of what was done, and

the checklist deliverables, where applicable, shall also be loaded into the CDE as evidence of what

was done. See BIM4NRP Checklist.

OFFICIAL OFFICIAL

5.9 GRIP Stages 7-8 This stage describes the activities associated with, handover of the asset including, updating ‘as

constructed’ information, commissioning, and training. All information necessary for Soft Landings

activities should be completed and the Asset Owner / Maintainer briefed and or trained in any

operational requirements.

5.9.1 Start The process for GRIP Stages 7-8 starts here.

5.9.2 Review Checklist from Previous Stage The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP Stage 6 checklist to assess what steps and activities they need to complete. See

BIM4NRP Checklist.

5.9.3 Validate Project Information Requirements The Project Information Manager with the Project Manager (or equivalent roles) shall check the output

of the BIM4NRP Project Information Requirements Tool to ensure the information requirements are

still valid.

5.9.4 Complete Sponsors Handbook Steps The Sponsor shall review the applicable process steps for the stage to assess what activities they

need to complete in accordance with the Sponsor’s Handbook (NR/GN/INI/P3M/150) and Network

Rail requirements (NR/L2/INI/P3M/104).

5.9.5 Data Transfer to Asset Information Management / Custodian Projects shall only be deemed to be complete when all the new, changed or removed assets and the

information relating to them, have been delivered.

OFFICIAL OFFICIAL

5.9.6 Transmit Source Records / As-Built to NRG

5.9.7 Transmit Health & Safety File / Technical File to Custodian / Owner Once As-Constructed / As-Built records have been accepted, the Project Information Manager and

Project Manager (or equivalent roles) shall return the Health & Safety (H&S) File to NRG as defined in

the Health and Safety File

5.9.8 Update GRIP Stage Gate The Project Information Manager and Project Manager (or equivalent roles) shall undertake GRIP

Stage Gate Checklist. The GRIP Stage Gate Checklist items shall be loaded into the CDE.

5.9.9 Update IELCP Phase Gate The Designated Project Engineer shall use the IELCP Phase F information to understand the

relationship between the engineering activities in order to construct / fabricate / install the railway

change. Testing activities are undertaken to confirm that the construction meets the design, and the

assets are commissioned and brought into service.

5.9.10 Complete BIM4NRP GRIP Stages 7-8 Checklists The Project Information Manager and Project Manager (or equivalent roles) shall review the

BIM4NRP GRIP Stages 7-8 / IELCP Phase F Checklists to ensure all relevant items have been

undertaken. The Checklist itself shall be loaded into the CDE as a record of what was done, and the

checklist deliverables, where applicable, shall also be loaded into the CDE as evidence of what was

done. See BIM4NRP Checklist.

5.10 Finish The process typically finishes when a GRIP based project is closed.

OFFICIAL OFFICIAL

6 Metrics and Assurance

6.1 What is being measured?

6.2 Metric Categories

Type Measure / Metric / Assurance / Verification Red Amber Green

1 Number of CP6 Projects that have defined their Project Information Requirements using the PIRT. Assurance of the above metric will be achieved by extracting the relevant information from the PIRT tool.

< 80% 81% -

98%

> 98%

2 Number of CP6 Projects that have defined Employers Information Requirements within their contracts. Assurance of the above metric will be achieved by extracting the relevant information from the Projects.

< 80% 81% -

98%

> 98%

2 Number of CP6 Projects that have completed a GRIP 4 checklist. Assurance of the above metric will be achieved by extracting the relevant information from the Projects.

< 80% 90% -

98%

> 98%

OFFICIAL OFFICIAL

7 Continuous Improvement The following know gaps have been identified as priority areas for continuous improvement

ID Section Action Priority By Whom? By

When?

1 5.2 Develop BIM4NRP Dashboard on NR BIM Portal

High BIM4NRP Programme

Q3 2019

2 5.3 Develop BIM4NRP Project Information Requirements Tool (PIRT) on NR BIM Portal

High BIM4NRP

Programme

Q3 2019

3 5.6.6 Prepare BIM4NRP Protocol & MPDT template

High BIM4NRP

Programme

July 2019

4 5.4.8 A complete review of all GRIP Products will also need to be undertaken to align the existing products with the new Information Management products, to ensure that there is no duplication or omissions

Medium BIM DRG GRIP DRG IELCP DRG

Q2 2020

5 5.4.8 BIM4NRP will need to be integrated with GRIP and IELCP processes

Medium BIM DRG GRIP DRG IELCP DRG

Q2 2020

6 5.5.7 Prepare Responsibility Matrix High BIM4NRP

Programme

July 2019

7 5.5.8 Prepare Information Management Services

High BIM4NRP

Programme

July 2019