Reference & Data Model
Unavailability (employee_unavailability, equipment_unavailability)
An unavailability is a period in which an employee is absent or a piece of equipment is not ready for use.
Purpose
Section titled “Purpose”Unavailabilities take capacity out of planning. They reduce the available hours in the workload, appear as bars in the resource Gantt and mark bookings that fall into the period as conflicts. The Optimizer plans around them. (Transactional data)
Where in the app
Section titled “Where in the app”Projekt & Portfolio › Ressourcenausfälle (Unavailabilities) (Guides › Unavailabilities). Toggle „Alle“ / „Equipment“ / „Mitarbeiter“ (all / equipment / employees); groups „Aktuelle Ausfälle“ (current), „Zukünftige Ausfälle“ (future), „Vergangene Ausfälle“ (past). „Neuer Ausfall“ (New unavailability) → „Neuer Mitarbeiterausfall“ (New employee unavailability) or „Neuer Equipmentausfall“ (New equipment unavailability); clicking a row opens „Auswirkungen“ (Impact) and „Ausfall bearbeiten“ (Edit unavailability).
Fields
Section titled “Fields”Employee unavailability (employee_unavailability):
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Employee | employee_id |
Reference | yes | Absent person | |
| Start | start |
Date + time | yes | Start | Default: now |
| End | end |
Date + time | yes | End | Default: now + 1 h |
Equipment unavailability (equipment_unavailability):
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Equipment | equipment_id |
Reference | yes | Affected device | |
| Kind | kind |
Selection | yes | „Wartung“ (maintenance, maintenance), „Störung“ (breakdown, breakdown), „Reserviert“ (reserved, reserved) |
Default „Wartung“; breakdown/maintenance highlighted in red |
| Start | start |
Date + time | yes | Start | |
| End | end |
Date + time | yes | End |
Displayed, not stored: „Auswirkung“ (impact) – number of bookings („{n}× Einsatz“) that overlap the unavailability; the detail shows affected tasks and projects („Ohne Aufgabe“, „Ohne Projekt“ — without task, without project — when the reference is missing).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Employee (employee unavailability) | belongs to | yes | — | deleted along |
| Equipment (equipment unavailability) | belongs to | yes | — | deleted along |
Rules & automation
Section titled “Rules & automation”- Unavailabilities are periods with a time of day; an unavailability does not have to be assigned to a project.
- Available hours = calendar hours − unavailability hours; utilization rises accordingly (Resources & workload).
- Booking × unavailability = conflict „Gebucht & abwesend“ (booked & absent, employee) or „Gebucht & Ausfall“ (booked & unavailable, equipment).
- The banner „{n} Ausfälle treffen {m} Einsätze in {k} Projekten“ ({n} unavailabilities affect {m} usages in {k} projects) summarizes the impact.