1 / 48

TAF.TSI Master Plan Workshop - Timelines, Consolidated Plan, and Governance

This workshop agenda covers the timelines, consolidated plan, and governance structure of the TAF.TSI Master Plan in Brussels. It also includes discussions on the roles and responsibilities of expert working groups, change management requirements, and the TAF.TSI functions explained.

francesr
Download Presentation

TAF.TSI Master Plan Workshop - Timelines, Consolidated Plan, and Governance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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. Master Plan Timelines Consolidated Master Plan Timeline Master Plan

  4. Master Plan Responses Infrastructure ManagersTrack-Kms Railway UndertakingsTonne-Kms

  5. 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.aspx • Database was updated and new Queries were developed • Complete Corridor analysis has been prepared

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

  7. Master Plan Results

  8. Master Plan Target Implementation Dates

  9. 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. The TAF TSI Functions Explained

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

  12. Implementation Guidelines • CRD • Train Monitoring • Train Preparation • Short Termpathrequest • Wagon Order • Wagon Movement • Reference files (not in CRD) • RSRD • Train IDent • The Implementation Guidelines are available on the UIC site : • > eBusiness > TAF TSI > TAF Deployment • http://www.uic.org/spip.php?article447

  13. Source Documents

  14. Source Documents - Metadata • Catalogue Version 5-2 willbepublished by ERA 4Q 2012 as draft version • To besubmitted to RISC for final approval • DT WorkingDraft 5.2.1 shallbeused for implementation and willbepublished on the ERA website as ‘Developer Version’ • Impacted issues • Timetable and PathRequest messages (WG5 – Joint Planning) • Train composition (WG 3 – Joint Operations) • DT willprovide ‘self-contained’ schemas by Message alsoso to bepublished by ERA

  15. Governance Structure

  16. Governance Evolution - Proposed

  17. 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. 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. 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. 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. 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. Realisation of the Reference File Function Master Plan Requirements Location Ident CompanyIdent (Country Code)

  23. Reference File Country • Identified by the Country Code ISO 3166-1 alpha-2 • optional attribute • UIC Country Code (leaflet 920-14)

  24. 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. 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. Primary Location Identifier • Primary Location • 2AN ISO country code • 5N LocationPrimaryCode

  27. 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. Subsidiary Location Identifier • Country Code (2AN) • LocationPrimaryCode (5N) • LocationSubsidiaryType Code (2AN) • LocationSubsidiaryCode (10AN) • AllocationCompany (4N)

  29. Location Subsidiary Type Code • This element details a Subsidiary Location by its LocationSubsidiary Type Code.

  30. LocationIdent (XML)

  31. Realisation of the Common Interface Function Master Plan Requirements Implementation of CI Installation Configuration Ready for Message Exchange End to End Legacy System Configuration

  32. Realisation of the Train Identifier(s) Master Plan Requirements Train Identifiers unique ID for all trains over the completelifecycle of the train Configuration IncludesPathident, Dossier numbers, pathrequest id, etc Implementation Guide Phasedapproachwith pilot

  33. Realisation of Path Requests Master Plan Requirements 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. Realisation of Train Preparation Master Plan Train Ready This message is sent from an RU to IM indicating that the train is ready for access to the network.

  35. Realisation of Train Preparation Master Plan Train Composition This message is sent from an RU to an IM defining the composition of the proposed train

  36. Realisation of Train Running Function Master Plan Train Running Function Train Running Message Train Running Forecast Message Train Delay Cause Message

  37. Realisation of Service Disruption Master Plan Service Disruption Train Running Interrupted Message This message isissued by the IM to the neighbouring IM and to the RU that has contracted the path if the train runisinterrupted.

  38. Conclusions/Experience IM’smayindicatethattheywish to have theircommon IM/RU Functionsalignedwith TAF submission – data and responseis on file Pleasetry to provide as much information as possible sothat the evaluation team is able to identifyanydependencies Have a good uderstanding of the functionalrequirements Realisticallyaddress the effort in yourowncompany Getbuy-in on strategiclevel in yourcompany

  39. Common Components

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

  41. 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. 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. Architecture Supporting Peer2Peer RU CI CI CI CI CI CI CI RU RU RU IM 2 IM 3 IM 1 • Reference files • Location ID • Company ID • Common Meta Data • C.A. PKI PCS TIS HMI ISR Orfeus CI CI CI IP Network Wagon Ref. Files CI Wagon Ref. Files CI CI IM = Infrastructure Manager RU = Railway Undertaking HMI = Human Machine Interface RU RU RU

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

  45. 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. 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. Common Interface Function Common Interface Referenceimplementationdelivered 2ndJanuary 2012 Whenwillyourcompany (As established in the Master Plan?) Be able to install the Common Interface? Common Components Group justdefine the registration rules to use the ReferenceImplmentation ….. 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 connectit to the TAF-TSI Legacy Systems? Start communications withother TAF-TSI Stakeholdersusing the TAF formats?

  48. Questions and Answers

More Related