National Implementation Plan for ERTMS in Austria

National Implementation Plan for ERTMS in Austria

National Implementation Plan for ERTMS in Austria National implementation plan Austrian Federal Ministry of Austria relating to the TSI for Transport, Innovation and Technology for the “control-command and Radetzkystraße 2, 1030 Wien signalling” subsystems Unit II / Infra 2 (Infrastructure Planning) (ERTMS NIP) Unit IV / Sch 4 (Technological Principles, Railway Technology, Technological Research) pursuant to Article 6 of www.BMVIT.gv.at Commission Regulation (EU) infothek.BMVIT.gv.at 2016/919 of 27th May 2016 July 2017 Based on contributions by Bundesministerium für Verkehr, Innovation und Technologie ERTMS NIP for Austria Federal Ministry for Transport, Innovation and Technology Table of contents 1. Context, scope and contents 3 1.1 Legal requirements _________________________________________________________3 1.2 Scope and contents ________________________________________________________3 1.3 Elaboration of this document _________________________________________________4 2. General description 5 2.1 Overview of ETCS planning and implementation processes _________________________5 2.2 Existing train protection systems ______________________________________________6 2.3 General strategy including cost-benefit considerations _____________________________7 3. Technical and financial migration strategy 10 3.1 Technical migration strategy ________________________________________________10 3.2 Financial migration strategy _________________________________________________14 4. Planning and schedules 18 4.1 Dates of ETCS deployment _________________________________________________18 4.2 Indicative dates of decommissioning of Class B systems __________________________19 4.3 Full benefits from “ETCS only equipped on-board” _______________________________20 5. References 22 Strategy documents __________________________________________________________22 Legal acts, regulations and guidelines ____________________________________________22 List of abbreviations __________________________________________________________23 Annex 1 – ETCS deployment dates 24 2 ERTMS NIP for Austria Federal Ministry for Transport, Innovation and Technology 1. Context, scope and contents 1.1 Legal requirements This document presents the National Implementation Plan (NIP) to be notified by Member States to the European Commission pursuant to Article 6(4) and section 7.4.4 of the technical specification for interoperability relating to the ‘control-command and signalling’ subsystems1. The NIP complements and further details the ERTMS European Deployment Plan (EDP) adopted by the European Commission in January 2017 in an implementing act2 on the legal basis of the TEN-T guidelines3. 1.2 Scope and contents Scope and contents of the NIP are specified in detail in point 7.4.4 of the TSI CCS. Table 1 summarises the scope of the NIP and compares it to the scope of the EDP. Aspect ERTMS NIP ERTMS EDP Geographical scope As defined in the technical TEN-T core network corridors (network parts considered) specifications for interoperability (Regulation 1316/2016, Annex I, Part I.2) (Commission Regulation (EU) 2016/919) Time horizon 2017 to 2032 (15 years) Phase 1: 2017 to 2023 Phase 2: 2024 to 2030 Table 1: Scope of ERTMS NIP and EDP Regarding the contents, the TSI lay down detailed requirements; the present document is therefore structured accordingly as outlined in table 2. 1 Commission Regulation (EU) 2016/919 of 27 May 2016 on the technical specification for interoperability relating to the 'control- command and signalling' subsystems of the rail system in the European Union 2 Commission Implementing Regulation (EU) 2017/6 of 5 January 2017 on the European Rail Traffic Management System European deployment plan 3 Regulation (EU) No 1315/2013 of the European Parliament and of the Council of 11 December 2013 on Union guidelines for the development of the trans-European transport network and repealing Decision No 661/2010/EU 3 ERTMS NIP for Austria Federal Ministry for Transport, Innovation and Technology Requirement in TSI CSS Section in this document (1) General and context description Chapter 1 and 2 (2) Definition of technical and financial migration strategy Section 3.1 and 3.2 (3) Measures related to Class B train protection systems Section 3.1.3 (4i) Dates of ETCS deployment on different lines Section 4.1 and Annex I (4ii) Indicative dates of decommissioning of Class B systems Section 4.2 (4iii) dates when cross-border services fully benefit from ‘ETCS only equipped on-onboard’ Section 4.3 Table 2: Coverage of the requirements specified in TSI CCS in this document The NIP provides the following additional information as compared to the EDP: • The NIP for ERTMS covers the whole rail network on which the TSI CCS applies whereas the EDP is limited to the TEN-T core network corridors. • In terms of substance, the NIP also includes information on the technical and financial migration strategy and on the decommissioning of Class B systems. In addition to the mandatory contents requirements from TSI CCS, section 3.1.4 gives an overview of current technical challenges for further ETCS deployment. 1.3 Elaboration of this document This document has been elaborated in close cooperation between BMVIT and ÖBB-Infrastruktur AG. BMVIT mainly took over a coordinating and overseeing role. Development of the migration strategy and implementation planning were done by ÖBB Infrastruktur AG. Raaberbahn AG has been consulted on the state-of-play of ERTMS planning on their network (which partially belongs to the TEN-T comprehensive network). Further infrastructure managers and railway undertakings operating in Austria will be consulted at a later stage (see section 2.1). 4 ERTMS NIP for Austria Federal Ministry for Transport, Innovation and Technology 2. General description This chapter provides an overview of the ETCS planning, consultation and implementation processes in Austria, presents a general description of the existing Class B train protection systems in use in Austria and outlines the overall ETCS implementation strategy. 2.1 Overview of ETCS planning and implementation processes The elaboration of the present national implementation plan is part of broader strategy, planning and implementation processes carried out by BMVIT, infrastructure managers and railway undertakings concerned. The roles of BMVIT are mainly: • to act as an interface between European Commission, the European Union Agency for Railways and infrastructure managers, with a view to ensure consistency between their strategies and plans and EU legislation and strategies (notably TSI CCS and the ERTMS EDP); • to ensure the availability of funding for ERTMS deployment, through the allocation of appropriate financial resources in the six-year investment programme for rail infrastructure (see section 3.2); • in the future, BMVIT will accompany consultation processes with railway undertakings and vehicle owners regarding ERTMS deployment. Initial information is prepared in the internal ETCS Board of ÖBB-Infrastruktur AG, in an extended formation this board also includes BMVIT and NSA whenever needed. These forums shall provide a wide range of opportunities for BMVIT and NSA to participate. In the current phase of migration planning, the migration process has not been coordinated with RUs. In the future, RUs will be consulted and involved in the migration process in a non-discriminatory manner. General and dedicated customer events shall ensure timely information and feedback for and from customers (ÖBB customer meetings, customer fair organised by ÖBB´s network access department especially for RUs). ETCS planning and implementation at ÖBB-Infrastruktur AG follows a „three phase model“, including: 1. Basic strategy phase; 2. Elaborated strategy phase; 3. Implementation phase. 5 ERTMS NIP for Austria Federal Ministry for Transport, Innovation and Technology The information presented in this national implementation plan is fully in line with the internal planning and implementation process at ÖBB-Infrastruktur AG; however it has to be noted that it provides a momentary snapshot of the current state-of-play. Actual implementation will be continue to be re-evaluated taking into account future developments. At the current stage, the signalling industry imposes key constraints on ERTMS implementation, as additional efforts are necessary to provide infrastructure managers and vehicle owners / operators with functionalities still under development. This lack of functionalities concerns both on-board and track-side equipment; section 3.1.4 provides a list of specific current challenges. 2.2 Existing train protection systems The Austrian railway network is equipped with two Class B systems, PZB and LZB. 2.2.1 PZB PZB is an automatic, punctual and intermittend system based on track magnets and unidirectional communication/influence of rolling stock units, based on signal aspects. The system features ability to emergency stop trains and influence their speed profile according to signal aspects. 2.2.2 LZB LZB is a proprietary legacy system, continuously surveilling train run on an interactive, bidirectional basis. Data transfer is provided by medium frequency transmission (33-56kHz) by means of line transmitting cable along the track. Maintenance of trackside equipment is expensive. It will not be run in parallel with ETCS and removed in this case. Overview for LZB: • LZB control centre Wels: in the course of the upgrade of the current double track line to four tracks by 2022 between Linz and Wels, LZB will be replaced by

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    31 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us