The Great Western Electrification Programme -

Collaborating for Success

Tuesday 10th September INCOSE – Railway Interest Group

Nassar Majothi – Parsons Brinckerhoff

Joe Silmon – Atkins

Acknowledgements

• What is the GWEP? • The Atkins / Parsons Brinkerhoff Team – LDO • The integration challenges • SE Tools and techniques

Overview

The Route London and Bristol, including Newbury and Oxford, by 2016 and to Cardiff by 2017

New trains Enabling the route for the new fleet of Intercity Express Trains

Capacity More seats and faster journeys Environment Reduction in emissions, carbon and local

environmental impact Economic growth

Stimulate economic growth across the region by better connecting towns and cities

Reduce costs Higher overall reliability, lower operations and maintenance costs

Programme Goals

1. High Output Plant System – Construction Technology

2. New Product Technology – Series 1, FEDs. IPC, RATS

3. 3 new Grid Supplies

4. Circa 50 Local Auto Transformer/Switchgear Sites

5. 22,000 OLE Support Structures

6. 1000 Km of Wiring

7. 150 Structures to gauge clear (reconstructions, track lowers, jacking; awnings, tunnels, demolisions)

Programme Scope

Programme Scope – Innovation

The GWEP Route

Dec 2017 Sept 2015

1. Network Rail Investment Projects – The Client 2. Network Rail Route & EPDG 3. Amey – The Construction Contractor 4. Atkins & Parsons Brinckerhoff – The Lead

Design Organisation 5. Other Designers 6. Furrer & Frey – Series 1 Development 7. Windhoff – High Output Train

The Delivery Team

What is a Lead Design Organisation?

The LDO responsibility for systems integration

The LDO shall... enable the co-ordination and integration of engineering, designs, construction and commissioning produced by the LDO and others and to provide on going site design/engineering support and validation of the works during implementation and commissioning through to Entry into Service (EIS).

The LDO responsibility matrix

1. Market forces

2. Breadth of skills required

3. Size of team

4. Efficiencies

5. Innovation

6. Multi-discipline Approach

Why a JV and the drive for collaboration

Systems Integration

Design Integration

Design Integration

Design Integration

EDMS / CAD Management System

Document Control

Project, Design & Engineering Processes

PM, Project Controls & Schedule Management

Design Integration

Construction Integration

Operational Integration

Approach to Systems Integration

GRIP 4

GRIP 5

GRIP 3

GRI

P 6

GRIP 2

GRIP 1

LDO – Picks up design and integration (inc V&V) at start of GRIP 4

EIS – Entire GW Route – Complete

EIS – Route Section 3

GRI

P 7

EIS – Route Section – Staged

Great WesternElectrificationProgramme

Test

ing

& Co

mm

issio

ning

EIS

Application Design

In Service Monitoring

Inspection, Test & Comission Requirements

Route Section Design Requirements

System Requirements (PRS, Strategies & AIPs)

Operational and Performance Requirements (Client Functional)

Cons

truct

ion

Series 1

Series 1 – T&C

Series 1 – SRP Certificate

Series 1 – Approved Product Catalogue

Series 1 – Requirements

Series 1 – Product Development

Series 1 – Specification

Intergated Protection &

Control

Fixed Earth Devices

Products and Technology Development – GRIP 7/8 > Feed into GWEP GRIP4

Products and Technology Development: Series 1, IPC & FEDS, T&C on RS3 – V&V needed

Other NR GW Project & Programmes: Delivery for GWEP – V&V needed

External Project & Programmes: Delivery for GWEP – V&V needed

GRIP 8

NR Corporate / Route NR GWEP Lead Design

Organisation

High Output Construction Contractor

Conventional Construction Contractor

Other Design Organisations

The Challenge of Multiple V’s

CROSSRAIL WEST

Fixed Telecoms Network

Design stage

GRIP4-8Discipline/function

Systems & AssuranceOriginator

Checker

Reviewer

AuthoriserDateRevision

Title

LDO TECHNICAL INTERFACE MANAGEMENT - PROGRAMME LEVEL BOUNDARY DIAGRAM (DRAFT)

Number

[Atkins & Parsons Brinckerhoff]

