Skip to content

Guides

Scheduling a portfolio with the Optimizer

How to have several planned projects scheduled together, check the result and fix it in place.

The selected projects have a coordinated schedule in which the projects share jointly used resources and material. Applied projects run in the phase „Umsetzung“ (Execution).

Portfolio manager/PMO (selects, evaluates), Project managers (provide the work plans), Admin (starts, applies, reverts).

  • The projects are in the phase „Planung“ (Planning). Only these are shown by the tab Strategy.
  • Their work plans with dependencies and „Ressourceneinsatz“ (resource deployment) are maintained (see Building & optimizing the work plan).
  • Prio scores are assigned.
  1. Select projects – in the tab „Strategie“ mark the rows and choose „Optimieren (n)“ (optimize). Only projects are optimized; Aligia skips selected programs.
  2. Start the run – The „Portfolio-Optimierung“ (portfolio optimization) opens from below and shows the last saved run. Starting a new run needs access to optimization. The Optimizer plans all projects together. The goal is the planned project end. Delays of projects with a higher prio score weigh more heavily.
  3. Evaluate the result – The KPI bar shows how many projects are „termingerecht“ (on schedule), the „Gesamtverspätung“ (total delay), the deviation „ggü. aktueller Planung“ (vs. current plan), the „Gesamtkosten“ (total costs), bottlenecks and orders. Four views go deeper:
    • „Projekte“ (projects): per project „Aktueller Plan → Optimierter Plan“ (current plan → optimized plan), „Bestellvorschläge“ (order proposals) and „Probleme / Zu beheben“ (problems / to fix). The portfolio overview sets rank and delay against each other.
    • „Ressourcen“ (resources): workload per employee and device, overbookings and resources used by several projects.
    • „Material“: demand, coverage and goods for which „Beschaffung nötig“ (procurement needed) applies.
    • „Zeitplan“ (schedule): the plan of an individual project.
  4. Play through variants – Pin tasks or dates and „Neu berechnen“ (recalculate). Pins are what-if and are not saved unless you choose „Als Bedingung speichern“ (save as constraint). If the plan is not solvable, the „Diagnose“ names the causes.
  5. Apply – per project with „Übernehmen“ (apply) or collectively with „Alle übernehmen (n)“ (apply all), each after a confirmation. Applying needs access to optimization.

Tasks, gates and milestones receive fixed dates. For employees and equipment, resource bookings are created; from the order proposals, open purchase requisitions in Procurement. Projects from an early phase move into „Umsetzung“ and thus into the tab Operations. The success message also names booking conflicts and violated gates. Reverting is done via the phase transition back, see Gate decision & phase transition.

Resolving a resource conflict · Evaluating & prioritizing a project idea · Resource workload