Reliability Strategies in Maximo Manage 9: FMEA, RCM, and a 58,000-Failure-Mode Library

Part 4 of the MAS MANAGE series. This is the capability that moves Manage from recording what broke to deciding what to maintain and why.

<aside>
🎯 Who this is for: Reliability engineers, maintenance strategists, and Maximo administrators who want to stop reacting to failures and start engineering them out — and who need to know exactly what Reliability Strategies delivers in Manage 9.
</aside>

Estimated read time: 24 minutes

🔥 From Firefighting to Strategy

Here is the uncomfortable truth about a lot of maintenance programs: the PM schedule was inherited, not engineered. Someone, years ago, decided to grease that bearing every month and inspect that valve every quarter — and nobody has revisited whether those intervals match how the asset actually fails. You are maintaining on tradition, not evidence.

Reliability Strategies is the Manage capability built to end that. It is not FMEA with a fresh coat of paint. It is the machinery that connects how an asset fails to what you do about it — and then writes that decision into the job plans and PMs your team actually executes.

The shift is from this:

Old world: "We've always greased it monthly. Don't touch the schedule."

to this:

MAS world: "This bearing has three dominant failure modes. Two are best caught by vibration monitoring; one justifies a time-based PM. Here's the RPN that ranks them, and here's the job plan each one drives."

<aside>
💡 Key insight: Reliability Strategies' job is to make your maintenance program defensible — every task traceable to a failure mode and its risk, not to habit.
</aside>

🧬 How FMEA and RCM Actually Connect to Work

Two disciplines sit at the core: FMEA and RCM. They are widely taught, but Reliability Strategies makes them operational by wiring them into Maximo's work objects.

FMEA — Failure Mode and Effects Analysis

FMEA decomposes an asset into a structured hierarchy:

   Function  ──▶  Functional Failure  ──▶  Failure Mode  ──▶  Effect / Cause
   "pump      "fails to maintain      "seal degradation"   "loss of
    coolant"   flow"                                         containment"

Each failure mode is scored for severity, occurrence, and detectability, which combine into a Risk Priority Number (RPN). The RPN ranks the failure modes so mitigation effort lands where the risk is greatest — not where the loudest stakeholder points.

RCM — Reliability Centered Maintenance

RCM is the decision logic layered on top: for each significant failure mode, what is the right response? The choices are essentially:

  • Preventive (time-based) maintenance — when failures are age-related and a scheduled task prevents them.
  • Condition-based monitoring / inspection — when a measurable signal (vibration, temperature, wear) gives warning before failure.
  • Run-to-failure — when the consequence is tolerable and prevention is not worth the cost.

Wiring it into Maximo

This is the part that makes it more than a spreadsheet exercise. The recommended actions from FMEA and RCM — PM tasks, inspection routines, design changes, operational controls — are mapped to job plans and PMs (Part 3). Failure modes connect to the Failure Codes application (failure class → problem → cause → remedy), so the codes your technicians report against align with the failure modes your strategy anticipated. The result is a closed loop: you plan against the failure modes you expect, technicians report against the same taxonomy, and the feedback tells you whether your strategy was right.

┌──────────────────────────────────────────────────────────────┐
│   THE RELIABILITY LOOP                                        │
├──────────────────────────────────────────────────────────────┤
│                                                              │
│   FMEA / RCM  ──▶  Strategy (PM / CBM / RTF)                  │
│       ▲                    │                                 │
│       │                    ▼                                 │
│   Failure Codes  ◀──  Job Plans + PMs  ──▶  Work Orders      │
│   (what actually          (the plan)         (the work)      │
│    happened)                                                 │
│       ▲                                          │            │
│       └───────────  feedback closes loop  ───────┘            │
│                                                              │
└──────────────────────────────────────────────────────────────┘

<aside>
💡 Key insight: Reliability Strategies is valuable precisely because it does not stop at analysis. Its output is job plans, PMs, and failure codes — the same objects from Part 3 — so the strategy lives inside the work, not in a binder.
</aside>

📚 The Library Is the Headline

Here is the feature that genuinely changes the economics. Building FMEAs from a blank page is brutal, slow work — it is the reason most organizations never finish them. Reliability Strategies ships with a curated, pre-built reliability library so you apply expert analysis rather than author it from scratch.

The scale, per community reporting, is striking:

Library dimension — Approximate scale

Asset types covered — ~800

Failure modes — ~58,000

Suggested PM activities — 5,000+ (with step-by-step tasks)