Western Mainline Signalling Renewals (WMSR)

Western Building and Civils

Electrification Plant Design Group(EPDG)

National SCADA

National Traffic Management/ Regional

operating centres

Bristol+ Oxford Redevelopment

NETWORK RAIL INFRASTRUCTURE PROJECTSNETWORK RAIL (NR)

GREAT WESTERN ELECTRICIFICATION PROJECT

The purpose of diagram is to identify and visualise the organisational and programme interfaces to be considered by the LDO within its interface scope of work.

Cross Country

First Great Western

Heathrow Express

TRAIN OPERATING COMPANY (TOC)

FREIGHT OPERATING COMPANY

REGULATORY BODIESHealth Safety

Executive (HSE) HIGHWAYS

Highways Agency

ELECTRICAL UTILITIES, GAS,WATER &TELECOMS

Gas Company?

BT & other telecoms

companies?

Water Company?

DB Schenker

GB Railfreight

DirectRail Services

LOCAL RESIDENTS AND COUNCILS

NETWORK RAIL GREAT WESTERN ROUTE

Route Maintenance and Renewals (Track)

NETWORK RAIL WALES ROUTE

Country Land Owners

Association

Arriva Trains Wales

Environment Agency

British Transport

Police

National Grid

Department for Transport

Councils including Basingstoke and Deane, Reading, Bath & North East Somerset, Bristol City, Gloucestershire County, Hampshire County, Oxford City, Oxfordshire County, Reading Borough, Somerset County, South Gloucestershire County, Surrey County, Swindon West Berkshire , Wiltshire, Windsor and Maidenhead Royal.

XXXX - Refers to Stakeholder

XXXX

HMRI

Office of Rail Regulation (ORR)

Scottish & Southern Energy Other DNOs

ERTMS /European Train Control System(ETCS)

Programme

Colas

XXXX-Refers to Great WesternElectrification Programmeinternal structure

- Refers to Workstream or programme

Legend

Operations(Route Control & Signalling

Control)

Purpose:

Amey

AGILITY TRAINS

Station Renewals and Upgrades

NOTE THAT THIS DRAWING

English Heritage

Intercity Express Programme (IEP)

(Network Rail)

W12 Gauging Enhancement Programme

Filton Bank 4-Tracking

GW

EP

/PIF/3100

GWEP/PIF/0100

GWEP/PIF/2300

GW

EP

/PIF/2700

GWEP/PIF/3000 GWEP/PIF/3200

GWEP/PIF/1800

GWEP/PIF/1400

GWEP/PIF/1100

GWEP/PIF/1300

ERTMS - European Rail Traffic Management SystemDNOs - Distribution Network Operators

GWEP/PIF/1600

GWEP/PIF/1700

GWEP/PIF/1500

GW

EP

/PIF/2900

GW

EP

/PIF/2800

Electric Spine ElectrificationIEP Depot/stabling

Construction programme

New IEP Trains

Oxford Station Redevelopment

GWEP/PIF/1000

GWEP/PIF/0200 GWEP/PIF/0800

Welsh Government

GWEP/PIF/1200

GWEP/PIF/0700

Arriva Crosscountry

Port Talbot West Re-signalling

Electrification Development Programmes *

*- Electrification Development Programmes includes Thames Valley Lines, Reading to Basingstoke, Cardiff to Swansea,

GWEP/PIF/1900

GWEP/PIF/2100

GWEP/PIF/2200

Integrated Protection and

Control

GWEP/PIF/2400

GWEP/PIF/2500

Fixed Earthing Devices

TECHNOLOGY AND PRODUCT DEVELOPMENT

Rail for London (including future Crossrail TOC)

Track Renewals

GWEP/PIF/0300

Series 1 - Electrification Design Development review

Series 1

Electrification Alliance

IEP and Electrification works

(Associated NR infrastructure works)

Route Clearance Structures

Railways Heritage Trust

Crossrail on Network Works

NR Crossrail Infrastructure Paddington- Maidenhead

Route Maintenance and Renewals (Track)

XXXX - Further investigation required

- Her Majesty's Railway InspectorateHMRI

