Transport

Development of the Rhine-

Danube Rail Freight Corridor
(RFC 9)
Corridor Forum 18 June 2014
Brussels

Dr. Gerhard Troche
European Commission DG MOVE
Single European Rail Area



1
Transport
. Six Rail Freight Corridors became operational by November
2013:
RFC 1 Rhine-Alpine Corridor
RFC 2 North Sea-Mediterranean Corridor
RFC 4 Atlantic Corridor
RFC 6 Mediterranean Corridor
RFC 7 Orient East-Med Corridor
RFC 9 Czech-Slovak Corridor (future Rhine-Danube RFC)

. RFC 3, 5 and 8 to become operational by November 2015

November 2013
A milestone for the Rail Freight Corridors
Transport
. 10 November 2013 Original RFC 9 became operational
. 10 November 2020 (latest) Rhine-Danube RFC to be made
operational in its entirety
- Shortest RFC becomes one of the longest
- Participation of seven Member States (five more than today) /
and high number of Infrastructure Managers
- Major geographical overlaps with other RFC (in particular RFC 7)
- Extensions (or parts of them) may be made operational earlier on
a voluntary basis
RFC 9 Key deadlines
Transport
Rhine-Danube RFC Participating Member
States and Principal Route
. Closes gaps in the RFC network (European Rail Network for
Competitive Freight)
. Important potential in development of East-West traffic,
including feeder traffic from/to the Europe-Asia landbridge




Transport
. RFCs form the rail freight backbone of the CNCs
. Each CNC "comprises" a RFC
. The role of rail as a transport mode in the CNCs is
strengthened by a strong and ambitious development of the
RFCs in terms of
. (Technical) standard
. Capacity
. Service quality (i.a. Corridor-OSS)
. Customer orientation
. The Implementation Plan of the RFCs constitutes the rail
freight element of the CNC Work Plan

Relation between Rail Freight Corridors (RFC)
and Core Network Corridors (CNC)
Transport
. Annex II of CEF-Regulation 1316/2013/EC amends the
Principal Routes of the initial RFCs
. Geographical integrity of the original Principal Routes of the RFC
is maintained
. Certain extensions of RFCs in order to optimally match the CNC
. RFC numbers are replaced by names
. All provisions of Reg 913/2010/EC remain fully in force
. Including provisions on the composition, rights, tasks and
obligations of the RFC governance bodies
But co-operation with CNCs is envisaged
. Including provisions on the modification and establishment of
further RFC


Relation between RFC-Regulation 913/2010/EC
and CEF-Regulation 1316/2013
Transport
. CNC routes are "fixed" by the TEN-T Guidelines Regulation
(1315/2013/EC) and are limited to the Core Network
. Designation of lines and terminals to the RFC is task of the
Management Board (and requires approval by the Executive
Board)
. Relevant Core Network lines should be designated to the RFC,
but:
. Even rail lines and terminals of the Comprehensive TEN-T
Network can be designated to a RFC
. Even rail lines and terminals outside the TEN-T Network can be
designated to a RFC
I.e. geographical scope of RFCs can be wider than of the CNCs


Geographical scope of RFCs and CNCs
Transport
. Governance bodies (ExBo / MaBo) need to become extended
Possible approach:
. First step: Informal contacts between Member States /
Infrastructure Managers to find consensus about a suitable point
of time for inclusion / Dissemination of information
. Second step: Inclusion of new members as observers
. Third step: Full inclusion as new members (well in advance of the
deadline for establishment of the extended RFC)
. Update of Transport Market Study for RFC 9 should at an
adequate time take into account future extensions into the
Rhine-Danube RFC
. Take into account work already done in RFC 9 and on
experience in other RFC




Rhine-Danube RFC Approach
Transport
9
Requirements on the Core Network (Freight) according
to Art 39(2a) of Reg. 1315/2013/EC (TEN-T Guidelines)
740m train length
22,5 t axle-load
100 km/h line speed
ERTMS
Electrification
To be achieved until 2030
Core Network infrastructure requirements
in the context of the RFC (I)
Transport
10
Infrastructure requirements important for interoperability in
the RFC
Cross-border coordination of their implementation needed
Realise synergies in the implementation of the requirements
RFCs should carry out studies for the implementation of the
requirements (eligible for co-funding under CEF) additional
parameters such as loading gauge may be covered as well!
The studies should form the basis for a plan for
implementation of the requirements on the Core Network of
the RFC to be included in the RFC Implementation Plan !
Consultation of RFC Advisory Groups necessary

Core Network infrastructure requirements
in the context of the RFC (II)
Transport
CEF Multi-Annual Work Plan
Specific objective: Rail interoperability

Ensuring easy access for users to information about itinerary, time and
availability
Ensuring compliance of the rail system and its subsystems with the TSI
Simplifying procedures for the authorization, placing in service and use of
rolling stock on the Union's railway network
Ensuring compliance with other relevant requirements of the TEN-T
Guidelines
Ensuring the establishment Rail Freight Corridors, their full
extension and integrated development with the core network
corridors (incl. support to studies, managerial structures, user-
involvement, tools)




RFCs are eligible under the CEF
Transport
12
Thank you for
your attention !
gerhard.troche@ec.europa.eu