1. PCS Technical Board
17th October 2017, Vienna

2. Agenda

3. Agenda
Release plan till the end of 2019 including Major Release 2017 (~1 h)
New change request workflow (~10 m)
C-OSS guideline implementation (~1,5 h)
Empty Envelope Concept status update (~0,5 h)
PCS IT Day (~0,5 h)
TAF-TSI Pilot results update (~10 m)
Communication plan (~0,5 h)
27 November 2018

4. Release Plan, timeline

5. PCS Core Group 6th November (mockups, wireframes)
Until 1th November 2017 Exception to N day rule PA/PM operations New notification messages Enable loco types for C-OSS Unify branches (Major Release, IP cons., Monitoring app)
Until January 2018
PCS Core Group 6th November (mockups, wireframes)
Interviews – 13th November
Deletion of saved drafts CNDW
Filters, labels
Trivial CRs (1130, 1220, 1141, 1229)
EEC requirements locked – end of the year 2017
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
Test 16th March
Prod 4th April
Test
Prod
EEC workshop 5th February 2018
Editing of C-OSS TT
Alternative offer in Pre-booking phase
PAMT report for RU/IM
Withdraw dossier – process issue
Open EEC branch
EEC techn.specs. (including IP) – latest 27th February
Minor 2018
EEC
Single Border Point administration
New PaP product
Major 2018
Non-RU applicant
Single Border Point usage in dossiers
Validity period of master data (locos, parameters, agencies)
Major 2019
27 November 2018

6. Details of „Until 1th November”
Exception of N day rule
Possibility for C-OSS to import PaPs inside the „N day rule” window
Support Short Term Path Request pilots with PaPs
PA/PM operations
New notification messages
Only in Late and Ad-Hoc path request process
RFC, IM, AB receives when new path request arrived
RU receives when Harmonization started, offer (draft, ad-hoc, final) arrived
Enable loco types for C-OSS
Provide the same read-only view to C-OSS as for the RUs
27 November 2018

7. Details of „Until January 2018”
Deletion of saved drafts in CNDW
Filters, labels
Trivial change requests
Rename of field „days in service on this path“ (1130)
Improved editing of the TT when add a location (1220)
No partial harmonization with non-PCS agency (1141)
Advanced Search criteria reset, hidden fields (1229)
27 November 2018

8. Details of „Minor 2018” C-OSS TT rest of the work: Editing of C-OSS TT
Alternative offer in Pre-booking phase
PAMT report for RUs/IMs
„Withdraw & close” dossier – process issue
Leading RU regardless of the colour of the ligths
From Observations, Post-Processing, Final Offer to Closed phase
Automatic promotion until X-3: dossier from Final Offer to Closed, if all lights are red
Irreversible action!!!
27 November 2018

9. Details of „Major 2018”
Empty Envelope Concept – details on following slides
Single Border Point Approach administration
Similar approach as with the Loco Types
Development of the administration area
Preparation of the data in PCS Test and after Major 2018 in PCS Production by the IMs
Possible warning mechanism already in EEC
New PaP product – details on following slides
27 November 2018

10. PCS Core Group 6th November (mockups, wireframes)
Until 1th November 2017 Exception to N day rule PA/PM operations New notification messages Enable loco types for C-OSS Unify branches (Major Release, IP cons., Monitoring app)
Until January 2018
PCS Core Group 6th November (mockups, wireframes)
Interviews – 13th November
Deletion of saved drafts CNDW
Filters, labels
Trivial CRs (1130, 1220, 1141, 1229)
EEC requirements locked – end of the year 2017
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
Test 16th March
Prod 4th April
Test
Prod
EEC workshop 5th February 2018
Editing of C-OSS TT
Alternative offer in Pre-booking phase
PAMT report for RU/IM
Withdraw dossier – process issue
Open EEC branch
EEC techn.specs. (including IP) – latest 27th February
Minor 2018
EEC
Single Border Point administration
New PaP product
Major 2018
Non-RU applicant
Single Border Point usage in dossiers
Validity period of master data (locos, parameters, agencies)
Major 2019
27 November 2018

11. New change request workflow

12. New elements in the workflow
Maintenance issue
Waiting for requirement
Requirement analysis
Waiting for specification
Under specification
Specified
Process issue, waiting for agreement
Proposed to reject
Change Request
Development state
Complexity
Small, Medium, Big, Huge
Responsibility
PCS Team, S & TT, NCA, Users, …
27 November 2018

13. C-OSS guideline implementation

14. Timeline Pre-booking phase RFC traffic light separation from IM light
TT2019
Pre-booking phase
RFC traffic light separation from IM light
C-OSS timetable (read-only)
C-OSS timetable (editable)
PaP publication of reference PaP with slots
Threshold/warning instead of error in parameter set codes
Adjusting conflict resolution
Provide full update possibility for IMs in Path Elaboration
Publication of updated import sheet
New classification of operation point protection
Implementation of the bandwidth
Major Release 2017 ✓
Minor Release 2018 ⌛
Major Release 2018
Minor Release 2019
June 2019 latest
Major Release 2019
TT2020
TT2021
27 November 2018

15. For TT2019 Pre-booking phase:
When RU submits path request with a PaP in the dossier
Dossier status id: PB
IM has read-only rights
C-OSS has editing rights
Separated traffic lights: easier search
C-OSS TT:
C-OSS has editing rights on the PaPs and the additional intermediate sections
Times
Parameters
Calendar cannot be changed, the capacity is reserved
Special cases when C-OSS timetable update would result offset on the IM’s part
Copy to IM TT while C-OSS promotes the dossier from Pre-booking to Path Elaboration
27 November 2018

