1 / 12

TAF/TAP Joint Sector Pilot for TAF/TAP TSI Short Term Path Request and Train ID

Recap of the latest JS Pilot Meeting focusing on technical requirements for testing, updates on program plans, impact assessment, and partner testing status. Learn about CI-CI communication and what to expect in the short and long term.

schen
Download Presentation

TAF/TAP Joint Sector Pilot for TAF/TAP TSI Short Term Path Request and Train ID

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/TAP Joint Sector Pilot for TAF/TAP TSI Short Term Path Request and Train ID Seid Maglajlic JS Pilot and TEG Meeting, Vienna, 12/02/2019

  2. Topics • Current status of testing with partners • Update of the program plan • Impact assessment • Technical pre-conditions for testing - revisited • The inclusion of TIS in the pilot program. Introduction of the daily object in the pilot. JS Pilot: Topics for today JS Pilot Meeting, 12.12.2018

  3. JS Pilot: Topics for today • Status of testing with partners • RCA/RCG – ÖBB: Discussion with ÖBB-Infra ongoing • SBB Infra • CI-CI communication established. • System development was scheduled for Q1/Q2-2019 • Trafikverket • Problems with CI-CI heartbeat outage solved with the new version of CI • RNE Test Environment upgraded to CI 2.0 JS Pilot Meeting, 12.12.2018

  4. JS Pilot: Topics for today • Status of testing with partners • Prorail • CI-CI communication established with problems. • Firewall and proxy settings were an issue. Functional part is about to start • Infrabel • together with Prorail - currently in preparation • SZDC • system-to-system planned for 2019 • Changes in RNE Test Environment will be done by end of February 2019 JS Pilot Meeting, 12.12.2018

  5. JS Pilot: Topics for today • JS Pilot plan update – short term • Upgrade of RNE Test Environment • CI 2.0 upgrade - done • XSD 2.2.3 until end of February • Messaging with PCS as a broker until end of February • FTE test cases • Inclusion of PathDetailsMessage exchange with TIS (Operations) JS Pilot Meeting, 12.12.2018

  6. JS Pilot: Topics for today • JS Pilot plan update – short term JS Pilot Meeting, 12.12.2018

  7. JS Pilot: Topics for today • Long term plan JS Pilot Meeting, 12.12.2018

  8. Impact assessment survey • External document – will be prepared as survey JS Pilot: Topics for today JS Pilot Meeting, 12.12.2018

  9. Technical pre-conditions – revisited (1) • CI-CI communication • Your CI machine: • Ensure that your team has an access • Ensure you can “ping” and “traceroute” the RNE CI machine 195.110.209.104 (taftest1.railneteurope.info) • All RNE CIs have a valid security certificate • Ignore the certificate warning • It comes due to the CA-authority RNE, which is not recognized by browsers. Don’t worry, the certificate is valid. JS Pilot: Topics for today JS Pilot Meeting, 12.12.2018

  10. Technical pre-conditions – revisited (2) • CI-CI communication • Provide us with your IP address • Of your CI machine • OR – if you are using proxy, then incoming and outgoing proxy IP! • We will report you the “traceroute” results • Only when both “traceroutes” work, the CI-CI Heartbeat can be established • Only when CI-CI Heartbeat is successfully tested, the messages can flow JS Pilot: Topics for today JS Pilot Meeting, 12.12.2018

  11. Technical pre-conditions – revisited (3) • System-CI-CI-PCS communication • XSD Schema 2.1.7 currently • CI routes (company codes): • RU-IM / IM-RU • To be 2.2.3 by end of February • CI routes (company codes): • RU-PCS / PCS-RU • IM-PCS / PCS-IM • RU-IM / IM-RU JS Pilot: Topics for today JS Pilot Meeting, 12.12.2018

  12. JS Pilot: Topics for today • Inclusion of TIS • Path Details Message from PCS will feed TIS with timetable data (CTT) • PCS TIL will produce Path Details Message for each day in calendar of the path • Dossier must be in “active timetable” in PCS • PCS TIL will send the Path Details Messages on behalf of IM • It will be PCS-CI-CI-TIS connection JS Pilot Meeting, 10.10.2018

More Related