interim advice note 165/12 managed motorways ...€¦ · interim advice note 165/12 managed...

Interim Advice Note 165/12 Managed Motorways- Commissioning and Handover Guidance

IAN 165/12 of 62 Apr 2012

INTERIM ADVICE NOTE 165/12

MANAGED MOTORWAYS - COMMISSIONING AND HANDOVER GUIDANCE

Summary This document provides advice on the process, requirements, and maintenance liabilities associated with the commissioning and handover of managed motorway schemes.

Instructions for Use This document applies to all managed motorway schemes. It is to be used by all those responsible for the delivery of, and involved in, the commissioning and handover of the scheme.


IAN 165/12 of 62 Apr 2012

[This page has been intentionally left blank]


IAN 165/12 of 62 Apr 2012

Table of Contents 1. About this Document ............................................................................................5

1.1 Introduction ...........................................................................................................5 1.2 Purpose ................................................................................................................5 1.3 Who is this Guidance for?.....................................................................................6 1.4 Relationship to other HA Documents....................................................................6 1.5 Status of this document ........................................................................................6 1.6 Further Support.....................................................................................................6

2. Delivery of a Managed Motorway Scheme ...........................................................7

2.1 Key Policies and Principles...................................................................................7 2.2 Roles and Responsibilities....................................................................................7 2.3 Managed Motorway Lifecycle ...............................................................................8 2.4 Commissioning and Handover..............................................................................9 2.5 Maintenance .........................................................................................................9

3. Commissioning and Handover Period ................................................................10

4. System Commissioning and Operational Regime Testing .................................11

4.1 System Commissioning ......................................................................................11 4.1.1 RCC Readiness ..................................................................................................11

4.2 Operational Regime Testing ...............................................................................12 4.2.1 Approach One – Include Variable Advisory Speed Limit Stage..........................12

4.2.2 Approach Two – Exclude Variable Advisory Speed Limit Stage ........................13

4.3 Manual / Automatic Setting of Signals ................................................................15 5. Managing and Documenting Stage Completion Requirements..........................17

5.1 Stage Transition Criteria .....................................................................................17 5.2 Consent to Implement.........................................................................................17

6. Traffic Management Milestones..........................................................................18

7. Timescales for Commissioning and Handover ...................................................19

8. Maintenance during the Lifecycle of a Managed Motorway Scheme .................21

8.1 During Stages A - C: Maintenance during Construction .....................................22 8.2 During Stages D - F: Interim Scheme Specific Maintenance..............................23 8.3 During Stage G: Handover to HA for Operational Maintenance .........................23 8.3.1 Maintenance Handover Procedure .....................................................................24 8.4 Required level of Maintenance ...........................................................................25 8.4.1 Changes to HA Maintenance Contracts .............................................................26 8.5 Selection of Maintenance Service Provider ........................................................26


IAN 165/12 of 62 Apr 2012

9. Requirements for Scheme Handover .................................................................27

9.1 Criteria for handover of Civil Infrastructure into Maintenance.............................27

9.2 Criteria for handover of Technology Infrastructure and Equipment into Maintenance .......................................................................................................28

9.3 Criteria for Operational handover .......................................................................28 9.4 Outstanding Defects and Faults .........................................................................29 9.5 Defects Liability...................................................................................................29 9.6 Post Opening Optimisation .................................................................................29 9.7 Project Closeout .................................................................................................30

10. Variations that impact the Commissioning and Handover Process ....................31

10.1 Phased / Sectional Construction and Completion of Schemes ..........................31 10.2 Commissioning and Handover of a Controlled All Lane Running Scheme or

Managed Motorway All Lane Running Scheme..................................................31

Appendices

Appendix 1 – Glossary .......................................................................................................33 Appendix 2 – Roles and Responsibilities related to Commissioning & Handover..............37 Appendix 3 – Local Commissioning and Systems Commissioning ....................................47 Appendix 4 – Stage Completion Requirements..................................................................51 Appendix 5 – Mapping of MM Lifecycle to PCF Stages & CTI ...........................................55 Appendix 6 – Stage Transition Criteria and the use of CTI ................................................57

List of Figures

Figure 1 - Lifecycle of a Managed Motorway Scheme.........................................................8 Figure 2 - Commissioning and Handover period ...............................................................10 Figure 3 - Local and System Commissioning ....................................................................11 Figure 4 - Operational Regime Testing - includes VASL, proceed to VMSL and then

HSR trials..........................................................................................................13 Figure 5 - Operational Regime Testing - Skip VASL, proceed to VMSL and then

HSR trials..........................................................................................................14 Figure 6 - Manual / Automatic setting of Signals ...............................................................16 Figure 7 - Maintenance over the lifecycle of a Managed Motorway Scheme ....................22 Figure 8 - Phased / Sectional Construction and Completion of Schemes .........................31 Figure 9 - Lifecycle of the CALR or MM-ALR Scheme ......................................................32

List of Tables

Table 1 - Lifecycle of a Managed Motorway Scheme..........................................................8 Table 2 - Traffic Management Milestones .........................................................................18 Table 3 - Maintenance Specification..................................................................................25


IAN 165/12 of 62 Apr 2012

1. About this Document 1.1 Introduction The delivery of a managed motorway scheme is relatively complex when compared to previous road construction or widening schemes. This is because it is delivered across a number of distinct activity areas in the Highways Agency - namely Construction, Technology, Operations and Maintenance. Engagement across these functional areas is imperative to ensure that a fit for purpose product is delivered, enabling it to be successfully handed over into operations and maintenance. Commissioning and handover have to be considered in the widest context and throughout the delivery lifecycle of a managed motorway scheme. Although knowledge about the commissioning and handover process is generally high within the managed motorway community, it is inconsistent, something which has led to implementation teams approaching the process in a number of ways. This document aims to provide a consistent, controlled, and best practice approach for all managed motorways schemes. 1.2 Purpose The purpose of this document is to provide a framework within which the Contractor delivering the scheme on behalf of Major Projects should approach commissioning and handover and set up maintenance activities in support of it. This document aims to:

1. Inform the managed motorway community of the policies and principles

under which commissioning and handover should be undertaken; 2. Set out the processes involved in the commissioning and handover of a

managed motorway scheme; 3. Provide governance and control criteria for delivery and handover: 4. Set out the maintenance liabilities and requirements for a managed

motorway scheme; 5. Clarify the roles and responsibilities of parties involved throughout the

commissioning and handover process; and, 6. Define the requirements that need to be achieved in order to

successfully achieve handover and set out how the handover of the scheme should be managed.


IAN 165/12 of 62 Apr 2012

1.3 Who is this Guidance for? This document and its requirements must be used and followed by all those tasked with delivering managed motorway schemes. This is primarily the Contractor delivering the scheme on behalf of Major Projects. The requirements herein shall also be followed by all stakeholders integral to the acceptance (into maintenance and operation) of managed motorway schemes. These include, but are not limited to, Senior Users, Service Delivery Managers, the Maintenance Community, and Operational Managers. 1.4 Relationship to other HA Documents The commissioning and handover process is governed and supported by a wide range of formal documentation. Much of this documentation falls into one of three groups:

1. Guidance on the technology commissioning and handover process - MCH document suite;

2. Standards on the handover of Civil infrastructure - DMRB Volumes; and, 3. Governance of the civil, technology and operational handover process -

Project Control Framework (PCF) Products.

Where necessary, these documents are referenced and their applicability is discussed. 1.5 Status of this document The key policies and principles that are set out in this document and underpin the commissioning and handover of managed motorway schemes have been formally approved by both the Roads Programme Steering Group (RPSG) (formally Managed Motorway Steering Group) and Managed Motorways Operations Management Board (MMOMB). This document enables schemes to include its content and methodology in developing delivery plans, target costing and preparing associated Project Control Framework documents. 1.6 Further Support It is advised that at the time of developing a target cost and agreeing a handover plan, contact is made with Highways Agency Delivery Hub Operations team ([email protected]) who will be able to advise further on the items discussed in this document and ensure that queries are forwarded to the appropriate specialist. Any questions or feedback regarding this document shall be directed to the Standards_Feedback&[email protected]


IAN 165/12 of 62 Apr 2012

2. Delivery of a Managed Motorway Scheme 2.1 Key Policies and Principles The key policies and principles impacting a managed motorway scheme are as follows:

1. The Contractor delivering the scheme on behalf of Major Projects shall be responsible for the scheme up until it has been accepted (into maintenance and operation) by Network Delivery and Development Directorate (NDD) and Traffic Management Directorate (TMD).

2. Those responsibilities include all aspects related to the construction,

commissioning, testing (operational regimes), maintenance and handover of the scheme.

3. Unless alternative arrangements are agreed with the NDD Senior User,

throughout the delivery of the scheme, maintenance of existing and new assets (e.g. technology and civil infrastructure) shall be the responsibility of the Contractor delivering the scheme on behalf of Major Projects.

4. A scheme shall only be considered fit for handover and subsequently

accepted into maintenance and operation, when the NDD Senior User is satisfied that all the acceptance criteria and requirements have been successfully achieved by the Contractor delivering the scheme on behalf of Major Projects.

5. Handover shall be governed by the Project Control Framework which

requires the NDD Senior User sign-off of the Civil, Technology and Operational handover certificates in Stage 6 of the PCF lifecycle.

2.2 Roles and Responsibilities The delivery of a managed motorway scheme requires input from multiple stakeholders that are both internal and external to the Agency. These stakeholders are referenced, and their roles and responsibilities explained in the relevant sections of this document. An indicative list of the key stakeholders and their roles and responsibilities is provided within Appendix 2. It is recognised that there will be variances at a scheme and regional level and schemes are encouraged to identify and agree these as early as possible in the delivery process.


IAN 165/12 of 62 Apr 2012

2.3 Managed Motorway Lifecycle This document assumes that the construction, commissioning and handover of a managed motorway scheme is conducted across seven distinct stages, as summarised in Figure 1 and Table 1 below.

A B C D E F G

60Sign under test

Use hard shoulder60?

Pre-works ConstructionOpening of

Scheme with VMSL & HSR / Handover to

Agency

SystemsCommissioning

Hard Shoulder Running

Trials

Variable Mandatory

Speed Limits

Variable Advisory

Speed Limits (optional)

Figure 1 - Lifecycle of a Managed Motorway Scheme

Stage Description

