Bill of Materials Graph

Unlike a traditional indented BOM, a graph models non-linear parent-child relationships. A single sub-assembly can be a child of multiple parent products without data duplication.

• Shared Assets: A common fastener or sensor module is a single node linked to every assembly that uses it.
• Recursive Structures: Supports sub-assemblies that contain other sub-assemblies to infinite depth.
• Contextual Roles: The same physical part can have different functional roles depending on its position in the graph.

Edges in the graph are not just 'has part' links. They carry typed predicates that define the precise nature of the connection.

• Functional Coupling: fastens, seals, insulates, conducts.
• Positional Logic: isAdjacentTo, isEnclosedBy, isMountedOn.
• Process Linkage: Links parts directly to the Bill of Process steps that install or machine them.
• Constraint Modeling: Explicitly defines isIncompatibleWith or requiresCalibrationBy edges.

The graph natively handles temporal validity and revision control without flattening the data model.

• Effectivity Windows: Edges include validFrom and validTo timestamps, allowing queries like 'Show the BOM for Serial Number 4521 as it was on 2023-06-15.'
• Revision Nodes: A design change is a node that connects old part revisions to new ones, preserving full traceability.
• As-Maintained vs. As-Designed: The graph can diverge to capture field modifications while maintaining a link back to the original engineering intent.

The BOM Graph extends beyond engineering to connect parts directly to their commercial and logistical realities.

• Approved Manufacturer Lists (AML): A single design part node links to multiple qualified supplier part nodes.
• Geo-Spatial Constraints: Links to supplier nodes with properties for lead time, country of origin, and tariff codes.
• Compliance Mapping: Parts link to regulatory nodes (e.g., REACH, RoHS) for automated compliance checking.
• Risk Propagation: A disruption at a supplier node can be instantly traced to every affected top-level assembly.

The graph serves as the backbone of the Digital Thread, connecting the BOM to requirements, simulations, and service records.

• Requirement Fulfillment: Links a part or assembly directly to the functional requirement it satisfies.
• Simulation Correlation: Connects a physical part to its finite element analysis model and test results.
• Failure Feedback Loop: Field failure incidents link back to the specific lot and part revision, enabling closed-loop corrective action.
• Cost Roll-Up: Dynamic traversal from raw material nodes to finished goods for real-time cost analysis.

By applying a Reasoner or graph algorithms, the BOM Graph reveals non-obvious consequences of engineering decisions.

• Where-Used Queries: Instantly find every product and prototype affected by a component end-of-life notice.
• Transitive Dependency Chains: Identify all assemblies that will exceed weight or cost thresholds if a sub-component changes.
• Clustering: Graph algorithms can identify modules with high internal coupling but low external dependencies, suggesting optimal modularization strategies.
• Change Propagation: Simulate the ripple effect of a tolerance change across the entire product hierarchy.