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 dialogue:

This dialog provides users with the option 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

A user can indicate that a train is awaiting train crew. When applied, a purple T icon appears on the train. A tool-tip is available to describe the note.

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 the same right-click 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. For circular trains the user can choose to suppress a specific instance of that train. Example user case: orphaned train not going to run as no incoming stock however the service hasn’t been cancelled in TRUST. Nb. Every service has a two hour expiry time so will automatically disappear from the platform docker two hours after the planned (or actual) destination arrival time.

Once suppressed, the schedule can still be found if searched for. A red S is displayed next to the platform docker location in the train’s schedule as seen below.

If a user wants to reinstate a suppressed service, they click on the red S and commit the action. A tool-tip informs the user of this. Nb. A service will automatically unsuppress if a movement report is received. (If the reports received are off-route then the service remains suppressed).

Amend Association

Clicking Amend Association opens the Association Editor. Below is an example: it 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.

When an association has been deleted, conflicts will be raised on the affected services.

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

Clicking the ‘This Train’ grey 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’s 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. Nb. The association line looks the same regardless of the type of association.