When: Tuesday, Nov 14, 2017, 08:00
Where:
Nov
14

Where to find?

Carry forward function is located under the Dashboard menu in Bulk editing.

Carry forward selection from menu

How to use?

In the Carry forward view the user can find the same filter criteria as in Advanced Search. Here the user can search for the dossier that he/she would like to carry forward to the next timetable period. The result will have the following content:

Carry forward search result

After the user clicks on the "Start carry forward" button, a maximum three steps process starts. Number of process steps depends on the used operation points and national IM parameters.

Steps

Timetable selection

In the first step the user can select:

  • Which timetable should be carry forwarded? IM or Applicant timetable. The default value is IM timetable
  • To which phase should PCS promote dossier? The default value is Open, although the user can select Harmonization too.

Carry forward step 1

Operation points

User can select mapping for invalid operation points found in selected timetables for all selected dossier and/or passenger train composition migrated operation points (more details below). Operation point validity is calculated based on respective timetable validity period or in the case of train composition the validity period of the main timetable.

In this step, the user can replace the invalid operation points with a valid in every affected dossier in a single step.

Carry forward step 2, operation point mapping

Of course it is mandatory for the user in this step to fix the invalid operation point, however, later it would take much more time to do it in every dossier and every timetable one by one. Thus the system asks for confirmation if the user likes to continue without mapping.

Carry forward step 2, confirmation message

Please note that in order to submit Path Request all the used locations in the dossier have to be valid.

IM Parameters

User can enter new dossier level parameters. This step is visible only if the Applicant that is performing the carry forward is paired in any of the selected dossiers with an IM agency for which the system did not succeed to map any of the dossier level IM parameters. The rest of the parameters are mapped and copied based on the new feature in IM parameters carry forward to next timetable period with a link being kept or mapping based on the name and type of the parameter. The entered dossier level parameters will be applied to all selected dossiers.

Carry forward step 3, parameter mapping

Upon confirmation, the bulk carry forward process is started in the background and after all selected dossiers are carry forwarded successfully an email notification is sent to the user. Also, a notification is sent, if the process failed for certain dossiers in which case the dossier id is indicated and all selected dossiers after this dossier are not carry forward.

Loco types

With Major Release 2017 Loco types have become a list in PCS uploaded by the IMs instead of the former free text field. During carry forward to TT2019 PCS tries to resolve the free text entry - defined loco type mapping in the background. Long-term the user will be able to map the locos if there is an update in the loco type database from one year to another.

  • for dossiers that have loco type number system tries to find defined loco type for that loco type number for the target TTP. If matching is found loco type is replaced
  • for dossiers that have loco types there are 2 cases that are covered:
    • exists loco type for target TTP with the same loco type number for the given agency -> it will be automatically replaced
    • not exist loco type for the next TTP with the same loco type number for the given agency -> system offer view where user can choose with which one wants to replace the invalid one

In this case the system cannot resolve automatically the GM66; CRB CL66 loco type that is why the user should fix it during the carry forward. Please note that each Applicant has access to the loco type database in PCS under the Administration menu.

After typing "gm..." the system proposes the possible loco types. User can select the proper one and apply the fix. After when it is fixed user can proceed further and the system will ask the same confirmation as it does with the operation points.

Passenger train composition

Until timetable period 2017 the train composition of the passenger Applicants had a lot of free text fields. After Major Release 2017 some of the train composition fields will be changed to lists instead of free text.

  • From/To fields are replaced with actual operation points on the best effort bases:
    • Matching is done with operation points in the selected timetables based on the operation point name
    • The matching algorithm accepts the first/last operation point that has a name that is equal or starts with the from/to text respectively and it can cope with upper/lower case differences and umlaut characters. Examples
      • Berlin could be Berlin Hauptbahnhof...
      • Budapest could be Budapest-Keleti
      • Wien Hbf could not fit Wien Hauptbahnhof..., because Wien Hbf does not fit either to the equal or the starts with the rule

      If PCS cannot match the operation points, the train composition field becomes empty there. If PCS finds an invalid operation point in the timetable, the same rule would be applied as written above. The user will have the possibility to map the invalid operation points during the carry forward.

  • Prev./Sub seq. Route fields will become empty. After the carry forward the Applicants can select actual operation points to this field
  • Admin free text fields are replaced with the actual Applicant agencies (short name)
  • Code free text fields are replaced with a single select list

 

Period: Submission of Ad-Hoc Path Requests

Milestone: Dossiers in Final Offer to Active Timetable

Milestone: Dossiers in Observations to Post-Processing

Deadline: Path Request for Annual Timetable 2023

Milestone: Limit for answering path study requests

Period: Dossiers in Feasibility Study Result to Harmonization

Milestone: Dossiers in Harmonization Conference to Harmonization

Milestone: Dossiers in Harmonization Conference to Feasibility Elaboration Conference

Deadline: PaP Publication

Period: Submission of Ad-Hoc Path Requests

Milestone: Dossiers in Final Offer to Active Timetable

Milestone: Dossiers in Observations to Post-Processing

Route Object in PCS - workshop

Deadline: Path Request for Annual Timetable 2023

Milestone: Limit for answering path study requests

Period: Dossiers in Feasibility Study Result to Harmonization

Milestone: Dossiers in Harmonization Conference to Harmonization

Deadline: PaP Publication

Deadline: Path Request for Annual Timetable 2022

Milestone: Dossiers in Harmonization Conference to Feasibility Elaboration Conference

Changes in the train parameters, appointing RU as an Applicant, introduction to TOM

PCS Test Group September 2022

