ERA - OTIF regional workshop Introduction of the general framework of Telematics application for freight (TAF) Vienna, 27 April 2016

Transcription

1 ERA - OTIF regional workshop Introduction of the general framework of Telematics application for freight (TAF) Vienna, 27 April

2 TAF TSI Common Components Central Reference Files Common Interface Certification Authority 22 April

3 Regulation 1305/2014 and 454/2011 Telematics Application for Freight Services and Telematics Application for Passenger Services Both Regulation requires from Rail Industry to support certain business processes by exchanging of standardized messages. Involved Actors are: Infrastructure Manager (IM) Railway Undertakings (RU) Waggon keeper (WK) Station Master (SM) Legal background 22 April

4 TAF TSI Functions Grouped Joint IM-RU Functions Reference Files Common Interface Short Term Path Request Train Preparation Train Running Information Train Forecast Service Disruption Deviations from plan (TAP) (Train Identifiers) RU (fright) Only Functions * Consignment Note Data WIMO Wagon Movement Shipment ETA * Commercial part of TAP is not considered in the table 22 April

5 Architecture Supporting Peer2Peer ISR Orfeus HMI Reference files Location ID Company ID CI CI CRD Common Meta Data Certificate Authority RU CI IP Network CI Wagon Ref. Files CI Wagon Ref. Files RU CI CI CI CI CI - Common Interface IM - Infrastructure Manager RU - Railway Undertaking HMI - Human Machine Interface SM - Station Master CRD Central Reference File Database IM 1 IM 2 SM CI RU CI RU RU CI RU RU 22 April

6 Reference Files Regulation 1305/2014 For the operation of freight trains on the European network the following reference files must be available and accessible to all service providers (IMs, RUs, logistic providers and fleet managers)... Centrally stored and administrated: Reference File of the Coding for all IMs, RUs, Service provider companies; Reference File of the Coding for Freight Transport Customers; Reference File of the Coding of Locations (Primary and subsidiary). 22 April

7 Regulation 1305/ Data Quality For data quality assurance purposes, the originator of any TSI message will be responsible for the correctness of the data content of the message at the time when the message is sent. Where the source data for data quality assurance purposes is available from the databases provided as part of the TSI, the data contained within those databases must be used for data quality assurance.. 22 April

8 Regulation 1305/2014 Appendix III Tasks to be undertaken by the TAF/TAP National Contact Point (NCP) Task 6 Work with the Member State to ensure that an entity is appointed to be responsible for populating the Central Reference Domain with primary location codes. The identity of the appointed entity shall be reported to DG MOVE for appropriate distribution. 22 April

9 TAF TSI Master Plan 22 April

10 Reference Files Content Country (ISO 3166) Company Location Primary Location Subsidiary Location Subsidiary Location Type 22 April

11 Reference File Country The Country code is as part of Location Code. Locations are unique per Country 22 April

12 Reference File Company The Company Code is part of location code. Also the identification by the Company code is a pre-condition for the usage of the Common Interface, as it is used for identification in the Message Header of TAF / TAP messages. 22 April

13 Allocation of Company Codes Status of registered Companies December 2015 Companies Passenger Freight Infrastructure Others Companies UIC (Allocation Entity) CRD (operated by RNE ) TAF / TAP Actors subscribe check, register maintain CRD Access to company codes Subscription + Maintenance Fee UIC RNE Maintenance Agreement CCS User Agreement 22 April

14 Apply for a Company code at European central entity At the time being this is UIC, independent if company is UIC member or not It is the same as known by RICS code Apply at Get registered as Company After registration the company code will be maintained in the Central Reference File Database (CRD) 22 April

15 Company coding used Message sender and receiver <MessageHeader> <MessageReference> <MessageType>4005</MessageType> <MessageTypeVersion>5.3.0</MessageTypeVersion> <MessageIdentifier>7aeb53f5-cbc8-4d ac9592bc62</MessageIdentifier> <MessageDateTime> T16:30: :00</MessageDateTime> </MessageReference> <Sender>0080</Sender> <Recipient>2180</Recipient> </MessageHeader> Responsible IM in LocationFileDatasetMessage <CountryCodeISO>HU</CountryCodeISO> <LocationPrimaryCode>11361</LocationPrimaryCode> <LocationPrimaryInformation> <LocationPrimaryName>Nyékládháza</LocationPrimaryName> <ResponsibleIM>0055</ResponsibleIM> <PrimaryLocationNameASCII>NYEKLADHAZA</PrimaryLocation 22 April

