Reference & Data Model
Optimization run (optimization_run)
An optimization run is a computed schedule for one or more projects that you can review, commit and roll back again.
Purpose
Section titled “Purpose”The Optimization run (optimization_run) stores one computation of the optimizer: the input (tasks, dependencies, scheduled people with availability, equipment, material demand, calendar), the status and – via the Optimization result (optimization_result) – the solved schedule. For each participating project a Run membership (optimization_run_project) records whether the project was solved, whether and when its result was committed and how many booking conflicts were detected in the process. Only committing writes the schedule into tasks, bookings and procurement. (Planning data; held server-side, not shown as a table in the interface)
Where in the app
Section titled “Where in the app”- Project optimization: the button „Optimierer“ (Optimizer) in the header of the project view opens the window „Projekt-Optimierung“ (Project optimization) for one project; see Guides › Building & optimizing the work plan.
- Portfolio optimization: Portfolio › Strategie, select projects, „Optimieren (n)“ (Optimize (n)) opens „Portfolio-Optimierung“ (Portfolio optimization) for several projects (programs are skipped); see Guides › Scheduling a portfolio with the optimizer.
- Both windows show the views „Zeitplan“ (Schedule), „Projekte“ (Projects), „Ressourcen“ (Resources) and „Material“, the buttons „Neue Optimierung starten“ (Start new optimization) / „Neu berechnen“ (Recompute), „Übernehmen“ (Commit) or „Alle übernehmen“ (Commit all) and the badges „✓ Übernommen“ (Committed) and „Veraltet — neu berechnen“ (Outdated — recompute).
- The rollback runs via the phase change back to an early phase („Optimierung verwerfen?“ › „Trotzdem zurücksetzen“, Discard optimization? › Reset anyway); see Guides › Gate decision & phase change.
Fields
Section titled “Fields”The fields are not shown as a form but evaluated in the windows „Projekt-Optimierung“ / „Portfolio-Optimierung“.
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Status | status |
Selection | yes | State of the computation, see States | System |
| Committed on | committed_at |
Date | no | Time of the commit (single-project run) | System; empty = never committed; badge „✓ Übernommen“ |
| Kind | kind |
Selection | yes | standard (normal run) or scenario (what-if run of an agent) |
System; scenario runs never appear in the optimizer window and cannot be committed |
| Label | label |
Text | no | Short description of a scenario run | System, scenario only |
| Project | project_id |
Reference | no | Project for single-project runs | System |
Run membership (optimization_run_project, one row per run and project):
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Solved | solved |
Yes/No | yes | Project had plannable tasks and is included in the result | System; false → commit refused |
| Committed on | committed_at |
Date | no | Commit of this project from this run | System; badge „✓ Übernommen“ per project |
| Booking conflicts | booking_conflicts |
Number | no | Overlaps with bookings of other runs or manual bookings, detected on commit | System; mentioned in the success message, never blocking |
| Committed scopes | applied_flags |
Selection (multiple) | no | Which scopes were committed (task positions, task dates, employee bookings, equipment bookings, procurement) | System; a repeated commit with the same scopes is refused („already applied — roll back first“) |
| State before commit | pre_commit_snapshot |
– | no | All values that the commit overwrites | System; basis for the rollback |
What a result contains
Section titled “What a result contains”The result (optimization_result.result) is resolved server-side into calendar dates and shown in the window:
| Content | Display |
|---|---|
| Per project: achieved end, desired end, delay (working days), costs | KPIs „Enddatum“ (End date), „Ziel“ (Target), „Verspätung“ / „Termingerecht“ (Delay / On time), „Puffer“ (Buffer), „Kosten“ (Costs), „Gesamtaufwand“ (Total effort), comparison „Aktueller Plan → Optimierter Plan“ (Current plan → Optimized plan; „Dauer“, „Parallelität“, „Zuweisungen“) |
| Per task: start, end, assigned resources (people, unfilled roles, equipment) | „Zeitplan“ (bars, markers „Zieltermin“, „Gate“, „Meilenstein“, „Termin“), chips „verschoben“ (shifted) / „Buchungen“ (bookings) |
| Order proposals (good, quantity, order date, costs) | „Bestellvorschläge“ (Order proposals) with „bestellen bis“ (order by), KPI „davon Bestellungen“ (of which orders); view „Material“ with „Benötigt ab“ (Needed from), „Lücke“ (Gap), „Deckung“ (Coverage), status „Verfügbar“ / „In Beschaffung“ / „Beschaffung nötig“ (Available / In procurement / Procurement needed) |
| Bottlenecks and problems (errors, warnings) | „Engpässe“ (Bottlenecks), „Engpass-Ressourcen“ (Bottleneck resources), „Probleme / Zu beheben“ (Problems / To fix), „Ressourcen-Auslastung“ (Resource workload; heatmap) |
| Position of gates, milestones and events | „Gates, Meilensteine & Termine“, KPIs „Gates gehalten“ (Gates held), „Meilensteine gehalten“ (Milestones held) |
| Solver statistics (computation time, target delay, costs) | „Status“, „Rechenzeit“ (Computation time), „Ziel-Verspätung“ (Target delay), „Kosten (Ziel)“ (Costs (target)) |
| Diagnosis on infeasibility | „Nicht lösbar“ (Not solvable), section „Diagnose“ with „Belegt“ / „Vermutung“ (Proven / Assumption), „Eingabe-Probleme“ (Input problems), „Ohne Fixierungen neu berechnen“ (Recompute without pins) |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
Optimization result (optimization_result) |
has one | no | – | managed server-side |
Run membership (optimization_run_project) |
has many | yes (at least one project) | – | managed server-side |
Project (project) |
n:m via run membership | yes | – | A project with a committed run cannot be deleted; roll back first (restrict, conditional) |
| Employee/equipment booking, procurement request | has many (via optimization_run_id) |
no | – | Rows created by the optimizer carry the run ID; they are replaced on a repeated commit and withdrawn on rollback |
States
Section titled “States”| Value | Label in the interface | Set by |
|---|---|---|
solving |
„Optimierung läuft…“ (Optimization running…) | Start („Neue Optimierung starten“, „Neu berechnen“) |
done |
Result is shown; solver status e.g. „Termingerecht“ / „Verspätung“ | Optimizer worker delivers a solvable result |
infeasible |
„Nicht lösbar“ + „Diagnose“ | Worker finds no feasible plan |
failed |
„Letzter Versuch fehlgeschlagen — angezeigt wird der letzte erfolgreiche Lauf.“ | Error in the workflow |
Start ──▶ solving ──▶ done ──(commit)──▶ committed_at set ──(phase back)──▶ committed_at empty ├──▶ infeasible └──▶ failedA run that stays in status solving unusually long is considered aborted („Letzter Versuch läuft ungewöhnlich lange oder wurde abgebrochen …“). As long as a run is in progress for one of the selected projects, no further run can be started.
Rules & automation
Section titled “Rules & automation”- Start: a run covers 1 to 50 projects. The optimizer plans with dependencies, the scheduled people including availability and absences, equipment, material demand and lead times as well as the bookings of other projects as occupied capacity. It does not match skills. The objective is the planned project end; with several projects the optimizer weights a project’s delay by its priority rank (
prioritization_rank): a higher rank value means more weight, a missing rank counts as 1. - Commit (per project, default scope all five scopes; see Optimizer commit):
- Tasks and segments receive new positions in the plan and scheduled start/end dates; gates, milestones and events are shifted accordingly; the task’s assignee follows the booking.
- For every solved assignment, employee and equipment bookings are created with the run ID. Earlier optimizer bookings on the project are replaced; manual bookings remain untouched. Overlaps with foreign bookings are counted and reported, not prevented.
- The order proposals become open purchase requests („Einkaufsaufforderung“, status „Offen“) with „Frühstens am“ (arrival) and „Fällig am“ (order, taking the article’s lead time into account). Earlier open optimizer requests of the project are replaced; in multi-project runs the project that commits first orders a good, later ones skip it.
- The planned project period is set to the solved period, the phase changes from „Initialisierung“, „Definition“ or „Planung“ to „Umsetzung“ (forward only). On the phase change Aligia freezes the EVM baseline.
- The commit is refused for projects in „Abschluss“, „Erfolgreich Abgeschlossen“ or „Fehlgeschlagen“, for unsolved projects, for outdated runs (there is a newer run: „Veraltet — neu berechnen“) and for already committed scopes.
- Rollback (phase change back to an early phase, needs access to optimization): all committed runs of the project are rolled back from newest to oldest. Optimizer bookings from today onward are removed, those running across the cutoff date are truncated at that date, open optimizer requests are withdrawn, positions, dates and assignments are reset to the state before the commit – only where the value still equals the one written by the commit; your own later changes remain. The EVM baseline is released,
committed_atis cleared. The past is preserved. If there is no committed run, Aligia only changes the phase. - Projects with a committed run cannot be deleted; the rollback must come first.
Optimizer dates are the source for „Feste Termine“ (Fixed dates) and the planned project period, which enter progress and date KPIs; see Ch. 13 › Progress and Ch. 13 › EVM.
See also
Section titled “See also”Optimizer commit · Phase rules · Task · Employee booking · Equipment booking · Procurement request · Guides › Scheduling a portfolio with the optimizer