The Operations Podcast with Fexingo · 2026-07-01 · 9 min
Key moments - from our scoring
Substance score
70 / 100
Five dimensions, 20 points each
Most predictive maintenance projects fail to scale because data collection becomes divorced from action - reports sit in a specialist's inbox while equipment fails. This Indiana steel mill, producing specialty alloy bars for automotive and aerospace, took a different approach. They installed vibration analysis, thermal imaging, and oil debris monitoring on their most critical assets (rolling mill stands, cooling systems, drive motors), but more importantly, they built a traffic-light dashboard visible to every operator: green for normal, yellow for trend-watch, red for stop-and-call-maintenance. Veteran operators with decades of experience initially resisted, but when the accelerometers caught a bearing failure 10 days before audible symptoms - a window that let them schedule a two-hour fix instead of an 18-hour emergency repair - skepticism shifted to trust. The mill prevented roughly one major breakdown per quarter, saving $14,000 per hour of downtime avoided. They also shifted maintenance from reactive firefighting to planned work, cutting overtime by 40 percent and improving crew retention. This wasn't a fancy AI implementation; it was basic sensors wrapped in a clear operational protocol.
The vibration sensors typically provided 10 days of warning before a bearing or cooling fan would fail, giving the maintenance team time to order parts and schedule replacements during planned shift changes instead of responding to failures at 2 AM.
They used three complementary technologies: vibration analysis (for rotating equipment like bearings and fans), thermal imaging (to catch electrical hot spots and resistance buildup in contactors), and oil debris analysis (to detect internal wear in gearboxes).
They ran a three-month pilot on two machines where operators could see the sensor data alongside their own observations; once the system proved correct multiple times (catching issues the human ear missed), trust built quickly, especially with a simple traffic-light dashboard and reward bonuses tied to downtime targets.
The mill calculated that each hour of unplanned downtime cost approximately $14,000 in lost output, meaning preventing even one major breakdown per quarter paid for the entire sensor installation in the first year.
Maintenance shifted from reactive firefighting to planned work, reducing overtime by 40 percent and improving crew retention because the work became predictable and less chaotic, addressing a major burnout point in traditional maintenance roles.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode delivers substantive operational insights about predictive maintenance implementation, including specific failure modes, the critical importance of decision protocols over technology alone, and the cultural shifts required. However, it relies heavily on one case study and lacks diversity of examples or contrarian perspectives that would push it toward 17+. The mechanics of the traffic-light system and the $14,000/hour downtime cost are genuinely useful, but the core idea - sensors plus clear decision rules - is not novel to practitioners in reliability engineering.
The key was the decision protocol they layered on top. Most plants collect data, but the data sits in a specialist's report that comes out weekly. By then, the bearing has already failed.
Start small, but tie the data to a decision rule that the operator owns. The technology is the easy part. The hard part is changing the workflow so that the data actually triggers action.
The episode presents a solid execution story but lacks original frameworks or contrarian thinking. The three-sensor stack (vibration, thermal, oil analysis) and the traffic-light protocol are sensible and effective, but not novel - these are standard reliability practices. The insight that 'process beats technology' and that operators need ownership are valuable but circulate widely in operations literature. No first-principles challenge to existing thinking.
They built a very specific framework around three sensing technologies: vibration analysis, thermal imaging, and oil debris analysis.
Operations improvements often come from process design, not just technology.
Lucas appears to be the primary voice and speaks with operational credibility about a real case, but he is not introduced as a named practitioner or executive from the mill itself. Luna is a co-host asking questions. Neither guest is identified with verifiable credentials or senior operational roles at scale. The case study is real and grounded, but the lack of direct testimony from the mill's own operations leaders (maintenance manager, plant manager, or engineer) weakens caliber. This reads like secondary reporting rather than firsthand experience.
Lucas: It's a midsized operation - about 400 employees - owned by a private group.
Luna: And the traffic-light dashboard is a great example of making that decision rule visible to everyone.
The episode is strong here: specific company size (400 employees), named technologies (vibration, thermal, oil debris), quantified results (80% downtime reduction, $12M → $2.5M savings, $14,000/hour cost of downtime, 10-day lead time on cooling fan failure, 20-minute repair on electrical contactor, 40% overtime reduction, 18-month timeline). The rolling mill stands, cooling systems, and 30→120 asset expansion are concrete. The 1,800 RPM example and 15-degree thermal variance add granularity. Only minor deduction because the mill is unnamed and some metrics lack exact sources.
Before the project, they were losing about 12 million dollars a year in lost production from unexpected breakdowns. Luna: And after? Lucas: Under 2.5 million.
The mill calculated that every hour of unplanned downtime cost them roughly $14,000 in lost output.
Luna asks solid clarifying questions ('What made this implementation different?' 'Did they focus on one type of asset?') and identifies key insights ('So they pushed the interpretation down to the floor'). However, questions are mostly open-ended setup rather than sharp pushback or productive disagreement. There's no challenge to the narrative, no exploration of failure cases, and no skepticism about the 80% claim. The podcast is conversational but soft; a stronger host would have pressed on scalability, long-term sustainability, or what didn't work. The pivots to fundraising break flow.
Luna: So the operators had ownership. They weren't just data entry clerks.
Luna: Ten days of lead time is enormous. What did they do with that window?
Computed from the transcript - who did the talking, and the words that came up most.
Lucas and Luna examine how a midsized steel mill in Indiana slashed unplanned equipment downtime by 80 percent over 18 months. They break down the specific predictive maintenance framework the mill adopted - vibration analysis, thermal imaging, and a tiered response protocol - and walk through the financial impact: from $12 million in annual lost production to under $2.5 million. The episode digs into why most predictive maintenance programs fail and what this mill did differently: they tied sensor data directly to a simple traffic-light dashboard that frontline operators owned. Lucas and Luna also discuss the cultural shift required to get veteran mill workers to trust algorithms over gut feel. A practical look at how operations teams can bridge the gap between data and action. #PredictiveMaintenance #SteelMill #IndustrialOperations #DowntimeReduction #VibrationAnalysis #ThermalImaging #Manufacturing #LeanOperations #Industry40 #MaintenanceStrategy #AssetManagement #DataDriven #OperatorEmpowerment #Business #OperationsPodcast #FexingoBusiness #BusinessPodcast #LucasAndLuna Keep every episode free: buymeacoffee.com/fexingo
Transcribed and scored by The B2B Podcast Index.
Lucas: Luna, when you hear the phrase 'predictive maintenance,' what comes to mind? Luna: Honestly? A lot of sensors, a lot of data dashboards, and usually a pilot project that never scales. Lucas: Right.
That's the stereotype, and it's not unfair. But there's a steel mill in Indiana that actually made it work - they cut unplanned downtime by 80 percent over 18 months. Luna: Eighty percent? That's not incremental.
That's a transformation. What's the name of the mill? Lucas: It's a midsized operation - about 400 employees - owned by a private group. They produce specialty alloy bars for automotive and aerospace.
Before the project, they were losing about 12 million dollars a year in lost production from unexpected breakdowns. Luna: And after? Lucas: Under 2.5 million.
The interesting part is how they got there. They didn't just buy a fancy software platform and hope for the best. They built a very specific framework around three sensing technologies: vibration analysis, thermal imaging, and oil debris analysis. Luna: Those are standard tools in the reliability world.
What made this implementation different? Lucas: The key was the decision protocol they layered on top. Most plants collect data, but the data sits in a specialist's report that comes out weekly. By then, the bearing has already failed.
This mill set up a traffic-light dashboard that every operator saw in real time. Green means everything's normal. Yellow means there's a trend but no immediate action - just monitor. Red means stop the machine and call the maintenance team within the hour.
Luna: So they pushed the interpretation down to the floor. That's a cultural shift. Lucas: Huge cultural shift. The veteran operators - some with 25 years on the job - initially hated it.
They'd say, 'I can tell a bad bearing by the sound. I don't need a computer.' And to be fair, sometimes they were right. But the data caught things the human ear couldn't.
For example, a gradual rise in vibration on a cooling fan that was spinning at 1,800 RPM - barely audible change, but the accelerometer picked it up 10 days before failure. Luna: Ten days of lead time is enormous. What did they do with that window? Lucas: They scheduled the replacement during a planned shift change, not during a rush order.
The maintenance team had time to order the exact replacement part, pull the right tools, and do the swap in under two hours. Compare that to the old way: the fan seizes at 2 AM on a Saturday, the whole line stops for 18 hours while they scramble for a replacement. Luna: And the cost difference between a planned two-hour fix and an 18-hour emergency repair is enormous. Lucas: Exactly.
The mill calculated that every hour of unplanned downtime cost them roughly $14,000 in lost output. So even preventing one major breakdown per quarter paid for the entire sensor installation within the first year. Luna: Let's talk about the failure modes they caught. Vibration analysis is great for rotating equipment.
Thermal imaging catches electrical hot spots. Oil debris tells you about internal wear. Did they focus on one type of asset? Lucas: They started with the critical path assets - the rolling mill stands and the cooling systems.
About 30 machines. Within six months, they expanded to 120 assets across the plant. The biggest wins came from the rolling mill stands themselves. Those are massive machines that shape red-hot steel billets.
If one stand goes down, the whole line stops. Luna: What was the most surprising failure they caught? Lucas: An electrical cabinet that powers a main drive motor. Thermal imaging showed a hot spot on a contactor that was 15 degrees above normal.
The operator flagged it red, maintenance opened the cabinet, and found that a bolt had loosened, causing resistance and heat buildup. If that contactor had failed, the motor would have stopped under load, potentially damaging the gearbox. They fixed it in 20 minutes during a lunch break. Luna: That's the kind of catch that never makes it into a ROI spreadsheet but saves you from a cascading failure.
Lucas: Right. And that's the thing about predictive maintenance done well - it prevents the secondary damage. A bearing seizes, it can take out the shaft, the coupling, even the motor. By catching it early, you save not just the bearing but everything downstream.
Luna: What about the human side? You mentioned the operators were skeptical. How did the mill get buy-in? Lucas: They ran a pilot on two machines for three months.
They let the operators see the sensor data alongside their own observations. When the system flagged a yellow on a pump that the operator thought was fine, they'd check together. After a few times where the data was right and the human was wrong, trust started to build. They also made the traffic-light dashboard very simple - big green, yellow, red circles on a screen mounted at each workstation.
No complex charts. Luna: Simplicity at the point of use. That's a lesson that applies way beyond steel mills. Lucas: Absolutely.
And they tied it to a reward system. Each shift had a downtime target. If they hit it, the whole crew got a bonus. That aligned everyone's incentives toward catching problems early rather than just running through the pain.
Luna: So the operators had ownership. They weren't just data entry clerks. Lucas: Exactly. And the maintenance team's role shifted too.
Instead of being firefighters, they became planners. They spent more time prepping for scheduled replacements and less time scrambling. The mill reported a 40 percent reduction in overtime for maintenance staff. Luna: That's a quality of life improvement.
I've heard maintenance crews burn out fast in reactive environments. Lucas: Yeah, the turnover in that department dropped significantly. People stayed because the work became more predictable and less chaotic. Luna: You know, speaking of keeping things running smoothly - and this is a bit of a sidestep - but shows like this one rely on a similar kind of support to keep going.
If these conversations have moved your work forward in some small way, a couple of dollars a month is genuinely what keeps them ad-free and independent. Lucas: It's true. We don't run sponsor spots or track you for ads. That's only possible because listeners who find value in the show chip in at buy me a coffee dot com slash fexingo.
It's a small thing that makes a real difference. Luna: Yeah. And we really appreciate it. Now, back to the mill - after the first year, did they hit any plateaus?
Lucas: They did. The low-hanging fruit was easy. Once you've caught the failing bearings and loose connections, the remaining failures are harder to predict. They had to add oil analysis for gearboxes and start tracking mean time between failure more granularly to set better thresholds.
Luna: So the first 50 percent reduction came quickly, and the next 30 percent required more sophistication. Lucas: Exactly. The last 20 percent is the hardest. They're now looking at using machine learning to combine vibration and temperature data to detect patterns that no single sensor would catch.
But the foundation is already solid. They went from reactive to mostly predictive in 18 months. Luna: What would you say is the one takeaway for an operations manager listening who wants to try something similar? Lucas: Start small, but tie the data to a decision rule that the operator owns.
The technology is the easy part. The hard part is changing the workflow so that the data actually triggers action. If you just install sensors and send reports to a reliability engineer, you'll get a shelf full of reports. But if you put a red light on the machine and say 'stop when this lights up,' you'll get results.
Luna: And the traffic-light dashboard is a great example of making that decision rule visible to everyone. Lucas: Right. It's not about the fanciest AI. It's about closing the loop between data and action.
This mill proved that with basic sensors and a clear protocol, you can cut downtime by 80 percent. And they're not a tech company - they're a 400-person steel mill in Indiana. Luna: That's the kind of story that makes you rethink what's possible in a traditional industry. Lucas: Yeah.
It's a reminder that operations improvements often come from process design, not just technology. And when you get both right, the numbers speak for themselves.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
Less about Models; More about ArchitecturePractical AI · on Predictive maintenance85 / 100
From Crisis to Innovation: How Authenticity and AI Are Reshaping B2B Publishing and Field Service | Kris Oldland | UNSCRIPTED Ep. 374UNSCRIPTED · on Predictive maintenance81 / 100
How to Design AI for Scale From Day One with Tom Greenlees, Intelligent Core [090]The Business of AI · on Predictive maintenance80 / 100
From Sales to Spare Parts - Festo´s AI solutionsIndustrial AI Podcast · on Predictive maintenance80 / 100
Why Aviation Maintenance Is the Next Generation's Best-Kept Career Secret | Jennifer Radtke, BoeingThe Lost Art Of the Skilled Trades · on Predictive maintenance80 / 100
The Trick to Aligning Tech, People & Process for Operational SuccessExperts of Experience · on Predictive maintenance80 / 100
How a Steel Plant Cut Unplanned Downtime by 70 Percent with Ops82 / 100How a Solar Farm Cut Panel Cleaning Costs by 40 PercentHow a Food Bank Cut Spoilage by 60 Percent with Demand ForecastingHow a Hospital Cut Supply Waste by 47 Percent with OperationsHow a Chip Factory Cut Wafer Scrap by 45 Percent