Every plant has a short list of assets that maintenance already knows by name, the ones where a work order shows up so often that technicians stop bothering to ask why and just grab the usual part. That familiarity is exactly the problem. Chronic failures get treated as normal because they never look dramatic enough on their own to trigger a real investigation, yet a pump that fails eight times a year is quietly costing more than the one dramatic breakdown that gets a full root cause review. A bad actor program exists to replace that gut-feel familiarity with a ranked, data-driven list, so the plant's limited reliability engineering hours go to the five assets actually driving most of the cost. See how iFactory builds that ranked list automatically at ifactory support.
iFactory Bad Actor Identification & Elimination
Stop Treating Chronic Failures as Just Part of Running the Plant
Rank every asset by failure frequency and cost impact, isolate the small group actually driving most of your downtime, and turn each one into a tracked elimination project instead of a recurring line item on the work order log.
Why "It's Always Been Like That" Is the Most Expensive Sentence in Maintenance
A single dramatic failure gets a root cause investigation because it is impossible to ignore — a line goes down for a full shift, a safety incident gets logged, someone above the plant manager asks what happened. A chronic failure never earns that same scrutiny because no single occurrence looks bad enough in isolation. A conveyor motor that trips twice a month for twenty minutes each time never triggers an investigation on its own, but stacked across a year that adds up to more lost production than most of the "big" failures the plant actually does investigate. Without a structured way to rank failures by cumulative cost, chronic problems stay invisible precisely because they are frequent.
60%
Of maintenance cost can trace back to chronic failures
Eliminating repeat failures typically has a bigger budget impact than any single sporadic event, however dramatic.
3+
Failures in a rolling window is the common bad actor threshold
Three or more unplanned failures within two years, or two within six months, is a widely used starting flag.
Repeat
Fixes without root cause almost always come back
Replacing the same failed part repeatedly usually means the investigation stopped at a symptom, not the actual cause.
Hidden
Cost that never shows up as one big number
Spread across a year and a dozen work orders, chronic failure cost rarely triggers the scrutiny a single major event would.
Sporadic Failure vs. Chronic Bad Actor
Not every breakdown belongs in a bad actor program. A sporadic failure is sudden, has a single identifiable cause, and rarely repeats — a forklift striking a control panel, for example. A chronic bad actor is the opposite: frequent, often perceived as normal, and usually driven by several contributing factors stacked on top of each other. Telling the two apart correctly at the start is what keeps a bad actor program focused on the failures that actually deserve a structured investigation.
How to Tell the Two Apart
Characteristic
Sporadic Failure
Chronic Bad Actor
Frequency
One-off, rarely repeats on the same asset
Three or more occurrences in a defined window
Root cause
Usually a single, identifiable event
Multiple contributing factors, often compounding
How it's perceived
Treated as unusual, investigated on its own
Treated as normal, rarely investigated in isolation
Cumulative cost
Contained to the single incident
Compounds silently across every recurrence
Right response
Incident-specific corrective action
Structured root cause analysis and elimination project
The Pareto View: A Small Group of Assets Driving Most of the Cost
In this pattern, four assets already account for roughly 80% of cumulative maintenance cost — exactly the group a bad actor program is built to isolate and fix first.
See Your Own Ranked List
Find Out Which Assets Are Actually Driving Your Costs
Bring your last twelve to twenty-four months of work order history to the call. We will build a live Pareto ranking from your own data and show you exactly where the 80% is hiding.
Frequency Alone Is Never Enough to Rank a Bad Actor
Two assets can have the exact same number of failures over the same period and carry wildly different consequences, depending entirely on where they sit in the process. A motor that fails five times a year on a spared, non-critical line is an annoyance. A motor that fails five times a year on the plant's single bottleneck operation is a systemic threat that deserves engineering attention immediately. Cross-referencing the failure Pareto against asset criticality is what turns a raw frequency list into a genuine priority list.
Failure Frequency vs. Asset Criticality
Low Criticality
High Criticality
High Failure Frequency
Watch List
Top Priority
Low Failure Frequency
Monitor Only
Investigate Trend
Top Priority — schedule a formal root cause analysis now
Watch List or Investigate — track closely, revisit next ranking cycle
Monitor Only — low consequence, no dedicated project needed yet
The Bad Actor Elimination Workflow, Start to Finish
Ranking bad actors is only the first half of the program. The second half is a disciplined, repeatable workflow that turns each top-ranked asset into an actual improvement project with an owner, a root cause, and a verification step, rather than a name on a list that everyone agrees is a problem and nobody is assigned to fix.
1
Pull the Failure History
Collect work order data across the review period, including equipment tag, failure mode, repair cost, and associated downtime for every asset.
2
Rank by Frequency and Cost
Build the Pareto view across downtime hours, repair cost, and production loss to see where the cumulative impact concentrates.
3
Cross-Check Against Criticality
Weight the ranked list against each asset's role in the process, so a bottleneck bad actor outranks one on a fully spared line.
4
Run Root Cause Analysis
Investigate each top-ranked asset using 5-Whys, fishbone, or fault tree analysis, stopping at the true source rather than the first symptom.
5
Assign and Deploy the Fix
Match the corrective action to the actual root cause found — a design change, a procedure fix, a material upgrade, or a maintenance strategy shift.
6
Verify and Re-Rank
Confirm the failure rate actually dropped over the following cycle, then remove the asset from the active list and re-run the ranking plant-wide.
What Plants Report After Running a Structured Bad Actor Program
The value of a bad actor program is concentrated, not incremental — because the whole premise is that a small group of assets is responsible for most of the cost, fixing that small group produces an outsized result compared to spreading the same engineering effort evenly across the entire plant. The ranges below reflect what manufacturers have reported after running a structured, ranked elimination program for a full cycle.
40-60%
Reduction in maintenance cost tied to chronic failures
Eliminating repeat root causes removes the recurring cost, not just one instance of it.
50-70%
Reduction in unplanned downtime from top-ranked assets
Assets that once triggered a work order every few weeks stop showing up on the list at all.
10-20%
Of assets typically qualify as active bad actors
That share shrinks measurably each cycle as root causes get resolved instead of just patched.
One-Click
Pareto ranking instead of a monthly spreadsheet exercise
A live ranked list replaces a manual data-cleanup project that used to eat a reliability engineer's week.
Frequently Asked Questions
What actually counts as a bad actor, versus just a normal maintenance need?
The common industry threshold is three or more unplanned failures in a rolling two-year window, or two failures within six months for a tighter repeat-offender watchlist, though every plant should tune those numbers to its own asset count and data maturity. The defining trait is repetition with a pattern, not a single bad breakdown — a one-off failure with a clear, isolated cause is a sporadic event, not a bad actor. Talk to our team about setting thresholds that fit your plant's size and history.
Why does the same bad actor keep coming back even after we thought we fixed it?
A returning bad actor almost always means the previous fix addressed a symptom rather than the true underlying cause — for example, replacing a failed bearing repeatedly without ever investigating why the bearing keeps failing in the first place, such as a contaminated lubrication source or a misalignment nobody checked. Root cause analysis needs to run separately for each distinct failure mode an asset exhibits, because combining several different failure modes into one investigation tends to produce a muddled, unactionable conclusion. Book a walkthrough to see how failure mode tracking prevents this from happening again.
Should we rank bad actors by downtime hours, repair cost, or production loss?
All three tell a slightly different story, which is why a thorough program builds a separate Pareto view for each rather than picking just one. An asset might rank low on repair cost but extremely high on production loss if it sits on a bottleneck operation, and relying on only one metric can mask exactly the kind of asset that most needs attention. Reach out to our team to see how a multi-metric ranking is built from your existing data.
How much of our plant's asset base should we expect to qualify as bad actors?
Most plants find that roughly ten to twenty percent of critical assets qualify as active bad actors at any given point, though the exact figure depends heavily on plant age, process complexity, and how mature the existing maintenance program already is. A newly launched program often surfaces more candidates simply because nobody had previously ranked failures by financial impact, and that number should shrink measurably as root causes get resolved over successive review cycles. Book a demo to see what a first-pass ranking typically surfaces for a plant your size.
Do we need a CMMS to run this kind of analysis, or can it work off spreadsheets?
A spreadsheet-based approach can work for a first pass, but it tends to break down quickly because failure data lives in operator notebooks, maintenance logs, and separate departmental files that nobody can query consistently across twenty-four months of history. The same bearing failure often gets coded three different ways by three different technicians, which makes pattern recognition nearly impossible without a standardized failure mode structure behind the data. Contact our team to see how a live, structured work order history turns this into a one-click report instead of a recurring data-cleanup project.
Find the 20% Costing You 80%.
Build a Ranked Bad Actor List From Your Own Failure History
Bring your work order history to the call. We will rank your assets by frequency, cost, and criticality, and show you exactly which ones deserve a root cause investigation first.
