REDESIGN OF THE INTERNATIONAL TIMETABLING PROCESS (TTR) · 9 TTR Vision Implementation of the TTR...
81
1 REDESIGN OF THE INTERNATIONAL TIMETABLING PROCESS (TTR) supported by Overall Presentation
Transcript of REDESIGN OF THE INTERNATIONAL TIMETABLING PROCESS (TTR) · 9 TTR Vision Implementation of the TTR...
1
REDESIGN OF THE INTERNATIONAL TIMETABLING PROCESS
(TTR)
supported byOverall Presentation
2
TTR General Information
3
The Problems with the Current TT ProcessThe current timetabling process does not fulfil the needs of the market and varies from country to country.
This lack of quality leads to a loss of attractiveness :
• Constantly changes in planning (for both RUs and IMs)
• Unused capacity bookings (for both paths and TCRs )reducing available capacity and causing unnecessary coordination processes
• Different planning procedures in different countries
Result: High costs, unsatisfied end customers and missed business opportunities! MARKET SHARE
EFFICIENCY
4
Current Situation: Examples→ today freight RUs have to order their train paths 8 to 20 months in advance
→ therefore freight RUs are booking ‘on the safe side’
→ Infrastructure capacity therefore heavily overbooked
→ just 20-25 % of freight train path requests are stable
→ 75-80 % of freight train path requests have to be modified constantly, resulting in a big waste of resources on both sides: RUs and IMs
→ leftover capacity does not really exist because of RU requests
→ in total: clear situation of capacity waste
5
Introduction: What is TTR?TTR is the joint project of RailNetEurope and Forum Train Europe to
• simplify • unify • solidify
improvements to the European rail timetabling system to significantly increase
the competitiveness of railways.
They are being supported by the European Rail Freight Association (ERFA).
6
Introduction of RNE, FTE and ERFARailNetEurope (RNE)
o Association of 35 IMs and ABs as well as 10 RFCs as Associate Memberswww.rne.eu
Forum Train Europe (FTE)
o Association of more than 90 RUs, authorized applicants andservice companies in passenger and freight trafficwww.forumtreineurope.eu
European Rail Freight Association (ERFA)
o Association of 30 RUs, leasing companies, wagon keepers, freight forwarders and intermodal operatorswww.erfarail.eu
7
The TTR Project Team
The TTR project team is made up of around 200 contributors recruited from Railway Undertakings, Infrastructure Managers / Allocation Bodies, and
supporting companies.
Market expertsfrom RUs
TT experts fromIMs/ABs
IT experts fromall stakeholders
Works expertsfrom IMs/ABs
Legal expertsfrom all
stakeholders
Business caseteam
8
Detecting Market NeedsThe TTR concept is based on the following marked needs:
o Flexibility, especially in the freight sector
o Possibility for earlier commercial use of paths, e.g. earlier ticket sales
o Reduction in load peaks and redundant work
o Higher stability and quality of timetables
MarketNeeds
9
TTR VisionImplementation of the TTR process started with a clear vision:
o Main focus on freight and passenger market needs with optimised request deadlines
o Improved reliability and stability incl. temporary capacity restrictions (TCRs)
o Binding implementation and application of the redesigned timetabling process (TTR)
o Increased efficiency (capacities, resources) in order to avoid duplication of work and planning efforts
10
Benefits of TTRo Optimised usage of infrastructure capacity
→ more efficiency
→ more flexibility
o Heavily decreased effort for path requests
→ ordering at any point of time
→ no more wasted resources for constant amendments
TTR is needed to keep railways competitive!
11
Financial Benefits of TTR
- Modal shift and increased use of infrastructure capacity
- Cost reduction due to efficient planning procedures
- Investments and IT- Change Management
and HR costs
12
TTR Basic Organisation
TTR Pilots
TTR Commercial Conditions
Steering Committee + Programme Management Office
TTR Legal Framework
TTR IT Landscape
TTR Implementation
13
TTR Governance: PMO and Steering Committee
• For FTE
Stephan Pfuhl (President)
Thorsten Dieter
Catherine Perrinelle
Maurizio Capotorto
Wolfgang Fritz
Edgar Schenk (Managing Director)
• For ERFA
Wolfgang Gross
• For RNE
Harald Hotz (President)
Guus de Mol
Bettina Wunsch-Semmler
Michael Beck
Ann Billiau
Paul Mazataud
Joachim Kroll (Secretary General)
Harald Reisinger (CIO)
• Sebastian Naundorf (Deputy Leader TTR Programme)
• Daniel Haltner (Substitute Leader TTR Programme)
• Philipp Koiser (Co-Leader TTR Programme)
• Martin Kreiter (Co-Leader TTR Programme)
• Aurelio Di Paola (Implementation Project Leader)
Programme Management Office (PMO)
Steering Committee (SteCo)
14
TTR Governance: Project and Task Force Leaders
TTR IT Landscape Project
• Mario Toma
• Seid Maglajlic (substitute)
TTR Commercial Conditions Project
• Zuhal Nalbant (co-chair)
• Zita Koops-Árvai (co-chair)
TTR Pilots Project
• Daniel Haltner
• Philipp Koiser (substitute)
TTR Implementation Project
• Aurelio Di Paola
• Philipp Koiser (substitute)
TTR Legal Framework Task Force
• Elisabeth Hochhold
• Tsvetan Tanev (substitute)
15
Useful Links (TTR in General)- TTR general overview:
http://ttr.rne.eu/general/
- Business Case:https://cms.rne.eu/ttr-documents/content/financial-framework
- TTR Forum:https://cms.rne.eu/ttr-forum
- TTR project results as approved by the RNE GA in May 2017:
- http://rne.eu/wp-content/uploads/TTR-Project-Results.pdf
- http://rne.eu/wp-content/uploads/TTR-Project-Results_Annex-01_Basic-IT-analysis.pdf
- http://rne.eu/wp-content/uploads/TTR-Project-Results_Annex-02_Draft-Implementation-Plan.pdf
16
Contacts TTR Programme Management Office
If you have further questions, please do not hesitate to contact either of the leaders of the TTR programme, Mr Philipp Koiser and Mr Martin Kreiter or the
deputy programme leader, Mr Sebastian Naundorf.
Co-Leader TTR ProgrammePhilipp [email protected]
Deputy Leader TTR ProgrammeSebastian Naundorf [email protected]
Co-Leader TTR ProgrammeMartin [email protected]
17
The TTR Process
18
TTR Approach: Detecting RequirementsThe TTR concept is based on the market needs:
Provide adequate capacity request methods
Plan capacity in advance and take into consideration:
- Market requirements
- Available capacity
RUs
TTR Team
IMs
- A request method for later requests(especially required by freight traffic)
- The current timetabling process, but improved(especially required by passenger traffic)
But we also have capacity restrictions!
19
Need for Advanced PlanningIn order to support both approaches, capacity needs to be planned and partitioned, before the start of the request phase (‘Advanced Planning’).
We need capacity for my early requests!
But safeguard capacity for our later requests!
We have capacity restrictions!
IM
RU1 RU2
- Capacity Models must be created to ensure the inclusion of all market requirements
- Construction works and other Temporary Capacity Restrictions (TCRs) must be taken into consideration
- Capacity Models must be created for each line and for every year
- Advanced Planning must focus on origin to destination approach
20
The TTR Process: From Rough to Detailed Information
The redesigned timetabling process consists of several components to cover advance as well as short-term planning and provides products for stable as well as variable market needs.
21
Components of the TTR Process
Additional process components:
o Leading entities
o Allocation rules
o Key Performance Indicators (KPIs)
Main components are:
22
Capacity Strategy
The creation of the capacity strategy starts five years before the timetable change and allows all stakeholders to announce and pre-coordinate these influencing factors at an early planning stage.
23
Capacity Model and Partitioning: Sources
Capacity Model
Results from Capacity Strategy
Experiences by IMs
Expected Change of Traffic Volume
Capacity Needs Announcements
24
Capacity Model and Partitioning: PrinciplesThe Capacity Partitioning follows two principles:
1) Partitioning by market needs:
Capacity required for TCRs
Capacity available for ATT (especially for passenger)
Capacity safeguarded for RP (especially for freight)
Note: If required, ATT can be planned for freight and RP for passenger traffic as well
2) Inclusion as path or band:
Capacity bands blocked for TCRs
Capacity bands with one or several paths
System paths with exact path details
25
Temporary Capacity Restrictions (TCRs)TCRs are defined in the latest recast Annex VII of Directive 2012/34/EU and in the TCR Guidelines issued by RNE:
TCRs must become predictable to stabilise all offers!
Consecutive days Impact on traffic*Deadline for final
publication
Major impact TCR > 30 > 50% X-18
High impact TCR > 7 > 30% X-13,5
Medium impact TCR 7 <= > 50% X-12
Minor impact TCR 7 <= > 10% X-4*)Percentage of estimated traffic volume on a railway line per day
cancelled, rerouted or replaced by other modes of transport
26
Current TCR DevelopmentsProcess
- TCR Guidelines were created, covering all provisions of Annex VII of Directive 2012/34/EU
- To further serve the needs of the market, and improve the process with a realistic approach, RNE has started the project ‘TCRs in Timetabling Process’.
- Together with FTE, use cases and best practice examples have been created (shared with RU Dialogue)
IT
RNE has provided a first version of the TCR Tool, firstly deployed on RFC Rhine-Alpine in December 2019 for limited real-life usage (major/high/medium impact TCRs).
Further improvements are underway:
- Provision of interfaces
- Functional improvements and simplifications in the tool
Expected full rollout in December 2020
Note: Most TCR developments are steered via and conducted by the RNE TCR Working Group
27
Provision of Capacity SupplyTo ensure quick and efficient answers to path requests, it must be clear which capacity is available. Note: This is not to be confused with the Capacity Model!
Until X-18: Capacity Model:
- Representation of a model time period (e.g. working day, week)
- Allows pre-planning of capacity, including harmonisation, detection of pressure points/creation of alternatives and inclusion of all market needs.
Starting X-11: Capacity Supply:
- Actual available capacity expressed in capacity products (paths + bandwidths)
- Enables quick access to capacity and provides an overview of available capacity to the applicants.
28
Request Method ‘Annual Request’
The ‘Annual Request’ option offers the possibility of an early request and early response.
Benefit: Booking systems can be opened earlier
(aim: 6 months prior to the timetable change).
29
Request Method ‘Rolling Planning Request’This method will draw from capacity already assigned in the capacity model and safeguarded for the specific purpose of short-notice requests.
Benefit: Quick response times provide the flexibility needed to react to fluctuating market needs as they occur.
30
Goals of Rolling Planning RequestReduce the number of annual ‘phantom’ requests
o Remove obligation to request based on best guesses
o Remove unnecessary (non-existing) conflicts
Provide alternative request method to the annual request
o Designed based on freight RUs’ needs but also available for passenger traffic
o Balance the need for stability (creation of capacity models, reduce request period) and flexibility (shift of the path request deadline, quick answers)
o Note: Rolling Planning is not intended as alternative to the ad hoc request
Ensure high quality capacity offers
o Based on dedicated (‘safeguarded’) capacity
o Answers in short period of time
Support applicants in their long-term planning and thus in their investments
31
TTR Process TimelineCapacity Strategy
Capacity ModelCapacity Partitioning
Capacity Planning & Publication Capacity Supply
Path / Capacity Requests
Path Modification / Alteration / Cancellation
Train Operation
AdvancedPlanning
Phase
CapacityRequestPhase
X-60 –X-36
X-36 –X-18
X-18 –X-11
Starting atX-11
Annual Requests (incl. Late Requests)
PathAllocation
Rolling Planning Requests
Path / CapacityAllocation
Ad Hoc Requests
PathAllocation
After allocation
32
Differentiation of Path Request Types
When? Which capacity?
An
nu
al
Re
qu
est
s Annual Request Placed on Time
X-11 –X-8.5
Pre-planned or non-pre-planned capacity
Late RequestsX-8.5 –
X-2Residual capacity from annual requests (pre-planned and
non-pre-planned capacity)
Sho
rt-T
erm
Re
qu
est
s
Rolling Planning Request
M-4 –M-1
Pre-planned (safeguarded) capacity
Ad Hoc RequestX-2 –X+12
Residual capacity from annual and rolling planning (<M-1) requests and dedicated safeguarded capacity
Path Modification1
/Alteration2
After allocation until X+12
Depending on original request: residual capacity OR
alternative rolling planning capacity
1) Requested by applicant2) Request by IM
33
Positive Effects of All Components Implemented
Freight RUs
can request shortly before the train run knowing all path details and being assured to receive high-quality paths
Passenger RUs
can plan early and open their booking system 6 months prior to the timetable change
IMs
can stabilise their plans, reduce redundancies in the timetabling process, make better use of the available infrastructure capacity and provide harmonised high-quality offers
34
Pre-conditions for the TTR ProcessThe TTR process requires some framework conditions to be adapted, improved or created. They must ensure that…
… all stakeholders implement the process in the same way
-> Legal Framework
… all stakeholders behave in accordance with the process components’ intention
-> Commercial Conditions
… all stakeholders can access the process and receive information real-time and in high quality
-> IT Landscape
TTR Process
ITCommercialConditions
LegalFramework
35
Useful Links (TTR Process)- Summarised TTR process description:
http://ttr.rne.eu/process/
- Further information and downloads on activities regarding TCRs:http://rne.eu/sales-timetabling/temporary-capacity-restrictions/
- Full TTR process description:https://cms.rne.eu/ttr-documents/content/process-description
36
Contacts TTR Process
If you have further questions regarding the TTR process, please do not hesitate to contact the leader of the task force TTR Process, Mr Daniel Haltner, or the deputy
leader, Mr Philipp Koiser.
Task Force Leader 'TTR Process'Daniel [email protected]
Deputy Task Force Leader‘TTR Process’Philipp [email protected]
37
TTR IT
38
Aims of the TTR IT Landscape
The TTR IT landscape aims to
o raise the quality of information exchanged between all stakeholders,
o accelerate process steps by allowing for a certain extent of automation,
o and provide easy access to all stakeholders, either via interfaces or via web browsers.
TTR Process
ITCommercialConditions
LegalFramework
39
Introduction to Big Data
In addition to implementing specific communication standards, a main pillar of the TTR IT landscape is the use of common data components, using data collected and maintained in the RNE Big Data system.
40
Basic IT Architecture
The future TTR IT landscape is split into two main blocks:
o The central IT framework, developed by RNE
o National and external systems, which need to communicate with the central IT framework
Communication between systems will be based on TAF/TAP TSI standards.
IMs & RUs
Systems
TTR IT Landscape
A
B
C
Central
IT
Framework
IMLayer
CommonLayer
RULayer
41
Layers of the Central IT Framework
In order to meet all business needs throughout the process, the central TTR IT Framework is set up in three layers:
o RU layer
o IM layer
o Common layer
Central
IT
Framework
IMLayer
CommonLayer
RULayer
42
Layers and Modules of the TTR IT Landscape
RU Domestic
Systems and Users
IM Nationals
Systems and Users
National
Processes
and TCR
Negotiation
National
Processes
and TCR
Planning
Capacity Needs
Announcement
TCRCapacity
Hub
Train Harmonisation
Path Request Management
Path Management
Capacity Broker
Messaging and Big Data
Cen
tral IT
Fra
mew
ork
RU
Layer
IM L
ayer
Co
mm
on
Layer
43
Modules of the RU LayerCapacity Needs Announcements: Using this module, RUs will announce their capacity needs for the upcoming timetable period in advance to help IMs predict the traffic volume for accurate capacity modelling.
Train Harmonisation: This module will support information exchange on, and harmonisation of, train characteristics (load, weight, length, border handling etc.), train routes and train composition.
Path Request Management: Using the Path Request Management module, RUs will submit path requests to each IM, using the data harmonised in the Train Harmonisation module.
44
Modules of the IM Layer
TCR (Temporary Capacity Restrictions): The TCR module collects all available information on planned TCRs in one dedicated space. This helps IMs to coordinate at international level and decrease the negative influence of TCRs on train operation.
Capacity Hub: The Capacity Hub module collects all data from the IMs/ABs and RUs and provides an overview of available capacity and TCRs in an early stage of planning.
Capacity Broker: By means of an algorithm, this module checks available capacity against the IMs’/ABs national systems, and distributes it according to RUs’ requests.
Path Management: The Path Management module ensures that international path coordination is done in a harmonised format by all involved parties.
45
Connection of IM and RU Layers
Capacity Bands
CapacityNeeds
AnnouncementsTCRs Catalogue Paths
Input (Capacity Hub)
Path Request Management
Train Harmonisation
Path Management
Capacity Broker
RU/ApplicantIM/AB
46
Common Layer: Messaging Module
Messaging Module:
o communication between RNE’s central systems and the external systems of IMs and RUs
o router function for external systems of IMs and RUs to communicate with each other
o based on TAF/TAP TSI standards
47
IT Implementation
48
Useful Links (TTR IT)- Summarised TTR IT landscape description:
http://ttr.rne.eu/it/
- TTR IT documents:https://cms.rne.eu/ttr-documents/content/ttr-it-landscape
49
Contact TTR IT Landscape
If you have further questions regarding the TTR IT Landscape, please do not hesitate to contact the leader of project ‘TTR IT Landscape’, Mr Mario Toma.
Project Leader'TTR IT Landscape'Mario [email protected]
50
TTR Legal Framework
51
Legal Framework: Introduction
The current legal framework (European and national laws) reflects existing capacity management processes, which do no longer (fully) meet market needs.
A team of legal experts from RNE Members, FTE, CER, EIM and CIT*
o Investigated how to support TTR in terms of legal framework conditions
o Provides ongoing legal analysis
*DG MOVE joins the task force as observer from May 2020
52
Basic Considerations for Legal Framework
EU legal framework
TTR
Options for implementation*
Network Statements
FCA Other MeasuresImplementing/
Delegated Acts
Bilateral Agreements
*Such measures must respect applicable EU law, in particular Directive 2012/34/EU.
53
Preliminary findings on the Legal Framework Some shortcomings have been identified, which might result in a high degree of legal uncertainty if TTR was to be implemented fully under the existing legal framework:
▪ No common understanding among stakeholders on key questions of interpretation of the legal framework, e.g.:
➢ can provisions of Article 48 of Directive 2012/34/EU serve as a basis to accommodate the rolling planning concept (even for TTR full roll-out)?
➢ can ATT requests be rejected if this is necessary to protect rolling planning capacity?
▪ Diverging transposition of provisions of Directive 2012/34/EU at national level, e.g.:
➢ possibility to safeguard capacity exists but is subject to specific national requirements (e.g. capacity can only be reserved for specific types of transport)
➢ possibility for safeguarding of capacity for ad hoc requests (Article 48(2)) not transposed into national law
54
Preliminary Conclusions
In some Member States uncertainties about compliance of TTR with the legal framework lead to serious hesitation to proceed with the implementation of TTR
Adjustments to the legal framework at European level seem required to enable a harmonised implementation of TTR
55
Useful Links (TTR Legal Framework)- Overview of aspects in the legal framework:
http://ttr.rne.eu/legal/
- Documents containing TTR legal evaluations:https://cms.rne.eu/ttr-documents/content/legal-framework
56
Contact TTR Legal Framework
If you have further questions regarding the TTR Legal Framework, please do not hesitate to contact the leader of task force ‘TTR Legal Framework’,
Ms Elisabeth Hochhold.
Project leader 'TTR Legal Framework'Elisabeth [email protected]
57
TTR Commercial Conditions
58
TTR Commercial Conditions: Introduction
Rail capacity is wasted, mainly due to
o Constant changes of planning parameters (both: RU and IM)
o Capacity blocked but not used by stakeholders
To encourage stakeholders to use the process and capacity products as efficiently as possible, common, harmonised commercial conditions have to be applied to avoid misuse/spoiling of capacity (‘who breaks pays’).
TTR Process
ITCommercialConditions
LegalFramework
59
Elements of Commercial ConditionsProcess elements that require steering through commercial conditions:
o Path cancellation by applicant
o Non-usage of a path by applicant
o Cancellation of a partially non-used path by IM
o Path modification by applicant
o Path alteration by IM
Note: A scope extension to requested but not yet allocated paths is under consideration.
HarmonisedCommercialConditions
60
Useful Links (TTR Commercial Conditions)- Overview of commercial conditions basics:
http://ttr.rne.eu/commercial-conditions/
61
Contacts TTR Commercial Conditions
If you have further questions regarding the TTR commercial conditions, please do not hesitate to contact the co-chairs of the project ‘TTR Commercial Conditions’,
Ms Zuhal Nalbant or Ms Zita Koops-Árvai.
Project Co-Chair 'TTR: Commercial Conditions'Zuhal [email protected]
Project Co-Chair 'TTR: Commercial Conditions'Zita Koops-Árvai [email protected]
62
TTR Pilots
63
Introduction to TTR Pilots
In order to test the new approach to capacity management developed in TTR, several pilots have been launched:
o To improve the process
o To detect pressure points
o To use lessons learned for full TTR rollout
64
List of Pilots
Three pilot lines along Rail Freight Corridors (RFCs) were launched in 2017 to introduce capacity models and test the innovative Rolling Planning request based on safeguarded capacity:
o Mannheim – Miranda de Ebro (starting in timetable 2021)
o Antwerp – Rotterdam (starting in timetable 2020)
o Munich – Verona (starting in timetable 2020)
To complement the test results, a network pilot will be conducted on the core network of ÖBB INFRA starting in timetable 2021.
Further pilots and extensions are currently being considered.
65
TTR Pilots: Achievementso Development of functioning organisations for the respective pilots
o Creation of Capacity Models with the support of applicants for TT 2020
o Elaboration of a first tool for visualising the Capacity Model (Electronic Capacity Model Tool / ECMT)
o Availability of a tool (PCS) for placing the first Rolling Planning requests in August 2019
o Good cooperation thanks to highly motivated IMs
o Broad-based willingness of stakeholders (Ministries, Regulatory Bodies, applicants) to participate in the pilots
66
TTR Pilots: Lessons Learnedo Management attention is crucial for the success of the pilots
o Planning and coordination of TCRs respecting 2012/34 Annex VII is still difficult: This is crucial to make requests later than annual requests for freight RUs possible (also now)
o Benefits for passenger RUs must be tested as well
o Ministries of Transport and Regulatory Bodies are required to implement strategic thinking (not only based on existing laws) and allow tests
o Need for increased resources for IT implementation (nat. and internat. level)
o Commercial Conditions required to influence applicants’ path requesting behaviour and IMs’ allocation processes (incentive to respect agreed processes)
o Multi-annual validity of a Rolling Planning request require legal backing
67
Status: TTR PilotsNext steps in 2020
- Lessons learned included in existing pilots
- Mannheim-Miranda de Ebro scheduled to become active
- ÖBB Core Network pilot will launch its first step
68
Useful Links (TTR Pilots)- TTR pilots overview:
http://ttr.rne.eu/pilots/
- TTR pilots concept paper:https://cms.rne.eu/ttr-documents/content/pilots
- TTR pilots communication platform:https://cms.rne.eu/ttr-pilots-communication-platform
69
Contacts TTR Pilots
If you have further questions regarding the TTR process, please do not hesitate to contact the leader of the TTR Pilot project, Mr Daniel Haltner, or the deputy
leader, Mr Philipp Koiser.
Project Leader ‘TTR Pilots’Daniel [email protected]
Deputy Project Leader ‘TTR Pilots’Philipp [email protected]
70
Contacts TTR Pilots
Mannheim – Miranda de Ebro: Mr Michel Dupuis ([email protected])
Munich – Verona: Mr Andri Kopperschmidt ([email protected])
Antwerp – Rotterdam: Mr Freddy Van Der Cruyssen ([email protected]) or Mr Floris Visser ([email protected])
ÖBB INFRA network pilot: Ms Birgit Leber ([email protected])
71
TTR Implementation
72
Implementation in PackagesPre-conditions must be provided in time to start each TTR phase:
All pre-conditions must be implemented nationally as well. Any delayed start of the implementation means late rollout of TTR.
The implementation has already started!
Capacity Strategy
Capacity Model
Path Planning
Capacity Request
TIME-TABLE 2025
Start: August 2021
Start: June 2022
Start: August 2023
Start: December 2023
Start: December 2024
73
Implementation Packages: OverviewAiming for the full rollout of TTR in December 2024, end dates were defined for all packages:
74
Implementation Packages: ContentImplementation packages were created, in which all required developments are bundled:
o Implementation packages 1 & 2: division of roles and tasks under the new TTR process
o Implementation package 3: preparation of all framework conditions (including IT)
o Implementation package 4: commercial conditions and allocation rules
o Implementation package 5: TTR IT landscape
o Implementation package 6: IT micro services for final TTR rollout
75
TTR Implementation as Center Piece of TTR
TTR Pilots
TTR Commercial Conditions
Steering Committee + Programme Management Office
TTR Legal Framework
TTR IT Landscape
TTR Implementation
76
National TTR Implementation ManagersRNE members have been asked to provide nominations for national TTR implementation managers:
The national implementation projects have started in September 2019!
First tasks and alignments are already tackled.
76
No nomination yet
Nomination received
77
Organisation of the TTR Implementation Project
TTR Implementation Project
TTR Core Team
Chair persons of all RNE/FTE TTR projects and task forces:- TTR Pilots project- TTR Commercial Conditions project- TTR IT Landscape project- TTR Legal Framework task force
Chair persons of relevant RNE Working Groups:- WG Sales & Timetabling- WG Temporary Capacity Restrictions- WG Network Statements & CIDs
Chair persons of relevant FTE Working Groups:- WG Passenger- WG Freight
Representative of the Corridor-OSS Community
TTR management and back office:- TTR Steering Committee representative- TTR Programme Management Office- Communications Manager
National TTR projectsto coordinate the
national TTR implementation efforts
to provide and coordinate the TTR process andEuropean TTR framework conditions
Community of National TTR Implementation Managers
78
Implementation StepsShort-term
o Setup of national TTR projects and launch of change managements
o Finalising the definition of pre-conditions
o Test and improve TTR elements
o Gradually implement TTR including all preconditions
Mid-term
o Full TTR implementation for timetable 2025 (starting December 2024)
o Monitoring and improving the process
79
Successful Implementation of TTR
The market needs TTR – we must start performing now!
• Railways lose market share and interest in investing in railways
decreases.
• Therefore, TTR is highly anticipated by many European stakeholders.
• The status quo is not an option anymore.
• We cannot wait for others to do our job.
• Even the ambitious timeline of implementing for TT 2025 was
labelled as too late by the CEOs of freight RUs (‘30 by 2030’).
80
Contacts TTR Implementation
If you have further questions regarding the TTR implementation, please do not hesitate to contact the leader of the TTR Implementation project,
Mr Aurelio Di Paola, or the deputy leader, Mr Philipp Koiser.
Project Leader ‘TTR Implementation’Aurelio Di [email protected]
Deputy Project Leader ‘TTR Implementation’Philipp [email protected]
81
Links and ContactsT
TR S
tee
rin
g C
om
mit
tee
RNE PresidentHarald [email protected]
FTE PresidentStephan [email protected]
RNE Vice PresidentGuus de [email protected]
Co-Leader TTR ProgrammePhilipp [email protected]
Co-Leader TTR ProgrammeMartin [email protected]
Deputy Leader TTR ProgrammeSebastian [email protected]
TR P
rogr
amm
e M
anag
em
en
t O
ffic
e
Further information can be found online: ttr.rne.euTTR working material can be downloaded at: https://cms.rne.eu/ttr-documents
