key takeaways
If you only read 30 seconds of this article:
- The three inputs: criticality (what a stockout costs), lead time (how long exposure lasts), and usage pattern (how demand behaves).
- The dominant failure mode is usage-only policy: ERPs default to demand history, and intermittent, failure-driven parts break formulas built for steady movers.
- A nine-cell matrix crossing criticality with lead time gives each material class a rule; usage pattern tunes quantities inside each cell.
- Policy becomes real through three standing reconciliations: policy vs ERP configuration, policy vs network stocking, policy vs drifting reality.
Why each input alone misleads
Each input to MRO inventory policy misleads on its own, and the failure signatures differ. Usage alone is the ERP default and the source of the classic MRO paradox, too much inventory and stockouts at the same time: demand history works for steady consumables and lies about failure-driven spares, because a part consumed twice in five years has no demand pattern, only a consequence. The safety stock guide covers why the standard formulas fail there. Criticality alone protects uptime and drowns working capital, filling the storeroom with insurance you did not need to buy. Lead time alone is a supplier-relations metric until combined with the other two; a long lead time on a non-critical steady mover is a planning note, on a critical intermittent part it is the whole policy.
The nine-cell policy matrix
A workable MRO inventory policy crosses consequence (criticality) with replenishability (lead time relative to how fast failure bites), then lets usage pattern tune quantities within each cell.
| Short lead time | Medium lead time | Long lead time | |
| High criticality | Stock minimally but firmly: small on-hand, guaranteed source, monitored | Stock deliberately: on-hand set by failure exposure, alternate source qualified | Stock and protect: insurance-spares territory, formal review of every unit |
| Medium criticality | Consider stockless: reliable next-day supply may carry it | Stock by usage: standard min/max tuned to actual pattern | Stock ahead of need: order points anticipate lead time, substitutes documented |
| Low criticality | Do not stock: buy on demand, catalog-routed | Minimal stock or vendor-managed | Question the part: consolidation and standardization candidates |
Usage pattern then adjusts inside the cell: steady movers get calculated min/max, intermittent items get discrete decisions with unit counts chosen by exposure rather than formula, and declining-usage items get a de-stocking path. The criticality input itself comes from the classification logic on the spare parts criticality page and the reasoning in stock by criticality, not guesswork.
If you want to see which of your materials sit in the wrong cell today, book a call with an MRO expert and bring a stock extract.
Making policy real: the three reconciliations
An MRO inventory policy that lives in a spreadsheet while the ERP runs different numbers is a wish. Workable programs reconcile three gaps on a standing basis. First, policy vs configuration: do the min/max and reorder points actually configured in each ERP match the matrix cell the item belongs to? Local edits drift, and the reconciliation catches it. Second, policy vs network: is the item stocked at several sites when the network needs it at fewer? Cross-site visibility converts duplicate stocking into a sharing decision, a central theme of the multi-site optimization guide. Third, policy vs reality: lead times, criticality, and usage all drift, and trigger-based review keeps the inputs honest without re-reviewing everything annually. To see which reconciliation gap is largest in your estate, book a working session.
Where Verusen fits
The matrix is simple; feeding it accurately for tens of thousands of materials across multiple ERPs is the hard part. Verusen connects the three inputs, criticality context, supplier lead-time reality, and true cross-site usage, and surfaces the items whose configured policies disagree with what the data says, so reconciliation becomes review of exceptions rather than an annual project. See the Verusen platform or set up a working session.
Frequently Asked Questions
An MRO inventory policy is the standing rule that decides, for each material, whether to stock it, how much to hold, and when to reorder. Policies that hold up are built from three inputs together: criticality, meaning the operational consequence of a stockout, lead time, meaning replenishment exposure, and actual usage pattern.
Failure-driven spares have almost no demand history, so formulas built for steady movers return zero or nonsense for exactly the parts whose absence stops production. That is how plants end up with excess stock and stockouts simultaneously: the formula over-serves predictable items and abandons consequential ones.
That matrix cell is insurance-spares territory: quantities are discrete decisions set by failure exposure, alternate sourcing, and asset redundancy, reviewed formally rather than generated by formula. The right answer is a documented judgment with a named owner, not an output of demand-history math.
On triggers: asset additions and retirements, material supplier or lead-time changes, failures that expose gaps, and duplicate merges. Add a standing reconciliation of configured ERP values against the intended policy, because local edits drift quietly, and the gap between intended and configured policy is where stockouts hide.
PN
- Jeremiah Woodford
- CRO, Verusen
Chief Revenue Officer (CRO) at Verusen AI – AI Built for Industry. Designed to Solve What Legacy Systems Can’t.
