Send us Fan Mail

Vibration analysis can be the difference between planned work and an expensive surprise, but only if you collect the right data in the right way. After a week packed with fresh ideas from Fluke’s Accelerate event in Austin, we sit down and get practical about what vibration monitoring can detect, what it struggles with, and why so many programmes fail on strategy rather than technology.

We unpack the fundamentals that quietly shape every result: how long you capture the time waveform, how high your frequency range needs to be, and what that means for bearings, gears, envelope analysis, and early fault detection. From there we compare the three big acquisition routes. Handheld data collection brings high-resolution flexibility and the huge advantage of having an engineer at the machine, but it can become inefficient when experts spend time gathering data on low-risk assets or when the plant isn’t running on survey day. Wireless vibration sensors can fill the gaps with better trending and easier installation, yet they come with real-world constraints: connectivity dropouts, battery life, limited frequency response, and devices that often collect data without understanding load or running state.

Then we make the case for wired continuous monitoring on the most critical equipment: stable sensors in the load zone, long captures for slow-speed machinery, smarter alarms tied to operating conditions, and far fewer blind spots. We also talk capability building, from training teams to collect repeatable data to why you should be cautious of black-box AI recommendations if nobody on site understands the basics.

If you want a vibration analysis strategy that actually reduces downtime, subscribe, share this with your maintenance team, and leave us a review. What assets are you trying to protect right now?

Support the show

Send us Fan Mail

The engineering skills gap is already shaping what factories can deliver, how reliable our assets can be, and how quickly new infrastructure can scale. We’re joined by Parker, president of Fluke, and we dig into what we’re hearing from the next generation of technicians and engineers and what leaders can do right now to make these careers easier to discover and harder to ignore.

A highlight comes from our time with students at Texas State Technical College. The talent pipeline isn’t “one type” of person: we meet people straight out of high school, veterans bringing a decade of service, and career changers who want a fresh start and a future they can control. That range forces a rethink of how we talk about the trades, reliability engineering, and technical careers. When we clearly explain the menu of opportunities, from working globally to owning your own business, we give people a reason to lean in.

We also get practical about education and early exposure. Schools are moving beyond traditional shop class into modern STEM programmes, including robotics, 3D printing, and automation. The goal is to make hands-on learning engaging and fun while still building real skill. Parker shares how Fluke supports the next generation through internships, training, and partnerships that put current tools into classrooms, and we connect those skills to high-growth areas like data centres where power quality and reliability matter every day.

If you care about workforce development, manufacturing, and keeping great people, you’ll take away a simple message: meaning and mentorship are not “nice to have”. They are the system. Subscribe, share this with someone starting their career, and leave us a review with your answer: what first pulled you towards engineering or the trades?

Support the show

Send us Fan Mail

You can have all the data in the world coming out of your condition monitoring programme… vibration data, OGI surveys, thermography images, air leak reports… and still not improve reliability.

And it usually comes down to one simple thing.

No one can actually see what’s going on end to end.

In this episode, we talk properly about that. The gap between finding issues and actually fixing them. Because too often the insight is there, but it’s sat in emails, reports, or spreadsheets and nothing really moves forward.

We get into the systems we’re building to solve that. Things like customer portals where everything sits in one place. Recommendations, evidence, current status, deadlines. So actions don’t just disappear or get forgotten about. Everyone can see what needs doing and where things are at.

We also break down what should sit where, because this is where a lot of people get it wrong.

Your CMMS is there to manage work. History, failure codes, maintenance actions. That’s its job. But it’s not built to visualise vibration data or leak images. Trying to force it into that role just creates friction.

That’s why we’re pushing towards more of a reliability hub approach. Something that sits alongside your CMMS and, where possible, links into it. So when you raise a recommendation, it can turn straight into a work order with proper traceability.

And where integration isn’t possible because of security or system limitations, we still need that feedback loop. So we talk about simple, practical ways to capture comments, updates, and closures without slowing engineers down or adding more admin.

We also get into the value of closing the loop properly on repairs.

When you can link the fix back to the original condition monitoring finding, everything becomes clearer. Photos, verification, root cause… it all starts to tell a story. People understand what those “high readings” actually meant. And more importantly, what needs to change to stop it happening again.

There’s also a lot of money being left on the table in areas people overlook. Air leaks are a big one. They just sit there costing thousands until someone actually takes ownership and fixes them.

And we touch on RCM and FMECA as well. How to keep them simple and useful, rather than turning them into massive Excel exercises that no one wants to touch.

If you’re serious about predictive maintenance, defect elimination, and building systems that actually work for engineers, this one will land.

If it does, share it with someone you work with, subscribe to the podcast, and leave a review so we can get it out to more people.

And I’d be interested to hear this…

What would give you better visibility on your site right now?

Support the show