1. PCS Technical Board
1st June 2017, Vienna

2. Agenda

3. Agenda Major Release 2017 interface impact PaP Product definition
Common mandatory train parameters
Loco types
TAF-TSI related changes
Path Alteration/Path Modification status. What is the current? What should be the future?
How to work with PaPs? Fields and processes. Life with or without combined PaP/Tailor-made. What will happen with Empty Envelope Concept?
RFC Short term path request pilots. Status of RFC5 pilot, capacity handling on RFC3 and RFC7.
Documentation. What are we missing?
Testing procedures. How to prepare for a PCS test with several involved parties including RNE?
Any other business
12 January 2019

4. Major 2017

5. Major 2017 Pre-Booking phase and C-OSS TT
When? Pre-Booking phase should be inserted to the path request workflow. When an RU submits a path request (NPR, LPR or AHPR) with a dossier that has at least one PaP. When path request issued, PCS should copy the RU TT content to C-OSS TT regardless if there was Feasibility Study Result. Later when C-OSS releases Path Elaboration PCS should copy content from C-OSS TT to IM TT regardless, if there was Feasibility Study Result.
ACL in Pre-Booking:
RU can see the RU timetable only
IM can see the C-OSS timetable only
C-OSS can edit the C-OSS timetable
C-OSS can reserve the PaPs as today in the same views (PaP request details, CST)
C-OSS should be able to edit the timetable and train parameters in the dossier details view (NEW)
C-OSS should be able to remove and insert PaPs in the C-OSS timetable same as today with the alternative offer. Reference point and calendar handling should be same as the IM TT. (NEW)
Removing/editing of a PaP should be possible only, if that is not reserved
Alternative offer should be supported as today (but subsidiaries too ← EEC)
C-OSS should have the possibility to send the dossier for review and confirmation to the Rus. All RFC lights should be green. When RU accepts/refuses the dossier, RFC lights should go back to blue.
If RU accepts the alternative offer, then C-OSS can release Path Elaboration.
If alternative offer refused, C-OSS should have the possibility to send new alternative offer, but release path elaboration is possible only with accepted alternative offer (or of course normally with all the green C-OSS lights when there was no alternative offer)
12 January 2019

6. Major 2017 C-OSS TT what else?
For comparsion C-OSS TT should be possible to select
TT comparison
TT combination comparison
Reports, PDF export (?) currently we have request and offer sheet, we should add pre- booking sheet with the content of the C-OSS timetable. This part we have to check later. I would say we don't change anything right now.
PCS IP schema should be also adopted and documented (first!)
Feasibility Study:
RU should not be able to go to Feasibility Study with pure PaP dossier
In Feasibility Study PCS should create only IM timetable
12 January 2019

7. Major 2017 Leaving Pre-Booking phase
C-OSS acceptance indicators are green. The acceptance indicators should belong clearly to the RFC and not anymore to the "on behalf IM". RFC can change the lights manually. If the C-OSS reserves all PaPs or request tailor-made for the whole dossier, PCS can change their lights to green automatically, but the phase promotion is relying on the C-OSS.
Searches should also consider this fact, e.g. when IM search for his lights via advanced search, the C-OSS lights should be ignored in the search. If IM has business (ToDo) in the dossier, it will get anyhow an own light. Setting green light as C-OSS should consider the usual rules:
All mandatory times and parameters are entered
All PaP section is either reserved or marked as tailor-made
In case of alternative offer the RU accepted the modifications
RFC promotes the dossier manually or bulk to Path Elaboration.  Even if they request full tailor- made, the system should keep the dossier in Pre-Booking, the C-OSS will deal with the phase promotion.
After releasing the dossier to path elaboration the C-OSS acceptance indicator should go back to blue.
In case of multi-corridor request the dossier can be released to path elaboration only if all the C- OSS lights are green (no partial offer). Promotion should be supported with an automatic PCS promotion in the morning and in the night of X-7.5.
12 January 2019

8. Major 2017 Editing PaP calendar in Path Elaboration
„If IMs are forced to reconsider PaPs due to TCRs the principle of “guaranteed capacity” is to be kept. Therefore, all requests based on pre-booked PaPs have to receive an offer. The C- OSS has to be informed about reduced operation days of PaPs.”
IMs will be able to edit the reserved PaP capacity calendar
If IM changes the reserved PaP capacity (only reduce is possible), he must send alternative offer for those days
Idea/Proposal of RNE to be discussed with the RFCs
Close Combined PaP/Tailor-made solution for TT2019
Why?
Too complex either technically or from the end user point of view
FCA opened the possibility:
LPAP = Total requested length of all PaP sections on all involved RFCs included in one request. Not anymore dossier
RU can create more dossiers for one request (one traffic please don’t mix TAF-TSI terms) and link them
12 January 2019

