Conflict Detection

acumen identifies and raises potential conflicts to the user. This prompts the user to investigate and where possible resolve the conflict before it creates a performance impact.

Types of Conflict

The different types of conflict are as follows:

Conflict Type	Description
OC	An Occupation Conflict will be raised when the platform docker detects two or more trains that are forecast to occupy the same platform for an overlapping period of time. This includes reoccupation time.
IR	An Infrastructure Restriction conflict is raised when a train is forecast to occupy a restricted platform within the times set for that restriction.
SC	A Station Crossing conflict is raised when the routes into or out of the station of two or more trains are forecast to clash. Note: Only applicable to York, Crewe and Birmingham New St. at this time.
MA	A Missing Association conflict is raised when acumen cannot find the association for a service, i.e. one has not been planned.
BA	A Broken Association conflict is raised when the planned association cannot be identified.
SA	A Split Association conflict is raised when the associated services are split across different platforms, i.e. the stock can not physically form the next service.
TRN	A Train Running Restriction Note conflict is raised when a user has included a note in the process of applying a train running restriction.
TRP	A Train Running Restriction Platform conflict is raised when a train is forecast to occupy a platform that it should be avoiding, as per the restriction applied to the train.
TRS	A Train Running Restriction Side conflict is raised when a train is forecast to occupy a platform where passengers alight on a side (e.g. left) that a restriction is in place for.

Conflict Identification

When a conflict is identified a yellow (C) appears next to the headcode. When hovered over, a tool-tip describes the type of conflict and the headcodes affected.

Note: If a Station Crossing conflict has been identified a red (X) is displayed in place of the yellow (C). The tool-tip states the headcodes involved and the junction at which the clash is forecast.

The yellow triangular conflict marker shows how many conflicts have been identified in that platform. This includes conflicts past the initial timeframe that a user can see at a glance. Clicking on the conflict marker jumps down to the next conflict in that platform and highlights the affected train.

Platform occupancy conflicts are represented by a red dashed box. The box indicates the time period in which the trains are forecast to be in conflict. Again, a user can hover within this box to raise the tool-tip which describes the type of conflict and the trains involved.

Users may wish to resolve the conflict by re-platforming a service.

Note: There is an edge-case whereby the rendering of the second train completely covers the first train and in this case the right-click context menu cannot be accessed for the first train. In this circumstance the user may make use of the TBC column by re-platforming the second train out of the way temporarily, to then re-platform the first train.

Suppressing a Conflict

To suppress an individual conflict via the docker, right-click on the yellow (C). A pop-up box will ask you to confirm the action. Click Yes to suppress.

Note: Users are unable to suppress OC occupation conflicts or SC station crossing conflicts due to their transient nature.

Warning: The suppression acts globally so will suppress the conflict for all users.

The option is provided to turn off this pop-up box via the Docker Viewing Preferences cog icon. If this option is selected, users should be aware that a conflict will be suppressed with the right-click alone.

If there is more than one conflict raised against a particular train, it is not possible to suppress via a right-click. Users will instead need to suppress the conflict via the Conflict List.

Conflicts can also be suppressed via the Conflict List by clicking in the Suppression Status column.

For more information see Platform Docker Tabs#Conflict List.