Broken master data
If the same part exists under four numbers, demand history is split four ways and no model recovers it. Catalogue quality gates forecast quality, which is why rationalization usually comes first.
Guide · Supply chain AI
What it is, which decisions it actually improves, why knowledge graphs beat another dashboard, and how to tell a usable system from a demo.
Definition
Supply chain AI is the use of machine learning and knowledge representation to forecast demand, plan supply, optimize inventory and recommend operating decisions across a manufacturing and logistics network. It differs from supply chain analytics because the output is a proposed action with its expected impact, not a chart that leaves the decision to a human under time pressure.
Three capabilities separate it from the reporting stack most manufacturers already own.
Remove any one of the three and the value collapses. Prediction without representation produces numbers nobody can act on. Representation without decision produces an elegant graph that changes nothing on Monday.
Use cases
These are the decision loops where machine learning consistently outperforms a rule, a spreadsheet or a monthly planning run.
Models read order patterns, seasonality, promotions and supplier lead-time behaviour, then constrain the forecast against real bill of materials, routing and work-center capacity so the plan is executable.
Demand planning →Safety stock set from measured demand and supply variability across every tier at once, instead of duplicate buffers held independently at each location.
Inventory optimization →Remaining useful life converted into lost capacity hours, pushed into material requirements planning and available-to-promise before the line stops.
Predictive maintenance →Vessel positions, port dwell and fleet telemetry scored for lane risk, then joined to the orders and inventory that depend on those shipments.
Ship and fleet tracking →Duplicate materials detected and explained, missing attributes flagged, taxonomy enforced, so forecasting and sourcing stop inheriting catalogue errors.
Master data →Thousands of daily alerts ranked by real impact on service, cost and capacity, each one carrying a recommended action and the evidence behind it.
Decision intelligence →The core problem
Most manufacturers are not short of data or short of charts. They are short of decisions that survive contact with the plant.
A graph-based system attacks the join directly. Because the relationships between orders, materials, routings, suppliers, lanes and assets are modelled explicitly, a change at one node can be propagated to its consequences everywhere else.
The practical test is simple. Ask the system what a two-week delay on one supplier does to on-time-in-full, to cash and to plant capacity next month. If the answer requires an analyst and three days, the data is connected on a slide, not in the system.
That is the difference between reporting on a supply chain and operating one.
Honest limits
Any vendor claiming otherwise is selling a demo. These limits are real and worth designing around.
If the same part exists under four numbers, demand history is split four ways and no model recovers it. Catalogue quality gates forecast quality, which is why rationalization usually comes first.
Models extrapolate from history. A first-of-its-kind disruption has no precedent to learn from. What AI can do is propagate the consequence quickly once a human states the assumption.
Which customer gets the constrained allocation is often a commercial judgement. The system should surface the trade-off honestly and then get out of the way.
The useful posture is narrow and verifiable: pick one decision loop, run it on production data, measure whether the recommendation was accepted and whether the outcome improved. Programmes that try to boil the network stall in integration.
Evaluation
Seven questions that separate an operating system from a screenshot.
A plan computed on last month's extract is stale before the meeting ends. Ask how often the graph is refreshed and what happens between refreshes.
It should name the signals it read, the model that scored them, the threshold crossed and the expected impact. If the answer is that the model is proprietary, no planner will approve it twice.
Bill of materials, routing, work-center capacity, changeover and shelf life. A plan that ignores these is a wish list with a confidence interval.
Decision rights should be configurable by exception class and by value or service impact, so routine actions flow and material ones wait for a human.
An approved recommendation that still needs re-keying into the ERP is not automation. It is a second inbox.
Who approved which recommendation, on what evidence, and what happened next. This is what makes the system defensible when a decision goes wrong.
Measured in weeks against production data, not in a multi-quarter programme. The first loop should pay for the integration that carries the rest.
Glossary
Plain definitions for the vocabulary that shows up in every planning conversation.
Forecasting future customer demand and converting it into a production, procurement and inventory plan the network can execute.
Using short-term signals such as point-of-sale data, open orders and channel inventory to correct the near-horizon forecast faster than a monthly cycle allows.
The recurring cycle that reconciles commercial demand with supply capability and finance, producing one agreed plan across the business.
Setting stock levels across all tiers of a network simultaneously so buffers are not duplicated at each location independently.
Inventory held to absorb demand and supply variability over the replenishment lead time at a target service level.
How long current stock will last at expected demand. When cover falls below the replenishment lead time, a stockout is already in motion.
The calculation that explodes a production plan through the bill of materials into timed component and purchase requirements.
The quantity a business can commit to a customer on a given date, based on current inventory, supply already scheduled and capacity.
The shop-floor system that tracks work orders, machine states, downtime and production output as it happens.
The share of customer orders delivered complete and on the promised date. The service measure most supply chain decisions are traded against.
The predicted time before an asset degrades past acceptable performance. Useful to planning only when expressed as lost capacity.
Using condition and telemetry data to predict failure and intervene before it happens, rather than on a fixed calendar interval.
A model storing orders, materials, routings, work centers, suppliers, lanes and assets as connected entities, so effects can be traced across the network.
A synchronized model of a physical network or asset used to simulate changes before committing to them in the real operation.
A single operating view of network exceptions with the decisions and owners attached, rather than a wall of read-only dashboards.
The layer that converts analytics into a specific recommended action with expected impact, approval rights and an audit trail.
The Supply Chain Operations Reference model, which structures supply chain activity as Plan, Source, Make, Deliver and Return.
Vision, robotics and sensor intelligence applied on the shop floor, treated as a planning input rather than an isolated monitoring feed.
Where to go next
Forecasts that become executable plans on live ERP and MES constraints.
Open →Safety stock and replenishment across every echelon of the network.
Open →Explainable next best actions with human approval and audit.
Open →Catalogue health before planning is asked to trust the masters.
Open →Nine modules on one knowledge-graph pipeline.
Open →Ship, fleet, physical AI and predictive maintenance in live operations.
Open →Answers
Supply chain AI is the use of machine learning and knowledge representation to forecast demand, plan supply, optimize inventory and recommend operational decisions across a manufacturing and logistics network. It differs from reporting because it produces a proposed action, not only a chart.
The common uses are demand forecasting, constrained production planning, multi-echelon inventory optimization, supplier and lead-time risk scoring, transport and ETA prediction, quality and vision inspection, and predictive maintenance that converts asset health into available capacity.
A supply chain knowledge graph stores orders, materials, bills of materials, routings, work centers, suppliers, lanes and assets as connected entities with explicit relationships. Because the connections are modelled, the system can trace how a delay at one node changes service, cost and capacity elsewhere.
A dashboard reports a condition but leaves the diagnosis, the trade-off and the decision to a human under time pressure. Value appears only when the system proposes a specific action, quantifies its impact and carries it through approval into the system of record.
It is when three conditions hold: every recommendation explains the signals, model and threshold behind it; approval thresholds keep material decisions with humans; and the outcome of each decision is recorded so the system can be audited and corrected.
Order and shipment history, current inventory, open purchase orders, bills of materials and routings, work-center capacity, supplier lead-time history, and whatever asset or telematics signals exist. Master data quality usually matters more than model sophistication.
A single decision loop, such as stockout risk to replenishment or demand to constrained plan, can be proved on production data within a focused engagement. Broad programmes stall; narrow loops that reach execution do not.
Traditional advanced planning systems re-plan in batch against a snapshot, so the plan is stale before the meeting ends. A graph-based system keeps demand, supply, capacity and logistics as one live object and re-evaluates decisions as signals arrive.
No. It removes the search-and-assemble work that consumes a planner's day and leaves the judgement calls. Planners move from rebuilding spreadsheets to approving, rejecting and tuning recommendations.
Cost is driven by integration scope and the number of decision loops, not by seat count alone. The honest way to size it is a discovery workshop that maps the data fabric and picks the first loop before committing to a platform-wide programme.
Next step
Map orders, BOM, routing, MES, assets and suppliers into the knowledge graph, then pick the first decision loop worth automating.