From Failure Modes to Work Orders: Exploring IBM Maximo Reliability Strategies

As we continue our exploration of the IBM Maximo Application Suite (MAS), our next application in focus is IBM Maximo Reliability Strategies - and I'll say it up front: this one is a game changer.

If you are new to MAS, new to CMMS altogether, or your PM plan is "whatever the OEM manual said in 2009", this is the application that gets you a real reliability-centered maintenance program.

Here is the problem it solves. Everyone agrees that Reliability Centered Maintenance (RCM) is the right way to decide what maintenance an asset actually needs. Very few organizations do it, because a proper Failure Modes and Effects Analysis (FMEA) means pulling your best people off the floor for a couple of weeks per asset type, and the result usually lands in a spreadsheet nobody opens after the consultant leaves.

Reliability Strategies puts the study, a library of ready-made answers, and the resulting PMs inside Maximo - right next to the assets they are supposed to protect.

What is Reliability Strategies?

Reliability Strategies is an add-on for Maximo Manage. You will find it under Assets, it uses the newer Graphite interface, and it costs no AppPoints to install or enable (the AI features are the one exception).

In plain English, it is an FMEA tool that talks to the rest of Maximo. For each type of equipment it records how it fails, what happens when it does, how risky that is, and which maintenance task prevents or catches it best. Then - and this is the part that matters - it turns those answers into Job Plans and PMs in Manage.

It arrived in MAS 8.11 as a read-only view of IBM's library, gained custom strategies in 9.0 and native Maximo records plus the first AI assist in 9.1. In 9.2 the strategy finally ends at a PM.

The Library: 25 Years of Homework, Already Done

The Reliability Strategies Library is IBM's content behind the application, built from 25 years of large-scale RCM studies with industry experts. As of MAS 9.2 it holds:

• 800+ equipment types with pre-built reliability strategies
• 58,000+ components and failure mechanisms, each tied to the operating conditions that drive it
• 5,000+ PM tasks with step-by-step instructions and recommended intervals

If you run centrifugal pumps, air compressors or switchgear, somebody has already done the FMEA. You start from it, pick the operating context that fits your equipment (critical or minor, high or low duty cycle, severe or mild service), and the recommended intervals change with it.

The library lives on IBM's servers, so an on-premises Maximo needs outbound internet access to reach it. Coverage is broad but not complete, so check your asset types first; for anything missing, the AI Strategy Builder drafts a first pass for you to validate.

Four Words You Need

• Failure mode = component + mechanism + influence: the tires, low pressure (think problem code), cold weather (think cause code).
• Action - one small task that prevents or detects it: check the tire pressure.
• Mitigation activity - a bundle of actions done together at a frequency. "Oil change" includes the oil, the tire rotation and the pressure check, every year or every 30,000 km. This is what becomes the Job Plan and the PM.
• RPN - risk priority number: how bad × how often × how hard to spot, scored before actions (RPNi) and after (RPNf). The gap is what your maintenance is buying you.

From Failure Mode to Work Order

The whole flow fits in five steps:

1. Start from the library - Pick the equipment type and configuration in the Strategy library, choose the operating context on its Mitigation activities tab to see the recommended intervals, then duplicate it as your own custom strategy.
2. Failure modes & risk - On the Failure modes tab, add your own, drop the ones that do not apply, and score each one for risk.
3. Actions & mitigation activities - Add the actions that prevent or detect each failure mode, then bundle them into mitigation activities with a frequency that matches your operating context. Condition-based, time- or meter-based, predictive, or a deliberate run-to-failure. Yes, "let it fail" is a valid strategy - as long as it is a decision and not a surprise.
4. Assets & locations - Assign the strategy on its Assets or Locations tab. The operating context belongs to the strategy, not the asset, so assets that run in different contexts need their own copy of the strategy.
5. Job Plans & PMs - Once the strategy is complete, open a mitigation activity and save it. Link an existing job plan or create one from it (the actions become the tasks), then use Apply mitigation activity to create a PM or Master PM. The PMs generate the work orders. Done.

Every PM traces back to a failure mode and a consequence. That is the difference between a maintenance strategy and a to-do list.

New in MAS 9.2

Until now, a strategy ended at a recommendation. In 9.2 it ends at a PM in Manage. The highlights:

• Job Plan & PM support - create or link Job Plans, PMs and Master PMs directly from mitigation activities. Strategies are written per equipment type, so Master PMs are the natural fit.

• Implementation Dashboard - a Strategy tab on the asset and location dashboard: how well each failure mode is protected, which mitigation activities are implemented, and which PMs are untracked, meaning their job plan is not linked to the strategy.
• Meters and locations - PMs can be time-based, meter-based or both, and strategies apply to locations as well as assets. Assets get swapped out; the pump position in the plant does not.
• Risk matrices - define your own scoring scales once, so an RPN of 60 means the same thing at every site.
• Enhanced AI Strategy Builder - suggests actions for a failure mode and drafts mitigation activity descriptions. It is opt-in and needs the Maximo AI Service, which consumes AppPoints.

Seamless Integration with Other MAS Applications

As with every application in the suite, the real value shows up when Reliability Strategies is connected to the rest of MAS.

Manage: Assets, locations, meters and failure codes flow in. Job Plans, PMs and Master PMs flow out. When a technician closes a work order with a failure code, that history is what you check the strategy against next time.

Health: Health's criticality and risk scores tell you which assets deserve a study first. Start at the top of the risk matrix, not at the top of the asset list.

Monitor: Many of the mitigation activities in the library are condition-monitoring tasks. Map a Monitor metric to a Manage meter and a meter-based PM runs off live data - the compressor runtime metric from my last post is really a "check for air leaks" task that runs itself.

Predict: For a high-consequence failure mode, Predict's failure probability models can predict the failure to execute a mitigation activity. The strategy says why you are watching an asset or a particular component; Predict does the watching.

And for the agentic AI crowd: a structured model of how your assets fail is exactly what an AI agent needs before it can recommend tightening a PM interval or raising a follow-up work order. More on that soon.

Where to Start

• Classify your assets first. The library is keyed by equipment type. If "PUMP-07" is the only thing Maximo knows about a pump, you will spend your time mapping instead of analyzing.
• Start with criticality, not coverage. Twenty good strategies on critical assets will change outcomes. Two hundred shallow ones will not.
• Link your existing job plans before you create new ones. Then open the asset's Strategy tab: the untracked PMs and unimplemented mitigation activities are your PM optimization backlog.
• Keep failure codes short. Technicians must pick a problem and cause code in seconds: five to eight options per level, not forty.

Final Thoughts

For years, the honest answer to "where is our RCM study?" was "in a binder somewhere." Now it lives in Maximo and generates the PMs itself. If you are on MAS 9.2, pick one critical asset type, copy its library strategy, assign a few assets and look at the gaps on their Strategy tab. They will make the business case for you.

With that I will sign off for now - stay tuned for more insights into the innovative features and functionalities of the Maximo Application Suite!