A Pre-works (encompassing all design and approval processes) B Construction (including technology outstation and instation work) C Systems Commissioning (final stage of Site Acceptance Testing, SAT #3) D Manual / Automatic Variable Advisory Speed Limits (optional) E Manual / Automatic Variable Mandatory Speed Limits F Hard Shoulder Running (HSR) Trials G Opens to the Public (fully operational with Hard Shoulder Running); Scheme

handover to the Agency (for maintenance and operation)

Table 1 - Lifecycle of a Managed Motorway Scheme


IAN 165/12 of 62 Apr 2012

2.4 Commissioning and Handover Commissioning and handover is a critically important phase of a scheme that demands detailed planning and collaborative working to ensure the successful delivery of the scheme. In order for the Systems Commissioning, Operational Regime Testing and Handover to be considered as completed, the scheme must have achieved the following milestones:

1. All infrastructure works are complete (by end of Stage B); 2. The required technology systems have been commissioned (during

Stages B and C); 3. The Statutory Instrument (SI) is in place (preferably by end of Stage C;

must be in place prior to start of Stage E); 4. The Regional Control Centre (RCC) is able to operate a managed

motorway scheme with Variable Mandatory Speed Limits (VMSL) & Hard Shoulder Running (HSR) operational (by end of Stage F); and,

5. The NDD Senior User has accepted the scheme in to maintenance and operation (during Stage G).

Once step 4, above, has been achieved, the Agency should be in a position to use all features of the managed motorway scheme, specifically hard shoulder running and variable mandatory speed limits in an operational capacity. As soon as this step has been completed, the Contractor delivering the scheme on behalf of Major Projects should make every effort to complete all requirements associated with the handover of the scheme (see Section 9). Failure to do so will result in a delay to scheme handover, subsequently increasing the costs incurred by the Contractor due to ongoing maintenance and staffing requirements. A managed motorway scheme will only be considered fit for handover back to the Agency (i.e. the completion of step 5 above), once it is in receipt of it’s certificates of completion for Civils, Technology and Operations issued by the NDD Senior User for the scheme. This process is governed by the PCF process via its products related to handover. 2.5 Maintenance The formal handover of a managed motorway scheme occurs at end of the seven stage project lifecycle detailed in Section 2.3. Maintenance of the scheme (by the Contractor) prior to handover, carries particular significance within the context of the commissioning and handover of a managed motorway scheme because the level of technology and civil infrastructure installed is far greater than that of a traditional road construction or widening scheme. This additional infrastructure must be sufficiently maintained to allow the network, on which the scheme is being implemented, to continue to operate safely throughout the Construction, Systems Commissioning (see Section 4.1), Operational Regime Testing (see Section 4.2), and Handover (see Section 8.3 and Section 9) stages.


IAN 165/12 of 62 Apr 2012

3. Commissioning and Handover Period Within the lifecycle of a managed motorway scheme the commissioning and handover period relates to all stages that are delivered post construction in the lead up to handover. Of these stages, the following is noted:

Stage C, Systems Commissioning, is where the roadside equipment testing is undertaken (note: this testing may begin during the latter part of Stage B).

Stage D, the running of Variable Advisory Speed Limits (VASL), is optional. Further details on whether schemes should look to undertake Stage D are contained in Section 4.2.1.

If required, Stage D and Stage E can be split into Manual and Automatic settings. This is further discussed in Section 4.3.

Stage E and Stage F may be run in parallel as they can be tested independently.

Stage G, similar to the other stages, is a period of activity (as opposed to a milestone) during which the scheme can be operated by the RCC while the Contractor delivering the scheme on behalf of Major Projects is progressing the scheme handover tasks.

Stage C through to Stage G in the managed motorway lifecycle is generally referred to as the Commissioning and Handover period, of which Stage D through to Stage F is commonly referred to as Operational Regime Testing.

A B C D E F G

60Sign under test




Agency



Trials

Variable Mandatory

Speed Limits

Variable Advisory


Commissioning and Handover Period

Operational Regime Testing

Figure 2 - Commissioning and Handover period


IAN 165/12 of 62 Apr 2012

4. System Commissioning and Operational Regime Testing 4.1 System Commissioning Following the installation of the technology infrastructure and systems on a managed motorways scheme, they are subject to a series of Site Acceptance Tests (SATs). These provide assurance that the infrastructure and systems have been designed and installed to an acceptable standard and are able to be operated effectively. SAT 1 and SAT 2 make up the local commissioning activities that involve individual or groups of technology devices being tested. These tests are likely to be undertaken towards the end of Stage B (Construction). The final Systems Commissioning (Stage C), referred to as SAT3, is the end-to-end test of the roadside equipment together with the Regional Control Centres (RCC) instation equipment. During SAT3, the device, controller, local cabling, communications links, site data and the operator interface are all tested from the RCC. The activities within SAT1, SAT2 and SAT3 are further detailed in Appendix 3. Figure 3 below provides a graphical illustration of this sequence of SAT activities in the lead up to and during the Systems Commissioning stage.

Local Commissioning

Var

iab

le

Ad

viso

ry

Sp

eed

Li

mits

Har

d

Sho

uld

er

Run

ning

Tr

ials

Op

enin

g o

f S

chem

e w

ith H

SR

/

Han

do

ver

to A

gen

cy

NRTS CablingNRTS end to end testing

SA

T 3

fro

m

RC

C MV

AS

L

HS

R T

rails

(th

is

may

ove

rlap

w

ith E

2

D1 D2 F

SAT 1 and 2 ongoing in parallel CCTV Adjustment

Var

iab

le

Man

dat

ory

S

pee

d

Lim

its

AV

AS

L

E1 E2H

and

ove

r to

H

AG

Op

en to

the

pub

lic

MV

MS

L

AV

MS

LB C D E F G

Sys

tem

s C

om

mis

sio

ning

C

Construction

Man

ual

Man

ual

Aut

o

Aut

o

NRTS Activation

End Operational Regime Testing /

ready for operational use

Start of Operational

Regime Testing

Figure 3 - Local and System Commissioning

4.1.1 RCC Readiness A significant part of the end-to-end testing is dependent on the readiness of the RCC, in terms of upgraded systems capable of controlling the roadside equipment and trained staff able to operate the managed motorway scheme. The Contractor


IAN 165/12 of 62 Apr 2012

delivering the scheme on behalf of Major Projects should work in close liaison with the regional HA Service Delivery Team (SDT), Traffic Technology Division (TTD) and TMD to ensure RCC readiness is progressed in parallel to scheme delivery timelines. 4.2 Operational Regime Testing Experience from the M42 pilot managed motorway scheme and Birmingham Box Phases 1 & 2 schemes suggests that there are two approaches that can be undertaken for Operational Regime Testing. Schemes must ensure that the approach to Operational Regime Testing is agreed regionally between the Scheme, the NDD Senior User and the RCC. 4.2.1 Approach One – Include Variable Advisory Speed Limit Stage All stages of Operational Regime Testing are undertaken, including Stage D, Variable Advisory Speed Limits (VASL), Stage E, Variable Mandatory Speed Limits (VMSL) and Stage F, Hard Shoulder Running (HSR) trials. Issues that may influence the inclusion of VASL include:

1. Level of experience in dealing with Controlled Motorway (CM) conditions by the RCC Operators

The advisory settings may be considered beneficial where the RCC staff have not had the use of variable mandatory speed restrictions on the motorway and as such they might appreciate being introduced gradually to the full MM toolkit including VMSL and HSR.

2. Level of road user exposure to VASL and VMSL in the region

Schemes in areas not accustomed to mandatory signals may wish to use advisory signals first to introduce the concept to the travelling public.

3. Various issues local to the scheme

Such as link-by-link construction, site data load restrictions and other regional constraints.

4. The Statutory Instrument (SI) is not expected to be in place in time for

commencement of VMSL Schemes should look to initiate the process of getting their Statutory

Instrument agreed and adopted well in advance of the undertaking of their Operating Regime Testing. In the event of not having this in place VASL may be used as an interim measure.

Figure 4 provides a pictorial overview of the process for operational regime testing when Variable Advisory Speed Limits are set.


IAN 165/12 of 62 Apr 2012

A B C D E F G

60Sign under test




Agency



Trials

Variable Mandatory

Speed Limits

Variable Advisory


2+ weeks for final end to end testing

Dependent on the reason for operating

under VASL

2+ weeks (generally 2 weekends)

Dependent on Contractor fulfilling its

obligations for handover

4+ wks but can run parallel to Stage F

Milestone:Start of Operational

Regime Testing

Milestone:End of Operational Regime Testing /

Ready for operational use

Milestone:Scheme

Handover Completed

Figure 4 - Operational Regime Testing - includes VASL, proceed to VMSL and

then HSR trials 4.2.2 Approach Two – Exclude Variable Advisory Speed Limit Stage Within this approach VASL is bypassed, the scheme proceeds to VMSL and then HSR trials, after it has completed its system commissioning (Stage C) works. This approach reduces the need for an additional site data load to enable VASL and therefore reduces the time and risk taken to progress from the end of systems commissioning in Stage C to the scheme opening and operating as a fully functioning managed motorway in Stage G. Figure 5 provides a pictorial overview of the process for operational regime testing when Variable Mandatory Speed Limits are set.


IAN 165/12 of 62 Apr 2012

A B C F G

Sign under test?

Pre-works Construction SystemsCommissioning

E

Variable Mandatory

Speed Limits

Use hard shoulder

Opening of Scheme with VMSL & HSR / Handover to

Agency


Trials

60

60

Variable Advisory


SKIP STAGE D

D

2+ weeks for final end to end testing

0 weeks 2+ weeks (generally 2 weekends)

Dependent on Contractor fulfilling its

obligations for handover

4+ wks but can run parallel to Stage F

Milestone:Start of Operational

Regime Testing

Milestone:End of Operational Regime Testing /

Ready for operational use

Milestone:Scheme

Handover Completed

Figure 5 - Operational Regime Testing - Skip VASL, proceed to VMSL and then

HSR trials


IAN 165/12 of 62 Apr 2012

4.3 Manual / Automatic Setting of Signals Stage D, Variable Advisory Speed Limits, and Stage E, Variable Mandatory Speed Limits, may be activated through a period of ‘manual’ and ‘automatic’ setting of the Advanced Motorway Indicator (AMI) signals. Stage D and E can be further split as follows:

1. Stage D a. D1 – Manual Variable Advisory Speed Limits (MVASL) b. D2 – Automatic Variable Advisory Speed Limits (AVASL)

2. Stage E

a. E1 – Manual Variable Mandatory Speed Limits (MVMSL) b. E2 – Automatic Variable Mandatory Speed Limits (AVMSL)

If Approach one is selected for the If Approach One (as detailed in Section 4.2.1) is selected for the Operational Regime Testing phase, thereby including a step with Advisory Speed Limits prior to implementation of Mandatory Speed Limits, all fours settings (D1, D2, E1, E2) must be tested and proven to be working correctly in an operational capacity. If a scheme is going straight to Mandatory Speed Limits (Stage E) as per Approach Two (as detailed in Section 4.2.2), then only E1 and E2 are required. During D1 and/or E1, the controlling RCC may ‘manually’ set any speed or lane control aspect that is deemed appropriate to support their operational need at the time. During D2 and E2, the speed limits are set ‘automatically’ using data from the MIDAS system, effectively implementing MIDAS Queue Protection, Variable Mandatory Speed Limits (Controlled Motorway), or both. The durations for each manual and automatic speed setting stage is wholly dependent on any technical (fine tuning of speed thresholds, changes to speed algorithms etc) and / or operational (comfort level of road users, confidence of RCC operators etc) issues that may require resolution. Figure 6 below provides a graphical illustration of this sequence of activities for Manual and Automatic setting of signals.


IAN 165/12 of 62 Apr 2012

Local Commissioning

Var

iab

le

Ad

viso

ry

Sp

eed

Li

mits

Har

d

Sho

uld

er

Run

ning

Tr

ials

Op

enin

g o

f S

chem

e w

ith H

SR

/

Han

do

ver

to A

gen

cy


SA

T 3

fro

m

RC

C MV

AS

L

HS

R T

rails

(th

is

may

ove

rlap

w

ith E

2

D1 D2 F


Var

iab

le

Man

dat

ory

S

pee

d

Lim

its

AV

AS

L

E1 E2

Han

do

ver t

o

HA

G

Op

en to

the

pub

lic

MV

MS

L

AV

MS

L

B C D E F G

Sys

tem

s C

om

mis

sio

ning

C

Construction

Man

ual

Man

ual

Aut

o

Aut

o

NRTS Activation




Regime Testing

Figure 6 - Manual / Automatic setting of Signals


IAN 165/12 of 62 Apr 2012

5. Managing and Documenting Stage Completion Requirements 5.1 Stage Transition Criteria There are several key activities that need to be completed, and criteria considered, in managing the transition across a stage boundary. These provide a level of control and governance to the transition process and enable all impacted stakeholders to be consulted during a stage or at the time of transition from one stage to another within the managed motorway lifecycle. The key Stage Completion Requirements are provided within Appendix 4. At a minimum these must be adhered to by those delivering the scheme. It is advised that additional requirements based on regional or scheme variations are identified and agreed regionally. Some of these key activities require the production of formal HA documentation (e.g. MCH documents, PCF products etc). The completion of these activities at the appropriate stage will enable the smooth transition to the next stage and ensure that the scheme is delivered to its agreed programme. It should be noted that not all stage transitions are currently subject to a formal control or governance mechanism within approved HA documentation. This is further discussed in Section 5.2 below. 5.2 Consent to Implement In addition to the stage completion requirements and formal documentation discussed above, a process similar to the Consent to Implement (CTI) adopted on the Birmingham Box managed motorway schemes is currently being developed by the Delivery HUB Operations team. CTI provides a formal governance procedure to control the transition between operating regimes going live. In doing so it ensures that the key parties involved in the delivery of the scheme have confirmed that they are content for the scheme to progress to the next stage in the commissioning and handover process. CTI template forms and guidance will be made available to managed motorway schemes in April 2012. -- Figure A5-1 in Appendix 5 provides a tabular representation of how PCF stages and PCF products correlate to the managed motorway lifecycle. Figure A6-1 in Appendix 6 maps out the stage transition criteria and CTI against the PCF process.


IAN 165/12 of 62 Apr 2012

6. Traffic Management Milestones Stage C (and then Stage D) through to Stage F, is the period during which the scheme makes the transition between construction site and operational scheme, as the newly installed technology and systems are commissioned and made available to the RCC. During this period significant changes are made to the provision of Traffic Management (TM).

Table 2 below highlights some of the key TM milestones that are likely to fall within this period. The timing of each is indicative only, as this phase of the project requires liaison and agreement between the Contractor, the RCC, MP and NDD. It is critical that care is taken to avoid conflicts between fixed plate temporary signage, permanent verge and/or gantry signage, and any information displayed on signs and signals during this transitional phase.

Likely Stage

Milestone Pre-requisites

Towards end of Stage C.

Removal of Free Recovery, Temporary CCTV

PTZ CCTV and ERT commissioned and available to RCC

Beginning of Stage D1 or E1

Removal of temporary speed restrictions.

Above plus MVASL or MVMSL available to RCC.

Within Stage D2 or E2

Removal of temporary speed restrictions

Above plus MIDAS loops commissioned, certified and MIDAS Queue Protection algorithm enabled.

Before Stage F Removal of any remaining temporary lane closures, such as at TJR sites.

All of the above

Table 2 - Traffic Management Milestones

Further guidance on this aspect can be obtained through the Delivery HUB (via the following address: [email protected]).


IAN 165/12 of 62 Apr 2012

7. Timescales for Commissioning and Handover Indicative timescales for all stages within the commissioning and handover process are provided below, however it should be noted that the number of stages adopted and the length of each stage will vary between schemes. These variables should be agreed with the NDD Senior User and Regional Operations Board in Stage A (pre-works). Irrespective of the approach chosen for Operational Regime Testing (see Section 4.2), the following time scales shall be considered when scheduling activities related to the commissioning and handover process: 1. Stage C – a duration of at least 2 weeks enables a final full systems test (ie.

SAT 3) within a link (or section). It does not include the soak testing or local commissioning (SAT 1 and SAT 2) - it is assumed these tests and commissioning activities are conducted during the construction phase (Stage B).

2. Stage D – the duration of this stage shall be decided by the scheme as it is

dependent on the reason for adopting VASL. However, given a site data load would be required to enable VASL, it is expected the scheme would run VASLs for a duration of at least 4 weeks. The split between manual and automatic setting of signals will also impact this duration.

3. Stage E – a duration of 4+ weeks provides for sufficient testing of VMSL.

During this period, if VMSL testing is prolonged (due to debugging of speed algorithms, tuning of thresholds etc), it is possible for the HSR trials (Stage F) to be run in parallel with VMSL. The split between manual and automatic setting of signals will also impact this duration.

4. Stage F – experience from the M42 pilot and Birmingham Box Phase 1 & 2

schemes suggests that the HSR trials be carried out at weekends during off-peak (as defined by the RCC) periods. Two successful trials as a minimum should be completed to provide assurance that the technology is working to enable the scheme to be safely operated (ie. HSR system is fully functional and ready to be opened to the public). For planning purposes, the Contractor shall assume that 3 weekends are required for this, two for the tests and one as a contingency. At the end of Stage F, the scheme is ready to go into full operation hence this is considered a key milestone.

5. Stage G – during Stage G, the scheme shall be fully open to traffic with

Operational Regimes available for use by the controlling RCC as required. Handover of the scheme into full operational maintenance shall also take place during this stage. Commencement of operations and handover into maintenance shall take place simultaneously. In practice this may not always be possible because the handover into maintenance is wholly dependent on the Contractor, Maintenance Service Provider(s), and HA Directorates (namely MP, NDD and TMD) fulfilling their obligations for handover. Therefore the length of Stage G cannot be specified and is left for the Contractor


IAN 165/12 of 62 Apr 2012

delivering the scheme on behalf of Major Projects to manage after consultation with those contributing to achieve this milestone.


IAN 165/12 of 62 Apr 2012

8. Maintenance during the Lifecycle of a Managed Motorway Scheme

As per current HA policy, maintenance within a managed motorway scheme is the responsibility of the Contractor delivering the scheme on behalf of Major Projects. All required maintenance activities are to be carried out until such time that the scheme is handed over to NDD and TMD for maintenance and operation. The Contractor needs to make allowance within their target cost for the provision of maintenance within the scheme boundaries. Maintenance of a managed motorway scheme is critically important due to the high density of technology installed and the need to ensure Systems Commissioning and Operating Regime Testing can be successfully carried out. Furthermore, the operational, safety and reputational consequences for the Highways Agency of not being able to operate the scheme due to technology unavailability or insufficient maintenance provision make maintenance during delivery of a scheme particularly important. Due to the evolving nature of the schemes, maintenance requirements vary throughout the lifecycle of a managed motorway scheme. The level of maintenance which must be provided by the Contractor also varies as the scheme progresses through each stage. The rest of this chapter deals with the issue of maintenance over the lifecycle of a managed motorway scheme. As shown in Error! Reference source not found., and for ease of discussion, maintenance requirements are grouped as follows:

1. During Stages A – C: Maintenance during Construction 2. During Stages D – F: Interim Scheme Specific Maintenance 3. During Stage G: Handover to HA for Operational Maintenance


IAN 165/12 of 62 Apr 2012

A B C D E F G

60Sign under test




Agency



Trials

Variable Mandatory

Speed Limits

Variable Advisory


2. Interim Scheme Specific Maintenance

1. Maintenance During Construction

3. Handover to HA for

Operational

Maintenance

Figure 7 - Maintenance over the lifecycle of a Managed Motorway Scheme

8.1 During Stages A - C: Maintenance during Construction Before the start of works (Stage B), the Contractor delivering the scheme on behalf of Major Projects should develop an agreement with the NDD Senior User, Regional Maintenance Service Providers (e.g MAC, TechMAC) and Regional Control Centre setting out which assets should be taken out of maintenance, and the arrangements that will be put in place to maintain any equipment that remains on the network. This should be formally accorded in a Memorandum of Understanding (MoU) or Detailed Local Operating Agreement (DLOA). The MOU/DLOA should also set out the approach to conducting condition surveys, define the obligations of all parties during the construction phase, and describe how the handover process will be managed in Stage G. Further information on the level of provision of Information Technology Services (ITS) during construction is provided in the position statement “Maintaining Information Technology Systems (ITS) during Construction (14/02/2011)” released by the Delivery HUB, copies of which can be obtained by e-mailing [email protected]. Unless an alternative arrangement is agreed with the NDD Senior User and the Regional Operations Board, maintenance during construction shall be undertaken in accordance with the principles set out in Chapter 6.6.8 (Coordination of Design and Works: During the contract) of the Network Management Manual (NMM), which state that:


IAN 165/12 of 62 Apr 2012

“During the contract, responsibility for any routine inspections and all routine maintenance within the site area, shall pass to the Contractor who will be required to comply fully with the Routine & Winter Service Code and the Network Management Manual.’’

Whilst the Contractor is responsible for all technology and civil maintenance activities until scheme handover, they are excluded from maintenance related to Winter Maintenance and Severe Weather. These services shall continue to be provided by the Maintenance Service Providers (MSPs) contracted by the Agency. The maintenance requirements for this period are further outlined in Table 3 in Section 8.4 below. Note: Although ‘Maintenance during Construction’ is referred to as Stages A to C, in reality the maintenance will only need to be in place starting Stage B when the Contractor takes over the asset. 8.2 During Stages D - F: Interim Scheme Specific Maintenance Following the successful completion of Systems Commissioning (Stage C) and the Contractor demobilising the main works site, the scheme will move into Operational Regime Testing (Stages D-F). In these Stages the newly installed technology and civil infrastructure is tested in a live environment to ensure that all the technology systems are stable and that all elements are completed to enable Hard Shoulder Running and the live operation of the scheme. One of the key activities during this period is the maintenance of the technology and civil infrastructure that have been constructed and installed to enable the operation of variable mandatory speed limits and hard shoulder running. These maintenance activities shall be carried out as per the requirements outlined in Table 3 in Section 8.4 below. At the point of scheme handover in Stage G, responsibility for controlling access to the network shall be transferred back to the HA MSPs. Up until such time, the management of network occupancy (within the scheme boundaries) shall remain the responsibility of the Contractor. 8.3 During Stage G: Handover to HA for Operational Maintenance As per current HA policy, civil and technology infrastructure associated with a managed motorway scheme shall only be handed over to the Agency for maintenance and operation during Stage G, when the scheme is complete and has been opened to the public. Until the point of scheme handover, the scheme shall be maintained by the Contractor as per the requirements outlined in Table 3 in Section 8.4 below.


IAN 165/12 of 62 Apr 2012

In preparation for the handover of maintenance to the HA, the scheme must ensure that the Maintenance Service Provider(s) have been trained in the maintenance of the new infrastructure. At the time of formal handover, the Contractor shall handover the required Health and Safety (H&S), technical and operational documentation (including PCF Products) to the Highways Agency (NDD and TMD) and their Maintenance Service Providers (TechMAC / MAC / NRTS). It is recommended that all the required handover documentation is collated and developed throughout the lifecycle of the scheme to ensure that there is no delay to handover in Stage G. In practice the preparation and submission of the H&S file is an iterative process and shall begin in Stage B and continue on until such time as the Scheme is handed over to the Agency in Stage G. At this point, the Contractor delivering the scheme on behalf of Major Projects relinquishes day-to-day responsibility for maintaining the assets previously under their custodianship. 8.3.1 Maintenance Handover Procedure This process is defined in MCH 1349F Section 7.2 (Maintenance Handover Procedure). For ease of reading, a copy of the steps is provided below (note: readers should check for later versions or successor documents of the referred MCH to ensure full compliance): 7.2.1 The Maintenance Handover Procedure may be considered in five parts related to the Maintenance Responsibilities and the O&M requirements that apply to the different elements of the scheme (Section 2 and Table 2.1.1 refer). These can be summarised as:

a) Part 1: Civil and Structures Infrastructure Handover: Comprising Gantries, CCTV Masts, Safety Barrier, Retaining Walls, Ducts, Access, Steps, MS3 Bases etc. These will be handed over to the Area MSP for Infrastructure.

b) Part 2: Technology Infrastructure Handover: Comprising Cabinets,

Power etc. will be handed over to the MSP for Technology. c) Part 3: NRTS Passive Infrastructure Handover: Comprising Ducts and

