Send us Fan Mail

If you’ve ever thought, “We’ve got condition monitoring, we’ve got a CMMS, so why are we still firefighting?”, you’re not alone and you’re not imagining it. We talk about the uncomfortable gap between doing “the right activities” and actually getting reliability results, and why so many plants stay trapped in reactive maintenance even when the data is screaming for change.

We break down why benchmarking is the starting line. Until you can compare your current maintenance practices to a recognised standard, you cannot see the real opportunity or even agree on what “good” looks like. That’s the thinking behind the MRL Core Audit we’ve built at Maintain Reliability: an external, honest assessment aligned to the EFQM framework and the key elements of maintenance practice, designed to give a true baseline that often mirrors what you see in OEE.

From there we get practical. An audit is pointless if it lands on a desk and dies, so we explain how findings turn into a roadmap built around the biggest gaps, quick wins that keep momentum, and clear roles and responsibilities so actions get finished. We also talk ROI, because culture change and proactive maintenance cost money up front, and leaders need to understand what they get back in reduced downtime, higher availability, lower maintenance cost and lower risk.

We finish by challenging a common trap: adding sensors, online systems or AI “because we can” instead of fixing the upstream causes. Design for reliability, acceptance testing, maintainability and better cross-team communication can reduce failures and mean time to repair in ways monitoring simply can’t.

Subscribe for more straight-talking reliability engineering and asset management conversations, share this with someone stuck in firefighting, and leave a review telling us what’s the biggest barrier to proactive maintenance at your site.

Support the show

Send us Fan Mail

Breakdown culture is expensive, exhausting, and strangely normal in a lot of factories. We wanted a straight-talking conversation about what actually shifts the dial, so we sat down with Dan Bridges to trace his reliability journey through soft drinks manufacturing and the hard lessons that come with it. If you’ve ever watched a team do “regimented” maintenance only to see the same faults return, you’ll recognise the trap: activity without value, OEM checklists without context, and a blanket approach that never goes deep enough.

We dig into how reliability leaders win senior leadership support by changing the language from engineering detail to outcomes like uptime, trend improvement, reduced overtime, and the true cost of firefighting. We also talk about culture on the shop floor: why being visible matters, why authenticity builds trust faster than a polished persona, and how choosing your battles keeps progress moving when resources are tight. Along the way, we tackle the reality of headcount reductions, contractor dependency, and what it takes to retain site knowledge and engineer motivation.

Training and development get a proper rethink too. We explore why rigid qualifications and exam pressure can miss the point, and why targeted courses, mentoring, and understanding learning styles can build stronger engineers sooner. Tools like DISC profiling come up as a practical way to communicate better across different personality types, especially when a team’s energy levels and decision styles vary.

We finish by challenging the predictive maintenance hype: wireless sensors, Industry 4.0 marketing, and AI promises do not create reliability on their own. Without criticality, CMMS discipline, and defect elimination, you just collect data nobody has time to use. If you found this useful, subscribe, share it with a reliability mate, and leave us a review. What part of your maintenance strategy needs the biggest reset?

Support the show

Send us Fan Mail

AI is moving at breakneck speed, but the plant floor still runs on trust, habit, and hard-earned routines. We sit down with Vinit to unpack the real challenge behind “digital transformation” in reliability: designing tools that work for an experienced workforce that values buttons, PDFs, and proven processes, while also meeting the expectations of early-career engineers who want fast answers, mobile access, and connected systems.

We get practical about what actually closes the gap. Instead of big-bang rollouts, we talk roadmaps, small experiments, and pilots that demonstrate value without risking operations. We also draw a firm line around safety and accuracy: in reliability engineering, there is no room for hallucination. A fault has to be a fault, and any AI-assisted workflow must be validated, secure, and compliant across industries and markets.

From there, we zoom out to connected reliability and why data trapped in folders and silos limits predictive maintenance, pattern recognition, and decision-making. We explore how central platforms such as CMMS and connected ecosystems enable sharing, faster analysis, and better prioritisation, even when legacy equipment and mixed vendors complicate integration. We also touch on how “retro” tech keeps a foothold, and why value is better measured by outcomes than by the physical box in your hand.

