What Preventive Maintenance Is Missing: Reasons Why & the Shifting Landscape | Blog No. 130

I spent 90 minutes at a RETA meeting last week that was almost entirely dedicated to one thing: spray nozzles on evaporative condensers.

Cleaning them. Inspecting them. Understanding what happens when you don't.

It sounds like a narrow topic. But the longer the conversation went, the more it opened up performance degradation, energy costs, refrigerant pressure creep, and underneath all of it, safety. One small neglected component, compounding quietly over time.

That's what a great preventative maintenance culture looks like in practice. Not a binder. Not a checklist. A room full of people who care deeply about a spray nozzle, because they know what it connects to.

PM is wildly important. Everyone in this industry knows that. It's also wildly difficult to master and even harder to scale across multiple facilities, multiple covered processes, and a team that didn't all come up through the same culture.

But here's the problem nobody talks about enough: the compliance program and the preventative maintenance program are living in separate universes. They don't communicate. They don't reinforce each other. And the gap between them is costing facilities time, money, and in some cases, a lot more than that.

Why the Gap Exists

This isn't a people problem. It's a structural one. Three things keep maintenance and compliance from working together the way they should.

Each program has its own language, its own logic, and its own demands.

Preventive maintenance is driven by equipment. Asset lists, work orders, labor hours, parts availability. The job is to keep the system running. The metrics are uptime, mean time between failures, and cost per repair.

Compliance is driven by regulation. Program elements, audit cycles, recommendation status, and code references. The job is to demonstrate that the facility is operating within the bounds of OSHA PSM, EPA RMP, and CalARP. The metrics are on-time completion rates, open findings, and what an inspector would see if they walked in tomorrow.

Both programs are doing important work. But they're optimized for different questions, managed by different people, and tracked in different systems. The maintenance manager and the PSM coordinator often operate in parallel, not in partnership.

Most software only solves for one side.

A CMMS is built for maintenance. Work orders, PM scheduling, asset history, parts inventory. It does that well. But it doesn't know what IIAR-6 requires for your evaporative condensers. It doesn't know which of those completed work orders generated a PSM-relevant finding. It doesn't tie equipment condition to your process safety information.

Compliance software, on the other hand, knows the regulatory framework. It can build your audit calendar, track recommendations, and generate a report your auditor can actually read. But it doesn't speak to your CMMS. It doesn't know what your maintenance team completed last Thursday or whether that work order closure actually resolved the underlying hazard.

The result is duplication at best, and dangerous blind spots at worst.

Compliance hasn't been integrated into maintenance in a way that a maintenance manager can actually use.

Ask a maintenance manager to take on PSM responsibilities, and the most common reaction isn't resistance; it's overwhelm. The regulatory framework is dense. The documentation requirements are extensive. The consequences of getting it wrong are significant. And the tools available to help are either built for compliance professionals or require a compliance professional to interpret.

That's not a failure of the maintenance manager. It's a failure of how compliance has been packaged and delivered. If the only people who can navigate your compliance program are the ones who already know it, your program has a scalability problem.

The Shifting Landscape

Something is changing. Slowly, then all at once, which is usually how it goes in this industry.

The compliance tools getting built today are different from the ones that came before. And the difference isn't just interface or user experience. It's that they're being designed by people who actually understand what IIAR-6, IIAR-7, and the PSM standard require at the equipment level and who are asking a different question than software developers have historically asked.

Not just: how do we store this information?

But: how do we make this information useful to the person doing the work?

Here's what that shift looks like in practice.

Build compliance software that understands the IIAR standards for maintenance, forwards, and backwards.

Not a generic checklist builder. Not a task management tool with a PSM skin on it. A platform that knows the difference between an IIAR-6 inspection requirement and a general PM, that can populate the right questions based on the equipment type, and that ties the completed work to the right program element automatically.

When a technician finishes an annual inspection on a shell-and-tube heat exchanger, the software should already know what that inspection is supposed to demonstrate, what a finding means in a compliance context, and where that record needs to live.

Make it navigable for anyone, not just the compliance team.

The goal isn't to turn every maintenance tech into a PSM expert. The goal is to lower the barrier enough that the person doing the work can answer basic questions without needing to call someone.

What am I supposed to do here? Is this in scope for a PSM activity? What happens if I find something? Who needs to know?

When the interface can answer those questions clearly, compliance becomes something the whole team participates in, not a separate program that runs alongside the real work.

Systematize the overlap. Build collaboration around the parts that matter.

There are parts of this that should be systematized completely. The scheduling. The routing. The notifications. The record-keeping. That's not where human judgment adds value, and it shouldn't require human effort to maintain.

But there are also parts where collaboration is the point. A recommendation that comes out of a compliance audit and a work order that comes out of a PM inspection might be describing the same problem in two different systems. The question of whether that problem is actually resolved and resolved in the way the regulation requires is a conversation. The software should be the infrastructure for that conversation, not a replacement for it.

When work gets done and changes get made, systems should share data and focus on answering the basic questions.

This is the north star.

Completed, yes or no. Compliance steps scheduled, yes or no. Completed, yes or no. What comes next? Where is the detailed information if I need it?

That's it. That's what most facilities are missing. Not all information, but most facilities have plenty of information. What they're missing is a system that surfaces the right information to the right person at the right moment, in a form they can actually use.

The Bottom Line

Compliance is getting smart enough to be systematized like PM. Slick enough to integrate into the maintenance workflow. And easy enough to navigate that the compliance load can finally be shared across the team rather than carried by one or two people who already know the whole program by heart.

The PSM software is built to be user-friendly, speak to any PM system intelligently, and act like a PSM partner: organizing program details in the background, and enabling you to scale compliance and system health together is here and getting better every day, and is worth a conversation, no matter what your connection is to ammonia! Check out Samwise. 

Previous Blog: Balancing Safety and Efficiency in Ammonia Refrigeration | Blog No. 129

---

For a comprehensive training on Anhydrous Ammonia, click here for our PSM Academy Ammonia Awareness training, to learn and earn a certificate of completion. Training is in English and Spanish. Use code SDS20 for a 20% discount on the entire purchase. For more information, email us at academy@machapsm.com.For a comprehensive training on Anhydrous Ammonia, click here for our PSM Academy Ammonia Awareness training, to learn and earn a certificate of completion. Training is in English and Spanish. Use code SDS20 for a 20% discount on the entire purchase. For more information, email us at academy@machapsm.com.