This is a body of asset-specific failure details and mitigation activities assembled by industry experts. Instead of a reliability engineer spending months documenting how a centrifugal pump fails, you start from the library's analysis for that asset type and tailor it to your context. It compresses what used to be a multi-year program into something you can stand up and iterate on.

<aside>
⚠️ Watch out: The library is a starting point, not gospel. Apply it, then tune it to your operating context — duty cycle, environment, criticality. The figures above (≈800 asset types, ≈58,000 failure modes, 5,000+ PMs) come from community reporting; treat them as the scale of the offering, and confirm specifics for your release against IBM documentation.
</aside>

🛠️ Working With Reliability Strategies in Manage 9

Manage 9.0 made the application genuinely workable, and 9.1 added intelligence. Here is what each delivered.

Manage 9.0 — the working application

  • Study Overview — a consolidated view of a reliability study.
  • Import, apply, create, and edit FMEAs — pull from the library, apply to your assets, or author your own.
  • Bulk import of failure-mode details — get a large analysis in quickly rather than record by record.
  • Apply actions based on Risk Priority Number (RPN) — let risk drive which mitigations become scheduled work.
  • Select, assign, and track Action status — manage the recommended actions through to completion, not just to recommendation.
  • Custom strategies — define your own strategies beyond the delivered library.

Manage 9.1 — the AI assist

Manage 9.1 added AI to the workflow:

  • Suggesting boundary conditions — AI proposes the operating boundaries for the analysis.
  • Generating components and failure mechanisms — AI helps populate the structure of an FMEA, accelerating the slowest part of the authoring process.

This is targeted, practical AI: it attacks the exact step — building out components and failure mechanisms — that makes FMEAs so labor-intensive. (For the broader picture of AI inside Manage, see Part 10.)

Manage 9.2 — platform reach

On the platform side, IBM Maximo Reliability Strategies gained IBM Power (ppc64le) architecture support in the 9.2 stream — relevant if you run MAS on Power hardware.

🔁 Closing the Loop With the Rest of Manage

Reliability Strategies only pays off because it connects outward:

  • Inspections (Part 5) capture the quantitative and qualitative condition data — bearing temperatures, vibration amplitudes — that validate or revise your failure-mode assumptions and feed condition-based strategies.
  • Meters and condition monitoring (Part 8) provide the signals that condition-based strategies act on, triggering conditional PMs when thresholds are crossed.
  • Work management (Part 3) executes the job plans and PMs your strategy produced and records the failure codes that feed back into it.
  • The AI suites (Health, Predict — their own series) consume this same reliability and failure data when deployed, but the strategy itself lives in Manage.

The feedback loop is the discipline: when a failure mode recurs despite mitigation, tighten the strategy; when an anticipated failure never materializes, consider extending the interval. Reliability Strategies gives you the structure to make those adjustments evidence-based.

🎯 The Commandments of Reliability Strategies

  1. Thou shalt trace every task to a failure mode — no maintenance by tradition.
  2. Thou shalt let RPN set priority — mitigate the highest risk first.
  3. Thou shalt start from the library, then tune to your operating context.
  4. Thou shalt choose the right response — PM, condition-based, or run-to-failure — per failure mode.
  5. Thou shalt close the loop with failure codes and inspection data.
  6. Thou shalt use the 9.1 AI to accelerate the slow part — building out FMEAs.

Key Takeaways

  • Reliability Strategies turns FMEA and RCM analysis into job plans and PMs — the strategy lives inside the work objects, not a document.
  • FMEA scores failure modes into Risk Priority Numbers (RPN); RCM decides the right response (PM, condition-based, or run-to-failure).
  • The built-in library spans roughly 800 asset types and 58,000 failure modes with 5,000+ PM activities, so you apply expert analysis rather than author it from scratch (figures per community reporting).
  • Manage 9.0 delivered the working application — study overview, import/apply/create/edit FMEAs, bulk import, RPN-driven actions, action tracking, and custom strategies.
  • Manage 9.1 added AI for suggesting boundary conditions and generating components and failure mechanisms; 9.2 added IBM Power architecture support.
  • The capability closes the reliability loop with failure codes, inspections, meters, and conditional maintenance.

References

IBM Official

Community

Series Navigation

Previous: — Part 3 — Work Management Reimagined

Next: — Part 5 — Inspections and Digital Forms

Published by TheMaximoGuys | June 2026

About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS — from architecture and migration planning to the day-to-day work of configuring, extending, and running Maximo Manage. This series is the guide we wish we'd had.