Danish Onboard ERTMS Implementation Nordic Rail Conference - 07 October 2015 David Chabanon – Onboard ERTMS Project Manager 1

Agenda Danish Signalling Programme overview Onboard ERTMS project overview Focus on the Øresund link Onboard ERTMS Software roadmap Main challenges & Lessons Learned Conclusion

Danish Signalling Programme Overview ETCS Trackside contract for East Denmark: Alstom ETCS Trackside contract for West Denmark: Thales ETCS Onboard Contract for all Rolling Stock in Denmark: Alstom GSM-R infrastructure & Onboard voice radio: Siemens East contract West contract Traffic Management Systems Coordination by suppliers

Danish Signalling Programme Overview Scope: Design Build Maintain contracts – up to 25 years of maintenance Total replacement of signalling assets (including interlocking, Traffic Management System) Baseline 3 ETCS Level 2 Deployment on the whole Danish network with no overlay (wayside signals removed) Fit all rolling stock operating in Denmark including freight and maintenance vehicles (yellow fleet) Danish STM + integration with Swedish STM ETCS over GPRS + Online Key Management System Other contracts: New TCC buildings Danish STM baseline 3 (Siemens) Integration contract with Ansaldo for Swedish STM integration / support Rental agreement with Hector Rail to build a Test Train (Taurus locomotive) for Swedish/Denmark solution

Danish Signalling Programme Overview Early Deployment lines East and West

Danish Signalling Programme Status All contracts signed since 2011-2012 Both trackside projects in installation and test phase for Early Deployment lines GSM-R voice radio replacement well underway GSM-R data infrastructure upgrade started Onboard ERTMS completing Generic Design phase, entering Testing phase Traffic Control Center East building commissioned

Onboard ERTMS Project focus: scope 89 Yellow Machines 5 different types Around 600 Passenger and Freight Trains 25 First of Class

Project Plan ED East + West Rollout Joint Test Lab Joint Test Lab Programme activities: 2012 2013 2014 2015 2016 2017 2018 2019 2020 December15: end of Generic Design Design Stages: CD, PD, GD Supplier Lab Tests Test Train Baseline 3 First Of Class Fitment Rollout Fitment

ERTMS Onboard Project Status Joint Test Lab activities

ERTMS Onboard Project Status Factory Acceptance Test completed with version compliant with Baseline 3.3.0 + DK specific functions: GPRS and online Key Management System Integration with Danish STM Baseline 3 completed (lab) Integration with Swedish STM ongoing (lab) ETCS compatibility tests (DK/SE) ongoing (lab) Driving Simulator ready for Instructors

ERTMS Onboard Project Status Next major milestones: Danish Test Train approved to perform test runs in mixed traffic (Level STM): March 2016 Start of Danish fleet fitment for Early Deployment lines: April 2016 Swedish / Danish Test Train (Hector Rail Taurus Loco) ready for test in Sweden in June 2016 Start training of drivers Q2 2016

Focus on Øresund link Objective: Keep the traffic between Sweden and Denmark (and to Germany) open for business!

Focus on Øresund link Scope (Onboard): Develop and approve an Onboard “Øresund package” than can be deployed on different types of train ET (X31) passenger fleet: 111 trains including DSB and Swedish RUs to be fitted Freight Trains (corridor B), between Alvesta North (Sweden), Denmark and Germany: potentially 60 more trains to be fitted

Plan to validate “Øresund” package Banedanmark, Trafikverket and Øresundbro Consortium signed an MoU for coordinating ERTMS programmes between Sweden and Danemark Steering group and working groups in place to develop the solutions (onboard and trackside) Taurus locomotive hired from Hector Rail to test the “Øresund” package

Banedanmark EVC Software Roadmap EVC 6.3.0 compliant with Baseline 3.3.0 + DK specific functions + CRs from Baseline 3.4.0 Final target is Baseline 3.5.0 Intermediate version? Early Deployment version Available version EVC 6.3.0 + additional improvements to increase performance and safety operations EoG Danish solution needs to be changed to match ERA requirements

Main challenges so far Freezing the software scope Installation design Human Factor engineering and cab design STM integration Safety approvals Fitment plan and workshop capacity

Main challenges so far: Freezing the software scope Supplier internal software development cycle Contractual requirements: Baseline 3 Other requirements affecting EVC software: STM EVC software scope Users acceptance (e.g. DMI) Baseline 3 moving target: 3.2.0 » 3.3.0 » 3.4.0 » 3.5.0 Adjustment of solutions: design choices from supplier may not meet operational needs

Main challenges so far: installation design Decide preliminary location of equipment Light Survey Detailed Survey Draft FoC Design FoC Designed Approved Confirm location of equipment + Engineer the detailed design (cable paths…etc.) Review by BDK and Operators

Main challenges so far: installation design Mechanical and electrical installation design: old fleet requires extra effort to install ETCS and STM equipment Missing or outdated train documentation Clearly define upfront criteria to declare a new First of Class: train variances identification process Ask operators upfront what are the most important technical requirements (e.g. Underframe connectors)

Main challenges so far: Human Factor engineering and cab design Simple problem: replace and relocate existing train components to make room for new DMI

Main challenges so far: Human Factor engineering and cab design Human Factor engineering: Visibility study, Ergonomic analysis, Drivers and Drivers Instructor tasks analysis Final Cab Design to be approved by Drivers union

Main challenges so far: STM integration It is important to place the STM integration and installation responsibility into one responsible party To mitigate risks of claims: clearly define upfront fit/form factors of STMs as well as specific functional requirements Align safety processes: STM should be covered by a Generic Application Safety Case. Installer needs to deal with Specific Application Safety Case STM/EVC integration requires intensive lab tests: not always easy to identify responsible party to fix software bugs

Main challenges so far: Safety and Interoperability approvals EU directives can be interpreted in different manners by NSAs and are changing: we, as Customers, do not take advantage of lessons learned from suppliers Our Industry is still immature using the Common Safety Method Risk Assessment process: the CENELEC regime still prevails Who should be the Applicant / Proposers for Vehicle APIS after new Onboard CCS system installed? Interoperability demonstration: how to involve Onboard supplier in the ETCS system integration (train/track system validation)?

Main challenges so far: Fitment plan and workshop capacity Allow enough time for taking trains out of service for fitment without jeopardizing operators business and infrastructure rollout Conflict between tender evaluation criteria versus what can be practically achieved Force bidding suppliers to be very specific in terms of workshop capacity needs: pits, roof access, number of tracks available per workshop When planning fitment you MUST take into account: expected learning curve, authorization process, workshop capacity, Supplier assumptions in terms of shift, other contractual requirements (reliability demonstration)

Conclusion Major milestone achieved in proving an Onboard solution compliant with ERTMS Baseline 3.3.0 and good enough to operate in STM mode and start ETCS L2 integration tests Need some extra efforts to prove a solution acceptable for operations on Early Deployment lines in ETCS L2 mode Special focus on the ”low tech” topics such as mechanical installation design and cab design Special focus on maintanibility Challenging programmes need ”out of the box” mindset to keep the collaboration Customer/Supplier up and running

End