Skip to content

Reference & Data Model

Project (project)

The project is the central object in Aligia: it carries master details, phase, target dates, working time model and financial performance, and is the root for work plan, team, finances and reports.

A Project is the actual initiative. Almost all other data (segments, members, costs, risks, reports, files) belongs to exactly one project. The phase controls what can still be changed in the work plan. (Data type: planning data, steering level)

Projekt & Portfolio › Projekte & Programme › Project. Master details in the tab „Projektsteckbrief“ (Project fact sheet) and in the dialog „Updaten“ (Update; action menu); phase via the phase label on the right of the header („Phase wählen“, Choose phase), status via the lifecycle buttons next to it („Pausieren“, „Fortsetzen“, „Abschließen“, „Wieder öffnen“). See Guides › Project fact sheet, Guides › Creating a project.

Field Technical Type Required Meaning Notes
Title title Text yes Project name
Key user_key Text yes Short code, e.g. PRJ-001
Project type project_type_id Reference no Type from the Project types
Project manager leader_id Reference (Employee) yes Main responsibility On creation a Project member with the lead flag is created automatically
Color color Selection yes Calendar/board color
Phase project_phase Selection yes Lifecycle phase see States
Status status Selection yes „Aktiv“ (Active), „Pausiert“ (Paused), „Erfolgreich abgeschlossen“ (Succeeded) or „Fehlgeschlagen“ (Failed) System; changeable only via the lifecycle actions; new projects are „Aktiv“

Classification („Organisatorische Einordnung“, „Standort“)

Section titled “Classification („Organisatorische Einordnung“, „Standort“)”
Field Technical Type Required Meaning Notes
Portfolio portfolio_id Reference yes Parent portfolio Changing it re-maps the assessments to the criteria of the new portfolio
Program program_id Reference no Optional program within the portfolio Only programs of the chosen portfolio selectable
Prioritization prioritization_rank Number („Rang“) no The higher the score, the higher the priority Appears as „Prio-Score“ on cards and in the portfolio strategy
Location address Address no Physical project or plant location
Tech structure technical_structure_id Reference no Linked Technical structure

Dates („Zeitplan & Kapazität“, „Eckdaten“)

Section titled “Dates („Zeitplan & Kapazität“, „Eckdaten“)”
Field Technical Type Required Meaning Notes
Planned start target_start_date Date yes Target start; anchor for all relative positions of the work plan
Planned end target_end_date Date yes Must be on or after the start date
Current schedule start / end scheduled_start_at / scheduled_end_at Date no Period committed from the optimizer System; set on Optimizer commit
Field Technical Type Required Meaning Notes
Working days per week working_days_per_week Number yes Working calendar of the project Default 5
Working hours per day working_hours_per_day Number yes Conversion duration ↔ calendar days Default 8

Financial performance („Budget & Wirtschaftlichkeit“)

Section titled “Financial performance („Budget & Wirtschaftlichkeit“)”
Field Technical Type Required Meaning Notes
Currency currency Selection yes Project currency Default EUR
Budget goal budget_goal Amount no Guide value, does not enter cost accounting
Economic benefit benefit Amount no Expected benefit over the lifetime For a customer order the fact sheet shows „Erwarteter Umsatz“ (Expected revenue) from the Order
Success probability success_probability_in_pct Number (%) no
Internal interest internal_interest_in_pct Number (%) no Internal interest / strategic significance
Project is a customer order – Yes/No no Shows the section „Kundenauftrag“ (Customer order) Creates or links an Order
Customer / requirements customer_id / customer_requirement Reference / Text no Customer and requirements specification Read-only in the fact sheet („Kundenauftrag“); currently not editable in the dialogs
Field Technical Type Required Meaning
General description description Text no
Project scope scope_description Text no Scope of delivery
Consequences of non-fulfillment consequences_of_non_fulfillment Text no
Specification specification_of_plant Text no Plant or requirements specification

The fact sheet also shows creation date and creator (system) as well as target and risk contribution from the Portfolio criteria.

Related to Kind Required On archive On delete
Portfolio belongs to yes archived along blocked
Program belongs to no kept reference cleared
Employee (lead) belongs to no kept reference cleared
Project type belongs to no kept reference cleared
Technical structure belongs to no kept blocked
Segment, Task, Event has many – archived along deleted along
Project member, Cost item, risks, reports, files has many – archived along deleted along

Phases (project_phase), labels from „Phase wählen“:

Value Label
initial Initialisierung
definition Definition
planning Planung
execution Umsetzung
closing Abschluss

Status (status), labels from the status label next to the phase:

