PT-M Traffic Stream Priorities

Countdown time:

Forced cancellation takes place at the earliest at the start of green. This means that a request is held even if the self-counting time is 0s, for example, until the green start. The exception to this is the special case of the compulsory request time of the check out message point = INAC.

PT priority list:

If a priority list is defined without equal positions, the following decision criteria become ineffective, as the decision can already be made unambiguously. On the other hand, further criteria must become effective in the case of equal rankings.

Prioritisation type and priority classes:

On the one hand, it may be desirable not to prioritise a PT traffic stream that is too early. On the other hand, it may be that a PT traffic stream that is too late should no longer be prioritised. For this reason, the first step is to check the type of prioritisation required, irrespective of conflicting requirements. This decision should be made on the basis of the timetable position criterion:

Figure 80: Schedule position

In contrast to the other traffic stream types, a PT traffic stream can be defined in several priority classes in the main series. vs | plus checks which priority class the PT traffic stream is to be treated in as part of the "Prioritisation tests" function based on the timetable position and the defined limits.

Distance following train:

Value range minimum distance:

INAC	The minimum distance parameter is not taken into account.
[1 ... 3276]	Minimum required time to the preceding train.
no follower train	Follow-up train is never taken into account.

Value range maximum distance:

all	Always take the next train into account.
[1 ... 3276]	Maximum permitted time to the preceding train.
no follower train	Never take the next train into account, the next train is only taken into account again after the minimum red period at the earliest.

The minimum time and maximum time limits must not overlap (the maximum time must be greater than the minimum time).

Display	Identifier	Values	Description
TctDn	Countdown time		With the initial request at the first message point vs \| plus starts a request time counter [twts] related to the traffic stream as described. The following message points are recalibrated with TCAL. Thus, the request time counter [twts] represents the current travel time since the initial request on the recorded route. Now a logoff can be lost e.g., by faulty acquisition. For these cases vs \| plus provides the parameter "countdown time". With this, a train is deregistered (train-by-train forced deletion) when the time counter [twts] reaches the value countdown time. It should be noted that vs \| plus holds a request until either a correct check-out or a forced deletion occurs.

		0 .. 3276	If the traffic stream waiting time reaches the countdown time, the foremost train is deleted. The request remains until the countdown time has elapsed. Several green repetitions are possible.
		once green	Forced deletion after the first green window, which is in the range of the expected arrival second.
PrioList	Priority list PT		Ranking order according to which competing PT are to be considered (rank 1 = high priority, rank 50 = low priority). The parameterization is done by assigning ranks. Equal positions of traffic streams (traffic streams have the same rank) are allowed.

		1 .. 50	Rank
PrioType	Type of priority		The Prioritization type parameter defines the criterion according to which the limits Timetable position: upper and lower limit are to be determined.

		Schedule	According to schedule.
		Priority	According to priority according to VOeV regulation.
Late_low_PC	Schedule lateness: lower priority class		Depending on the lower limit, a registered PT traffic stream is assigned to the priority class specified in the lower priority class parameter. This means that the traffic stream in question, regardless of whether it is assigned to other priority classes, is treated only in the lower priority class specified under the parameter.

		NOT	Will not be considered.
		1 .. 3 (12)	Can be assigned to one of the classes 1 to 3 (12).
Late_low_limit	Schedule lateness: lower limit		The lower limit parameter defines the limit between the lower priority class and the medium priority class. If the deviation from the timetable is greater than the entered value, the PT traffic stream is treated in the priority class specified under lower priority class. The parameters lower and upper limit can be applied analogously for the timetable position as well as for the priority according to the VOeV regulation. The choice between these two possibilities is defined with the parameter prioritization type.

		+1 ... +127	Delays
		Schedule	According to schedule.
		-1 ... -127	Prematurity
		+1 ... +127	For the prioritization type with priority according to VOeV, this value range applies.
Late_med_PC	chedule lateness: medium priority class

		NOT	Will not be considered.
		standard vs \| plus	vs \| plus searches for the traffic stream in question in order in priority classes 1, to 3 / 12 and processes it where it is found first.
		1 .. 3 (12)	Can be assigned to one of the classes 1 to 3 (12).
Late_upper_limit	Schedule lateness: upper limit		The lower limit parameter defines the limit between the lower priority class and the medium priority class. If the deviation from the timetable is greater than the entered value, the PT traffic stream is treated in the priority class specified under lower priority class. The parameters lower and upper limit can be applied analogously for the timetable position as well as for the priority according to the VOeV regulation. The choice between these two possibilities is defined with the parameter prioritization type.

		+1 ... +127	Delays
		Schedule	According to schedule.
		-1 ... -127	Prematurity
		+1 ... +127	For the prioritization type with priority according to VOeV, this value range applies.
Late_upper_PC	Schedule lateness: upper priority class

		NOT	Will not be considered.
		1 .. 3 (12)	Can be assigned to one of the classes 1 to 3 (12).
Min_distance	Follower train: Minimum headway		If a PT logs off and another train is already registered (subsequent train), a decision must be made as to whether the subsequent train is also to be taken into account. The parameters Minimum and Maximum distance of following train influence this decision. If the time interval corresponds to the parameters Minimum and Maximum interval of following train, vs \| plus additionally checks whether the frame signal for extension is still present at the second of the expected arrival and whether the maximum green time tg max2 is then not exceeded. Only if all conditions are fulfilled, the following train is considered. In any case, however, a following train is only considered if its extension conditions are not violated.

		INAC	The minimum distance parameter is ignored.
		no follower train	Follow-up train is never taken into account.
		1 .. 3276	Minimum required distance to the preceding train in seconds.
Max_distance	Follower train: Maximum headway		The Maximum spacing of subsequent trains parameter results in an upper limit. Follow-on trains that have a greater time interval than the maximum interval is no longer taken into account.

		no follower train	Never consider following move, following move is considered again at the earliest after the minimum red duration.
		all	Always consider the following train.
		1 .. 3276	Maximum allowed distance to the preceding train in seconds.