The most common failure mode of an IBM Maximo Health rollout is not technical. It is a failure of communication. A board sees a number on a slide, asks the obvious follow-up question, and discovers that the head of asset management cannot defend it. Within a quarter, the score is no longer a board artefact, and Health stops being the capex prioritisation tool it was bought as.
This is avoidable. The discipline is to be precise about what an APM criticality score is, what it is not, and to lead the conversation toward decisions rather than numbers.
What the score actually is
The asset criticality and risk score is a composite. The components are the four ideas that the wider asset performance management community has converged on, and they are worth being precise about.
Criticality is what the asset matters to. It is a property of the asset in the operating context, not a property of the asset on its own. The same pump in two plants can have very different criticality. Health gets this from the asset hierarchy, the safety case, the production picture and the operating context already held in Manage.
Condition is what the asset is doing now. It comes from inspection records, work history, condition monitoring and — where present — live signal from Monitor. Where the condition data is thin, the score reflects that. The honest version of the conversation says so.
Consequence is what happens if the asset fails. Safety, environmental, production, regulatory, financial. This is the conversation that turns a number into a decision and the one that operators most often skip.
Risk is the product of these. It is not the score on the screen; it is what the score is trying to express.
When we present a criticality picture to a board, we present these four explicitly. The score is a summary of these, not a black box.
The board questions we have learned to expect
A few questions tend to come up in the first board conversation, and they are worth rehearsing before the slide goes up.
“Why is this asset scored higher than that one?” The answer is not “the model says so.” The answer is which of criticality, condition or consequence is driving the score, and what the underlying evidence is. If the head of asset management cannot answer this in one sentence, the model is being used as a black box and the credibility leaks.
“What if the inspection data is wrong?” The honest answer is “the score moves.” Health is not a oracle. It is a way of organising the evidence the operator has, weighted against the operating context. Where the evidence is thin, the score is provisional. Saying so is not weakness; it is precision.
“Are we managing this risk, or are we just measuring it?” This is the question that decides whether Health is doing its job. The score has to connect to a maintenance decision, a capex line, an inspection regime change, or an asset replacement plan. If it does not, it is wallpaper.
“How does this connect to the regulator?” For regulated estates, this matters. The criticality picture has to live in a register the regulator can read, with an audit trail that connects the score to the underlying inspection and condition evidence. Health does this, but the operator has to design the connection deliberately.
What the score is not
A few common misreadings are worth heading off before they happen.
The score is not a probability of failure. It is a composite risk view. Probability of failure is what Predict does, on the asset classes where the data supports it.
The score is not a maintenance plan. It is the input to a maintenance plan. The plan itself is a separate artefact, owned by the reliability function, that takes the score and applies the maintenance strategy that fits the asset class.
The score is not a budget. The Asset Investment Optimization layer above Health turns the score into a financially-optimised plan against a budget and a risk appetite. Health on its own produces a prioritised list; the budget conversation is the next step.
The score is not stable. As condition data improves, as work history accumulates, as the operating context changes, the score moves. A board that expects a static number will be confused. A board that understands the score is meant to move will read it correctly.
Designing the board slide
The slide that works is rarely a heat map. Heat maps are visually compelling and operationally unhelpful. They invite the reader to focus on the colour rather than on the underlying decision.
The slide that works is closer to a prioritised list with three or four columns: the asset, the dominant driver of its risk score (criticality, condition or consequence), the proposed action, and the cost of that action. The board reads it as a decision queue, which is what it is. They can see what is being prioritised and why, and they can challenge the proposed action without having to argue with the model.
We tend to put the heat map in the appendix for the readers who like one. The decision queue goes on the front.
Closing position
An APM criticality score is a composite of criticality, condition and consequence, organised as a prioritised view of risk. It is most useful when it is presented as the input to a decision, not as the decision itself. The board conversation that goes well is the one where the head of asset management can name the driver of every score, name the action that follows from it, and name the cost of that action.
For the broader implementation pattern, see IBM Maximo Health — how we deliver it and the Health and asset criticality guide. For the case-specific framing of how Health connects into a capital plan, see costing a Maximo Health rollout against a capital plan.