Repeat failure analysis turns scattered work orders into recurring failure patterns. Its purpose is not to claim root cause from CMMS text. It is to identify where restoration keeps repeating, quantify the consequence, and decide which patterns deserve structured root cause failure analysis, strategy change, or engineering action.
Not every repeat needs a full RCA. Some patterns can be resolved through better repair standards, PM changes, alignment or lubrication controls, parts quality, operator practices, or data cleanup. The purpose of triage is to reserve deeper investigation for recurrence that matters.
The asset repeatedly trips, leaks, jams, overheats, loses pressure, or produces the same abnormal condition.
The same bearing, sensor, belt, coupling, seal, valve, drive, or other component is repeatedly repaired or replaced.
A documented underlying contributor recurs, such as contamination, misalignment, inadequate lubrication, wiring damage, or a process condition.
I treat recurrence as an alarm, not as a diagnosis. Three bearing replacements do not automatically mean the bearing is the root cause. The repeated component may be the victim of misalignment, contamination, loading, installation practice, lubrication, shaft condition, or another upstream problem.
CMMS recurrence is rarely a perfect match on one failure code. Work-order language varies by technician, shift, component name, shorthand, symptom, and level of detail. Useful analysis normalizes those differences without pretending uncertain records are exact.
Resolve aliases, parent assets, line-level charging, retired IDs, and duplicate equipment records before comparing recurrence.
Group comparable terms such as “belt tracking,” “belt walking,” and “conveyor belt off center” while keeping the original text available for review.
Define a recurrence window appropriate to the asset and failure. Three events in one week may represent a different problem than three similar events over five years.
When records are vague, label the pattern as suspected recurrence and identify what better closeout or inspection evidence is needed.
| Signal | What it adds |
|---|---|
| Event count | Shows recurrence frequency. |
| Downtime | Shows operational interruption when captured consistently. |
| Labor hours | Shows maintenance capacity consumed by restoration. |
| Parts / cost | Shows material burden and repeat replacement. |
| Emergency priority | Shows schedule disruption and response urgency. |
| Safety / quality consequence | Can justify escalation even when event count is low. |
| Time between repeats | Shows whether recurrence is accelerating or repair life is shorter than expected. |
Four drive-end bearing replacements in nine months, similar noise complaints, increasing emergency response, and progressively shorter time between repairs.
The bearing itself is defective. The same history could be consistent with alignment, contamination, lubrication, shaft fit, loading, installation practice, housing damage, or an operating condition.
The repeat-failure analysis should group the events, quantify the burden, inspect parts and closeout history, validate whether the repairs are comparable, and escalate to focused RCFA if the consequence and evidence justify it. The corrective action should then include a verification plan, such as a defined run interval, condition trend, inspection result, or recurrence-free operating period.
For each high-priority recurrence, document the evidence, current hypothesis, required investigation, action owner, target date, and what future condition will demonstrate that the problem improved. Without verification, the organization can complete corrective actions while the same failure pattern continues.
An RCA is not complete when the presentation is finished. It is complete when the corrective action is implemented and later operating history shows the failure behavior changed.
Combine recurrence with downtime, labor, cost, and consequence to rank asset priorities.
Improve the history needed to distinguish symptom, finding, correction, and verified cause.
Turn repeat failures and other work history into a prioritized maintenance action register.
Use the method yourself, or apply the same reasoning to your facility's CMMS history through XRVE Reliability.
Free maintenance maturity assessment See sample analysis