You can see the status of their SIRI Vehicle Monitoring feeds within the Vehicles section of Passenger Cloud.
This feature lists the subscriptions and some details about them, such as:
- Last seen - when Passenger last received any data from the SIRI supplier.
- Last matched - when Passenger was last able to match any vehicle activity data from the SIRI feed to the TransXChange.
- Last updated - when Passenger was last able to match any vehicle activity data from the SIRI feed to the TransXChange.
- Matched vehicle activity - the number of vehicle activity elements from the last service delivery that we were successfully able to match to an operator/line from your TransXChange, these vehicles will appear in Cloud/Apps/Websites.
- Unmatched vehicle activity - the number of vehicle activity elements from the last service delivery that we were not able to match to an operator/line from your TransXChange, these vehicles will not appear in Cloud/Apps/Websites.
- Update interval - the requested interval for the SIRI supplier to provide vehicle activity data
- Note that this field varies by SIRI supplier, based on what their system supports. Apps / Websites will poll vehicle activity data at a 10 second interval regardless of the supplier.
- Ticketer only - Operator reference - the reference used to request a specific operator’s data from the SIRI supplier. This is an optional filter.
- Vehicle monitoring reference - an arbitrary reference used to request a subset of data from the SIRI supplier.
By clicking on a subscription you can see the following additional information:
- Supplier - details who provides the SIRI-VM feed to Passenger.
- URL - the URL of the supplier that Passenger uses to establish a subscription.
- Detail level - the requested level of detail to be sent from the SIRI supplier.
- Requestor reference - an arbitrary reference used to identify the requestor, this is given to Passenger by the supplier.
- Username - the username we use to connect to the SIRI supplier.
Using these details it is possible to easily identify common issues with SIRI feeds, for example:
- If the last seen field is significantly different from the update interval, your supplier may be having issues providing data reliably. This can be resolved by contacting your SIRI supplier.
- For new feeds, you should confirm all vehicles are set up with your SIRI supplier.
- Short term, a re-subscription will often improve data transmission, this can be requested via our Help Desk.
- If this is a new feed and we’ve never seen data, please ensure you have correctly configured all vehicles with your supplier, then request a re-subscription via our Help Desk.
- If the last matched field is significantly different from the update interval (or non-existent):
- Your TransXChange Operator and Line Names may not match the SIRI feed, this can be resolved by one of the following:
- Updating your TransXChange to match what is being sent by the SIRI supplier
- Updating the reference with your SIRI supplier to match your TransXChange
- Your operator code should match your “National Operator Code” (NOC)
- Your TransXChange Operator and Line Names may not match the SIRI feed, this can be resolved by one of the following:
- Your SIRI supplier is not sending vehicle activity data, this can be resolved by one of the following:
- Contact your SIRI supplier to enquire why Passenger cannot match any vehicle activity data.
- Short term, a re-subscription may resume data transmission, this can be requested via our Help Desk.
- Ticketer only - If the operator reference does not match the operator code defined in your TransXChange:
- This can be resolved by ensuring that the same NOC is being used with your supplier and in your TransXChange that you upload to Passenger Cloud
- Note that this field is not required. If no operator reference is defined, then all data will be sent from the supplier.
- This can be resolved by ensuring that the same NOC is being used with your supplier and in your TransXChange that you upload to Passenger Cloud