ERA s view on Implementa3on of Telema3c TSIs

Transcription

1 ERA s view on Implementa3on of Telema3c TSIs Interoperability in Prac3ce - HitRail workshop Brussels, 09/10/2014 Stefan JUGELT N 1

2 Content of this presenta3on 1. Legal framework for telematics TSI s 2. Functionalities to be implemented for telematics TSI s TAP TSI TAF TSI 3. Implementation of telematics TSI s Governance for the telematics TSI s Master plan for implementation 4. Monitoring of the implementation N 2

3 TAP TSI: Direc3ve 2008/57/EC on the interoperability of trans- European rail system (Annex II - 2.5: Telema3cs Applica3ons): a) applica)ons for passenger services, including systems providing passengers with informa)on before and during the journey, reserva)on and payment systems, luggage management systems and management of connec)ons between trains and with other modes of transport. European Rail Passengers Rights Regula3on EC/1371/2007 (Art 10 and Annex II). 1. In order to provide the informa)on and to issue )ckets referred to in this Regula)on, railway undertakings and )cket vendors shall make use of CIRSRT, to be established by the procedures referred to in this Ar)cle. In place since 2011 European Rail Legisla3on for telema3cs TSI s TAF TSI: Direc3ve 2008/57/EC on the interoperability of trans- European rail system (Annex II - 2.5: Telema3cs Applica3ons): b) applica)ons for freight services, including informa)on systems (real- )me monitoring of freight and trains), marshalling and alloca)on systems, reserva)on, payment and invoicing systems, management of connec)ons with other modes of transport and produc)on of electronic accompanying documents. In place since 2006 Revised in , approved by RISC in June 2014 à see: N 3

4 Purpose of telema3cs TSIs TAP TSI: The TAP TSI prescribes protocols for the data exchange of: 3metables, tariffs, reserva3ons, Fulfilment, Informa3on to passengers in sta3on and vehicle area train running informa3on, etc. TAF TSI: The TAF TSI prescribes protocols for the data exchange of: Consignment Note data Path Request Train Prepara3on Train Running Forecast, etc. The TAF TSI prescribes furthermore databases: Rolling Stock Reference Databases Wagon and Intermodal Unit Opera3onal Database Trip plan for wagon / Intermodal unit Reference Files (such as loca3on ID, company ID, dangerous goods, etc.). N 4

5 Example: TAP TSI 3metable data Purpose: - Exchange of 3metable data with other RU s, 3rd par3es and public bodies Condi3ons: - Annual 3metable must be published at least two months before entering into force - Timetable changes must be published at least 7 days in advance How: - File in EDIFACT- format document B.4) (technical RU Other RU s Public bodies 3 rd parties N 5

6 Example: TAF TSI - RU/IM Communica3on Basic Parameters Functionalities: Long-term planning, Path Request on Short Notice, Train Preparation, Train Running Forecast, Service Disruption Information and Train Location. LRU.. RU 1 RU 2 RU N IM 1 IM 2 IM 3 IM N N 6

7 Governance for the telema3cs TSI s RepresentaBv e bodies European Commission ERA General assembly TAP TSI TAP TSI steering commi>ee *) TSGB Advisory board TAF TSI TAF TSI steering commi>ee Joint sector group (JSG) TAF TSI cooperabon WG General Manager Rail freigth corridors, rail sector TSGB suppliers Provide services TSGB licensees *) the TAP TSI steering committee will be replaced by TSGB once in place N 7

8 Tasks of the TAF/TAP Na3onal Contact Point (NCP) 1. Act as point of contact between ERA, the TAF/TAP Steering Commifee and railway actors 2. Communicate the concerns and issues of the railway actors in the Member State to the TAF/TAP Steering Commifee via the co- chairs 3. Liaise with the Member State Railway Interoperability and Safety Commifee (RISC) member 4. The Member State ensures that all licensed Railway Undertakings and other railway actors are provided with NCP details 5. Make the railway actors in the Member State aware of their obliga3ons under the TAF and TAP regula3ons and that they must comply. 6. Ensure that an en3ty is appointed to be responsible for popula3ng the Central Reference Domain with primary loca3on codes 7. Facilitate informa3on sharing between the Member State railway actors N 8