Chambers etc. will be handed over to NRTS. d) Part 4: Technology Outstations Handover: Comprising Telephones,

Signals, Message Signs, and other Outstation equipment will be handed over to the MSP for Technology.

e) Part 5: Technology Instation - System Software and Site Data Handover:

Comprising HATMS Hardware, Software and Site Data will be handed over to the MSP for Technology.


IAN 165/12 of 62 Apr 2012

8.4 Required level of Maintenance In principle, all maintenance shall be carried out by the Contractor in accordance with the Service Level Agreement (SLA) and the maintenance specification(s) that the Agency Maintenance Service Provider(s) (MSP) are contractually bound by within each region. This information shall be obtained by liaising with the HA Service Delivery Manager and/or the MSP and regionally agreed with the NDD Senior User. Where there is ambiguity on the SLA or the requirements, for example due to managed motorway specific technology being installed that are currently not covered within MSP maintenance, the Contractor delivering the scheme on behalf of Major Projects shall target cost based on suitable service levels agreed with the NDD Senior User and the ROB. These service levels shall be based on:

1. Overall availability of asset; and, 2. Critical equipment availability.

Table 3 below defines the level of maintenance the Contractor delivering the scheme on behalf of Major Projects shall provide during each stage of the managed motorway lifecycle. Stage Asset type -