Value Label Meaning
active Aktiv (Active) The project is running; the phase can be changed
paused Pausiert (Paused) The project rests; the phase is frozen
succeeded Erfolgreich abgeschlossen (Succeeded) End state; possible only from the phase „Umsetzung“ onward
failed Fehlgeschlagen (Failed) End state; possible from any phase
early phases (planning objects can be created, Gantt editable)
┌───────────────────────────────────────────────────┐
│ Initialization ⇄ Definition ⇄ Planning │
└───────────────┬───────────────────────────▲───────┘
│ "Execution" chosen │ step back
▼ │
Optimizer opens Optimization committed?
"Übernehmen" (with access) yes → warning "Discard
sets Execution optimization?", rollback (with access)
│ no → phase set directly
▼ │
Execution ⇄ Closing ─────────────┘

The status is independent of this and changes only via the lifecycle actions:

Active ⇄ Paused ("Pausieren" / "Fortsetzen")
│ │
└───┬────┘ "Abschließen"
▼
Succeeded (from Execution)
Failed (any phase)
│ "Wieder öffnen"
▼
Paused

Transition rules (code: project layout, system_optimize_commit, system_optimize_rollback):

  • Every change is triggered manually; the phase never changes by itself.
  • Early phase → Execution: instead of setting the phase, the „Projekt-Optimierung“ (Project optimization) opens. Only committing a result writes execution (forward only, server-side; needs access to optimization) and fills „Aktuelle Planung“ (Current schedule).
  • Execution or later → early phase: if an optimization was ever committed, „Optimierung verwerfen?“ (Discard optimization?) appears. The rollback removes future optimizer bookings and open procurement requests, restores positions and assignments and sets the phase server-side (needs access to optimization, otherwise „Du hast keinen Zugriff zum Zurücksetzen.“). Without a commit the phase is set directly.
  • All other phase changes (within the early phases, Execution → Closing) are saved directly.
  • End states are not phases: you set „Erfolgreich abgeschlossen“ and „Fehlgeschlagen“ via „Abschließen“ (Close), not in the „Phase wählen“ dialog. „Erfolgreich abgeschlossen“ is possible only from „Umsetzung“ onward; „Fehlgeschlagen“ at any time. „Wieder öffnen“ (Reopen) brings a closed project back to the status „Pausiert“.
  • Phase frozen: While the project is not „Aktiv“, its phase cannot be changed. The database enforces this. Committing an optimization is then rejected, and so are rolling it back and starting an optimization run.
  • Planning objects only in early phases: new segments, work packages, tasks, milestones, gates and events can only be created in Initialization, Definition and Planning; the Gantt is read-only from Execution on. This lock is an interface rule, not a database lock. See Phase rules.
  • Default cost items: on creation every project receives seven cost items (material, staff, other OPEX, investments, repayment, interest, …); see Default cost items.
  • Lead = member: the project manager is created as a project member with the role „Projektleitung“ (Project management) and the lead flag.
  • Assessments: on creation and on a portfolio change, empty assessment rows are created for all criteria of the portfolio.
  • Closure event: every closure is stored as an immutable event (project_closure) with outcome, reason (optional, at most 2000 characters) and time. „Wieder öffnen“ only notes the reopening on the event.
  • Bookings: „Pausieren“ and „Abschließen“ release planned bookings from today on, manually created ones too. This cannot be undone; past entries stay.
  • Delete: a project can be deleted only while it is „Aktiv“, in an early phase, without a committed optimization run and with nothing recorded: costs/revenue, procurement, time entries, history (closure events). Otherwise deleting is rejected with error ZGV01, and the dialog offers „Als fehlgeschlagen abschließen & archivieren“ (close as failed & archive). A committed run has to be rolled back first.
  • Archiving only hides and does not change any KPI.
  • Archiving archives work plan, team, finances and reports along with it; see Lifecycle.

Progress, delay (scheduled_end_at − target_end_date), schedule index, planned duration vs. current schedule, phase, phase funnel, share of failed projects: Progress & dates, Status, Counts. EVM baseline: EVM.

Which projects a KPI counts depends on the status, never on archiving:

  • Stock KPIs (tasks, risks, capital, project count) count „Aktiv“ and „Pausiert“.
  • Progress KPIs count „Aktiv“ only.
  • Forecast and EVM count „Aktiv“ projects in „Umsetzung“ or „Abschluss“ only.
  • Fact KPIs (costs, revenue, counters of recorded data) count every non-deleted project, failed and archived ones too.
  • Flow KPIs („Anteil gescheiterter Projekte“) read the closure events.

Segment · Optimization · Guides › Project lifecycle · Guides › Gate decision & phase change · Guides › Closing a project