Dossier creation demo

Content

Video Text

There are several ways to create dossier: 

  • Copy dossier 
  • Carry forward an existing dossier to the next timetable period 
  • From PaP Search (Please refer to "Select PaPs" document) 
  • Create a new dossier using "+ New dossier" button with the wizard 

For presenting purposes using "Create New Dossier Wizard". 

The following steps are must fill to proceed further with the new dossier creation wizard: 

  • Basic Data 
  • RU path (main RU timetable) 
  • Dossier-level data 
  • Train Parameter 
  • Subpaths 
  • Calendar 

 

Basic data 

Draft version 

If you save the dossier before you get to the final step and press "Create dossier" button, then the created dossier is saved automatically by PCS into the Draft versions.  

To access Draft versions, click on "+ New Dossier" which takes you to Basic data and then click on "Open an existing draft" dossier:

A list of draft dossiers appears on the screen, select the required dossier by clicking to the dossier which opens up automatically.

PCS will prevent to save the dossier as a draft version without the following data: 

  • At least one path section with missing responsible IM 
  • Only one path section in a territory 
  • Invalid dwell time calculation between the actual arrival and departure time in the path section (ex. arr: 10:00, dwell: 120, dep: 11:00 -> 120 min. dwell time is invalid between arrival and departure).  
  • The same rule applies between the next path sections ex.: ps1 – arr: 10:00, dwell:120; ps2 – arr:11:00 -> dwell time has an invalid value between the actual arrival in a path section (ps1) and arrival time in subsequent path section (ps2). 

 

If you don’t want to use an existing dossier’s draft version, then you need to go through on the dossier creation wizard steps mentioned earlier above. In basic data you need to fill the followings: 

  • Dossier name: mandatory, name the dossier 
  • International train number and Train ID are optional identifiers but can define one international train number for presentation purposes, enter “277”. 
  • Timetable period: the system automatically proposes the current timetable period. In this example select from the drop-down menu year of “2019” can select another time….  
  • Train type: assigned by PCS automatically according to the agency type by the creator agency 
  • Process type: The process type is automatically defined by PCS based on the particular timetable calendar (New, Late or Ad-hoc path request). For further information please visit <<Process Description>> documentation. 
  • Dossier type: select from the drop-down menu “Default”, for further information please visit "Dossier Type" documentation. 

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

There is a page break on the screen highlighting that start to fill the "Train Id" related information’s based on TAF-TSI requirements (further info comes later).

Note: The system prevents an already existing composite Train Id to be defined that is used in another dossier for the same timetable period! 

 

RU Path 

 

In this step, RU can start to build their timetable and start to define the train geographical route by adding operation points. Start type the operation point into the field and PCS will recognize automatically will propose a list of known operation points.  

Please note that the first path section always will be the reference point automatically assigned by PCS system! 

Users can select Construction starting point, which can be changed later in the system, that indicates the starting point of the planning. 

Before completing the timetable and proceed further with new dossier creation wizard, it is possible to name the sub-path section, to do that go to "Sub-path title". This is a useful option for the RU to give identical information to the sub-paths. The system assigns "Main route(S1)" title to an RU path with no title entered, upon saving the dossier. The system proposes to select previously entered title. 

When getting to RU path screen, PCS automatically starts with a blank path section with the creator of RU company appears by default. To add more operation points, use "+ Add path section". When adding a new path section to the RU timetable, PCS assigns automatically the previous path section’s RU-IM pairs. The same rule applies if you want to add a new path section into the middle of the RU path. Easy to use the TAB key to move further when filling the document. After leaving the "Path no." field using TAB key or clicking with your mouse cursor then PCS automatically adds a new empty path section.  

There are some other new fields added to PCS such as Service days for the reference point and TSI variant ID. The Service days for reference point field is an optional text field where the RUs can define the days in service with text or with their special identification. The TSI variant ID is also an optional identifier that consists of exactly two alphanumeric characters and also the system proposes to select previously entered TSI identifier (further details comes later).

