Context Menu - Replan Functionality

Right-clicking on a forecast schedule reveals the context menu:

Note: If accessing acumen via a mobile device, a right-click is achieved with a ‘long press’.

View Schedule Details

Clicking on View Schedule Details opens the Train Details View, in the same manner that a left click on the forecast schedule performs.

Replan Service

Clicking on Replan Service opens the Train Service Replan dialog:

This dialog provides users with the options and ability to:

• Change the platform of a train;
• Amend the arrival and/or departure times;
• Convert Call to Pass or vice versa.

Clicking Update commits any changes, clicking Close cancels any changes and closes the dialog.

Points to note:

• Users will receive a warning if the arrival and departure times (for a calling service) do not meet the minimum dwell time, as specified in the respective services schedule.

• When a platform change has been submitted and processed by acumen, and the change results in the service being planned to call at a platform other than that specified in the schedule, a Platform Change Icon will be rendered on the train plot; when hovered over, the tool-tip states the details of the planned platform.

• If a platform is changed for a terminating or joining service, any associated services will automatically be replatformed to match.

Notify Train Crew Issue

Clicking this option indicates to all users that the departure of a service from the docker location is/will be delayed due to a train crew issue (or other operational reason).

Once applied, the relevant service plot is decorated with a corresponding notification icon; hovering over the icon reveals a tool-tip with information on the icon meaning

When applying a train crew issue, the user has the option to amend the expected departure time of the train within that same action.

The train crew icon can be removed by again clicking on the Notify Train Crew Issue option of the context menu.

Suppress Service from Docker

A user has the option to suppress a service from the platform docker, meaning it will no longer be rendered or considered when calculating the forecast or conflicts.

For circular trains (services that are timetabled at the docker location multiple times), the user can choose to suppress a specific instance of passing/calling.

An example user case would be where an orphaned train is not going to run because there is no incoming stock and where the service has not yet been cancelled in TRUST.

Note: Within acumen, every service schedule expires and therefore will not be plotted, 2 hours after the expected time of arrival at destination regardless of suppression.

If suppression results in all instances being suppressed and therefore the service is not plotted on the docker view, users can search for the service either in the Global Search tab or the Forecast Search.

Locations where the service is suppressed are decorated with an icon (red S); clicking on this icon removes the suppression at that location and timetable instance:

Note: A suppressed service is automatically unsuppressed when a movement report is received.

Amend Association

Clicking Amend Association opens the Association Editor; below is an example that shows that the selected ‘base’ train 2K37 has an active ‘Next Working’ association at Crewe with 5K49. (This rendering in Platform 1 can also be seen to the left of the screenshot):

To remove an association, a user clicks on the [x] in the grey box in the right hand column of the associations list.

Note: Where an association has been deleted, conflicts will be raised against the affected services.

Associations are made by selecting the Base Train and Association Trains:

Clicking the This Train button fills in the headcode field with the train that was initially selected; in our example 2K37. It also populates the UID box to the right hand side. It is important to check the Time field to ensure the correct instance of the train’s service has been populated. This is most applicable for circular trains.

The association type options are Next Working, Split and Join. Once submitted, the association is displayed in the Association Editor box, and an association line is drawn between the services on the platform docker.

Note: The association line is rendered the same regardless of the type of association.