PCS constraints overview

Content

The aim of this document is to give an overview to PCS GUI users and integrators about the constraints that are applied by the system during the daily business with the dossiers. We tried to collect here the fields that are mandatory in PCS and some rules that are applied during dossier creation, dossier editing and dossier processing (change of acceptance indicator and promotion). We also tried to cluster the different constraints, mandatory fields. As this is a summary of the constraints we made some references to the original documentation where you may find more details.

Basic Data

  • Dossier name is a mandatory field of PCS

Agencies

  • There must be always one RU marked as leading RU
  • There must be always one IM marked as leading IM
  • Each agency (RU or IM) must be responsible for at least one path section
  • Production-only agencies have read-only access to the dossier. If an RU is presented in the timetable as production-only, it will have read-only access to the dossier.

Paths

  • Each path (either main or subsidiary) must have at least two path sections
  • Involved RU/IM cannot update/delete anything outside of its responsibility via GUI neither via PCS IP
  • RU/IM can delete international subsidiary timetable via the GUI
  • RU/IM cannot delete international subsidiary timetable via PCS IP

Reference points

  • In the RU timetable part, in each RU timetable (main or subsidiary) there must be one, and only one, reference point.
  • In the IM timetable part, in each IM timetable, there must be one, and only one, reference point per IM.
  • Mandatory departure and arrival time must be entered at the reference point (If it is the starting point, only departure time is needed. If it is the end point, only arrival time is needed)
  • The reference point cannot be deleted from the timetable. If you want to delete it, change the reference point first to another path section and save the timetable.
  • Leading RU has access to the reference point in the RU timetable regardless of the position of the leading RU

Path section content

  • There must be valid operation points at each path section
  • There cannot be an empty calendar at any path section
  • Dwell time
    • It cannot be bigger than the difference between the departure and arrival time
    • It must be entered as a decimal number in minutes

Speed constraints

  • Loco type max speed must be equal to or higher than the train max speed
  • Train max speed must be equal to or higher than the planned speed
  • Loco type max speed must be equal to or higher than the planned speed

PaPs

  • To release Feasibility Study with PaPs, the dossier must have at least one feeder or outflow section

Fix PaPs

  • RU can edit the arrival/departure times only at the first/last path section if it's connected to a feeder/outflow section. Apart from that, the times are read-only for RUs
  • RU can delete always the first and last location of the fix PaP, but never from the middle
  • RU/IM can update the parameters according to the published parameter limits
  • IM can edit the arrival/departure times only at the first/last path section if it's connected to a feeder/outflow section. Apart from that, the times are read-only for IMs
  • IM cannot delete a published, requested, then reserved PaP point from the timetable

Flex PaPs - protected border (path section marked with a lock)

  • RU/IM can edit the times only if it's connected to a feeder/outflow section. Apart from that, the times are read-only.
  • RU/IM cannot delete path section marked as protected border
  • RU/IM can update the parameters according to the published parameter limits

Flex PaPs - regular points

  • RU can delete any regular flex PaP location
  • RU/IM can edit always the times
  • IM cannot delete a published, requested, then reserved PaP point from the timetable
  • RU/IM can update the parameters according to the published parameter limits

Parameters

  • RU/IM must fulfil all mandatory common parameters to process dossier to the next phase (change light and promotion)
  • Dossier level parameters are editable only by RUs
  • RU must fulfil all mandatory national IM parameters (dossier level and/or path section level)
  • IM must fulfil all mandatory national IM parameters (path section level)
  • For information about the common train parameters please check the reference documentation. Please note that each IM can customize default optional parameters to be mandatory only on their network. 

Loco types

  • RU/IM must use valid (the available ones in PCS) loco type in each path section according to the responsible IM of the section

For further ACL rules please check the description of the phases.