Reference & Data Model
The core data relations
Six chains connect the data types. Once you know them, you can find every entity and understand why a change in one place has an effect elsewhere.
Map of all domains
Section titled “Map of all domains” Organization & access (1) Master data (2) Organization · User Employee · Skill · Department Roles · Settings Material · Specification · Equipment │ Project type · Work calendar │ │ ▼ ▼ ┌──────────────── Planning data (3) ─────────────────────┐ │ Portfolio → Program → Project → Segment → Task │ │ Technical structure → Node → Component │ └───────┬──────────────┬──────────────┬──────────────┬────┘ ▼ ▼ ▼ ▼ Resources (4) Time tracking (5) Finance (6) Risks (7) Project member Time log Budget Risk/Opportunity Effort/Booking Time entry Cost item Measure Material req. Approval Actual/plan Portfolio Procurement booking criteria │ │ │ │ └──────────────┴──────┬───────┴──────────────┘ ▼ Issues (8) · Knowledge (9) · Files & Drive (10) · Automation & AI (11) │ ▼ System logic (12) generates → Calculated data → KPIs (13)1 · The planning hierarchy
Section titled “1 · The planning hierarchy”Portfolio (prt)├── Program (prg) [optional]│ └── Project (prj)└── Project (prj) └── Segment (seg) ├── Work package (tpk) [optional] │ └── Task (tsk) ├── Task (tsk) │ └── Subtask / "Checkpoint" (sub) ├── Milestone (mil) ├── Gate (gcr) └── Event (evt) [segment optional, project required]A Program and a Project always belong to exactly one Portfolio (required). The program is optional for the project. Every Segment belongs to a project, every Task to a segment; the Work package is an optional bundle within the segment. Milestones and Gates hang off the segment. The Event belongs to the project and can be assigned to a segment. Dependencies (project_item_dependency) connect tasks, subtasks and milestones with one another. Everything about this in chapter 3; the hierarchy from the user’s perspective in Guides › Hierarchy.
2 · Technical structure and material
Section titled “2 · Technical structure and material”Project (prj) ──▶ Technical structure (tst) [optional] └── Node (tsn) [nested via parent node] ├── Component (tsg) ──▶ Variant (goo) ──▶ Material (prd) ──▶ Material category (gty) └── Requirement (tsr) ──▶ Material category (gty) └── Specification requirement (tss) ──▶ Specification (gts)A project can refer to a Technical structure. It consists of nested Nodes. A node carries Components, each pointing to a concrete Variant from the material catalog, and Requirements, which describe a Material category with conditions on its specifications. A component can fulfil a requirement. Material category, material, variant and specification are master data (chapter 2); structure, node, component and requirement are planning data (chapter 3).
3 · People, effort, time and personnel costs
Section titled “3 · People, effort, time and personnel costs”Employee (emp) ──▶ Project member (pmb) [employee optional: unfilled role] └── Planned effort (eus) on Task (tsk) └── Booking (ebk) [System: optimizer]Employee (emp) ──▶ Time log (tlg) on Project (+ task optional) └── Time entry (ten) ⇒ on approval: actual booking personnel costs (cto) [System]An Employee becomes a Project member in the project; without an employee this is an unfilled role with skill requirements. A Planned effort plans hours of a project member on a task; from it arise planned personnel costs and, through the optimizer, Bookings. Independently of that, the employee records Time logs with Time entries. When a time log is approved, the system books personnel costs as an actual booking. Details in chapter 4, chapter 5 and Actual personnel costs.
4 · Material, procurement and material costs
Section titled “4 · Material, procurement and material costs”Component (tsg) ──▶ Material requirement (gus) on Task (tsk)Variant (goo) ──▶ Procurement request (gpr) [System: from requirement; type stock or purchase] └── Purchase (gpc) ──▶ Actual booking material costs (cto) [System] └── Cost item (cti) ──▶ Budget (bgt)A Material requirement hangs off a task and refers to a component or a node of the technical structure. From it the system generates Procurement requests per variant. A request of type purchase becomes a Purchase; the system books its amounts as material costs on the Cost item „Materialkosten“ (Material costs), which is bound to a Budget. Details in chapter 4, chapter 6, Material costs and Procurement.
5 · Uncertainty, status and strategy
Section titled “5 · Uncertainty, status and strategy”Project (prj) ──▶ Risk (rsk) ──▶ Risk measure (rac) [optional: gate, cost item]Project (prj) ──▶ Opportunity (cha) ──▶ Opportunity measure (cac) [optional: gate]Project | Program | Portfolio ──▶ Status report (sr) ──▶ Assessment (sas) per dimensionPortfolio (prt) ──▶ Criterion (ptt) ──▶ Rating (tas) per projectPortfolio (prt) ──▶ Risk contribution (rco) ──▶ Rating (rca) per projectRisks and Opportunities belong to the project and have Measures, which can additionally be bound to a gate or a cost item. Status reports exist for project, program and portfolio; every report contains Assessments (traffic lights) per dimension. The portfolio defines Criteria and Risk contributions; every project of the portfolio receives a Rating for them. Details in chapter 7 and chapter 9.
6 · KPIs from the bottom up
Section titled “6 · KPIs from the bottom up”Project (prj) ──▶ KPI values (kpv, scope project) └─ Rollup ─▶ Program (prg) ──▶ KPI values (scope program) └─ Rollup ─▶ Portfolio (prt) ──▶ KPI values (scope portfolio) └─ Rollup ─▶ Organization ──▶ KPI values (scope overall)The server first calculates KPI values (kpi_value) per project from tasks, bookings, risks and events. Program, portfolio and organization values arise as the sum or average of the project values or directly from the data of that level. A KPI value always carries its scope (project, program, portfolio or organization). Details in chapter 13.