Traffic Management Progress and Next Steps. Andy Bourne Digital Railway Programme

Size: px
Start display at page:

Download "Traffic Management Progress and Next Steps. Andy Bourne Digital Railway Programme"

Transcription

1 Traffic Management Progress and Next Steps Andy Bourne Digital Railway Programme 1

2 Why Traffic Management Matters Number of incidents has decreased but the delay per incident has increased. 2

3 Components of the Digital Railway The Digital Railway brings together systems, technology, business and people change in an integrated way Industry Skills, Capabilities and Business Change Builds capacity and capability and develops expertise. Enables the workforce and industry to adopt new technologies and ways of working, build digital capabilities and maximise the benefits of the overall systems. Safe Separation Train System European Train Control System (ETCS) Allows trains to run closer together and to travel at their best speeds whilst maintaining safe braking distances. Train Movement Control Connected Driver Advisory Systems (CDAS) + Automatic Train Operation (ATO) Provides decision support to drivers in the cab so that they have the information they need at the right time to boost performance and safety. ATO progressively automates this. Traffic Management (TM) & Reliability Growth (TM & DRACAS) Maximises performance as trains flow across the network, maximising the throughput that Infrastructure can support and adapting in real-time as network conditions change to aid rapid recovery. Telecommunications + Data Through Fixed Telecom Network (FTN) and mobile network (FTMX), will underpin and connect all these systems. Smart Infrastructure Through Remote Condition Monitoring technologies which will improve performance, reduce disruption and improve safety. 3

4 Types of Traffic Management 1 ISOLATED (Online Decision Support Tool) Inputs (e.g. timetable, train locations/delay) TM (Plan/Replan) Signalling Control Replacing manual system used to plan/replan train service 4

5 Types of Traffic Management 2 INTERFACED / INTEGRATED Inputs (e.g. timetable, train locations/delay) TM (Plan/Replan) Signalling Control Semi or fully automatic implementation of revised plan 5

6 TM Technical Interfaces Business Systems CDAS Other TM systems TM User S&C Control 6

7 Data Integration via LINX LINX deals with: Business Systems TM Business Systems TM- CDAS TM-S&C TM-TM LINX CDAS S&C TM B User TM A TM-C SC SC SC 7

8 User Integration Options: HMI tweaks to full planning layer LINX CDAS S&C TM B User TM A TM C SC SC SC 8

9 Signal Control Interface (where Interfaced TM) LINX CDAS S&C TM-TLP User TM Sussex TM-Kent Options: Proprietary v standards based SC SC SC 9

10 Business Change New equipment (maintenance) New terminology Changes to ways of working - Evolutionary - Pod working Training Collaboration Fundamental to successful delivery. 10

11 Early Schemes Implementation of LINX Evolution of requirements Lessons Learned Better understanding of benefits 11

12 Current Schemes 1 st Deployment Thales Aramis System Two locations : Wales and Anglia route Live in Wales (timetable deconfliction) Not yet live on Anglia Awaiting further software modification from Thales Commissioning dates by 31/12/18 12

13 Wales (Cardiff) Scope Key: Isolated TM Interfaced TM Integrated TM ETCS Level 2 without signals ETCS Level 2 with signals Conventional infrastructure upgrade Treherbert Aberdare Merthyr Tydfil Rhymney Ebbw Vale Fishguard Maesteg Cwmbran Gloucester Cardiff Pilning Milford Haven Pembroke 13 Swansea 13

14 Anglia (C2C) scope 14 14

15 Current Schemes Thameslink Hitachi Tranista System Thameslink Route north and south of core (see next slide) Live for training/familiarisation Commissioning dates from April 2019 to November 2020 (see next slide) 15

