Docs/Engineering
Components, subsystems and properties
Model the engineered system and keep technical values attached to the right objects.
Components and subsystems
Use subsystems to group meaningful areas of the design and Components for the engineered items within the system. The structure should help you reason about the design rather than mirror an arbitrary folder hierarchy.
- Give objects clear names and stable keys.
- Use links to show relationships to requirements, tasks, risks and other records.
- Associate versions/design cycles when the object's context changes over time.
Engineering properties
Properties hold technical values that belong to an engineering object. This is where values such as mass or other design parameters should live when they describe the component/subsystem itself.
Note: Mass belongs to Components/Subsystems, not the BOM/Budget costing system.
Component quantity is not BOM quantity
Component quantities and BOM-item quantities are intentionally separate. Linking a component and BOM item is a reference relationship only; Nodetropy does not automatically propagate quantity between them.
Note: This separation prevents a design-structure count from silently changing procurement/costing data.