Predictive maintenance: what Duke Energy's sensor AI does

September 30, 2026 · 5 min · Free, with full transcript

Duke Energy says its machine learning models flag turbine failures two to three weeks out. The episode asks what was actually built and what a smaller operator can copy. The position taken here: the prediction is not the value, the lead time is. Moving a repair from an unplanned trip with spot market replacement power into a scheduled outage is where the money sits. You come away knowing how the sensor-to-model pipeline works, why labelling past failures in the data historian is most of the work, why models stay silent on failure modes absent from training data, how false positive thresholds differ for a turbine versus a cheap pump, and why vendor claims from Hugging Face and OpenAI need cross-checking against your own pilot.

Listen to the podcast

4 min

Chapters

Key takeaways

  • Pick your three most expensive failure modes and pull historian data on the last ten occurrences to look for patterns in the weeks before.
  • Label past failures in your data historian first, since without labelled history the model has nothing to learn from.
  • Set false positive thresholds by asset value: tolerate more false alarms on a turbine, skip the effort on a cheap pump.
  • Check the sensor sampling rate on your most critical asset; if it is minutes rather than seconds, no model can see the early signal.
  • Treat vendor deployment and benchmark claims as marketing until an operator or your own pilot confirms them.
Read the full transcript

Host:Welcome back to Leaders Insights. Read how Duke Energy cut turbine failures using sensor AI, and why it matters this week. Duke Energy just went public with the numbers, and they're the kind that make plant managers sit up. Weeks of warning before a turbine dies. What did they actually build?

Expert:They wired vibration and temperature sensors on their generation fleet into machine learning models — software that learns patterns from data instead of following fixed rules — and trained those models to spot the signature of a failure before it happens. The headline they're pushing is early detection two to three weeks out.

Host:Two to three weeks. Let's pull that claim apart, because "we caught it early" is what every vendor says right before the demo breaks.

Expert:Fair, and here's the part that's real. The value isn't the prediction, it's the lead time against the maintenance calendar. A turbine that fails unplanned costs you replacement power on the spot market — sometimes at peak prices — plus emergency crews. Push that same repair into a scheduled outage and you're paying a fraction. The model earns its keep in the gap between "surprise" and "Tuesday."

Host:So the artefact we're dissecting is that sensor-to-model pipeline. Start at the front. What's actually feeding it?

Expert:High-frequency sensor streams — think thousands of readings per second on bearing vibration, oil temperature, rotor speed. That's the strong part. Turbines are heavily instrumented already, so Duke wasn't installing hardware from scratch, they were finally using signals they'd been throwing away for years.

Host:Throwing away being the polite word for "logging to a database nobody opened."

Expert:Exactly that. Most utilities have a data historian — an archive of decades of sensor readings — sitting cold. Duke's real move was labelling it: going back through past failures and tagging what the sensors looked like in the days before each one. Without that labelled history, the model has nothing to learn from. That's the unglamorous 80% of the work.

Host:Where does it get shaky?

Expert:The failure modes it can't see. A model trained on bearing wear and thermal drift will catch bearing wear and thermal drift. Hit it with a failure type that never appeared in the training data — a manufacturing defect, a one-off — and it stays silent right up to the bang. Predictive maintenance is only as smart as your history is complete, and no fleet's history is complete.

Host:How do they keep it from crying wolf? Because a model that flags a failure every third Tuesday gets ignored by week two.

Expert:That's the failure that kills these projects. If false alarms are high, crews stop trusting the alert and you're back to run-to-failure. The tuning question is where you set the threshold — do you tolerate more false positives to never miss a real one, or the reverse? For a turbine where an unplanned trip costs millions, you lean toward more false alarms. For a cheap pump, you don't bother.

Host:Let's talk tooling, because I've seen the sources. Some of these platform figures come from vendors.

Expert:Right, and I'll flag it. A lot of the "ease of deployment" numbers floating around cite platforms like Hugging Face — that's a company that hosts machine learning models and sells the tooling to run them. Useful, but they're selling the shovels, so treat their "deploy in days" claims as marketing until an operator confirms it. Same with OpenAI's benchmark figures on model performance — they're an AI lab with product to move. Cross-check against your own pilot, not their slide.

Host:So a listener running a mid-size plant. What actually transfers, and what's Duke-only because they've got a research budget you don't?

Expert:What transfers: pick your three most expensive failure modes, pull the historian data on the last ten times they happened, and see if there's a visible pattern in the weeks before. You can do that with a data scientist and a spreadsheet before you spend a cent on a platform.

Host:And what doesn't?

Expert:The fleet-wide scale. Duke can pool patterns across dozens of identical turbines. One plant with three units doesn't have the volume, so you lean harder on physics-based rules and less on pure learning.

Host:Give me the one thing to do Monday.

Expert:Open your data historian and check one thing — what's your sensor sampling rate on your most critical asset. If it's minutes, not seconds, you're already blind to the early signal, and no model fixes that. Fix the sampling first.

Host:Sources for today's episode: TechCrunch AI, The Decoder, Ars Technica AI, Hugging Face (vendor — AI platform), OpenAI (vendor — AI lab). That's a wrap. Fresh AI briefings drop daily at mba-training.com.

Read and go deeper