Conflict Detection

Conflict Detection

Types of Conflict

The types of conflict identified by acumen are listed in Table 4. This includes the abbreviation used in the Conflict List tab. Conflict Type Abbreviation Occupation Conflict OC Infrastructure Restriction IR Missing Association MA Broken Association BA Split Association SA Train Running Restriction Note TRN Train Running Restriction Platform TRP Train Running Restriction Side TRS

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.

An Infrastructure Restriction conflict is raised when a train is forecast to occupy a restricted platform within the times set for that restriction.

A Missing Association conflict is raised when acumen cannot find the association for a service, i.e. one has not been planned.

A Broken Association conflict is raised when the planned association cannot be identified.

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.

A Train Running Restriction Note conflict is raised when a user has included a note in the process of applying a train running restriction.

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.

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, as shown in Figure 55, Figure 56 and Figure 57.

The yellow triangular conflict marker shows how many conflicts have been identified in that platform. This includes conflicts past the 20min 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, as shown in Figure 58.

Platform occupancy conflicts are represented by a red dashed box. The box indicates the time between which the conflict occurs, therefore this borders the second (and third+ where applicable) train. Again, a user can hover within this box to raise the tool-tip which describes the type of conflict and the trains involved.

When a user left-clicks within this dashed box the Train Service Replan dialogue pops up enabling the user to change the platform and/or arrival and departure times of that train. Nb. To open the Train Details View as is normal with a left-click, then hold down ctrl + left click.

If the user instead wishes to re-platform the first train, they can right-click and select Replan Service from the context menu as described in Section 8.2. Nb. 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.

Further details about the conflict are included within the Conflict List tab. See Section 4.5. Once a conflict is resolved e.g. by undertaking a platform change, the conflict will drop off the list.