Reference & Data Model
Resource data overview
Resource data is transactional data: it arises per project and per task and references master data such as employees, equipment and material.
What defines this data kind
Section titled “What defines this data kind”Resource data answers three questions: Who belongs to the project (project member)? How much work is planned per task (employee usage, equipment usage, good usage)? When exactly does it take place (booking)? In addition there are unavailabilities (absence, maintenance) that take away capacity, and procurement requests that request missing material.
All entities in this chapter are synchronized business data. Anyone whose grant at their place allows it may read and edit them (see Access: who may do what).
Entities and relations
Section titled “Entities and relations”Employee (ch. 2) ──┐ Equipment (ch. 2) Good variant (ch. 2) │ optional │ │ ▼ ▼ ▼Project ──► Project member ◄── parent Equipment usage Procurement request │ (project_member) member (equipment_usage) (good_procurement_request) │ n:m skills │ ▲ ▼ ▼ │ optionalTask ──► Employee usage Equipment booking Good usage ──► Task (employee_usage) (equipment_booking) (good_usage) │ │ ▼ ▼ Employee booking Component / Node (ch. 3) (employee_booking)
Employee ──► Employee unavailability (employee_unavailability)Equipment ──► Equipment unavailability (equipment_unavailability)Four views of work
Section titled “Four views of work”Aligia distinguishes four quantities per person and task. They appear side by side in the task sheet „Ressourceneinsatz“ (Resource usage) (columns „Plan-Aufwand“, „Ist-Aufwand“, „Rest“ — planned effort, actual effort, remaining):
Source Unit Where visible─────────────────────────────────────────────────────────────────────────────────Planned Employee usage Hours „Ressourceneinsatz“ › Plan-Aufwand,effort estimate_effort_in_hours org chart › „Zuweisungen“ › Plan │ ▼ Scheduling (manual or Optimizer)Booking Employee booking Date + „Ressourceneinsatz“ › sub-rows start_at … end_at time „Buchung“; resource Gantt; workload │ ├─ minus Unavailability Period Unavailabilities; Gantt bars; │ employee_unavailability conflict „Gebucht & abwesend“ ▼Logged time Time entry (ch. 5) Hours „Ressourceneinsatz“ › Ist-Aufwand, time_entry via time_log org chart › „Zuweisungen“ › IstPlanned effort is the estimate. Bookings distribute it onto concrete days. Unavailabilities reduce the available hours and create conflicts when a booking falls into them. Logged time is reality; the column „Rest“ shows estimate − actual or bookings − actual.
Entities of this chapter
Section titled “Entities of this chapter”| Entity | Purpose | Where in the app |
|---|---|---|
Project member (project_member) |
Role of a person in the project; unfilled = resource demand with skill requirements | Project › „Ressourcen“ › „Team“ (Guides › Resources) |
Employee usage (employee_usage) |
Planned effort of a project member per task | Task › „Ressourceneinsatz“ (Guides › Workspace) |
Equipment usage (equipment_usage) |
Equipment that a task needs | Task › „Ressourceneinsatz“ |
Employee booking (employee_booking) |
Concrete period in which an employee works on a task | Task › „Ressourceneinsatz“; resource Gantt (Guides › Resource workload) |
Equipment booking (equipment_booking) |
Concrete period of an equipment usage (Optimizer only) | Resource workload › „Equipments“ |
Unavailability (employee_unavailability, equipment_unavailability) |
Absence or downtime of a resource | Multi-project management › „Ressourcenausfälle“ (Guides › Unavailabilities) |
Good usage (good_usage) |
Material or technical node that a task consumes | Task › „Ressourceneinsatz“ › goods |
Procurement request (good_procurement_request) |
Request for material from stock or purchase | Project › „Beschaffung“; engineering (Guides › Procurement) |
Connections to other chapters
Section titled “Connections to other chapters”- Master data (ch. 2): Employees, skills, equipment, materials and the working calendar are only referenced here, see Employee, Skill, Equipment, Material.
- Planning data (ch. 3): Usages hang on tasks; good usages reference components and nodes; bookings arise during optimization.
- Time tracking (ch. 5): logged time yields the actual effort, see Time entry.
- Finance (ch. 6, 12): planned effort becomes planned personnel costs, procurement becomes material costs.
- KPIs (ch. 13): Resources & workload, Procurement.