Unit 7 / 11

Predictive Maintenance: Transformer, Turbine and Equipment Health

Gains:

  • Explain the business value of failure modes, sensor data and predictive maintenance in energy equipment.
  • Ability to configure anomaly detection, remaining useful life estimation and alarm prioritization with artificial intelligence
  • Ability to manage the false alarm/missed fault balance and the need for expert approval in maintenance decisions

Equipment failure in a power system is expensive and sometimes dangerous: a power transformer explosion causes millions of dollars in damage and long outages; Breaking a wind turbine gearbox means months of lost production. Conventional maintenance operates on either a "fix it when it breaks" (breakdown maintenance) or "replace by schedule" (periodic maintenance) logic; Both intervene either too late or too early. Predictive maintenance aims to constantly monitor the actual condition of the equipment, predict the malfunction before it occurs, and intervene just in time. Artificial intelligence is a powerful tool in processing the flood of sensors and producing this insight. In this unit, we will learn about failure modes, AI-assisted anomaly detection and remaining life estimation, and their limits.

Failure Modes and Sensor Data

The basis of predictive maintenance is the fact that equipment leaves traces as it breaks down. A malfunction does not occur suddenly, but usually develops as a process, and this process produces measurable symptoms.

  • Power transformer: Oil temperature, load, and especially dissolved gas analysis (DGA; measurement of gases accumulated in the oil). An increase in certain gases indicates internal arcing, overheating, or insulation deterioration.
  • Wind turbine: Gearbox and bearing vibration, temperature, oil particles, deviation from power curve. Bearing degradation produces characteristic vibration frequencies.
  • Cable and line: Partial discharge (small electrical discharges in the insulation), temperature.
  • Breaker and switchgear: Number of on-off switches, opening time, contact resistance.

Artificial intelligence captures subtle trends and multivariate patterns in these signals that the human eye would miss. An anomaly is a statistical deviation of data from normal behavior; This is often the first signal of predictive maintenance.

Tip: Good predictive maintenance starts with knowing "normal" well. It is not possible to recognize deviation without knowing what kind of sensor signature a piece of equipment produces when operating properly. So the first investment is to establish a clean foundation of "healthy behavior".

Two Essential Tasks: Anomaly Detection and Remaining Life

Artificial intelligence has two main tasks in predictive maintenance.

Anomaly detection is catching early when equipment deviates from normal. The model learns healthy behavior and tests incoming data against it; deviation generates an alarm. The most critical parameter here is the threshold: how much deviation counts as an alarm?

Remaining Useful Life (RUL) is an estimate of how long the equipment has until failure. This allows maintenance to be planned (parts ordering, outage window). The RUL estimate is inherently uncertain and should be given with a range.

False Alarm / Missed Fault Balance

At the heart of predictive maintenance is balance. False alarm (false positive) is producing an alarm when there is no fault; It results in unnecessary maintenance, wasted downtime and – most dangerously – the team's loss of confidence in alarms (the "wolf has arrived" effect). A missed fault (false negative) is failure to predict the actual fault; Unexpected explosion means damage and safety risk.

If you lower the threshold, missed faults decrease but false alarms increase; If you increase it, the opposite happens. The correct threshold is set according to the cost of these two failures: the cost of a missed fault of a distribution transformer is much higher than that of a street lamp, so the threshold is kept more sensitive (more susceptible to false alarms) in critical equipment.

Caution: Saying "the model is 95 percent accurate" is misleading in predictive maintenance. Because failures are rare, even a model that produces no alarms may be 95 percent "accurate" — but it won't catch even a single actual failure. Therefore, success is measured individually by missed failure and false alarm rates, not by overall accuracy.

Step by Step: AI-Powered Predictive Maintenance

Step 1 — Establish the healthy foundation. Learn the normal operating signature of the equipment with sufficient data.

Step 2 — Select and verify sensors. Signals appropriate to the failure mode (vibration, DGA, temperature); sensor calibration is checked.

Step 3 — Build an anomaly model. Model that detects deviation from normal; The threshold is set based on equipment criticality.

Step 4 — Prioritize alarms. Not all deviations are of the same urgency; AI sorts alarms by severity and possible fault type.

Step 5 — Expert verification. Every significant alarm goes to the maintenance engineer for review; AI doesn't diagnose, it offers hypotheses and priorities.

Step 6 — Feedback. Actual fault/normal results are fed back to the model; The threshold and model are improved.

Three Mini Cases: By the Numbers

Case 1 — Early warning of transformer. In DGA data of a power transformer, AI captured a slow but steady increase of certain gases (ethylene); a single measurement was within the normal range, but the trend was abnormal. Expert review found a hot spot (overheating connection). A possible malfunction was prevented by planned intervention; The estimated avoided damage was in the order of several million lira.