Newport / Cardiff Area Signalling Renewals(CASR

and NASR )

RASR (Electrification +

Resignalling)

RASR - Reading Area Stations Renewals

Natural England

South West Trains

Freightliner Heavy Haul

FreightlinerIntermodal

Track AlignmentPaddington - Cardiff

Operations(Route Control & Signalling

Control)

Electrification Plant Design Group(EPDG)

GWEP/PIF/2000

GWEP/PIF/2600

GWEP/PIF/0400

GW

EP

/PIF/0500

Network Rail Central/Corporate

Engineering

Network Rail Environment and

SustainabilityROSR

GWEP/PIF/0600

GWEP/PIF/0900

3 Position Load Break Switch

A Complex Set of Programme Interfaces

A Complex Set of Programme Interfaces

Maintenance

Signalling

Reading

Electrification

IEP

Electrification

Crossrail West

IEP

Electrification

Electrification

IEP

Sign

allin

g

Elec

trifi

catio

n Signalling Signalling

Signalling Wales Western

Track Renewals

7 Day Railway

National Stations Improvement Programme

Other Enhancements

CASR NASR

IEP Depot Filton Bank IEP Depot

North Pole

Kensal Green

Swindon to Kemble

CRL Depot OOC

HS2 Didcot

Melksham

Imperial Park

Oxford Re-modelling

Bristol TM Re-modelling

ERTMS

Engineering Challenges

Case A: LDO undertakes all design work for the route section

Case C: LDO undertakes no design work, all design is done by other organisations. LDO retains integration accountability.

LDO CEMNR DPE

LDO Project Manager

LDO Discipline

A CRE

LDO Discipline

B CRE

Others Org Discipline

C CRE

NR Discipline

A PE

NR Discipline

B PE

LDO Discipline

C PE

Others Org CEM

Others Org CEM

NR DPE

Others Org Discipline

A CRE

Others Org Discipline

B CRE

Others Org Discipline

C CRE

NR Discipline

A PE

NR Discipline

B PE

LDO Discipline

C PE

LDO CEM

LDO CEMNR DPE

NR Contract Project

Manager(s)

LDO Project Manager

LDO Discipline

A CRE

LDO Discipline

B CRE

LDO Org Discipline

C CRE

NR Discipline

A PE

NR Discipline

B PE

LDO Discipline

C PE

Case B: Design work is shared between the LDO and other organisations. LDO retains integration accountability.

Others Org CEM

Others Org CEM

NR Discipline

B PE

LDO CEM

Others Org CEM

Formal Engineering Flow and Information Exchange

Formal Contractual Communication and Documentation Flow

Engineering Information Exchange

Network Rail

Lead Design Organisation

Others Design Organisations

NR Contract Project

Manager(s)

Other Orgs Project

Manager(s)

NR Contract Project

Manager(s)

Other Orgs Project

Manager(s)

Governance Challenges

SYSTEMS ENGINEERING TECHNIQUES

Requirements management – guiding principles

Requirements drive the design Provide requirements to designers at the start – reduce retrospective verification

GRIP3 design contains numerous requirements

Huge value in Approved in Principle designs

Requirements are not confined to the PRS, they are defined and refined by design GRIP4 and GRIP5 designers write new requirements that are relevant to the next stage

Requirements relate to the system in different ways Need to ensure each design package only sees the applicable requirements

Avoidance of unnecessary work Reject non-value-adding requirements

Rich traceability Record and justify how requirements were evolved through the life-cycle

20

Challenge 1: a distributed system

RequirementMinimise environmental

impacttype a)

RequirementW10 structure gauge

type b)

RequirementNo impact piling near

Mr X’s housetype c)

PhysicalOLE Production Unit GW/00

PhysicalOLE Production Unit GW/01

PhysicalOLE Structure

GW/00/01

PhysicalOLE Structure

GW/00/02

PhysicalOLE Structure

GW/01/01

Each of these links must be independently verified for full technical assurance

traces to

traces to

traces to

Multi-level applicability of requirements Requirement

Type a) requirementAll elements

traces toPhysical

T00 Generic design element

PhysicalT03 OLE Structure

PhysicalGW/00/01 structure

is a

