Planned Cancellations: Difference between revisions
PeterHicks (talk | contribs) Add an overview of planned cancellations |
m categorisation |
||
| Line 11: | Line 11: | ||
Planned cancellations will be activated by a [[Train Activation]] message as normal, but immediately cancelled with a [[Train Cancellation]] message with a 'PD' - Planned Cancellation - causation code. For the purposes of tracking real-time trains, these can be ignored. | Planned cancellations will be activated by a [[Train Activation]] message as normal, but immediately cancelled with a [[Train Cancellation]] message with a 'PD' - Planned Cancellation - causation code. For the purposes of tracking real-time trains, these can be ignored. | ||
[[Category:Schedule Data]] | |||
Revision as of 09:11, 20 May 2013
Overview
Planned cancellations are schedule records with an STP indicator of "C" which are overlaid on WTT schedules. They contain no calling points, and they indicate a schedule is not valid for a particular day.
The difference between a planned cancellation and an operational cancellation is subtle, but important:
- An operational cancellation is reactive - a train was due to run to this schedule, but was cancelled for an operational reason, e.g. service disruption
- A planned cancellation is not reactive - the schedule that would apply on a particular date is overridden, for example, on a public holiday
Activations for CAN schedules
Planned cancellations will be activated by a Train Activation message as normal, but immediately cancelled with a Train Cancellation message with a 'PD' - Planned Cancellation - causation code. For the purposes of tracking real-time trains, these can be ignored.