What is a bad actor in a compressed-air system?
Every maintenance team knows the machine that “always gives trouble”. The bad-actor method turns that instinct into evidence. The practical question is not “which compressor failed most often?” but “which recurring defect should we tackle next, why does it matter, and how will we know the action worked?”
A bad actor can sit at any level of the system:
- An asset – one compressor that trips repeatedly on high discharge temperature every summer.
- A subsystem – the cooling circuit, the condensate drains or the dryer on one line.
- A failure mode – inlet valve sticking, minimum-pressure valve leaking, drain solenoid failing, motor bearing overheating – that appears across several machines.
Counting alone misleads. A machine that runs round the clock will collect more work orders than a standby unit while actually failing less often per running hour. A cheap timer drain that sticks open can wreck air quality downstream without ever appearing near the top of a spend report. The method corrects for both.
Three decisions kept apart
A sound analysis separates three questions so that urgent safety and supply issues are never held back by a monthly ranking.
- Immediate response. A serious loss of a critical function – no instrument air, a pressure vessel defect, a fire risk – goes straight to the site’s breakdown and incident procedures, whatever its position in the list. See our breakdown diagnostics and fault triage page.
- Investigation priority. Among non-emergency defects, compare burden and evidence to choose the next root-cause investigation.
- Remedy. Only then decide whether the answer is maintenance practice, operating practice, spares holding, a system modification, an overhaul or replacement.
The output is a justified action, not a permanent label on a machine. Keep people, suppliers and brands out of blame-based rankings; record what failed and what the evidence shows.
The records you need
A credible register lets anyone move from a ranked result back to the event records behind it. Each event should carry, at minimum:
| Field | Why it matters |
|---|---|
| Work-order or log reference | Traceability back to the original record |
| Asset and location | Groups events by machine, line or compressor house |
| Component and failure mode | Separates “airend” from “drain” from “motor”; enables cross-fleet patterns |
| Symptom and confirmed cause | Distinguishes what was seen from what was proven |
| Date, time stopped and time restored | Gives downtime and repair duration |
| Running hours at failure | Normalises by exposure; supports interval and life analysis |
| Labour hours and parts used | Measures maintenance burden without needing prices |
| Production or air-supply consequence | Captures pressure dips, quality excursions, lost output |
| Corrective action and repeat flag | Shows whether the same failure returned after a fix |
Controller fault logs are valuable: high discharge temperature trips, motor overload, phase faults and dew-point alarms carry timestamps and running hours. Where history is thin, start recording now; three to six months of clean data is more useful than years of vague entries such as “compressor problem attended”.
How the ranking is calculated
The calculation uses rates and weighted burdens, so machines with different duty can be compared fairly.
- Failure rate per exposure. Failures ÷ running hours × 1,000 gives failures per 1,000 running hours. Mean time between failures (MTBF) is the inverse: running hours ÷ failures.
- Downtime burden. Sum of hours unavailable for each asset or failure mode over the period.
- Labour burden. Sum of maintenance labour hours, including call-outs outside shift.
- Consequence weight. A factor from the site’s criticality ranking – for example 1 for a fully redundant machine, 3 for one with partial standby, 5 for a machine with no backup feeding critical users. Our criticality and service level worksheet sets these consistently.
- Recurrence. A flag for any failure that returns within a set number of running hours after a corrective action; repeats deserve extra weight because the previous fix did not work.
- Combined score. A simple, transparent product such as (downtime hours + labour hours) × consequence weight, with repeats highlighted, is usually enough. Avoid scoring systems so complex no one can check them.
Then sort by score and draw a Pareto chart. In most plants a small number of failure modes accounts for most of the burden, and those are where investigation effort belongs.
Worked example
A plant has three screw compressors and two refrigerated dryers. Over twelve months the records show the following (illustrative figures):
| Asset / failure mode | Events | Running hours | Failures per 1,000 h | Downtime h | Labour h | Weight | Score |
|---|---|---|---|---|---|---|---|
| Compressor A – high temperature trip | 9 | 7,800 | 1.15 | 27 | 18 | 5 | 225 |
| Compressor B – inlet valve sticking | 4 | 5,200 | 0.77 | 16 | 20 | 3 | 108 |
| Compressor C – drain and filter faults | 6 | 1,900 | 3.16 | 6 | 9 | 1 | 15 |
| Dryer 1 – drain stuck, water carry-over | 5 | 8,300 | 0.60 | 4 | 8 | 5 | 60 |
| Dryer 2 – condenser fouling alarm | 3 | 8,300 | 0.36 | 3 | 5 | 3 | 24 |
Compressor C has the highest failure rate, but it is a standby unit with full redundancy and little downtime. Compressor A tops the list: it is the base-load machine with no backup, and its repeated high-temperature trips cluster in April to June. That pattern points at cooling – a fouled oil cooler, blocked intake louvres, recirculating hot air in the compressor room, low oil level or a failing thermostatic valve – rather than at the airend. Dryer 1 ranks third despite low labour, because water carry-over damages users downstream.
The investigation on Compressor A would check cooler condition, room ventilation and hot-air recirculation, oil grade and level, thermostatic valve operation and sensor accuracy. Our compressor room ventilation worksheet helps quantify the airflow side.
From ranking to root cause
A bad-actor list only pays off when it leads to a confirmed cause and a lasting fix. A disciplined sequence:
- Define the problem precisely. “Compressor A trips on high discharge temperature at afternoon ambient in summer, nine times in twelve months.”
- Collect evidence before dismantling. Trend logs, ambient and room temperatures, oil analysis, cooler differential temperature, photographs.
- List credible mechanisms and test each against the evidence. A normal oil-injected screw compressor typically discharges at about 75–95 °C; readings well above that under load point to cooling or oil problems.
- Confirm the cause with a measurement or inspection, not an assumption.
- Choose the remedy at the right level: cleaning schedule, ventilation change, spares holding, operating instruction, modification or overhaul.
- Set a verification criterion before the work, such as no high-temperature trips through the next summer at similar loading.
Common bad actors we see
| Failure mode | Typical underlying mechanism | Usual remedy direction |
|---|---|---|
| High discharge temperature trips | Fouled cooler, poor room ventilation, hot-air recirculation, low oil, faulty thermostatic valve | Cooling and ventilation correction, cleaning interval |
| Inlet or unloader valve faults | Worn seals, contamination, dirty intake air | Kit replacement at planned intervals, intake filtration |
| Oil carry-over | Separator element end of life, scavenge line blocked, overfilling | Element and scavenge check, correct oil level |
| Condensate drain failures | Timer drains clogging, strainers blocked, electrical faults | Zero-loss drains, strainer cleaning, drain checks in routines |
| Motor and starter trips | Voltage imbalance, loose terminations, frequent starts, bearing wear | Electrical survey, thermography, bearing care |
| Dryer dew-point alarms | Dirty condenser in dusty summer air, refrigerant issues, overload | Condenser cleaning, load check, dryer service |
In hot, dusty conditions typical across Telangana and Andhra Pradesh, cooler and condenser fouling is often the hidden thread connecting several of these.
Verifying that the fix worked
Close a bad-actor item only when the evidence shows the failure has stopped returning under comparable duty. Compare failures per 1,000 running hours before and after over a period long enough to include the conditions that triggered it – for seasonal faults, the next hot season. Re-rank monthly or quarterly; as one bad actor is cleared, the next becomes visible. If the same mode keeps returning despite good maintenance, the question moves to redesign, overhaul or replacement, which our overhaul versus replacement decision tool addresses.
How Reddy Compressors helps
We are an independent multi-brand compressor specialist based at Tarnaka, Secunderabad, serving industry since 2002. We sell, rent and service ELGi, Atlas Copco, Ingersoll Rand, KAESER, Chicago Pneumatic, Sullair, Doosan, Kirloskar and other makes, and our team of over 20 service engineers and technicians covers all of Telangana and Andhra Pradesh. We are not an authorised dealer of any brand. We have tie-ups with all major and reputed brands.
- Review your maintenance and controller fault history and build a bad-actor register with you.
- Investigate the top-ranked failure modes on site: cooling, unloading, separation, drains, dryers and electrical checks.
- Put recurring fixes into a structured AMC or preventive maintenance plan.
- Identify and supply the spare parts behind repeat failures, matched from make, model, serial number and nameplate.
- Provide rental compressors as cover while a bad actor is overhauled, from our own fleet of 50–2,000 cfm and 2–30 bar machines.
What to send us
- List of compressors and dryers with make, model, serial number and running hours.
- Maintenance records or work orders for the last 6–24 months, in any format.
- Controller fault and trip logs, if available.
- Which machines feed critical users and what standby exists.
- Photos of the compressor room, nameplates and any failed parts.
Frequently asked questions
What is a bad actor in maintenance?
A bad actor is an asset, subsystem or failure mode that repeatedly consumes a disproportionate share of maintenance effort or causes repeated loss of service. In compressed-air systems it might be one compressor tripping on high temperature, a dryer drain that keeps failing, or a valve fault seen across a fleet. Identifying it lets you focus investigation where it removes the most burden.
How do you identify bad actors in a plant?
Collect failure events with running hours, downtime, labour hours and consequence for each asset and failure mode. Normalise failures by running hours, weight by criticality, flag repeats after previous fixes, then rank and plot a Pareto chart. The handful of items at the top usually account for most of the burden and are the right place to start root-cause work.
Why does my air compressor keep tripping on high temperature?
The most common causes are a fouled oil cooler or aftercooler, poor compressor room ventilation or hot air recirculating to the intake, low or degraded oil, a faulty thermostatic valve and blocked filters. Summer ambient heat and dust make all of these worse. Check cooling first, then oil and sensors, before suspecting the airend itself.
Should I rank compressors by number of breakdowns?
Not on its own. A machine running round the clock will naturally collect more breakdowns than a standby unit. Divide failures by running hours to compare fairly, and weight by consequence, because one failure on a machine without backup can matter far more than several on a fully redundant one. Raw counts often send effort to the wrong place.
How long should I track data before ranking bad actors?
Three to six months of clean, consistent records gives a useful first ranking for most plants, and twelve months captures seasonal patterns such as summer overheating or monsoon moisture problems. Start with what you have, even if incomplete, and improve recording as you go. Re-rank regularly, because clearing one bad actor reveals the next.
When does a bad actor justify overhaul or replacement?
When root-cause work shows the recurring failure comes from wear, damage or a design limitation that maintenance practice cannot correct, the question moves to overhaul or replacement. Compare the options on restored reliability, duty fit, parts support and whole-life energy, not on age alone. A structured decision method keeps that comparison fair.
Related pages
Calculators and worked examples
These tools give indicative figures for screening, comparison and for preparing an enquiry. They run in your browser and send nothing. No prices or tariffs are assumed: enter your own to see costs. Efficiencies and other figures shown are example values: replace them with your own. Results are not a performance guarantee or a design certificate; final selection is confirmed by a service engineer against the machine data sheet and the site.
Bad-actor ranking
The worked example below shows the method with fixed numbers. Turn on JavaScript to change the inputs.
Worked example
Inputs
- Failure events per item: 9, 4, 6, 5, 3
- Running hours per item (h): 7800, 5200, 1900, 8300, 8300
- Downtime per item (h): 27, 16, 6, 4, 3
- Labour per item (h): 18, 20, 9, 8, 5
- Consequence weight per item (1–5): 5, 3, 1, 5, 3
- Repeat failures after a fix, per item: 0, 0, 0, 0, 0
Result
- Item 1 score: 225 1.15 failures per 1,000 h; MTBF 867 h; 52.1% of total score
- Item 2 score: 108 0.77 failures per 1,000 h; MTBF 1,300 h; 25% of total score
- Item 3 score: 15 3.16 failures per 1,000 h; MTBF 317 h; 3.5% of total score
- Item 4 score: 60 0.6 failures per 1,000 h; MTBF 1,660 h; 13.9% of total score
- Item 5 score: 24 0.36 failures per 1,000 h; MTBF 2,767 h; 5.6% of total score
- Ranking by score: Item 1, Item 2, Item 4, Item 5, Item 3 highest first
- Highest failure rate: Item 3 3.16 failures per 1,000 h
- Items carrying at least 80% of the burden: Item 1, Item 2, Item 4 91% of a total score of 432
Method. Enter one value per asset or failure mode, in the same order in every list. Failure rate = events ÷ running hours × 1,000 (failures per 1,000 h); MTBF = running hours ÷ events. Score = (downtime hours + labour hours) × consequence weight (for example 1 fully redundant, 3 partial standby, 5 no backup). Items are ranked by score; the Pareto line lists the top items that together make up at least 80% of the total score. Items with failures that returned after a corrective action are marked. Default: the page example over twelve months (Compressor A, B, C, Dryer 1, Dryer 2).
What to take from it. The item with the highest failure rate is often not the one to investigate first: a redundant standby can fail often and cost little.
Technical content reviewed by D. Srinivas Reddy, Managing Partner and service engineer, Reddy Compressors. Last updated 17 October 2026. How our engineering content is reviewed.