Common Mistakes

CMMS, EAM and Spare Parts Mistakes That Quietly Wreck Your Numbers

The reporting and data errors that make CMMS ROI, PM compliance, wrench time and spare parts numbers lie, plus how to catch each one.

The most common CMMS ROI mistake is counting avoided downtime that never existed. Symptom: your CMMS ROI Calculator shows a 340 percent return but plant availability barely moved. Root cause is baselining against a bad year, so a fluke 18 hours of downtime in the prior period becomes your recurring savings. Fix: baseline on a rolling 24 month average, not a single quarter. If prior downtime was 210 hours per year and the trailing average is 140, credit savings against 140. That single correction typically cuts an inflated ROI from 300 percent down to a defensible 90 to 130 percent.

Wrench time gets faked by measuring the wrong denominator. Symptom: the Wrench Time Calculator reports 62 percent when observed techs are clearly waiting on parts half the shift. Root cause: people divide hands-on-tool time by scheduled hours instead of paid attendance hours, quietly deleting travel, waiting, and permitting. World-typical wrench time sits at 25 to 35 percent, so any number above 45 percent should trigger an audit. Fix: use a full-shift work sampling study, 40 to 50 random observations per tech over two weeks, and count everything that is not turning a wrench as non-wrench time.

Planned maintenance compliance lies when the schedule window is too generous. Symptom: Planned Maintenance Compliance reads 98 percent but assets still fail between PMs. Root cause: a 30 day grace window on a monthly PM lets a job done 29 days late still count as compliant. Fix: measure schedule compliance against a tight window, plus or minus 10 percent of the interval. On a 30 day PM that is a 3 day window, not 30. Real-world compliant plants land at 85 to 90 percent under a tight window, and a program that only passes under a wide window is not actually protecting the asset.

Spare parts carrying cost gets understated by ignoring the real holding rate. Symptom: the Spare Parts Carrying Cost Calculator shows 12 percent when finance is charging you 26 percent. Root cause: teams plug in only warehouse rent and forget obsolescence, insurance, capital cost, shrinkage, and handling. A realistic all-in carrying rate for MRO spares runs 18 to 30 percent of inventory value per year. On a 4 million dollar storeroom, using 12 percent hides roughly 560,000 dollars of annual cost. Fix: pull the actual weighted cost of capital and add a 5 to 8 percent obsolescence charge for slow-moving critical spares.

Critical spares coverage fails on a unit-of-measure trap. Symptom: Critical Spares Coverage shows every critical asset protected, then a pump fails and the storeroom has zero usable parts. Root cause: the bill of material lists a seal kit as one line, but the repair needs two kits plus a shaft sleeve that was never flagged critical. Fix: run criticality off the failure mode, not the asset, and stock to the full repair kit quantity. If mean time between failures is 3 years and lead time is 16 weeks, one on-hand unit gives you roughly a 90 percent service level only if reorder triggers at one, not zero.

Stockout downtime exposure gets wildly underestimated by using catalog lead time. Symptom: the Stockout Downtime Exposure Calculator says a stockout risks 4 hours of downtime, but the last event cost 3 days. Root cause: the model used the vendor quoted lead time of 5 days instead of the real expedite-and-install cycle, which included 2 days of freight, a day of receiving and inspection, and a shift to install. Fix: use actual historical replenishment cycle time from your CMMS work order timestamps. If a critical spare protects a line worth 9,000 dollars per hour, a realistic 48 hour exposure is 432,000 dollars, not 36,000.

Maintenance work order backlog gets gamed by silently closing stale orders. Symptom: the Maintenance Work Order Backlog Calculator shows a healthy 3 weeks, down from 8, but nothing got fixed. Root cause: a cleanup batch-closed 400 orders older than a year, deleting real deferred work. Backlog should be measured in ready-to-schedule crew-weeks, target 2 to 4 weeks; below 2 you are overstaffed, above 6 you are losing control. Fix: segment backlog into ready, waiting-on-parts, and waiting-on-approval, and never close an order without a documented reason code.

Asset hierarchy completeness reads high while the data is useless. Symptom: Asset Hierarchy Completeness reports 95 percent because every asset has a record, yet 40 percent of work orders get charged to a generic parent like Building 2. Root cause: completeness was measured as records existing, not records at the correct functional location depth. Fix: measure the share of labor hours and cost charged to a leaf-level asset, target above 80 percent. If half your maintenance spend lands on a parent node, your Maintenance Labor Load and EAM Implementation Cost analyses are built on sand and every downstream reliability metric inherits the error.

Published 2026-07-01.