Pre-existing1 vs. New2 Required level of Maintenance

Pre-existing 1 In accordance with the Service Level Agreement / Maintenance Specification for Maintenance Service Provider(s).

During Stages A – C (in practice this may be Stage B to C)

New2 To a level deemed fit by the Contractor to support its own activities such as systems commissioning.

Pre-existing1 In accordance with the Service Level Agreement / Maintenance Specification for Maintenance Service Provider(s).

Under testing To a level deemed fit by the Contractor to support its own activities such as Operational Regime testing.

During Stages D - F

New2

In operational use (to aid with the tuning of Queue Protection algorithms, for Incident Management, etc)

In accordance with: 1. the Service Level Agreement /

Maintenance Specification for Maintenance Service Provider(s); or

2. as agreed regionally. Pre-existing1 During Stage G New2

In accordance with: 1. the Service Level Agreement /

Maintenance Specification for Maintenance Service Provider(s); or

2. as agreed regionally. Table 3 - Maintenance Specification Notes 1 Pre-existing: defined as asset types that were available prior to start of works and remain in operation during the course of the works. 2 New: defined as asset types that were installed as part of managed motorway scheme.


IAN 165/12 of 62 Apr 2012

8.4.1 Changes to HA Maintenance Contracts Starting in 2012, it is expected that all maintenance contracts will be re-let under the new maintenance arrangements based on the Asset Support Contract (ASC) and the Regional Technology Maintenance Contract (RTMC). When target costing, the Contractor delivering the scheme on behalf of Major Projects are advised to take these changes (to maintenance contracts) in to account as the maintenance Specifications used for these contracts will differ from those currently in use. The ASC and RTMC contracts will be based on the Asset Maintenance and Operational Requirements (AMOR) and Technology Management and Maintenance Manual (TMMM) specifications. 8.5 Selection of Maintenance Service Provider This document does not define who should undertake these maintenance activities. It is the responsibility of the Contractor delivering the scheme on behalf of Major Projects to determine who is best placed to undertake these activities for each scheme. It is recognised that the Contractor may have the capability to undertake these activities themselves or alternatively may wish to contract in a third party (e.g. TechMAC, MAC or others) to provide the maintenance on their behalf.


IAN 165/12 of 62 Apr 2012

9. Requirements for Scheme Handover There are three facets to the handover of a scheme from delivery in to operations and maintenance. These are as follows:

1. handover of the civil infrastructure, 2. handover of the technology infrastructure and equipment, and, 3. handover of the scheme in to operation.

The criteria for handover (and associated processes) are defined in Section 9.1 to 9.3. In addition to the above, scheme handover is dependent on the completion and agreement of the following:

1. outstanding defects and faults, 2. defects liability, 3. post opening optimisation, and, 4. project closeout.

These are further discussed in Section 9.4 to 9.7. It is the responsibility of the Contractor delivering the scheme on behalf of Major Project to ensure that these handover criteria are successfully achieved. Failure to do so will result in a delay to scheme handover, subsequently increasing the costs incurred by the Contractor due to ongoing maintenance and staffing requirements. 9.1 Criteria for handover of Civil Infrastructure into Maintenance These requirements are defined in the Maintenance Handover Certificate within the PCF product ‘Civils Maintenance (MAC) Handover Documentation & Certificate’. For ease of reading, a copy of the Handover Checklist is provided below (note: readers should refer to the PCF template for the most current checklist to ensure full compliance): 1. All Highways Agency Standards in place at date (dd/mm/yyyy) have been met

(includes Health and Safety file, As Built drawings etc.) 2. All departures required at above date have been agreed by the Highways

Agency 3. Final inspections have been undertaken with the Service Provider and an action

list agreed 4. All information handed over in accordance Handover Schedule 5. All information pertaining to Local Authority Roads and detrunked routes has

been handed over to Local Authority 6. Stage 1, 2, and 3 Road Safety Audit Completed 7. All findings of Road Safety Audits 1, 2, and 3 actioned 8. Maintenance and Repair Strategy Statement included 9. Maintenance spares have been provided 10. All asbestos related documentation handed over and asbestos tracker updated 11. Outstanding Matters Checklist included


IAN 165/12 of 62 Apr 2012

9.2 Criteria for handover of Technology Infrastructure and Equipment into Maintenance These requirements and this process are defined in MCH 1349F Section 4.9 (Acceptance Testing). The Contractor delivering the scheme on behalf of Major Projects shall ensure that Acceptance Tests are carried out on all systems to demonstrate that they are "fit for purpose", meet the Highways Agency’s requirements, and are suitable for operation and handover into maintenance. This is achieved through the completion of the follow activities:

1. Acceptance Testing - Infrastructure and Transmission; 2. Acceptance Testing - Technology Equipment; 3. Acceptance Testing – System Software and Site Data; and, 4. System Performance Monitoring (Soak Testing) Period

The completion of activity 4 above is critical to achieving ‘technology handover’. It is intended to demonstrate that the systems delivered are ‘fault free’ and are ready for operational use in the live environment. For ease of reading, a copy of the steps associated with this is provided below (note: readers should check for the latest versions or successor documents of the referred MCH to ensure full compliance): System Performance Monitoring (Soak Testing) Period 4.9.15 The Scheme Manager must arrange for systems performance monitoring, and supply documentary evidence to demonstrate that the equipment / system / scheme has operated "fault-free" to specification for a continuous period of a minimum of 7 days without intervention. 4.9.16 This evidence can be based on equipment logs, COBS fault logs and / or HALOGEN logs, whichever is deemed appropriate. Where faults are reported during the monitoring period, and these are either "expected" due to the MTBF, or can be attributed to "known / identifiable faults", these may be recorded as "exceptions" to fault-free operation. 4.9.17 In such cases, they may not prevent the entire system from being handed over into maintenance, provided the requirements defined in Section 7.4 "Outstanding Defects, Faults and O&M Requirements" are fully met.

