Reference & Data Model
Earned Value (EVM): baseline and indices
Earned Value compares the value a project has achieved with the plan as of the reference date; the basis is a baseline frozen once.
Baseline
Section titled “Baseline”The baseline (project_baseline) is a frozen plan state of the project. It is created exactly once per project (version 1) and is not changed afterwards. A renewed baseline (“re-baseline”) is not provided for.
When it is frozen:
- Automatically on the first calculation of an Earned Value KPI, as soon as the project is in phase „Umsetzung“ (Execution) or „Abschluss“ (Closing). The trigger is opening a scoreboard that shows SPI/CPI/EAC, or a background run.
- Explicitly when applying an optimizer result that lifts the project into phase „Umsetzung“ (see Optimizer commit). If the commit is rolled back and the phase falls back, this baseline is deleted again.
Prerequisites (all must be met, otherwise nothing is frozen and the next attempt waits for the next calculation):
- Phase „Umsetzung“ or later.
- „Geplanter Start“ (
target_start_date) and „Geplantes Ende“ (target_end_date) set, end after start. - BAC > 0 (see below).
- At least one task with estimated effort and hourly rate, so that the sum of the weights is > 0.
What is frozen:
| Component | Content |
|---|---|
| Plan window | Copy of „Geplanter Start“ and „Geplantes Ende“ of the project |
| BAC (Budget at Completion) | „Budgetziel“ (budget goal) of the project; if none is set, the sum of the cost item budgets |
| Weights per task | Σ estimated effort (employee_usage.estimate_effort_in_hours) × hourly rate (hourly rate of the project member, otherwise hourly cost of the employee, otherwise 0), only non-deleted and non-archived tasks; tasks without effort have weight 0 |
| Planned costs | Copy of all planned costs at the time of freezing (currently not read by any KPI) |
The quantities
Section titled “The quantities”The reference date is always the current calendar day (UTC).
| Quantity | Meaning | Calculation | Without baseline |
|---|---|---|---|
| PV (Planned Value, „Plankosten“) | Value that was planned up to today | BAC × elapsed share of the plan window; linear over calendar days, limited to 0–100 % | 0 |
| EV (Earned Value) | Value of the completed work | BAC × (Σ weight of the tasks with state „Erledigt“) ÷ (Σ of all weights). 0/100 method: a task only counts fully once „Erledigt“. Only tasks that have a weight in the baseline are counted; a task archived later but completed keeps its share | 0 |
| AC (Actual Cost) | Actual costs incurred up to today | Σ cost occurrences with date ≤ today, not deleted | is calculated |
| SPI (Schedule Performance Index, „Terminindex“) | Schedule performance | EV ÷ PV; PV = 0 → 0 (display „—“) | 0 |
| Work-based CPI (internal) | Classic cost index | EV ÷ AC; only an intermediate quantity for EAC, not displayed | 0 |
| Value CPI (displayed as „Value CPI“) | Realized value per euro spent | (benefit of the project project.benefit + Σ earning occurrences with date ≤ today) ÷ AC; AC = 0 → 0 |
is calculated if AC > 0 |
| EAC (Estimate at Completion) | Forecast total costs | AC + (BAC − EV) ÷ work-based CPI; CPI = 0 → 0 (display „—“) | 0 |
Not implemented: ETC (Estimate to Complete) and VAC (Variance at Completion). BAC and EV are not separate KPIs in the interface; EV appears only in tooltips of the organization overview.
Value CPI versus work-based CPI
Section titled “Value CPI versus work-based CPI”The classic CPI (EV ÷ AC) measures cost efficiency via work progress. Because the weights contain personnel costs only, it would systematically come out too poor for material-heavy projects. Aligia therefore shows the Value CPI: realized value (benefit plus earnings already recorded) divided by actual costs up to today. It needs no baseline and can be calculated even before execution, as soon as costs are booked. The EAC internally still uses the work-based CPI. The SPI tile, Value CPI tile and EAC tile of a project can therefore have different “availability”: Value CPI with a value, SPI and EAC „—“.
Rollup to program, portfolio, organization
Section titled “Rollup to program, portfolio, organization”At higher levels the indices are not averaged; the building blocks are summed instead: SPI = Σ EV ÷ Σ PV, Value CPI = Σ (benefit + earnings) ÷ Σ AC over all child projects that are „Aktiv“ (Active) and in „Umsetzung“ or „Abschluss“. Paused, succeeded and failed projects as well as projects in an early phase do not contribute; archiving changes nothing. Every child project without a baseline contributes EV = PV = 0, but its AC and its value count in the Value CPI. EAC exists at project level only.
Where visible
Section titled “Where visible”- Project › „Scoreboard“ › card „Earned Value“: SPI (scale 0–2, mark at 1.0), Value CPI, EAC (hint „Plankosten“ = PV). The card appears only from phase „Umsetzung“; Value CPI only if actual costs > 0.
- Program › „Scoreboard“ › KPI strip: SPI, Value CPI.
- Portfolio › „Scoreboard“ › KPI tiles 6 and 7: SPI, Value CPI.
- Organization › „Portfolio-Vergleich“ and „Was heute zählt“: SPI, Value CPI per portfolio; tooltips name EV, PV, AC.
Traffic light: < 0.9 red · 0.9 to 1.0 yellow · > 1.0 green. A portfolio without SPI and Value CPI counts as “neutral”.
See also
Section titled “See also”Earned Value (catalog) · Freshness · Project · Guides › Project scoreboard