Connecting Asset Condition, Criticality and Cost: A Management Framework
Ask three teams in the same organisation which assets matter most and you will often get three answers. Maintenance points to what is in poor condition. Operations points to what would hurt most if it stopped. Finance points to what consumes the budget.
All three are right, and none of them is sufficient. Condition, criticality and cost are only decision-useful together. An asset in poor condition that nothing depends on can wait. A critical asset in good condition needs monitoring, not investment. The assets that deserve money this year sit where all three signals converge — and finding them requires the three datasets to meet.
They usually don’t. Condition lives in inspection reports or a CMMS, criticality in a risk register or in someone’s head, cost in the finance system. Each is maintained by a different team on a different cycle.
What each dimension actually tells you
Condition answers: how much life is left? Its value depends on being comparable. A 1-to-5 score means little unless everyone scoring uses the same definitions, and unless the score maps to an expected remaining life rather than a general impression.
Criticality answers: what does failure cost beyond the repair? Service interruption, safety, regulatory exposure, reputational damage, knock-on failures. Criticality is a property of the asset’s role, not its condition, and it changes when the system around it changes — a redundant pump stops being low-criticality the day its twin is decommissioned.
Cost answers: what does each option consume? Not just the intervention price: the cost of doing nothing, the cost of doing it later, and the cost of doing it alongside other work.
The prioritisation logic
Joining the three produces a simple, defensible ordering:
- Poor condition, high criticality — act now. This is unmanaged risk, and it is where unplanned failures come from.
- Poor condition, low criticality — run to failure deliberately, and record that as the decision. This is a legitimate strategy, and stating it explicitly stops it being mistaken for neglect.
- Good condition, high criticality — monitor and protect. Spending here feels prudent but usually buys little; the asset was not going to fail.
- Good condition, low criticality — leave alone.
The useful surprise, for most organisations doing this for the first time, is how much planned spend sits in category 3 and how much unmanaged risk sits in category 1. Reallocating between them improves risk and cost simultaneously, which is rare.
Where the framework breaks in practice
Inconsistent condition scoring. If two inspectors would score the same asset differently, the ordering is noise. Fixing scoring definitions is unglamorous and high-return.
Criticality set once and never revisited. Ratings assigned during a commissioning project, five reorganisations ago, are a liability. Criticality needs a review trigger tied to changes in the system.
Cost without a time dimension. A cost figure with no view of what it becomes if deferred by three years cannot support a prioritisation decision — deferral is the main lever available.
No asset hierarchy. Without a consistent hierarchy, condition, criticality and cost are recorded against different objects and cannot be joined at all. This is the most common blocker, and it is a data-structure problem, not an analysis problem.
Moving from framework to plan
A framework orders assets. A plan says what gets done, when, within a budget — and that requires projecting each asset forward. Degradation modelling turns a condition score into an expected trajectory, so interventions can be scheduled before failure rather than after, and compared across years.
That is the step where the three datasets stop being reports and become an investment plan, aligned with ISO 55001 practice on evidencing decisions. Oxand Simeo™ is built around this join: a consistent hierarchy, condition-based degradation models per asset, criticality weighting, and cost scenarios compared on the same horizon — the mechanism behind the 30,000+ recommended actions generated with asset owners.
Where to start
Do not begin with a data-integration programme. Begin with one asset class, in one location, and build the joined view by hand for a few hundred assets. Two outputs follow quickly: a defensible priority list, and a precise specification of which data is missing and why it matters.
That specification is worth more than a generic data strategy, because it is grounded in a decision someone actually needs to make.
To discuss applying this to your portfolio, talk to an Oxand expert or read more on asset management practices and ISO 55001.