16 Location Reference File Location is a place, a geographic point, inside or outside the rail network, which is needed to be identified for operational, technical, administrative or statistical purposes. This can be either a Railway or a Customer location Primary Location This location is a network rail point managed by an Infrastructure Manager (IM). Code is managed nationally by an allocation entity May be an Infrastructure Manager May be a national Location entity 22 April

17 Primary Location Examples Trains can start, end, stop, change line and time needs to be provided. 22 April

18 Location coding example Primary location example 22 April

19 Location coding used In the messages always if it refers to locations. <TrainLocationReport> <Location> <CountryCodeISO>SE</CountryCodeISO> <LocationPrimaryCode>3844</LocationPrimaryCode> <PrimaryLocationName>Stangby</PrimaryLocationName> </Location> <TrainCompositionJourneySection> <JourneySection> <JourneySectionDestination> <CountryCodeISO>SI</CountryCodeISO> < LocationPrimaryCode>44361</LocationPrimaryCode> </JourneySectionDestination> 22 April

20 Subsidiary Location Subsidiary Location identifies a location as a part of primary location e.g. a junction, a signal, a marker point, etc. This may be a non-rail point or a rail point that is not managed by an Infrastructure Manager (IM). Subsidiary location without Primary location is not possible. It is always in combination with a Primary Location. Subsidiary locations have subsidiary type code 22 April

21 Subsidiary Location Examples 22 April

22 Subsidiary Location Type 22 April

23 Subsidiary Location Type Subsidiary location Types are part of the TAF coding schema At the type code it is indicated which entity is in principle allowed to maintain the subsidiary locations 22 April

24 Subsidiary Location example 22 April

25 Common Components System Implementation of Reference Files 22 April

26 What is the Common Components System? Central Reference Files Database (CRD) * Coding of Locations and Companies Common Metadata Certificate Authority * which provides X509 certificates for secure communication Common Interface (CI) a software package which is locally installed within the user s IT environment *) In the regulation also mentioned as Central Repository Domain 22 April

27 TAF TSI Business Process & RNE Applications 22 April

28 Who developed CCS? The TAF TSI Common Components Group (CCG) a Special Group of UIC have developed the CC and are in roll-out since January Stakeholders Main European Infrastructure Managers and some smaller ones o DB Netz, RFF, RFI, Infrabel, ProRail, PLK, MAV, NetworkRail, Eurotunnel, etc. Largest Freight Railway Undertakings and some smaller ones o DB Schenker Group, SNCF fret, Trenitalia, RCA, Green Cargo, etc. Current Supplier (contractor) EVRY - largest IT supplier in Nordic countries 22 April,

29 The CCG General Assembly on 9 December 2014 approved the transfer of the Common Components to RNE with all the verification transfer conditions successfully implemented. The CCG was dissolved on 31 December What was Transferred?: Software IP Rights (IPR) Service Contracts Transfer of the CC to RNE As of 1 January 2015, RNE is now in charge of further development, maintenance and on-going operations of the TAF TAP Common Components. 22 April

30 Location Coding Implementation 22 April

31 Allocation Process Location Data 22 April

32 Sign up page for CRD Precondition is to sign a CCS user Agreement with RNE 22 April

33 How to feed the Reference files 1) CSV file Maintenance of location reference files by national entities (or registered companies for defined subsidiary type codes) Central Reference File Database (CRD) 2) WEB GUI (Browser) Https CRD Location codes: - Primary - Subsidiary Common Interface 3) Legacy location database (messaging) A B C D Configuration Mapping Metadata Routing and Security 22 April 2016

34 Ask for import templates at RNE by Deliver an CSV file with the qualified Location coding by to RNE Find more information in the TAF / TAP sector handbook in chapter 9 Initial Population content/uploads/2015/11/ _tap_taf_ru_im_sector- Handbook_v2.1.2_1.1.pdf 22 April

