Asset management planning and the system behind it
Asset spending is usually decided a year at a time, in a budget round, with no document that says what the money buys. Why asset management plans matter, and how objectives, levels of service and criticality turn into a costed plan that holds.
what the money buys, in service and in risk
renewals visible beyond the next budget
the funding gap stated rather than absorbed
The challenge
Asset spending is commonly decided a year at a time. Operating budgets are set by last year's number, renewals surface as capital requests when something fails, and the document that should connect them either does not exist or was written for an audit and has not been opened since.
The cost of that is invisible until a decision has to be defended. Nobody can say what a budget cut removes, in service or in risk, and nobody can show why a renewal is due now rather than in three years. Boards, regulators, insurers and joint venture partners increasingly ask for that reasoning in writing, and the answer has to come from a plan rather than from the memory of whoever has been there longest.
When it's time to act
The signs we commonly see when this initiative is due.
- Renewal decisions arrive as emergency capital requests after a failure.
- The asset management plan was written for an audit and nobody has opened it since.
- No agreed levels of service, so every budget conversation is about cost alone.
- Renewal forecasts built from install dates and default lives, with no condition data behind them.
- Two teams quoting different asset counts for the same plant.
How we deliver it
Understand
Work through the decisions being made, and the ones being deferred, with the people accountable for them.
Assess
Benchmark the current system and data against your own standards and recognised practice, so gaps are evidenced rather than asserted.
Levels of service
Agree what the assets must deliver, with measures, targets and the cost of each option.
Plan and cost
Lifecycle activities by asset class, built into a year by year forecast that separates operating from capital.
Govern
A named owner, an update tied to the budget cycle, and measures reported with everything else.
Understand
Work through the decisions being made, and the ones being deferred, with the people accountable for them.
Assess
Benchmark the current system and data against your own standards and recognised practice, so gaps are evidenced rather than asserted.
Levels of service
Agree what the assets must deliver, with measures, targets and the cost of each option.
Plan and cost
Lifecycle activities by asset class, built into a year by year forecast that separates operating from capital.
Govern
A named owner, an update tied to the budget cycle, and measures reported with everything else.
Our approach
- Understand where asset decisions are actually made, and where they are being deferred, with the operations, maintenance and finance people who live with the consequences.
- Assess the current asset management system, plans and data against your own framework and, where it adds value, published practice such as ISO 55001 and the ISO 55000 series.
- Set levels of service with the people accountable for delivering them, measured in terms the operation recognises, then cost at least two options so the trade-off is a decision rather than a debate.
- Rank criticality so analysis and spending stay proportionate to consequence, and reuse the ranking that already exists where it holds up.
- Build lifecycle activities by asset class, drawing maintenance strategy from FMECA or templates by band, and renewal timing from condition rather than a default life.
- Cost the plan year by year, separating operating from capital, and state the funding gap with its consequence in service and risk rather than trimming the plan to fit.
- Hand over a plan with a named owner, a review cycle tied to the budget round, and an improvement plan that says what must get better before the next version.
Tools and methods
The value it creates
- Asset spending gets argued in terms of service and risk rather than last year's budget, because the plan says what the money buys.
- Renewals become visible years ahead instead of arriving as emergency capital after a failure.
- The funding gap is stated with its consequence, which turns a quiet trimming exercise into a decision the organisation makes deliberately.
What changes
Spending set by last year's budget
Spending set by service, risk and whole of life cost
Renewals surfacing as emergencies
A renewal profile visible years ahead
A plan written for an audit
A plan that changes the budget and the work program
The funding gap quietly absorbed
The gap stated, with its consequence in service and risk
Where these initiatives fail
The failure modes we design against.
- Writing the plan in language nobody in operations uses, which guarantees it is never referred to again.
- Skipping levels of service, which leaves cost with nothing to be traded against.
- Scoping every asset at component level, so the plan describes everything and finishes nothing.
- Building renewal forecasts on an asset register that has never been verified against the field.
- Treating certification as the goal rather than the system it is meant to evidence.
Common questions
Is this an ISO 55001 certification project?
Only if you want it to be. ISO 55001 is a useful structure for the asset management system and the plans that sit inside it, and certification matters where a customer, regulator or insurer asks for it. The value comes from the system and the plans, and most operations get that without certifying.
How is this different from a maintenance strategy?
A maintenance strategy decides which failure modes are managed and by what kind of task. An asset management plan sits above it and covers the whole life of the assets, including renewal, upgrade and disposal, with the money and the level of service attached. The strategy is an input to the plan.
What if our asset data is not good enough?
That is the usual starting point, and it is why the plan states the confidence behind each input. Critical systems get verified against the field first, the forecast is built where the data supports it, and the improvement plan says what has to get better before the next version can be trusted further.
Key terms
Plain-language definitions from our glossary for the concepts this page leans on.
Standards and further reading
Reference points we draw on where they suit the work. We also work to client internal standards and established site practice.
- ISO 55001:2024 Asset management system requirements (ISO)
- ISO 55000:2024 Asset management, vocabulary, overview and principles (ISO)
- ISO 55002:2018 Guidelines for the application of ISO 55001 (ISO)
- ISO 15663:2021 Life cycle costing for petroleum and gas industries (ISO)
- The Asset Management Landscape, third edition (GFMAM)
- Asset Management Council, Australian asset management community (Asset Management Council)
- Best practices, metrics and guidelines for maintenance and reliability (SMRP)
Further reading
Articles and calculators on the methods behind this work.
Related projects
Facing a similar challenge?
Tell us what you are working through and we will bring the right mix of engineering, data and hands-on experience.
Contact us