Infrastructure Projects

ATO over ETCS Achieving Metro Headways on the Mainline

Jon Hayes November 2017

1 Paul Bates FIET FIRSE 1959 - 2017

2 - Objectives

To Finsbury Park, Stevenage, L Peterborough & NE M C M E ML • Reduce overcrowding on Kentish Town Thameslink and other commuter

services Dock Junction

• Reduce overcrowding to

Underground. St Pancras Kings Cross Intl

• Reduce the need for interchange Farringdon

City between main-line and LUL train Thameslink

Cannon St services Blackfriars Rive r Tha mes

H s London e o l b m o Bridge a r • Provide for the introduction of h n T s

r e S v i o ut R h E new cross-London services, so as te rn Elephant L in improving public transport & Castle es N. E Jct accessibility in South East Deptford / S Bermondsey Greenwich Line New

e Cross New Cross / th n England u i Loughborough Jct, o L Gate / Lewisham n S o Herne Hill d Croydon n Peckham, o L & Dulwich / Sussex Brixton Coast 3 Objective Delivery

16 tpph 24 tpph thru’ Core thru’ Core

2016 Thameslink Network 2018 Thameslink Network

May / December 2018 timetables introduce a substantial change to train services across the South East IRSE Visit November 2014 Thameslink - Overview

• Network infrastructure • Rolling stock programme •Major re-franchising exercise to introduce investment •New Siemens fixed formation phased “Thameslink, Southern, •Signalling, Track, Civils, E&P trains - 55 x 12-car units and 60 x Great Northern” franchise •Works on 5 Routes 8-car units •Southeastern largely unaffected

The Thameslink Programme is a government funded initiative to increase capacity on commuter routes into and across London, and to remove key bottlenecks through the re-development of and the introduction of a new high frequency service through Central London, operated by new 8 and 12-car trains.

14-Nov-14 5 5 Increasing capacity - Additional Block Sections

ETCS status used to modify signal aspects

Unfitted or Non-Communicating Train

ETCS Train in FS

ETCS MA EOA SvL

6 6 Increasing Capacity - ATO over ETCS Concept • ATO supervises to achieve journey time using least power, but within ETCS Protection Curve (EB) – warning curves suppressed.

• Detailed ATO interface/operation specified by the train manufacturer

• Onboard track map

• Event driven interface (packet 44 via RBC)

• Ability to modify dwell/run-time

• ATO brake rate modifiable via packet 44

• Balises used for stopping accuracy at platforms

• +/-0.5m accuracy specified (no Platform Screen Doors)

7 7 IV&V Approach

•IV&V development involves NR, Siemens and GTR •Initial testing in SI Lab and test track (ENIF)

• NR “2.3.0d” reference train & Thameslink train Test and Validation Outline – Alternative 6 - September 2012 Contract award Date System Int. Lab HNIF Tr T C Core Tr T C Dec12 Set to work Jan13 2.3.0d / Base RBC Feb13 Single Train Running Mar13 ETCS Apr13 Multiple Train Running May13 ETCS Jun13 Soak testing Jul13 Upgrade and Aug13 new EVC & RBC Sep13 Set to work Oct13 Single Train Running Nov13 ETCS Dec13 ATO Integration Test Jan14 Multiple Train Running Feb14 ETCS/ATO Mar14 Soak /Ops test Apr14 •All software/data initially tested in Static Lab May14 Rules Validation Jun14 Lab maint. / upgrade Jul14 Set to work Aug14 Integration regression Sep14 test of updated product Oct14 and data (V1) Balise Installation Nov14 Configure for HNIF Install TLP Configuration And test Dec14 HNIF Test Scenarios Jan15 base results Set to work (20) 313 5 15 Feb15 Single Train Running (20) 313 15 5 Mar15 ETCS (20) 313 10 10 Remainder of core Apr15 Regression test HNIF & (20) 313 20 installation/test May15 Core Infra. Set to work Jun15 (V2) Regression Test (5) 313 4 1 Jul15 Set to Work (12) 313 8 4 Aug15 Single Train Running (12) 313 10 2 Sep15 ETCS (12) 313 10 2 Oct15 Set to work (20) 700 5 15 (9) 313 8 1 Nov15 Single Train Running (20) 700 15 5 Infra Performance Test (12) 313 8 4 Dec15 ETCS (20) 700 10 10 Jan16 ATO Integration Test 700 15 5 •All dynamic tests first run at ENIF. Feb16 Mar16 Two Train Running (20) 700 15 5 Set to Work (12) 700 8 4 Apr16 ATO Ops & Stopping 700 15 5 Single Train Running (12) 700 10 2 Accuracy (20) May16 ETCS (9) 700 8 1 Jun16 Multiple Train Running (12) 700 8 4 Jul16 & Performance Test (12) 700 8 4 Aug16 ATO testing (12) 700 11 1 Sep16 (12) 700 11 1 Oct16 Regression Test (12) 700 8 4 Nov16 ETCS/ATO Rules Validation (12) 700 10 2 Dec16 (V3) (9) 700 6 3 Jan17 Regression Test ETCS (12) 700 8 4 Feb17 (V3) (12) 700 6 6 Mar17 ETCS Commissioning (2) 700 2 2 Apr17 Regression test May17 ATO /ETCS (V4) Jun17 Regression Test (V4) (12) 700 8 4 Jul17 ATO commission (1) 700 1 Aug17 Sep17 Oct17 Nov17 Dec 17 Jan 18 20TPH Feb 18 Mar18 Apr 18 Regression test May 8 ATO /ETCS (V5) Jun 18 Regression Test (V5) (12) 700 8 4 Jul 18 Aug18 •Only uses Core for “sign off” tests or geographicalSep 18 “tuning” •Software drops (6 increments) planned in.

Testing commenced Jun 13 for a Dec 17 Entry into Service

8 Test Cases

11-Jul-18 9 Systems Integration Laboratory

10 ENIF – ETCS National Integration Facility

11 11 ATO Testing in “The Core”

12 12 Learning Points

• Record as much data from different sources as possible (3 people in a cab will generate at least 4 opinions of what happened!) • Onboard (JRU, DMI) • Infrastructure (RBC, Interlocking, Control, GSMR) • Every hour of testing generated 4 to 6 hours of analysis work. • Maximise testing away from the operational railway. • Confirm how ‘representative’ of the real world any simulation is. • ATO over ETCS is capable of delivering 30tph with careful system design.

13 Thank You

14