Signaller Briefing: Difference between revisions
(Created page with "This briefing note has been created for the benefit of signallers viewing the Birmingham New Street platform docker. The information contained will help signallers understand...") |
No edit summary |
||
| Line 1: | Line 1: | ||
This briefing note has been created for the benefit of signallers viewing the Birmingham New Street platform docker. | This briefing note has been created for the benefit of signallers viewing the Birmingham New Street platform docker. | ||
The information contained will help signallers understand what the docker is | The information contained will help signallers understand what information the docker is displaying, and how it can support decision-making. | ||
Signallers are not expected to interact with the docker in terms of undertaking any re-plan changes, however they are welcome to navigate around the system. There will be links within this briefing note to other pages within the online acumen [[User Guide]] to support situational awareness. | Signallers are not expected to interact with the docker in terms of undertaking any re-plan changes, however they are welcome to navigate around the system. There will be links within this briefing note to other pages within the online acumen [[User Guide]] to support situational awareness. | ||
= Background = | |||
The acumen platform docker has been deployed to both signalling and station teams at Birmingham New St to assist with platform management. | |||
The docker is a visual display of actual platform occupation and forecast platform occupation. | |||
acumen identifies conflicts (e.g. platform clashes) and notifies of changes to the plan (e.g. platform alterations). | |||
The intention is that acumen will provide a common operational picture, and enable conflicts to be identified and resolved in good time, therefore reducing late-notice platform changes, reducing the time trains spend outside the station awaiting a platform, and improving decision-making times. | |||
= What feeds the platform docker? = | = What feeds the platform docker? = | ||
acumen is an Operational Decision Support Tool (ODST). It subscribes to various data feeds to receive messages, but does not publish any messages out. | |||
acumen receives the Long Term Plan via the CIF, and then receives daily incremental CIF updates with Short Term Plan changes. | |||
On the day of operation, acumen will receive VSTPs, messages from TRUST (e.g. cancellations), platform changes and train length/consist information from DARWIN, and updates from TIGER (LICC feed). | |||
acumen also subscribes to train movement reports. This informs the forecast and measures how a train is running to time. | |||
More information about data feeds can be found on the [[Data Feeds]] page here. | |||
acumen does not publish any messages. This means changes made in acumen will be seen by other acumen users but will not feed through to other systems such as CIS. | |||
= Interpreting the docker interface = | = Interpreting the docker interface = | ||
acumen can be viewed in either the horizontal view or vertical view. The functionality is the same across both views. More information here: [[User Cases##Horizontal and Vertical Views]]. | |||
<i>The rest of this briefing note is written for the vertical view configuration.</i> | |||
A <b>TBC</b> 'platform' is included in addition to the numbered platforms. This is where trains without platform information will be rendered, for example VSTPs. | |||
The blue line indicates current time. Therefore everything above the timeline (horizontal view: to the left of) is actual/historic data and everything below the timeline (horizontal view: to the right of) is forecast data. There is approximately 5mins of historic data displayed and 4hrs of forecast data. | |||
Trains are represented by boxes with the length of the box (horizontal view: width) representing the platform occupation time. Sub-platforms have been catered for at Birmingham so the width of the box (horizontal view: height) represents whether the train is forecast for the full-length platform or a sub platform. | |||
The colours of the trains represent lateness and are aligned to CCF as much as possible. A white train represents an overdue report. Typically these revert to a block colour within 30s when the next movement report is received. | |||
= Other interfaces = | = Other interfaces = | ||
Revision as of 10:59, 3 March 2021
This briefing note has been created for the benefit of signallers viewing the Birmingham New Street platform docker.
The information contained will help signallers understand what information the docker is displaying, and how it can support decision-making.
Signallers are not expected to interact with the docker in terms of undertaking any re-plan changes, however they are welcome to navigate around the system. There will be links within this briefing note to other pages within the online acumen User Guide to support situational awareness.
Background
The acumen platform docker has been deployed to both signalling and station teams at Birmingham New St to assist with platform management.
The docker is a visual display of actual platform occupation and forecast platform occupation.
acumen identifies conflicts (e.g. platform clashes) and notifies of changes to the plan (e.g. platform alterations).
The intention is that acumen will provide a common operational picture, and enable conflicts to be identified and resolved in good time, therefore reducing late-notice platform changes, reducing the time trains spend outside the station awaiting a platform, and improving decision-making times.
What feeds the platform docker?
acumen is an Operational Decision Support Tool (ODST). It subscribes to various data feeds to receive messages, but does not publish any messages out.
acumen receives the Long Term Plan via the CIF, and then receives daily incremental CIF updates with Short Term Plan changes.
On the day of operation, acumen will receive VSTPs, messages from TRUST (e.g. cancellations), platform changes and train length/consist information from DARWIN, and updates from TIGER (LICC feed).
acumen also subscribes to train movement reports. This informs the forecast and measures how a train is running to time.
More information about data feeds can be found on the Data Feeds page here.
acumen does not publish any messages. This means changes made in acumen will be seen by other acumen users but will not feed through to other systems such as CIS.
Interpreting the docker interface
acumen can be viewed in either the horizontal view or vertical view. The functionality is the same across both views. More information here: User Cases##Horizontal and Vertical Views.
The rest of this briefing note is written for the vertical view configuration.
A TBC 'platform' is included in addition to the numbered platforms. This is where trains without platform information will be rendered, for example VSTPs.
The blue line indicates current time. Therefore everything above the timeline (horizontal view: to the left of) is actual/historic data and everything below the timeline (horizontal view: to the right of) is forecast data. There is approximately 5mins of historic data displayed and 4hrs of forecast data.
Trains are represented by boxes with the length of the box (horizontal view: width) representing the platform occupation time. Sub-platforms have been catered for at Birmingham so the width of the box (horizontal view: height) represents whether the train is forecast for the full-length platform or a sub platform.
The colours of the trains represent lateness and are aligned to CCF as much as possible. A white train represents an overdue report. Typically these revert to a block colour within 30s when the next movement report is received.