If you care about asset reliability, maintenance strategy, industrial IoT, condition monitoring, and the culture that makes change stick, you’ll take plenty from this conversation. Subscribe for more, share it with a colleague who’s wrestling with adoption, and leave us a review with your answer: what would make new tech truly trustworthy in your plant?

Support the show

Send us Fan Mail

Your CMMS probably knows more about your plant than any one person does, but most of that information is buried in reports, menus and half-completed work orders.

While we were at Accelerate 2026, we sat down with Jay Hack to look at four practical ways generative AI is being used to make maintenance and reliability work easier, faster and more accurate.

The first was the ability to simply talk to your data inside eMaint. Instead of needing to know how to build reports or search through different parts of the system, you can ask a normal question and get an answer back from the CMMS.

But as Jay explains, the AI itself is not necessarily the hardest part. The real challenge is making sure the right people have access to the right information, especially across different sites, departments and levels of the business.

We then looked at two areas that could make a real difference on the plant floor.

The first is automated SOP generation. The system can scan OEM manuals and technical PDFs and turn that information into practical procedures that can be added to work orders. There is still a human involved in checking and approving the content, but it could save a huge amount of time and help improve consistency.

The second is voice-based work requests. Technicians and operators can speak naturally into the system, even while they are out on the plant, and the CMMS can then populate the relevant fields.

Instead of receiving a work request that just says “pump broken”, you can capture what the operator saw, heard or experienced and create a much better maintenance history.

We also discussed how AI could support global teams by searching document libraries, translating manuals and helping standardise maintenance and reliability practices across different sites and countries.

Looking further ahead, there is also the potential for AI-powered competency mapping, using a person’s actual work order history and experience to better understand skills and identify development gaps.

This was a really practical conversation about where AI can genuinely support maintenance teams, rather than just adding more technology for the sake of it.

If you are interested in AI in maintenance, CMMS adoption, preventive maintenance and digital transformation that actually works, give this episode a listen.

What is the first maintenance workflow you would want AI to improve?

Support the show

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

Send us Fan Mail

Mentorship beats tools. Full stop.

I’ve been on the road with Maintain Reliability across food factories, metal plants and logistics sites, and the pattern is the same everywhere. Companies invest in systems before they invest in judgement. They gather more data before they build the confidence to act on what they already know. Then they wonder why the breakdowns keep coming.

The issue is rarely a lack of information. It’s a lack of guided decision making.

Training gives knowledge. Mentoring builds judgement. There’s a big difference. In a classroom everything makes sense. On a live plant with production breathing down your neck and budgets under pressure, it’s a different game. That’s where experience matters. Someone standing next to the engineer saying, focus here, not there. Fix this first. Leave that for now. Sequence it properly.

Order is everything in reliability.

Before we talk about monitoring strategies, we ask simple questions. Is planning and scheduling tight. Are critical assets clearly defined. Is lubrication consistent. Are work orders closed properly. Do people understand their roles. If those foundations are weak, adding more layers just increases confusion and backlog.

When the basics are strong, performance compounds.

A proper reliability audit is usually the turning point. Not a tick box exercise. A real look at how the plant operates. It exposes gaps in communication, spares, lubrication standards, ownership and accountability. More importantly, it gives leadership clarity. It turns reliability from a cost into a structured improvement plan.

Technology has its place. We use condition monitoring every day. But the team must own the data. They must understand what a trend means, what the risk is, and what action follows. Without that, nothing changes.

I’ve seen engineers with almost no budget transform a site because they closed the loop fast and acted decisively. I’ve also seen sites with serious investment still stuck reactive because culture didn’t support action.

Reliability works when people take ownership. When KPIs drive behaviour. When leaders back decisions. And when mentors hold the rope when pressure hits.

If you want results that last, start with an honest audit. Build a roadmap you can defend. Strengthen the people. Then layer in the systems.

That’s how we do it at Maintain Reliability.

Support the show