Skip to content

Reference & Data Model

Resources & workload

KPIs on effort, workload and conflicts; the basis is efforts, bookings, unavailabilities and work calendars.

All values on this page are calculated in the view, except „Aufwand (geschätzt)“ (estimated effort; server).

KPI MP PF PG PJ Where Meaning Calculation Display
Workload per project member (curve) („Auslastung“) ✓ ✓ PF: Resource planning › project › „Auslastung“; PJ: Resources › „Auslastungen“ Planned task hours per day relative to daily capacity Per member and task with estimated effort > 0: hours/day = effort ÷ task duration (days), stacked over the task window; capacity = min(calendar daily hours, „Max. Stunden/Tag“), otherwise 8 Step curve in the Gantt; color bands 80 % / 100 %
Effort (estimated) („Aufwand (geschätzt)“) ✓ Portfolio › Strategy › table „Aufwand“ (+ Σ footer) Estimated personnel effort Server: Σ estimated effort over the project’s tasks; program: own rollup, otherwise Σ children in the view „n h“
Workload % (per employee, global) („Auslastung %“) ✓ Menu Resource workload › „Mitarbeiter“ (badge per row), portfolio-independent Scheduled ÷ available hours Window today − 30 days to min(latest project end/unavailability, + 365 days); scheduled = calendar hours of confirmed bookings + effort spread evenly over the project window (dropped if already booked); available = calendar hours (weekly hours ÷ working days, ≤ „Max. Stunden/Tag“) minus unavailabilities % · badge (grey ≤ 0, green < 80, yellow 80–100, red > 100) + curve
Workload curve (employee) („Auslastungskurve“) ✓ Resource workload › curve per row Workload per day/week Time series of the same calculation; sections with availability 0 are omitted Step curve; from 80 % yellow, from 100 % red
Resource conflicts („Ressourcenkonflikte“) ✓ Resource workload › header badge + row badge Number of booking conflicts from today Booking × booking (same employee, different assignment, time overlap) + booking × unavailability; „{n} Konflikte bei {m} Mitarbeitenden“ Badge green/red
Equipment workload % / conflicts („Equipment-Auslastung %“ / „Konflikte“) ✓ Resource workload › „Equipments“ Booking hours ÷ calendar hours in the active period As for employees, with equipment capacity („Aktiv seit/bis“); downtimes reduce availability; conflicts booking × booking / booking × downtime % badge + curve; badge
Current workload (team node) („Aktuelle Auslastung“) ✓ Project › Resources › „Team“ (node color border + tooltip) Confirmed workload for the next 30 days Confirmed booking hours ÷ available hours (work calendar − unavailabilities) in the window now to + 30 days; not computable → 0 % · color border (< 70 green, 70–89 yellow, > 89 red)
Working hours per day / working days per week („Arbeitsstunden pro Tag“ / „Arbeitstage pro Woche“) ✓ Project › Profile › segments (footer) Project calendar (master data) Direct fields Number (both with suffix „h“)
  • Time windows and thresholds differ between resource workload (−30 to +365 days; 80 / 100 %) and team nodes in the project (+30 days; 70 / 89 %). The same employee can be green in one view and yellow in the other.
  • The workload does not match skills; it only calculates hours against capacity.
  • „Arbeitstage pro Woche“ carries the suffix „h“ in the profile.

See Employee effort, Employee booking, Unavailability, Guides › Resource planning, Guides › Workload.