1. TAF TSI – Master Plan Brussels, 25 September 2012 Information Workshop

2. 2 Telematic Applications for Freight Agenda Introductions Master Plan –Master Plan Timelines –Consolidated Master Plan –Timeline Governance Structure –Merged RU/IM Governance –Expert Working Groups Roles and Responsibilities –RU Representation –Change Management Requirements The TAF TSI Functions Explained Common Components Questions and Answers

3. 3 Telematic Applications for Freight MASTER PLAN Master Plan Timelines Consolidated Master Plan Timeline

4. 4 Telematic Applications for Freight Master Plan Responses Infrastructure Managers Track-Kms Railway Undertakings Tonne-Kms

5. 5 Telematic Applications for Freight Master Plan Status DT Produced and Delivered Master Plan – 10 May 2012 –Launched in January 2012 Preliminary Master Plan is now Published on ERA Website –http://www.era.europa.eu/Document-Register/Pages/CR- TAF-TSI.aspxhttp://www.era.europa.eu/Document-Register/Pages/CR- TAF-TSI.aspx Database was updated and new Queries were developed Complete Corridor analysis has been prepared

6. 6 Telematic Applications for Freight Functions Grouped Joint IM-RU Functions Train Running Information Train Forecast Service Disruption Train Enquiries Train Preparation Infrastructure Restrictions Adhoc Path Request Common Interface Reference Files (Train Identifiers) RU Only Functions Consignment Note Data WIMO Wagon Movement Shipment ETA

7. 7 Telematic Applications for Freight Master Plan Results

8. 8 Telematic Applications for Freight Master Plan Target Implementation Dates

9. 9 Telematic Applications for Freight Consolidated Master Plan No company may be obligated to respect another date other than submitted Consolidation with application solutions to be delivered by 3rd Quarter 2012

10. 10 Telematic Applications for Freight THE TAF TSI FUNCTIONS EXPLAINED

