Unplanned Equipment / Mechanical Failure
HIGH SEVERITY
Typical duration: 2–4 hrs
Frequency: Most common category
Bearing seizures, motor burnout, hydraulic or pneumatic failures, conveyor jams, tooling breakage. Usually the single most frequent source of unplanned downtime on a plant floor, and the category most SMB manufacturers already track informally — even if they've never priced it out.
Typical Cost Drivers
- Lost production value for the stoppage window
- Repair parts and contractor/vendor callout fees
- Overtime to make up missed production
- Secondary damage if the failure cascades (e.g., a jam that damages product in-process)
Common Mitigations
- Predictive maintenance — vibration and thermal sensors on your highest-failure-cost assets
- MTBF tracking by asset in a CMMS to catch degrading equipment before it fails
- Critical-spares inventory for anything with a long replacement lead time
- Preventive maintenance schedules tied to actual usage/runtime, not just calendar time
Run an equipment failure through the Calculator →
Software / Controls / OT Failure
HIGH · GROWING
Typical duration: 1–3 hrs
Trend: Rising as OT/IT converge
PLC or SCADA crashes, HMI failures, firmware bugs after an update, OT network or connectivity loss, MES/ERP outages that block the scheduling floor even when the machines themselves are fine. As plants add more connected sensors, historians, and cloud-linked analytics, this category is growing fastest — and it's the one most SMB manufacturers are least prepared to diagnose quickly, since it often needs both an electrician's and an IT person's skill set in the same ten minutes.
Typical Cost Drivers
- Lost production value — often a full line stop, since controls failures rarely allow manual workarounds
- IT/OT support time, sometimes at after-hours or contractor rates
- Data loss or reconciliation work if MES/historian data is affected
- Longer diagnosis time than mechanical failures — root cause isn't visually obvious
Common Mitigations
- Redundant controllers or a documented manual-override procedure for critical lines
- OT patch and change management — test firmware/software updates on a non-production line first
- Network segmentation between OT and IT to contain the blast radius of either side's failure
- Local HMI failover so an operator can run basic functions even if the network drops
Run a software/OT failure through the Calculator →
Power / Utility Outage
VARIES · OFTEN SEVERE
Typical duration: 1–6 hrs + restart
Scope: Usually whole-plant
Grid outages, voltage sags that trip sensitive equipment, compressed-air or utility supply interruptions. The outage window itself is often the smaller part of the cost — many processes (ovens, chillers, continuous casting, anything with a warm-up or purge cycle) take significant time to restart and requalify before output returns to normal rate, and that ramp-up time is the part most teams forget to count.
Typical Cost Drivers
- Lost production across the entire plant, not just one line
- Restart and ramp-up losses, often underestimated or ignored entirely
- Scrapped work-in-process if the outage hits mid-cycle (e.g., a molten or curing process)
- Equipment damage from an ungraceful shutdown
Common Mitigations
- UPS or generator backup for the systems where an ungraceful shutdown causes the most damage
- A documented soft-restart procedure that sequences equipment back online safely and predictably
- Periodic review of your utility's SLA and outage history for your service area
- Surge protection and power-quality monitoring to catch voltage sags before they trip equipment
Run a power outage — remember the restart-time field — through the Calculator →
Quality Defect & Recall
MED · COSTLY TAIL
Typical duration: Per batch, not time-based
Risk: Reputational + regulatory
Out-of-spec batches, contamination, mislabeling, and field returns don't usually stop the line the way a mechanical failure does — the cost shows up downstream instead, in scrap, rework, customer chargebacks, and in the worst case a formal recall. This is the category where a relatively small up-front defect can balloon into a much larger cost if it isn't caught before it ships.
Typical Cost Drivers
- Scrap and rework cost for the affected batch or run
- Customer penalties, chargebacks, or expedited replacement shipments
- Recall logistics and regulatory reporting, if it escalates that far
- Reputational cost with the affected customer — often larger than the direct cost, and harder to quantify
Common Mitigations
- In-line statistical process control (SPC) to catch drift before a full batch is affected
- Incoming-material inspection for critical raw materials and components
- Root-cause/CAPA discipline so the same defect doesn't recur next quarter
- Clear hold/quarantine procedures so a suspect batch doesn't ship while it's being investigated
Run a quality event through the Calculator →
Supply Chain Disruption
MED · EXTERNAL
Typical duration: 4 hrs – 3 days
Cause: Outside your plant's walls
A supplier outage, raw material shortage, or logistics failure that starves your line of what it needs to run. The mechanics look different from an equipment failure — nothing is actually broken — but a starved line costs almost as much as a broken one, since your labor and overhead keep running while output stops.
Typical Cost Drivers
- Idle labor cost while the line waits for material
- Lost production value for the starved window
- Expedited freight to close the gap once material is available
- Downstream schedule disruption — the line behind the starved one often backs up too
Common Mitigations
- Dual-sourcing for critical inputs, especially single-supplier components
- Safety stock sized to your longest-lead-time critical input, not your average lead time
- Supplier scorecards that track on-time delivery and flag degrading reliability early
- A documented substitution or de-rate plan for when a specific input is unavailable
Run a supply disruption through the Calculator →
Safety / Compliance Incident
HIGH · REGULATORY
Typical duration: 1–8 hrs stop-work
Risk: Legal, insurance, reputational
An injury, a near-miss serious enough to trigger a stop-work order, or an OSHA/EPA finding. Beyond the direct cost, this category carries the longest tail — insurance premium impact, potential legal exposure, and the hit to morale and hiring if the plant develops a reputation for safety issues.
Typical Cost Drivers
- Idle labor during the stop-work investigation
- Regulatory fines, legal fees, or workers' comp claims
- Insurance premium increases following a reportable incident
- Hiring and retention impact if safety reputation suffers
Common Mitigations
- A near-miss reporting culture that surfaces issues before they become injuries
- JSA (Job Safety Analysis) and LOTO (lockout/tagout) discipline, audited regularly, not just documented
- Regular safety audits with real follow-through on findings, not just a checklist
- Clear escalation paths so a near-miss gets reviewed, not just logged and forgotten
Run a safety incident through the Calculator →
// Price out your own incident
Run it through the Calculator.
Select the matching incident type and get a cost breakdown, an annualized exposure estimate, and a tailored first move.
Frequently Asked Questions
My incident doesn't fit neatly into one category — what do I do?
Pick whichever category drives most of the cost. A supplier delay that also causes a quality problem downstream, for example, is usually best modeled as supply chain disruption with the quality cost folded into the scrap/rework field on the Calculator.
Which category is usually the most expensive per incident?
It depends heavily on your plant, but power/utility outages and quality recalls tend to have the widest ranges — a short power blip is cheap, but a multi-hour whole-plant outage with a slow restart can be the most expensive single event a plant experiences. Quality events are unusual in that cost scales with batch size rather than time.
Should near-misses count toward my incident frequency?
If a near-miss still cost you idle time, inspection effort, or a partial stoppage, yes — count it on the Calculator's "incidents per year" field for whichever category it resembles. Near-misses that cost nothing but attention are worth tracking separately for safety culture, but don't need to go into the cost model.