Presentation is loading. Please wait.

Presentation is loading. Please wait.

RFC Short Term Path Request Pilots

Similar presentations


Presentation on theme: "RFC Short Term Path Request Pilots"— Presentation transcript:

1 RFC Short Term Path Request Pilots
Vienna, 10th May 2017

2 ScanMed

3 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 submissoion of the offer Pre-accepted offer (will be included in the PCS TAF-TSI developments in Major Release November 2017) is supported Partial offer id possible (up to the customers decision, submission only if the border time is confirmed) 22 November 2018

4 Baltic-Adriatic

5 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 22 November 2018

6 Orient/East-West

7 Orient/East-West 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 22 November 2018

8 PCS Impact

9 Pilot impacts on PCS PCS is planned to be used in each mentioned pilot
Impact on PCS Likely maintenance/configuration issues Notification service configuration National IM parameter set up Minor modification How to publish a PaP in the „N-day” window? Necessary changes to be done until November 2017 22 November 2018


Download ppt "RFC Short Term Path Request Pilots"

Similar presentations


Ads by Google