This process is also referred to in the Maintenance Handover Certificate within the PCF product ‘Technology Maintenance Handover Documentation & Certificate’. 9.3 Criteria for Operational handover These requirements are defined in the Operational Handover Certificate within the PCF product ‘Operational Handover Documentation & Certificate’. For ease of reading, a copy of the Handover Checklist is provided below (note: readers should refer to the PCF template for the most current checklist to ensure full compliance):


IAN 165/12 of 62 Apr 2012

1. TMD have agreed to the principles of the operating regime and the use of

operational resource to manage and operate the scheme. 2. Any use of operational resource to mitigate scheme specific hazards / risks have

been agreed by TMD. 3. TMD have confirmed that there is sufficient on road and control room resource

to manage the scheme effectively and safely. 4. TMD requirements have been met in terms of control room (building) capacity to

enable them to operate the scheme safely and effectively. 5. TMD have been engaged in the regional process to agree the compliance

strategy and any MOUs with category 1 responders. 6. The Traffic Learning Centre (TLC) or appropriate training provider has provided

assurance that operational staff within the directorate have received training and that those staff have reached the minimum competency requirements.

7. Appropriate technology has been implemented prior to handover that meets the requirements of TMD in operating the scheme.

8. TMD procedures for the scheme are available and accessible and have been approved by the TMD procedures team for use.

9. TMD have been actively engaged in the live testing of the scheme and have had the opportunity to operate it before the intended point of handover into operations.

10. TMD are actively engaged with the plan for monitoring operations and agreements have been made to share results and outcomes with operations.

11. TMD have been provided with appropriate Q+A’s and lines to take reference the scheme prior to operational handover.

12. TMD have agreed a formal date for handover into operations with NDD and MP. 9.4 Outstanding Defects and Faults Before handing the scheme over to the Agency (NDD and TMD), the MP Project manager and the Contractor must ensure that all outstanding defects and faults arising from construction and technology installation have been addressed or recorded in an Exception Report / Outstanding Matters Checklist, which form a part of the Handover PCF Products. 9.5 Defects Liability The 12 months defects liability period for all Civil, Technology and NTRS Infrastructure delivered as a part of the scheme shall begin at the start of Operational Maintenance by the Agency. 9.6 Post Opening Optimisation Once the scheme is in operation, it is essential that allowance be made to undertake a review of the scheme operation and the optimisation work required.


IAN 165/12 of 62 Apr 2012

This typically entails a period of between 1-3 months during which traffic patterns, hard shoulder usage and take-up, and system performance are monitored on a regular basis. The results of the review period shall then be used to determine any required changes to the system, which should be implemented in a post go-live Site Data Load. The scheme Site Data Designer should also provide input, along with the Software Maintenance Contractor and TMD Operational Staff. The Contractor delivering the scheme on behalf of Major Projects should make allowance within their target cost for time and resources to undertake this assessment, noting that this activity typically falls outside the Contractors’ contractual ‘Completion’. Further guidance on post opening optimisation can be obtained from NDD Traffic Technology Division (via the following address: [email protected]). 9.7 Project Closeout The PCF process provides for a final revision of the handover documentation during Stage 7 (Closeout) of the PCF Lifecycle. Project Closeout shall be achieved as soon as reasonably practicable after handover. Prior to Closeout, a Project Closeout Review Workshop should be held and if deemed necessary, a Closure Checklist produced and agreed with the NDD Senior User. This should include details of all outstanding claims and issues (including any remaining issues from the Outstanding Matters Checklist), and identify who is to be responsible for these. It is at this point that SGAR 7 shall take place, which formally closes out the scheme.


IAN 165/12 of 62 Apr 2012

10. Variations that impact the Commissioning and Handover Process

10.1 Phased / Sectional Construction and Completion of Schemes On managed motorway schemes where approval has been given to a phased or sectional approach to construction, handover into operation and maintenance of any link can only take place when it is fully operational with hard shoulder running enabled. This applies to all subsequent links with a requirement that on completion of the final link, end to end commissioning from the start to the end of the scheme is undertaken. Figure 8 below provides an example of how this might be undertaken.

1F1C 1E1D 1G

xG

1A

xA xFxC xExD

NDD/TMD accept full scheme into maintenance/operations

Operations/Maintenance handed over to NDD

Major Project and its Contractor Maintenance Liability

1B

xB

NDD/TMD accept sectioninto maintenance/operations

Business as usual maintenance by MSPs

Figure 8 - Phased / Sectional Construction and Completion of Schemes 10.2 Commissioning and Handover of a Controlled All Lane Running Scheme

or Managed Motorway All Lane Running Scheme Controlled All Lane Running (CALR) and Managed Motorway All Lane Running (MM-ALR) are features of the managed motorway tool kit in which the hard shoulder is permanently converted into a controlled running lane. The process and principles behind the commissioning and handover of a CALR or MM-ALR Scheme or Link are the same as those that apply to an IAN 111/09 designed managed motorway scheme (with HSR), except that the HSR Trial stage (Stage F) is not applicable.


IAN 165/12 of 62 Apr 2012

This is illustrated in Figure 9 below.

A B C D E F G

60Sign under test

Use hard shoulder

60?


Scheme with CALR or MM-ALR

/ Handover to Agency



Trials

Variable Mandatory

Speed Limits

Advisory Speed Limits

(optional)

Not relevant to CALR / MM-ALR

Figure 9 – Lifecycle of the CALR or MM-ALR Scheme


IAN 165/12 of 62 Apr 2012

Appendix 1 – Glossary


IAN 165/12 of 62 Apr 2012

AMI Advanced Motorway Indicator AMOR Asset Maintenance and Operational Requirements ASC Asset Support Contract ATM Active Traffic Management AVASL Automatic setting of Variable Advisory Speed Limits AVMSL Automatic setting of Variable Mandatory Speed Limits CALR Controlled All Lane Running CCTV Closed Circuit Television CM Controlled Motorways Commissioning and Handover Period

Stages C through to G within the managed motorway Lifecycle

Contractor Contractor delivering the scheme on behalf of Major Projects (i.e. Delivery Partner and their Scheme Designer)

CTI Consent to Implement Delivery HUB Managed Motorways Delivery HUB (previously referred to as the Managed

Motorways Delivery Office, MMDO) DLOA Detailed Local Operating Agreement DMRB Design Manual for Roads and Bridges ERT Emergency Response Telephones H&S Health and Safety HA Highways Agency HSM Hard Shoulder Monitoring HSR Hard Shoulder Running ITS Intelligent Transportation Systems Lead OM Lead Operations Manager (RCC) MAC Managing Agent Contractor MCH An HA technical document (MCH is not an acronym) MIDAS Motorway Incident Detection and Automatic Signaling MM Managed Motorways MM-ALR Managed Motorways All Lane Running MMDO Managed Motorways Delivery Office (or Delivery HUB) MMOB Managed Motorways Operations Board MMSG Managed Motorways Steering Group MOU Memorandum of Understanding MPD Major Projects Directorate (Highways Agency) MS4 Motorway Signal Mark 4 Signs MSP Maintenance Service Provider MVASL Manual setting of Variable Advisory Speed Limits MVMSL Manual setting of Variable Mandatory Speed Limits NDD Network Delivery and Development Directorate (Highways Agency) NMM Network Management Manual NRTS National Roads Telecommunications Service Operating Regime Testing

Stages D, E and F within the MM Lifecycle

PCF Project Control Framework PM Project Manager PTZ Pan Tilt Zoom RCC Regional Control Centre ROB Regional Operations Board RSC Roadside Controller RTMC Regional Technology Maintenance Contract RWSC Routine Winter Service Code SAT Site Acceptance Test SDT Service Delivery Team Senior User NDD Divisional Director for that region Senior User Rep A person appointed by the NDD Divisional Director for that region SI Statutory Instrument


IAN 165/12 of 62 Apr 2012

SLA Service Level Agreement Systems Commissioning

SAT 3, a true end-to-end test, testing the devices from its controller, local cabling, communications links, site data and to the operator interface.

TechMAC Technology Managing Agent Contractor TJR Through Junction Running TM Traffic Management TMD Traffic Management Directorate (Highways Agency) TMMM Technology Management and Maintenance Manual TPMS Technology Performance Management Database TTD Traffic Technology Division VASL Variable Advisory Speed Limits VMSL Variable Mandatory Speed Limits


IAN 165/12 of 62 Apr 2012



IAN 165/12 of 62 Apr 2012

Appendix 2 – Roles and Responsibilities related to Commissioning & Handover


IAN 165/12 of 62 Apr 2012

Stage A (Pre Works)

R Responsible A Accountable C Consulted I Informed

The tables below provide an indicative list of roles and responsibilities that are specific to the process of commissioning and handover. They are based on what is required either in preparation for (in Stages A and B) or as a part of the commissioning and handover process (in Stages C to G) within the context of the managed motorway lifecycle. Note: Roles and responsibilities related to PCF products are not included in these tables as each PCF product template provides a matrix of the roles and responsibilities applicable to that product.

Contractor(s) Maintenance Service

Providers Highways Agency

