Repeat fault analysis for mining equipment starts with record quality

Repeat-fault analysis begins before a chart is built. The underlying records must let a reviewer distinguish the same observed symptom, the same subsystem and the same confirmed cause. If those states are blurred together, a recurrence count can look precise while grouping different problems.

This guide focuses on record quality and review structure. It does not provide machine-specific diagnosis or claim that every repeated symptom has one root cause.

Define what “repeat” means for the review

Write the grouping rule before selecting records. A review may be looking for the same reported symptom on one asset, the same confirmed cause across a fleet, a reopened fault after incomplete verification or a new recurrence after return to service.

These are different questions. Combining them into one repeat-fault number makes it difficult to decide what action the result supports.

Confirm stable asset and fault identity

Each record needs an unambiguous asset, fault identifier, relevant subsystem, work reference, report time and current status. Check for duplicate records created for the same active event before counting later entries as recurrences.

Model, fleet and component fields can support broader comparison, but the review still needs a stable machine-level history underneath them.

Normalise the symptom without inventing a cause

Field descriptions can use different language for the same observed behaviour. Grouping rules may normalise wording, but the original report should remain visible. “Loss of drive under load” and “failed transmission” should not be treated as equivalent because one is a symptom and the other is a cause hypothesis.

Preserve operating conditions such as load, duty, temperature, environment and whether the event was intermittent. Those differences may explain why two similar titles are not the same fault pattern.

Check the repair and verification record

A closed status alone does not show that the original symptom was cleared. Review the repair action, parts used, after-repair checks, operating conditions during verification and any stated limitation or follow-up.

If verification was incomplete, classify the record accordingly. A later report may be continuation of an unresolved event rather than a new recurrence.

Build a synthetic fault timeline

This fictional example shows how record states change the interpretation. It is not based on customer or machine data.

1. Event A: intermittent warning under load, connection cleaned, symptom not reproduced during limited verification.
2. Event B: same warning two shifts later, earlier verification limitation visible, fault reopened rather than counted as a new cause.
3. Event C: damaged harness confirmed and repaired, full authorised verification completed, equipment returned to service.
4. Event D: similar warning six weeks later, different subsystem finding confirmed. Same symptom family, different recorded cause.

A simple title count could label all four events as one repeat cause. The field record supports a more careful conclusion.

Identify missing fields before calculating measures

Time-to-repair, recurrence interval and repeat-offender views depend on complete and consistently defined timestamps. Missing report, work-start, verification or return-to-service times should remain visible in the result.

The same rule applies to cause and repair fields. Do not fill an unknown value with the most common category merely to complete the chart.

Drill every pattern back to its source records

A reviewer should be able to move from a fleet or asset pattern to the contributing faults, findings, repairs and verification evidence. This exposes inconsistent grouping and lets a qualified person challenge the conclusion.

Use the maintenance record quality guide before treating an operational measure as decision-ready.

Repeat-fault record checklist

• Stable asset, subsystem, fault and work identity
• Original symptom and operating conditions
• Evidence, findings and confirmed cause where known
• Repair action and parts used
• After-repair verification and its limitations
• Report, start, handover, closeout and return-to-service times where applicable
• Reopened, continued or new-recurrence classification
• Link from every grouped result to the source record

Start with the mining equipment fault report template, then see how attributable history can support asset and reliability review when the required inputs are present.