Applicant/IM/C-OSS Timetable_old


Each dossier contains at least two timetables: an Applicant and an IM timetable. Applicant timetable contains the information about the request of the Applicants and the IM timetable represents the answer from IMs. In case of a PaP request, PCS also shows the C-OSS timetable that represents the pre-booking decision of the RFCs.

The timetables for the Applicants, IMs and C-OSS differ in a few details only. For that reason, the data fields are described together. If a data field is only available to either one of them, it is identified accordingly.

Basic access control rules (depends also on the dossier phase):

  • Applicants can only edit the requested timetable for their particular national section.
  • Similarly, the IM’s can only edit the IM timetable for their national section.
  • C-OSS can only edit the path section that belongs to its PaP or can edit any feeder/outflow path sections
  • Each Dossier has a specified leading Applicant and leading IM. From timetable, editing point of view the leading IM has the same access as any other, but among the Applicants, the leading Applicant has additional rights. Regardless of the position of the leading Applicant, it can always edit the reference point of the Applicant timetable (origin station).

Timetable segment of the dossier has the following tabs.

  • Geography: geographical presentation of the timetables. All subpaths are shown per territories and the user can edit them according to the above written basic access control rules.
  • Calendar: presentation of running days and the validity period of the timetables
  • Path Variants: presentation of the combination of all entered subpath in the dossier. The route is shown from origin to destination across all territories.

Geography contains a sequence of path sections. In the header is shown current entered validity period of the calendar with selected operation days in brackets and PCS Path ID. In editing mode, the user can select, if the fields for the earliest/latest times should be shown either. In reading mode, these fields are shown in the tooltip above the time entries (if they are defined). There is also a free text field for "Service days for reference point", where additional information could be defined to the calendar.

For each inserted path section, the following fields are at disposal:

  • Actual Arrival time: field for requested/offered time in the format "hh:mm".The user can enter the time in "hhmm" format, PCS will adjust it automatically.
  • Actual Departure time: field for requested/offered time in the format "hh:mm". This is a mandatory field for the reference point. The user can enter the time in " hhmm " format, PCS will adjust it automatically.
  • Dwell time: This field is for entering the minimum stop duration at the stop in decimal number. For further consistency rules and constraints of this field, please check the referenced documentation
  • Responsible Applicant: Here the responsible Applicant or unknown agency (this last one for study purposes only) has to be selected for the operation point. Each participating Applicant has to be responsible for at least one path section
  • Responsible IM: PCS sets automatically the responsible IM according to the selected operation point. However, in case of a border crossing, it's possible for the users to select a different responsible IM. Operation point owner IM and responsible IM (in most of the cases the same) are shown below the location.
  • Location: This field serves as an operation point selection. When the user starts typing, the system predicts according to inserted signs and pre-select corresponding operation points.
  • Star: the indication of the reference point. It's set automatically by the system to the origin point of the timetable.
  • Bell: the indication of the construction starting point. It's an optional indication that can be set by the Applicants to inform the IMs/ABs about the point, where they should start the construction of the paths.
  • Detail: This field could be used for a closer description of the stop, e.g. platform or track specification.
  • Train no.: Field for train number valid for the path from this path section (used as OTN - Operational Train Number - by the IMs)
  • Path no.: Field for path number valid for the path from this path section.
  • Catalogue path no.: Field for catalogue path number valid for the path from this path section. It's fulfilled automatically by PCS based on the selected PaP or catalogue path (if this number is published there)