European Rail Conference 2014 Harald Reisinger - RNE CIO

Transcription

1 European Rail Conference 2014 Harald Reisinger - RNE CIO Lille, 8 May 2014

2 RailNetEurope (RNE) Introduction RNE Members Network RailNetEurope was established in 2004 currently has 37 members is an umbrella organisation of Infrastructure Managers (IMs)/Allocation Bodies (ABs) enhances international rail traffic delivers solutions and tools for international infrastructure management provides information on the European railway infrastructure is service provider of choice for the new corridor organisations

3 RailNetEurope (RNE) Members Nearly all European IMs and ABs are RNE Members Exceptions: IMs/ABs from Ireland, Northern Ireland, the Baltic States, and parts of the Balkan area IMs from Greece and Turkey are in current talks about RNE Membership RNE Membership Status 08/2012

4 RailNetEurope (RNE) Business The core business of RNE is to provide support to European Rail Infrastructure Managers with the planning, selling and managing of international train paths. RNE is following a market-oriented approach. RNE is designing the entire rail infrastructure production process. Sales & Timetabling Operations & After Sales Corridor Management In the end of 2010 RNE has additionally received the mandate to become the service provider of choice and expert support provider for corridor organisations.

5 RNE IT Developments (3) Telematics TSIs (TAF & TAP) RNE is coordinating IMs RNE is leading Sector Coordination (Cluster) and most of Telematics Expert Groups RNE is asked to coordinate IMs during TAF/TAP TSI implementation RNE is leading Train ID Project IM coordination within TAF/TAP TSI framework Legal text was rewritten based on sector requirements Data exchange was updated based on Sector (RNE IT) input RNE IT systems are TAF TSI compliant RNE IT systems (PCS/TIS) are processing TAF/TAP messages TIS is using Common Interface (CI)

6 RailNetEurope and its IT systems at the TAF and TAP TSIs Taking up the TAF / TAP TSIs challenge 2006: RNE started coordinating IMs for TAF TSI implementation 2007: RNE headed TAF TSI IM Cluster + contributed to working groups 2009: RNE mandated to coordinate tasks in TAF and TAP TSIs 2010: - specifications for TAF TSI messages agreed - Implementation Guides finalised 2011: - coordinating IMs in Steering Committee - expert advice to bring TAF knowledge into TAP 2012: RNE coordinated IMs through TAF TSI Master Plan development 2013: - ERA's TAF TSI text revision and WP message changes with RNE support - RNE assists with harmonised IM implementation

7 RNE IT TAF TSI phases Phase 1 IT Specifications Phase 2 Development Phase 3 Deployment (Pilot) Detailed IT specifications and master plan: WG results were available Change Requests (CR) are ready Master Plan was ready The ERA WP has agreed on the Change Requests TAF TSI has to be amended Development and first deployment: IM/RU development projects starts Lifecycle principle Using existing data exchange (company solutions, TIS, PCS,...) Using Reference Files and Common Interface Migrate to a TAF/TAP TSI data exchange Phase 4 TAF TSI in operation Deployment and Pilot: Finalising company deployment Pilot phase for new processes and systems (Train ID) Data exchange is based on TAF TSI format and structure TAF/TAP Change Management is in place

8 RailNetEurope and its IT systems at the service of international rail 2004: European railway IT landscape a patchwork of already-existing but perhaps under-used software tools Therefore one of RNE s main tasks since 2004 has been to: refine and develop these tools improve digital information flows concerning international rail traffic make them seamless align IT tools with emerging EU-wide standards such as TAP/TAF TSIs

9 RNE Train Information System (TIS)

10 RailNetEurope and its IT systems TIS EUROPTIRAILS until 2011, thereafter Train Information System (TIS) : participation in EUROPTIRAILS meetings, transfer preparation 2007: RNE takes over responsibility for EUROPTIRAILS 2008: in-depth analysis, further roll-out 2009: quality improvement initiative 2010: TAF TSI pilot started 2011: Data Exchange function improved; reporting functions for Train Performance Management developed 2012: TIS V.4 (incl. TAF TSI and new reporting features) released; pilot for TAF-TSI Common Interface Since January 2013: TIS first productive TAF TSI application in Europe

11 RNE Train Information System (TIS) Train Information System (TIS) RNE system for real-time international train run monitoring Originally developed by consortium of 6 IMs Handed over to RNE in 2007 RNE developments Improvement of data quality Roll-out to other IMs (currently 16 IMs are users) Introduction of additional functions

12 RNE Train Information System (TIS) Flash Animation

13 RNE Train Information System (TIS) Functions Main TIS functions: Real-time information Real-time traffic data for each train Graphical interface Added value for: Supports IMs/ABs traffic management Supports RUs/Terminals own production system Reporting Pre-defined reports Customisable reports Information source for other projects Information source for IMs/RFCs and RUs in identification of problems Support for other projects such as Train Performance Management and EPR Data exchange Raw data exchange Filtering function TAF TIS pilot for CI (Common Interface) Data Exchange via UIC messages/day Data Exchange via CI TAF/TAP messages/day

14 RNE Train Information System (TIS) The right tool... to meet TAF-TSI requirements over 65 million messages were processed in 2013 messages can already be sent in TAF TSI format & structure TAF TSI messages are currently exchanged per week... to comply with new Rail Freight Regulation (913/2010) Train monitoring on corridors Train Performance Management (performance schemes) Including terminals on the corridors... to ensure availability of new products Support terminals with real-time information Dedicated national trains in TIS Functions to improve Traffic Control Centre communication

15 TIS Data Exchange The IMs (TIS Members) are sending Data to the Core System CTT (Contracted TimeTable) Train Running Advice Train Running Forecast Delay Reasons 7 May 2014

16 TIS Data Exchange TIS is sending filtered Data to IMs and RUs. CTT (Contracted TimeTable) Train Running Advice Train Running Forecast Delay Reasons 7 May 2014

17 RNE Train Information System (TIS) Figures (1) During one month, more than international trains are recorded TIS monitors in real time international trains at over reporting points 7 May 2014

18 RNE Train Information System (TIS) Figures (2) Almost 6 million messages are processed monthly by the systems 7 May 2014

19 RNE Train Information System (TIS) Figures (3) 7 May 2014

20 RNE Train Information System (TIS) Rollout Participants: Current participants: AT, BE, CH, CZ, DE, DK, FR, HU, HR, IT, LU, NL, PL, SE, SI, SK Potential future participants: BG, ES, NO, PT, RO

21 RailNetEurope and its financing Financing RNE IT activities Until 2008: Membership Fees only Since 2008: additional funding thanks to European Union 2008-EU S 2010-EU S 2011-EU S 2012-EU S

22 Contact Information RailNetEurope Oelzeltgasse 3/ Vienna AUSTRIA Phone Fax mailbox@rne.eu Web Map RailNetEurope Joint Office