Guides
Technical structure
The technical structure models what is built in a project: as a tree of folders, components and requirements with technical specifications.
What it is
Section titled “What it is”The technical structure is the digital twin of the deliverable. It organizes a plant into structure folders and attaches the required goods from the Material catalog to them. Where the concrete good is still open, a requirement with minimum and maximum values takes its place. Aligia continuously checks whether an assigned good meets the required specifications.
Where it appears
Section titled “Where it appears”In the project tab „Engineering“. If a project has no structure yet, the tab shows „Keine Tech-Struktur vorhanden“ (no tech structure available) and offers „Tech-Struktur hinzufügen“ (add tech structure). A structure can be used by several projects. The header shows which projects share it. The page is here because the tool is complex.
Structure
Section titled “Structure”On the left is the tree under „Anordnung“ (arrangement), on the right the detail panel of the selected entry.
| Entry | Meaning | Tabs in the detail panel |
|---|---|---|
| Structure folder | Organizational level, e.g. assembly or plant section | „Allgemein“ (General), „Allokation“ (Allocation), „Dokumentation“ (Documentation), „Verknüpfte Dateien“ (Linked files) |
| Technical component | Concrete good from the Material catalog with required quantity | „Allgemein“, „Technische Spezifikationen“ (Technical specifications), „Beschaffungsaufforderungen“ (Procurement requests), „Allokation“, „Dokumentation“, „Verknüpfte Dateien“ |
| Component requirement | Required material type with specification limits, without a fixed good yet | „Allgemein“, „Technische Anforderungen“ (Technical requirements), „Verknüpfte Dateien“ |
How to work with it
Section titled “How to work with it”- Build: The tree grows via „Knoten hinzufügen“ (add node), „Gut hinzufügen“ (add good) and „Anforderung hinzufügen“ (add requirement). An entry can be edited, assigned to another folder or deleted.
- Formulate requirements: A component requirement defines a condition per specification: =, ≥, ≤, „zwischen“ (between) or „einer von“ (one of).
- Spec matching: Via „Spec-Matching“ you assign a suitable good to a requirement. The requirement thereby becomes a technical component. Later, „Zuordnung ersetzen“ (replace assignment) swaps the good.
- Continuous check: A badge shows the result: „Zuordnung erfüllt Spezifikation“ (assignment meets specification), „Zuordnung verletzt Spezifikation“ (assignment violates specification) or „Zuordnung ungeprüft (Werte fehlen)“ (assignment unchecked, values missing).
- Further processing: On a component you create a „Neue Beschaffungsaufforderung“ (new procurement request), a „Neue Allokation“ (new allocation) or a „Neuer Dokumentationsbericht“ (new documentation report). Allocations link the good to tasks. Procurement requests appear in the „Beschaffung“ (Procurement) tab.
Specifics per view
Section titled “Specifics per view”The tool exists only in the project tab „Engineering“. Its results, however, carry further: into Procurement, into Financial performance and into the status report with the „Engineering“ area. The path is described in From engineering to order. The goods themselves are maintained in the Material catalog.