Reference & Data Model
Overview: levels, topics, how to read
Aligia shows around 130 KPIs on four levels; this section explains how to read the catalog tables of this chapter.
What makes a KPI
Section titled “What makes a KPI”A KPI is a value derived from records: a sum, a count, a ratio or a verdict („im Plan“, on track). KPIs are not edited. They only change when the underlying data changes, for example when a task is completed or a cost occurrence is booked. KPIs are the read-out of the data from chapters 3 to 9.
Levels
Section titled “Levels”Every KPI applies to a scope: the organization, a portfolio, a program or a project. The catalog tables list the levels as columns:
| Abbreviation | Level | Where in Aligia |
|---|---|---|
| MP | Organization (multi-portfolio) | Projekt & Portfolio › Übersicht (organization scoreboard), see Guides › Overview |
| PF | Portfolio | Portfolio › „Scoreboard“, „Aufsicht“ (Oversight), „Strategie“ (Strategy), „Budget“, „Business Case“, „Steckbrief“ (Profile), „Kriterien“ (Criteria), resource planning; see Guides › Portfolio scoreboard |
| PG | Program | Program › „Scoreboard“, „Budget“, „Business Case“, „Risiken/Chancen“ (Risks/Opportunities), „Statusberichte“ (Status reports), „Steckbrief“; see Guides › Program scoreboard |
| PJ | Project | Project › „Scoreboard“, „Steckbrief“, „Wirtschaftlichkeit“ (Financial performance: budget plan, business case), „Risiken/Chancen“, „Beschaffung“ (Procurement), „Ressourcen“ (Resources), „Insights“; see Guides › Project scoreboard |
A ✓ in a level column means: the KPI is shown at this level in the interface. Where the meaning is the same but the calculation differs per level, the difference is stated in the “Calculation” column. Where the formula is fundamentally different, there is a separate row with a qualifier in the name.
Personal work KPIs (Workmanagement › Übersicht) have no level in this sense; they are listed in Personal work KPIs.
Topics
Section titled “Topics”| Topic | Page | Count |
|---|---|---|
| Progress & dates | 13.3 | 11 |
| Budget & costs | 13.4 | 21 |
| Financial performance | 13.5 | 23 |
| Earned Value (catalog) | 13.6 | 5 |
| Risks & opportunities | 13.7 | 16 |
| Strategy & prioritization | 13.8 | 12 |
| Resources & workload | 13.9 | 8 |
| Procurement & material | 13.10 | 6 |
| Quality & gates | 13.11 | 5 |
| Status & traffic lights | 13.12 | 12 |
| Structure & counts | 13.13 | 10 |
| Personal work KPIs | 13.14 | 21 |
Main catalog summary: 129 KPIs, of which visible on MP 24 · PF 66 · PG 58 · PJ 87.
How to read the tables
Section titled “How to read the tables”Every catalog page has the same columns:
| Column | Content |
|---|---|
| KPI | English name with the German UI label; variants of the same label in parentheses |
| MP · PF · PG · PJ | ✓ = visible at this level |
| Where | View › tab › card, per level |
| Meaning | The business statement in one sentence |
| Calculation | Formula with all filter rules (phase, archive, date, state) |
| Display | Unit and form (tile, column, bar, traffic light) |
Below a table, Notes follow where needed: KPIs with the same name but a different formula, and known discrepancies you should be aware of when comparing numbers.
Calculated by the server or calculated in the view
Section titled “Calculated by the server or calculated in the view”Aligia has two calculation paths. The difference explains many small discrepancies between views.
- Calculated by the server and stored. The KPI is defined centrally, calculated in the background and distributed to all users as a stored value (details in Freshness). Characteristics: same value for everyone, short delay after a change, division by 0 yields 0, deleted records never count, archived ones only do not count where the table has an archive field. Examples: progress, profit, risk exposure, SPI, Value CPI, all counters of the organization overview.
- Calculated in the view from the visible data. The KPI is produced when the view opens, from the locally synchronized records. Characteristics: immediately up to date after your own input, archived projects are hidden by the default filter, the result depends on which records the view loads. Examples: all budget plan and business case values, probable damage, workload, prioritization.
- Both. Building blocks from the server, ratio or sum in the view (or vice versa). Example: „Kosten / Budget“ (costs / budget) divides two server values in the view; „Einnahmen“ (revenue) in the scoreboard = server profit + actual costs calculated in the view.
Recurring building blocks
Section titled “Recurring building blocks”All catalog pages use these terms:
- Actual costs („Ist-Kosten“) = sum of cost occurrences (
cost_occurrence.cost_value). The table contains only actual bookings, see Cost occurrence. - Planned costs („Geplante Kosten“) = sum of planned costs (
planned_cost.cost_value), see Planned costs. - Cost item budget („Kostenarten-Budget“) = sum of the budgets stored per cost item (
cost_item.budget.value), see Budget. - Budget goal („Budgetziel“) = field
budget_goalon the project, program or portfolio (master data of the profile, not the sum of the cost item budgets). - Phase filter „Planung“ (planning) = in portfolio and program aggregates, planned costs count only for projects whose phase is not „Initialisierung“ (Initialization) or „Definition“. Individual rows per project do not apply the filter.
- Last status report = the most recent status report of the object with its six assessments (overall, work plan, costs, resource effort, risk/opportunity, engineering); a missing assessment counts as “not assessed” (grey). See Status report.
- Rollup = a sum formed by the server from the stored project values of a program or portfolio. Archived projects are included, with two exceptions: the portfolio profit and all Earned Value rollups exclude archived projects.
- „—“ = not computable. The server returns the value 0 for “not computable”; ratio tiles show this 0 as „—“.
Traffic light conventions
Section titled “Traffic light conventions”| Where | Red | Yellow | Green |
|---|---|---|---|
| Ratio KPIs SPI, Value CPI, strategic budget adherence | < 0.9 | 0.9 to 1.0 | > 1.0 |
| Costs against budget („Kosten / Budget“, budget utilization) | > 100 % | ≥ 90 % | otherwise |
| Amount tiles „Gewinn“ (profit), „Rest-Budget“ (remaining budget), „Rest-Budget nach Forecast“ (remaining budget after forecast) | < 0 | = 0 | > 0 |
| Workload (resource Gantt) | > 100 % | 80–100 % | < 80 % (grey at ≤ 0) |
| Workload (team node in the project) | > 89 % | 70–89 % | < 70 % |
| Status report traffic lights | Assessment „Rot“ | „Gelb“ | „Grün“; grey = not assessed |
| Counters requiring action (overdue, open gate criteria, K.O. violated) | > 0 | – | – |
Connections to other chapters
Section titled “Connections to other chapters”- Data basis: Planning data, Resource data, Budget & financial data, Risk & opportunity data, Knowledge data.
- Automatic recalculation: KPI recalculation.
- Usage: Guides › Scoreboard & KPI tiles.