9. Major 2017 Common mandatory parameters
Administration area for IMs to maintain all the train parameters (not IM specific only)
Possible to change from optional to mandatory (other way around is not allowed)
RU must fulfill the parameters according to this definition
Single Border Point Approach: On border crossing areas, if the participating Ims define different mandatory status, the following rule should be applied
Edit Planned Speed parameter
In case of PaP dossier the planned speed parameter can be edited only by the IM
IM1
IM2
(=or)
optional 1
mandatory
12 January 2019

10. Major 2017 Loco types IM should publish locos in PCS
If not a single loco is published, RU can request without traction details ← RNE Support
UNKNOWN_LOCO_TYPE_NUMBER(278)
Copy of locos only inside the IM (same as the IM parameters)
Legacy values:
Old free text values are still visible in the dossier in read only
User can remove the old value and add new loco type (if the IM defined)
Speed constraints:
Loco type max speed must be equal or higher than the train max speed
Train max speed must be equal or higher than the planned speed
Loco type max speed must be equal or higher than the planned speed
PaP publication:
Reference locos should be compliant to the published locos
12 January 2019

11. TAF-TSI changes

12. Identification
Object type: A two character element indicating the type of object this ID is for.
TR for Train
PA for Path
PR for Path Request
CR for Case Reference
Company: A four character element is indicating the company who created the object (RICS Code)
Example:
Core element: the main part of the ID. It is free format and determined by the company that creates it. It can use any digit from 0 to 9 and any upper case character from A to Z. It is fixed width 12 characters. If it is less than 12 characters long it must be left justified by padding out the remaining space with a horizontal dash “-”.
Variant: The variant field is a fixed length of 2 characters.
Timetable period: In order to allow the core element to be reused for different timetable periods the year is included to indicate which year it applies to.
Start-Date (used only in operation): The start-date is the day of planned departure from the origin station of the object. The field is only present in the daily object.
12 January 2019

13. Transition and Integration layer between PCS and CI
12 January 2019

14. PCS related changes
Release notes:
Dedicated test environment for the pilot:
Operation points from CRD
IM Parameters from PCS Production TT2018
PCS Core application with TAF-TSI changes
Process related changes
 The following actions will be possible for the leading RU from Draft Offer phase:
directly submit Active Timetable, the transition Post-processing will be skipped which is the behavior today
do Withdraw, an option that is not supported today, that will effectively bring the dossier back to Harmonization phase. The IM timetable will be lost and the last version of the dossier in Harmonization will be revived
do 'Return to Path Elaboration' which will change the phase to Path Elaboration and give appropriate dossier permissions (read for RU's, write for IM's). The last dossier version in Path Elaboration will be revived. Pap requests status changes in some cases will be necessary from drafted to reserved, tailor-made will stay tailor-made.
New process type: ad-hoc with pre-accepted offer (type of information – 19). This means that once Draft Offer is submitted by the leading IM the dossier will immediately transition to Active timetable phase.
12 January 2019

15. PCS related changes Train ID:
This identifier should be stored on the dossier level in the Basic Data (under the international train number field). 
It should be possible to define it during the dossier creation wizard in the 1st step and later it should be visible in the Basic Data.
As the modification of the train id is not supported in later phases, the Leading RU can modify it only in Open phase. After releasing the dossier to Harmonization the field should be blocked.
Path request ID/Path ID:
TsiPathID element is added to PCS
Available only in web-services and defined as optional element
Path Request ID meaning RU timetable (modification until the end of Harmonization)
Path ID meaning IM timetable (modification undil the end of Ad-Hoc request Offer)
Traction mode new value:
„No leading Engine” is added to the list
12 January 2019

16. PCS related changes TrainCC system code table update →
Route Class code list:
Free text field was replaced with the following list:
A, B, C, D, E, F, G, C2, C4, CM2, CM3, CM4, CM,
CE, D2, D4, A2, A4, B1, B2, C3, D3, E4, E5
Brake type: „X” was added to the list
Spelling mistakes had been fixed for „Braking” (instead of „Breaking”)
Dangerous goods indication - new fields
Danger Label: It should be added to the dangerous goods area. Free text.
Dangerous Goods Volume: It should be added to the dangerous goods area. Values are expected in cubic meters.
Limited Quantiy Indicator: New check box in the dangerous goods area.
ETCS Level 0
EBICAB 700
NEXTEO
ASFA
ETCS Level NSC LS
DAAT
EBICAB 900
ETCS Level 1
ZUB 123
EVM
SELCAB
ETCS Level 2
ALSN
CAWS
SIGNUM
ETCS Level 3
ATP-VR/RHK
ATP
ZUB
PZB
KVB
BACC
ATB 1st Gen
LZB
TVM 300
RSDD/SCMT
ATB Next Gen
Crocodile
TVM 430
SSC
GW ATP
TBL 1
KVBP
MEMOR II+
RETB
TBL 2
KCVP
SHP
TPWS
TVM 430TBL1+
KCVB
PKP
12 January 2019

