Menu
Insurance Spares: When the Storeroom Holds Parts You Hope Never to Use

Insurance Spares: When the Storeroom Holds Parts You Hope Never to Use

Operating spares and insurance spares are different problems. Two thresholds (failure cost > 30-day-equivalent + lead time > 2 weeks) decide what belongs.
Insurance Spares: When the Storeroom Holds Parts You Hope Never to Use

Key takeaways

See EAM vs CMMS for tracking spare parts.

  • Most spare-parts policies do not distinguish between operating spares (parts that get consumed regularly) and insurance spares (parts that may sit unused for years and exist only to prevent a catastrophic outage). Treating them with the same min/max rules produces both overstock and missed coverage.
  • Insurance spares are a different decision: not "how often does this part fail?" but "if it fails, what does that one failure cost, and can we accept that risk?" The calculation is closer to insurance than to inventory.
  • The practical rule: hold an insurance spare when the failure would cost more than 30 days of operating-cost-equivalent and the lead time to source it is more than two weeks. Below those thresholds the part belongs in the regular operating-spares pool.
  • The biggest mistake is putting insurance spares into the consumption-based reorder system. They never trigger a reorder because they never get consumed, and when one finally does get used, there is no replacement on order until someone notices the gap, often months later.

Why operating spares and insurance spares are different problems

The typical storeroom holds two populations of parts that look similar on the shelf and are very different in purpose. Operating spares, bearings, belts, seals, sensors, get consumed regularly. They have a measurable failure rate, a min/max level that follows it, and a reorder pattern driven by consumption. The framework that handles them is the one covered in our broader spare-parts piece.

Insurance spares are different. A specific high-voltage transformer for the main electrical supply. A custom-machined drive shaft for the largest mill on site. A spare PLC for the line's master controller. These parts may sit in the storeroom for five years without being touched.

They exist not because the team expects to use them, but because the cost of being without one, if and when it fails, is too high to accept on lead time.

Most plants store both populations the same way and apply the same min/max logic to both. The result: insurance spares either get over-counted (the storeroom is full of low-failure parts that are not really insurance and not really operating) or under-covered (the genuine insurance items are missing because their consumption history shows zero).

How to identify insurance spares

Two thresholds, both qualitative until the numbers go in.

1. Failure cost above 30 days of operating-cost-equivalent

If a single failure of this part would cost the plant more than the asset's annual operating cost divided by 12, the part is in the insurance category. A bearing that costs 4 hours of downtime to replace is operating. A transformer whose failure means a multi-week outage and a major production loss is insurance.

The calculation uses the same cost-per-production-minute number from the article on the preventive maintenance schedule .

2. Lead time greater than two weeks

If the part can be sourced in under two weeks even from the OEM, it is operating, not insurance. Two weeks is short enough that most plants can run on workarounds, partial production, alternative routing, hand-built temporary substitutes. Above two weeks, the workarounds run out and the plant is exposed.

Both thresholds need to be true. A high-failure-cost part with a 3-day lead time is operating (just source it when it fails). A low-failure-cost part with a 12-week lead time is also operating (accept the gap; it does not warrant insurance treatment).

The math on holding insurance spares

The cost of holding an insurance spare is the carrying cost: storage, capital tied up, occasional inventory counting. For most parts, this is 20-30% of the part's value per year.

The cost of not holding one is the expected loss: probability of failure × cost of the resulting outage. For a transformer with a 1% annual failure probability and a large outage cost, the expected annual loss is a small fraction of that outage. If the carrying cost of keeping it on the shelf is several times that expected loss, the straight math says do not hold it.

But the straight math is misleading on tail-risk items. The expected-loss calculation assumes the plant is risk-neutral; in practice, a single catastrophic outage is much worse than several years of small expected losses, because the plant has to absorb it all at once. Insurance spares earn their keep on the variance, not the expected value. The article on manufacturing KPIs covers the trend-vs-variance tradeoff in adjacent metrics.

The practical rule: hold the spare if the carrying cost is less than 4-6x the expected annual loss. Above that ratio, the math is too unfavourable even with risk aversion baked in.

