Reference & Data Model
Progress & dates
KPIs on work progress, dates and milestones; the basis is tasks, segments, milestones and the project dates.
| KPI | MP | PF | PG | PJ | Where | Meaning | Calculation | Display |
|---|---|---|---|---|---|---|---|---|
| Progress / completion („Fortschritt“ / „Fertigstellung“) | ✓ | ✓ | ✓ | PJ: Scoreboard › KPI band, card „Umsetzung“; PG: Scoreboard › „Projekt-Gesundheit“; PF: Scoreboard › „Aufsicht“ | Share of completed tasks of a project | Server: 100 × number of tasks with state „Erledigt“ ÷ number of tasks of the project; excluding deleted and archived tasks; ÷ 0 → 0. PF oversight, program row: unweighted mean of the child projects in the view (0 without children) | % · tile or bar | |
| Delay (D) („Verzug (T)“) | ✓ | ✓ | PJ: Scoreboard › briefing chip; PG: Scoreboard › „Projekt-Gesundheit“ | Deviation of the currently scheduled project end from the target end | Server: „Ende“ (scheduled_end_at) − „Geplantes Ende“ (target_end_date) in calendar days; decimals and negative values possible; a missing date → no value („—“) |
Days · number | ||
| Ø progress („Ø Fortschritt“) | ✓ | Program › Scoreboard › strip | Unweighted average of the progress of the projects in the program | Server rollup: Σ progress of the child projects ÷ number of child projects already calculated; archived included | % (0 decimals) · tile | |||
| Schedule index („Terminindex“) | ✓ | Project › Scoreboard › briefing chip | Relative deviation of the current duration from the target duration | Server: ((end − start) − (target end − target start)) ÷ (target end − target start); exactly 0 is hidden as „—“ | Ratio (2 decimals) · chip | |||
| Planned duration / current schedule („Geplante Laufzeit“ / „Aktuelle Planung“) | ✓ | Project › Scoreboard › status card; Profile › key data | Target dates against rescheduled dates (planning/optimizer, no actual data) | Direct fields „Geplanter Start/Ende“ (target_*) and „Start/Ende“ (scheduled_*) |
Date – date | |||
| Overdue tasks („Überfällige Aufgaben“) | ✓ | Project › Scoreboard › „Umsetzung“ | Tasks not completed with a due date before today | View: number of tasks with state ≠ „Erledigt“ and „Spätestens bis“ (notAfterDate) set and < today |
Count; red > 0 | |||
| Milestones (completed / total) („Meilensteine“) | ✓ | Project › Scoreboard › „Umsetzung“ | Completed milestones of the project | Server: number of milestones (via segments) with „Abgeschlossen“ = yes; hint: ÷ number of all milestones | Count · tile with hint | |||
| Next milestone („Nächster Meilenstein“) | ✓ | Project › Scoreboard › „Umsetzung“ | Name of the next open milestone | View: across all segments, the non-completed milestone with the smallest time distance | Text | |||
| Segment progress („Segment-Fortschritt“) | ✓ | Project › Scoreboard › card „Segmente“; Profile › segments | Task completion per segment | View: tasks „Erledigt“ ÷ tasks of the segment × 100. Scoreboard: without tasks „Keine Aufgaben“; profile: 0 % | % · progress bar („erledigt / gesamt Aufgaben“) | |||
| Duration (prioritization) („Dauer“) | ✓ | Portfolio › Strategy › table (+ footer Ø duration) | Duration of an element in days | View: (end, otherwise target end) − (start, otherwise target start) in days | „n d“ | |||
| Duration (radar) („Dauer“) | ✓ | Portfolio › Strategy › radar | Duration in calendar years, relative to the maximum of the selection | View: end year − start year + 1 (at least 1) | Radar axis |
- Progress has exactly one definition on the server:
projectProgress_in_pct. - Progress of the program row in the portfolio oversight is averaged in the view and can differ from the server value „Ø Fortschritt“ of the program scoreboard (the server value includes archived projects).
- Delay counts calendar days, not working days, and can be negative (ahead of plan). The briefings only count delay > 0.
- Duration carries the same label in table and radar, but days versus calendar years.