The European Deployment Plan
The ERTMS European Deployment Plan (EDP) sets deadlines for the implementation of ERTMS and its aim is to ensure the progressive deployment of ERTMS along the main European rail routes.
The currently applicable EDP is included in the Commission Implementing Regulation (EU) 2017/6 of 5 January 2017 on the European Rail Traffic Management System European deployment plan .
This Regulation lays down the timetable for the deployment of the ERTMS on core network corridors (CNC) as set out in its Annex I schemes. These CNC are:
|Scandinavian-Mediterranean (SCM)||Finland (Turku/Naantali-Kouvola-Hamina) Stockholm-Malmö-Copenhagen-Hamburg-Innsbruck-Verona-Roma-Napoli-Palermo|
|North Sea-Mediterranean (NSM)||UK (Glasgow-Edinburgh-Liverpool-Manchester-Birmingham-London-Dover)|
|Mediterranean (MED)||Algeciras-Valencia-Tarragona/Sevilla-Madrid-Zaragoza-Barcelona-Marseille-Lyon-Turin-Milan-Verona-Padua/Venice-Trieste/Koper-Ljubljana-Budapest-Zahony(Hungarian-Ukrainian border)/Budapest-Zagreb and Budapest-UA border|
|Rhine-Danube (RDN)||Prague-Horní Lideč–Žilina–Košice-Čierna nad Tisou (Slovak/ Ukrainian border)|
|North Sea-Baltic (NSB)||Bremerhaven/Rotterdam/Antwerp-Aachen-Utrecht/Hannover-Amsterdam/Berlin-Warsaw-Terespol (Poland-Belarus border)/Kaunas/Warsawa-Vilnus/Helsinki/Kaipeda/Ventspils|
|Baltic-Adriatic (BAC)||Gdynia-Katowice-Ostrava/Žilina-Bratislava/Vienna/Klagenfurt-Udine-Venice/ Trieste/Bologna/Ravenna/ Graz-Maribor-Ljubljana-Koper/Trieste|
|Atlantic (ATL)||Sines-Lisbon/Leixões-Madrid-Medina del Campo/ Bilbao/San Sebastian-Irun-Bordeaux-Paris/Le Havre/Metz Sines-Elvas/Algeciras|
|Orient/East-Med (OEM)||Rostock/Hamburg/Wilhelmshaven/Bremerhaven-Dresden-Prague-Bratislava/Vienna-Budapest Arad-Timisoara-Vidin-Sofia-Thessaloniki-Athens/ Igoumenitsa|
European deployment Plan for ERTMS, corridor maps (updated 05/01/2017)
Within the EDP, the full compliance with the Technical Specifications for Interoperability Control Command and Signalling 2016/919/EC (CCS TSI) is a prerequisite In this CCS TSI, rules for the deployment of the system in the vehicles is also included. With regard to rolling stock, EC Decision 2016/919 states that new vehicles authorised to be put into service for the first time shall be equipped with ERTMS and by 2019 any new vehicle to be equipped with ERTMS should implement Baseline 3 specifications.
|ERTMS Corridors||ERTMS Corridor description|
|Corridor A||Rotterdam - Genoa|
|Corridor B||Stockholm - Naples|
|Corridor C||Antwerp - Basel - Lyon|
|Corridor D||Valencia - Budapest|
|Corridor E||Dresden - Prague - Budapest - Costanza|
|Corridor F||Aachen - Berlin- Warsaw - Terespol|
Initially, the EDP for ERTMS included the geographical scope of the 6 ERTMS Corridors, named A to F. The dates for their deployment were foreseen no further than 2020. In fact, the basis of this EC Decision and the EDP was the sending of the national ERTMS deployment plans by the Member States to the Commission in 2007. The EDP does not include all national plans, but it focuses on the most important stretches of European interest.
These 6 ERTMS Corridors are: European Deployment Plan for ERTMS, detailed map (updated: 27/05/2010)
In 2010 the Rail Freight Corridor regulation (Regulation 913/2010 ) was published. This regulation concluded with the need for an alignment of the Rail Freight Corridors with ERTMS corridors, since this regulation describes the ERTMS as the way to improve the efficiency of rail freight transport. This regulation is included under the scope of The European Rail Network for Competitive Freight
This regulation defines 9 initial corridors and establishes the RFC structure and governing bodies. It also addresses timetabling and capacity allocation issues. However, no associated deployment plan for the RFC is included. Instead, within the corridor governing structure the obligation to publish an implementation plan including an interoperability chapter is defined. This can be found in the Regulation handbook.
The following are the 9 RFC:
|RFC Corridors||Rail Freight Corridors Description|
|RFC 1||Zeebrugge-Antwerp/Rotterdam-Duisburg-[Basel]-Milan- Genoa|
|RFC 3||Stockholm-Malmö-Copenhagen-Hamburg-Innsbruck- Verona-Palermo|
|RFC 4||Sines-Lisbon/Leixões — Madrid-Medina del Campo/ Bilbao/San Sebastian-Irun- Bordeaux-Paris/Le Havre/Metz Sines-Elvas/Algeciras|
|RFC 5||Gdynia-Katowice-Ostrava/Žilina-Bratislava/Vienna/ Klagenfurt-Udine-Venice/ Trieste/ /Bologna/Ravenna/ Graz-Maribor-Ljubljana-Koper/Trieste|
|RFC 6||Almería-Valencia/Madrid-Zaragoza/Barcelona-Marseille- Lyon-Turin-Milan-Verona-Padua/Venice-Trieste/Koper- Ljubljana-Budapest-Zahony (Hungarian-Ukrainian border)|
|RFC 7||Bucharest-Constanta Prague-Vienna/Bratislava-Budapest — Vidin-Sofia-Thessaloniki-Athens|
|RFC 8||Bremerhaven/Rotterdam/Antwerp-Aachen/Berlin-Warsaw- Terespol (Poland-Belarus border)/Kaunas|
|RFC 9||Prague-Horní Lideč-Žilina-Košice-Čierna nad Tisou (Slovak/ Ukrainian border)|
In the ERTMS Coordinator's view (Work Plan – May 2015), "The EDP needs to be adapted to the reality and create an ambitious and pragmatic plan with clearly defined priorities within the Corridors with a definite time limit of 2030." In 2009 (when the first EDP was adopted) the ERTMS implementation experiences available were very few at both national and European levels. The national deployment plans (dating back from 2007) have turned out to be too optimistic, and to make matters worse, a serious economic crisis was hampering any infrastructure activities in Europe and delayed the implementation. Despite the legislative actions of the EC and the significant provision of EU funding, deployment on corridors is behind the expected schedule and results in an uncoordinated and irregular deployment. This is the main reason why a new EDP with binding updated dates was necessary.
That is why EC has identified the need to integrate the EDP for ERTMS into a wider context and ensure consistency not only with the RFC regulations but also with the TEN – T regulations and the Connecting Europe Facility regulations, and that is the purpose of the current EDP 2017/6/EC.
TEN Regulation (Reg. 1315/2013) – is the EU transport infrastructure policy that connects the continent and aims to close the gaps between transport networks and boost the European economy. The deadline for the aimed objectives is 2030 / 2050, depending on the nature of the projects.
CEF Regulation (Reg. 1316/2013) – The Connecting Europe Facility sets out the rules for awarding EU financial support, for priority projects and maximum limits of EU co-financing per project type. It also includes a pre-identified list of projects where most CEF investments will be placed.
In 2013 the TEN-T Regulation (1315/2013) established guidelines and set out the priorities for the development of a trans-European transport network. Regarding railway transport infrastructure the requirement for full deployment of ERTMS (among others) was established. For core network corridors the deadline is 2030 and 2050 for the comprehensive railway line network.
To ensure that each corridor is effectively and efficiently developed each corridor is managed by a European Coordinator. The ERTMS coordinator Mr. Karel Vinck is also nominated to speed up the implementation of ERTMS throughout Europe. Their duties include producing an ERTMS work plan along with the Member States concerned, supporting and monitoring implementation of the work plan and highlighting difficulties, among others.
Thus, there is a need to build a new ERTMS Deployment Plan to ensure consistency with the RFC Regulation, the TEN-T Regulation and the Connecting Europe Facility Regulation.
These corridors link public and private resources and concentrate EU support from the CEF , to specifically remove bottlenecks, build missing border crossings and connections, and promote modal integration and interoperability. In fact, ERTMS is a CEF horizontal priority.
The National Implementation Plans (NIPs)
The Member States shall draw up a National Implementation Plan, describing their actions to comply with the TSI 2016/919, in accordance with Section 7.4.4, setting out the steps to be followed for the implementation of fully interoperable 'control-command and signalling' subsystems.
The National Implementation Plans shall be sent to the Commission before 5 July 2017 and shall be updated at least every 5 years.
The first national implementation plans have been received during 2017. A summary on the main issues contained can be found in the synthesis report.
For the complete ERTMS NIP please refer to the section National Implementation Plan in each country.