Introduction to IBM Maximo Health: Your Assets Are Lying to You
Who this is for: Maintenance managers, reliability engineers, and asset management leaders who suspect their PM programs are not targeting the right assets -- and want a data-driven way to prove it.
Estimated read time: 15 minutes
🔥 The $3.2 Million Wake-Up Call
A petrochemical facility in the Gulf Coast ran a textbook preventive maintenance program. Every pump, every compressor, every heat exchanger -- all on a fixed 90-day PM cycle. The compliance rate was 94%. The maintenance manager's dashboard was green. The VP of operations was satisfied.
Then Pump P-4407 failed catastrophically on a Tuesday afternoon. Seal failure led to a process fluid release. Emergency shutdown. Environmental response. Two weeks of lost production. Total cost: $3.2 million.
Here is the part that keeps you up at night: P-4407 had passed its most recent PM inspection 11 days earlier. Rating: "Satisfactory."
But if anyone had looked at the data -- really looked at it -- the story was obvious:
- 17 corrective work orders in the previous 18 months
- Vibration readings trending upward for 6 months
- Bearing temperature 22% above baseline
- Three consecutive inspections where technicians noted "minor seal weep" in the comments field
The data was screaming. Nobody was listening. Because the PM schedule said the pump was fine, and the PM schedule is what drove every decision.
"We do preventive maintenance on everything. That is our strategy."
No. That is not a strategy. That is a policy that treats a mission-critical process pump and a break room ceiling fan with the same level of urgency. And it is exactly the problem IBM Maximo Health was built to solve.
🚫 The Problem with How You Prioritize Today
Let's be honest about what most maintenance organizations actually do. Not what the asset management policy document says. What actually happens on the floor.
The Calendar Trap
You maintain assets on a fixed schedule because someone decided -- probably years ago -- that 90 days or 6 months or 10,000 hours was the right interval. That number might have been based on OEM recommendations, a reliability study, or (more often than anyone admits) a guess that nobody questioned.
The result:
THE CALENDAR TRAP
Assets that need attention NOW Assets getting PM they don't need
┌─────────────────────────────┐ ┌────────────────────────────────┐
│ Critical pump with rising │ │ Backup air handler that runs │
│ vibration and 17 CMs in │ │ 200 hours/year, last failure │
│ 18 months │ │ was 2019 │
│ │ │ │
│ STATUS: "Next PM in 47 days"│ │ STATUS: "PM completed on time" │
│ RISK: Nobody knows │ │ RISK: Nobody asked │
└─────────────────────────────┘ └────────────────────────────────┘
Same priority. Same schedule. Same treatment.
Different consequences.The Spreadsheet of Doom
When capital budget season arrives, someone builds a spreadsheet. It has columns for "Asset Age," "Replacement Cost," and "Condition" -- where condition is a subjective rating assigned by whoever happened to fill in the form. The spreadsheet gets emailed around. People add comments. Someone changes a formula. Three versions exist by Friday.
The $8 million capital request that goes to the board is based on this spreadsheet. And the board approves it because what else are they going to look at?
The Tribal Knowledge Problem
Your best maintenance planner knows which assets are trouble. She has been there 23 years. She knows that Compressor C-201 sounds different when it is about to throw a bearing. She knows that the HVAC in Building 7 always fails in August.
She is also retiring in 14 months.
When she leaves, that knowledge leaves with her. And the PM schedule will keep running on its 90-day cycle as if nothing changed.
🧠 What Maximo Health Actually Does
IBM Maximo Health is not another dashboard. It is not a reporting tool. It is a risk translation layer that sits between your data and your decisions.
Here is what it does in plain language:
- Consumes data you already have -- work orders, failure codes, meter readings, inspections, and optionally IoT telemetry and predictive outputs
- Calculates a composite health score for each asset based on configurable indicators and weightings
- Combines health with criticality to produce risk indicators
- Surfaces the results in portfolio views, ranked lists, and drill-down dashboards
- Connects to work management so health insights drive actual maintenance and capital decisions
That is it. No magic. No black box. Just a structured, transparent way to answer the question every maintenance organization asks every day: "Which assets should I worry about first?"
The Architecture in 30 Seconds
YOUR DATA MAXIMO HEALTH YOUR DECISIONS
┌──────────────────┐ ┌────────────────────┐ ┌───────────────────┐
│ Maximo Manage │ │ │ │ │
│ - Work orders │────────>│ Health Scoring │ │ Work orders │
│ - Failure codes │ │ - Indicators │ │ PM adjustments │
│ - Inspections │ │ - Components │──────>│ Capital plans │
│ - Meters │ │ - Weightings │ │ Risk reviews │
├──────────────────┤ │ │ │ Budget requests │
│ Maximo Monitor │────────>│ Criticality │ │ │
│ - IoT telemetry │ │ - Business impact │ └───────────────────┘
│ - Anomalies │ │ - Safety/prod/reg │
├──────────────────┤ │ │
│ Maximo Predict │────────>│ Risk = H x C │
│ - Failure prob │ │ - Prioritization │
│ - RUL estimates │ │ - Portfolio views │
└──────────────────┘ └────────────────────┘Key insight: Maximo Health does not replace Maximo Manage. It makes Maximo Manage smarter by adding a scoring and prioritization layer on top of the data you already collect.
📊 The Core Concepts You Need
Before we go deeper in later parts, you need four concepts locked in.
Concept 1: Health Score
The health score is a composite number -- typically 0 to 100 -- that represents the overall condition of an asset. It aggregates multiple factors:
- Condition -- what inspections and measurements say about physical state
- Reliability -- how often the asset fails and how frequently it needs emergency repair
- Performance -- how well the asset meets its throughput, efficiency, or quality targets
- Environment -- how harsh operating conditions and duty cycles affect wear
A pump with a health score of 35 is in materially worse shape than one scoring 78. That comparison is the entire point.
Concept 2: Criticality
Criticality answers: "What happens if this asset fails?" It captures business impact across dimensions:
- Safety and environment -- potential for injury or environmental damage
- Production -- lost output, service disruption, customer impact
- Regulatory -- non-compliance risk, penalties, audit exposure
- Financial -- direct repair cost plus indirect losses
A backup office HVAC unit and a primary process pump might both score 45 on health. But their criticality scores are wildly different. And that difference is what drives the next concept.
Concept 3: Risk
Risk is the combination of health (likelihood of failure) and criticality (consequence of failure). This is the number that matters most:
Health — Criticality — Risk — Action
Poor (25) — Very High — CRITICAL — Immediate intervention
Poor (25) — Low — Elevated — Planned replacement
Good (80) — Very High — Monitor — Watch closely
Good (80) — Low — Minimal — Continue routine maintenance
A poor-health, high-criticality asset jumps to the top of every list. A poor-health, low-criticality asset gets scheduled, not panicked about. That discrimination is what calendar-based PM cannot do.
Concept 4: Portfolio View
You do not manage one asset at a time. You manage thousands. Portfolio views aggregate health and risk across sites, systems, and asset classes so you can answer questions like:
- How many high-risk assets do we have at Plant A vs. Plant B?
- What percentage of our rotating equipment is in "Poor" or "Critical" health?
- Is our overall risk exposure getting better or worse quarter over quarter?
These views turn individual health scores into organizational intelligence.
🔍 Why This Matters More Than You Think
The Over-Maintenance Problem
Industry research consistently shows that 30-40% of preventive maintenance adds no value. You are spending labor hours, spare parts, and downtime windows on assets that do not need the work.
"But if we skip a PM and something fails, we are liable."
Nobody is telling you to skip maintenance. We are telling you to direct it differently. An asset with a health score of 92 and low criticality does not need a PM every 90 days. An asset with a health score of 38 and high criticality might need one every 30 days -- or an immediate overhaul.
Health-based maintenance is not less maintenance. It is smarter maintenance.
The Under-Maintenance Problem
The flip side is worse. Your most critical assets -- the ones where failure means safety incidents, environmental releases, or production shutdowns -- are getting the same PM frequency as everything else. Some of them are deteriorating right now, and the only evidence is buried in work order comments, meter trends, and inspection notes that nobody is correlating.
Maximo Health correlates it for you. Automatically. Continuously.
The Capital Planning Problem
Every year, you request capital for asset replacements. Every year, the board asks: "Why this asset? Why now? Why this much?" And every year, the answer is some combination of age, gut feeling, and "it has been on the list for three years."
Maximo Health gives you data-backed answers. "This transformer has a health score of 22 out of 100, criticality is rated Very High due to grid reliability impact, and the risk trend has been deteriorating for 18 months. Replacement cost is $1.2M. Failure cost is $8M." That is a capital request that gets approved.
🏭 Where Maximo Health Fits: Industry Snapshots
Manufacturing
- Prioritize maintenance on bottleneck production equipment using health and risk rankings
- Identify assets driving quality or scrap issues through reliability indicators
- Plan shutdown maintenance based on health trends, not just calendar cycles
Utilities and Energy
- Assess transformer and substation health using loading, oil tests, and condition assessments
- Focus capital investment on aging infrastructure with the highest safety and reliability risk
- Support regulatory reporting with standardized, auditable health and risk metrics
Oil, Gas, and Chemicals
- Evaluate rotating equipment, pipelines, and process units using inspection and reliability data
- Prioritize inspection campaigns in high-consequence environments
- Support integrity management programs with transparent scoring models
Transportation and Fleet
- Monitor fleets for safety and reliability using health scores tied to usage and failure data
- Drive maintenance scheduling and replacement strategies with risk-based rankings
- Align decisions with service reliability and safety targets
Facilities and Infrastructure
- Assess building systems like HVAC, elevators, and life safety equipment
- Prioritize upgrades based on health, usage, and occupancy criticality
- Support portfolio-level planning for campuses and distributed facilities
🛠️ Getting Ready: What You Need Before You Start
You do not need a perfect Maximo environment to start with Health. You need a realistic one.
Technical Readiness
- A supported MAS environment with Maximo Manage as the system of record
- Appropriate Health entitlements or licenses
- Administrative access for configuration
- Network connectivity for users who will consume dashboards
Data Readiness
- Asset master data -- classifications, locations, and hierarchy relationships populated
- Work history -- failure codes, downtime fields, and completion details used consistently
- Meters -- runtime, throughput, or other key meters configured and updated
- Inspections -- structured condition ratings (not just free-text notes)
Key insight: You do not need all of this in perfect shape. But you need to know where the gaps are so you can interpret early health scores honestly.
Organizational Readiness
- Clear objectives -- what does success look like in 6 months?
- Agreement on pilot scope -- which site, which system, which asset class?
- Stakeholder buy-in from maintenance, operations, reliability, and finance
Start with 50 assets on one production line. Prove the model. Expand from there.
🔮 What Comes Next in This Series
This introduction gave you the "what" and the "why." The rest of the series gives you the "how."
- Part 2 dives into the data model and scoring mechanics
- Part 3 walks you through activation and initial configuration
- Part 4 covers health score and criticality configuration in detail
- Part 5 connects Health to Monitor and Predict
- Part 6 builds your dashboards and KPI framework
- Part 7 shows how health scores drive work and capital decisions
- Part 8 covers governance, rollout, and the patterns that separate programs that last from programs that die
🎯 The 7 Commandments of Asset Health
- Thou shalt not treat all assets equally. A bottleneck compressor and a break room fan are not peers.
- Thou shalt define criticality before health. Consequence matters more than condition.
- Thou shalt start small. Fifty assets, one site, one asset class. Prove it.
- Thou shalt not worship the score. A health score of 72 means nothing without context. It means everything with criticality.
- Thou shalt close the loop. Health scores that do not create work orders are trivia.
- Thou shalt govern thy models. Ungoverned models degrade in 18 months. Guaranteed.
- Thou shalt question thy data. The model is only as honest as the failure codes behind it.
Next in the series: Part 2 -- Data Model and Health Scoring takes you under the hood to understand how Maximo Health turns raw data into the scores that drive your decisions.
About TheMaximoGuys: We help Maximo developers and teams build, configure, and optimize IBM Maximo Application Suite. Our content comes from real implementations, not marketing slides. If it is in our blog, we have done it in production.



