ASIST Wrong Route Tool: Difference between revisions
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The aSIST Wrong Route Tool displays the headcode of the approaching train at preconfigured junctions along with its planned route. | |||
In the event of a wrong route, the tool will generate both an audible and visual alarm. | |||
The Wrong Route Tool can also be configured to include train approach alarms, crossing approach alarms, and a TRTS indication. | |||
=Data Feed= | |||
aSIST runs off of the plan contained within acumen. | |||
The plan begins as the long term plan CIF file which is then updated with short term plan incremental CIFs. | |||
On the day of operation, VSTPs are processed alongside other updates through TRUST (e.g. cancellations) and received through external sources such as DARWIN/CIS. | |||
=Initial Screen= | =Initial Screen= | ||
| Line 9: | Line 17: | ||
Users are initially presented with the following screen. | Users are initially presented with the following screen. | ||
::[[File: asist-start.png|400px]] | |||
To start the tool, click on the screen. | To start the tool, click on the screen. | ||
<b>Note:</b> The tool will remain open and running unless there is a connection failure such as a computer restart. Only on these occasions would the initial screen be seen. | |||
=Standard View= | =Standard View= | ||
| Line 18: | Line 28: | ||
==System Health== | ==System Health== | ||
The bottom half of the interface includes a number of | The bottom half of the interface includes a number of indicators of system health. | ||
::* The <b>dot</b> next to <i>SERVER LINK CONNECTED</i> confirms the tool is connected to the server. | ::* The <b>blinking dot</b> next to <i>SERVER LINK CONNECTED</i> confirms the tool is connected to the server. If the dot is static then the server connection has been lost. | ||
::* The <b> TD Lag</b> | ::* The <b> TD Lag</b> indicates how old the data is. There should be minimal lag between a message being sent and then displayed within aSIST. The TD lag will typically be within 10 seconds. | ||
::* The <b>Last Update</b> displays the time the most recent data was received. This will most commonly update every 1-2 seconds. | ::* The <b>Last Update</b> displays the time the most recent data was received. This will most commonly update every 1-2 seconds. | ||
If the system health indicators are not updating as expected, please see [[aSIST Support]]. | If the system health indicators are not updating as expected, please see [[aSIST Support]]. | ||
| Line 31: | Line 39: | ||
The Wrong Route Tool can display up to six different junctions. | The Wrong Route Tool can display up to six different junctions. | ||
Each junction is confined to its own box. For example, below is the display for | Each junction is confined to its own box. For example, below is the display for Bricklayers Arms. | ||
::[[File: | ::[[File: mute.png|330px]] | ||
The tool displays the headcode of the next train approaching the junction. | The tool displays the headcode of the next train approaching the junction. | ||
A <b>black arrow</b> indicates the planned route or direction of that train. | |||
<b> | When the <b>arrow is green</b>, this means the route set is the same as the planned route; a correctly routed train. | ||
If the route set is not the same as the planned route, an audible and visual warning is displayed. An example is seen below in the <i>Wrong Route Set</i> section. | |||
A <b>question mark</b> will be displayed if aSIST has been unable to match a schedule or it is an unplanned service: | |||
::[[File: asist_unmatched.png|350px]] | |||
If multiple headcodes are displaying as unmatched, there may be an issue with the timetable information. Please see [[aSIST Support]]. | |||
Below the arrow is the <b>mute</b> status. When clicked, the mute button will turn pink and show 'Muted' for 60 minutes, or until it is clicked again, whichever is sooner (for example during perturbation when several trains are being diverted). Whilst muted the system will not produce any audible alerts on the selected signal, but will still show a visual alert. | |||
<b>Note:</b> The other boxes below the arrow and headcode have been reserved for additional functionality. | |||
=Wrong Route Set= | =Wrong Route Set= | ||
| Line 59: | Line 67: | ||
The audible alarm reads the name of the signal at the junction. | The audible alarm reads the name of the signal at the junction. | ||
In the example below, 9C21 has been routed | In the example below, 9C21 has been incorrectly routed at Sydenham Junction. | ||
The arrow has turned red to show this is incorrect and the headcode is also flashing red. | The arrow has turned red to show this is incorrect and the headcode is also flashing red. | ||
<b> | <b>Note:</b> The arrow will always point in the intended direction. | ||
::[[File: wrong_route_set.gif|400px]] | ::[[File: wrong_route_set.gif|400px]] | ||
The audible alarm will sound once. The visual alert will continue until the train passes the junction or the route drops out following a time out. | |||
=Additional Tools= | =Additional Tools= | ||
| Line 75: | Line 83: | ||
At configured locations, a train approach bell will sound. | At configured locations, a train approach bell will sound. | ||
For example the image below captures the train approach indication for 6M56 striking | For example the image below captures the train approach indication for 6M56 striking a pre-determined point on approach to Clapham Jn. The booked time is also displayed. | ||
::[[File: approach.png|400px]] | ::[[File: approach.png|400px]] | ||
| Line 83: | Line 91: | ||
At configured locations, a TRTS indication is displayed when the TRTS button is pushed. | At configured locations, a TRTS indication is displayed when the TRTS button is pushed. | ||
For example, the image below indicates the TRTS has been pushed on Platform 3 at | For example, the image below indicates the TRTS has been pushed on Platform 3 at St Pancras. | ||
::[[File: asist-trts.png|450px]] | ::[[File: asist-trts.png|450px]] | ||
Latest revision as of 14:33, 15 March 2021
The aSIST Wrong Route Tool displays the headcode of the approaching train at preconfigured junctions along with its planned route.
In the event of a wrong route, the tool will generate both an audible and visual alarm.
The Wrong Route Tool can also be configured to include train approach alarms, crossing approach alarms, and a TRTS indication.
Data Feed[edit]
aSIST runs off of the plan contained within acumen.
The plan begins as the long term plan CIF file which is then updated with short term plan incremental CIFs.
On the day of operation, VSTPs are processed alongside other updates through TRUST (e.g. cancellations) and received through external sources such as DARWIN/CIS.
Initial Screen[edit]
Users are initially presented with the following screen.
To start the tool, click on the screen.
Note: The tool will remain open and running unless there is a connection failure such as a computer restart. Only on these occasions would the initial screen be seen.
Standard View[edit]
System Health[edit]
The bottom half of the interface includes a number of indicators of system health.
- The blinking dot next to SERVER LINK CONNECTED confirms the tool is connected to the server. If the dot is static then the server connection has been lost.
- The TD Lag indicates how old the data is. There should be minimal lag between a message being sent and then displayed within aSIST. The TD lag will typically be within 10 seconds.
- The Last Update displays the time the most recent data was received. This will most commonly update every 1-2 seconds.
If the system health indicators are not updating as expected, please see aSIST Support.
Routing Display[edit]
The Wrong Route Tool can display up to six different junctions.
Each junction is confined to its own box. For example, below is the display for Bricklayers Arms.
The tool displays the headcode of the next train approaching the junction.
A black arrow indicates the planned route or direction of that train.
When the arrow is green, this means the route set is the same as the planned route; a correctly routed train.
If the route set is not the same as the planned route, an audible and visual warning is displayed. An example is seen below in the Wrong Route Set section.
A question mark will be displayed if aSIST has been unable to match a schedule or it is an unplanned service:
If multiple headcodes are displaying as unmatched, there may be an issue with the timetable information. Please see aSIST Support.
Below the arrow is the mute status. When clicked, the mute button will turn pink and show 'Muted' for 60 minutes, or until it is clicked again, whichever is sooner (for example during perturbation when several trains are being diverted). Whilst muted the system will not produce any audible alerts on the selected signal, but will still show a visual alert.
Note: The other boxes below the arrow and headcode have been reserved for additional functionality.
Wrong Route Set[edit]
If a wrong route is set an audible and visual alarm is generated.
The audible alarm reads the name of the signal at the junction.
In the example below, 9C21 has been incorrectly routed at Sydenham Junction.
The arrow has turned red to show this is incorrect and the headcode is also flashing red.
Note: The arrow will always point in the intended direction.
The audible alarm will sound once. The visual alert will continue until the train passes the junction or the route drops out following a time out.
Additional Tools[edit]
Train Approach[edit]
At configured locations, a train approach bell will sound.
For example the image below captures the train approach indication for 6M56 striking a pre-determined point on approach to Clapham Jn. The booked time is also displayed.
TRTS[edit]
At configured locations, a TRTS indication is displayed when the TRTS button is pushed.
For example, the image below indicates the TRTS has been pushed on Platform 3 at St Pancras.
