Skip to content

Reference & Data Model

How to read this part

Part B is a reference to the data stored by Aligia. It complements the guides but does not replace them.

This part is aimed at power users, administrators, controllers and integrators. It assumes that you already use Aligia and know what a project, a task or a budget is in the interface. If you are new to Aligia, it is better to start with Guides › How to read this handbook.

The guides explain how you use Aligia: views, workflows, roles. This part explains what is stored and what the system does with it. Where the guides are organized by app, this part is organized by data type. A task appears in the guides under Work management and Project view; here it appears once, in chapter 3, with all fields and relations.

Chapter Content in one sentence
1 Organization & access Organization, users, roles, permissions and settings: who may access what.
2 Master data Employees, departments, skills, material, specifications, equipment, project types and work calendars: the catalogs that all projects share.
3 Planning data Portfolio, program, project, segment, work package, task, milestone, gate, event, dependency and technical structure: the undertaking and its plan.
4 Resource data Project members, planned efforts, bookings, absences, material requirements and procurement requests: who and what is scheduled when.
5 Time tracking data Timer, time log, time entry and label: the hours actually worked.
6 Budget & financial data Cost items, budgets, plan and actual bookings, earnings, benefits, orders, purchases and budget requests: money in the plan and in the actuals.
7 Risk & opportunity data Risks, opportunities, their measures and the portfolio criteria: uncertainty and strategy.
8 Issues Issues and comments: matters that run alongside the work plan.
9 Knowledge data Status reports, assessments and key takeaways: documented knowledge.
10 Files & Drive Storage locations, folders, files, versions and links.
11 Automation & AI Agents, skills, MCP servers, LLM connection, workflows, triggers, executions and conversations.
12 System logic & automation What Aligia itself generates, locks or converts, with trigger and formula.
13 KPIs All KPIs with meaning, calculation and where to find them.
14 Reference lists States, glossary and index.

Every entity page follows the same template. This is how you read it:

  1. Purpose – What the record is for, with the data type label in parentheses.
  2. Where in the app – Menu path or tab, plus a link into the guides.
  3. Fields – Table with field, technical name, type, required, meaning and notes. Types are text, number, amount, date, yes/no, selection or reference.
  4. Relations – Table with target entity, kind (belongs to, has many, n:m), required and the behavior on archive and on delete. The four rules are explained in Lifecycle of a record.
  5. States – only if the entity has a state: values with German label and transitions.
  6. Rules & automation – Validations, locks and what the system generates from the record, with a link into chapter 12.
  7. KPIs – only if the entity feeds into KPIs, with a link into chapter 13.
  8. See also – Cross-references.

Small helper entities such as assignment tables, labels or participant lists appear as a section on the page of their main entity.

Notation Meaning
Task Business term, bold on first occurrence
task technical name of the entity or field, in code font
Target end (target_end_date) business name first, technical name after it
Required: yes Field must be filled, otherwise the record cannot be saved
System Value is set by Aligia, not by you; in the text as > **System:**
„Phase wählen“ UI label, exactly as in the app
Projekt & Portfolio › Portfolios Menu path