Platform Docker Tabs: Difference between revisions

From acumen Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 26: Line 26:
= TD =
= TD =


The TD tab displays a track schematic showing train describer berth descriptions and where configured, signal state (on/off), TRTS indication and routes set information:   
The '''TD tab''' displays a track schematic showing ''train describer berth descriptions'' and where configured, ''signal state (on/off)'', ''Train Ready to Start (TRTS) indication'' and ''routes set'' information:   


::[[File:TD_TRTS.png|650px]]
::[[File:TD_TRTS.png|650px]]
Line 32: Line 32:
Users can click on the headcodes to view details about the train:
Users can click on the headcodes to view details about the train:


::*white coloured headcodes are forecast services and clicking opens the <b>Train Details View</b>;
::*'''white coloured''' headcodes are forecast services and clicking opens the <b>Train Details View</b>;


::*headcodes coloured yellow are non-forecast services. Clicking on these services opens the <b>Global Search</b> and inputs the headcode ready for the user to search for the service.
::*headcodes '''coloured yellow''' are non-forecast services. Clicking on these services opens the <b>Global Search</b> and inputs the headcode ready for the user to ''search for the service''.


Users can zoom in and out on the map via the + / - buttons in the top left.
Users can ''zoom in and out'' on the map via the + / - buttons in the top left.


= Global Search =
= Global Search =


