Reference & Data Model
Overview: What the system creates
All automations on one page: trigger, result, chapter link, and the difference between “created once” and “continuously reconciled”.
Two kinds of automation
Section titled “Two kinds of automation”Aligia has two behaviors for records the system creates:
- Created once (create-only): The system creates the record on the first matching event and never touches it again. It is neither recalculated nor deleted, even if the source changes. This applies to actual bookings (
cost_occurrence), except the continuously reconciled material costs from purchases, and to a project’s default cost items. An actual booking is a fact; it is corrected only with a reversal booking (see Actual booking). - Continuously reconciled (reconcile): The system keeps the derived record in sync with the source at all times: create when the condition is met; update when values change; remove when the condition no longer holds or the source is deleted. This applies to planned items (
planned_cost) and stock movements (stock_inbound_outbound).
All system-generated cost rows carry the flag „Systemgeneriert“ (system-generated) and a visible „Quelle“ (source) (detail view of the cost item, section „Kosten“). They cannot be changed by users (see Locks & delete protection).
Rule overview
Section titled “Rule overview”| Trigger | Result | Behavior | Page |
|---|---|---|---|
| Project is created | 7 cost items with budget 0 in project currency | created once | Default cost items |
| Resource usage (employee) created/changed; hourly rate changed; task moved to another project | Planned item „Personalkosten“ = hours × count × rate | continuous | Planned personnel costs |
| Time log first set to „Genehmigt“ | Actual booking „Personalkosten“ = hours × rate | created once | Actual personnel costs |
| Purchase in base class „Bestellt“ or „Geliefert“ | Actual booking „Materialkosten“ (net, discount/surcharge included); in „Geliefert“ additionally a goods receipt | continuous | Material costs from purchases |
| Procurement request of type purchase | Planned item material until a linked purchase is ordered or delivered | continuous | Procurement |
| Procurement request of type stock | Goods issue; planned item while „Offen“; actual booking on „Erledigt“ | continuous / created once | Procurement |
| Risk active | Planned item „Erwartete Risikokosten“ = damage × effective probability | continuous | Risk and opportunity costs |
| Risk occurred (date + damage set) | Actual booking „Risiko eingetreten“ | created once | Risk and opportunity costs |
| Measure on an occurred risk/occurred opportunity | Actual booking with the measure’s costs | booked once (see limitations) | Risk and opportunity costs |
| Budget request set to „Genehmigt“ | Budget of the cost item increases by the requested amount | client logic | Budget request |
| Optimization „Übernehmen“ | Dates, bookings, purchase requests, phase „Umsetzung“, EVM baseline | procedure, reversible | Apply optimizer |
| Choose phase | Direct change, optimizer coupling or rollback | rules | Phase rules |
| Approval, system rows, deletion | Locks and delete protection | rules | Locks & delete protection |
| Criterion, agent, invitation | Assessment row, user account, employee stub | follow-up data | Follow-up data |
| Any data change | KPIs are recalculated | pipeline | KPI recalculation |
Connections to other chapters
Section titled “Connections to other chapters”The cost rules write exclusively into chapter 6 Budget & financial data. Their sources lie in Resource data, Time tracking data and Risk & opportunity data. The optimizer changes Planning data and Resource data. The KPIs derived from them are explained in chapter 13.