Pa P Publication strategy TT 2019 Combined Pa

Pa. P Publication strategy TT 2019 – Combined Pa. P RU AG, PCS CCB

Current situation & possible solution

Problems » Pa. P calendars are not stable during the Harmonization and Path Elaboration phase » Publication of calendar is often useless and a week later presents wrong information to the customer » Calendar is changed in the national system » Calendar is blocked in PCS » Combined Pa. P/Tailor-made solution » Aim: cover the not available days with automatically created subsidiary timetables (managed by PCS) » Problems of the feature: » Due to first point above the originally available days are not available anymore » RU cannot edit the managed by PCS timetables » Hard to understand the logic and quite difficult to manage them as a user » IM cannot delete the managed by PCS timetables » IM doesn’t edit the managed by PCS timetables, even if they could do that. They rather create their own national subsidiaries » Unreadable offers: main timetable, managed by PCS subs, IM created national subs, comments, contradictions, overlapping 16 September 2020 3

Solution » Empty Envelope Concept would solve the problem » Multiple Pa. Ps per section is supported » RFC could make pre-allocation or request tailor-made subsidiary per Pa. Ps in each subsidiary » Calendar handling (split & join days) is much easier among subsidiary timetables » Target release date November 2018 → TTP 2020 » Temporary solution is necessary » Without development it cannot be solved, however RNE would like to solve it as optimal as possible » Trying use elements that might be useful long-term too 16 September 2020 4

Solution » Solution that would be ready for TT 2019 publication and usage: » RFCs publish all running days in the Pa. P and mark those that will be likely solved as tailormade* » No need for combined Pa. P/Tailor-made solution as all day marked in the Pa. P calendar. *RFC 7 doesn’t support the idea of the whole calendar publication, but support the second point in order not to block other RFCs » Result » RUs can place request on any of the days » No managed by PCS subsidiary will be created » In case RUs need re-routing, they can make subsidiary timetable same as they do it today » RFCs can pre-allocate or request tailor-made Pa. P by Pa. P » IMs can create national subsidiaries for deviations same as they to it today Please find the an example for better explanation on the following slides 16 September 2020 5

Demonstration of the solution

Publication Request RFC marks all days in Excel template → Pre-Booking Path Elab. Draft Offer 1 2 3 4 5 6 7 X X X X X TM TM Import result in PCS → X X X Flagging RFC flag the TM days in PCS → Pa. P Technically all days are Pa. Ps for PCS. Development is necessary for flagging and visualization. 16 September 2020 7

Request Publication Request Pre-Booking Path Elab. RU selects Pa. Ps: Draft Offer Result in PCS: Pa. P TM TM • Pa. P 2 Pa. P TM • Pa. P 3 Pa. P Pa. P • Pa. P 4 Pa. P TM TM TM • Pa. P 5 Pa. P TM TM TM RU selects running days (1 – 3) 16 September 2020 Main TT (1 -3) Feeder Pa. P Subsidiaries (optionally) Pa. Ps TM Outflow • Pa. P 1 8

Pre-Booking Publication Request Dossier content for RFC: • Feeder Pre-Booking Draft Offer Pre-allocation decision by RFC • Pa. P 1 TM Pa. P Pre-booked • Pa. P 2 Pa. P Pre-booked • Pa. P 3 Pa. P Pre-booked • Pa. P 4 Pa. P TM Request tailor-made • Pa. P 5 Pa. P Request tailor-made • Outflow Path Elab. Development is needed that K value calculation is based on only Pa. P days. TM days should be ignored. PAMT report is also affected. Even though Pa. P days are presented here, we could see in practice that tailor-made request was/could have been issued in some cases 16 September 2020 9

Path Elaboration Publication Request Dossier content for RFC: • Feeder Pre-Booking Path Elab. Draft Offer Tasks/possibilities for IMs • Edit feeder in main TT, option to create sub at anytime • Pa. P 1 TM Pa. P • Edit main TT according to Pa. P rules, option to create sub for day 1 • Pa. P 2 Pa. P • Edit main TT according to Pa. P rules • Pa. P 3 Pa. P • Edit main TT according to Pa. P rules • Pa. P 4 TM TM TM • Edit main TT, option to create sub at anytime • Pa. P 5 TM TM TM • Edit main TT, option to create sub at anytime • Outflow • Edit outflow in main TT, option to create to sub at anytime 16 September 2020 10

Draft Offer Publication Request Pre-Booking Path Elab. Draft Offer What will likely happen with the clean Pa. Ps (Pa. P 2 and Pa. P 3)? • IM might publish subsidiary also for the clean Pa. P days • Still better option than uploading PDFs • Still easier to compare the request to the offer as there won’t be any managed by PCS subsidiary timetable Offer: • Days that are covered by subsidiaries: offer in the subsidiary • Days that are not covered by subsidiaries: offer in the main timetable (main route), everything else should be only deviation. Technically Pa. Ps are only in the main timetable. Request for the IMs: • For better understanding, if subsidiary is really necessary, then please prepare that for your whole network: • Origin – Handover • Handover – Destination As you do it already today. 16 September 2020 11