/21 Apr 2023 1

Signalling - Safety Step Up

System Safety in the delivery of Signalling Projects

To be delivered as ‘safety conversational’ and discussed within a Step Up environment1st – 12th December 2014

## Please delete this slide for onward brief ##

/21 Apr 2023 2

Signalling - Safety Step Up ConversationSystem Safety in the delivery of Signalling Projects

Delivery Lead & Lead Engineer names

/3

Signalling Projects Safety Working Group Background & Timeline• A number of system safety issues encountered on

signalling projects over the last 5 years. • Supply chain members’ concerns were raised with the

Railway Industry Association (RIA) and the Institute of Railway Signal Engineers (IRSE) in mid 2013 and mapped to investigation causes.

• These parties with NR IP met to discuss the concerns in October 2013.

• A working group was convened under auspices of the IRSE Council, and incorporated a wider representation of the rail supply industry.

• This group under the banner of the IRSE made recommendations in June 2014.

/

The IRSE and Industry Recommendations…..

21 Apr 2023 4

Build upon the use of technical stage-gates already developed for data in signalling systems, to be applied to all signalling projects, with any non-compliance to this requirement being very much the exception to the rule and treated with the seriousness it deserves

If the agreed date for passing a stage-gate (financial or technical) cannot be met, the implications (including safe assured delivery) for the planned commissioning date(s) and other critical milestones must be identified, risk assessed and mitigations addressed

Any change to the agreed/approved specification during the detailed design, construction, testing and commissioning phases should be avoided. Where change is absolutely necessary, both supplier and client must be in agreement that the impact of the change can be safely managed.

The non-sequential application of signalling design/development processes should be the exception, not the norm and when utilised shall be subject to formal risk assessment.

Rigorous change control processes must be applied to all designs issued for construction purposes (and not just AFC designs).

/21 Apr 2023 5

1. Projects need to be developed in a manner that enables and secures safe and efficient delivery.

2.Initial bolt down of scope.

3. Managed approach to change, the assessment of time and process impact and the reduction of technical risk.

What we have to ensure…..

4. Whenever the process is impacted, a reassessment and any necessary reduction of technical risk.

/21 Apr 2023 6

The Network Rail Safety Vision Statement…

The CEO’s Safety Vision Statement

#3: We will plan work to ensure that it can be done safely.

#8: We will relentlessly strive to find new ways to keep ourselves, colleagues, passengers and the public safe.

#9: We will design, construct, inspect, operate and maintain the railway to keep everyone safe.

The context of the necessary actions….

/

Planning & Integration…

721 Apr 2023

- Integrated Plans

- Include ALL Disciplines

- Includes all stage gates at a timely point before the end of that GRIP stage

- Include Inter Disciplinary Check

- Realistic & durations confirmed by stakeholders

- Sequential Working

/

A Typical Project Timeline…

821 Apr 2023

Pla

nn

ed A

ctiv

ity

Time

Pre Feasibility (GRIP 1)

Option Selection (GRIP 2&3)

Single Option Development (GRIP 4)

Detailed &Stage works Design (GRIP 5)

GRIP 6

Technical Stagegate

end of GRIP 1

Deliverable Yes/No?

Deliverable Yes/No?

Technical Stagegate

end of GRIP 3

Technical Stagegate

end of GRIP 4

Deliverable Yes/No?

DWWP & CP0077

ProcessesT- 37 & Stage Gate (GRIP5)

Deliverable Y/N?

Co

mm

issi

on

ing

Per

iod

Entry into Service

/ 921 Apr 2023

When we don’t get it right…

/

An example of a Technical Stagegate Checklist…

21 Apr 2023 10

Image Slide

Deliverable / Check Item End of GS Stagegate Output Purpose

Operational Requirements Specification

1 Pass / Fail - escalate The purpose of the Operational Requirements Specification is to provide a detailed and final definition of the Operations stakeholder‘s requirements. (To also include List of Routes)

Project HAZID 1 Pass / Fail - escalate Project HAZID to include but not limited to compatibility with rolling stock, duty of co-operation (ref GE/RT8270)

Design Decision Log 1 Pass / Fail - escalate The purpose of the design log is to record all relevant decisions on the project to create an audit trail for the evolving design.

Review level of complexity and interlocking capability

1 Low – No actionMedium / High - escalate

Review the level of complexity and capability for the technology proposed and to be altered for risk.Are sufficient resources availableHow easily can the system be alteredCan the system deliver the required outputs

Review Non Sequential Activities 1 Low – No actionMedium / High - escalate

Review the risk imported or to be imported due to non sequential activities already taken place or those planned to take place during the next phase.

Review current status of source records

1 Low – No actionMedium / High – escalate

Review the availability of source records to allow this scheme to move forwards. This shall also include the current status of the signalling deficiency register.

/21 Apr 2023 11

The Common Safety Method – Risk Evaluation and Assessment Flow Chart

HAZID

Risk Evaluation

& Assessment

For scope changes and before introducing non sequential working identify risks and controls using this established process.

/

What to consider about your project works as you return to the workplace…

21 Apr 2023 12

1. Is the scope fixed and understood?

2. Have you and are you managing the risk from change?

3. Recognise non-sequential working, assess the imported risks to safe delivery & control…

AND… Are you in a fit state to progress?

/

Presentation Title: View > Header & Footer

21 Apr 2023 13

Thank You for Listening…Questions……?