ATO over ETCS Benoît BIENFAIT 10/2/2016

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done ? Roadmap Conclusion 2 3 4 5 6

Background ETCS provides safety & worldwide interoperability But… major challenges for Main Line Operators are: to improve the performance and capacity of lines to reduce operating cost To improve CO2 footprint Automatic Train Operation (ATO) is proven in Urban application, but Main Line networks and application are more complex There is a great variety of train, variable consists and a variety of infrastructure fitment ATO on Mainlines shall not jeopardize interoperability

What is ATO over ETCS? Automatic driving of the train to meet the operational timetable in the most energy efficient way (including automatic doors control). ATO is an add-on which complements ETCS ATO operates under ETCS supervision and does not affect safety ATO will be interoperable and backward compatible (both ATO-fitted and non-ATO trains can coexist on both ATO-fitted and non-ATO infrastructure ATO is an option (but when implemented must follow the standard specifications)

What is ATO over ETCS ? Performances Suppression of reaction time due to the driver (from ETCS safety curves) Reduced dispersion in the travel times Reduced margins included in Theoretical Time Tables Reduced operational headway More trains per hours on the same infrastructure Quality of Service Beter punctuality Greater comfort impression Operation Costs Reduced enegry consumption Reduced train fleet to operate a line for a given operational headway Time Tables and Infrastructure data Optimum Speed Profile Guaranteed arrival and departure time

Energy Savings IC operation (Speed Profiles)

Energy Savings IC operation (Energy consumption)

Energy Savings Local operation (Speed Profiles)

Energy Savings Local operation (Energy consumption)

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done Roadmap Conclusion 2 3 4 5 6

How does ETCS provide « Interoperability » ? Split of responsibilities between operation stakeholders Infrastructure Manager responsible for data stored in ETCS infrastructure systems Train Owner responsible for performance data stored in ETCS on-board equipment Technically Trackside system sends track description according to “ETCS language” and ETCS rules. ETCS on-board systems implement ETCS-specified behaviour, according to messages received from the ETCS infrastructure on the route.

ATO « Interoperability » as an extension of ETCS ! Responsibilities: Infrastructure Manager: correctness + accuracy of ATO description of the track network. Train Owner: correctness + accuracy of ATO train data, performance characteristics and Energy Management Traffic Manager : planned and actual traffic schedules Technically: There should be no difference between "ETCS Interoperability" and "ATO Interoperability“ ATO communication based on ETCS principles and grammar (add-on) ATO is not safety related  ETCS always supervise the current speed as today ATO active only in ETCS FS

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done Roadmap Conclusion 2 3 4 5 6

Grades of Automation

Current situation (GoA1) Current ETCS

ATO over ETCS (GoA2) ATO over ETCS FIS

ATO over ETCS Functional Architecture

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done ? Roadmap Conclusion 2 3 4 5 6

What has been done Preliminary Study of ATO over ETCS Users Requirement collection  Concept of ATO over ETCS defined up to GoA 4 AoE Solution Specification for GoA2: SUBSET-125 ATO System Requirements Specification SUBSET-126 - ATO-OB/ATO-TS Interface Specification All related documents attached to CR1238 in ERA data base

ATO preliminary study Completed in March 2012 Activities: Activity 1: Feasibility demonstration of ATO with ETCS combined system using “in revenue service” constituents. Activities 2 and 3: Three simulations of urban low speed, urban high speed and suburban railways. Activity 4: A standards development activity to develop standard protocols. Conclusions: ATO over ERTMS is feasible and can deliver improved capacity, performance and energy consumption which could help with ETCS deployment ATO can offer an improved service but relies on input from the TMS to manage operating conflicts and perturbations.

ATO Operational Concept Completed in Sept 2013 Deliverables: ATO Operational Principles ATO Operational Requirements ATO Operational Scenarios ATO Glossary The ATO Operational Concept covers GoA2 to 4 and takes an ATO over ETCS system approach In the context of the change request, the scope is limited to GoA2

ATO Specifications SUBSET-125 v 0.0.10 : System Requirement Specification First version issued the 21/10/13 Latest version issued the 17/04/15 based on EECT comments Content Functional features Input and output required Driver Machine Interface (UNISIG proposal) ATO Operational Modes & States Architecture SUBSET-126 v 0.0.6: ATO-OB/ATO-TS Interface Specification First version issued the 7/1/14 Latest version issued the 29/09/14 based on UG comments "ATO packets" definition "application to application" communication principles

ATO interaction with ETCS Specs New ETCS mode to support ATO (called AD Mode) Control function for ATO traction/brake commands. Additional icons on the DMI Additional inputs from the driver Suppression of warning indication in AD Mode. Suppression of release speed monitoring in AD Mode. Interface on-board between ATO and ETCS Additional data for the On Board Recording Unit

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done ? Roadmap Conclusion 2 3 4 5 6

ATO System Development (GoA2) ATO SRS & Interface spec ATO Feasibility Study Start of Shift2Rail ATO Ops Concept 2012 2013 2014 2015 2016

S2R TD 2.2 Activities

S2R TD 2.2 Activities

Agenda Back Ground of AoE and expected benefits Interoperability 1 Back Ground of AoE and expected benefits Interoperability Functional architecture What has been done ? Roadmap Conclusion 2 3 4 5 6

Conclusion ATO is profitable for operators Consequently, ATO over ETCS will promote ETCS deployment ATO features must be standardised: To guarantee ATO interoperability To permit cross compatibility of ATO with ETCS (train with/without ATO running on infrastructure fit for ATO or not) To promote competition between suppliers ATO over ETCS may be optional But, when implemented, it shall comply with the standard specification to guarantee the interoperability EUG has specified their requirement (Operation Concepts up to GoA4) UNISIG has issued System Requirement and Interface specification compliant with Ops Concept (GoA2) ETCS specification must be adapted to support ATO (discussions started with ERA)