Skip to content

Reference & Data Model

Applying and rolling back an optimization (system_optimize_commit, system_optimize_rollback)

„Übernehmen“ writes a solved optimization run bindingly into project, tasks, bookings and procurement; the rollback undoes that for the future.

„Übernehmen“ / „Alle übernehmen“ (apply / apply all) in the portfolio or project optimization (Guides › Schedule the portfolio with the optimizer). Rollback: phase change back to an early phase after confirming „Optimierung verwerfen?“ (Phase rules).

  • An access on the whole organization that allows optimization (for example base access „Bearbeiten“, Edit); otherwise „Du hast keinen Zugriff zum Übernehmen.“ (You have no access to apply this.)
  • The project is „Aktiv“ (not „Pausiert“, „Erfolgreich abgeschlossen“ or „Fehlgeschlagen“) and not in „Abschluss“.
  • The run is the most recent; with a newer run: „Veraltet — neu berechnen“.
  • No repeated apply with exactly the same options („already applied — roll back first“); an apply with new options (e.g. first dates, later bookings) is allowed.

What changes (depending on the chosen options)

Section titled “What changes (depending on the chosen options)”
Area Effect
Tasks, segments Relative positions (deltas) and „Geplanter Start/Ende“ (scheduled_start_date/end_date) from the solution plan; gates/milestones with their segments
Task → assignment assigned_member_id = first assigned project member
Bookings Employee booking / equipment booking per (task, resource); earlier optimizer bookings of the project are replaced, manual ones never touched
Procurement Per order proposal one procurement request of type purchase, status „Offen“, with run identifier; earlier open optimizer requests are replaced; user-created or already completed ones remain
Project „Geplanter Start/Ende“ (scheduled_start_at/end_at) set to the solved window (only when applying dates)
Phase From „Initialisierung“, „Definition“ or „Planung“ forward to „Umsetzung“; never downward; only if a date or booking option is chosen (a pure procurement apply does not change the phase)
EVM The phase change to „Umsetzung“ freezes the baseline (project_baseline, version 1), see EVM
Run Apply timestamp, number of booking conflicts and a before-snapshot of all overwritten values are stored on the run

Follow-on effect: the new procurement requests create planned items „Materialkosten“ (Procurement).

The rollback (needs access to optimization, active project only) undoes all applied runs of the project in one transaction, newest first:

  • Dates, positions, assignments and project window are reset from the snapshot – only where the value still matches the applied one; subsequent manual changes remain and are counted.
  • Future optimizer bookings (from today, UTC day) are removed, running ones are cut off at the previous day; the past remains.
  • Open optimizer procurement requests are deleted (completed ones remain).
  • The EVM baseline is released if the apply had created it.
  • The phase is set to the chosen early phase. If there is no applied run, the phase is simply set directly.

Gantt (workspace, read-only from „Umsetzung“ on), Projektansicht › Ressourcen (bookings), › Beschaffung, phase badge, activity („Optimierung zurückgesetzt“).

  • The optimizer plans with scheduled persons, availability and material; skills are not matched.
  • Apply and rollback cannot be undone; the rollback removes no manual bookings.
  • A project with an applied run cannot be deleted; roll back the optimization first (Locks & delete protection).

See Optimization · Employee booking · Equipment booking · Procurement request.