Reference & Data Model
Structure node (technical_structure_node)
A structure node is a grouping level of the technical structure, for example a plant, an assembly or a trade.
Purpose
Section titled “Purpose”The Structure node (technical_structure_node, in dialogs also „Knoten“) structures the technical structure hierarchically. It carries components and requirements and can be nested to any depth. Allocations, documentation reports and linked files that refer to the assembly as a whole are also attached to it. (Planning data)
Where in the app
Section titled “Where in the app”Projekt › Engineering, left tree under „Anordnung“ (Arrangement). The button „Knoten hinzufügen“ (Add node) creates a subnode under the selected node. Context menu on the node: „Bearbeiten“ (Edit), „Löschen“ (Delete; not on the root node). On the right the detail panel with the tabs „Allgemein“ (General), „Allokation“ (Allocation), „Dokumentation“ (Documentation) and „Verknüpfte Dateien“ (Linked files) as well as the lists „Strukturordner“ (Structure nodes), „Technische Komponenten“ (Technical components) and „Anforderungen für Komponenten“ (Requirements for components) of the direct children. See Guides › Technical structure.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Title | name |
Text | yes | Name of the node | Editable directly in the header of the detail panel |
| General description | description |
Text | no | Short description | Markdown editor below the title („Kurzbeschreibung hinzufügen..“) |
| General requirements | general_requirements |
Text | no | Free-text requirements for the assembly | Markdown editor in the tab „Allgemein“ |
| Parent node | parent_id |
Reference | no | Parent structure node | Dialog „Strukturordner bearbeiten“ › „Übergeordneten Knoten wechseln“ (Change parent node); the node itself and its subnodes are locked as targets; root cannot be moved |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
Technical structure (technical_structure) |
belongs to | no* | – | Node is deleted with the structure (cascade) |
Parent structure node (parent) |
belongs to | no | – | Subnodes are deleted with the parent node (cascade) |
Structure node (children) |
has many | no | – | deleted along (cascade) |
Technical component (technical_structure_good) |
has many | no | – | deleted along (cascade) |
Component requirement (technical_structure_requirement) |
has many | no | – | deleted along (cascade) |
Allocation (good_usage) |
has many | no | – | Reference cleared, allocation stays on the task (detach) |
Documentation report (service_documentation) |
has many | no | – | Reference cleared (detach) |
* Optional in the schema, the interface always sets the structure.
Rules & automation
Section titled “Rules & automation”- Deleting a node deletes the entire subtree: subnodes, components and requirements. The interface asks first („Löschen“ warning).
- An Allocation on the node (tab „Allokation“ › „Neue Allokation“, New allocation) assigns the node as a whole to a task. It creates a material usage (
good_usage) with quantity 1 and no good; see Material usage. A task can be chosen only once per node. - A Documentation report (
service_documentation, tab „Dokumentation“ › „Neuer Dokumentationsbericht“, New documentation report) records content (content, required) and date (documentation_date, required); the list shows creator, date „zum …“ and creation time. Reports are created on the node or on the component and sorted by date. - „Verknüpfte Dateien“ uses file links of kind
technical_structure_node, see File link.
See also
Section titled “See also”Technical structure · Technical component · Component requirement · Material usage