11. 11 Telematic Applications for Freight Reference Documentation All references can be found on the UIC site –eBusiness > TAF TSI > CR TAF TSI (http://www.uic.org/spip.php?article446)http://www.uic.org/spip.php?article446 Directive 2001-16 –http://eur- lex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexapi!prod!CELE Xnumdoc&numdoc=32001L0016&model=guichett&lg=enhttp://eur- lex.europa.eu/smartapi/cgi/sga_doc?smartapi!celexapi!prod!CELE Xnumdoc&numdoc=32001L0016&model=guichett&lg=en TAF TSI Regulation –http://ec.europa.eu/transport/rail/interoperability/interoperability/tel ematic_applications_en.htm#tophttp://ec.europa.eu/transport/rail/interoperability/interoperability/tel ematic_applications_en.htm#top Strategic European Deployment Plan (SEDP) –http://www.era.europa.eu/Document-Register/Pages/CR-TAF- TSI.aspxhttp://www.era.europa.eu/Document-Register/Pages/CR-TAF- TSI.aspx

12. 12 Telematic Applications for Freight Implementation Guidelines The Implementation Guidelines are available on the UIC site : –> eBusiness > TAF TSI > TAF Deployment –http://www.uic.org/spip.php? article447http://www.uic.org/spip.php? article447 CRD Train Monitoring Train Preparation Short Term path request Wagon Order Wagon Movement Reference files (not in CRD) RSRD Train IDent

13. 13 Telematic Applications for Freight Source Documents ContentSource TAF TSIhttp://www.uic.org/spip.php?article446 Masterplanhttp://www.era.europa.eu/Document- Register/Documents/TAF- TSI%20Preliminary%20Master%20Plan.pdf TAF Implementation Guides http://www.uic.org/spip.php?article447 Implementation Guide Reference Files http://tap-tsi.uic.org/What-s- new,4.html#outil_sommaire_7 Import templatehttp://www.uic.org/spip.php?article447 Company Codehttp://www.uic.org/spip.php?article311 Sign up for CRDhttps://crd.tsi-cc.eu/CRD/Login.action

14. 14 Telematic Applications for Freight Source Documents - Metadata Catalogue Version 5-2 will be published by ERA 4Q 2012 as draft version To be submitted to RISC for final approval DT Working Draft 5.2.1 shall be used for implementation and will be published on the ERA website as ‘Developer Version’ Impacted issues –Timetable and Path Request messages (WG5 – Joint Planning) –Train composition (WG 3 – Joint Operations) DT will provide ‘self-contained’ schemas by Message also so to be published by ERA

15. 15 Telematic Applications for Freight GOVERNANCE STRUCTURE

16. 16 Telematic Applications for Freight Governance Evolution - Proposed

17. 17 Telematic Applications for Freight EG 1 - Planning EG 1 – Planning - Deliverables Change Requests for message catalogue concerning path request Change Requests for path request related code lists Updated implementation guidelines especially to reflect Change Requests If necessary, proposal of modification for TAP TSI and TAF TSI core text

18. 18 Telematic Applications for Freight EG 2 - Operations EG 2 – Operations - Deliverables Change Request for message catalogue and updated implementation guidelines concerning operations Change requests for new messages and new chapters for implementation guidelines for passenger train composition Change Request for operations related code lists If necessary, proposal of modification for TAP TSI and TAF TSI core text

19. 19 Telematic Applications for Freight EG3 – IT and Reference Data EG 3 – IT and Reference data - Deliverables Change requests for message catalogue and update implementation guidelines concerning reference data (if required) Change request for reference data related code lists

20. 20 Telematic Applications for Freight EG 4 – Train ID EG4 – Train ID - Deliverables Change Requests for message catalogue and updated implementation guidelines concerning the identifiers Change Requests for new messages and new chapters for implementation guidelines for creation/updating identifiers Review document of the current state of the stakeholder impact analysis Pilot plan for use of new identifiers, including identification of stakeholders able for transmitting messages containing Train ID for testing/piloting

21. 21 Telematic Applications for Freight 5.2 Short-term workplan (6-months) Consolidated plan –Due six months after publication, proposed delivery end of November –Set up the necessary expert groups –DT to visit the outliers – see if there is any room to speed up implementation or find interim approaches –Develop detailed workplan for implementation Work in cooperation with the established working groups (RU and IM) Consolidation of TAF and TAP plans for RU and IM… Change Control Management –Consolidated input to ERA Workshops

22. 22 Telematic Applications for Freight Realisation of the Reference File Function Master PlanRequirements Location Ident Company Ident (Country Code)

23. 23 Telematic Applications for Freight Reference File Country Identified by the Country Code ISO 3166-1 alpha-2 optional attribute –UIC Country Code (leaflet 920-14)

24. 24 Telematic Applications for Freight Reference File Company Companies –Railway Companies –Other Transport bodies –Any company involved in the rail transport chain Centrally allocated and managed http://www.uic.org/spip.php?article311 Identified by a 4 numeric number

25. 25 Telematic Applications for Freight Reference File Location 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). –Managed nationally by an allocation entity

26. 26 Telematic Applications for Freight Primary Location Identifier Primary Location –2AN ISO country code –5N LocationPrimaryCode

27. 27 Telematic Applications for Freight 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). It is unique and is always used in combination with a Primary Location.

28. 28 Telematic Applications for Freight Subsidiary Location Identifier Country Code (2AN) LocationPrimaryCode (5N) LocationSubsidiaryType Code (2AN) LocationSubsidiaryCode (10AN) AllocationCompany (4N)

29. 29 Telematic Applications for Freight Location Subsidiary Type Code This element details a Subsidiary Location by its LocationSubsidiary Type Code.

30. 30 Telematic Applications for Freight LocationIdent (XML)

31. 31 Telematic Applications for Freight Realisation of the Common Interface Function Master PlanRequirements Implementation of CI –Installation –Configuration –Ready for Message Exchange End to End Legacy System Configuration

32. 32 Telematic Applications for Freight Realisation of the Train Identifier(s) Master PlanRequirements Train Identifiers –unique ID for all trains over the complete lifecycle of the train Configuration –Includes Pathident, Dossier numbers, path request id, etc –Implementation Guide –Phased approach with pilot

33. 33 Telematic Applications for Freight Realisation of Path Requests Master PlanRequirements The following messages used for Path request must be sent –Path Request RU to IM –Path Details IM to RU –Path Confirmed RU to IM –Path Details Refused RU to IM –PathDossier RU to IM (New Requirement) Implementation Guide Available

