Reference & Data Model
Technical component (technical_structure_good)
A technical component is a concrete good from the material catalog that the structure needs in a specific quantity.
Purpose
Section titled “Purpose”The Technical component (technical_structure_good) anchors a good – more precisely: an article (good_variant) – with a required quantity in a structure node. Allocations to tasks and procurement requests to purchasing originate from it. If it results from spec matching, it stays linked to the fulfilled component requirement, and Aligia continuously checks whether the specifications of the article still fulfill the requirement. (Planning data)
Where in the app
Section titled “Where in the app”Projekt › Engineering. The button „Gut hinzufügen“ (Add good) opens „Neue Technische Komponente“ (New technical component); alternatively the component is created via „Spec-Matching“ on a requirement. Tree row: title, material category, quantity with base unit. Detail panel with the tabs „Allgemein“ (General), „Technische Spezifikationen“ (Technical specifications), „Beschaffungsaufforderungen“ (Procurement requests), „Allokation“ (Allocation), „Dokumentation“ (Documentation), „Verknüpfte Dateien“ (Linked files); on the right the card „Bedarf“ (Demand) and the product information of the article. Plus menu: „Neue Beschaffungsaufforderung“, „Neue Allokation“, „Neuer Dokumentationsbericht“. See Guides › Engineering and Guides › From engineering to order.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Title | name |
Text | no | Name of the component | Header of the detail panel editable; may be empty |
| Good / Component | good_id |
Reference | yes | Chosen article (good_variant) |
Dialog: search „Komponente suchen“ (Search component); inactive articles not selectable; „Komponente wechseln“ (Change component) in the edit dialog |
| Quantity / Demand | quantity |
Number | yes | Required quantity in the base unit of the good | Card „Bedarf“ in the detail panel; default 1; the dialog additionally shows the good’s „Einheitsmenge“ (Unit quantity) |
| General description | description |
Text | no | Short description | Markdown editor below the title |
| General requirements | general_requirements |
Text | no | Free-text requirements | Tab „Allgemein“ |
| Parent node | technical_structure_node_id |
Reference | no* | Structure node | Edit dialog › „Übergeordneten Knoten wechseln“ (Change parent node) |
| Fulfilled requirement | technical_structure_requirement_id |
Reference | no | Component requirement from which the component was created | System: set by spec matching; visible via verdict badge and check marks in the tab „Technische Spezifikationen“ |
* Optional in the schema, the interface always sets the node.
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
Structure node (technical_structure_node) |
belongs to | no* | – | deleted with the node (cascade) |
Article (good_variant) |
belongs to | yes | – | Article cannot be deleted as long as components use it (restrict) |
Component requirement (technical_structure_requirement) |
belongs to | no | – | Reference is kept (keep); the requirement is deleted during matching anyway |
Allocation (good_usage) |
has many | no | – | Reference cleared, allocation stays on the task (detach) |
Procurement request (good_procurement_request) |
has many | no | – | Reference cleared, request stays in the project (detach) |
Documentation report (service_documentation) |
has many | no | – | Reference cleared (detach) |
Rules & automation
Section titled “Rules & automation”- Spec-matching verdict (system): if a requirement is linked, Aligia continuously compares its technical requirements in the client with the specification values of the article. Result in the header of the component: badge „Zuordnung verletzt Spezifikation“ (Assignment violates specification; red) or „Zuordnung ungeprüft (Werte fehlen)“ (Assignment unchecked (values missing); yellow); when fully fulfilled no badge appears on the component. The tab „Technische Spezifikationen“ shows value and check mark per specification (✓ fulfilled, ✗ violated, „?“ unchecked). The verdict is not stored but recomputed on every display. For the comparison rules see Component requirement.
- Allocation („Neue Allokation für …“, New allocation for …): chooses a task of the project and creates a material usage (
good_usage) with the component’s required quantity as the initial value. If there is exactly one non-failed procurement request on the component, Aligia links the usage to it automatically. The tab „Allokation“ lists task, segment, planned period of the task and „Allokation am“ (Allocated on). Through the allocation the optimizer knows the material demand per task. - Procurement request („Neue Beschaffungsaufforderung“, New procurement request): „Lageraufforderung“ (Stock request) or „Einkaufsaufforderung“ (Purchase request) with quantity, „Fällig am“ (Due on), „Frühstens am“ (Earliest on) and status „Offen“ / „Erledigt“ / „Fehlgeschlagen“ (Open / Done / Failed); see Procurement request.
- Deleting a component that fulfills a requirement sets that requirement back to „offen“ (open), provided no other component fulfills it. The delete warning points this out („Die zugehörige Anforderung wird wieder geöffnet.“).
- The material category in the tree row comes from the product of the chosen article (
good.good_type_id), not from the component itself.
The required quantity does not enter KPIs directly. Procurement requests and purchases that originate from the component count in Ch. 13 › Procurement.
See also
Section titled “See also”Component requirement · Structure node · Material · Specification · Material usage · Procurement request · Guides › Spec matching