Loading deterministic model…
Decision window / 21 days
Trace the part.
Protect the build.
A deterministic multi-level bill-of-materials engine connects on-hand inventory and inbound timing to the integrated plan, then shows exactly which leaf component changes the decision.
- Deterministic
- Explainable
- 100% synthetic
Scenario lab
Baselineintegrated vehicles
leaf-level shortages
synthetic unit cost
01 / Causal model
Interactive digital thread
- Nominal
- Constraint path
- Limiting leaf
- Plan clear
One accent carries the whole chain: dimmed along the path, full strength on the limiting leaf. Green appears only when the build gap is zero.
Vehicle model — isometric
Awaiting model
The 3D view is unavailable. Every number it shows is also in the critical-path list and exception queue below.
Vehicle view
Presentation only. Nothing here changes the model result.
Subsystem layout
Pulls the assemblies apart along the stack axis so leaf components stay readable. The renderer counts the stack as exploded past the halfway mark, which is what the buttons above report.
Focus subsystem
Reading the renderer's current focus…
Click a node, or focus the diagram and use the arrow keys to move between components; press Enter to inspect the selected one, or X to separate and restack the assemblies. Every one of those moves is reflected back into the vehicle-view controls above.
Text description of the diagram
The diagram draws a four-level synthetic bill of materials for one launch vehicle. The integrated vehicle consumes three level-1 assemblies: a propulsion module, a thermal protection set, and an avionics package. Propulsion consumes engine assemblies and cryogenic methane valves; thermal protection consumes protection tiles; avionics consumes flight computers.
The highlighted chain runs from the vehicle down to the single leaf component whose supply limits the build. That same chain is printed as text under Critical path, the shortage and recommended action appear under Constraint radar, and the arrival dates driving it appear in the inbound order board. The diagram is a faster way to read the result, never the only way.
02 / Exception queue
Constraint radar
Priority score = build gap + timing + lead-time exposure
03 / Propagation
Critical path
Why this matters
A late order is not automatically the constraint. Supply is propagated through quantity-per-parent until the actual integrated-build consequence is visible.
04 / Recovery timing
Inbound order board
| Order | Component | Qty | Arrival | Confidence | Plan status |
|---|