34. 34 Telematic Applications for Freight Realisation of Train Preparation Master PlanTrain Ready This message is sent from an RU to IM indicating that the train is ready for access to the network.

35. 35 Telematic Applications for Freight Realisation of Train Preparation Master PlanTrain Composition This message is sent from an RU to an IM defining the composition of the proposed train

36. 36 Telematic Applications for Freight Realisation of Train Running Function Master PlanTrain Running Function Train Running Message Train Running Forecast Message Train Delay Cause Message

37. 37 Telematic Applications for Freight Realisation of Service Disruption Master PlanService Disruption Train Running Interrupted Message –This message is issued by the IM to the neighbouring IM and to the RU that has contracted the path if the train run is interrupted.

38. 38 Telematic Applications for Freight Conclusions/Experience IM’s may indicate that they wish to have their common IM/RU Functions aligned with TAF submission – data and response is on file Please try to provide as much information as possible so that the evaluation team is able to identify any dependencies Have a good uderstanding of the functional requirements Realistically address the effort in your own company Get buy-in on strategic level in your company

39. 39 Telematic Applications for Freight COMMON COMPONENTS

40. 40 Telematic Applications for Freight What are the Common Components? Central Repository Domain (CRD) –Reference Files (Locations, Companies) –Certificate Authority –Common Metadata Common Interface (CI)

41. 41 Telematic Applications for Freight Regulation 62 / 2006 4.2.14.6 Central repository –The central repository must be able to handle: –metadata — structured data describing the content of messages, –Public Key Infrastructure (PKI), –Certification Authority (CA),

42. 42 Telematic Applications for Freight Regulation 62 / 2006 4.2.14.7. 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.

43. 43 Telematic Applications for Freight ISR CI PCSTIS CI IP Network Reference files Location ID Company ID Common Meta Data C.A. PKI IM 1 CI IM 2 CI IM 3 CI RU CI RU CI RURU RURU RURU HMI CI IM = Infrastructure Manager RU = Railway Undertaking HMI = Human Machine Interface RU CI RU CI Orfeus Wagon Ref. Files Architecture Supporting Peer2Peer

44. 44 Telematic Applications for Freight Common Interface Reference Implementation Time Table systems Production systems Preprocessing Normalization Translation Validation Remote LI Configuration Host Protocol Company ID WS Metadata Private Common Shared Mappings (Reference files) IP Network Message- Compression Signature Encryption Routing Security Transport SOAP (HTTP), JMS, FTP, File SMTP, JMS-MQ, „IP-Socket“ Supported protocols Supported formats XML, Text, CSV, UIC Leaflet 407-1 Connectors WS FTP WS WMQ WS … Specific Connector- Configuration Common Interface (Software) MySQL Java EE, CI Application components, Java PKI APIs Jboss Application Server, Jboss ESB, Struts2 …… SOAP (Https) xml (UTF8)

45. 45 Telematic Applications for Freight What You Can Expect Multiple Instances, if desired Installation Support Documentation and User Manuals Service Desk –On-line Ticket Support –Telephone Support – Working Hours –Hot-line Support – 24hour incident management

46. 46 Telematic Applications for Freight Reference Implementation Hardware to be provided by Companies Win OS, Linux RedHat Enterprise LI Installation is automated using Install Jammer and bundled as executable. Separate installable for Windows and Linux platforms. It include following software : MySQL 5.x Java 1.6.14 JBoss AS 6 with ESB CI application components All Administration screens are running in a Web browser Language of all documentation and user guide is English

47. 47 Telematic Applications for Freight Common Interface Function Common Interface Reference implementation delivered 2 nd January 2012 When will your company (As established in the Master Plan?) –Be able to install the Common Interface? Common Components Group just define the registration rules to use the Reference Implmentation –….. in a way which is satisfactory both for above stakeholders and for the “new comers” in particular with view to fair cost sharing. –Be able to connect it to the TAF-TSI Legacy Systems? –Start communications with other TAF-TSI Stakeholders using the TAF formats?

48. 48 Telematic Applications for Freight QUESTIONS AND ANSWERS