17. PA/PM

18. How to work with PaPs?

19. How to work with PaPs? PaPs catalogue IDs:
M(andatory), O(ptional), N(ot used)
* Fix PaP – create slave / Flex PaP – create slave – in case of creation of subsidiary in dossier with PaPs, for the path sections of the subsidiary that you want to create, none of those fields should be entered (general Ids will be generated by PCS; catalogue fields should not be entered, because you cannot create subsidiary with PaPs)
No PaP
Fix PaP – replace Master
Fix PaP – create slave
Flex PaP –replace Master
Flex PaP –
create slave
Flex PaP – border point
general ID’s (pathID, pathSectionID,…) M
corridor_catalogue_id N
corridor_id O
catalogue_selector_agency_id
originCorridorCatalogueId
catalogueTeId
catalogue_path_number
12 January 2019

20. Managed by PCS IM Timetable
Fix PaP
Flex PaP
Pap TT
SNAD
location
remove: NO
Yes (except location with )
Yes (except location with )
add /remove (feeder/outflow)
Yes
yes
(except location with )
insert intermediate location between 2 adjacent PaP sections
Yes (except between two locked point as far as I remember)
Insert intermediate location in a PaP section
Train no
Path no
Catalogue path nr
Not available
Arr/dep times
Yes (except locked points)
Edit activity type of location part of PaP
Edit location type of location part of PaP
Edit calendar
No: you cannot edit the calendar of the PaP, but you can edit the calendar of the intermediate point as that’s handled as f/o. Example: vpe-09: Check DABAS in the first sub.
YES
12 January 2019

21. RFC Short term path request pilots

22. ScanMed pilot details Start of the pilot planned for November 2017
Expected duration 6 months
Empty PaPs, not guaranteed capacity
Feeder/Outflow paths only allowed on networks with participating IMs
Spot traffic only for single train runs
Application deadline: no deadlines, but not less than 5 working days before train run (if RFI is involved)
No committed deadline for submission of the offer
Pre-accepted offer (will be included in the PCS TAF-TSI developments in Major Release November 2017) is supported
Partial offer is possible (up to the customers decision, submission only if the border time is confirmed)
12 January 2019

23. Baltic-Adriatic pilot details
Starts in May
Planned for 6 month (extension is possible)
Nothing will be published in PCS, tailor-made dossiers are in scope
Feeder/Outflow paths only allowed on networks with participating IMs
No limitation in the requested running days
Application deadline is 8 working days
C-OSS is not directly involved, only reporting function
Deadline for submission of the offer is 5 working days before the train run
Pre-accepted offer (will be included in the PCS TAF-TSI developments in Major Release November 2017) is supported (for some IMs where national parameter exists, even earlier than November 2017)
Partial offer is not supported
12 January 2019

24. Orient/East-Med pilot details
Operational departments would not be involved into the procedure (they have no access to PCS) only the timetable departments (automatic TT-construction is optional)
The pilot product would apply for all international freight trains crossing at least one border on the corridor line including feeder and outflow
Multi-corridor requests, or feeder/outflow from non-RNE countries or outside RFC 7 shall not be allowed
Pilot duration: 6 months
The publication of the pilot product will start after the main PCS release (mid-end of November 2017) and will concern only TT2018 (type of PaP in PCS (empty or catalogue with times) per border crossing)
Two-week update frequency in case of catalogues (reminders to be sent by C-OSS Manager)
Matrix for deadlines, taking into consideration the timetable periods and national holidays
No limitation in terms of running days, but timetable periods should be respected
Pre-accepted offer (will be included in the PCS TAF-TSI developments in Major Release November 2017) is supported
No partial offer (based on our current rules)
Due to the fact that the pilot only concerns TT 2018, DB Netz will not participate
12 January 2019

25. Documentation

26. Documentation What do you miss? Which area, topic?
Could you prepare a template that you would like from us to fulfill?
Prepare your own documentation. Show us how you do! We can post it in CMS
12 January 2019

27. Testing procedures

28. Testing procedures Internal test procedure is up to you
PCS test procedure is interesting for us too. Couple simple questions can help a lot in the preparation:
Which features would you like test?
Which system would you like to use?
We can check the tested functionality before your test
Which process type do you need, what kind of calendar settings?
Maybe we need to change the configuration
Are operation points, IM parameters, locos, PaPs in place?
We can adjust master data in the system if you want, just indicate it in advance
Which agencies would you like to use?
We can check, if RICS code are in place, credentials are properly set up
In which period will you have your test session?
We can have a special attention on your tickets and question in that period
12 January 2019

29. CRs

30. Any other business