Reference & Data Model
Component requirement (technical_structure_requirement)
A component requirement is a placeholder for a good not yet chosen: material category plus technical requirements against which Aligia checks articles.
Purpose
Section titled “Purpose”The Component requirement (technical_structure_requirement) describes what is needed before it is decided which good it will be. It names a Material category (good_type) and carries Technical requirements (technical_structure_spec_req), one condition per specification of the material category. Spec matching rates all articles of the category against these conditions and converts the requirement into a technical component. (Planning data)
Where in the app
Section titled “Where in the app”Projekt › Engineering. The button „Anforderung hinzufügen“ (Add requirement) opens „Neue Komponentenanforderung“ (New component requirement) with title and material category search. Tree row: title and material category. Detail panel: header with title, status badge and material category, description, „Allgemeine Anforderungen“ (General requirements), table „Technische Anforderungen“ (Technical requirements; grouped by specification category, with the columns „Spezifikation“, „Einheit“, „Anforderung“) and on the right the button „Spec-Matching“ or „Zuordnung ersetzen“ (Replace assignment). See Guides › Spec matching.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Title | name |
Text | yes | Name | Empty in the dialog → Aligia sets „Anforderung“ |
| Material category | good_type_id |
Reference | no | Material category whose specifications and articles apply | Without a material category no technical requirements and no spec matching (hint „Warentyp wählen, um Spezifikationen festzulegen.“) |
| General description | description |
Text | no | Short description | Editor below the title |
| General requirements | general_requirements |
Text | no | Free-text requirements | Editor in the detail panel |
| Status | status |
Selection | yes | „offen“ / „erfüllt“ (open / fulfilled) | System: not directly editable; visible as a badge, see States |
| Parent node | technical_structure_node_id |
Reference | no* | Structure node | Edit dialog › „Übergeordneten Knoten wechseln“ (Change parent node) |
* Optional in the schema, the interface always sets the node.
Technical requirement (technical_structure_spec_req)
Section titled “Technical requirement (technical_structure_spec_req)”Auxiliary entity, one row per (requirement, specification). Created via „+“ in the row of the table „Technische Anforderungen“ (dialog „Technische Anforderungen für …“), edited by double-click, deleted via „Anforderung löschen“ (Delete requirement).
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Specification | good_type_spec_id |
Reference | yes | Specification of the material category or of a parent category | Available for selection are the specifications of the category and all parent categories |
| Operator + requirement value | value |
Selection + value | yes | Condition as JSON {op, value} or {op, min, max} or {op, values} |
Operators per data type: number „=“, „≥“, „≤“, „zwischen“ (between); selection list „=“, „einer von“ (one of); text „=“; yes/no „=“ („Zutreffend“, applicable) |
Display in the column „Anforderung“: = 100 kW, ≥ 5 A, ≤ 40 °C, 10 – 20 mm, A | B.
Relations: belongs to component requirement (required, cascade) and to specification good_type_spec (required, cascade – if the specification is deleted in the catalog, the condition disappears).
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) |
Material category (good_type) |
belongs to | no | – | Reference cleared, requirement stays without category (detach) |
Technical requirement (technical_structure_spec_req) |
has many | no | – | deleted along (cascade) |
Technical component (fulfillingGoods) |
has many | no | – | Component is kept, reference is kept (keep) |
States
Section titled “States”| Value | Label in the interface | Set by |
|---|---|---|
open |
no badge; button „Spec-Matching“ visible | Creation; deletion of the last fulfilling component |
fulfilled |
Badge „Zuordnung erfüllt Spezifikation“ (Assignment fulfills specification; green), „Zuordnung verletzt Spezifikation“ (Assignment violates specification; red) or „Zuordnung ungeprüft (Werte fehlen)“ (Assignment unchecked (values missing); yellow), below it the name of the component; for red/yellow the button „Zuordnung ersetzen“ | Spec matching |
open ──(spec matching: adopt component)──────────▶ fulfilled ▲ │ └──(last fulfilling component deleted)─────────────┘Rules & automation
Section titled “Rules & automation”- Spec matching (dialog „Spec-Matching –
“): candidates are all articles of the products of the material category and its subcategories. Per article Aligia counts fulfilled, violated and unknown conditions and shows a rate in percent (over known values only). Ranking: first articles that fulfill everything; then those without violation but with missing values (fewer unknowns first); then articles with violations (higher rate first); last articles without any value. Ties: SKU ascending. Color: green for a full match, red for one violation, otherwise yellow. - Comparison rules: numbers and number ranges must lie entirely within the bounds (bounds inclusive). Text must be exactly equal after trimming; text is never converted to a number. A missing or unsuitable value counts as “unknown”, never as a violation. There is no unit conversion; the unit comes from the specification.
- Adopting („Hinzufügen“ after the warning „… Dieser Vorgang ist unwiederrufbar.“): Aligia creates a technical component in the same structure node with the chosen article, the entered „Benötigte Menge“ (Required quantity), title, description and general requirements of the requirement, sets its reference to the requirement and deletes the requirement. With „Zuordnung ersetzen“ the previous component is deleted as well. If a step fails, Aligia rolls back the new component and reports this.
- Invalid stored conditions (e.g. from legacy data) are shown by the matching dialog as the hint „… ungültige Anforderungen“ and ignored.
- Without a material category or without conditions the dialog only shows a hint; matching is then not possible.
The verdict (summaryToState) is part of the quality KPIs as a badge, see Ch. 13 › Quality. No numeric value is reported.
See also
Section titled “See also”Technical component · Specification · Material · Guides › Spec matching