scope:

2.1 Types of Assets

This business process applies to the following types of Network Rail assets:

NOTE 1: These assets are otherwise known as Buildings & Civils (B&C) infrastructure and are defined in NR/L1/CIV/001.

a) structures;

b) buildings;

c) tunnels and mines (mineral workings);

d) earthworks;

e) drainage;

f) building services;

g) lineside (excluding vegetation / trees)

h) buildings and civils type elements or components of other assets.

NOTE 2: The types of assets listed might include architectural aspects.

2.2 Types of Works

This business process applies to the following types of proposed or actual works when undertaken on buildings and civils infrastructure that is owned, or is to be owned, by Network Rail:

a) enhancements;

b) replacements;

c) renewals;

d) repair works;

e) emergency works;

f) temporary works:

1) to mitigate the impact of temporary conditions created as part of the permanent works;

2) to facilitate the construction of permanent works or staged construction;

3) to provide access for examination and inspection.

NOTE: Where NR standard designs are used, this standard should be read in conjunction with NR/L3/CIV/151 Application of Standard Designs and Details for Building and Civil Engineering Works

2.3 External Party Assets

This business process applies to External Party Buildings and Civils infrastructure where either:

a) Works are undertaken by Network Rail; or

b) the External Party infrastructure is:

1) on, over, under or adjacent to Network Rail's infrastructure; and

2) the External Party does not have an equivalent engineering assurance procedure to NR/L2/CIV/003 for those Works; and

3) all works follow the requirements attributed to Outside and Third-Party Projects under NR/L2/CIV/095 & NR/L2/CIV/096.

Network Rail has no power to enforce the requirements of this business process on Works undertaken on External Party infrastructure which lies entirely outside Network Rail's property boundary, except through legal agreement, whether or not such Works could affect railway operations.

For such Works, reasonable endeavours can be followed to apply the requirements of this business process or to obtain confirmation from the External Party that an equivalent procedure to that shown in Section 5 is in place.

Where an External Party decides to adopt the requirements of this business process, it is acceptable to use modified versions of the forms associated with this business process. For example, not following references to PACE.

NOTE 1: This business process applies to External Party works managed through the Asset Protection Framework and the Landlord's Consent process.

NOTE 2: The procedure defined in the Design Manual for Roads and Bridges (DMRB) 'Technical Approval of Highway Structures' (CG 300) is considered to be equivalent where amended to include railway aspects from Form A

2.4 Application

This business process applies to Network Rail and non-Network Rail personnel involved in the remitting, design, checking, design assurance, construction assurance and taking into use of Buildings and Civils infrastructure.

2.5 Exclusions

This business process does not apply to:

a) consents or approvals from bodies outside Network Rail including:

1) regulatory and statutory authorities;

2) planning, listed building and conservation authorities;

3) environmental regulators;

4) land and property owners or leaseholders;

5) statutory undertakers and other public services and utilities owners;

b) obtaining approvals for the New Roads and Street Works Act;

c) obtaining approval from other Network Rail engineering disciplines for the equipment carried by Equipment Support Structures or for the performance of that equipment;

NOTE 1: For Example, signal sighting and reduced clearances.

d) assessments of structures;

e) obtaining acceptance of engineering deliverables for a project to achieve Approved for Construction status, without fulfilling the additional requirements as set out in NR/L2/RSE/02009; and,

NOTE 2; Refer to NR/L2/RSE/02009 for requirements to obtain acceptance of engineering deliverables for a project to achieve Approved for Construction status,

f) work delivered in compliance with NR/L3/OHS/005 that does not fall within the scope of NR/L2/RSE/02009

Purpose

This business process sets out:

a) the Technical Approval of works covering Buildings, Civils and Architecture, as part of the requirements detailed in NR/L2/RSE/02009; and

b) Entry into (Operational) Service (EIS) requirements for such works. This engineering and architectural assurance process is a method of consistently verifying that Building and Civil Engineering infrastructure designs:

1) meet client, project and stakeholder requirements;

2) are suitable in terms of:

• safety;

• security;

• constructability;

• functionality;

• appearance and other architectural aspects;

• planning conditions & requirements;

• heritage requirements;

• spatial capacity;

• human factors / ergonomics;

• wayfinding and navigation;

• accessibility;

• maintainability;

• sustainability, including sustaining the condition or operational serviceability of an asset over time.

• environmental sustainability, including decarbonisation and social value.

• specification;

• cost;

• decommissioning; and

• demolition.

Quality design, checking, execution and assurance is critical to controlling business and safety risks and opportunities throughout the asset lifecycle.

The processes described in this document support the Engineering Management processes detailed in NR/L2/RSE/02009. They also support the Project Acceleration in a Controlled Environment requirements set out in NR/L2/P3M/201, where PACE applies.