Reference & Data Model
Employee booking (employee_booking)
An employee booking is a concrete period in which an employee is scheduled for an employee usage.
Purpose
Section titled “Purpose”The booking turns the estimated effort into an appointment: from date/time to date/time. Bookings are the basis of workload and of conflict checking across all projects. They are created manually or by the Optimizer. (Transactional data)
Where in the app
Section titled “Where in the app”Task › „Ressourceneinsatz“ (Resource usage) › expand a row: sub-rows „Buchung“ (Booking) with start, end and hours. „Buchung hinzufügen“ (Add booking, plus) opens „Neue Buchung“ (New booking); context menu „Bearbeiten“ (Edit) → „Buchung bearbeiten“ (Edit booking), „Löschen“ (Delete). Across projects in the resource Gantt under Projekt & Portfolio › Ressourcenauslastung (Resource workload) (Guides › Resource workload) and in the project’s „Auslastungen“ (workloads).
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Start (date) | start_at |
Date | yes | First day | |
| Start (time) | start_time |
Time | no | Start on the first day | dialog requires a time |
| End (date) | end_at |
Date | yes | Last day | „Startdatum ist Enddatum“ (start date is end date) sets end = start |
| End (time) | end_time |
Time | no | End on the last day | Without times the booking counts 0 hours |
| Project member / Task | via employee_usage_id |
Reference | yes | Displayed in the dialog | |
| Employee | employee_id |
Reference | yes | Booked person | System: from the project member |
Not displayed: optimization_run_id (system, server only; marks Optimizer bookings).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Employee usage | belongs to | yes | archived along | deleted along |
| Employee | belongs to | yes | — | deleted along |
Rules & automation
Section titled “Rules & automation”- Only filled roles can be booked.
- Optimizer: When a run is applied, all earlier Optimizer bookings of the project are replaced; manual bookings remain untouched. Rolling back removes Optimizer bookings only (Optimizer commit).
- Conflicts: Two bookings of the same person that overlap, or a booking within an absence, produce a resource conflict (Guides › Resolve a resource conflict).
- The sum of booked hours appears in „Plan-Aufwand“ as a second value („Geschätzter Aufwand / Summe der gebuchten Stunden“ — estimated effort / sum of booked hours).
Utilization % (scheduled ÷ available), resource conflicts, current utilization on the team node – see Resources & workload.