Learning Zone · Decision example

A priority customer is about to be short-shipped. Here is who ships, who waits, and what it costs.

One page, assembled around a single available-to-promise shortfall. The customers, the SKU family, and the disruption stay fixed. The telemetry changes to the question you ask of it — not to a row of filters.

Notebook NB-2261 · SCOR P2 · Plan / Order · Agent Order Planning · Subject DR-7 imported drive modules · opened Jul 4, 2026

● Signal detected · Critical

Available-to-Promise on the DR-7 family has fallen below committed demand this week. A U.S. East & Gulf Coast port strike has halted inbound container flow — three vessels carrying 5,200 units are held at anchor, ETAs slipped 9–16 days. Committed customer orders now exceed on-hand plus firm receipts by 3,800 units. Six open orders are exposed; two are Tier-1 contracts with OTIF penalty clauses.

Analogue event · 2024 U.S. port strike — 36 ports, $3.78B/week economic cost, ~50% container-volume delay. GEP · lessons for supply-chain resilience ↗

Systems consulted by the agent ✓ ERP · open orders, ATP, allocations, on-hand ✓ TMS · inbound vessel ETAs, port status ✓ Customer master / CLM · tier, OTIF SLA, penalties ✓ Risk feed · port-strike event

The fixed subject

What this page is about, and what it is not.

Pinned to this decision

DR-7 drive modules · six exposed orders

SO-4471 Continental Foods · T1 SO-4472 Meridian Mfg · T1 SO-4480 Harbor Retail · T2 SO-4488 Delphi Group · T2 SO-4495 Orbu Logistics · T3 SO-4503 Castellan Co · T3

These stay fixed for the life of the decision. You do not re-slice a dataset to change subject — you open a new notebook.

The gap, this week

8,600 available against 12,400 committed

Fill rate is fixed at ~69% whatever we do. The decision is not how much ships — it is who ships, and what that protects.

The recommendation

Allocate the 8,600 units.

The agent recommends an allocation. Change the strategy to see the same supply distributed a different way — and what each choice costs.

Order	Customer	Tier	Requested	Allocate now	Backorder	New promise	Status

What changes on write-back

Order quantity, promise date, allocation

The trade-off, across strategies

Same fill rate. Very different exposure.

Strategy	Penalty exposure	Tier-1 SLA	Serves spot 1st?

Every strategy ships 8,600 units. Only the allocation decides whether a strategic OTIF commitment is honored or breached.

Why those promise dates

Backorders are promised against inbound recovery, not guessed.

Each re-promise date is the first point the delayed and firm supply actually lands — read straight from the TMS, so a promise is a commitment the network can keep.

Act

Commit the decision, and archive it.

Write the allocation and the new promise dates back to the ERP. The notebook — its signal, the systems it read, the recommendation, and the rationale — persists and archives, so the reason for the call survives the call.

No decision recorded yet. Choose a strategy above, then commit.

Learning Zone · Decision example · P2 · Plan / Order — telemetry is representative and computed in-page; customers, SKUs, and penalties are synthetic. SCOR is ASCM's framework. A worked example of an instrument, not a dashboard.