Vertical agentic orchestration · manufacturing

Where agentic plays in manufacturing orchestration, and where it does not

An outside read of the category: what the archetype changes, and which recurring situations are genuine candidates for judgement rather than arithmetic.

01

Part one

The archetype governs everything else#

There is no single manufacturing orchestration problem. Where the customer order sits relative to the build — the decoupling point — changes what is known when, what counts as late, and which variance dominates. Get the archetype wrong and every subsequent model is wrong in the same direction.
ETOMTOATOMTSRTO / MRO
Decoupled atDesignRaw materialSub-assemblyFinished goodsThe inducted asset
BOM knownWeeks before delivery, not at orderAt order entryConfigured from a module libraryStableOnly after inspection
“Late” meansA project milestone slipsAn order slipsA configuration cannot be assembledA stock-outA turnaround stalls at a gate
Dominant varianceBOM latency and customer-initiated changeSupplier commitment and deliveryModule availability and option mixForecast errorScope discovered from findings

Most plants are hybrid — primary product to order, spares to stock, specials engineered — so the archetype belongs to the product family, not the customer.

Three layers, and only one of them is agentic

Already solved — calculation

Deterministic arithmetic

Exploding the bill of materials, netting requirements against supply, computing running coverage, propagating a date change through every level, deriving the first period that goes short. Exact answers to well-posed questions.

Test — two competent planners would compute the same number. If so, no model belongs anywhere near it.

Already solved — simulation

What-if and optimisation

Staging a change and recomputing: move this date, transfer that stock, re-sequence, substitute an alternate — then compare before and after on delivery, coverage and cash. Where the objective can be written down, a solver beats judgement.

Test — can the objective be stated as one function? Then optimise it. Do not reason about it.

The remainder — agentic

Choosing between defensible answers

Simulation tells you what each option costs. It does not tell you which one this plant should take, because coverage, cash and delivery are in genuine tension and the trade-off is a judgement about this customer, this programme, this supplier relationship.

Test — do two good practitioners disagree, and can both defend their answer? Only then is there something to teach.

02

Part two

Nine situations that recur everywhere#

Supply does not arrive as promised

Supplier date slipAll archetypes

A confirmed delivery date moves out.

Alternate source · pull stock from another order · re-sequence the build · expedite · escalate to the supplier

Silence inside the lead timeAll archetypes

A purchase order is still unconfirmed with too little time left to react.

Chase · assume it will slip and re-plan now · stage a fallback · wait

Quality hold at receiptAll archetypes

The part is physically there but not usable — inspection, non-conformance, paperwork.

Seek a concession · rework · alternate source · re-sequence around it

The plan itself changes underneath you

Engineering change mid-buildSharpest in ETO and MTO

The bill of materials changes while orders are already in flight.

Re-explode and reconcile the open orders · scrap · rework · run out the old revision

Customer moves their own dateCharacteristic of ETO

The customer’s project slips, so they ask the factory to move the shipment.

Re-plan · re-prioritise other work into the freed capacity · hold the slot · re-negotiate

The bill of materials is not ready yetStructural in ETO

Long-lead material must be committed before the specific design exists.

Buy against a template · commit at parent level · escalate to engineering · accept the exposure

Contention inside the plant

Capacity lossAll archetypes

A machine is down, or maintenance overruns.

Overtime · re-route to another line · re-sequence · subcontract the operation

Two builds need the same scarce partAll archetypes

Demand for one part exceeds what is available, across parents.

Protect the key programme · protect total flow · protect cash · protect the supplier relationship · buy time

Inspection finds unplanned workDefining case in MRO

The work scope grows after induction, because the scope was never knowable in advance.

Rotable pool · cannibalise · expedite · re-gate the turnaround · re-commit the date