9 Master plan for implementa3on TAP TSI: : The Master plan draged by the TAP TSI phase one team and submifed to EC in may 2012 May 2013: A consolidated master plan taking into account the individual master plans was submifed by the rail sector 40 railways and groups of railways have submifed their individual plans, covering over 70 individual RU s and IMs. June 2013: the member states accepted the master plan in the RISC. The plan was published by ERA as TAP TSI technical document B.62 in December TAF TSI: January 2013: the Commission Accepted a NEW consolidated Master Plan to replace the old one (from 2007) whose implementa3on was delayed. The plan was published by ERA in May A total of 58 companies, represen3ng over 85% of the total tonne- and track- Kilometres in Europe responded with their individual plans for implementa3on The implementa3on plans of the individual companies having contributed to the new Master Plan were sent to the Commission together with the new Master Plan N 9

10 Master plan for implementa3on Retail functions: The master plan defines the implementation dates for the functionalities of the TAP TSI retail functions N 10

11 Master plan for implementa3on RU/IM-functions: The master plan defines the implementation dates for the functionalities of the TAF TSI RU/ IMcommunication functions Common interface implementation Reference files population RSRD Wagon movement WIMO Consignment Data Train Run Short term PR Shipment ETA Service Disruption Train Ready Train Composition TID final N 11

12 Management of reference files Which Reference files have to be made available: The Loca3on Reference File which uniquely iden3fies physical rail points (e.g. sta3ons, customer sidings, loading places) The Partner Reference File uniquely iden3fies all rail actors who exchange informa3on (Company Codes) Further reference files (e.g. for reserva3on, 3metable data, tariff data). Which requirements have to be respected for reference files: 1. reference files must be available and accessible to all service providers. 2. The data must represent the actual status at all 3mes. What is the Central reference database (CRD)? Central database to store the reference files about partners (companies) and rail loca3ons (e.g. sta3ons, loading points) à TAF TSI Common Components Group (CCG) is charged with the development, maintenance and on- going opera3ons of CRD N 12

13 Status of deployment of reference files (loca3on data) Central Reference File Database (CRD) Data population started May Users are registered on CRD Primary Location codes are populated for 21 IM Minimum one IM published Not populated yet IM not CCG-member N 13

14 Monitoring of TAF/TAP TSI implementa3on by ERA ERA will monitor the progress of the TAF/TAP TSI implementa3on TAF TSI: An ERA coopera3on working party for the implementa3on of the TAF TSI will be set up (NCP s, railway representa3ve bodies via Joint sector group, corridor managers if necessary) Working party will monitor the implementa3on based on rail freight corridors Results will be available on the ERA- website (e.g. which func3on implemented on which corridor) TAP TSI: A similar Working party will be set- up in 2015 N 14

15 Monitoring of TAF/TAP TSI implementa3on by ERA Based on GIS (Geographical Informa3on System) to present maps with 9 freight corridors Data stored in linked SharePoint lists IT co- opera3on tool will be available online (24/24, 7/7) N 15

16 Source Documents Content TAF TSI > 62/2006/EC > 328/2012/EC > 280/2013 TAF TSI - appendices TAF TSI Masterplan TAF Implementa3on Guides TAP TSI applica3on guides Company Code Sign up for CRD Source h>p://eur- lex.europa.eu h>p:// Register/Pages/CR- TAF- TSI.aspx h>p:// Register/Documents/TAF- TSI- Master- Plan.pdf h>p:// h>p:// Register/Pages/TAP- TSI.aspx h>p:// h>ps://crd.tsi- cc.eu/crd/login.acbon 16

17 Thank you for your kind afen3on: E- mail: N 17