MRO Supply Chain Management: Why Programs Break Down

Most plants carrying $50M in MRO inventory have the same problem: the wrong $50M — well-stocked on parts that rarely fail, understocked on the ones that stop production lines — and standard supply chain tools can’t fix it because they were built for finished goods, not failures.

---

Short answer: MRO supply chain management is the practice of optimizing spare-parts inventory across multiple sites, ERPs, and EAM systems to balance stockout risk against working capital—a problem that demand-planning tools built for finished goods cannot solve. Most programs break down because safety-stock formulas require demand history; for a bearing that fails twice in five years, there is no history, so the formula returns zero. As a result, plants simultaneously carry 20–30% excess inventory on slow-moving parts and face stockout risk on 10–15% of critical parts (industry estimates suggest this — consistent with Verusen’s experience across hundreds of implementations). MRO Supply Chain Management: The orchestration of maintenance, repair, and operations (MRO) spare-parts inventory across multiple manufacturing sites, ERPs, and asset-management systems to minimize unplanned downtime while reducing working capital tied up in excess or slow-moving stock. Unlike finished-goods supply chain management, MRO optimization must account for equipment failures that are difficult to forecast and criticality levels that vary by site and production line.

Key takeaways

• Demand-planning formulas fail on spare parts. A formula that works for finished goods returns zero safety stock for a part that fails once every two years—then the plant orders zero, and the part fails next month.
• Multi-ERP chaos breeds emergency purchasing. A Fortune 500 CPG manufacturer with 41 sites and multiple ERPs spent 20+ minutes reviewing materials for each stocking decision; emergency purchasing consumed 15–20% of MRO budget vs. best-in-class under 5% (based on Verusen customer results).
• Excess and stockout happen at the same time. Industry estimates suggest 20–30% excess MRO inventory and simultaneous stockout risk on 10–15% of critical parts—consistent with Verusen’s experience across hundreds of implementations.
• Uptime impact is invisible in traditional metrics. Unplanned downtime costs industrial manufacturers about $50 billion a year; a single critical bearing stockout can stop a production line for three weeks, yet inventory turns miss this entirely.

Why MRO Supply Chain Programs Break Down: Five Structural Failures

MRO supply chain programs fail because they apply finished-goods supply chain logic to a problem that operates under fundamentally different rules. Finished goods sell on a schedule. Spare parts fail on no schedule. Standard forecasting, safety-stock formulas, and demand-planning tools were built for products customers buy — not for equipment that breaks unpredictably — and when you force MRO into that framework, you get the same outcome at every plant: the wrong inventory, excess working capital locked in dead stock, and critical parts missing when you need them.

The result is visible everywhere. Industry estimates suggest the average asset-intensive manufacturer carries 20–30% excess MRO inventory and simultaneously faces stockout risk on 10–15% of critical parts — consistent with Verusen’s experience across hundreds of implementations. That contradiction is not accidental. It is structural.

The cost of fragmentation. When data is spread across ERPs, EAMs, and spreadsheets, procurement spends 60% more time reviewing materials — searching across systems, validating part numbers, confirming stock before ordering. That time compounds across sites, slowing every decision and embedding risk deeper into the process.

MRO Demand Is Not Forecast-Friendly: Why Finished-Goods Tools Fail

MRO parts either move predictably—tied to preventive maintenance schedules—or sit idle then spike during failures. Applying demand forecasting formulas to sparse, non-linear demand is a category error, not a tuning problem. Standard demand planning tools built for finished goods assume historical sales patterns repeat. MRO spare parts don’t sell on a schedule; they fail. That distinction breaks every demand planning model.

Consider a bearing that fails twice in five years. A demand planning formula looks at historical movement—two failures across 60 months—and returns zero average monthly demand. The system recommends zero stock. Then the bearing fails during a production run, and your plant waits three weeks for the replacement to arrive. The line is down. The formula worked exactly as designed. It just solved the wrong problem.