For further information please visit "RU/IM Timetable" documentation. 

Next steps are: 

  • Add and remove stations. Please note that re-ordering of stations is not supported 
  • User must define departure on the reference point. This reference point will be the basis of the calendar, running days and offset calculation. 
  • Definition of arrival and departure time. To define earliest/latest times by ticking the checkbox next to <<Include earliest/latest time>>. In the system it adds two extra field for arrival/departure times. The system automatically converting the time format and it is enough to enter numbers into the field. 
  • Definition of dwell time in minutes. For further information please read <<Dwell time>> document. 
  • Responsible RU: default settings is the dossier creator RU, who will be the leading RU in Open phase (leading RU can be changed later in Harmonization, for that, please read <<Edit agencies>> documentation). If you like, you can assign the path section to other RUs. Every RU is available in the list. Please note that they are organized by alphabetical order and filtered by agency type (if the train type of the dossier is cargo, you will see cargo agencies in the list). An RU must be responsible for at least two path sections in the timetable. 
  • Responsible IM: default setting is the owner IM of the operation point. But RU can select another responsible IM (potential use case is the border points). RU-IM pairs are generated based on the responsible IM. Parameters and locos are available also according to responsible IM. 
  • Definition of train number and path number is optional 

 

Dossier-level data 

 

The system assigns the leading IM by default as the pair of the leading RU. The system allows the creator RU user to enter dossier level agency parameters for their IM pairs.  

 

Train parameters 

 

Let’s continue to fill the common train and IM parameters. In this topic, PCS is focusing only on common train mandatory fields such as:  

  • Activity type: start type the planned activity or select from the drop-down menu list 
  • Loco type number: start type in the loco number and system proposes previously entered list of locos 
  • Traction mode: start type in the mode of traction and select it from the drop-down menu list.  Define the unit place the same way into the below field. 
  • Train max. speed: train max speed 
  • Weight carriages set: carriages total weight 
  • Length carriages set: carriages total length 
  • Train weight: traction unit weight 
  • Train length: traction unit length 

Users can use pre-calculation of train parameters based on the selected loco(s) and the weight/length of the carriages. 

Possible to add more locos by clicking to <<Add another entry>> in the traction mode area. The same concerns to DANGEROUS GOODS INDICATION sections. 

 To get a detailed description of all common train parameters please read "Train path parameters" document. Mandatory fields are marked with an Asterix symbol (*) and if the fields are correctly filled it turns into a green pipe (). 

 There are some train attributes constraint please go to "PCS Constraints overview" documentation to read more. 

The system lets you copy the same common train and/or IM parameters is used at the first path section to any other path section using "Copy parameters" button at the bottom of the screen. There is very handy user-friendly feature added into PCS. Use the + or sign by the common train or by the IM parameters to extend/collapse details. 

 There are some train attributes constraint please go to <<PCS Constraints overview>> documentation to read more. 

Subpath 

Since PCS EC version, the subsidiaries are called as subpaths. By default, one subpath is defined per territory (RU-IM pair). If there is a need for deviation, the user can create alternative timetables with subpaths only on his territory. However, it’s also possible to create a whole new timetable along the whole stretch. In this case, the user variant option is recommended, and for that user can use the add user variant option (“+User variant”). It is also possible to add new territory with “+Territory” and/or add subpath with the “+Subpath” buttons. 

When it is required to modify (add/change/delete) the subpath, should edit the subpath to apply necessary changes. For further options check the attached: 

 

Calendar 

The system allows to define the running days and offset for the entire timetable or also possible to define specific months/days for a required journey to every path section in all subpaths. Users can select the entire year, a month, a circulation day or individually day by day in the calendar. 

Users should enter a template calendar for the complete dossier indicating the running days of the planned train(s). The selected running days will be assigned automatically by PCS to the first subpaths. Later, users can switch those days to other subpaths, if it’s necessary. Once the user selects a day in a subpath, PCS will remove it immediately from the other calendar. This logic will prevent overlapping calendars. 

 

For further steps, please check the other videos.