Reference & Data Model
Skill (skill)
A skill is an ability from the catalog; employees have it, project roles require it.
Purpose
Section titled “Purpose”The skill catalog is the common language between supply (employees) and demand (project members with skill requirements). It is master data: a skill is defined once and referenced by any number of employees and projects.
Where in the app
Section titled “Where in the app”Stammdaten › Skill-Katalog (Master data › Skill catalog): tree of categories and skills; dialogs „Neue Skill-Kategorie“ (New skill category), „Neuer Skill“ (New skill) and „Updaten“ (Update). The skill view shows „Mitarbeiter mit diesem Skill“ (employees with this skill), „Offene Rollen“ (open roles), „Projekte mit Bedarf“ (projects with demand) and „Bedarf aus Projektrollen“ (demand from project roles) („Besetzt“/„Unbesetzt“, filled/unfilled). See Guides › Skill catalog.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Title | name |
Text | yes | Name of the skill | search-weighted |
| Category | osp_skill_category_id |
Reference | no | Skill category in the tree | prefilled from the tree selection in the create dialog |
| Certification required | certification_required |
Yes/No | yes | Skill requires proof | |
| Certification name | certification_name |
Text | no | Name of the certificate | only visible when certification is required |
| Description | description |
Text | yes (DB) | Free text | dialog does not enforce input |
Skill category (osp_skill_category)
Section titled “Skill category (osp_skill_category)”Tree node with Title (name, required), Color (color, required), Description (description, required in the database) and parent category (parent_id, reference cleared on delete). The category view counts „Skill-Unterkategorie“ (skill sub-categories) and „Skills“. Deleting a category only clears the reference of its skills and sub-categories.
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
Skill category (osp_skill_category) |
belongs to | no | – | reference cleared |
Employee (employee) |
n:m via employee_skill_map |
– | – | mappings deleted along |
Project member, existing skill (project_member_skill_map) |
n:m | – | – | mappings deleted along |
Project member, skill requirement (project_member_skill_requirement) |
n:m | – | – | requirements deleted along |
Rules & automation
Section titled “Rules & automation”- The KPIs of the skill view come from the mappings: open roles = skill requirements of project members without an assigned employee; projects with demand = projects of those roles.
- Resource matching in the project shows the required skills of a resource demand for comparison; there is no automatic check or lock. The Optimizer does not match skills.
- Master data character: Renaming or a changed certification requirement applies immediately to all employees and all skill requirements in all projects. Deleting a skill removes it from all employee profiles and from all project roles, including the requirements of open roles.