16 Geography Background Derby York Terminals deployed to key control and signalling locations across the Thameslink network System built: functionally in three major stages Prior day re-planning King s Cross Real time (to control) West Hampstead Real time (to signalling) Geographically in two major stages London Bridge Stage 1 - Luton North Crystal Palace KICC Stage 2 East Coast, London Bridge, Kent, Brighton Main Line Victoria Core system development completes after Stage 1; Stage 2 is just a geographic extension (more data) NR Route teams developing an entry into service strategy Stage 1 aligns with functional builds TB ASC TBROC 16 Stage 2 under development (geographic) TBROC Ashford

17 Current Schemes Western Trial using Resonate Luminate System Location : Paddington to Bristol on Western route Went live 10 th June 2018 Further updates during trial Assessment of business benefits Decision on leaving in June 2019 Payments based on performance 17 17

18 Western TM Scope Key: Isolated TM Interfaced TM Integrated TM ETCS Level 2 without signals ETCS Level 2 with signals Oxford Conventional infrastructure upgrade Pilning Kemble Bristol Parkway Greenford Bristol Temple Meads Bath Spa Newbury Reading London Paddington Windsor Heathrow 18 18

19 Planned / Potential Schemes South Eastern East Coast Main Line (alongside ETCS) Transpennine Upgrade Manchester (including Castlefield Corridor) Anglia Wessex Chiltern 19 19

20 Planned / Potential Schemes South Eastern East Coast Main Line (alongside ETCS) Transpennine Upgrade Manchester (around Castlefield Corridor) Anglia Wessex Chiltern Others emerging Northern TM 20 20

21 21 Transpennine Upgrade and TM

22 Next Steps on New Schemes Develop of route based strategy/plans - geographic interfaces - building on signal control schemes where possible - route specific requirements Development of standard procurement components Capability and standardisation 22 22

23 Next Steps: Route Based TM Strategy and Plans 23 Builds on National Strategy development shared with DR Programme Board in early 2018 which proposed a route/roc based approach. Includes a level of international and external validation of plans Inputs: - Status of signal control in each ROC including existing suppliers - Current CP6 re-control plans (and beyond) - Needs of Route - Interfaces (especially for Northern TM, where LNE, TRU and LNW) Outputs: - Strategy for each route including a procurement/commercial strategy, optimal migration sequence, end state for TM (integrated/interfaced/isolated) and whether interfaces to C-DAS, Crew and Stock systems should be included - optimised interfaces to other TM deployments. - Initial deployment plan (including an outline programme, costing and view of benefits and risks) based on the strategy - visualisation of the key aspects of the plan 23

24 24 Next Steps: Scheme Development (including Procurement) Procurement approach ITT Documents (based on ECML and Western TM). Associated GRIP (1-3) products or equivalent Associated Route Support Approach aligned with Route Strategy and Plan 24

25 25 Next Steps: Capability Development Development of Generic Interfaces (in partnership with or with validation by the supply chain) to include: - Standard interface to Signal Control (acknowledging System Authority work on Eulynx) - Progress towards standardisation of user interfaces - Progress towards full implementation of LINX message catalogue Improved understanding of Software as a Service and its impact on: - procurement - generic DR requirements - type of TM that can be supported using SaaS, including safety integrity aspects Development of a means of visualisation of options (TM/Sig Control) and consideration of data management during deployment based on GIS mapping. 25

26 Towards a National Perspective Route based Alignment to Rail Operating Centres (ROCs) Standardisation of Interfaces Resilience Alignment to Re-control projects Future National Layer 26 26

27 Challenges (Lessons Learned) Significant business change Significant interfaces Traffic Management is not a standard product, nor are the interfaces standard yet The significance of operating rules and data Learning curve for UK applications Alignment to resignalling and re-control 27 27

28 Opportunities Growing confidence Learning the lessons one of the Digital Railway Programme s roles Very strong business cases Integration with Crew & Stock and Connected Driver Advisory Service (C-DAS) 28 28

29 Conclusion Traffic Management here to stay! Significant lessons from early deployments are being learned and applied Gives confidence to progress Traffic Management Schemes which have very strong business cases We are now developing the next set of schemes Need to also progress our capability in areas such as: - standardisation - Software as a system - mapping/data management 29 29