When journeys are cancelled in a SIRI system, by default we revert departure boards to scheduled times. This is because we've seen errors with SM feeds, where visits were lost and departure boards were empty when they shouldn't be.
From what we've seen from most SIRI suppliers' SM feeds, cancelled visits are omitted, rather than shown in the feed as cancelled.
This fall-back is configurable in our system, so the fall-back to scheduled times can be removed if required. This would have the effect of not showing cancelled buses on departure boards but would also mean that if the feed had errors then the departure boards would be empty.
The [2] different departure board configuration options are shown below. For each configuration, the same 3 example visits are used as input data.
[1] Departure board configured to always show data, no matter what sources it includes
| If the departure board has | Will the departure board include the visit? |
| A: 9am visit with only SIRI data | ✓ |
| B: 10am visit with only TXC data | ✓ |
| C: 11am visit with both SIRI and TXC data | ✓ |
[2] Departure board configured to require data from SIRI
| If the departure board has | Will the departure board include the visit? |
| A: 9am visit with only SIRI data | ✓ |
| B: 10am visit with only TXC data | - |
| C: 11am visit with both SIRI and TXC data | ✓ |