Learning Zone · Decision example

The work order releases Friday. One BOM line out of 214 says no. What unlocks it — and at what cost?

One page, assembled around a single work order that cannot start. The order, the BOM, and the binding line stay fixed. Change the unlock path to see what each one costs — in money, in days, and in the promise behind it.

Notebook NB-2418 · SCOR Source / Transform · Agent Material Availability · Subject WO-58214 · CF-7400 fabric router · opened Aug 11, 2026

● Signal detected · Critical

WO-58214 — CF-7400 fabric router, quantity 300 — is not Clear to Build. The BOM runs 214 lines; 212 are covered and one of the two shorts clears on its own. The binding line is TN-C-04471 (470 µF polymer capacitor, 4 per unit): need 1,200, allocated on hand 40 — short 1,160 — after PO-77841 slipped nine days to Sep 2. Release is Fri Aug 21 against a customer promise to Talvora of Fri Aug 28: 82% probability the promise is missed on current supply, with a $438,000 shipment at risk.

MRP presumes supplier dates hold — it keeps releasing the other 212 lines to plan while one line slips. The condition is imbalance, not shortage: inventory building against a work order that cannot start.

Systems consulted by the agent ✓ ERP / MRP · BOM explosion, allocations, PO dates ✓ WMS · on-hand by lot, receiving-scan vendor parts ✓ Quality · hold status by lot ✓ Customer master · AVLs, ownership, consignment

The fixed subject

One work order, one gate, one binding line.

Pinned to this decision

WO-58214 · CF-7400 fabric router · qty 300

TN-C-04471 capacitor · short 1,160 · binds TN-HS-2201 heat sink · short 300 · PO lands Aug 19 212 lines covered · arriving to plan

The gate goes by many names — clear to build, kittable, material-complete. It means every component a work order needs has been received. Evaluated continuously, per line, with the binding constraint named and dated — not a report assembled the night before release.

The binding line, this week

1,200 needed against 40 allocated

Whatever we choose, the other 213 lines are already decided. This page is about the one line that binds — and what covering it is worth.

The recommendation

Unlock the build.

The agent recommends a path. Change it to see the same short covered a different way — and what each choice costs, in money and in days.

BOM line	Description	Short	Covered by	Cover date	Status

What changes on write-back

Records, not homework

The trade-off, across paths

Same short. Very different cost.

Path	Clear to Build	Aug 28 promise	Incremental spend

"Free" is the most expensive column: waiting spends no money and slips a $438,000 shipment thirteen days. The recommended path costs a $208.80 accounting entry.

Why the transfer is safe

The decision ontology found equivalent stock two programs away — and can prove it.

The decision ontology joins what usually lives in separate look-ups: customer AVLs, the vendor part number captured at receiving, lot history, ownership, and quality status. Voralis Medical part VM-CAP-1180 resolves to the same vendor part — VC-471P-25V — and that part is approved on both customers' AVLs. Today that join is a five-to-six-step detective hunt across systems; here it is one governed read.

Voralis stock under VM-CAP-1180 · decomposition

Tranche	Qty	Standing
Voralis-owned · FIFO-clean · lot-traced	1,240	Usable
Quality hold · lot QH-2231	400	Excluded
Consigned · customer-owned	200	Excluded
Total on hand	1,840	1,240 eligible

Two lots came back from the floor out of sequence, so eligibility is read from receiving-scan lot genealogy — actual stock movement, not assumed FIFO.

The checks that make it a recommendation

Commitment check. Voralis needs 800 on Oct 12; a replenishment PO for 2,000 is confirmed for Sep 20. Transferring 1,160 leaves Voralis fully covered — no promise affected.
Commercial check. Voralis standard cost $0.84 against $1.02. The transfer moves at cost with a $208.80 variance entry to program accounting. Clean books, no margin smeared between programs.
Codified restraint. The ontology also sees a consigned Quarzon-9 FPGA (customer-purchased, drop-shipped, $84.00 vs $101.50 contract prices). It is flagged requires commercial approval — known, and deliberately never auto-recommended.

The same read, two more decisions

Nothing extra was queried to find these: quality-hold lot QH-2231 (400 pcs) routes to disposition instead of aging into excess, and a −22% demand signal at Kelvane Energy recommends reducing open PO-79102 before its Aug 14 commit date — $27,900 of projected excess avoided before it exists. Excess & obsolete prevented at the moment of decision, not analyzed at quarter-end.

Act

Approve the parts, commit the whole.

Judgment stays human — four roles approve their part: Buyer · transfer + PO re-date Program manager, Voralis · stock release Program manager, Talvora · promise confirm Inventory analyst · variance + disposition

Write the transfer, the PO re-date, the allocation, and the confirmed promise back to the systems of record. The notebook — signal, systems read, recommendation, approvals, and rationale — persists and archives, so the reason for the call survives the call.

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

What the platform keeps: the TN-C-04471 ↔ VM-CAP-1180 equivalence, codified with receiving-scan provenance — next time a look-up, not an investigation. The FIFO exception, recorded. The jeopardy model, updated with the actual slip.

Learning Zone · Decision example · Source / Transform — 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.