ASIST Support
Data Issue[edit]
aSIST receives train movement data that informs the various tools, such as indicating the next headcode on the aSIST Wrong Route Tool.
The Wrong Route Tool displays a health check to users, indicating when the last data message was received.
The TD lag will typically be within 10 seconds.
Overnight if less trains are running there may be no trains to report on the TD and users will see this lag increase. This is not a cause for concern.
After 45 seconds of no TD report the following status message will appear seen in red text in the image below:
aSIST sends a 'heartbeat' every 60 seconds. Therefore in most cases the above message will disappear within a minute.
However in the event the message persists, there may be an issue with the incoming data feed.
User Actions[edit]
Users are requested to first rule out an internet issue within their signalling location.
- Does the page work following a refresh?
- Are other web pages updating?
- Does it work following the browser being closed and restarted?
If aSIST is still not updating, users should contact the on-call Support. (Click on the hyperlink for the details of the on-call technician).
Unmatched Schedules[edit]
If aSIST is unable to match a schedule, it will display a question mark as seen below:
If all services are showing a question mark then there may be an issue with the timetable feed.
User Actions[edit]
First, check CCF. If the headcode is grey then there is not a timetable for that service and the issue is not with aSIST.
Otherwise, is there significant disruption or a known issue meaning services are running without a published plan?
If the issue is believed to be with aSIST, users should contact the on-call Support. (Click on the hyperlink for the details of the on-call technician).