In the planning phase, dependencies between processes are used to represent logical, structural, logistic and other necessary links. In lcmd you can identify linked process chains and rapidly resolve conflicts resulting from rescheduling.
A conflict between two processes or milestones arises when a dependency is not met. In lcmd there are various options for displaying or resolving these conflicts. So that you can decide for yourself how a collision should be resolved, lcmd itself does not move any processes, but shows you what options you have.
Display of conflicts
If there is a conflict, this is displayed in lcmd in each view with a red frame around the processes concerned.
In addition to this display, there is also the conflict view and the conflict mode for a more detailed view of conflicts. These are explained below.
Conflict View
- Switch to the “Conflicts” view under the “Eye” symbol at the top right to get an overview of the status of your rescheduling.
- Select a process to highlight the associated linked process chain.
Green symbolizes no need for action, as there is no conflict here. Processes that are affected by the shift are colored yellow and the direct conflict in red.
Display overlapping dependencies
- The number in the circle on each process in the conflict view shows how many days the original dependency has been exceeded and therefore by how many days individual processes would have to be postponed in order to restore the original dependency and thus resolve the conflict.
Resolving conflicts
To resolve a conflict, you can either move the affected processes and milestones manually or have them resolved automatically with the help of lcmd.
Manual conflict resolution
- Delete the dependencies for processes manually or change the offset of the dependency by editing the process details.
- Alternatively, you can move, change and shorten the processes manually so that there is no longer a conflict.
- You can also undo the changes or manually move processes with overruns.
Conflict mode - resolve conflicts automatically
- If you select a red process, the red “Conflicts detected” button appears at the top center of the process plan.
- If you click on the “Conflict detected” button, the conflict mode opens.
- In conflict mode, all unaffected processes are displayed transparently. If required, select the focus view for an isolated display of the conflict.
- You now have two options for resolving the conflict automatically:
- Adapt dependency to current situation to adapt the dependency highlighted in yellow in the details according to the situation. In the example from EA+0d to EA-1d. In this case, you allow the two processes to overlap by one day, as they can take place in parallel.
- Alternatively, click Resolve conflict to move the affected processes to the back according to the situation.
Of course, you can also combine the various manual and automatic conflict resolution options.
Tags: Abhängigkeit, Verknüpfung, Konflikt, Kollision, auflösen, Konfliktmodus, Konfliktansicht, Störung,