Reference & Data Model
Planning data at a glance
Planning data forms a fixed hierarchy: steering levels above the project, the work plan below it.
What defines this data type
Section titled “What defines this data type”Planning data is project-specific (as opposed to master data, ch. 2). It is created while an initiative is set up and carries three kinds of information: structure (who belongs to whom), position in time (target dates, relative position in the plan, dates computed by the optimizer) and state (phase, task status, gate status, milestone reached). All positions below the project are stored internally as an offset from the project start; the interface turns them into calendar days.
The entities of this chapter
Section titled “The entities of this chapter”Portfolio (portfolio)├── Program (program) ───────────────┐ optional└── Project (project) ◄──────────────┘ ├── Technical structure (technical_structure) → 3.12 ├── Event (event) ────── optional → Segment └── Segment (segment) ├── Work package (task_package) │ └── Task (task) ├── Task (task) │ ├── Subtask "Checkpoint" (subtask) │ ├── Subscriber (task_subscriber) │ └── Comment (task_comment) → ch. 8 ├── Milestone (milestone) └── Gate (gate_criteria) └── preventive/reactive measure → ch. 7
Dependency (project_item_dependency): Task/Milestone/Gate ⇄ Task/Milestone/Gate| Entity | Purpose | Where in the app |
|---|---|---|
Portfolio (portfolio) |
Top steering level, e.g. a business unit | Guides › Portfolio view |
Program (program) |
Bundles the projects of a portfolio | Guides › Program view |
Project (project) |
The initiative with team, budget, work plan, phase | Guides › Project view |
Segment (segment) |
Section of the project; container for all planning objects | Guides › Work area |
Work package (task_package) |
Optional group of tasks within a segment | Guides › Work area |
Task (task) |
Plannable unit of work with status, duration, assignment | Guides › Work area, Guides › My tasks |
Subtask (subtask) |
Checkable step within a task (“Checkpoint”) | Task › „Checkliste“ (Checklist) |
Milestone (milestone) |
Key date that is marked as reached | Guides › Work area |
Gate (gate_criteria) |
Checkpoint with status and deal-breaker flag | Guides › Gate decision |
Event (event) |
Meeting, digital or on site | Work area, calendar |
Dependency (project_item_dependency) |
Ordering relation between planning objects | Guides › Gantt |
| Technical structure, node, component, requirement | Digital twin of the plant | 3.12 ff. |
| Optimization | Schedule and resource computation | 3.16 |
Links to other chapters
Section titled “Links to other chapters”- Master data (ch. 2): leads and assignments reference Employees; programs and projects carry a Project type.
- Resources (ch. 4): tasks are assigned to Project members; staff and equipment usages hang off tasks.
- Finances (ch. 6): customer order (Order), budget goals, default cost items per project.
- Risks (ch. 7): gates carry preventive and reactive Risk measures.
- System logic (ch. 12): Phase rules, Optimizer commit, Locks.
- KPIs (ch. 13): Progress & dates, Quality & gates, Status, Counts.