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' stop monitoring 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.

If your SIRI suppliers' stop monitoring feed does provide cancelled visits, these will be filtered if: 

  • The MonitoredCall->DepartureStatus field equals “cancelled”
  • A MonitoredStopVisitCancellation element is included in the StopMonitoringDelivery, and the ItemRef matches the ItemIdentifier on a MonitoredStopVisit

If you’re expecting visits to be removed from departure boards via SIRI cancellations but they’re still showing, then please confirm with the supplier that either of the above methods are set up for your SIRI-SM feed.

If your SIRI supplier does not support either providing cancellations that match the above methods, or not sending cancelled visits, you can prevent them being displayed to passengers using the “Network” → “Journey Cancellations” section of Passenger cloud, for further details see Managing journey cancellations.

Continue to the next article on Managing Departure Boards: Definitions.