is a

RequirementType b) requirementAll elements of type

RequirementType c) requirement

location specific

traces to

traces to

Inferred applicability of requirements

• Inference: If A →B and B→C then A→C

• If the requirement applies to OLE structures, and GW/00/01 is an OLE structure, then the requirement applies to GW/00/01.

PhysicalT03 OLE Structure

PhysicalGW/00/01 structure

is a

RequirementType b) requirementAll elements of type

traces to

Inferred trace

Requirements that apply to each element

• Now three logical conditions are brought together to infer the traceability

• Useful for global requirements and aspirations e.g. environmental impact

• Use sparingly to avoid overloading designers!

RequirementType a) requirement

All elementstraces to

PhysicalT00 Generic design

element

PhysicalT03 OLE Structure

PhysicalGW/00/01 structure

is a

is a

Inferred trace

Challenge 2: Multiple requirements sources

• 65 requirements source documents from GRIP3

• ~5000 requirements

• Definition of specialist requirements ongoing

Requirements management & traceability

CLI

EN

T

STA

KE

HO

LDE

R

SA

FETY

RA

M

EM

C

ER

GO

NO

MIC

S

EN

VIR

ON

ME

NT

INTE

RFA

CE

DE

SIG

N

Design progression & change management

Verification and validation

Acceptance

Challenge 3: Evolution of assurance through the life-cycle

Integrating requirements with design

27

Project RequirementSpecification

GRIP3 output document

GRIP6 Inspection, testing &

Integration reports

GRIP4 coordinated requirement specification

GRIP4 output document

GRIP5 output document

GRIP7 Commissioning

reports

Traceability by Network Rail requirements

manager

Sponsor & Client

requirements

Traceability by LDO capture and

analysis

Traceability by LDO capture and

analysis

Traceability by LDO design teams

Owned and traced by LDO design

teams

e.g. Approved in Principle designs, EMC strategy, etc.

e.g. Form 001

Leaf-level requirements

RequirementOriginating

requirement 1

RequirementOriginating

requirement 2

RequirementOriginating

requirement 3

RequirementDerived requirement

4

RequirementDerived requirement

5

supersedessupersedes

RequirementDerived requirement

6

supersedes

DocumentProject specification

traces to traces to traces to

Set of leaf-level requirements

A simple rich traceability metamodel

Satisfaction argument

Requirement [TRAK]a requirement

Requirement [TRAK]a requirement

Document [TRAK]a document

satisfies

traces toIssue (UML)

argument of necessity

Change (UML)argument of sufficiency

arises from

resolves

implementsPhysical [TRAK]

a physical[TRAK]

traces to

Document [TRAK]a document

documented by

addresses

Direct traceability Rich traceability

Audit trail

“Pilot’s manual” instruction flowcharts

• Guide to contents of detailed documents

• Indicate involvement of multiple actors

• Easy to test logic

XLS

XLS

Syst

ems

and

assu

ranc

e te

am

Scrip

tSC

R00

3

Design team

1.1

Capture derived requirements

Design phase n baseline

Start of design phase n+1

Scrip

tSC

R00

1 1.2

Import requirements to database

XLSHS2 originating requirements baseline

Man

ual

1.3

Create traceable requirements structure

1.4

Review structure

Scrip

tSC

R00

2 1.5Flow inherited applicability to

individual elements

1.6

Generate element verification templates

XLSCompleted

capture sheets

XLSElement verification sheets

Enterprise Architect

Simplified architecture framework

31

traces to{interface req}

is configured with

interfaces with

VP03: Geographical

asset hierarchy

VP06: Element classification

VP04:Functional

model

VP05: System

interfaces

Requirementa requirement

Documenta document

supersedes

traces to

Satisfaction Argumentreason for changing/refining requirement

traces to

traces to

SystemGeographical area

PhysicalAsset [specific]

is configured with

is configured with

is configured with

SystemRoute

is a

SystemRailway system/

subsystemis configured with

SystemContext

SystemEnvironment/

external system

is configured with

is configured with

is configured with

interfaces with

traces to

traces to{global req}

traces to{area/section req}

traces to{localised/site req}

traces to{discipline/asset type req}

