Reference & Data Model
Overview of budget & financial data
All financial data hangs off the project and is structured by cost items; program and portfolio only compute totals.
What defines this data type
Section titled “What defines this data type”Aligia manages finances exclusively at project level. Every project has Cost items (cost_item), for example material costs or personnel costs. Every cost item owns exactly one Budget (budget). Below the cost item sit two separate lists: Planned costs (planned_cost) as the living cost forecast and Cost events (cost_occurrence) as the immutable cost journal. Additional needs go through Budget requests (budget_request). The revenue side consists of the Order (order) with its Earning events (earning_occurrence) and the Benefit as a field on the project. Purchases (good_purchase) belong to procurement but generate cost events and are therefore listed here.
Programs and portfolios do not store their own costs. Their tabs „Budget“ and „Business Case“ sum up the values of their projects. Their only own field is the Budget goal (budget_goal), see Budget.
Entities in this chapter
Section titled “Entities in this chapter”Project (project) ── budget_goal · benefit · currency ├─ 1:n Cost item (cost_item) ── 1:1 Budget (budget) │ ├─ 1:n Planned cost (planned_cost) [manual | system] │ ├─ 1:n Cost event (cost_occurrence) [manual | system] │ └─ Budget ── 1:n Budget request (budget_request) ├─ 1:1 Order (order) ── 1:n Earning event (earning_occurrence) └─ 1:n Purchase (good_purchase) ──► rule ──► Cost event „Materialkosten aus Einkauf“
Server ledger: system_derived_record ── source ⇄ generated record (never in the client)Plan → expected → actual
Section titled “Plan → expected → actual”Budget (frame per cost item) budget.value │ ▼Planned costs (expected costs) planned_cost.cost_value │ created manually OR derived by the system (resource planning, │ purchase/stock request, expected risk costs); continuously │ updated: source changes → amount changes, source gone → row gone ▼Cost events (cost journal) cost_occurrence.cost_value │ manual OR by the system (time approval, ordered purchase, stock withdrawal, │ occurred risk, measures); purchase + stock withdrawal are kept │ current, everything else: once written = fact │ └─ Mistake? → „Korrigieren“ = reversal record (−amount, „Storno: …“) + optional corrected record. Original stays.Overview
Section titled “Overview”| Entity | Purpose | Where in the app |
|---|---|---|
Cost item (cost_item) |
Cost category with its own budget | Guides › Financial performance › „Budgetplan“ |
Budget (budget) |
Budget and budget goal of a cost item | Detail view of the cost item |
Planned cost (planned_cost) |
Expected costs | Detail view › „Kosten“ |
Cost event (cost_occurrence) |
Incurred costs | Detail view › „Kosten“ |
Earning event (earning_occurrence) |
Incoming payment for the order | „Business Case“ |
Benefit (project.benefit) |
Benefit of internal projects – in the user interface the project field benefit |
Guides › Profile |
Order (order) |
Order volume and order status | Create/edit project, profile |
Purchase (good_purchase) |
Order of a good | Guides › Procurement |
Budget request (budget_request) |
Request for more budget | Detail view › „Budgetanfragen“, Guides › Portfolio budget |
System-generated record (system_derived_record) |
Provenance of automatic records | Marker „Systemgeneriert“ |
Connections to other chapters
Section titled “Connections to other chapters”- Sources of automatic records: Time log, Employee usage, Procurement request, Risk, Risk measure, Opportunity measure.
- Rules: Ch. 12, KPIs: Budget KPIs, Value KPIs, EVM.
- Locks by phase: Phase rules.