Internal · content review
SCOR content foundation — review.
This is the standing review surface for the SCOR content foundation: every explainer and caselet renders here, draft or published. The original six explainers and seven caselets passed editorial review 2026-07-10 and are live under /scor; future drafts appear here first, before their flag flips. Edition of record: SCOR DS. All scenario data is synthetic.
The caselet format contract
Each micro-caselet is 250–350 words on a fixed skeleton, committed as MDX with this frontmatter:
title — the decision, stated as a hook
scor_process — one of: Orchestrate · Plan · Order · Source · Transform · Fulfill · Return
adip_agent — which ADIP agent owns the scenario
kpi_tags — metrics touched, aligned to SCOR DS attributes (RL/RS/AG/CO/PR/AM/EV/SC);
ADIP measures, not ASCM catalog metrics — codes only where the fit is clean
summary — one-card synopsis (also the social-post seed)
last_reviewed — editorial date · draft — true until the passBody beats, always in order: The situation → The signal (what the agent sensed, and from which systems) → The decision (the recommendation and the priced alternative) → The write-back (what changed, in which system) → The outcome (small table, synthetic numbers) → The takeaway (one line, LinkedIn-postable). Every caselet ends with a synthetic-data note.
Plan: the road maps the supply chain runs on
Plan is where requirements meet resources — and where the gaps between them get found early or discovered late. What the process covers, the metrics that matter, and where the recurring decisions live.
What it is. Everything a supply chain executes, it first plans — and SCOR DS treats that planning as a process in its own right. Plan describes the activities that develop the road maps to operate the chain: determining requirements, gathering what is known about available resources, balancing the two, and identifying the actions that close the gaps between them. Planning is a family rather than a single activity — plans are developed for Order, Source, Transform, Fulfill, and Return individually, then reconciled with one another so the road maps agree. That reconciliation is the point: a sourcing plan that never meets the fulfillment plan is two documents, not a plan.
The questions it answers. How much demand are we actually carrying, and how confident are we in it? What supply — on hand, committed, in motion — stands against that demand? Where do requirements and resources diverge, and how early can we see the divergence forming? What is the cheapest reliable correction: buy more, make more, move inventory, or reshape demand? And when a correction is needed, does it wait for the planning calendar or move now?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Forecast accuracy (MAPE) | practice measure | How far actuals run from plan, family by family |
| Forecast bias | practice measure | Whether the misses lean one direction — the silent killer |
| Re-plan cycle time | practice measure | How long a known deviation waits for a corrected plan |
| Inventory Days of Supply | AM.2.2 | How much buffer the plan is actually spending — rising days with flat service means the plan is buying insurance it may not need |
| Supply Chain Agility | AG.1.1 | How fast the chain can absorb a sustained change in demand or supply |
Where the decisions live. Plan’s recurring decisions are triggers. When has forecast error left its control band and made re-planning cheaper than waiting? When does a demand signal justify changing supplier requirements mid-cycle? Both questions have priceable answers: the cost of acting early is a planner-day and some supplier churn; the cost of waiting is measured in expedites and stockouts. A worked example — four weeks of MAPE creep, priced against riding the monthly cadence to its next meeting — is in the forecast-deviation caselet. What ADIP changes is cadence: the balancing act SCOR describes runs continuously against last night’s transactions, with a write-back into the planning system when the trigger fires.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures, not ASCM catalog entries.
Order: where demand becomes commitment
New in SCOR DS — Order was split out of classic Deliver to give the customer's purchase its own process. What it covers, why the split matters, and the allocation decisions that live here.
What it is. Order describes the activities associated with the customer’s purchase of products and services — quoting, order capture and validation, promising, allocation, and the management of the order through to invoicing. It is the newest Level-1 process: SCOR DS split classic Deliver into Order and Fulfill, recognizing that committing to a customer and executing that commitment are different disciplines with different failure modes. A missed promise made carelessly and a good promise executed badly look identical on a scorecard; the split lets each be diagnosed where it actually broke. Order is also where the customer’s terms enter the system — tiers, service-level agreements, penalty clauses — the context that turns an order line into an obligation with a price on failure.
The questions it answers. Can we promise this order, and against which supply? When commitments exceed availability, who ships and who waits — and what does each answer cost? What is each open commitment exposing us to, contractually and relationally? Is the order book clean enough that the demand the other processes plan against is real demand, not stale or duplicated lines?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Perfect Customer Order Fulfillment | RL.1.1 | The headline: in full, on time, documented, undamaged — every component must pass |
| Percentage of Orders Delivered In Full to the Customer | RL.2.1 | The in-full component on its own, so quantity misses can’t hide behind timing |
| Order Cycle Time | RS.2.1 | How long an order takes to move through its stages — and where it waits |
| Order Management Cost | CO.2.1 | Rising cost per order at flat volume means exceptions are eating the order desk |
| Order Supply Chain Agility | AG.2.1 | How fast the order process absorbs a sustained change in demand |
Where the decisions live. Allocation under scarcity is the signature: available-to-promise falls short of committed demand, and the same fill rate carries very different exposure depending on who is served first. We work that decision end to end — four strategies, one port strike — in the ATP short-ship example. The second recurring decision is the promise itself: a defensible promise date is derived from confirmed supply events, and when it changes, the change is written back to the ERP where the rest of the chain can see it.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference.
Source: buying well is a decision discipline
Source covers procuring, scheduling, receiving, and transferring products and services — and the supplier-risk decisions that determine whether the inbound side holds. Process scope, metrics, recurring decisions.
What it is. Source is where the supply in “supply chain” actually enters. In SCOR DS terms, it covers procuring, ordering, scheduling the delivery, receipt, and transfer of products and services: supplier agreements upstream of any transaction, then the operational loop of ordering, receiving, inspecting, and paying. The process holds a structural mirror worth naming — your suppliers’ Fulfill process is your Source process seen from the other side. Their reliability becomes your raw-material availability, their lead-time variance becomes your buffer size, and the standard lets you measure them with the same yardstick you apply to yourself.
The questions it answers. Are suppliers delivering what was promised, when it was promised — and are we measuring them with the same definitions and the same rigor we apply to our own outbound performance? Which drifts in supplier behavior are noise, and which are the start of a failure that deserves money spent against it? Where is inbound cost accumulating: price, freight, duties, expediting? How much raw-material buffer is protecting the plan, and what is that protection costing to carry?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Perfect Supplier Order Fulfillment | RL.1.2 | The supplier’s reliability, held to the same standard as your own outbound |
| Supplier OTIF vs SLA | practice measure | Contract-floor compliance per supplier, with consequences attached |
| Inbound Freight and Duties | CO.3.13 | Growth here at flat volume usually means expediting is becoming routine |
| Direct Material Cost | CO.2.6 | Whether negotiated price is surviving contact with actual buying behavior |
| Inventory Days of Supply — Raw Material | AM.3.1 | How much protection you’re carrying against inbound failure, in days |
Where the decisions live. A supplier starts sliding: three deteriorating periods, lead-time variance widening. The recurring decision is a threshold call — how much drift is tolerable before splitting an award, qualifying an alternate, or expediting a purchase order, and is the premium worth the exposure it removes? The supplier-OTIF caselet prices one such call against a line stoppage. The write-back matters as much as the analysis: the expedite flag on the PO, the split award, and the corrective-action case all land in the systems that run procurement, so the decision exists where buyers work.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures.
Transform: from schedule to product
SCOR DS renamed Make to Transform — wider than manufacturing, it covers the scheduling and creation of products. Scope, metrics, and the capacity decisions that live here.
What it is. Classic SCOR called this process Make; SCOR DS renamed it Transform, and the rename is doing real work. The process covers the scheduling and creation of products — transformation in the broad sense, from discrete manufacturing and process production to kitting, assembly, refurbishment, and the maintenance of the assets that do the transforming. A distribution business that never runs a machine still transforms: kitting is Transform, and so is the refurbishment leg of a returns operation. Scheduling sits inside the process, not upstream of it — deciding when and where to make something is Transform work, which is why a schedule nobody can execute is a Transform failure, not a planning footnote.
The questions it answers. Can the released schedule actually happen on demonstrated — not nameplate — capacity? When a line is over commitment, what spills, where, and at what cost? What is work-in-process hiding: how much cash sits between raw material and finished goods, and is it growing while output stays flat? Are the costs of transformation — labor, indirect, tooling — moving with volume, or drifting independently of it?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Schedule adherence | practice measure | Whether the plan the plant accepted is the plan the plant ran |
| Direct Labor Cost | CO.2.7 | Sustained growth ahead of volume usually means overtime has become structural |
| Indirect Cost Related to Production | CO.2.8 | The overhead that volume changes don’t automatically fix |
| Inventory Days of Supply — Work in Process (WIP) | AM.3.2 | How long value sits mid-transformation; growing WIP at flat output is a flow problem |
| Transform Supply Chain Agility | AG.2.3 | How much sustained schedule change the transform stage can take without breaking |
The decisions that live here. A line is at 112% of demonstrated capacity for the week. Three levers exist — overtime, alternate routing, re-promising — and they have different costs, different risks, and different owners, which is precisely why the call tends to stall in email. The capacity-spillover caselet prices all three and lands on a blend, written back to the ERP and MES as revised orders and routings. The general rule stands regardless of tooling: capacity problems found at schedule release cost money; capacity problems found at the due date cost customers.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures.
Fulfill: keeping the promise
Fulfill executes what Order committed — scheduling, picking, packing, shipping, installing, invoicing. Scope, metrics, and the carrier and consolidation decisions that live here.
What it is. Order makes the commitment; Fulfill keeps it. The process covers executing customer orders and services — scheduling the delivery, picking, packing, and shipping, installation and commissioning where the offer includes them, and invoicing. Together the two processes replace classic SCOR’s Deliver, and the split earns its place because execution has its own physics: warehouses with labor curves, carriers with acceptance behavior, lanes with capacity that evaporates in a tight market, appointment windows that don’t move because your schedule slipped. An order can be promised perfectly and still fail here — which is exactly the diagnostic information the old combined process obscured.
The questions it answers. Are promises being kept — in full, on time, documented, undamaged — and when they aren’t, did the failure happen in commitment or in execution? How long does fulfillment actually take, stage by stage, and which stage is the queue? Is transportation capacity available at contracted rates, or is the network quietly sliding onto the spot market one declined tender at a time? Which lanes, carriers, and consolidation patterns keep the promise at the lowest reliable cost?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Perfect Customer Order Fulfillment | RL.1.1 | The whole promise — every component must pass for the order to count |
| Customer Order Fulfillment Cycle Time | RS.1.1 | End-to-end speed as the customer experiences it, not as stages report it |
| Fulfill Supply Chain Agility | AG.2.4 | How much sustained volume change the fulfillment network absorbs |
| Tender acceptance rate | practice measure | Early warning that contracted capacity is evaporating — it falls weeks before service does |
| Freight cost per unit | practice measure | What keeping the promise costs, normalized so mix changes don’t hide drift |
The decisions that live here. Carriers start declining tenders. The operational default — chase spot capacity — keeps the promise at whatever the market asks, and hides the structural problem inside the freight bill. The alternative is restructuring: re-mixing carriers, consolidating LTL into FTL, re-timing pickups to windows carriers accept. The tender-rejection caselet prices both paths at the same service level. Re-promising is the other recurring call: when execution can’t recover an order, the new date should be read from where recovery supply actually sits in the TMS, then written back so the order desk and the customer see the same truth.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures.
Return: the reverse flow, dispositioned
Return covers the reverse flow of goods and services — diagnosing condition, evaluating entitlement, and dispositioning back into Transform or other circular activities. Scope, metrics, recurring decisions.
What it is. A return is inventory with options, not waste with paperwork — and SCOR DS structures the Return process around exactly that idea. It covers the reverse flow of goods and services from the customer back through the network: receiving the return, diagnosing its condition, evaluating entitlement, and dispositioning the unit — back into Transform for repair or refurbishment, into other circular activities, or out of the system entirely. The standard connects Return explicitly to circular-supply-chain thinking, which upgrades the process from an afterthought to the place where recovered value and sustainability metrics are actually earned. Return also carries information forward: return reasons, failure patterns, and firmware or lot correlations are quality signals that upstream processes need and rarely receive.
The questions it answers. Why are returns arriving — and is a pattern forming that Source, Transform, or engineering should hear about this week rather than this quarter? What is each returned unit actually worth under each disposition path, condition and entitlement considered? Is the customer made whole quickly enough that the return doesn’t cost the relationship on top of the unit? How much value does the reverse flow recover versus destroy — and how much of it re-enters productive use?
The metrics that matter.
| Measure | SCOR DS | What it tells you |
|---|---|---|
| Perfect Return Order Fulfillment | RL.1.3 | Whether the reverse promise is kept as reliably as the forward one |
| Diagnostic Cycle Time | RS.3.117 | How long a returned unit waits to learn its fate — dead time nobody owns |
| Value recovery rate | practice measure | The share of unit value the disposition path preserves |
| Credit cycle time | practice measure | How long the customer waits to be made whole |
| Reclaimed Products and their Packaging Materials | EV.3.1 | What the circular loop actually recaptures, counted |
Where the decisions live. Return’s recurring decision is disposition: restock, repair, refurbish, harvest, or scrap — per unit, priced, with entitlement checked rather than assumed. The warranty-wave caselet works a 3× return spike where per-unit disposition recovers 71% of value against roughly 10% for blanket scrap, and where auto-approving small entitled credits cuts the customer’s wait from 21 days to 6. The second decision is the feedback loop: a return spike traced to one firmware version is a quality signal wearing a logistics costume, and routing it to the owning team is part of the process, not a favor.
SCOR is ASCM’s framework; coded metrics reference the SCOR DS quick reference. Uncoded measures are common practice measures.
One disruption, five agents, one notebook: running the port-strike playbook
A port strike touches ordering, sourcing, and fulfillment at once. Orchestration is what keeps five agents solving one problem instead of five — decisions committed in 3 days, expedite spend capped at $120k.
The situation. A port strike stranding three inbound vessels doesn’t stay in one lane. It is simultaneously an allocation problem (who gets short-shipped), a sourcing problem (which inbound reroutes are worth paying for), and a fulfillment problem (which promises to re-cut). In 2021, the last event like this took the company three weeks of standing meetings to work through — decisions made serially, each one stale by the time the next was taken.
The signal. The risk feed raises the strike event; the Judgment Layer opens one disruption subject and pins it. Order Planning, Supplier Performance, Logistics, and Demand Planning agents each read the same fixed subject — same vessels, same SKUs, same customers — instead of four private versions of the truth. Four solvers and the Judgment Layer holding the envelope: five agents on one problem.
The decision. Orchestration is sequencing, not heroics: allocate against confirmed supply first (Order), then decide which reroutes change that supply picture enough to pay for (Source), then re-cut promises against the resulting dates (Fulfill) — with an expedite budget cap of $120,000 set once, at the top, instead of approved piecemeal.
The write-back. Each agent commits through its own systems — ERP allocations, rerouted POs, TMS promise dates — and every decision archives to the same notebook with its rationale and the telemetry it read.
The outcome.
| Metric | This event | 2021 baseline event |
|---|---|---|
| Signal → decisions committed | 3 days | ~3 weeks |
| Expedite spend | $120k (capped) | ~$310k (uncoordinated) |
| Decisions traceable to rationale | All | Meeting minutes |
The takeaway. SCOR DS makes Orchestrate a process of its own for a reason: in a real disruption, the expensive failure isn’t any single decision — it’s five good decisions made about five different versions of the problem.
Representative scenario; figures are synthetic. SCOR is ASCM’s framework. The allocation leg of this story is worked in detail in the ATP short-ship example.
Re-plan now or ride the noise: forecast error leaves its control band
Four weeks of MAPE creep on one product family — noise, or a trend worth re-planning for? The agent prices both answers and recommends pulling the re-plan forward seventeen days.
The situation. The components manufacturer behind the DR-7 drive-module family plans it on a monthly S&OP cadence. Between cycles, the plan is the plan — deviations accumulate until the next meeting.
The signal. The Demand Planning agent tracks rolling 4-week MAPE against a control band. On this family it has drifted from 18% to 31% (band: ≤22%), with a consistent under-forecast bias — actual orders are running ahead of plan, and the bias has persisted for three consecutive weeks. Systems consulted: demand-planning system (forecast, actuals), ERP (open orders, inventory position), and the customer master (which accounts are driving the lift).
The decision. Two honest options, both priced. Ride it to the next cycle: 19 days away, with a projected stockout on two SKUs that would force roughly $38,000 of expedited container moves to recover. Re-plan now: one planner-day plus supplier schedule changes, about $6,000. The agent recommends the early re-plan and shows its work — which accounts, which SKUs, and how much of the lift is repeat-order behavior rather than one-off spikes.
The write-back. Revised consensus forecast published to the planning system; updated requirements released to the two affected suppliers through the ERP.
The outcome.
| Metric | With early re-plan | Riding the cycle |
|---|---|---|
| Signal → re-plan | 2 days | 19 days |
| Expedite cost avoided | ~$32,000 net | — |
| Projected stockouts | 0 | 2 SKUs |
The takeaway. A forecast isn’t wrong when it misses — it’s wrong when it keeps missing in the same direction and nobody re-plans.
Representative scenario; figures are synthetic. SCOR is ASCM’s framework.
Who ships, who waits: an ATP short-ship under a port strike
A port strike leaves committed orders 3,800 units above available-to-promise. Four allocation strategies ship the same units — with a 5× spread in penalty exposure.
The situation. A components manufacturer has six open orders for its DR-7 drive-module family — two of them Tier-1 contracts with on-time-in-full penalty clauses. A U.S. port strike halts inbound container flow: three vessels carrying 5,200 units sit at anchor, ETAs slipped 9–16 days.
The signal. The Order Planning agent detects that committed orders (12,400 units) now exceed on-hand plus firm receipts (8,600 units) — a 3,800-unit shortfall. Systems consulted: ERP (open orders, ATP, on-hand), TMS (vessel ETAs, port status), customer master (tier, OTIF SLA, penalties), and the risk feed carrying the strike event.
The decision. Fill rate is fixed at ~69% whatever happens; the decision is who ships. The agent recommends protecting both Tier-1 OTIF contracts in full, filling Tier-2 as far as supply allows, and re-promising the spot orders against confirmed inbound recovery dates. The alternatives it prices: pro-rata (feels fair, breaches both Tier-1 SLAs), FIFO (ships a spot customer ahead of penalty-bearing contracts), and protect-margin (maximizes the week’s margin, shorts a Tier-1).
The write-back. Allocation quantities and new promise dates written to the ERP; each backorder promised against the first date delayed supply actually lands, read from the TMS.
The outcome.
| Metric | Recommended | Pro-rata (the “fair” default) |
|---|---|---|
| Tier-1 OTIF SLA | Held | Breached |
| Penalty exposure | $11,000 | $56,667 |
| Units shipped | 8,600 | 8,600 |
The takeaway. Same fill rate, 5× spread in exposure — the allocation, not the shortage, decides what a disruption costs.
Representative scenario; customers, SKUs, and figures are synthetic. SCOR is ASCM’s framework. Explore it interactively in the worked decision example.
When a trend becomes a decision: supplier OTIF drift
A key supplier's on-time-in-full slides from 98% to 88% over six weeks. The agent watches three periods, then recommends acting — before the line stops.
The situation. A single supplier feeds a critical machined component to two assembly lines. Their contractual OTIF floor is 95%, and for two years they have lived at 97–98%.
The signal. The Supplier Performance agent watches OTIF per supplier against the SLA with a persistence rule — one bad week is noise; three deteriorating periods is a trend. This supplier slides 98% → 93% → 88% over six weeks, and lead-time variance widens alongside. Systems consulted: ERP (PO receipts, promised vs actual dates), supplier scorecard, and inbound schedules from the TMS.
The decision. Doing nothing carries a priced risk: at the current trajectory, coverage on the two fastest-moving SKUs breaks in about three weeks, and a line stoppage idles roughly $22,000 per day — call it $44,000 of realistic exposure. The agent recommends a split response: expedite one open PO (premium freight ~$9,000) to rebuild the buffer, shift 30% of the next two months’ volume on those SKUs to the qualified alternate source, and open a corrective-action request with the primary rather than quietly punishing them.
The write-back. Expedite flag and revised routing on the open PO in the ERP; new split-award POs to the alternate; the corrective-action case logged against the supplier record with the evidence attached.
The outcome.
| Metric | Result |
|---|---|
| Line stoppages | 0 (exposure ~$44,000 avoided) |
| Premium freight spent | $9,000 |
| Component availability OTIF | Back ≥95% within 4 weeks |
The takeaway. Write down, in advance, how much drift you will tolerate before it becomes a decision. The trend will not tell you.
Representative scenario; suppliers and figures are synthetic. SCOR is ASCM’s framework.
What spills, where, at what cost: a line over commitment
Line 2 is committed to 112% of demonstrated capacity for the week. Overtime, alternate routing, or re-promising — the agent prices all three and recommends a blend.
The situation. A packaging plant’s Line 2 runs the week’s premium SKUs. A late large order plus a maintenance carryover leaves the line scheduled at 112% of its demonstrated weekly capacity — the plan, as written, cannot happen.
The signal. The Production Planning agent compares released schedule against demonstrated (not nameplate) capacity and flags the overcommitment before the week starts, not after the misses. Systems consulted: MES (demonstrated rates, changeover history), ERP (released orders, due dates, margins), and maintenance schedules.
The decision. Three levers, none free. Full overtime: two extended shifts across the week, about $18,000, with operators already at six-day weeks. Re-promise: push two mid-tier orders a week — free, but it spends customer reliability. Alternate routing: Line 5 can take the two compatible SKUs — about 8% of the week’s volume — after a six-hour changeover (about $3,000), at a one-day delay. The agent recommends the blend: route the compatible SKUs and add a single overtime shift (about $9,000) on Line 2, which also absorbs the maintenance carryover. Every promise date holds, at a cost of about $12,000.
The write-back. Revised production orders and routings in the ERP/MES; the changeover scheduled; the overtime shift posted to workforce management.
The outcome.
| Metric | Blend (chosen) | Full overtime |
|---|---|---|
| Schedule adherence | 98% | 97% (fatigue risk) |
| Orders re-promised | 0 | 0 |
| Incremental cost | about $12,000 | about $18,000 |
The takeaway. Capacity problems announced on Monday cost money; capacity problems discovered on Friday cost customers.
Representative scenario; lines and figures are synthetic. SCOR is ASCM’s framework.
Holding the promise when carriers say no: a tender-rejection spike
Tender acceptance on a lane cluster collapses from 84% to 61% in a tightening market. Chasing spot capacity holds the promise at +14% cost; restructuring holds it at +4%.
The situation. A regional distributor ships daily from one DC across a five-lane cluster. The freight market tightens fast; contracted carriers start declining tenders they would have taken a month ago.
The signal. The Logistics agent tracks tender acceptance by lane and flags the cluster when it drops from 84% to 61% over three weeks — with spot-market premiums on the same lanes running +23%. Left alone, the operational default is spot-chasing: promises kept, at whatever the market asks. Systems consulted: TMS (tenders, acceptances, spot quotes), ERP (order volumes, promise dates), and carrier contracts.
The decision. The agent replaces that default with a restructure: shift two lanes to the contracted backup carrier at slightly worse transit, consolidate three LTL departures into one daily FTL, and re-time pickups to windows carriers actually accept. Projected outcome holds OTIF above 95% at roughly +4% freight cost per unit, versus about +14% for spot-chasing the same service level as acceptance keeps sliding.
The write-back. Routing-guide changes and re-timed pickup appointments in the TMS; consolidated shipment plans and adjusted promise logic in the ERP.
The outcome.
| Metric | Restructure (chosen) | Spot-chasing |
|---|---|---|
| OTIF | 95%+ held | 95%+ held |
| Freight cost per unit | +4% | +14% (as the slide continues) |
| Tender acceptance (4 wks later) | 79% | 61% and falling |
The takeaway. Restructure the network before you pay the spot market to hide the problem.
Representative scenario; lanes and figures are synthetic. SCOR is ASCM’s framework.
Three times the returns, one disposition decision at a time
A firmware defect triples weekly returns. Blanket-scrap recovers ~10% of value in salvage; per-unit disposition recovers 71% — and cuts the customer's credit wait from 21 days to 6.
The situation. A connected-device maker ships a firmware release with a defect that surfaces in the field over weeks. Returns climb to 3.2× baseline — about 410 units a week — and the returns desk falls back to the historical default: scrap and credit.
The signal. The Returns & Service agent flags the volume anomaly, ties it to one firmware version from service records, and — the useful part — classifies the incoming stream: most units are healthy hardware with bad firmware. Systems consulted: RMA system (return reasons, serials), service/IoT telemetry (firmware versions), ERP (credit memos, inventory), and warranty entitlements.
The decision. Blanket-scrap is simple and destroys value — scrap-and-credit recovers salvage only, around 10%. The agent recommends disposition per unit: 62% qualify for reflash-and-test (~$14/unit against a $96 replacement cost) and return to stock as refurbished; 28% route to bench repair; 10% scrap. Credits under $400 with valid entitlement auto-approve rather than queueing for manual review.
The write-back. Disposition codes and refurb work orders in the ERP; auto-approved credit memos issued; the firmware-version linkage logged to the quality case.
The outcome.
| Metric | Per-unit disposition | Blanket scrap |
|---|---|---|
| Value recovered | 71% | ~10% (salvage) |
| Credit cycle time | 6 days | 21 days |
| Reflash cost per unit | ~$14 | — |
The takeaway. Return is where margin goes to die quietly. Treating disposition as a decision — not a default — is the difference between a cost center and a recovery operation.
Representative scenario; figures are synthetic. SCOR is ASCM’s framework.
Why SCOR Still Matters in the Agentic Era
AI agents can read anything — so why would a process framework born in 1996 matter more now, not less? Because agents raise the price of ambiguity. A founder's argument for SCOR DS as the shared language between humans, systems, and the agents that now sit between them.
The obvious objection
Here is the argument against this essay, stated as strongly as we can: large language models can read anything. They ingest your ERP exports, your contracts, your emails, your tribal knowledge in whatever dialect your company speaks it. If the machine can meet your supply chain where it is, why would anyone spend effort conforming to a reference model written before most of today’s planners had email?
It’s a fair question, and for a while we wondered ourselves. We now believe the opposite is true: agents raise the price of ambiguity, and a shared reference model is how you stop paying it.
What SCOR is, for the record
The Supply Chain Operations Reference model — SCOR — was developed in 1996 by the management consulting firm PRTM together with AMR Research, and was endorsed by the Supply Chain Council as the cross-industry standard for supply chain strategy, performance management, and process improvement. The Council later became part of what is today the Association for Supply Chain Management (ASCM), which stewards the model.
We know this model from practice. Both of us worked at PRTM as management-consultant SCOR practitioners, and we contributed to SCOR there — in engagement rooms, against real client supply chains, where the model earned its keep or didn’t.
The current edition, the SCOR Digital Standard (SCOR DS), is open-access under Creative Commons and restructures the model around seven processes: Orchestrate at Level 0 — connecting the chain to suppliers, customers, and internal stakeholders — and six Level-1 processes: Plan, Order, Source, Transform, Fulfill, Return. Gone is the old linear pipeline; SCOR DS draws the supply chain as a network loop, because that is what supply chains actually are. Performance is expressed through eight attributes — reliability, responsiveness, agility, cost, profit, asset management, environmental, and social — each decomposing into a hierarchy of defined metrics.
Keep that word, defined. It’s the whole essay.
Language precedes coordination
Every supply chain organization runs on a private dialect. “On time” means the customer-request date in one division and the last-committed date in another. “Fill rate” is measured in units here, lines there, orders somewhere else. Humans absorb these inconsistencies through years of hallway calibration; that’s what “experience at this company” partly is.
Now put an agent in the middle. An AI agent negotiating between your demand plan and your supplier commitments doesn’t get years of hallway calibration. It gets whatever definitions it can find — and if those definitions conflict, it will do something worse than fail: it will proceed, confidently, on one of them.
This is the lesson of the last few years of enterprise AI. The failure mode isn’t usually the model being weak; it’s the model being ungrounded — fluent about entities that mean different things in different systems. The remedy isn’t more intelligence. It’s shared, versioned, externally-stewarded definitions the model can be held to. An ontology.
SCOR is that ontology for supply chains, and it comes with three properties an internal glossary never has: it’s industry-neutral, so it survives your reorgs and your acquisitions; it’s complete enough, covering process, metric, practice, and skill; and it’s not yours, which means no internal faction can quietly redefine a metric to look better in the Monday deck.
The metrics hierarchy is a contract
The part of SCOR we lean on hardest at A2go is the part most people skim: the metric hierarchy. Perfect customer order fulfillment is a Level-1 reliability metric; it decomposes into defined Level-2 components — delivered in full, delivered on time to commit, documentation accurate, condition perfect — and SCOR treats each level as the diagnostics of the level above. For a metric like this, the descent is arithmetic: you can compute your way from the headline number to the transactions beneath it with no interpretive step.
Once agents participate in decisions, that structure does two jobs.
First, it separates what may be generative from what must be deterministic. An agent’s reasoning about a trade-off — protect this contract, re-promise that spot order — is judgment, and generative models are genuinely good at it when grounded. But the numbers the judgment rests on must be computed, not composed. When a CFO asks why penalty exposure is $11,000 and not $56,667, “the model estimated it” is not an answer. “It is the defined SCOR reliability decomposition over these six orders, computed from these ERP rows” is. Our architecture pairs non-deterministic reasoning with deterministic compute for exactly this reason; SCOR’s hierarchy is what makes the deterministic half specifiable.
Second, the hierarchy is the explanation path. When an agent recommends an allocation and a human asks why, the answer should descend the same tree an analyst would: attribute, to metric, to component, to transaction. Explainability isn’t a feature you bolt onto a model; it’s a property of having agreed, in advance, what the numbers mean and how they roll up.
SCOR DS is quietly agent-shaped
Here is what surprised us on re-reading the Digital Standard with 2026 eyes: the revision reads as if it anticipated agents, though it predates the current generation of them.
The old SCOR drew a linear thread — source, then make, then deliver, with Plan sitting above it — which matched how monolithic planning systems batch-processed the world. SCOR DS draws the supply chain as a continuous, connected network, always in motion. Read that picture with agent eyes and it describes concurrent, asynchronous work: an order-planning agent re-allocating while a sourcing agent re-routes inbound while a logistics agent re-cuts promises, all against the same disruption, none waiting for a meeting. That is not how a monthly S&OP cycle behaves. It is exactly how a set of agents behaves.
And the DS made Orchestrate a process in its own right — the Level-0 layer where strategy, business rules, risk posture, and performance management connect the others. Read that with agents in mind and it describes the coordination layer every multi-agent system needs and few actually specify: who sets the constraint envelope, who sequences the loops, where the budget cap lives, what gets archived and why. When we say ADIP’s agents are “coordinated through a Judgment Layer,” we are describing an implementation of what SCOR DS calls Orchestrate — one operating under more constraints than cost and speed, now that environmental and social sit among the performance attributes.
What changed, and what didn’t
When we practiced SCOR at PRTM, a diagnostic worked like this: weeks of data gathering, a metrics baseline assembled by hand from extracts, a benchmark comparison, a gap analysis, and a roadmap — delivered as a document, decaying from the day it was printed. The model was never the bottleneck. Data access was. Compute was. The refresh cycle was.
All three bottlenecks are now engineering problems rather than facts of life. Systems are queryable in place; the metrics baseline that took weeks is a view that refreshes continuously; the “diagnostic” can run every morning against last night’s transactions. What the agentic era actually changes is the cadence at which SCOR can be applied — from an engagement every few years to a standing instrument.
What didn’t change is the questions. Which commitments are at risk? Where is the trade-off between serving this customer and protecting that margin? What is the cheapest reliable recovery? We asked those questions with SCOR in consulting rooms decades ago. Our agents ask them now — with the same vocabulary, against the same metric definitions, at a cadence no engagement team could sustain.
What to do Monday
If you run a supply chain and any of this lands, three moves, in order:
- Adopt the vocabulary deliberately. SCOR DS is open-access. Map your internal terms to its processes and metrics and write the mapping down. Every ambiguity you resolve on paper is one an agent won’t resolve for you, silently, later.
- Instrument the Level-1 metrics before automating anything. If perfect customer order fulfillment, customer order fulfillment cycle time, and total supply chain management cost aren’t computed deterministically from your systems today, fix that first. Agents amplify whatever measurement discipline they find — including its absence.
- Pick one decision loop, not one department. A single recurring decision — an allocation under shortage, a re-plan trigger, a disposition call — instrumented end to end with its rationale archived, teaches you more about agentic operations than any platform evaluation.
The framework was never the point; the shared understanding was. For thirty years SCOR let people who had never met walk into the same room and argue productively about the same supply chain. The agentic era doesn’t retire that idea. It just adds new participants to the room — and they, more than anyone, need the language.
SCOR is developed and stewarded by ASCM; the SCOR Digital Standard is available open-access at ascm.org. A2go’s founders contributed to SCOR as management-consultant practitioners at PRTM.