Bad actor analysis identifies the assets, components, or failure patterns consuming a disproportionate share of corrective work, reactive labor, downtime, cost, emergency response, or operational consequence. The goal is not another top-ten list. The goal is to direct reliability effort where eliminating defects will create the most value.
A maintenance team cannot perform a deep reliability investigation on every asset at the same time. Bad actor analysis narrows the field by showing which assets, systems, or failure modes are creating the largest reliability loss or maintenance burden.
How often is the asset failing, generating corrective work, or returning with the same symptom after repair?
How much downtime, production loss, labor, cost, emergency work, or operational disruption does the asset create?
Are multiple work orders actually the same unresolved failure mode repeating under different descriptions, technicians, or codes?
A pump that fails ten times for ten minutes each can be less important than a compressor that fails twice and stops production for two days. A useful ranking looks across several dimensions and keeps the underlying evidence visible.
Number of failure-related, breakdown, or corrective work orders in the selected period.
Actual labor consumed responding to unplanned failures, repeat repairs, troubleshooting, and emergency work.
Total unavailable or production-impacting time associated with the asset where trustworthy downtime data exists.
Maintenance cost, parts usage, contractor spend, or other economic burden where the CMMS captures it reliably.
Evidence that the same component, symptom, cause, or failure mode keeps returning after previous interventions.
Safety, environmental, quality, throughput, redundancy, and business consequence used to prevent a low-frequency but high-risk asset from being ignored.
| Ranking | Useful for | What it can hide |
|---|---|---|
| Corrective event count | High-frequency nuisance assets and repeat repairs. | Low-frequency catastrophic or long-duration events. |
| Reactive labor | Assets consuming technician capacity through troubleshooting and restoration. | Production consequence if downtime data is stronger than labor data. |
| Downtime | Assets creating operational interruption. | High-maintenance assets that do not stop production. |
| Cost | Material, contractor, and financial burden. | Safety, quality, or production consequence that is poorly monetized. |
| Repeat failure pattern | Unresolved recurrence despite prior maintenance activity. | One-off high-consequence events. |
| Criticality / consequence | Protects low-frequency but high-risk assets from disappearing in volume metrics. | Actual observed reliability burden if used by itself. |
I prefer to look at several raw rankings before I trust a weighted score. A single composite number can be useful, but it can also hide why an asset is bad. The next action is different for an asset ranked high because of downtime than one ranked high because of hundreds of low-consequence labor hours.
Select the site, area, line, asset population, and analysis window so comparisons are meaningful.
Standardize asset identifiers, work types, failure codes, dates, and other fields before ranking the population.
Rank by frequency, downtime, labor, cost, emergency work, and recurrence rather than forcing every decision into one metric.
Review descriptions, codes, and technician notes to determine whether apparently separate events represent one recurring failure mechanism.
Use criticality, production impact, safety, quality, environmental risk, and redundancy to keep the ranking aligned with the business.
Move each high-priority actor toward RCA, PM optimization, condition monitoring, design correction, operating change, or another defined action.
Fleet-wide rankings can be misleading when equipment types, operating duty, population size, criticality, and data quality vary dramatically. Segment by line, equipment family, area, operating service, or another logical population when that produces fairer comparisons.
Twenty similar pumps should not be compared to one compressor without understanding how event counts scale with exposure and population.
An asset running 24/7 and one running 10% duty may need normalization by operating hours, cycles, tons, starts, or another exposure basis.
If one area captures downtime and labor accurately while another does not, keep the confidence difference visible rather than pretending the rankings are equally precise.
12 corrective events, 18 reactive labor hours, 90 minutes downtime, low criticality.
Signal: nuisance recurrence worth defect elimination, but limited business consequence.
3 failures, 54 reactive labor hours, 19 hours downtime, A-critical production constraint.
Signal: fewer events, much larger consequence and maintenance burden.
1 failure, 8 labor hours, 2 hours downtime, but failure affected a safety-protective function.
Signal: may deserve investigation regardless of rank by volume.
A useful bad-actor review preserves these distinctions, then assigns the appropriate next action instead of treating rank number one as automatically equivalent to "launch RCA."
Missing asset IDs, vague closeout notes, inconsistent failure codes, unreliable downtime, and incomplete labor capture can distort rankings. XRVE Reliability keeps those limitations visible instead of hiding them behind a single score.
If the same machine appears under several names or locations, its failure burden can be split across records and disappear from the top of the list.
If every problem is coded as "mechanical" or "other," the asset may rank correctly while the recurring failure mechanism remains invisible.
Downtime, labor, and cost should be used only to the extent the site records them consistently enough to support the decision.
Use when the recurring failure mechanism is consequential, unresolved, and worth deeper technical investigation.
Use when current preventive work is missing the failure mode, poorly written, duplicated, or not producing useful findings.
Use when deterioration can be detected more effectively through condition-based or predictive methods than by fixed-interval intrusive work.
Use when chronic failures point to alignment, contamination, piping strain, foundation, component selection, accessibility, or another engineered defect.
Use when the equipment is being run outside the intended operating envelope, duty, startup method, or process condition.
Use when the apparent reliability problem is being amplified by poor planning, missing parts, bad job plans, delayed corrective work, or weak closeout discipline.
A bad-actor list without an owner, next action, and verification plan is just a leaderboard.
The Maintenance Intelligence Assessment starts at $2,500 and includes focused bad-actor and repeat-failure analysis within the agreed facility and asset scope.
Typical turnaround: about 10 business days after usable data is received.
The review cadence should match how quickly the plant’s failure history changes. Many teams review monthly or as part of a regular reliability meeting, but the important point is consistent ownership and follow-through.
A weighted score can be useful when the weighting is transparent and agreed. XRVE Reliability also keeps the underlying rankings visible because a single score can hide whether an asset is high because of frequency, downtime, cost, or consequence.
Not always. The team should consider business consequence, whether the pattern is validated, whether the cause is already known, and whether a simpler corrective action can remove the defect before launching a deeper investigation.
Yes, but confidence will vary. Work-order descriptions, labor, asset history, downtime, and technician notes can still reveal patterns. Poor coding should also become a specific data-quality improvement action.
Use CMMS history to identify which assets are consuming your maintenance capacity, understand why they keep returning, and assign the reliability actions that deserve attention first.
Start free Health Check See sample bad-actor output