Applicant/IM/C-OSS Timetable


Each dossier contains at least two timetables: an Applicant and an IM timetable. The applicant timetable represents the Applicant's path request and the IM timetable represents the Applicant request's response from the IMs. If the dossier has a PaP or PaPs added then the RFC acts on behalf of the IM. In this case, the C-OSS timetable represents the response and decision for the Applicant's path request in pre-booking. The timetables have the same structure and contain common fields but it differs in some fields based on the user roles in the system (Applicant/IM/C-OSS).

Basic access control rules (phase-dependent):

  • 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.

The dossier's timetable segment consist of the following tabs:

  • Territories: geographical presentation of the route and timetable divided to Applicant - IM pairs. Timetables are shown in subpaths.
  • Calendar: It shows the running days and on the top shows the validity period of the entire timetable year. The system allows us 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. 
  • Path Variants: It gives a global view of our timetable data and presents the combination of all entered subpaths in the dossier. The route is shown from origin to destination across all territories. It also indicates path variants consistency.

The following fields are available for each inserted path section:

  • Actual Arrival time: field for requested/offered time in the format "hh:mm".The user can enter the time in "hhmm" format as well and the system adjusts it. This rule applies to all "Time" fields.
  • Actual Departure time: field for requested/offered time in the format "hh:mm". This is a mandatory field for the reference point.
  • Include the earliest/latest times: this is an optional field and the system allows us to define the earliest and the latest times.
  • Include public times: this is an optional field and the system allows us to define the public transport service times, to assist passengers with planning a trip.
  • Service day for a reference point: it is an optional field and the system allows us to add common descriptions among subpaths that are combined.
  • 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
  • Offset/Time zone: Manual time offset defined in days assigned by the user to an arrival or departure time in a path section. The system allows defining the time zone value in each path section in hours format.
  • Responsible Applicant: the responsible Applicant or unknown agency (this last one for study purposes only)  be default always the creator applicant but possible to change the Applicants corresponding to the neighboring country.
  • Responsible IM: system-generated field according to the selected operation point depending on where is that operation point geographically and by which IM has been registered in the system.
  • Location: select the operation point name by start typing the name and PCS will propose the list of available locations registered in the system. 
  • Star icon: indicates the reference point of the timetable. Always the first path section is the reference point of each subpath. 
  • Gear icon: 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. By default set to the first path section as Construction reference point of each sub-path that doesn’t have a Construction reference point assigned.
  • Detail: This field could be used for a detailed 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 ITN - Infrastructure Train Number)
  • 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)