Skip to main content

Visualizing and solving conflicts

Here you'll learn how dependency conflicts in specter are detected, displayed, and resolved.

Written by Niklas Beese

In this article, we'll show you:

  • How to recognize that a dependency conflict has occurred

  • How to switch to conflict mode and view all conflicts

  • How to resolve a conflict via the conflict card

  • How to display, filter, and color conflicts in the 3D model

Video: Dependency conflicts in specter

Timestamps
​0:33 – Viewing conflict details with a click
​0:48 – Conflict due to minimum distance
​1:12 – Conflict indicator and opening conflict mode
​1:20 – Conflict list in the sidebar
​1:41 – Color coding of task cards
​2:17 – Conflict cards in detail
​2:56 – Resolving a conflict
​3:36 – Impact on the critical path
​4:17 – Displaying, filtering, and coloring conflicts in the 3D model

Recognizing a dependency conflict

If a dependency between two tasks isn't maintained – for example because a task starts too late or a minimum distance isn't reached – a conflict occurs. The affected dependency arrow is shown in red and directly indicates how many days you're short of the required distance.

Opening conflict mode

At the top of the Planner, an indicator shows you how many conflicts currently exist. It takes you into conflict mode.

Here's how:

  1. Click the conflict indicator at the top of the Planner.

  2. Conflict mode opens – a list with all current conflicts appears on the right.

Hovering your mouse over an entry in the list directly shows you where in the plan this conflict is located.

Once conflict mode is active, the coloring of the task cards adjusts:

  • Green: no conflict

  • Red: direct conflict

  • Yellow: downstream affected – successor tasks that could be affected by the conflict

Expanding a conflict card shows you how many tasks are affected by this conflict – for example one directly following task, or a whole chain of further tasks.

Using the Resolve button on the conflict card, you can resolve the conflict directly. specter then shifts the affected task back by the missing days. Tasks that aren't directly part of the chain remain unchanged.

If resolving a conflict affects several tasks in sequence, a new critical path emerges: the chain of tasks that ends up delayed as a whole shows you by how many days your project shifts overall.

Displaying conflicts in the 3D model

Dependency conflicts can also be visualized directly in the 3D model.

Here's how:

  1. Enable the display for dependency conflicts in the model.

  2. By default, all current conflicts are shown simultaneously – but you can also display individual conflicts specifically, to click through them quickly.

  3. Optionally filter to just the affected objects or to the critical path.

You can also filter or color by individual dependency conflicts.

Did this answer your question?