If several PT traffic streams are requested, the order in which they are to be prioritised must be decided. Newly requested PT traffic streams must be placed in a queue. With the PT prioritisation module, vs | plus provides the option of creating a queue based on various criteria.
When a PT traffic stream is first requested, the system checks where the newly requested PT traffic stream should be placed in the queue. The decision is made in several stages in a freely definable order. The first criterion is used to check where the newly requested PT traffic stream should be queued. If there is equivalence with a PT traffic stream that has already been applied for, the second criterion is used for further checks, then the third criterion and so on. The checks are carried out until there is no ambiguity. It is essential that PT traffic streams are not re-sorted once they have been queued.
The queuing principle without re-sorting existing entries reduces the risk of instability in the influencing process (initiated influencing processes are cancelled in favour of a new one).
In order to achieve clarity in the sequence in all cases, it is recommended that the PT priority list criterion is always entered in the criteria sequence.
|
Display |
Identifier |
Values |
Description |
|
Rank |
Rank 1 to 8 |
|
When several PT traffic streams are requested, it must be decided in which order they are to be prioritized. Newly requested PT traffic streams must be placed in a queue. With the PT prioritization module, vs | plus provides the possibility to create a queue based on different criteria. When a PT traffic stream is requested for the first time, it is checked at which position the newly requested PT traffic stream is to be placed in the queue. The decision is made in several stages in a freely definable order. The first criterion is used to check where the newly requested PT traffic stream should be queued. If there is equivalence with a PT traffic stream that has already been registered, the second criterion is used for further checking, followed by the third criterion, and so on. The check is continued until there is unambiguity. It is essential that once PT traffic streams have been classified, they are no longer reclassified. |
|
Criterion |
|
List of possible criteria. |
|
|
|
|
|
|
|
|
|
no criterion |
No criterion selected. |
|
|
|
HStg |
Holding a stage. |
|
|
|
Stage holds in the red. |
|
|
|
|
ArrSF |
Arrival in the frame signal plan. |
|
|
|
PC |
Priority classes. |
|
|
|
Infl_zones |
Influence Zones. |
|
|
|
PrioLists |
Priority PT Lists. |
|
|
|
PT Ph |
VOeV Priority. |
|
|
|
SchLateness |
Schedule position |
|
|
|
estArr |
estimated time of arrival |
|
|
|
withoutSort |
After priority flag without sorting. |
|
|
|
withSort |
After priority flag with sorting. |
|
|
|
user |
User definition. |
|
Parameter |
from vs | plus version |
Comment |
|
Criteria sequence |
8.0.0 |
Up to version 6.2.6: If no criteria sequence is supplied in vs | workSuite, a default sequence is created in vs | plus. This consisted of " stage hold" (HStg) and "expected arrival second" (estArr). This resulted in all PT traffic streams being evaluated according to the criteria sequence. If a traffic stream had reached the top of the list, it would hold that until it had logged off or was forcibly deleted. From version 8.0.0: New from this version is that no default sequence is created without criteria sequence. PT traffic streams are then equal to IT traffic streams. For a phase change, only the intervention types and the green times are decisive. PT traffic streams therefore no longer block the sequence until they are de-registered. |
|
8.0.0 |
Up to and with vs | plus version 6.2.6 the following applied: If a traffic stream is in the first position of the criteria sequence, it cannot be aborted by any conflicting traffic stream until it checks out or is forcibly deleted - even if the traffic stream has green. As of vs | plus version 8.0.0 there is the criterion: "Stage hold in red" (PhHr). This ensures that the traffic stream remains at the top of the criteria sequence only as long as it has red. As soon as it has green, it loses its top position and can thus be aborted by any conflicting traffic stream with the corresponding intervention type. Only when it has red again, it will be re-ranked in the criteria sequence if it is logged in. The "Stage hold in red" criterion applies to all traffic streams. It also overrides the "Hold stage" criterion, even if it comes after it in the sequence. |