ERP systems like SAP IBP and demand optimization platforms like ToolsGroup were purpose-built for finished goods—products with predictable sell-through and seasonal patterns. Why demand planning fails for spare parts is structural: these tools treat all materials as forecast-able. They are not. When you feed sparse failure data into a demand planning engine, you get false confidence in the number it returns—usually zero or a number so low it guarantees a stockout.

1. Finished-Goods Demand. Historical sales repeat. Patterns are reliable. Forecasting works. Safety stock formulas have historical data to work with.
2. MRO Demand. Failures are sparse and non-linear. History is unreliable. Forecasting formulas return zero or false certainty. Safety stock requires criticality and lead time, not sales history.

Most plants carrying $50M in MRO inventory have the same problem: the wrong $50M. They’re well-stocked on parts that rarely fail and understocked on the ones that stop production lines. Demand planning didn’t cause this—it enabled it. The tool did what it was built to do. It optimized for the wrong input.

The real lever. MRO optimization requires asset criticality, failure consequence, lead time, and supplier reliability—not historical demand. Parts that move every month need less safety stock than parts that fail once every five years but halt a $260,000-per-hour production line (Aberdeen Strategy & Research).

Risk Lives in People’s Heads: Why MRO Systems Don’t Quantify What Matters

Maintenance teams know which parts cause sleepless nights. Procurement teams know which suppliers fail consistently. Finance teams watch inventory ballooning. But MRO systems rarely quantify the things that actually matter — asset criticality, failure consequences, lead-time volatility, supplier reliability trends — so decisions default to defensive overbuying or dangerous underprotection.

The cost of this blindness is staggering. Unplanned downtime costs the world’s 500 largest companies about $1.4 trillion a year — roughly 11% of annual revenue (Siemens, True Cost of Downtime, 2024). Most of that downtime traces back to a spare part that was either not there when needed or tied up capital that could have been deployed elsewhere.

This is not a new problem. It is structural. Risk lives in people’s heads because standard MRO systems were designed around inventory counts and purchase orders, not around the specific question every maintenance engineer actually asks: what will break, when will it break, and what happens if we don’t have the part.

Why Standard Systems Can’t Quantify Asset Risk

Your ERP holds purchasing history and on-hand counts. Your EAM or CMMS holds maintenance records and failure dates. Your spreadsheets hold shutdown plans and supplier performance notes. None of them talk to each other, and none of them were built to answer: which parts, on which assets, create the most operational risk if they fail.

That gap forces a choice. A bearing that fails twice in five years has no demand history. Standard safety stock formulas require history. When there is none, the formula returns zero — so you order zero. Then the bearing fails and the production line stops for three weeks. You then overstock that bearing for years to prevent it happening again. Result: you carry excess inventory on parts that rarely fail while remaining exposed on the ones that matter most.

The average asset-intensive manufacturer carries 20–30% excess MRO inventory and simultaneously faces stockout risk on 10–15% of critical parts (industry estimates suggest this — consistent with Verusen’s experience across hundreds of implementations). That is not incompetence. That is a system that cannot distinguish between a cosmetic gasket and a coupling that stops a $5M asset.

How Risk Quantification Changes Decisions

When risk is quantified — when you know which assets are critical, which parts cause the longest downtime, which suppliers miss lead times most often — procurement and maintenance stop playing defense and start playing offense. Reliability-centered maintenance programs depend on this. So does strategic supplier partnership. So does right-sized inventory.

A Fortune 500 CPP manufacturer across 41 sites identified $63M in MRO inventory savings and verified $60M — the highest identified-to-verified ratio in Verusen’s customer base. The same company reduced material review time from over 20 minutes to 4 minutes. That speed came from quantified risk: the system told reviewers exactly which parts mattered and why, so they could make decisions in seconds instead of hunting through spreadsheets and calling maintenance.

The data exists. Your ERP, EAM, and procurement systems already hold failure history, lead-time data, and criticality signals. You do not need a data cleanse or a three-year implementation. You need a system built to extract risk signals from data as-is.

Data Fragmentation Across ERP, EAM, and Spreadsheets Creates Invisible Excess