Case 2 — The wolf came effect. In one wind field the threshold was set too low; The model was producing dozens of false vibration alarms per week. Over time, the team began to ignore the alarms and missed an actual bearing failure. When the threshold was recalibrated based on actual failures in historical data, false alarms dropped to one per week and confidence returned.

Case 3 — RUL range. For a gearbox the model said "remaining life is approximately 6 weeks" but as an odd number. In fact, uncertainty has increased; The part arrived in the 9th week, the failure occurred in the 5th week and there was an unplanned outage. In the next exercise, the RUL was given with an interval ("3-8 weeks, 80 percent confidence") and the parts order was brought forward based on a reasonable worst-case scenario.

Weak Prompt / Strong Prompt

Weak prompt:

Look at this vibration data, is there any malfunction?[data]

Powerful prompt:

Your role: Predictive maintenance analyst. Equipment: wind turbine gearbox.- First summarize the normal (healthy) behavior in the data; identify the anomaly against it.- Prioritize deviations by severity and possible failure type; DO NOT make a definitive diagnosis, generate hypotheses. - For each hypothesis, indicate which additional measurement/examination will confirm it. - Consider the balance of false alarms and missed faults; Justify your threshold recommendation based on the criticality of this equipment. - If RUL is requested, give it with a confidence interval, not a single number. Data: [vibration/temperature series]

The powerful prompt defines normal first, asks for hypotheses instead of diagnoses, adds a verification step and threshold offset, prompts RUL at intervals — avoiding the classic pitfalls of predictive maintenance from the start.

Four Copiable Templates

1) Healthy basic extraction:

Extract the normal/healthy operating signature from this equipment's data: typical ranges, seasonal/load dependent variation. Then define the anomaly on this basis. Distinguish changes that can be explained by load or temperature from true anomalies.

2) Alarm prioritization:

Prioritize the following deviations by severity, rate of development, and possible failure type. For each: urgency (urgent/monitor/normal), probable cause hypotheses, and verification step. Making a definitive diagnosis; A decision note is issued to the maintenance engineer.

3) Threshold balance analysis:

Show with historical data the impact of different thresholds on the number of false alarms and missed faults for this anomaly score. Suggest and justify thresholds taking into account the criticality of the equipment ([high/medium/low]). Look at the two error types separately, not the overall accuracy.

4) RUL uncertainty report:

Give your estimate of remaining useful life with a range and confidence level. When to expect failure in the "worst-plausible scenario"? Recommend parts procurement and outage planning based on this worst-case scenario.

Fault Mode and Signal Table

equipment

monitored signal

early symptom

power transformer

DGA, oil temperature

Gas increase, hot spot

wind turbine

Vibration, oil particle

Bearing/gear frequency

cable/line

Partial discharge, temperature

insulation deterioration

cutter

Opening time, contact resistance

Mechanical deceleration

generator

Vibration, temperature, current

imbalance, friction

Common mistakes

  • Relying on general accuracy. Since failures are rare, even “no alarm” shows high accuracy; The missed fault must be measured separately.
  • Setting the threshold incorrectly. Too low a threshold will result in a "wolf has arrived" effect, too high a threshold will result in a missed fault.
  • Having AI diagnose. AI generates hypotheses and priorities; The final diagnosis and intervention decision belongs to the specialist.
  • Giving RUL an odd number. Lifetime estimation given without uncertainty interval will lead to unplanned outage.
  • Searching for anomalies without recognizing the normal. Detection made without establishing a healthy foundation may mistake the load/seasonal change as a malfunction.

In summary

Predictive maintenance aims to intervene just in time by predicting the malfunction from the sensor traces of the equipment. Artificial intelligence is powerful in anomaly detection and remaining life prediction; but its success is measured not by overall accuracy but by the balance of false alarms and missed faults. The threshold is set based on equipment criticality, AI generates hypotheses rather than diagnoses, RUL is spaced out, and every significant alarm goes to expert verification.

Application task

Get sensor time series of a piece of equipment (transformer, turbine, motor). Request an analysis from the AI ​​with the “Healthy baseline extraction” and “Alarm prioritization” templates. Make sure you define normal first; Then ask yourself whether any deviation found can be explained by load or temperature. Choose a threshold and write how that threshold changes the false alarm/missed fault balance.

checklist

  • [ ] I have defined the basis for healthy/normal behavior of the equipment
  • [ ] I selected sensor signals suitable for the fault mode and considered calibration
  • [ ] I separated the anomaly from the load/season effect
  • [ ] I determined the threshold based on equipment criticality and the cost of the two failure types
  • [ ] I looked at false alarm / missed failure rates rather than overall accuracy
  • [ ] I asked AI for hypothesis and verification step, not diagnosis
  • [ ] I presented the RUL estimate with confidence interval and subject to expert approval