35 Reference file distribution CRD Reference file download via authenticated WS directly to a legacy system Filter parameters Search Export via HMI Filter parameters (e.g. last modified date, country, subsidiary type code) CI local Instance Replication Reference files via Web Service (WS) to Local Instance Filter parameters (e.g. last modified date, country, subsidiary type code) Scheduler defined by Local Instance of CI Company Legacy System Search and export via Browser on Local Instance Reference file download via WS to Legacy System Filter parameters (e.g. last modified date, country, subsidiary type code) Scheduler to be defined by Legacy System 22 April

36 Two variants of Reference file replication Via local Common Interface CRD Directly from CRD to legacy System via secure Web service Deletions Locations Reference file download via authenticated WS and registered user directly to a legacy system Filter parameters CI CI local Instance Deletions Locations Locations Legacy System Company 22 April

37 Status of Location Codes with ERA ERA public WEB GUI (Browser) Single Request for Locations * RNE ERA CCS User Agreement *) all company code as PDF 22 April

38 Status of Location Codes At least 1 large IM published In Progress Not populated yet Non ex CCG IM ~ Primary Locations for 39 IM ~ 330 Subsidiary Location, Type 36 ~ 400 Subsidiary location, Type 37 ~ Subsidiary Location, Type 41 ~ Subsidiary Locations, Type 42 03/ April

39 Common Interface 22 April

40 Regulation 1305/ Common interface The common interface is mandatory for each actor in order to join the rail interoperability community The common interface has to be able to handle: message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of the outgoing messages, authenticity verification of the incoming messages decryption of incoming messages conformity checks of incoming messages according to metadata, handling the single common access to various databases Where a Common Interface is in common use with the TAP TSI, the development and changes must be in line with TAP TSI, in order to achieve optimum synergies. 22 April

41 Architecture Supporting Peer2Peer ISR Orfeus HMI Reference files Location ID Company ID CI CI CRD Common Meta Data Certificate Authority RU CI IP Network CI Wagon Ref. Files CI Wagon Ref. Files RU CI CI CI CI CI - Common Interface IM - Infrastructure Manager RU - Railway Undertaking HMI - Human Machine Interface SM - Station Master CRD Central Reference File Database IM 1 IM 2 SM CI RU CI RU RU CI RU RU 22 April

42 Common Interface Reference Implementation 22 April

43 CI Installation Locally installed at user company CI Installation is automated using an installer and is bundled as executable. Separate installable for Windows and Linux platforms. This will install the following software : MySQL 5.x or 5.5 (64bit) Java 1.8.x JBoss 6.x with ESB 4.9 LI application components Administration after installation via a Web Browser from remote Language of all documentation and User Guide is English GUI can be translated (effort to be taken) 22 April

44 Communications 22 April

45 Certificate Authority (CA) RNE acts as a Certificate Authority (CA) and provides X-509 certificates to support secure communication between partners, along with message-based encryption and signature. X-509 certificates are requested for: SSL/TLS communication on Https between CI A and CI B, and between CI A / CI B and CRD Encryption of messages Signature of messages. Only certificates from the RNE Certificate Authority (with the same root) will trust each other. 22 April

46 The Common Interface Reference Implementation was build by the TAF TSI Common Components Group based on Requirements TAF Common interface TAP Common Interface for RU / IM Communication TAF Appendix E : TAF TSI Appendix D.2: Appendix E COMMON INTERFACE European public tender Stakeholder funding EU Commission funding CI Reference Implementation 22 April

47 Mapping Definition 22 April