Your MRO data doesn’t live in one place—it lives in four, and they don’t talk to each other. ERP holds purchasing and inventory records. EAM or CMMS holds maintenance history and failure patterns. Spreadsheets hold shutdown plans and local stocking decisions. Local catalogs and naming conventions hold everything else. The result is the same material coded three different ways across sites, duplicate stock no one knows exists, and blind spots on what’s actually critical.

Each system answers one question well. ERP answers “what did we buy and when.” EAM answers “what failed and how often.” Spreadsheets answer “what do we think we need.” But no system answers the question that matters: “Given what we have, what we need, and where it lives, what should we stock and where.”

The Four Silos That Create Invisible Excess

• ERP inventory records. Purchasing history, on-hand counts, and reorder points — but no link to maintenance urgency or asset criticality.
• EAM or CMMS maintenance data. Failure history, repair records, and parts used — but fragmented by work order, not by material, and often incomplete for slow-moving items.
• Spreadsheets and planning tools. Local stocking decisions, shutdown schedules, and one-off procurement requests — created outside the system of record and never reconciled.
• Supplier and catalog systems. Part numbers, lead times, and supplier performance — often inconsistent across sites and versions.

When a maintenance engineer at one site needs a critical bearing, they search ERP by part number. When an engineer at another site needs the same bearing for the same asset type, they search by description. They find different part numbers. Neither knows the other has it. Both order new stock. Six months later, one site discovers it has three years of supply while the other faces a stockout.

Fragmentation also means that materials carrying excess inventory often sit unreviewed. A part coded one way in ERP and a different way in the maintenance history looks like two separate materials. Finance sees $2M in “slow movers.” Procurement sees opportunity for a supplier consolidation. But no one connects the data to see that one material is actually overstocked across three sites by 200%.

1. What procurement sees. Historical spend by supplier and category. Orders placed and lead times. But no signal on whether the parts ordered actually prevented downtime or sat on shelves.
2. What maintenance sees. Parts consumed per work order and failure mode. But no visibility into what’s in stock elsewhere, what cost, or whether a different part would be faster to get.
3. What finance sees. Total inventory value and aging. But no ability to separate “we need this” from “we’re holding this because we’re afraid.”

A Fortune 500 CPG manufacturer across 41 sites discovered this when it unified fragmented SAP inventory records with maintenance history. The company identified $63M in MRO inventory savings and verified $60M—a verification rate most companies can only dream of—and reduced material review time from over 20 minutes to 4 minutes. The difference wasn’t better data. The difference was connecting the data that already existed.

Fragmentation costs more than excess inventory. It costs the hours your team spends hunting for part numbers, cross-referencing between systems, and re-reviewing the same materials across sites because no one knows what’s already been decided elsewhere.

Multi-Site Blindness: Why Excess at One Location Doesn’t Reach Another

Large manufacturers operating 20+ sites with separate stocking policies, suppliers, and ERP instances face a structural blindness: procurement at Site A routinely buys what Site B already carries, while maintenance teams across the enterprise cannot see what peers hold in reserve. No enterprise visibility means no coordination — and no way to move excess inventory from one location to another, even when a critical shortage exists elsewhere.

This is not a data problem. It is an architecture problem. Each site manages its own storeroom, its own suppliers, and often its own instance of the ERP system. Purchasing decisions remain local. Maintenance teams trust their own records. The result: duplicate materials sitting in different warehouses, inconsistent part naming across locations, and no single source of truth for what the enterprise actually holds.

Georgia Pacific operates 110 US sites across roughly $1B in MRO inventory, split across 4 ERP systems. Before implementing how to optimize inventory across multiple sites, the company faced a classic multi-site problem: centralized procurement rules existed on paper, but execution was decentralized across hundreds of individual stocking decisions. The company identified $55M in potential inventory reductions, verified $26M, and in the process flagged 2,900 materials at stockout risk — parts the enterprise carried nowhere, despite dozens of sites relying on them.

