Skip to content

Reference & Data Model

Employee (employee)

An employee is a person in your organization with capacity, cost rate and skills; a user account is optional.

The employee is the plannable personnel resource (master data). Projects assign them as project members, book their time, log their hours and value those hours with their hourly rate. External staff are created the same way and marked with „Ist eine externe Ressource“ (Is an external resource).

Stammdaten › Mitarbeiter & Abteilungen (Master data › Employees & departments), dialog „Neuer Mitarbeiter“ (New employee) and the „Updaten“ (Update) area in the detail view with the tabs „Zuweisungen“ (Assignments), „Auslastung“ (Workload), „Skills“ and „Info“. See Guides › Employees & departments and Guides › Create employees with skills.

Field Technical Type Required Meaning Notes
First name / Last name first_name / last_name Text yes Display name search-weighted
E-mail email Text yes Contact; matching key when linking an account
Phone phone Text no Contact
Image image_url Text no Avatar
User ID app_user_id Reference no Linked user account, otherwise „Mitarbeiter ist kein User“ (Employee is not a user) system; can only be set via invitation
Key user_key Text no Your own key
Status active Selection yes „Aktiv“ / „Inaktiv“ (Active / Inactive) inactive employees are locked in selection lists
Position position Text yes Descriptive function no permissions
Department osp_employment_unit_id Reference no Node in the organization tree
Organizational affiliation („Ist eine externe Ressource“) external_source Yes/No yes „Intern“ / „Externe Organisation“ (Internal / External organization)
Description description Text no Free text
Working hours per week working_hours_per_week Number yes Weekly capacity in h
Maximum daily working time max_working_hours_daily Number yes Daily upper limit in h
Min. / max. daily utilization (%) min_utilization_daily_in_pct / max_utilization_daily_in_pct Number yes Target corridor of daily utilization Optimizer uses only „Max.“
Total utilization capacity (%) max_utilization_daily_in_pct Number – Shown in the update area writes the same field as „Max. Auslastung am Tag“
Upper / lower yellow utilization threshold (%) yellow_upper_bound_in_pct / yellow_lower_bound_in_pct Number no Yellow band of the utilization rating „Auslastungsbewertung hinzufügen“ (Add utilization rating); without values „Keine Schwellen hinterlegt“ (No thresholds set)
Utilization rating capacity_rating_direction Selection yes „Höher ist schlechter“ / „Höher ist besser“ (Higher is worse / Higher is better)
Hourly rate hourly_cost Amount yes Cost rate per hour fallback value for personnel costs
Currency currency Selection yes Currency of the hourly rate
Supervisor supervisor_id Reference no Line supervisor (employee) descriptive
Assignee assignee_id Reference no Additional contact person (employee) descriptive

Header and tabs additionally show system values: booked workload of the next 30 days, „Geloggt (Monat)“ (Logged (month)), next „Abwesenheit“ (absence), assignments with role and effort.

Skills of the employee (employee_skill_map)

Section titled “Skills of the employee (employee_skill_map)”

Mapping table employee ⇄ skill without fields of its own. The „Skills“ tab shows per skill „Häufigkeit“ (frequency: other employees with the skill), „Zertifizierung notwendig“ (certification required) and the „Zertifizierung“ (certification) from the Skill. A certification is not recorded per employee; the flag belongs to the skill.

Related to Kind Required On archive On delete
Department (osp_employment_unit) belongs to no – reference cleared
Supervisor / Assignee (employee) belongs to no – reference cleared
User account (app_user) belongs to (1:1) no – reference cleared
Skill (skill) n:m via employee_skill_map – – mapping deleted along
Project member (project_member) has many – – deleted along
Booking, unavailability (employee_booking, employee_unavailability) has many – – deleted along
Time log (time_log) has many – – kept
Lead of project, program, portfolio; owner/responsible for risk, opportunity, measure; responsible for equipment; department head has many – – reference cleared

The employee cannot be archived.

  • Account linking. When an owner/admin invites a person, they choose a not-yet-linked employee or Aligia creates an invitation stub: first name, last name, e-mail; position empty, 40 h/week, 8 h/day, max. utilization 100 %, hourly rate 0 EUR, „Höher ist besser“. When the invitation is accepted, the account is linked by selection or e-mail match. The founder of an organization also receives a stub this way. Check the hourly rate after the invitation, otherwise personnel costs are calculated with 0.
  • Availability (client): available hours = working hours per week ÷ working days of the working time default (5 days × 8 hours, Saturday and Sunday off), capped by „Maximale tägliche Arbeitszeit“ (maximum daily working time), minus unavailabilities. See KPIs › Resources.
  • Optimizer cap (server): daily cap = min(max. daily working time, ⌊calendar hours × max. utilization % ÷ 100⌋); weekly cap = min(daily cap × working days, working hours per week). Values of 0 fall back to the calendar. The Optimizer does not check skills.
  • Utilization rating: If utilization lies between the lower and upper yellow threshold → yellow; below/above green or red depending on the direction. Without thresholds always green.
  • Hourly rate as fallback: Planned personnel costs from usages use the hourly rate of the project member, otherwise hourly_cost; a change re-prices all live planned values (Planned personnel costs). Actual personnel costs from approved times are booked only at the first approval and not re-valued afterwards (Actual personnel costs).
  • Master data character: Capacity, thresholds, hourly rate and skills take effect immediately in all projects, workload views and optimization runs that reference the employee. Deleting removes their project memberships, bookings and unavailabilities; the delete dialog does not name the affected data.

Utilization % (global and per project member), current utilization (team node), resource conflicts, effort (estimated), EVM weighting (effort × hourly rate). See ch. 13 › Resources and EVM.

Department · Skill · Project member · Employee booking · Time log · User