16. For TT2020 First step of the implementation of the new PaP product
Slot approach development
No changes in the import
Adjustment of PaP Manager for C-OSS to mark the number of slots
Changes in the conflict resolution
Bandwidth definition only on organizational level
Soft cap for the parameter set code limits
Option 1: RU/RFC can exceed the defined values and gets warning instead of the current error
Option 2: threshold definition for each parameters in the set code, exceeding is not allowed. E.g. 50 meters threshold in the train length, 100 tons threshold in the weight of set of carriages, etc.
Development to give freedom to IMs in Path Elaboration (time, parameter, calendar update)
27 November 2018

17. For 2021 Second step of the implementation of the new PaP product
New classification of operation point protection
Currently: protected/flexible
Bandwidth definition:
RFC/IM can define bandwidth for each operation point (± timeframe)
RU/RFC has to consider the defined bandwidth
In the starting phase (e.g. first timetable period) it would be still soft cap for the IMs
PaP import sheet needs to be updated
New protection option
Bandwidth definition
27 November 2018

18. Questions
How do you plan to mark the published PaPs in your national system?
How do you plan to safeguard the published bandwidth surrounding the reference PaP?
Please note that the update of the capacity would be supported and not the erase/create from zero approach!
Are you able to handle this in the national system before TTR implementation?
27 November 2018

19. Empty Envelope Concept Status

20. Scope of the project
What is in the scope of the project? What would we like to do?
Creation of standard dossier structure
Border harmonization
Calendar consistency
What is out of scope of the project?
Change of the process in PCS
Why do we need this?
Establish the possibility of quality control and monitoring of timetables
Create readable dossiers
Check timetable quality task force measures
27 November 2018

21. Core Team Workshop September 20-21
Ground rules were:
Less discussion, more „together individually” work
Roles:
Facilitators: Jana Karcheska (NCA), Jorge Campo (RNE)
Decider: Matthias Lück (DB-F), Máté Bak (RNE)
Steps of the sprint method:
Map
Sketch
Decision
Prototype
Test
Interview during prototype testing with Peter Bouman (NSI) and Julia Weiss (DB Cargo)
Questionnaire about EEC and current PCS usage among the participants
27 November 2018

22. Core Team Workshop September 20-21
Result of the hitmap showed the focus points
Timetable presentation
Notification in case of modification: questions were raised in two dimensions:
Calendar changes
Geography changes (borders)
Propagation of changes among the timetables
Participants were invited to prepare sketches for the above mentioned points
Sketches:
Voting on sketches and explanations
Result:
None of them was 100% perfect, but each of them had at least 1 useful detail
We should combine the ideas and adopt them to the prototype and to the wireframes
Best workshop ever in EEC history
27 November 2018

23. RU and IM positions Opposite sides in the meeting room  IMs:
Handover – Handover subpath
Border harmonization
Calendar consistency
RUs:
View of the full timetable in each combination (train)
Possibility to edit these combination
Possibility to give name and order to the combinations
Win – win:
Timetable combination views have generated names based on the RU entries in the subpath title
Quick link from combination view to the particular subpath for editing (showing neighbouring timetables)
PCS stores the information in subpath according the IM’s demands
27 November 2018

24. Next steps Process and prepare the feedback from the last workshop
Adopt the prototype, create new wireframes
Deadline: 6th November, Core Group video conference
Quick Core Group feedback about the changes
Deadline: 10th November
Reason for short time: feedback can arrive even a bit later, but if changes should be done before PCS day presentation, we need the information as soon as possible
Interviews:
13th November: interview again (!) with Core Group members. Result of the former prototype test could be compared to the updated
Rest of 46th week: interview with the members of the extended group
Next personal meeting: 5th February
27 November 2018

25. PCS IT Day

26. PCS IT Day PCS IT Day won’t be a PCS Technical Board meeting
The purpose is to share knowledge
From us to you
From you to us
Among you
Topics from the PCS Team (RNE & NCA) to you:
General information about handling:
Loco types, TAF/TSI fields, PaP identifiers, complementary calendar
Path Alteration/Path Modification
How to go through the process?
How to use new the operations?
IP Consolidation package:
Automated test
27 November 2018

27. PCS IT Day What kind of agenda would you like?
Topics from us are known
Questions received from the registered participants
Topics from you…
Infrabel would like to present…
SNCF Reseau would love to talk about…
SZDC insists to share that…
ÖBB has an idea about…
Don’t think about big global presentation! Pick only one small segment, e.g. operation point update, using change sets from notification service, etc.
27 November 2018

28. TAF-TSI Pilot results

29. Just as a reminder: Transition and Integration layer between PCS and CI
27 November 2018

30. TAF-TSI Pilot Test Manager https://til.rne.eu/taf-testmanager/
(attached)
(attached)
Inbound communication:
RU/IM sends message to RNE CI
Triggers usual PCS web-service operations (updatePath, updateProgressStatus, etc.)
Outbound communication:
PCS agency notification is connected to the TIL. Testing partner RUs now:
SZ-C
RCA
TIL triggers usual TSI messages (PathCoordination, PathDetails, etc.) and sends to the partner CI
27 November 2018

31. Communication plan

32. Changes
Based on the feedback from PCS Change Control Board and other forums…
Login screen:
Supported PCS IP version will be shown on PCS login screen
PCS IP Documentation link will be updated on the login screen and linked to PCS IP Handbook in CMS (Migration guide in the related documentation)
Migration guide:
It’s written there, if the particular version is
Not longer supported
Supported
Will be supported from…
Publication date and update date is indicated for the particular versions
27 November 2018