The real win was not the $26M. It was centralized decisioning. What had required input from hundreds of maintenance engineers and procurement specialists across 110 locations was consolidated to a team of 7 people reviewing data systematically. Visibility across all sites revealed that some locations could supply others, that some purchases were truly redundant, and that some critical gaps existed only because no one could see demand patterns across the enterprise.

Most MRO supply chain programs cannot solve this because they were never designed for it. ERP systems manage inventory at the location level. Demand planning tools forecast finished goods, not failures. The result is that enterprises remain blind to their own excess — even as they simultaneously face stockout risk on materials that exist somewhere, held by someone, three sites away.

The visibility problem scales with complexity. Industry estimates suggest the average asset-intensive manufacturer carries 20–30% excess MRO inventory and simultaneously faces stockout risk on 10–15% of critical parts — consistent with Verusen’s experience across hundreds of implementations. Multi-site environments amplify both numbers.

Misaligned Ownership: Maintenance, Procurement, and Finance Pull in Different Directions

The breakdown in MRO supply chain management is rarely about poor execution. It’s about misaligned incentives: maintenance needs availability, procurement minimizes spend, and finance wants to cut working capital—and the systems connecting them were never built to resolve that conflict. As a result, organizations end up with both excess inventory and stockout risk at the same time.

In a single-site environment, informal coordination can bridge the gap. A maintenance manager calls procurement, procurement talks to finance, and decisions get made. But that handshake breaks down across multiple locations, ERPs, and shifts. Each site develops its own stocking practices. Procurement teams build inventory buffers because they distrust the data. Maintenance teams hoard critical spares in local caches because they’ve been burned by stockouts before. Finance sees inventory ballooning and issues directives to cut stock—which immediately triggers unplanned downtime because the cuts were blind to criticality.

Maintenance and Procurement Optimize for Different Goals

Maintenance wants zero risk. A bearing that fails twice in five years is a risk. The maintenance team wants it in stock, even if it sits idle. Lead time matters—if a replacement takes eight weeks, that bearing must be on hand. Cost is secondary.

Procurement wants to minimize spend and working capital. High-velocity consumables are fine to order-to-demand. But slow-moving parts look like waste—tied-up cash that could be deployed elsewhere. Procurement pushes back on stock requests it views as excessive or applies blanket purchase policies that apply the same logic to both high-velocity and critical-but-rare parts.

Neither team is wrong. They’re optimizing within their mandate. But without a shared model of what constitutes “enough,” the compromise is usually tension. Maintenance complains that procurement won’t buy. Procurement complains that maintenance hoards. Finance cuts across both with working capital targets that ignore operational risk.

Finance Drives Reductions Without Risk Visibility

Finance looks at a balance sheet showing $50M in MRO inventory and wants to know why. Industry estimates suggest the average asset-intensive manufacturer carries 20–30% excess MRO inventory and simultaneously faces stockout risk on 10–15% of critical parts—consistent with Verusen’s experience across hundreds of implementations. But “20–30% excess” is invisible in an aggregate inventory number. Finance sees one number and demands a cut.

The problem: that cut usually falls indiscriminately. Across-the-board inventory reductions hit fast-moving parts and critical-but-rare parts the same way. A $40 bolt that moves twice a week and a $1,200 coupling that fails once every three years both get cut by 15%. The bolt is fine. The coupling now carries stockout risk. No one knows which is which because stocking decisions were never grounded in a quantified model of failure consequence or lead time.

What’s missing from this conversation is a shared understanding of cost of downtime versus cost of carrying inventory. When that trade-off is invisible, finance wins the argument to cut stock. When it’s quantified, the decision changes. A plant carrying a $1,200 coupling with a 12-week lead time faces roughly $260,000 per hour in unplanned downtime costs if that coupling fails and isn’t in stock, according to Aberdeen Strategy & Research. Keeping one in inventory costs perhaps $50 a year. The math is not close. But it only works if maintenance, procurement, and finance see the same model.

Data Fragmentation Blocks Unified Decisions

Frequently asked questions