Skip to content

Reference & Data Model

Structure & counts

Counts of objects and tasks; the basis is the object inventory per scope.

KPI MP PF PG PJ Where Meaning Calculation Display
Projects (count) („Projekte“) ✓ ✓ ✓ MP: Overview › chip; PF: Scoreboard › chip, Profile › quick stats, program cards, resource planning › sidebar; PG: Scoreboard › chip, Profile Number of projects in the respective scope MP (server): projects of the organization with status „Aktiv“ (Active) or „Pausiert“ (Paused); succeeded and failed ones do not count, archiving does not change the number. PF chip (view): direct projects + program children excluding failed; PF profile: direct projects only; PG: projects of the program excluding failed Count · chip
Project members / segments / segment counters / criteria / receipts („Projektmitglieder“ / „Segmente“ / „Kriterien“ / „Belege“) ✓ ✓ ✓ PF: Profile › project cards, resource planning › sidebar, Criteria › heading; PG: Profile › project cards; PJ: Profile › header + segments (milestones, work packages, tasks, gates, events), Business Case › „Belege“ Object counts View: number of linked records (project members, segments, milestones, work packages, tasks, gate criteria, events, portfolio targets, risk criteria, earning occurrences) Count
Programs (count) („Programme“) ✓ ✓ MP: Overview › chip; PF: Scoreboard › chip, Profile Number of programs MP (server): all programs of the organization; PF (view): programs of the portfolio Count · chip
Open tasks („Offene Aufgaben“, project / program) ✓ ✓ PJ: Scoreboard › briefing chip + KPI band (hint „offen / gesamt“); PG: Scoreboard › chip Tasks not completed Server: number of tasks with state ≠ „Erledigt“ in the project, excluding deleted (archiving does not change the number); PG: rollup over projects with status „Aktiv“ or „Pausiert“; hint = number of all tasks Count · chip/tile
Portfolios (count) („Portfolios“) ✓ Overview › chip Number of portfolios of the organization Server: number of portfolios Count · chip
Share of failed projects („Anteil gescheiterter Projekte“) ✓ Overview › „Kapital & Rendite“ › chip 4 Share of failed projects among all closures Server: 100 × number of closures with outcome „Fehlgeschlagen“ ÷ number of all closures; the recorded closure events are counted, not the current status, and reopening does not change periods that were already reported % (0 decimals)
Failed projects (list) („Fehlgeschlagene Projekte“) ✓ Overview › „Was heute zählt“ › bottom card Which projects failed View: projects with status „Fehlgeschlagen“; per row title, portfolio, actual costs (server); empty → a note that there are none List with link
Phases (funnel) („Phasen“) ✓ Portfolio › Scoreboard › strategy fit › card 2 Number of projects per lifecycle phase View: count of the project phase over all projects that are not yet closed (direct + program children; programs themselves not counted); the five phases Initialization … Closing always; succeeded and failed projects do not appear; bars relative to the maximum Count + bars
Tasks by status („Aufgaben nach Status“) ✓ Project › Scoreboard › „Umsetzung“ Distribution of tasks across states Server, live: number of tasks per state (not stored); fixed status colors Stacked bar + legend (count)
Tickets (open) („Tickets“) ✓ Project › Scoreboard › „Umsetzung“ Open issues Server: number of issues with state not in {Erledigt, Abgebrochen, Duplikat} Count („offen“)
  • Project counting is inconsistent: the organization counts projects with status „Aktiv“ or „Pausiert“; the portfolio chip counts direct projects plus program children excluding failed ones, the portfolio profile only direct projects; the phase funnel counts projects that are not yet closed including program children, but no programs.
  • Status instead of phase: „Fehlgeschlagen“ (Failed) and „Erfolgreich abgeschlossen“ (Succeeded) are project statuses (technically failed and succeeded), not phases. Programs and portfolios have no status; their count includes every non-deleted object, archived ones too.

See Project, Task, Issue.