Reference & Data Model
Employee usage (employee_usage)
An employee usage is the planned effort of a project member for a task, including cadence.
Purpose
Section titled “Purpose”The employee usage states how many hours a project member is planned for a task and how this demand is distributed across the task. It is the input for the Optimizer, workload and planned personnel costs. (Transactional data)
Where in the app
Section titled “Where in the app”Open a task › sheet „Ressourceneinsatz“ (Resource usage) (table with „Plan-Aufwand“, „Ist-Aufwand“, „Rest“ — planned effort, actual effort, remaining). Create via „Noch nicht eingesetzte Hauptzuweisung“ (main assignment not yet used) or „Noch nicht eingesetzte Teilnehmer“ (participants not yet used) → dialog „Geplanter Aufwand für …“ (Planned effort for …). A participant added via the task table automatically receives a usage with 0 hours. Also in the org chart: tab „Zuweisungen“ (Assignments) of a member (Guides › Workspace).
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Planned effort | estimate_effort_in_hours |
Number (h) | yes | Estimated total effort | Default 0 |
| Cadence | cadence_kind |
Selection | yes | „Durchgehend“ (throughout, throughout), „Einmalig“ (once, once), „Alle…“ (every…, periodic) |
Default „Durchgehend“ |
| When | cadence.anchor |
Selection | no | For „Einmalig“: „Zu Beginn“ (at the start) / „Am Ende“ (at the end) | Part of cadence (JSON) |
| Every … / Unit | cadence.every, cadence.unit |
Number + selection | no | For „Alle…“: every n „Tag(e)“ (day(s)) / „Woche(n)“ (week(s)) | |
| Block length | usage_hours |
Number (h) | no | Hours per block for „Alle…“ | Warning „Block darf nicht länger als eine Periode sein“ (block must not be longer than one period) |
| Quantity | qty |
Number | yes | Number of slots; chip „×n“ in the table | Default 1; not changeable in the user interface |
| Project member | project_member_id |
Reference | yes | Who is deployed (also an unfilled role) | |
| Task | task_id |
Reference | yes | For what |
Not displayed: origin (system, always authored).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Project member | belongs to | yes | archived along | deleted along |
| Task | belongs to | yes | archived along | deleted along |
| Employee booking | has many | — | archived along | deleted along |
Rules & automation
Section titled “Rules & automation”- Per project member and task there is at most one usage in the user interface (the dialog edits the existing one).
- Planned personnel costs: effort × quantity × hourly rate (project hourly rate, otherwise the employee’s hourly costs) is booked as the planned item „Geplante Personalkosten aus Ressourcenplanung“ (planned personnel costs from resource planning) and recalculated on change; without a rate (unfilled role) no booking. See Planned personnel costs.
- The Optimizer distributes the effort onto bookings according to the cadence (Optimizer commit).
- Actual effort of the row = sum of the time entries of this employee on this task (Time entry).
Effort (estimated) per project, utilization per member, actual/planned effort per task – see Resources & workload and Work.