Guides
Date slips → taking corrective action
When a task or milestone slips, adjust the dates and have the optimizer recalculate the plan.
The schedule reflects the new situation. Dependent tasks, milestones, gates and resource bookings fit together again.
Who is involved
Section titled “Who is involved”- Project manager – evaluates the slip and takes corrective action.
- Employees/operatives – report status and actual dates of their tasks.
- Admin – starts the optimization and applies the result.
Prerequisites
Section titled “Prerequisites”- Tasks, milestones and gates are connected via dependencies (see Building & optimizing the work plan).
The workflow
Section titled “The workflow”- Understand dependencies. A dependency connects the start or end of one element with the start or end of another. There are four types: end → start, start → start, end → end and start → end. The optimizer respects all four.
- In the early phases. Up to „Planung“ (Planning) you move bars in the Gantt of the Work area directly. Successors do not move along automatically. Only the optimizer brings the plan back into line.
- From „Umsetzung“ (Execution) onward: maintain the facts. The Gantt is then read-only. Instead, change the task. You set the status, for example „In Bearbeitung“ (In progress) or „Erledigt“ (Done). You also maintain „Tatsächlicher Start“ (Actual start) and „Tatsächliches Ende“ (Actual end). Under „Zeitfenster (Optimierer)“ (Time window (optimizer)) you define „Nicht vor“ (Not before), „Nicht nach“ (Not after) and a „Grund der Einschränkung“ (Reason for the restriction). Milestones and gates have „Geplant am“ (Planned on), „Nicht vor“ and „Nicht nach“.
- Recalculate. The „Projekt-Optimierung“ (Project optimization) plans from the current state. Completed tasks are left out; their end constrains the successors. Running tasks are not rescheduled before their start. With „Fixieren…“ (Fix…) you pin individual start dates.
- Apply. „Übernehmen“ (Apply) commits the new dates. Milestones attached to tasks follow them. Open gates move along; passed gates keep their date. The optimizer’s bookings are created anew. Aligia reports new double bookings instead of aborting.
- Check the consequences. In the Resource workload you see conflicts such as „Doppelbuchung“ (Double booking). In the next status report you assess the „Arbeitsplan“ (Work plan) area and justify the slip.
Result
Section titled “Result”An updated schedule that respects dependencies, with matching resource bookings and a documented assessment in the status report.
See also
Section titled “See also”Gantt · Work area · Gate decision & phase change · Resolving a resource conflict