48 Message Mapping example Before mapping 21020[ , , , ] MMTG Mertingen Bahnhof MRIU München-Riem Ubf After Mapping <?xml version="1.0" encoding="utf-8"?><trainrunninginformationmessage xmlns=" xmlns:n1=" <MessageHeader> <MessageReference> <MessageType>2002</MessageType> <MessageTypeVersion>5.3</MessageTypeVersion> <MessageIdentifier>3e0c277a-e0bc a1a-a60fbec8ae55</MessageIdentifier> <MessageDateTime> T15:00: :00</MessageDateTime> </MessageReference> <Sender n1:ci_instancenumber="01">0080</sender> <Recipient n1:ci_instancenumber="02">3400</recipient> </MessageHeader> <MessageStatus>1</MessageStatus> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledTimeAtHandover> T10:17:48+02:00</ScheduledTimeAtHandover> </OperationalTrainNumberIdentifier> <ReferenceOTN> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledTimeAtHandover> T10:17:48+02:00</ScheduledTimeAtHandover> </OperationalTrainNumberIdentifier> </ReferenceOTN> <TrainLocationReport> <Location> <CountryCodeISO>DE</CountryCodeISO> <LocationPrimaryCode>17001</LocationPrimaryCode> <PrimaryLocationName>Mertingen Bahnhof </PrimaryLocationName> <LocationSubsidiaryIdentification> <LocationSubsidiaryCode n1:locationsubsidiarytypecode="1">830 </LocationSubsidiaryCode> <AllocationCompany>0080</AllocationCompany> </LocationSubsidiaryIdentification> </Location> <LocationDateTime> T15:02:11+02:00</LocationDateTime> <TrainLocationStatus>03</TrainLocationStatus> <TrainDelay> <AgainstBooked>+0151</AgainstBooked> </TrainDelay> </TrainLocationReport> <TransferPoint> <CountryCodeISO>DE</CountryCodeISO> <LocationPrimaryCode>17317</LocationPrimaryCode> <PrimaryLocationName>München-Riem Ubf </PrimaryLocationName> </TransferPoint> </TrainRunningInformationMessage> 22 April

49 Message Processing Graphical Overview Before mapping After Mapping <?xml version="1.0" encoding="utf-8"?><trainrunninginformationmessage xmlns=" xmlns:n1=" <MessageHeader> <MessageReference> <MessageType>2002</MessageType> <MessageTypeVersion>5.3</MessageTypeVersion> <MessageIdentifier>3e0c277a-e0bc a1a-a60fbec8ae55</MessageIdentifier> <MessageDateTime> T15:00: :00</MessageDateTime> </MessageReference> <Sender n1:ci_instancenumber="01">0080</sender> <Recipient n1:ci_instancenumber="02">3400</recipient> </MessageHeader> <MessageStatus>1</MessageStatus> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledTimeAtHandover> T10:17:48+02:00</ScheduledTimeAtHandover> </OperationalTrainNumberIdentifier> <ReferenceOTN> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledTimeAtHandover> T10:17:48+02:00</ScheduledTimeAtHandover> </OperationalTrainNumberIdentifier> </ReferenceOTN> <TrainLocationReport> <Location> <CountryCodeISO>DE</CountryCodeISO> <LocationPrimaryCode>17001</LocationPrimaryCode> <PrimaryLocationName>Mertingen Bahnhof </PrimaryLocationName> <LocationSubsidiaryIdentification> <LocationSubsidiaryCode n1:locationsubsidiarytypecode="1">830 </LocationSubsidiaryCode> <AllocationCompany>0080</AllocationCompany> </LocationSubsidiaryIdentification> </Location> <LocationDateTime> T15:02:11+02:00</LocationDateTime> <TrainLocationStatus>03</TrainLocationStatus> <TrainDelay> <AgainstBooked>+0151</AgainstBooked> </TrainDelay> </TrainLocationReport> <TransferPoint> <CountryCodeISO>DE</CountryCodeISO> <LocationPrimaryCode>17317</LocationPrimaryCode> <PrimaryLocationName>M?nchen-Riem Ubf </PrimaryLocationName> </TransferPoint> </TrainRunningInformationMessage> 22 April

50 Message Processing Graphical Overview 22 April

51 Status on Common Interface implementation 10 CI in Test 26 CI with Data exchange CI = Common Interface 01/

52 Cost model Costs Effort / support Common Interface One off Registration Fee Yearly Maintenance Fee Reference Files One off Registration Fee Yearly Maintenance Fee 900 Invests Maintenance Helpdesk Incident desk (24h) Software Updates Third Party Product Upgrades Management (User, Data) 22 April

53 How to become a CCS user? Access to CCS for TAF and TAP actors is based on a user agreement that needs to be signed beforehand: In order to become a CCS User Please provide the following information to support.ccs@rne.eu: Name, company and department Contact details (phone, , postal address) More information about CCS can be found on our website at: 22 April

54 Thank you! 54