PCS User Group February 2022

PCS Test Group February 2022

Period: Dossiers in Final Offer to Active Timetable

Period: Dossiers in Post-Processing to Final Offer

Milestone: Dossiers in Observations to Post-Processing

Milestone: Dossiers in Harmonization Conference to Feasibility Elaboration Conference

Milestone: Release Path Elaboration

Deadline: Path Request for Annual Timetable

Period: Dossiers in Feasibility Study Result to Harmonization

Milestone: Limit for answering path study requests

Milestone: Dossiers in Harmonization Conference to Harmonization

Deadline: PaP Publication

PCS User Group February 2021

FTE D Freight Traffic Day 3 / FTE C Passenger Traffic Day 2

FTE D Freight Traffic Day 4 / FTE C Passenger Traffic Day 3

FTE D Freight Traffic Day 2 / FTE C Passenger Traffic Day 1

RFC Rhine-Alpine, Scan-Med, Baltic-Adriatic, and Mediterranean PCS Training February 2020

RFC Orient/East-Med, Czech-Slovak, and Amber PCS Training February 2020

RFC Baltic-Adriatic, North Sea-Baltic, Czech-Slovak and Amber PCS Training February 2020

RFC Rhine-Alpine, Scan-Med, Orient/East-Med, and North Sea-Baltic PCS Training February 2020

RFC North Sea-Med, Atlantic, Mediterranean, and North Sea-Baltic PCS Training January 2020

PCS CCB Group Meeting Sep 2020

PCS User Group Half-day Meeting Sep 2020

PCS User Group Half-day Meeting May 2020

PCS Test Group Half-day Meeting May 2020

PCS CCB Group Half-day Meeting Feb 2020

PCS User Group Half-day Meeting Feb 2020

PCS Test Group Half-day Meeting Feb 2020

PCS Passenger Traffic IMs second day Training Nov 2019

PCS Passenger Traffic IMs Half-day Training Nov 2019

PCS Passenger Traffic Applicant Half-day Training Nov 2019

PCS Passenger Applicant Traffic Training Nov 2019

PCS CCB Group Meeting Sep-2019

PCS Train the trainer Sep-2019

PCS Test Group Meeting July 2019

PCS Test Group Half-Day Meeting July 2019

Railway Undertakings Advisory Group for Timetabling

PCS train the trainer May 2019

Period: Dossiers in Final Offer to Active Timetable 2020

Period: Dossiers in Post-Processing to Final Offer 2020

Milestone: Dossiers in Observations to Post-Processing 2020

FTE C - D Passenger and Freight Traffic 2019

Period: Dossiers in Path Elaborations to Observations 2019

Deadline: Draft Offer 2019

Milestone: Preparation of RNE Technical Meeting 2020

Period: Pre-Booking for Annual Timetable 2020

Milestone: Release Path Elaboration 2020

Deadline: Path Request for Annual Timetable 2020

FTE B Passenger Traffic 2020

Period: Dossiers in Feasibility Study Result to Harmonization 2019

Milestone: Limit for answering path study requests 2020

Milestone: Dossiers in Harmonization Conference to Harmonization 2020

Deadline: PaP Publication 2020

PCS User Group Meeting Sep-2019

PCS Test Group Meeting Sep-2019

PCS Test Group Meeting May 2019

PCS Test Group Meeting Feb-2019

PCS User Group Meeting Feb-2019

Baltic-Adriatic, North Sea-Baltic, Czech-Slovak and Amber Corridors PCS Training 2019

Rhine- Alpine, ScanMed and North Sea – Baltic Corridors PCS Training 2019

Orient/East-Med, Mediterranean, Czech-Slovak and Amber Corridors PCS Training 2019

National IM Parameter and Loco Preparation for TT2020

PCS User Group Meeting Sep-2018

PCS User Group Meeting May-2018

PCS User Group Meeting Feb-2018

North-Sea – Mediterranean, Atlantic and Mediterranean Corridors PCS Training 2018

Baltic-Adriatic, Orient/East-Med, Czech-Slovak PCS Training 2018

Rhine- Alpine, ScanMed and North-Sea – Baltic PCS Training 2018

Start Carry Forward for TT2019

PCS Training Group Meeting Sep-2017

PCS User Group Meeting Sep-2017

PCS Test Group Meeting Sep-2017

Start of timetable 2018

FTE D Freight Traffic 2020 Day 1

Period: Dossiers in Final Offer to Active Timetable

Period: Dossiers in Post-Processing to Final Offer

Milestone: Dossiers in Observations to Post-Processing

Period: Dossiers in Path Elaborations to Observations 2020

Deadline: Draft Offer 2020

Milestone: Preparation of RNE Technical Meeting

Milestone: Release Path Elaboration

Deadline: Path Request for Annual Timetable

Period: Dossiers in Feasibility Study Result to Harmonization

Milestone: Limit for answering path study requests

Milestone: Dossiers in Harmonization Conference to Harmonization

Deadline: PaP Publication

PCS Test Group Meeting May-2017

PCS User Group Meeting May-2017

PCS Training Group Meeting Feb-2017

PCS User Group Meeting Feb-2017

PCS Test Group Meeting Feb-2017

North Sea – Mediterranean, Atlantic and Mediterranean RFCs PCS Training 2017

Baltic-Adriatic, Orient/East-Med and Czech-Slovak PCS Training 2017

Rhine- Alpine, ScanMed and North-Sea – Baltic PCS Training 2017

Empty Envelope Concept common workshop

IM parameters are available for edition for IMs

RU Advisory Group and TT Support Group Meetings