The reorder problem

The single biggest operational mistake with insurance spares is putting them into the regular consumption-based reorder system. Operating-spare reorder is triggered when consumption drops the stock to the min level. Insurance-spare consumption is approximately zero. The trigger never fires.

So when an insurance spare finally gets used, usually at 2am in a crisis, there is no replacement order in the queue. The plant has solved the immediate crisis by consuming the insurance and is now exposed to the next failure for the entire lead time of the replacement order. Multiple months, sometimes.

The fix is structural: insurance spares are flagged as a separate inventory class with an event-based reorder rule. Any consumption of an insurance-class part triggers an immediate replacement order, regardless of remaining stock. The reorder is automatic, not dependent on someone noticing the gap. The work order management system needs to mark insurance-class parts when they are consumed against a work order so the trigger fires.

How to audit your insurance spares

An annual audit of the insurance-spare population is one of the easiest high-leverage exercises in the storeroom. The audit asks four questions per part:

  • Is the source asset still in service? (If decommissioned, retire the spare.)
  • Has the lead time changed? (Suppliers consolidate, parts get superseded.)
  • Has the failure cost changed? (Asset criticality shifts as plants rearrange.)
  • Is there a current substitute in the operating-spare pool that would cover the failure adequately? (Some parts move from insurance to operating because their replacements got cheaper or more available.)

Most plants find 10-15% of their insurance-spare population needs reclassification each year. Without the audit, the population grows stale and the storeroom value grows without the protection growing. The piece on root cause analysis often surfaces these reclassifications, when a failure mode is identified, the relevant insurance spare may need to be added or upgraded.

What an insurance-spare list looks like

For a typical mid-market plant with 50 critical assets, the insurance-spare list is 12-30 SKUs. Each one has:

  • The asset it protects.
  • The failure cost it covers (production minutes equivalent).
  • The lead time from primary supplier.
  • The flag that triggers event-based reorder on consumption.
  • An audit date for the annual review.

That is the whole list. It is short on purpose. Plants whose insurance-spare list is over 60 SKUs have usually misclassified a chunk as insurance when they belong in operating.

How Fabrico fits

The classification works in any inventory system that allows two distinct part classes and an event-based reorder rule.

Where a unified OEE + CMMS platform helps is in three places: the failure-cost calculation comes from the OEE event stream, the asset-link audit is automatic when assets are decommissioned, and the consumption trigger fires reliably because the work order, the parts and the asset are all in one database.

Fabrico is built so the insurance-spare class is a first-class concept rather than a workaround in the consumption-based system. To see what the classification would look like on your storeroom, book a demo .

Frequently asked questions

How do we decide between holding insurance spares ourselves vs a supplier holding them?

Some OEMs offer "guaranteed availability" agreements for critical parts at a fee. The math is the same one above: compare the agreement cost to the expected loss × risk-aversion multiplier, plus the carrying cost saved. For parts where the OEM holds local stock, the agreement is often cheaper than carrying the part ourselves. For parts that would ship from overseas regardless, holding ourselves is usually better.

What about insurance spares for end-of-life assets?

This is the trickiest category. The OEM may not support the part anymore; substitutes may not exist. The right answer is usually to hold one spare and to start the asset retirement calculation in parallel. The piece on preventive maintenance schedules covers how PM tuning interacts with retirement timing.

Should we hold multiple of the same insurance spare?

Almost never. If the failure rate is high enough to justify two on the shelf, the part is operating, not insurance. The exception is parts with a destructive failure mode that could damage a second one in close succession; even then, two is the maximum.

Who owns the insurance-spare list?

The reliability engineer where the role exists; the maintenance manager otherwise. Single owner. Annual audit. Changes go through the same review process as adding or removing an operating-spare SKU.

What is the most common implementation mistake?

Letting the storeroom team decide which parts are insurance. The classification is an asset-criticality and failure-cost decision, not a storeroom decision. The maintenance manager or reliability engineer owns the classification; the storeroom executes the storage and reorder rules.

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration