Business problem
Procurement & Supply
What's on order, when it lands, and how the supplier actually performs.
Metrics
Computable definitions from the KPI Dictionary — every decision switch made explicit, with the formula behind it.
| KPI | Formula | What it answers |
|---|---|---|
| Supplier On-Time DeliveryK-12 | Did the supplier deliver to your dock by the date they originally committed — at which receipt grain, against which promise, and after how much of the line arrived? |
Supplier performance is usually reported as one blended score, and blending is what makes it useless: a supplier that is best in the base on delivery and worst on quality lands mid-table and is never looked at again. The work here keeps delivery, quality and price as three separate numbers, measures on-time against the supplier's original promise rather than the promise as it was later revised, and treats purchase price variance as a quotient of two summed totals on received units rather than an average of per-line variances. The reference build runs a year of simulated purchase-order lines and includes the small-volume guard, because a supplier with eleven lines has not yet told you anything.
Reference builds
Reference builds for this business problem, implementing the definitions above wherever one exists, running over frozen, simulated data. Not a resource and not a case study — no client data, and no client named.
In the references
Where this data lives in each source system. A way into the ERP references, not an index of them — every reference landing lists all of its modules.
The other business problems
- Inventory & Working Capital — What you're holding, why it's there, and what it costs to hold it.
- Demand Planning & Forecasting — How wrong the forecast is, in which direction, and where the error is worth fixing.
- Customer Service & Fulfillment — Whether the order arrived complete, on the date you committed to.
- Manufacturing & Production — Whether the plant built what the plan said it would build.
- Data Foundation & Governance — Landing ERP data in a lakehouse without losing deletes, history, or control of who reads it.