interfaces with

VP01: Requirement

capture

VP02: Requirement tracing, refinement

and applicability

VP07: Asset checklist

verify

Collaborative tools for SE • NR DOORS environment (via Citrix):

– Client reporting of V&V

– Mirroring of developed traceability downstream of PRS

– Mastering of traceability upstream of PRS (Client & Sponsor requirements)

• LDO Enterprise Architect environment (on the cloud, eventually...)

– Mastering of traceability downstream of PRS (GRIP3 and GRIP4 output requirements)

– System architecture / Interface modelling

– Safety risk assessment (WIP)

32

Interface Management

Route Section Interface Registers

Master technical interface registers

Top level technical interface register

System Architecture input

Programme Boundary

Programme Interface register

I/F Reqs & ICDs

Interface Management

Interface Reference Number

Interface Description Responsible Discipline From To Technical

ComplexityInternal/E

xternal Schedule Sum Total

GWEP/TIF/0101 Structural load bearing of OLE for design of OLE support structures. OLE Overhead Line Equipment (Catenary) OLE Supporting Structures 1 2 1 4

GWEP/TIF/0102 Physical clearance between OLE supporting structure and catenary. OLE Overhead Line Equipment (Catenary) OLE Supporting Structures 1 1 1 3

GWEP/TIF/0103 OLE catenary interface between the FEDs and motorised switches. OLE Overhead Line Equipment (Catenary) Distribution-Power Supply 1 1 2 4

GWEP/TIF/0104Physical location coordination of OLE cables and cable route with respect to telecoms cables and equipment.

OLE Overhead Line Equipment (Catenary) Telecoms System 1 1 1 3

GWEP/TIF/0105 Physical location coordination of OLE cables and cable route with respect to telecoms equipment. OLE Overhead Line Equipment (Catenary) Telecoms System 1 1 1 3

GWEP/TIF/0106Position of signals with respect to OLE (coordination of signalling scheme planning with respect to OLE layouts).

OLE OLE Layout Signalling System 1 2 2 5

GWEP/TIF/0107 Interface of Traction distribution equipment with SCADA for monitoring. OLE Distribution-Power Supply SCADA 2 2 2 6

GWEP/TIF/0108

Compatibility of OLE earthing and bonding with Earthing and Bonding of other disciplines earthing and bonding(inline with overall earthing and bonding strategy).

OLE Overhead Line Equipment (Catenary) and OLE Supporting Structures Earthing & Bonding 2 2 1 5

GWEP/TIF/0109 Electromagnetic Compatibility of OLE with respect to other discipline subsystems.(Internal) OLE Overhead Line Equipment (Catenary)

and OLE Supporting StructuresElectromagnetic Compatibility (EMC) 2 1 1 4

GWEP/TIF/0110 Electromagnetic Compatibility of OLE with respect to other discipline subsystems.(Third party) OLE Overhead Line Equipment (Catenary)

and OLE Supporting StructuresElectromagnetic Compatibility (EMC) 2 2 1 5

GWEP/TIF/0111 Heights and staggers of the OLE Catenary with respect to track structures. OLE Overhead Line Equipment (Catenary) Track Structures (formation and

drainage) 1 1 2 4

A receptive environment to SE • “You guys are so crucial”

• “If you meet any resistance, let me know straight away”

– LDO Project Director (a civil engineer)

• “We have a golden window to achieve a requirements-led design”

– LDO Engineering Director (a mechanical engineer)

• “Oh yeah, we’ve done requirements capture before. No problem”

– Discipline leads (several)

• “and of course, we’ll be producing a verification report for the design”

– Route Section design manager (a mechanical engineer)

35

Work in progress...

1.Reliability, Availability & Maintainability 2.Testing & Commissioning Planning 3.Entry Into Service Planning 4.Safety Assurance & Safety Case Development 5.Operational & Maintenance Development

Conclusions

1.GWEP has set off with a systems engineering – the challenge is to embed it and keep it going

2.Systems Integration / engineering is a core responsibility for the LDO and is facilitating wider collaboration

3.Team approach working jointly with NR and all partners

4.Collaboration is a necessity for good systems engineering on major programmes