The Global Search tab provides similar information to TRUST. A user can search by headcode, Service UID or TIPLOC. The search is global so not limited to docker locations or services.  
The Global Search tab provides information from [https://wiki.openraildata.com/index.php?title=TRUST_vs_Darwin#TRUST TRUST] in a similar interface. A user can search by '''headcode''', Service '''UID''' or '''TIPLOC'''. The search is global and not limited to docker locations or services.


The example below shows a search for EUSTON TIPLOC:
The example below shows a search for <code>EUSTON</code> TIPLOC:


::[[File: global search.png|700px]]
::[[File: global search.png|700px]]
   
   
When searching for a TIPLOC, the result will list all called services. When searching for a headcode or UID, the result will show all headcodes or UIDs regardless of whether the service has been called.
When searching for a ''TIPLOC'', the result will list all called services. When searching for a ''headcode or UID'', the result will show all headcodes or UIDs regardless of whether the service has been called.


Headcodes coloured bright blue are for schedules within the acumen forecast. Clicking on the headcode opens up the <b>[[Train Details View]]</b>.
Headcodes coloured '''bright blue''' are for schedules within the acumen Forecast. Clicking on the headcode opens up the <b>[[Train Details View]]</b>.


Black headcodes represent schedules not within the acumen forecast. Clicking on the headcode opens up basic schedule details. Most of this information is read-only, however the <b>Off Route Train Call</b> drop down at the bottom of the page allows an off-booked route train to be rendered on the platform docker. <i> For more information see the [[User Cases]] </i>.
'''Black''' headcodes represent schedules not within the acumen forecast. Clicking on the headcode opens up Basic Schedule details. Most of this information is read-only, however the <b>Off Route Train Call</b> drop down at the bottom of the page allows an off-booked route train to be rendered on the platform docker. <i> For more information see the [[User Cases]] </i>.


= Map =
= Map =


The Map tab displays trains that are within that platform docker’s forecast, but over a wider area. The colours are aligned with CCF lateness colours and the map can be used to view lateness patterns.  
The '''Map tab''' displays trains that are within that Platform Docker’s forecast, but over a wide geographical area. The colours are aligned with ''CCF lateness colours'' and the map can be used to ''view lateness patterns''.
 
A user can hover over the train plot to bring up a tool-tip displaying the '''headcode''' and '''current location'''. Clicking on the plot opens the [[Train Details View]].


A user can hover over the train plot to bring up a tool-tip displaying the headcode and current location. Clicking on the plot opens the [[Train Details View]].
::[[File: map.png|700px]]
::[[File: map.png|700px]]


= Conflict List =
= Conflict List =


The Conflict List tab lists identified conflicts and displays the headcode, UID, conflict time, type of conflict including tool-tip, conflict description, status of train and suppression status:
The '''Conflict List tab''' lists identified conflicts and displays the ''headcode'', ''UID'', ''conflict time'', ''type of conflict'' including tool-tip, ''conflict description'', ''status of train'' and ''suppression status'':


::[[File: clist.png|border|1000px]]
::[[File: clist.png|border|1000px]]


The table includes column sort and text-string search consistent with other search functions.
The table includes ''column sort'' and ''text-string search'' consistent with other search functions.


The table is static until the user clicks the refresh button located in the top left corner.
The table is '''static''' until the user clicks the '''refresh button''' located in the top left corner.


A user can toggle the suppression status via the <i>Supp. Status</i> column.  
A user can ''toggle the suppression status'' via the <i>Supp. Status</i> column.  


::*A ticked box represents a suppressed service.  
::*A ticked box represents a suppressed service.  
::*<b>N/A</b> is marked against any occupation or crossing conflicts. These cannot be suppressed due to their transient nature.
::*<b>N/A</b> is marked against any occupation or crossing conflicts. ''These cannot be suppressed due to their transient nature.''


A user can click on the headcode to open the [[Train Details View]].
A user can click on the '''headcode''' to open the [[Train Details View]].


= Connection Editor =
= Connection Editor =


In acumen parlance, a connection is considered to be a relationship between a pair of trains for an operational purpose - such as passenger connections or train crew swap and should not be confused with an association.
In acumen, a '''connection''' is considered to be a relationship between a pair of trains for an operational purpose e.g. passenger connections or train crew swap, and should '''not''' be confused with an ''association''.


The Connection Editor lists existing connections and allows a user to set and/or delete a connection between train service pairs:
The '''Connection Editor''' ''lists existing connections'' and allows a user to ''set and/or delete a connection'' between train service pairs:


::[[File: connection editor.png|border|800px]]
::[[File: connection editor.png|border|800px]]


To create a connection, the user selects the first and second services to be connected, ensuring the correct instance of the platform docker location has been selected via the time field, in the event that the service is circular.
To '''create''' a connection, the user selects the first and second services to be connected, ensuring the correct instance of the Platform Docker location has been selected via the time field, in the event that the service is circular.
   
   
Once submitted, the connection populates the list.
Once submitted, the connection populates the list.


To delete a connection, the user clicks on the button next to the relevant item in the Connection Editor.
To '''delete''' a connection, the user clicks on the button next to the relevant item in the Connection Editor.
   
   
On the platform docker, a yellow line joins the connected services:
On the platform docker, a '''yellow line''' joins the connected services:


::[[File: connection.png|150px]]
::[[File: connection.png|150px]]
Line 96: Line 97:
= Alert List =
= Alert List =


The Alert List tab provides a list of all re-plan changes made by acumen users, automatically undertaken by the acumen forecast service, or received from other sources such as DARWIN.
The '''Alert List tab''' provides a list of all ''re-plan changes'' made by acumen users, automatically undertaken by the acumen Forecasting service, or received from other sources such as DARWIN.


It also provides a warning if a re-plan action has not been actioned.  
It also provides a warning if a re-plan action has ''not been actioned''.  


Items will remain in the list for 60 minutes.
Items will remain in the list for 60 minutes.
Line 106: Line 107:
= Restrictions =
= Restrictions =


The Restrictions tab lists current train running and infrastructure restrictions.
The '''Restrictions tab''' lists current ''train running'' and ''infrastructure restrictions''.
   
   
To delete either a train running or infrastructure restriction, click on the <b>[x]</b> in the grey box next to the relevant entry.
To '''delete''' either a train running or infrastructure restriction, click on the <b>[x]</b> in the grey box next to the relevant entry.


To edit an infrastructure restriction, click on the pen icon next to the relevant entry:
To '''edit''' an infrastructure restriction, click on the pen icon next to the relevant entry:


::[[File: restriction.png|800px]]
::[[File: restriction.png|800px]]


<b>Note:</b> Where an infrastructure restriction affects multiple platforms and this has been entered in one action, each platform/line is listed separately in the Restrictions tab to enable edits to be made to individual platforms/lines.
<b>Note:</b> ''Where an infrastructure restriction affects multiple platforms and this has been entered in one action, each platform/line is listed separately in the Restrictions tab to enable edits to be made to individual platforms/lines.''


= Advance Train Plan =
= Advance Train Plan =
Line 120: Line 121:
<i>Introduced as part of the 20.09 [[Upgrades]]</i>
<i>Introduced as part of the 20.09 [[Upgrades]]</i>


The Advance Train Plan tab enables a user to search for and display the train plan for a selected 12hr period. This may be useful for ensuring the train plan has been amended around planned engineering works, or to check there are no clashes in the timetable.
The '''Advance Train Plan tab''' enables a user to search for and display the train plan for a selected 12hr period. This may be useful for ensuring the train plan has been amended around planned engineering works, or to check there are no clashes in the timetable.


To select a time period, a user must click on the calendar icon next to the tab title. This opens the dialogue box as seen below.
To select a time period, a user must click on the '''calendar icon''' next to the tab title. This opens the dialogue box as seen below.


::[[File: ATP_3.PNG|650px]]  
::[[File: ATP_3.PNG|650px]]  


A Start Date/Time is then selected.
A ''Start Date/Time'' is then selected.


<b>Note:</b> A user has the option to select a time period weeks or months in advance but should bear in mind the timetable is more likely to be subject to change and may not have short term plans or other changes applied.
<b>Note:</b> A user has the option to select a time period weeks or months in advance but should bear in mind the timetable is more likely to be subject to change and may not have short term plans or other changes applied.


The user can then select Docker View Orientation as either Horizontal or Vertical. It is set to Horizontal by default. (<b>Note: </b> The picture below displays the vertical view).
The user can then select Docker View Orientation as either ''Horizontal or Vertical''. It is set to Horizontal by default. (<b>Note: </b> The picture below displays the vertical view).


Once submitted, the plan for that 12hr period is displayed. (This may take a minute to load due to the number of trains). The plan looks much the same as the Planned Layer on the normal docker view, with the date and time down the side(s) and associations drawn.
Once submitted, the plan for that 12hr period is displayed. (This may take several minutes to load due to the number of trains). The plan looks much the same as the Planned Layer on the normal docker view, with the date and time down the side(s) and associations drawn.


::[[File: ATP_2.PNG|650px]]  
::[[File: ATP_2.PNG|650px]]  


[[Conflict Detection]] is in effect for occupation conflicts (OC) and infrastructure restriction conflicts (IR).
[[Conflict Detection]] detects occupation conflicts (OC) and infrastructure restriction conflicts (IR).


Clicking on the calendar icon again reopens the dialogue box. Any conflicts are listed here in a table. The option is provided to export this table to excel format. Routes may decide to then send this output to Capacity Planning.
Clicking on the calendar icon again reopens the dialogue box. Any conflicts are listed here in a table. The option is provided to export this table to Excel format. Routes may decide to then send this output to Capacity Planning.


::[[File: ATP_1.PNG|650px]]  
::[[File: ATP_1.PNG|650px]]  


<b> Note: </b> The advanced plan remains loaded when a user clicks off on to another tab.
<b> Note: </b> ''The advanced plan remains loaded when a user clicks off on to another tab.''


= CIS =
= CIS =


A CIS tab has been introduced on each docker, displaying a live CIS feed.
'''Note:''' ''this tab is currently not functioning. We welcome user feedback on whether this functionality should be restored.''
 
A '''CIS tab''' has been introduced on each docker, displaying a ''live CIS feed''.


::[[File:New_CIS.png|650px]]
::[[File:New_CIS.png|650px]]
Line 156: Line 159:
<i>Introduced as part of the 21.02 [[Upgrades]]</i>
<i>Introduced as part of the 21.02 [[Upgrades]]</i>


The Internet Relay Chat (IRC) tab is a chat messaging feature, to assist communication between docker users.
'''Note''': ''this tab is currently not functioning. We welcome user feedback on whether this functionality should be restored.''
 
The '''Internet Relay Chat (IRC) tab''' is a chat messaging feature, to assist communication between docker users.


<b>The IRC MUST NOT be used for safety critical communications.</b>
<b>The IRC MUST NOT be used for safety critical communications.</b>
Line 192: Line 197:


<i>Introduced as part of the 21.04.01 [[Upgrades]]</i>
<i>Introduced as part of the 21.04.01 [[Upgrades]]</i>
'''Note:''' ''This functionality has not been available following the conclusion of the project where real-time occupancy data were sourced. This tab is currently not usable.''


<i>Data currently unavailable to populate tab for Crewe and York trial sites.</i>
<i>Data currently unavailable to populate tab for Crewe and York trial sites.</i>

Latest revision as of 11:01, 25 January 2025

This section describes the Platform Docker tabs. It is expected that users will spend most of their time monitoring the platform docker and then seeking out further information via these tabs.

Banner 21.04.png

Since March 2022 the OIM team have been supporting acumen Platform Docker on a best-efforts basis, while awaiting decisions on the future of the acumen suite. We continue to update these pages to keep users informed of any changes.


Platform Docker[edit]

The left-most tab labels the Platform Docker that is in use.

This is followed by four icons:

Pd tab icons.png
These icons function as follows:
  • The circled arrow enables the user to switch between horizontal and vertical views;
  • The triangle enables a user to expand and retract the platform and line index;
  • The cog icon enables the user to edit the docker viewing preferences. Switching these on makes these icons/markers visible on the Platform Docker:
DVP dec.png
  • And finally, the paint pot icon opens the colour legend - this opens a modal that details the color scheme used within acumen and guides users to the meaning of UI elements used within the application. Please be aware that not all UI elements are currently reported in the legend.

TD[edit]

The TD tab displays a track schematic showing train describer berth descriptions and where configured, signal state (on/off), Train Ready to Start (TRTS) indication and routes set information:

TD TRTS.png

Users can click on the headcodes to view details about the train:

  • white coloured headcodes are forecast services and clicking opens the Train Details View;
  • headcodes coloured yellow are non-forecast services. Clicking on these services opens the Global Search and inputs the headcode ready for the user to search for the service.

Users can zoom in and out on the map via the + / - buttons in the top left.

Global Search[edit]

The Global Search tab provides information from TRUST in a similar interface. A user can search by headcode, Service UID or TIPLOC. The search is global and not limited to docker locations or services.

The example below shows a search for EUSTON TIPLOC:

Global search.png

When searching for a TIPLOC, the result will list all called services. When searching for a headcode or UID, the result will show all headcodes or UIDs regardless of whether the service has been called.

Headcodes coloured bright blue are for schedules within the acumen Forecast. Clicking on the headcode opens up the Train Details View.

Black headcodes represent schedules not within the acumen forecast. Clicking on the headcode opens up Basic Schedule details. Most of this information is read-only, however the Off Route Train Call drop down at the bottom of the page allows an off-booked route train to be rendered on the platform docker. For more information see the User Cases .

Map[edit]

The Map tab displays trains that are within that Platform Docker’s forecast, but over a wide geographical area. The colours are aligned with CCF lateness colours and the map can be used to view lateness patterns.

A user can hover over the train plot to bring up a tool-tip displaying the headcode and current location. Clicking on the plot opens the Train Details View.

Map.png

Conflict List[edit]

The Conflict List tab lists identified conflicts and displays the headcode, UID, conflict time, type of conflict including tool-tip, conflict description, status of train and suppression status:

Clist.png

The table includes column sort and text-string search consistent with other search functions.

The table is static until the user clicks the refresh button located in the top left corner.

A user can toggle the suppression status via the Supp. Status column.

  • A ticked box represents a suppressed service.
  • N/A is marked against any occupation or crossing conflicts. These cannot be suppressed due to their transient nature.

A user can click on the headcode to open the Train Details View.

Connection Editor[edit]

In acumen, a connection is considered to be a relationship between a pair of trains for an operational purpose e.g. passenger connections or train crew swap, and should not be confused with an association.

The Connection Editor lists existing connections and allows a user to set and/or delete a connection between train service pairs:

Connection editor.png

To create a connection, the user selects the first and second services to be connected, ensuring the correct instance of the Platform Docker location has been selected via the time field, in the event that the service is circular.

Once submitted, the connection populates the list.

To delete a connection, the user clicks on the button next to the relevant item in the Connection Editor.

On the platform docker, a yellow line joins the connected services:

Connection.png

Alert List[edit]

The Alert List tab provides a list of all re-plan changes made by acumen users, automatically undertaken by the acumen Forecasting service, or received from other sources such as DARWIN.

It also provides a warning if a re-plan action has not been actioned.

Items will remain in the list for 60 minutes.

Alerts List.png

Restrictions[edit]

The Restrictions tab lists current train running and infrastructure restrictions.

To delete either a train running or infrastructure restriction, click on the [x] in the grey box next to the relevant entry.

To edit an infrastructure restriction, click on the pen icon next to the relevant entry:

Restriction.png

Note: Where an infrastructure restriction affects multiple platforms and this has been entered in one action, each platform/line is listed separately in the Restrictions tab to enable edits to be made to individual platforms/lines.

Advance Train Plan[edit]

Introduced as part of the 20.09 Upgrades

The Advance Train Plan tab enables a user to search for and display the train plan for a selected 12hr period. This may be useful for ensuring the train plan has been amended around planned engineering works, or to check there are no clashes in the timetable.

To select a time period, a user must click on the calendar icon next to the tab title. This opens the dialogue box as seen below.

ATP 3.PNG

A Start Date/Time is then selected.

Note: A user has the option to select a time period weeks or months in advance but should bear in mind the timetable is more likely to be subject to change and may not have short term plans or other changes applied.

The user can then select Docker View Orientation as either Horizontal or Vertical. It is set to Horizontal by default. (Note: The picture below displays the vertical view).

Once submitted, the plan for that 12hr period is displayed. (This may take several minutes to load due to the number of trains). The plan looks much the same as the Planned Layer on the normal docker view, with the date and time down the side(s) and associations drawn.

ATP 2.PNG

Conflict Detection detects occupation conflicts (OC) and infrastructure restriction conflicts (IR).

Clicking on the calendar icon again reopens the dialogue box. Any conflicts are listed here in a table. The option is provided to export this table to Excel format. Routes may decide to then send this output to Capacity Planning.

ATP 1.PNG

Note: The advanced plan remains loaded when a user clicks off on to another tab.

CIS[edit]

Note: this tab is currently not functioning. We welcome user feedback on whether this functionality should be restored.

A CIS tab has been introduced on each docker, displaying a live CIS feed.

New CIS.png

For trains not terminating at the docker location, users can hover over the destination TIPLOC to see a list of calling points for that train.

IRC[edit]

Introduced as part of the 21.02 Upgrades

Note: this tab is currently not functioning. We welcome user feedback on whether this functionality should be restored.

The Internet Relay Chat (IRC) tab is a chat messaging feature, to assist communication between docker users.

The IRC MUST NOT be used for safety critical communications.

A Nick(name) is generated based on the user role.

The Channel defaults to the docker location. A #General channel is also available.

IRC Signaller.png

To send a message in the chat, type next to your username at the bottom of the screen.


The left-hand banner lists the channels you as a user have access to. This would typically be the #General channel and the docker-specific channel e.g. #KingsCross.

A channel with a particular user can be created by selecting their username and clicking the Send a message button that appears in the right-hand pane.

Message.png

If the recipient is on a different tab when the message is sent, then a yellow (!) will appear on the IRC tab to represent unread messages.

IRC alert.png

An audible alert will also sound for the first message.

It is recommended acumen users respond to the message to acknowledge receipt.

The IRC has been introduced to help signalling teams understand which station roles are active on acumen and vice versa. To support this, users can choose to set their status as Away. To do this, click on the arrow next to your nickname at the bottom of the screen, and select Away. Your status indication will turn red.

Away.png

Clicking on the people icon in the top right shows what users are active within the chat.

Station[edit]

Introduced as part of the 21.04.01 Upgrades

Note: This functionality has not been available following the conclusion of the project where real-time occupancy data were sourced. This tab is currently not usable.

Data currently unavailable to populate tab for Crewe and York trial sites.

The Station tab provides information about station occupancy, and lift and escalator status where this information is available.

This occupancy data is based on mobile phone location data.

As seen in the screenshot below, station occupancy is plotted on a graph. This updates every 90s.

Area demand predicts which services the passengers in a station will board. These figures update every 5 mins.

Station tab.png

The lift and escalator status is obtained from a Network Rail feed and gives the status of a lift or escalator as either available, not available (out of order) or unknown (failure with the remote condition monitoring).