ID. Task / Activity Description

Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(Tec

hMA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(MA

C)

TM

D R

CC

Le

ad

Ope

ratio

ns

Man

age

r

NT

OC

1 Agreement of life cycle of scheme

R R C C C A C C C C I

2 Agreement on process and options adopted for Commissioning and Handover

R R C C C A C C C C I

3 Prepare and agree a Memorandum of Understanding (MOU) and/or Detailed Local Operating Agreement (DLOA)

R C C C C A C C C C C

4 If deemed necessary, obtain Activity Schedule from MSPs and include agreed pricing within Target Cost

R I C C C A C C I

5 Engage with MSP’s to ensure that Design for Maintenance requirements are captured and incorporated into the scheme design.

C R C C C A I C C I I

6 Agree criteria for eventual handover of Technology assets (Ref: MCH1349F)

R R C R A C R C C C

7 Agree criteria for eventual handover of Civil assets (Ref: BD62/07)

R R C R A C R I I

8 Agree criteria for eventual handover of NRTS assets (Ref: Guide to working with GeneSYS_rev 5)

R R R C C A C R C I C

9 Agree criteria for eventual handover of Operation to TMD

R R I I I A C I I R R

10 Develop, agree and obtain sign-off of applicable PCF Products (see Appendix 5) Note: as per R&R within each PCF Template


IAN 165/12 of 62 Apr 2012

Stage B (Construction)

Contractor(s) Maintenance Service Providers

Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

TT

D

Ser

vice

Del

iver

y M

ana

ger

(Tec

hM

AC

)

ND

D S

ervi

ce D

eliv

ery

Man

age

r (M

AC

)

RC

C

Lea

d O

pera

tions

M

ana

ger

NT

OC

1 Refinement of MoU / DLOA as required

R C C C C A C C C C C

2 Principal Contractor for the duration of the works A

3 Regular engagement with Contractor & project team throughout construction phase

R R R R R I A R R R R

4 Amendments to Design

C R C C C A C C C C C

5 Construction / installation works R C C C C A I C

C

I I

6 SAT1 and SAT2 Testing

R C C C C A I C I C I

7 Maintenance as per the MoU / DLOA

R C C C A C C C

8 Regular condition surveys and inspections as required

R R R R A A A

9 Preparation and implementation of Site Data and all associated liaison and documentation, including initial operational parameters for new operational regimes.

C R C C A C C I

10 Management of RCC Readiness related activities

C C C C C A R C

11 Initiate Operator induction and training (Ref: MM Delivery Office / TMD Position Statement on Operator Training)

R I C A C C

12 Ensure equipment/infrastructure installed are fit for purpose and can be maintained

R R C C C A I C C C I

13 Arrange Road Safety Audits as per HD19 requirements

A / R C C C C

14 Advise Contractor on type and format of O&M manuals, data for HA databases etc

C C R R R C A A C


IAN 165/12 of 62 Apr 2012


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

TT

D

Ser

vice

Del

iver

y M

ana

ger

(Tec

hM

AC

)

ND

D S

ervi

ce D

eliv

ery

Man

age

r (M

AC

)

RC

C

Lea

d O

pera

tions

M

ana

ger

NT

OC

15 Compilation of design information for inclusion in the H&S file

C R C C C A I I I I

16 Compilation of as-built information for inclusion in H&S file R R I C C

A

I I I



IAN 165/12 of 62 Apr 2012

Stage C (Systems Commissioning)


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(Tec

hMA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(MA

C)

TM

D R

CC

Le

ad

Ope

ratio

ns

Man

age

r

NT

OC

1 Statutory Instrument

I I A / R I I I C


R C C C A C C C C I

3 SAT3 Testing

R C C C C A I C I C I

4 Engage with all parties to ensure visibility and agreement of commissioning approach and progress

R C C C C A C C C C I

5 Advise Contractor on type and format of Commissioning Certificates and Handover documentation required

I I R R R C C C C

6 Preparation and implementation of Site Data and all associated liaison and documentation. Final Site Data to be ready and loaded prior to completion of Stage C.

C R I C A C C

7 Provision of design information for inclusion in H&S file

C R C C C A C C

8 Preparation of handover documentation such as the As-builts, H&S file, O&M manuals etc


9 Make staff available for training as required

I I R R A R R R

10 Progress Operator induction and training (Ref: MM Delivery Office / TMD Position Statement on Operator Training)

R I C A I C C

11 Initiate Operator induction and training (Ref: MM Delivery Office / TMD Position Statement on Operator Training)

R I C A I C C

12 Arrange RSA Stage 3 Audit, typically during Stage C

A / R C

13 Sign-off Consent To Implement, or otherwise provide authorisation to proceed to next stage.

R C I I I A C C C C


IAN 165/12 of 62 Apr 2012

Stage D, E & F (Operational Regime Testing - ASL, VMSL, HSR)


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(Tec

hMA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(MA

C)

TM

D R

CC

Le

ad

Ope

ratio

ns

Man

age

r

NT

OC


R C C C A C C C I I

2 De-mobilisation of Contractor / site presence / removal of construction related Traffic Management (where possible)

R C C C C A I C C I I

3 Progress Operator induction and training (Ref: MM Delivery Office / TMD Position Statement on Operator Training)

R I C A C C

4 Carry out Maintenance Service Provider training

R C C C A C C

5 Manage Operational Regime Testing stages and subsequent implementation of new regimes such as MIDAS Queue Protection and Variable Mandatory Speed Limits.

R C I C I A I C C C C

6 RCC staff to assist in the completion of Operational Regime testing.

C C A R

7 Ensure Operational Regime testing is kept to agreed timescales

R C C C I A I C C R

8 Support Contractor during Stages D, E & F

C R R R C A R R R

9 Preparation and implementation of any Site Data changes and all associated liaison and documentation.

C R I C A C C

10 Provide access to Instation systems to enable implementation and calibration of new operational regimes.

R A R

11 Develop snagging list and agree resolution dates

R C C C A I C C C C

12 Reinstate/Install Network Occupancy Management System in readiness for when handover occurs in Stage G

C C C A / R I I I C C I

13 Clarify requirements and timescales for handover



IAN 165/12 of 62 Apr 2012


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

igne

r

NR

TS

Tec

hMA

C

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(Tec

hMA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(MA

C)

TM

D R

CC

Le

ad

Ope

ratio

ns

Man

age

r

NT

OC

14 Continue with any updates to handover documentation

R C C C C A C C C

15 Sign-off Consent To Implement to proceed to next stage

R C I I I A C C C C I


IAN 165/12 of 62 Apr 2012

Stage G (Operational use of Scheme / Handover to HA)


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

ign

er

NR

TS

Tec

hM

AC

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(T

ech

MA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(M

AC

)

TM

D R

CC

L

ead

Op

erat

ion

s M

anag

er

NT

OC

1 Scheme opens with full operational capability of a MM Scheme with HSR

R C I I I A C C C R I

2 As deemed necessary, further calibration, fine tuning and incremental operational improvements are made.

R R I C I A I C I C I

3 Finalise requirements and timescales for scheme handover

R C C C C A C C C C

4 Complete Road Safety Audit (unless previously completed) prior to scheme handover

A / R C

5 Inspections of the works in accordance with MCH1349

R I R C A R

6 Inspections of the works in accordance with BD62 R R C A

R

7 Provision of sufficient quantities of non-Bulk Purchase equipment spares

R C C C A I C C

8 Agreement of a snagging list and resolution dates


9 Network Occupancy Management System is operational

C C C A / R I I I C C I

10 Formal acceptance of civil infrastructure in to maintenance R C R C A I R

11 Formal acceptance of technology assets in to maintenance R C R C A R I

12 Formal acceptance of scheme in to operations

R C I I I C A C C R I

13 Defects Liability (of 12 months post formal handover)

R C C A I C C C

14 Attending to defect rectification as per snagging list to agreed timescales and specification

R C C A I C C C


IAN 165/12 of 62 Apr 2012


Highways Agency


Del

iver

y P

artn

er

Sch

eme

Des

ign

er

NR

TS

Tec

hM

AC

MA

C

MP

P

roje

ct M

anag

er

ND

D

Sen

ior

Use

r

ND

D T

TD

S

ervi

ce

Del

iver

y M

ana

ger

(T

ech

MA

C)

ND

D S

ervi

ce

Del

iver

y M

ana

ger

(M

AC

)

TM

D R

CC

L

ead

Op

erat

ion

s M

anag

er

NT

OC



IAN 165/12 of 62 Apr 2012



IAN 165/12 of 62 Apr 2012

Appendix 3 – Local Commissioning and Systems Commissioning


IAN 165/12 of 62 Apr 2012

A3.1 Introduction Commissioning of new technology infrastructure and systems is an iterative process, divided into a series of testing activities that follow on from one another. Testing of end devices and local cabling (e.g. a group of AMI installed on a gantry, with local cabling to the associated Roadside Controller) is referred to as Site Acceptance Test (SAT) 1. Testing of a group of equipment including longitudinal communications circuits provided by NRTS is referred to as SAT2. SAT1 and SAT 2 grouped together is referred to as Local Commissioning. Final Systems Commissioning, where devices are controlled from the relevant Regional Control Centre, thereby testing the device, controller, local cabling, communications links, site data and operator interface in a true end-to-end test, is referred to as SAT 3. This stage of testing is contained within Stage C (Systems Commissioning). Further detail of each test stage is given below, and suggested allocation of responsibility is provided in Appendix 2. A3.2 Local Commissioning The following is a summary of activities contained within Local Commissioning. This block of testing is likely to overlap with latter part of Stage B (Construction).

1. SAT1 - testing of devices and associated controllers and local cabling, not requiring any NRTS provided SDP or longitudinal cabling. The start of SAT1 testing is defined as the point at which the end device is installed, and local cabling works are complete with power supply installed and certified.

2. SAT2 – testing of single or groups of devices from a remote location, including

NRTS provided longitudinal circuits. SAT2 Testing is dependent upon having part(s) or all of the longitudinal cable network installed and tested. If possible, SAT2 testing shall coincide with NRTS End-to-End Testing and enablement in order that connectivity issues are identified and rectified before the end of the NRTS programme window.

In parallel to Local Commissioning, the NRTS team(s) is delivering the NRTS supplied circuits and Service Delivery Points. The Contractor should note the pre-requisites and dependencies that drive the NRTS start date and programme duration, and take these into account when scheduling works. It is important that the NRTS team(s) is given unhindered access to sufficient lengths of completed infrastructure. The NRTS programme culminates in the activation milestone, which is when the newly installed Service Delivery Points and associated circuits are handed to the scheme. For the purposes of planning, and to allow comparisons to be made across multiple schemes, the NRTS Activation milestone shall be used to define the start of Stage C (Systems Commissioning).


IAN 165/12 of 62 Apr 2012

A3.3 Systems Commissioning This stage includes the final end to end testing of the whole system, including the Instation and its associated site data, the complete NRTS circuits, and the end devices such as MS4 and RSC, AMIs and RSC, CCTV, MIDAS Outstations etc. This phase of testing is also referred to as SAT3 Testing, as it is the last stage in the SAT1/2/3 Test methodology. The start of Stage C (Systems Commissioning) is driven by two key dependencies – the NRTS Activation Milestone and the Site Data Load containing the details for the new scheme (or section of a scheme). Stage C is completed when it is confirmed that all testing is successfully complete, evidenced by SAT3 Test Records. The transition to Stage D and beyond cannot be made if unresolved issues remain following Stage C. Figure A3-1 below provides a graphical illustration of the sequencing of activities and stages.

Local Commissioning

Var

iab

le

Ad

viso

ry

Sp

eed

Li

mits

Har

d

Sho

uld

er

Run

ning

Tr

ials

Op

enin

g o

f S

chem

e w

ith H

SR

/

Han

do

ver

to A

gen

cy


SA

T3

fro

m

RC

C MV

AS

L

HS

R T

rails

(th

is

may

ove

rlap

w

ith E

2

D1 D2 F


Var

iab

le

Man

dat

ory

S

pee

d

Lim

its

AV

AS

L

E1 E2

Han

do

ver t

o

HA

G

Op

en to

the

pub

lic

MV

MS

L

AV

MS

L

B C D E F GS

yste

ms

Co

mm

issi

oni

ng

C

ConstructionM

anua

l

Man

ual

Aut

o

Aut

o

NRTSActivation




Regime Testing

Figure A3-1: Local Commissioning and System Commissioning


IAN 165/12 of 62 Apr 2012



IAN 165/12 of 62 Apr 2012

Appendix 4 – Stage Completion Requirements


IAN 165/12 of 62 Apr 2012

The tables below provide stage completion requirements specific to the process of commissioning and handover. They are based on what is required either in preparation for (in Stages A and B) or as a part of the commissioning and handover process (in Stages C to G) within the context of the managed motorway lifecycle. As a minimum, these must be undertaken and completed prior to the transition from one stage to the other. It is recognised that there will be variances at a scheme and regional level and schemes are encouraged to identify and agree these as early as possible in the delivery process. Note: It is recommended that the stage completion requirements are read in conjunction with Appendix 2 (Roles and Responsibilities related to Commissioning and Handover). Stage A (Pre Works) Completion Criteria ID. Requirements 1 Agreement on the lifecycle of the MM scheme with NDD and TMD 2 Agreement on process and options adopted for Commissioning and Handover with NDD and

TMD 3 Memorandum of Understanding (MOU) and/or Detailed Local Operating Agreement (DLOA)

incorporating agreements on various other aspects deemed important / necessary (eg. maintenance) with Maintenance Service Providers, the applicable HA directorate and other stakeholders

4 Develop, agree and obtain sign-off of the following PCF Products (Ref: Appendix 5): Produce Project Schedule Produce Handover Schedule Produce Maintenance and Repair Strategy Statement Produce Technology Commissioning Plan Produce Health & Safety File

Stage B (Construction) Completion Criteria ID. Requirements 1 Review and agree refinements to the process and options for Commissioning and Handover

process agreed during Stage A 2 Review and agree refinements to the MOU / DLOA agreed during Stage A 3 All outstation infrastructure installed 4 Completion of SAT 1 & SAT 2 (Ref: Appendix 3) 5 Initiate Operator induction and training (Ref: MM Delivery Office / TMD Position Statement on

Operator Training) 6 Initiate the production of documentation related to MCH1349 and BD 62/07 7 Develop, agree and obtain sign-off of the following PCF Products (Ref: Appendix 5):

Produce TOS Training Requirement Produce As built Documentation Produce Plan for Monitoring Operations Update/Refine Handover Schedule Update/Refine Technology Commissioning Plan Update/Refine Health and Safety File


IAN 165/12 of 62 Apr 2012

Stage C (Systems Commissioning) Completion Criteria ID. Requirements 1 Statutory Instrument must be in place (unless Stage D, Advisory Speed Limits is undertaken) 2 Completion of end-to-end systems commissioning; this is to include all instation and outstation

systems installed and/or upgraded as a part of the works (Completion of SAT3) 3 Completion of Road Safety Audit #3 (typically done during Stage C) 4 Progress the production of documentation related to MCH1349 and BD 62/07 5 Operator training / induction to new systems (Ref: MM Delivery Office / TMD Position Statement

on Operator Training) 6 CTI Stage C sign-off to proceed to next stage Stage D (Advisory Speed Limits) Completion Criteria ID Requirements 1 De-mobilisation of Contractor / site presence / removal of construction related Traffic

Management (where possible) 2 Completion of Operator training / induction (Ref: MM Delivery Office / TMD Position Statement

on Operator Training) 3 The following conditions have been met:

Queue detection is accurate;

Number and frequency of false alarms is at a tolerable level;

Advisory signals are set and removed in a timely and credible manner;

System faults are at an acceptable level and do not prevent full and reliable operation; and,

Traffic performance is stable and a baseline has been established that is representative of “typical” traffic conditions.

4 Carry out Maintenance Service Provider training 5 CTI Stage D sign-off to proceed to next stage

Stage E (Variable Mandatory Speed Limits) Completion Criteria ID Requirements

1 If Stage D was not implemented, de-mobilisation of Contractor / site presence / removal of

construction related Traffic Management (where possible) 2 The following conditions have been met:

Queue detection is accurate;

Number and frequency of false alarms is at a tolerable level;

System faults are at an acceptable level and do not prevent full and reliable operation.


3 Complete Operator training; RCC is ready for Hard Shoulder Running Trails (Ref: MM Delivery Office / TMD Position Statement on Operator Training)

4 Carry out Maintenance Service Provider training 5 CTI Stage E sign-off to proceed to next stage


IAN 165/12 of 62 Apr 2012

Stage F (Hard Shoulder Running Trials) Completion Criteria ID Requirements 1 The following conditions have been met:

System faults are at an acceptable level and do not prevent full and reliable operation (although some faults could roll-over to Stage G).


Hard Shoulder Running trials are deemed successful.

2 Complete Operator training; RCC is ready for Hard Shoulder Running Operations. 3 Complete Maintenance Service Provider training 4 CTI Stage F sign-off to proceed to Operational use Stage G (Operational use of Scheme / Handover to HA) Completion Criteria ID. Requirements 1 As deemed necessary, further calibration, fine tuning and incremental operational improvements

are made. 2 Network Occupancy Management System is operational 3 Complete Road Safety Audit (unless previously completed) prior to scheme handover 4 Sign-off of the following PCF Products (Ref: Appendix 5):

Civils Maintenance (MAC) Handover Documentation & Certificate Technology Maintenance (TechMAC) Handover Documentation & Certificate Operational (RCC) Handover Documentation & Certificate

Note: Within PCF Stage “Closeout”, it requires the Scheme to Update/Refine the following PCF Products:

As built Documentation Health & Safety File Technology Commissioning Plan Civils Maintenance (MAC) Handover Documentation & Certificate Technology Maintenance (TechMAC) Handover Documentation & Certificate Operational (RCC) Handover Documentation & Certificate


IAN 165/12 of 62 Apr 2012

Appendix 5 – Mapping of MM Lifecycle to PCF Stages & CTI


IAN 165/12 of 62 Apr 2012

MM Lifecycle Stage PCF Stage * Key Products related to Commissioning and/or Handover

A – Pre Works 2 – Option Selection

• Maintenance and Repair Strategy Statement• Health and Safety File• Project Schedule

5 – Construction Preparation

• Handover Schedule• Technology Commissioning Plan• Operation Regime

Update/Refine...• Health & Safety File• Maintenance and Repair Strategy Statement

B – Construction 6 – Construction, Commissioning & Handover

• As built Documentation• TOS Training Requirements• Plan for Monitoring Operations

Update/Refine...• Technology Commissioning Plan • Health & Safety File• Handover Schedule

C – Systems CommissioningD – Advisory Speed LimitsE – Variable Mandatory Speed

LimitsF – Hard Shoulder Trials

6 – Construction, Commissioning & Handover

Other...• Propose to use Consent to Implement

(CTI) process (which is not within PCF)

G – Open to Public with HSR 6 – Construction, Commissioning & Handover

• Civils Maintenance (MAC) Handover Documentation & Certificate

• Technology Maintenance (TechMAC)Handover Documentation & Certificate

• Operational (RCC) HandoverDocumentation & Certificate

Post G 7 – Closeout • POPEUpdate/Refine...• As built Documentation• Health & Safety File• Technology Commissioning Plan• Civils Maintenance (MAC) Handover

Documentation & Certificate• Technology Maintenance (TechMAC)

Handover Documentation & Certificate• Operational (RCC) Handover

Documentation & Certificate

* It is assumed that managed motorway schemes will use the reduced lifecycle of PCF for single option projects.

Table A5-1 - Mapping of MM Lifecycle to PCF Stages & CTI


IAN 165/12 of 62 Apr 2012

Appendix 6 – Stage Transition Criteria and the use of CTI


IAN 165/12 of 62 Apr 2012

--

PCF Stage 2‘Options Selection’

PCF Stage 5‘Construction Prep’

Stakeholder key1. Delivery Partner2. Scheme Designer3. NRTS4. TechMAC5. MAC6. MP Project Manager7. NDD Senior User8. TTD Service Delivery Manager9. NDD Service Delivery Manager10. TMD RCC Lead Ops Manager11. NTOC

C&H Stage A

Agreement on process/options for Commissioning & Handover

NDD Senior User

Accountable: 6Responsible: 1,2

Agreement on MM Scheme lifecycle

NDD Senior User


Develop MoU/DLOA

NDD Senior User

Accountable: 6Responsible: 1

Develop, agree and sign‐off PCF products (Appendix 5)

C&H Stage C

Complete end‐to‐end systems commissioning (inc. SAT3)

NDD Senior User


Ensure SI are in place (unless Stage D is undertaken)

NDD Senior User


Complete RSA Stage3

NDD Senior User


Initiate operator induction and training to new systems

N/A Accountable: 6Responsible: 1

Update Documentation (MCH1349 & BD 62/07)


C&H Stage B

Review and refine MoU/DLOA form Stage A

NDD Senior User

Accountable: 6Responsible: 1,8, 9, 10

Review and refine C&H options from Stage A

NDD Senior User


Install all outstation infrastructure


Develop, agree and sign‐off PCF products (Appendix 5)

As per the R&R within each PCF Template

Initiate operator induction and training


Complete SAT1 and SAT2 (Appendix 3)

N/A Accountable: 6Responsible: 1,2

Produce Documentation (MCH1349 & BD 62/07)


C&H Stage GFurther calibration, tuning and system improvements as req.

NDD Senior User


NOMS setup and operational


Sign‐off PCF products (Appendix 5)


Activity Guide

Activity

NDD Senior User

Accountable: YResponsible: Z

Key Stakeholder Accountable*

Role of NDD Senior User. Colour Coded.

Key Stakeholder(s) Responsible*

* Refer to Stakeholder key

AcronymsC&H: Commissioning & HandoverCTI: Consent to ImplementDLOA: Detailed Local Operating AgreementHSR: Hard Shoulder RunningMM: Managed MotorwaysMoU: Memorandum of UnderstandingMSP: Maintenance Service ProviderNOMS: Network Occupancy Management SystemPCF: Project Control FrameworkRCC: Regional Control CentreR&R: Roles and ResponsibilitiesRSA: Road Safety AuditSAT: Site Acceptance TestsSI: Statutory InstrumentsTM: Traffic Management

C&H Stage D(Optional)

Complete operator induction and training


De‐mobilise Site/ Contractor/ TM (where possible)

NDD Senior User


Conduct MSP training


Ensure the following conditions have been met

NDD Senior User


Queue detection is accurateNumber / freq. of false alarms tolerableSignal set/removed in a credible mannerSystem faults are at acceptable levelsPerformance stable baseline established

C&H Stage EDe‐mobilise Site/ Contractor/

TM (If no Stage D)

NDD Senior User


Complete operator training (RCC ready for HSR Trials)





NDD Senior User


Queue detection is accurateNumber / freq. of false alarms tolerableSignal set/removed in a credible mannerPerformance stable baseline established

C&H Stage F

Complete operator training (RCC ready for HSR Operations)





NDD Senior User


System faults at acceptable levelsPerformance stable baseline establishedHSR Trials deemed successful

CTI Stage F Sign‐off

CTI Stage E Sign‐off

CTI Stage D Sign‐off

CTI Stage C Sign‐off

NO CTI Sign‐off

NO CTI Sign‐off

R

Role of the NDD Senior User

MP MP/NDD/TMD

Directorate Lead

A

C

I

Responsible

Accountable

Consulted

Inform


PCF Stage 7‘Close out’

Post Stage GFurther calibration, tuning and system improvements as req.

NDD Senior User


Complete RSA Stage 4 (12&36month)

NDD Senior User


Sign‐off PCF products (Appendix 5)


NO CTI Sign‐off

PCF Stage 6‘Construction’

PCF Stage 6‘Commissioning’

PCF Stage 6‘Handover’

Stage Transition Criteria

Complete RSA Stage3 (if not compete in Stage C)

NDD Senior User


N/ANo SU involvement required

Figure A6-1: Stage Transition Criteria and the use of CTI


IAN 165/12 of 62 Apr 2012

Appendix 7: IAN 165/12 - Amendments required to this IAN when used in projects carried out under English DBFO schemes. When used on the M25 DBFO Scheme, this IAN is to be amended as follows:

Para No. Description

Al occurrences Delete “Contractors” and insert “contractors” unless otherwise stated

Delete “Contractor” and insert “contractor” unless otherwise stated

Delete “Maintenance Service Providers” and insert “maintenance service providers” unless otherwise stated

Delete “Site Data” and insert “site data”

Figures 1 to 6, 8 and A3-1

In Stage G, delete “ to Agency”

1.6

Further Support

Delete “a target” and insert “the scheme” Insert “and copied to the Department’s Nominee” after “[email protected]”

Table 4

Lifecycle of a Managed Motorway Scheme

In row G, delete ““ to Agency”

2.4

Commissioning and Handover

last paragraph,

Delete ““ to the Agency” Delete “Civils, Technology and Operations” and insert “civils, technology and operations”

2.5

Maintenance

Delete “(from Major Projects to NDD and TMD)”

4


2nd paragraph

Delete “Scheme” and insert “scheme”

5.1

System Commissioning

After “works in close liaison with ” insert “the Department’s Nominee and”

7.

Transition from Construction to Operation

Insert “and copied to the Department’s Nominee” after “[email protected]”

9.

Post Opening Optimisation

2nd paragraph Delete “Site Data Load” and insert “site data load” Delete “Site Data Designer” and insert “site data designer” Delete “Software Maintenance Contractor” and insert “software maintenance contractor”

3rd paragraph Delete “Contractors” and insert “contractor’s”

4th paragraph Insert “and copied to the Department’s Nominee” after “[email protected]”

10

Maintenance during the Lifecycle of a Managed Motorway Scheme

In forth paragraph, sub-paragraph 3, delete ““ to HA”

10.1

During Stages A - C: Maintenance during Construction



IAN 165/12 of 62 Apr 2012


10.2

During Stages D - F: Interim Scheme Specific Maintenance

3rd paragraph Delete “contracted by the Agency”

4th paragraph Delete “transferred back to the HA” and insert “the”

10.3

During Stage G: Handover to HA for Operational Maintenance

In the title, delete “to HA”

1st paragraph Delete “to the Agency”

2nd paragraph Delete “to the HA” Delete “Maintenance Service Provider(s) have ” and insert “maintenance service provider(s) has”

3rd paragraph Delete “to the Agency”

10.3.1

Maintenance Handover Procedure

In 7.2.1, delete “Maintenance Responsibilities” and insert “maintenance responsibilities” In 7.2.1, sub-paragraph ‘a)’, delete “Area” In 7.2.1, delete “Technology” and insert “technology” at both occurrences

10.5

Maintenance Requirements

1st paragraph Delete “the Agency Maintenance Service Provider(s) (MSP)” and insert “the MSPs”

2nd paragraph Delete “target” and insert “agree the scheme”

11.1

Criteria for Acceptance of Technology Infrastructure into Maintenance

In 4.9.15, delete “Scheme Manager” and insert “scheme manager”

11.2

Criteria for Acceptance of Civil Infrastructure into Maintenance

In sub-paragraph 3, delete “with the MAC”

11.4

Outstanding Defects and Faults

Delete “to the Agency (NDD and TMD),”

11.5

Defects Liability

Delete “by the Agency”

Appendix 1 – Glossary Delete Contractor and its definition


In Stage A (Pre Works) table, column 7, insert “or DBFO Co” after “MAC” In Stage B (Construction) table, column 7, insert “or DBFO Co” after “MAC” In Stage C (Systems Commissioning) ) table, column 7, insert “or DBFO Co” after “MAC” In Stage D, E & F (Operational Regime Testing - ASL, VMSL, HSR) table, column 7, insert “or DBFO Co” after “MAC” In Stage G (Operational use of Scheme / Handover to HA), delete “to HA” in the title In Stage G (Operational use of Scheme / Handover to HA) table, column 7, insert “or DBFO Co” after “MAC” In Stage G (Operational use of Scheme / Handover) table, delete “(of 12 months post formal handover)” in the description of ‘ID’ 10

A3.2

Systems Commissioning

2nd paragraph

Delete “Site Data Load ” and insert “site data load”


IAN 165/12 of 62 Apr 2012

When used on all other English DBFO Schemes, this IAN is to be amended as follows:


Al occurrences Delete “Contractors” and insert “contractors” unless otherwise stated

Delete “Contractor” and insert “contractor” unless otherwise stated

Delete “Maintenance Service Providers” and insert “maintenance service providers” unless otherwise stated

Delete “Site Data” and insert “site data”

Figures 1 to 6, 8 and A3-1

In Stage G, delete “ to Agency”

1.6

Further Support

Delete “a target” and insert “the scheme” Insert “and copied to the Department’s Nominee” after “[email protected]”

Table 5

Lifecycle of a Managed Motorway Scheme

In row G, delete ““ to Agency”

2.4

Commissioning and Handover

last paragraph,

Delete ““ to the Agency” Delete “Civils, Technology and Operations” and insert “civils, technology and operations”

2.5

Maintenance

Delete “(from Major Projects to NDD and TMD)”

4


2nd paragraph

Delete “Scheme” and insert “scheme”

5.1

System Commissioning

After “works in close liaison with ” insert “the Department’s Nominee and”

7.

Transition from Construction to Operation


9.

Post Opening Optimisation

2nd paragraph Delete “Site Data Load” and insert “site data load” Delete “Site Data Designer” and insert “site data designer” Delete “Software Maintenance Contractor” and insert “software maintenance contractor”

3rd paragraph Delete “Contractors” and insert “contractor’s”

4th paragraph Insert “and copied to the Department’s Nominee” after “[email protected]”

10

Maintenance during the Lifecycle of a Managed Motorway Scheme

In forth paragraph, sub-paragraph 3, delete ““ to HA”

10.1

During Stages A - C: Maintenance during Construction


10.2

During Stages D - F: Interim Scheme Specific Maintenance

3rd paragraph Delete “contracted by the Agency”


IAN 165/12 of 62 Apr 2012


4th paragraph Delete “transferred back to the HA” and insert “the”

10.3

During Stage G: Handover to HA for Operational Maintenance

In the title, delete “to HA”

1st paragraph Delete “to the Agency”

2nd paragraph Delete “to the HA” Delete “Maintenance Service Provider(s) have ” and insert “maintenance service provider(s) has”

3rd paragraph Delete “to the Agency”

10.3.1

Maintenance Handover Procedure

In 7.2.1, delete “Maintenance Responsibilities” and insert “maintenance responsibilities” In 7.2.1, sub-paragraph ‘a)’, delete “Area” In 7.2.1, delete “Technology” and insert “technology” at both occurrences

10.5

Maintenance Requirements

1st paragraph Delete “the Agency Maintenance Service Provider(s) (MSP)” and insert “the MSPs”

2nd paragraph Delete “target” and insert “agree the scheme”

11.1

Criteria for Acceptance of Technology Infrastructure into Maintenance

In 4.9.15, delete “Scheme Manager” and insert “scheme manager”

11.2

Criteria for Acceptance of Civil Infrastructure into Maintenance

In sub-paragraph 3, delete “with the MAC”

11.4

Outstanding Defects and Faults

Delete “to the Agency (NDD and TMD),”

11.5

Defects Liability

Delete “by the Agency”

Appendix 1 – Glossary Delete Contractor and its definition


In Stage A (Pre Works) table, column 7, insert “or DBFO Co” after “MAC” In Stage B (Construction) table, column 7, insert “or DBFO Co” after “MAC” In Stage C (Systems Commissioning) ) table, column 7, insert “or DBFO Co” after “MAC” In Stage D, E & F (Operational Regime Testing - ASL, VMSL, HSR) table, column 7, insert “or DBFO Co” after “MAC” In Stage G (Operational use of Scheme / Handover to HA), delete “to HA” in the title In Stage G (Operational use of Scheme / Handover to HA) table, column 7, insert “or DBFO Co” after “MAC” In Stage G (Operational use of Scheme / Handover) table, delete “(of 12 months post formal handover)” in the description of ‘ID’ 10

A3.2

Systems Commissioning

2nd paragraph

Delete “Site Data Load ” and insert “site data load”