Skip to content

Reference & Data Model

Glossary

All technical terms of this part, alphabetically; entities with their technical name, each entry with a link to the page that explains it.

  • Dependency (Abhängigkeit) (project_item_dependency) – Sequence relation (finish to start, start to start, finish to finish, start to finish) between tasks, milestones and gates; a constraint for the optimizer, moves nothing by itself. → Dependency
  • Volume (Ablage) (volume) – Root of a file tree; owned by the organization or a project; per owner one volume „Dateien“ (files) and one flat volume „Anhänge“ (attachments). → Volume
  • Subscriber (Abonnent) (issue_subscriber, task_subscriber) – User account that follows an issue or a task without editing it. → Issue
  • Closure event (Abschlussereignis) (project_closure) – Immutable entry for every project closure with outcome, reason (optional) and time; source of the flow KPIs. → Project
  • Department (Abteilung) (osp_employment_unit) – Node of the organization tree with a head; structures employees and gives issues a responsibility, without permissions or planning logic. → Department
  • AC (Actual Cost) – Actual costs to date (only cost occurrences with date ≤ today) as a building block of Value CPI and EAC. → Earned value
  • Admin – Role that manages the organization: members, roles, teams, grants, base access, audit log, credentials and settings. Needs a grant for data like everyone. → Roles
  • Agent (agent) – The organization’s own AI specialist with instructions, model, step limit, skills and MCP servers; receives a service account on activation. → Agent
  • Agent skill (Agenten-Skill) (agent_skill) – Reusable instruction (prompt) that Polaris and agents load on demand. → Agent skill
  • Activity history (Aktivitätsverlauf) – Log of all changes to a record with author, field, old and new value; machine changes carry a tag such as „System“ or „Optimierung übernommen“. → What every record has
  • Allocation (Allokation) – Assignment of a technical component or a structure folder to a task; creates a good usage. → Technical component
  • Work package (Arbeitspaket) (task_package) – Optional group of tasks in a segment without its own time position. → Work package
  • Archive (Archivieren) – Hide a record together with its subordinates everywhere; reversible at any time with „Wiederherstellen aus Archiv“, also offline; changes no KPI. → Lifecycle
  • Article (Artikel) (good_variant) – Orderable unit of the material catalog with SKU, unit price, stock data and specification values; in Engineering „Gut“ or „Gut-Variante“. → Material
  • Task (Aufgabe) (task) – Plannable unit of work with status, position and duration in the plan, assignment, time window and checklist. → Task
  • Order volume (Auftragsvolumen) (order.order_volume) – Contractually expected revenue of the customer order; basis of all revenue KPIs. → Customer order
  • Unavailability (Ausfall) (employee_unavailability, equipment_unavailability) – Period in which an employee is absent or a piece of equipment is not ready for use; reduces capacity and creates conflicts. → Unavailability
  • BAC (Budget at Completion) – Total budget of the baseline: budget target of the project, otherwise the sum of the cost item budgets. → Earned value
  • Badness – Internal sort number “worst first” from traffic lights, delay, K.O. violations and progress. → Status & traffic lights
  • Baseline (project_baseline) – Plan state of a project frozen once (plan window, BAC, task weights) as the basis for earned value; no Gantt display. → Earned value
  • Procurement request (Beschaffungsaufforderung, BAUF) (good_procurement_request) – Request for a good variant from stock or purchase with quantity, dates and status; creates planned items and stock movements. → Procurement request
  • Assessment (Bewertung) (target_assessment, risk_contribution_assessment) – A project’s answer yes/no/open to a portfolio criterion. → Target assessment criterion
  • Relation (Beziehung) – Connection between two entities (belongs to / has many / n:m), required or optional, with a rule for archiving and deletion. → Basic terms
  • kept (bleibt) (keep) – Delete rule: the dependent record remains unchanged including its reference. → Lifecycle
  • Booking (Buchung) (employee_booking, equipment_booking) – Concrete period of a resource on a task; manual or from the optimizer. → Employee booking
  • Budget (budget) – Financial frame of exactly one cost item; increases only through manual input or an approved budget request. → Budget
  • Budget request (Budgetanfrage) (budget_request) – Request for additional budget of a cost item with status open/approved/rejected/withdrawn; never deleted. → Budget request
  • Budget target (Budgetziel) (budget_goal) – Optional target value on the project, program, portfolio or per cost item; feeds into no budget plan column, but into server KPIs and the BAC. → Budget
  • CDC (Change Data Capture) – Triggering a workflow on database changes (create or update in a table). → Trigger
  • Opportunity (Chance) (chance) – Possible success event of a project, mirror image of the risk; creates no planned item. → Opportunity
  • create-only – Policy “create once, never change or remove” (actual bookings, default cost items). → Rule engine
  • File (Datei) (file) – Shell with name, category, extension and reference to the active version; readable only with a ready, scanned version. → File
  • File link (Dateiverknüpfung) (file_link) – Edge object → file (attachment); removable without losing the file. → File link
  • File version (Dateiversion) (file_version) – Concrete content of a file with upload and virus status; new versions only through engine editing. → File version
  • Data type (Datenart) – Group of entities with the same role (master, planning, resource, time tracking, financial, risk, issue, knowledge, platform, computed data); determines the chapter. → Basic terms
  • Deal-breaker gate – Gate with the flag „Projektabbruch bei Fehlschlag“; when failed only a warning „K.-O.-Kriterium verletzt“, no lock. → Gate
  • Delegate (Delegieren) (delegate_id) – Handing an issue or a task over to Polaris or an active agent, independent of the assignment; starts a conversation. → Issue
  • Deployment (workflow_deployment) – Immutable, versioned form of a workflow’s rules document; the engine reads only this. → Workflow deployment
  • Service account (Dienstkonto) – Technical user account: system account, Polaris account or account of an activated agent (origin ≠ auth). → Service accounts
  • Execution (Durchführung) (workflow_execution) – One run of a workflow or agent with status, trigger, trace and child runs; private with an admin window. → Execution
  • EAC (Estimate at Completion) – Forecast total costs = AC + (BAC − EV) ÷ work-based CPI. → Earned value
  • Purchase (Einkauf) (good_purchase) – Order of a good with price, quantity, conditions and status; books material costs from base class „Bestellt“ and keeps them current, and from „Geliefert“ additionally stock. → Purchase
  • Invitation (Einladung) (invitation) – Open access for an e-mail address with a preset role and optional employee. → Roles
  • Earning (Einnahme) (earning_occurrence) – Recorded incoming payment on the customer order; freely editable. → Earning
  • Assessment (Einschätzung) (state_assessment) – Traffic light value green/yellow/red plus comment for one area of a status report. → Assessment
  • Entity (Entität) – Kind of record with a business and a technical name (e.g. task / task). → Basic terms
  • Equipment (equipment) – Device, vehicle or tool with hourly rate and active period, scheduled like a person. → Equipment
  • Key takeaway (Erkenntnis) (key_takeaway) – Recorded lesson (takeaway) with category and type; visible upward. → Key takeaway
  • EV (Earned Value) – BAC × share of completed task weights (0/100 method). → Earned value
  • Field (Feld) – Property of a record with type (text, number, amount, date, yes/no, selection, reference) and required flag. → Basic terms
  • Freeze – Lock on an approved time log and its time entries; only the status remains changeable. → Locks
  • Freshness budget (Frische-Budget) – Maximum age (60 s) of a stored KPI value before the server recomputes it live on read. → Freshness
  • Early phases (Frühe Phasen) – Initialization, Definition, Planning; only here can planning objects be created and the Gantt edited. → Phase rules
  • Guest (Gast) – Member who never does more than the guest list allows and gets grants only on single projects or drives; base access never reaches them. → Access
  • Gate (gate_criteria) – Checkpoint in the work plan with status pending/passed/failed and deal-breaker flag; technically blocks no phase change. → Gate
  • Base access (Grundzugriff) – One grant on the whole organization for the team “All members”, level Off, Company data, View or Edit. → Access
  • Good usage (Gütereinsatz) (good_usage) – Material or structure node consumed by a task, optionally with the supplying procurement request. → Good usage
  • Provenance ledger (Herkunfts-Ledger) (system_derived_record) – Internal table with rule key, source and target of every derived row; never in the client. → Rule engine
  • Initiative (chance_action) – Preparatory or reactive action on an opportunity with opportunity increase in percentage points, costs and status. → Initiative
  • Issue (issue) – Ticket outside the work plan with state, priority, due date, assignment and optional delegation. → Issue
  • Actual booking (Ist-Buchung) (cost_occurrence) – Cost item that actually occurred; immutable, correction only via reversal; sum = actual costs. → Actual booking
  • Actual costs (Ist-Kosten) – Sum of a project’s actual bookings; server and view may differ. → Budget & costs
  • KPI value (Kennzahlwert) (kpi_value) – KPI value computed by the server per project, program, portfolio or organization; read-only. → KPI recalculation
  • Comment (Kommentar) (issue_comment, task_comment) – Markdown message in the history of an issue or a task, with replies one level deep; the only channel of delegated agents. → Issue comment
  • Component requirement (Komponentenanforderung) (technical_structure_requirement) – Placeholder with material type and technical requirements, not yet with a fixed good. → Component requirement
  • Cost item (Kostenart) (cost_item) – Category of a project budget with its own budget (material, personnel, other operating expenses, investments, loan repayment, interest payments, dividends). → Cost item
  • KPI (Kennzahl) – Non-editable value derived from records (sum, count, ratio or verdict) per scope. → KPI overview
  • Customer order (Kundenauftrag) (order) – Order of an external project with order volume and order status; at most one per project. → Customer order
  • Label (issue_label) – Colored tag for issues (organization-wide, with filter). → Issue
  • Running timer (Laufender Timer) (active_timer) – Private, cross-device draft of the timer currently measuring. → Running timer
  • Live synchronization (Live-Synchronisation) – Local copy of the data; changes are distributed to all devices immediately; deleting needs a connection, archiving does not. → Data flow
  • LLM provider (LLM-Anbieter) (llm_provider) – The organization’s own access to a language model service (bring your own key). → LLM provider
  • LLM model (LLM-Modell) (llm_model) – Concrete model of an own provider with facts, prices and check status. → LLM model
  • Delete (Löschen) – Permanently remove a record and dependent data, with preview and a short undo; soft delete. → Lifecycle
  • Measure (Maßnahme) (risk_action) – Preventive or reactive action on a risk or gate with risk reduction in percentage points, costs and status. → Measure
  • Material category (Materialkategorie) (good_type) – Top material level, defines specifications; in Engineering „Materialtyp“. → Material
  • MCP (Model Context Protocol) – Standard by which an external system exposes its functions to AI as tools. → MCP server
  • MCP server (MCP-Server) (agent_mcp_server) – Connection to an external system with endpoint, connection state, connection policy and Polaris enablement. → MCP server
  • MCP tool (MCP-Tool) (agent_mcp_tool) – Single function of an MCP server with permission allow/ask/deny; only allow takes effect. → MCP tool
  • Milestone (Meilenstein) (milestone) – Point in time without duration in a segment with a reached flag and time window. → Milestone
  • Employee (Mitarbeiter) (employee) – Person with capacity, hourly rate and skills; user account optional; cannot be archived. → Employee
  • Employee usage (Mitarbeitereinsatz) (employee_usage) – Planned effort of a project member per task with cadence; source of the planned personnel costs. → Employee usage
  • Member (Mitglied) – Role without administrative rights; what a member may do with data comes from their grants. → Roles
  • deleted along / archived along (mitlöschen / mitarchivieren) (cascade) – Rule: the dependent record follows its target. → Lifecycle
  • Lookup list (Nachschlageliste) – List every member reads without a grant: skills, project types, good types and similar; changing it needs a grant on the whole organization. → Access
  • User account (Nutzerkonto) (app_user) – Mirror of a sign-in identity in the app; author, editor and delegate in all data; linkable 1:1 to an employee. → User account
  • Optimization run (Optimierungslauf) (optimization_run) – Stored computation of the optimizer for 1 to 50 projects with status and result; only „Übernehmen“ writes the plan. → Optimization run
  • Folder (Ordner) (folder) – Structuring element of a volume; names unique per level; no moving between volumes. → Folder
  • Organization (Organisation) (organization) – Tenant and closed data space; every account belongs to exactly one organization. → Organization
  • Organization settings (Organisationseinstellungen) (org_settings, org_llm_task_model) – AI models per task and platform model switch for all members; owner/admin only. → Settings
  • Owner – Creator of the organization; unique, not transferable, cannot be downgraded or removed; manages like an admin and gets full access on the whole organization when creating it. → Roles
  • Personal settings (Persönliche Einstellungen) (user_settings) – Preferences per user account, across devices; only your own row. → Settings
  • Phase (project_phase) – Lifecycle stage of a project or program (Initialization … Closing; a free value for programs); controls the editability of the work plan. End states are not phases, see project status. → Project
  • Planned item (Plan-Position) (planned_cost) – Expected cost item; manual or continuously reconciled by the system. → Planned item
  • Polaris – Built-in AI assistant living in the code without its own agent record; acts with the user’s permissions. → Service accounts
  • Portfolio (portfolio) – Top steering level to which every program and project is assigned; carrier of criteria and prioritization. → Portfolio
  • Principal (Prinzipal) – Party responsible for an action: person, agent, the organization’s service account or platform service. → Service accounts
  • Prioritization / priority score (Priorisierung / Prio-Score) (prioritization_rank) – Manually assigned rank from the portfolio prioritization; weights the delay in the multi-project optimizer. → Strategy & prioritization
  • Private data (Private Daten) – Conversations (creator only), executions (creator + admin), own settings and timers. → Private data
  • Product (Produkt) (good) – Middle material level with unit quantity and unit; bundles articles. → Material
  • Program (Programm) (program) – Optional bundling of projects within a portfolio with its own phase, dates and budget target. → Program
  • Project (Projekt) (project) – The undertaking: master data, phase, target dates, working time model, financial performance; root for work plan, team, finances and reports. → Project
  • Project member (Projektmitglied) (project_member) – Role of a person in exactly one project; without an employee a resource demand; descriptive, no permissions. → Project member
  • Project status (Projektstatus) (project.status) – State of a project independent of the phase: Active, Paused, Succeeded or Failed; programs have none. → Project
  • Project type (Projekttyp) (project_type) – Classification of projects and programs without templates, rules or permissions. → Project type
  • PV (Planned Value) – BAC × share of the plan window elapsed to date. → Earned value
  • reconcile – Policy “continuously reconcile”: create, update, remove along with the source (planned items, stock movements). → Rule engine
  • Rule engine (Regel-Engine) – Server component that creates derived records from data changes and records them in the provenance ledger. → Rule engine
  • Resource demand (Ressourcenbedarf) – Project member without an assigned employee, whose skills are requirements. → Project member
  • Resource conflict (Ressourcenkonflikt) – Overlap of two bookings, or of a booking and an unavailability, of the same resource. → Resources & workload
  • Risk (Risiko) (risk) – Possible damage event of a project with possible damage, probability of occurrence and rating; creates „Erwartete Risikokosten“. → Risk
  • Risk contribution (Risikobeitrag) – Weighted share of affirmed active risk criteria in percent; Y axis of the priority matrix. → Risk assessment criterion
  • Risk assessment criterion (Risikobewertungskriterium) (risk_contribution) – Weighted strategic risk question of a portfolio, independent of the risk register. → Risk assessment criterion
  • Risk exposure (Risikoexposition) – Server KPI Σ possible damage × probability of occurrence over all risks of a project, without measures, including inactive ones. → Risks & opportunities
  • Rollup – Sum formed by the server of the stored project values of a program or portfolio; the status decides which projects count, never archiving. → Freshness
  • Rollback (optimizer) (Rücknahme) – Undoing all applied runs for the future when stepping back into an early phase; needs access to optimization. → Apply optimizer
  • Scope – Reference object of a KPI: organization, portfolio, program or project. → KPI overview
  • Segment (segment) – Section of the project and mandatory container for work packages, tasks, milestones and gates. → Segment
  • Skill (skill) – Cataloged ability with optional certification requirement; employees have them, project roles require them. → Skill
  • Spec matching – Evaluation of all variants of a material type against the technical requirements and conversion of the requirement into a component. → Component requirement
  • Specification value (Spezifikationswert) (spec_value) – Value of an article for an attribute (number, range, text, selection, yes/no). → Specification
  • SPI (schedule performance index) – EV ÷ PV; below 0.9 red, up to 1.0 yellow, above 1.0 green. → Earned value
  • Master data (Stammdaten) – Organization-wide reference data without project reference; cannot be archived, instead „Aktiv“/„Inaktiv“. → Master data
  • Status report (Statusbericht) (state_report) – Dated snapshot of a project or program with six traffic light assessments. → Status report
  • Reversal booking (Storno-Buchung) – Negative actual booking „Storno: …“ to correct an unchangeable booking; created via „Korrigieren“. → Actual booking
  • Structure folder (Strukturordner) (technical_structure_node) – Structuring node of the technical structure (plant, assembly, trade); in dialogs „Knoten“ (node). → Structure folder
  • System-generated (Systemgeneriert) – Flag of a record created by the system (planned item, actual booking, procurement request); unchangeable for users. → Data flow
  • Cadence (Taktung) (cadence_kind) – Distribution of the planned effort over the task: „Durchgehend“, „Einmalig“, „Alle…“. → Employee usage
  • Technical requirement (Technische Anforderung) (technical_structure_spec_req) – Condition per specification (=, ≥, ≤, between, one of) of a component requirement. → Component requirement
  • Technical component (Technische Komponente) (technical_structure_good) – Concrete good variant with required quantity in a structure folder; starting point for allocation and procurement. → Technical component
  • Technical specification (Technische Spezifikation) (good_type_spec) – Attribute of a material category with data type and unit; inherited by subcategories. → Specification
  • Technical structure (Technische Struktur) (technical_structure) – Tree of structure folders, components and requirements shared by one or more projects. → Technical structure
  • Event (Termin) (event) – Meeting in the project (digital or physical) with a placeholder position in the plan and optional calendar slot. → Event
  • Timer (timer) – Stopped, not yet assigned period with date, start and end time. → Timer
  • Trend – Computed comparison of an assessment with the previous report (better / worse / unchanged). → Assessment
  • Trigger (workflow_trigger) – Start condition of a workflow from the on field of its rules document: manual or CDC; exactly one per deployment version. → Trigger
  • Apply (optimizer) (Übernahme) – Binding write of an optimization run into dates, bookings, procurement and phase „Umsetzung“; needs access to optimization. → Apply optimizer
  • Subtask (Unteraufgabe) (subtask) – Checkable step in a task’s checklist (“checkpoint”) without effort or time position. → Subtask
  • Conversation (Unterhaltung) (agent_conversation) – Private chat with Polaris or an agent with title, model, reasoning budget and read status. → Conversation
  • Value CPI – (benefit + revenues to date) ÷ AC; Aligia’s cost index instead of the classic CPI; needs no baseline. → Earned value
  • blocked (verhindert) (restrict) – Delete rule: the target cannot be deleted while dependents exist. → Lifecycle
  • reference cleared (Verweis lösen) (detach) – Delete rule: the dependent record remains, the reference is emptied. → Lifecycle
  • Virus scan (Virenprüfung, AV) (av_status) – Automatic scan of every file version; only „Geprüft“ releases reading. → File version
  • Probable damage (Wahrscheinlicher Schaden) – (occurrence % − Σ reduction) ÷ 100 × possible damage + measure costs, active risks only, without discarded measures. → Risks & opportunities
  • Economic benefit (Wirtschaftlicher Nutzen) (project.benefit) – Expected benefit of a project without an order; counts toward the business case profit only in the status „Erfolgreich abgeschlossen“ (Succeeded), toward the Value CPI immediately. → Economic benefit
  • Economic value (Wirtschaftlicher Wert) – Order volume + benefit; server KPI per project with rollup. → Financial performance
  • Workflow definition (Workflow-Definition) (workflow_definition) – Header (name, owner) of a rules workflow; Polaris writes the rules document. → Workflow definition
  • Time entry (Zeiteintrag) (time_entry) – Time span from–to within a time log; in the „Zeitenbuchung“ dialog. → Time entry
  • Time log (Zeiterfassung) (time_log) – Header of the time recorded by a person on one day for a project and optionally a task; carries status, billability and description. → Time log
  • Target contribution (Zielbeitrag) – Weighted share of affirmed active portfolio targets in percent; X axis of the priority matrix. → Target assessment criterion
  • Target assessment criterion (Zielbewertungskriterium) (portfolio_target) – Weighted strategic target question of a portfolio; every project answers with an assessment. → Target assessment criterion
  • Grant (Zugriff) – What lets a person or team do something at a place (whole organization, unit, portfolio, program, project, drive) and everything below it, unless restricted. → Access
  • Access profile (Zugriffsprofil) – Lists what a grant allows: Viewer, Editor, Lead, Full access or a profile of the organization. → Access
  • State (Zustand) – Selection field with a fixed value list that describes the processing stage; set by users, a workflow or the system. → States and selection values