Shortage module
Supply chain exception layer. Weekly part positions are classified against thresholds, ranked by planner actionability, and released through a human gate - the decision surface an agent would work beside.
- Integrated pipeline
- Plant and Procurement Intelligence Pipeline
- Role in stack
- Exception layer -> planner action
- Current state
- Mock demo from real pattern
- Best demo use
- Plant-and-procurement pitch alongside the chatbot and ERP PO Intelligence
- Honest boundary
- Demo is a mock; alert-level figures are illustrative, not measured - the shared data-foundation volumes are real
Seven stages of one weekly cycle: consistent operational sync, weekly position build, threshold classification, per-part impact snapshot, alert prioritisation by actionability, a planner release gate, and the run snapshot with week-on-week drift.
Completing the run opens the part inspector — six parts filterable by status and warehouse, each expanding into its full week series (cumulative build requirement, cumulative open quantity, past-due purchase orders, ending on-hand) with the reasoning behind its classification.
The demo is a static mock. It runs entirely in your browser on synthetic data — nothing is gated, nothing is collected.
See the shared reasoning core — sim mode ↗ — the same classify/validate/traverse/evidence pattern behind this product's narrative layer, running live on a small invented dataset.