Most asset-intensive operators have a criticality score somewhere. It might be in a spreadsheet, in a custom Manage field, or in the head of a senior engineer who is two years away from retirement. IBM Maximo Health makes that score a first-class object: scored against criticality, condition and consequence, kept current as the underlying data changes, and defensible at a budget review or an audit.
This guide is for the operations or asset-management leader who has been asked whether Health is worth doing. It sets out when it pays back, how it relates to ISO 55001, and how to scope a first programme that produces decisions, not slides.
What Health actually does
IBM Maximo Health scores assets across the estate against criticality, condition and consequence. It uses what is already in Maximo Manage — hierarchy, classification, work history, condition fields — and the operational signal that Monitor provides where available. The output is a prioritised view of the estate that the maintenance plan, the capital plan and the audit evidence trail can all defend.
The crucial difference from a static criticality score in a spreadsheet is that Health is dynamic. It updates as condition data, work history and operational signal change. Yesterday’s pump that was healthy is today’s pump that is not.
When Health earns its licence
Health pays off when two conditions are true.
The asset register in Manage is reasonably complete and structured. Consistent hierarchy, criticality fields populated, classification meaningful. Health does not require perfection — it requires enough discipline that the score reflects reality. Where Manage data is still being cleaned up, that work is the prerequisite, not the project.
There is a real decision waiting for the answer. A capital plan being built. A maintenance budget being challenged. An audit being prepared. An asset class going off-warranty. Without a decision waiting on it, Health produces an interesting score and not much action. With a decision waiting on it, Health is one of the few MAS-suite components that pays back on day one.
How Health relates to existing criticality work
A reasonable challenge from any senior engineer is “we already have criticality”. Health is not a replacement for that work — it is an upgrade.
A static criticality score is a snapshot. It is set during a workshop, occasionally refreshed, and used to defend the maintenance plan. It is durable, but it ages. Health takes the same input and combines it with condition data and operational signal. The criticality decision is still yours; Health makes the score consequential.
Where there is no formal criticality work today, that is the place to start. A scoring framework — failure consequence, safety, environmental, regulatory, operational — should exist before Health automates it. Our position is set out in asset criticality assessment frameworks.
How Health relates to ISO 55001
ISO 55001 auditors do not ask whether you have an asset health platform. They ask whether the basis for maintenance and capital decisions can be explained, reproduced and defended. Health is one of the more direct routes to that evidence: a score that can be derived, audited, recalibrated and trusted.
Health is not a substitute for the wider operating model work — risk appetite, decision rights, resource allocation, performance review — but it is a defensible piece of the audit trail. The broader picture is in ISO 55001 asset management system: what it really means.
Scoping a credible first programme
A credible first Health programme has five elements.
- Readiness assessment against the Manage asset register, criticality data and the decision the score has to support. If there is no decision waiting on it, defer the programme.
- Scoring model design — criticality, condition, consequence — calibrated to the operating reality of the estate, not generic templates. The senior engineer who would otherwise be the human criticality model has to be in this room.
- Health configuration on top of Manage, and on top of Monitor where condition signal is live.
- Capital and maintenance integration so the score drives plan revisions, not a separate dashboard. If the planners do not trust it, the score does not exist.
- ISO 55001-aligned evidence trail so the basis for decisions is documented, repeatable and reviewable.
Questions to ask a supplier
- “Walk me through how you would assess our criticality data before scoping a Health programme.”
- “Which decision should the first score support, and what does pay-back look like in the first year?”
- “How is the scoring model calibrated to our estate, rather than to a generic template?”
- “How does the score get into the maintenance plan? Who reviews it, on what cadence?”
- “How do you keep the model honest as the underlying data and the operating reality change?”
- “If we are going for ISO 55001, what evidence does Health give us, and what do we still have to do separately?”
Sequencing inside the wider suite
Health sits naturally between Monitor and Predict on the same asset class. Monitor brings the condition signal; Health uses it; Predict learns from it. Health is also one of the better candidates to start the wider-suite conversation when the executive question is “what is the state of our estate, and how should the capital plan be ordered”. For where it fits in the bigger picture, see the MAS suite overview. For the implementation pattern in detail, see IBM Maximo Health: asset health scoring and capital prioritisation.
Closing position
IBM Maximo Health is the MAS-suite component most likely to pay back on day one for asset-intensive operators with a real capital or maintenance decision in front of them. It rewards discipline in Manage. It rewards explicit criticality work. And it gives the asset-management leader something to defend the plan with that survives a change of senior engineer.
Talk to the people who would actually deliver it
No pitch deck, no pressure. A direct conversation with one of our senior consultants.