1 / 36

Retrospective report of the past year

Retrospective report of the past year. PCS-TTR Day 2018, Vienna. Customer satisfaction survey and stats. General Survey Workflow. General Survey Timeline. TIS Survey. Results Preparation and Analysis. Results Review General Assembly. Presentation General Assembly. CIS Survey.

bauder
Download Presentation

Retrospective report of the past year

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. Retrospectivereport of thepastyear PCS-TTR Day 2018, Vienna

  2. Customersatisfactionsurvey and stats

  3. General Survey Workflow

  4. General Survey Timeline TIS Survey Results Preparation and Analysis Results Review General Assembly Presentation General Assembly CIS Survey CIP Survey ReportingSurvey PCS Survey

  5. PCS Survey: Number of participants: 61

  6. Importance of PCS for your business

  7. PCS Usage

  8. Performance, usability, usefulness, support

  9. Performance, usability, usefulness, support (Average results)

  10. Frozen zone Showing the purpose, the story and the future of this action

  11. Frozen zone is a step in the timetable process when an actor is not allowed to make an update on the dossier. This year, IMs were allowed to update their offer in Observations. „

  12. 164 dossiers 6% of the dossiers were touched by IMs during Observations

  13. Where was it used? Although it was only 6% of the dossiers, the opportunity was widely used.

  14. Game over It was available only for TT2019

  15. GDPR in PCS: New users

  16. New users in PCS

  17. OPTIONAL

  18. Dossier closure

  19. Dossier closure Showing the possibilities 03. Post-processing* Leading IM or RFC can close the dossier 04. Final Offer* Leading RU can close the dossier and new automatic promotion with all red lights 02. Observations* Leading RU can close the dossier 05. 01. Active Timetable Leading RU or leading IM can close the dossier, after the timetable is started Open and Harmonization Leading RU can close the dossier

  20. Dwelltime

  21. What is dwell time?

  22. Dwell time format • Dwell time should have a standard format defined in minutes and should be taken into account when validating times.

  23. Dwell time formula In the example, the dwell time (DT) needs to be equal or smaller than 90 minutes DT ≤ Dep – Arr

  24. Missing arrival or departure times

  25. Other considerations • PCS will calculate automatically overnight shifts (offsets) • If a time zone change is implemented, PCS will adjust automatically the calculation • The system won't check the operation point type • In PCS IP error code indicates to the uploader agency if the web-service request contains invalid dwell time. • The error code is: 659 INVALID_DWELL_TIME

  26. Hello TSI world! <html> <header><title>This is title</title></header> <body> Hello TSI world! </body> </html>

  27. Instructions for the presentation PCS CI: Common Interface endpoint of PCS (for the TSI communication) PCS IP: Integration Platform endpoint of PCS (for the usual PCS web-service communication) TTM: TAF-TSI Test Manager that simulates pre-defined actions and triggers messages to PCS TIL: Transition and Integration Layer that maps the TSI message content to PCS web-services SOAP UI: the most popular platform for Application Programming Interface functional tests. Substituting your real application

  28. Communication Options PCS IP TIL PCS CI TTM PCS IP TIL PCS CI SOAP PCS IP TIL PCS CI RU/IM national tool PCS IP SOAP PCS IP RU/IM national tool

  29. Messages „…Path Coordination, Path Request, Path Details, Path Not Available, Path Details Confirmed, Path Details Refused, Path Booked, Receipt Confirmation, Error message…” Path Coordination For harmonization purposes. RU-RU or IM-IM communication Receipt confirmation Thank you! I got your message, I could import it in my system and I started to process your request. Path Not Available Something went wrong, the path is no longer available. We will inform you about the possible alternative options And the attributes… Message status, type of information, type of request, code lists, etc.

  30. Scope of the pilot(runs until 2020 Q2) 01 02 Path Request process Path modification, alteration, cancellation process Identification Train number candidates Path request and offer procedure among the RUs and IMs, including also the harmonization of the requests and the offers Updating the contracts after the allocation either from the RU or from the IM side. Reviewing the process and message workflow Checking all the TSI identifiers, like Train ID, Path Request ID, Path ID and Case Reference ID, if they are suitable for their task Testing FTE’s candidates for the planning and commercial train numbers 03 04

  31. Presentation

More Related