Reference & Data Model
Master data at a glance
Master data is maintained once and used in many projects; it cannot be archived, and deleting it propagates through references into the project data.
What defines this data kind
Section titled “What defines this data kind”A master data record belongs to no project. It is valid organization-wide, changes rarely and is referenced by planning, resource, time and financial data. None of the entities in this chapter has an archive (archived_at); there is only delete. Almost all of them instead have a status „Aktiv“/„Inaktiv“ (Active/Inactive, active) that controls whether they can be selected in projects without removing the record.
The catalogs live in the Stammdaten (Master data) app (menu „Mitarbeiter & Abteilungen“, „Skill-Katalog“, „Material-Katalog“, „Equipment-Katalog“). Project types live outside this app under Projekt & Portfolio › Projekttypen. Capacity uses a fixed working time default (5 days × 8 hours, Saturday and Sunday off).
Entities and relations
Section titled “Entities and relations”Department (osp_employment_unit) ─┬─ parent department (tree) └─→ Employee (employee) ─┬─ Supervisor / Assignee (employee) ├─ User account (app_user, 1:1) └─⇄ Skill (skill) ← Skill category (osp_skill_category, tree)
Material category (good_type, tree) ─┬─→ Product (good) ─→ Article (good_variant) ─→ Specification value (spec_value) ├─→ Specification category (spec_category) │ └─→ Technical specification (good_type_spec) ◄──────────────────┘
Equipment group (osp_equipment_unit, tree) ─→ Equipment (equipment) ─→ Responsible (employee)
Project type (project_type) ←── Project / Program (ch. 3)| Entity | Purpose | Where in the app |
|---|---|---|
Employee (employee) |
Person with capacity, hourly rate and skills; plannable resource | Guides › Employees & departments |
Department (osp_employment_unit) |
Node of the organization tree with a head | Guides › Employees & departments |
Skill (skill) with Skill category (osp_skill_category) |
Ability that employees have and project roles require | Guides › Skill catalog |
Material category › Product › Article (good_type › good › good_variant) |
Three-level material catalog with price and stock data | Guides › Material catalog |
Technical specification (good_type_spec) with Specification category (spec_category) and Specification value (spec_value) |
Attributes per material category, values per article | Guides › Material catalog |
Equipment (equipment) with Equipment group (osp_equipment_unit) |
Machines and devices as plannable resources | Guides › Equipment catalog |
Project type (project_type) |
Classification of projects and programs | Guides › Project types |
Connections to other chapters
Section titled “Connections to other chapters”- Planning data (ch. 3): Project, program and portfolio reference an employee as their lead; project and program reference a project type; the technical structure references material categories, articles and specifications.
- Resource data (ch. 4): Project member, usage, booking, unavailability and procurement request hang on employees, equipment and articles.
- Time tracking (ch. 5) and financial data (ch. 6): The employee’s hourly rate is the fallback value for personnel costs; the article’s unit price values procurement and purchases.
- Risks (ch. 7) and issues (ch. 8): Owners, people responsible for measures and the department of an issue are references to an employee or a department.
- System logic (ch. 12) and KPIs (ch. 13): Capacity, hourly rate, price, procurement lead time and the working time default feed into workload, the Optimizer and the cost rules.