Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Utility Cut Outage Response 70% With One Sensor Change
Transcript
- Lucas: So there's this story out of central Illinois that I think is a perfect example of the kind of tactical win we talk about on this show. Luna: Yeah? What happened? Lucas: Midwest Electric Cooperative — that's not a sexy name, I know, but they serve about 150,000 customers across a mostly rural area. Their average power outage used to last about four hours. Today it's seventy-two minutes. That's a seventy percent reduction. Luna: Wait — that's a massive improvement. Did they spend millions on fancy grid automation? Lucas: That's the thing. They didn't rip out their substations or install a whole smart grid. They made exactly one operational change: they installed smart fault indicators along their main distribution lines. Luna: Okay, so what's a fault indicator? I think I have the idea but let's be specific. Lucas: Sure. A fault indicator is a small device — about the size of a thick smartphone — that clamps onto a power line. When a fault happens, like a tree limb falling across a wire, it trips a sensor that sends a signal back to the control center. Before these, when a line went down, dispatchers had to rely on customer phone calls to figure out where the problem was. Luna: Right, so customers call in, the dispatcher triangulates from the reports, then sends a crew to check the whole line. That must eat up a lot of time. Lucas: Exactly. The old process took about ninety minutes just to locate the fault. Then the crew has to drive maybe twenty minutes to the patrol point, then drive along the line looking for the break. The smart indicators pinpoint the fault within a few hundred feet and send the location to a dashboard. Luna: So the dashboard tells them exactly which pole to drive to. That's a huge time saver right there. Lucas: It cut the location time from ninety minutes to under fifteen. But here's the part that surprised me: the co-op didn't just buy a bunch of sensors and plug them in. They had to train the dispatch team and the line crews to trust the data. The first few weeks, field crews would still drive the whole line even though the sensor said exactly where the fault was. Luna: Interesting. So the technology wasn't the whole story — the human side was what made it work. Lucas: Right. The operations manager told a local business journal that they ran parallel processes for two months: the old method plus the sensor data. They tracked how often the sensor was right. After about fifty faults, the accuracy was one hundred percent. Then they phased out the double-check. Luna: That's smart. Build trust by proving it works, then flip the switch. I bet that made adoption way smoother than a forced rollout. Lucas: Absolutely. And the ripple effects are interesting. Fewer outage minutes means higher customer satisfaction scores. But it also means lower regulatory penalties — the state public utilities commission has a reliability metric, and the co-op was at risk of fines if their average outage time crossed a threshold. Luna: So the sensor project basically paid for itself by avoiding fines alone. Do you know what the upfront cost was? Lucas: The piece I read said around four hundred thousand dollars for about two hundred sensors, plus integration and training. That's a two-year payback from reduced crew overtime and avoided penalties. After that, it's pure savings. Luna: That's a really clean case. It reminds me of the story we did on the airline fuel savings from a single data feed — small change, big compound impact. Lucas: Exactly. And it's not just utilities. Any operation that relies on mobile crews responding to distributed problems can benefit — think package delivery rerouting, field service repairs, even emergency services. Luna: Yeah, the pattern is the same: reduce the search time, improve the dispatch decision. And the technology has gotten cheap enough that the ROI is compelling even for smaller organizations. Lucas: And that's why we love covering these stories. A focused process tweak, backed by good data and a thoughtful rollout, can produce outsized results. It's not about big budgets — it's about understanding where the bottleneck is and addressing it precisely. Luna: It's exactly the kind of mindset this show is about. And if these conversations have moved your work forward in any small way, I'll echo what Lucas said a few episodes back: listener support is what keeps this ad-free and independent. If you find value here, you can throw a few bucks into the tip jar at buy me a coffee dot com slash fexingo. No pressure, just gratitude. Lucas: Yeah, that goes a long way. And speaking of moving forward — let's talk about how Midwest Electric took this win and applied the same logic to another problem. Luna: Oh, they didn't stop at outage response? Lucas: Nope. The operations team realized they had the same data gap for scheduled maintenance. They used the same sensor network to detect early signs of equipment degradation — like a small increase in voltage drop over weeks — which let them replace failing components before they caused an outage. Luna: So they went from reactive to predictive just by repurposing the same data feed. Lucas: Exactly. The maintenance crews now have a weekly list of 'watch these poles.' They do a visual inspection and often catch a cracked insulator or a frayed wire before it breaks. Their outage rate dropped another fifteen percent in the first year of that program. Luna: It's like compound interest on the same infrastructure investment. The sensors themselves didn't change — the use case did. Lucas: Right. And that's a key lesson: don't just solve the immediate problem. Ask what else the data can tell you. In this case, the sensor stream wasn't just for fault location — it was a continuous health monitor. Luna: So what's the takeaway for operations leaders listening? I think it's: start with one bottleneck, prove the concept, then expand the application. Lucas: Perfectly put. And do the parallel run to build trust. Don't assume your people will like the new tool on day one. Let them see the evidence. That's what made this work. Luna: Al right. And if you've got a similar story from your own industry — a simple operational fix that changed the game — we'd love to hear about it. Drop us a note. Lucas: Until next time, keep looking for those single changes that ripple out.