10 Downtime Horrors Stopped Just in Time:
Saves That Prevented Major Downtime and What We Learned from Each One
© Copyright AssetWatch 2026. All Rights Reserved.
Trusted by Leading Manufacturers
Join us on October 29th to learn how to:
Meet Your Webinar Hosts
Dale Burnham
Condition Monitoring Engineer, AssetWatch
Stay Alert. Stay Ahead. Stay Reliable.
Every plant has close calls. The bearing caught three weeks before it seized. The gearbox pulled during a planned outage instead of on a Saturday night. The temperature trend somebody happened to look at on a Thursday afternoon. Those stories get told once and then forgotten.
The problem is that almost nobody examines them closely. The alert fires, the work gets done, the line keeps running, and the team moves on to the next fire. The pattern connecting one save to the next — the thing that would tell you where your next close call is hiding — never gets extracted.
That pattern is worth more than any individual dollar figure. Across a set of saves you can see which signals show up first, which failure modes your monitoring is structurally blind to, and where detection lead time gets created by technology and then quietly spent by process.
A save records three things a failure never does: which signal appeared first, how much runway that signal bought, and what the failure would have cost if nobody had been watching. It is the clearest evidence a reliability program produces.
The Webinar Topic: Why Saves Matter
What You’ll Learn in This Webinar
Recognize the early-stage signals that precede the most common catastrophic failures — bearing degradation, lubrication failure, thermal and electrical faults — and know which ones your current monitoring would actually catch
Trace a save from first signal to completed work order, and see where detection lead time is created and where it gets spent
Read the P-F curve as a detection window, and understand why the signal most basic monitoring reports is one of the last to change before failure
Identify the failure modes your program is structurally blind to, based on which technologies you have deployed against which assets, and why that is a coverage question, not a budget one
Quantify an avoided failure in the terms operations and finance already use: downtime hours, secondary damage, expedite premiums, and lost throughput
Build a save log your team can learn from, so every close call makes the next one easier to catch
On the Webinar Agenda: 10 Saves From the Field
We’ll walk through 10 detection events from the field, mapping each one back to the stage on the P-F curve where it was caught, and what that lead time made possible.
Your Webinar Takeaways
You’ll leave with a save log template, an early signal reference, a P-F curve technology map, and a coverage self-check, all usable with the monitoring and maintenance history your team already has.
In this session, AssetWatch Condition Monitoring Engineers Dale Burnham, Steve Gierden, Dustin Moore, and Jim Hoffman will share 10 real equipment saves from manufacturing. As experts who work directly with AssetWatch customers to monitor their equipment, they’ll walk through each save—from the early signal and failure scenario avoided to the operational and financial impact.
Your Webinar Takeaways
WEBINAR
October 29th
2-3pm EST
Hosted By: Dale Burnham, Steve Gierden, Jim Hoffman & Dustin Moore.
LIVE WEBINAR / OCTOBER 29
Steve Gierden
Jim Hoffman
Dustin Moore
Condition Monitoring Engineer, AssetWatch
Condition Monitoring Engineer, AssetWatch
Condition Monitoring Engineering Manager, AssetWatch
