The asset management plan, and the strategy it comes from
An asset management plan says what will be done to a group of assets, when, at what cost and to what level of service. What it contains, how it follows from the strategy above it, what ISO 55001 actually asks for, and how to write one that changes decisions.
Key takeaways
- An asset management plan says what will be done to a group of assets, when, at what cost and to what level of service, across the whole life of the assets rather than just their maintenance.
- It sits below the asset management policy and the strategic asset management plan, which turn organisational objectives into asset management objectives. ISO 55001 calls that line of sight.
- Levels of service are the part most plans skip and the part that makes them useful, because they give cost something to be traded against.
- A renewal forecast is only as good as the asset register and condition data under it. Weak plans usually fail at that step, not at the writing.
- A plan earns its keep by changing a budget, a renewal date or a maintenance strategy, and by being updated on a cycle with a named owner.
An asset management plan sets out what will be done to a group of assets over a planning period, when it will be done, what it will cost, and the level of service it is meant to deliver. It spans the whole life of the assets, from acquisition and operation through maintenance and renewal to disposal.
That makes it a decision document rather than a description. Its job is to show, for a defined asset base, what the organisation will spend and what that buys in performance and risk. A plan that changes no budget, no renewal date and no maintenance strategy has not done its job, however thick it is.
This guide covers what separates the plan from the strategy above it and the maintenance plan below it, what ISO 55001 actually asks for, what goes in each section, how to write one, and why most weak plans fail at the data rather than at the writing.
The documents around the plan, and what each one is for
Asset management produces a stack of documents with similar names, and much of the confusion about planning comes from mixing them up. Each one answers a different question and is owned at a different level.
| Document | The question it answers | Typical horizon |
|---|---|---|
| Asset management policy | What the organisation commits to in the way it manages assets | Standing, reviewed periodically |
| Strategic asset management plan (SAMP) | How organisational objectives become asset management objectives, and how plans will be developed | The planning period of the business strategy |
| Asset management plan | What will be done to which assets, when, at what cost and to what level of service | Commonly five to ten years, with a longer outlook on renewals |
| Maintenance strategy | Which failure modes are managed, and by what kind of task | Reviewed by asset class |
| Maintenance plan and task list | The actual jobs, intervals and trades, held in the CMMS | Live |
A document that only lists maintenance tasks is a maintenance plan. An asset management plan has to carry the money and the service level as well.
The line from objectives to tasks
ISO 55001 calls it line of sight. Organisational objectives set the asset management objectives. The SAMP explains how one becomes the other and how plans will be built. The asset management plans say what will be done. The work that follows should trace back up that line, and the performance measures should report back down it.
Line of sight matters most when something has to give. When a budget is cut, it shows what falls over, in service and in risk, and which objective is no longer being served. Without it, the argument is between departments rather than about consequences.
The traffic runs both ways. What the assets can actually deliver, and what they cost to keep delivering it, should shape the objectives rather than simply be told to meet them. A plan that quietly absorbs an impossible target is worth less than one that says the target needs either more money or a different level of service.
ISO 55000, and what it actually asks for
ISO 55000 is a family rather than a single standard. ISO 55001 holds the requirements and is the one organisations certify against. Its 2024 edition sharpened what it asks on decision making, realising value from assets, asset management planning, risk and opportunities, data and knowledge, and life cycle operations. Standards Australia adopted it as AS ISO 55001:2024.
The standard is deliberately not prescriptive about format. It sets no template for the plan and no minimum number of years. It asks that objectives are set and are consistent with the organisational ones, that planning converts them into activities with resources, responsibilities and timeframes, that risks are considered across the life cycle, and that performance is evaluated and improved.
That freedom is useful. A mine, a water utility and a rail operator can all satisfy the same requirements with documents that look nothing alike, which is why copying another industry's template usually produces a plan nobody in the business recognises.
| Reference | What it is | Where it helps |
|---|---|---|
| ISO 55000:2024 | Vocabulary, overview and principles | Getting the terms straight before anything is written |
| ISO 55001:2024 | Requirements for an asset management system, and the standard certified against. Adopted as AS ISO 55001:2024 | Structuring the system the plan sits inside |
| ISO 55002:2018 | Guidance on applying ISO 55001 | Practical interpretation while its revision is in development |
| ISO/TS 55010 and ISO 55011, 55012 and 55013 | Guidance on aligning financial and non-financial functions, on public policy, on people and competence, and on data for asset management | The parts plans handle worst, particularly money and data |
| IIMM, from IPWEA and NAMS | The how-to manual for infrastructure asset management, widely used across Australia and New Zealand | Templates, levels of service and renewal modelling for infrastructure |
| GFMAM Asset Management Landscape | A map of the subjects that make up the discipline | Scoping an improvement program |
What goes in the plan
Formats vary by industry and regulator, but the content is consistent. The third column is the one to test a draft against, because a section with no evidence under it is an opinion with a heading.
| Section | What it answers | Evidence it rests on |
|---|---|---|
| Scope and asset base | Which assets are covered, by class, location and level of the hierarchy | The asset register and the hierarchy it is structured on |
| Levels of service | What the assets must deliver, in measures the operation or the customer recognises | Agreed service measures, and current performance against them |
| Demand and future need | What changes in volume, duty or regulation over the period | The production or growth plan, and regulatory commitments |
| Condition and performance | What state the assets are in and how they are behaving | Condition assessments, failure history, monitoring results |
| Risk and criticality | Which failures matter most, and what is being done about them | Criticality ranking, FMECA, the risk register |
| Lifecycle activities | Operate, maintain, renew, upgrade or dispose, by asset class | Maintenance strategies, renewal models, the project list |
| Financial forecast | What the plan costs year by year, split between operating and capital | Costed activities, unit rates, the renewal profile |
| Resources and capability | Who does the work, and what they need to do it | Resource plan, skills, contracts, spares holdings |
| Risks to the plan itself | What could stop the plan being delivered | Funding, resourcing, approvals and supply assumptions |
| Improvement plan | What has to get better before the next version can be trusted further | Data gaps, maturity assessment, audit findings |
The improvement section is the one worth writing honestly. Every plan rests on assumptions, and naming them is what makes the next version better than this one.
Levels of service, the part most plans skip
A level of service states what an asset or service has to deliver, with a measure and a target, in terms its users recognise. For a water utility that might be pressure, continuity and water quality. For a processing plant it is more often availability, throughput at specification, and compliance with environmental limits.
Levels of service do the hard work in a plan, because they are what connects money to consequence. Once a target is written down and costed, the conversation stops being about whether a budget is too big and starts being about which level of service the organisation is buying.
- Use measures that are already collected, or commit to collecting them. A target with no measurement behind it cannot be managed.
- Separate what the operation or the customer experiences from the technical measures that drive it. Availability is experienced. Mean time between failures is technical.
- Cost at least two options, such as holding the current level and accepting a lower one, so the trade-off is a decision rather than a debate.
- Record where current performance sits against each target, including where it sits comfortably above. Delivering more than was asked for also costs money.
How to write one
The order below front-loads the work everything else depends on. Each step produces something the next one uses, and the first pass will be rougher than the second, which is the point of writing the improvement plan at the end.
- Fix the scope. Which assets, at what level of the hierarchy, over what period. A plan that covers every asset at component level will never be finished.
- Establish the asset base. A register that matches what is in the field, on a hierarchy the business can actually use, carrying the data decisions need.
- Set levels of service with the people accountable for delivering them, and measure where performance sits today.
- Rank criticality, so the analysis and the spending are proportionate to consequence.
- Decide the lifecycle activities for each class, with maintenance strategies coming from RCM, FMECA or templates by criticality band.
- Cost the activities and build the year by year forecast, separating operating from capital and showing the renewal profile.
- Test the plan against the constraints that will actually bind, which are usually funding, shutdown windows, resources and supply lead times.
- Write the improvement plan, name the owner and set the review cycle before the document is issued, not after.
The data the plan stands on
Most asset management plans fail quietly at the data step. A renewal forecast built on a register with wrong install dates, missing assets and duplicate records produces a number that looks precise and is not, and the precision is what makes it dangerous.
The register and its hierarchy come first, because every cost, failure and condition record attaches to them. That is what maintenance master data makes possible, and rebuilding it is a project in its own right rather than a tidy-up, as the asset hierarchy rebuild describes.
Condition is the other pillar. Age alone predicts remaining life poorly, so a plan is stronger where condition assessments and condition monitoring inform renewal timing rather than a default life read off a table. For new assets, the plan, the strategies and the data should arrive with the asset, which is part of operational readiness.
Write down how much confidence each input deserves. A plan that says which numbers are estimates is more useful than one that pretends they all came from the same place.
Costing the plan
The financial section is what turns the document into a decision. It needs the operating cost of running and maintaining the assets, the capital cost of renewals and upgrades, and the timing of both, at a level of detail the finance team can work with.
Whole of life cost is the frame. The cheapest asset to buy is often not the cheapest to own, and a renewal deferred to next year usually costs more than it saves once the extra failures and their consequences are counted. The Cost of Downtime Calculator gives a defensible figure for the production side of that argument.
Where the plan costs more than the funding available, say so plainly and show the consequence in levels of service and risk. A plan quietly trimmed to fit the budget hides the decision that was actually made, and it is the organisation that carries that risk rather than the document.
Mining and industrial plans are not council plans
Public infrastructure planning follows a well established pattern in Australia, with levels of service written for the community, ten year forecasts that line up with long term financial plans, and manuals such as the IIMM for method. Regulators and auditors expect that shape, and the sector has decades of practice at it.
In mining and processing the drivers differ. The horizon follows the mine plan rather than a fixed ten years, the level of service is production, availability and compliance, and an asset can lose most of its value when the pit that feeds it closes. Relocatable and short-life assets change renewal decisions completely.
The structure still holds. What changes is the planning horizon, what counts as service, and how much of the plan is written around the shutdown calendar rather than the financial year.
- Tie renewal decisions to the remaining life of the operation, not to a standard asset life from a table.
- Plan around shutdown windows, because they decide when most renewal work can physically happen.
- Separate assets that move with the operation from fixed plant, because their strategies and their end of life differ.
- Where the operation is contractor run, check that the plan and the contract ask for the same things, since the contract is what will actually be delivered.
Keeping it alive
The failure pattern is consistent. A large document is produced, often with outside help, and nothing in the operating rhythm refers to it again. Two years later it is out of date, and the next team does not trust the numbers enough to update it, so they start again.
What keeps a plan alive is small and unglamorous. A named owner, an update tied to the budget cycle, a short set of measures reported alongside everything else the business reports, and a trigger to revisit when duty, regulation or the production plan changes materially.
A maturity assessment every few years is worth more than a rewrite. It shows whether the system behind the plan is improving, which is what ISO 55001 is really assessing, and it gives the improvement plan somewhere to point.
Judge a plan by what it changed in the budget and the work program, not by how long it is.
Common mistakes
- Writing the plan for an audit, in language nobody in operations uses, so nobody in operations reads it.
- Leaving out levels of service, which leaves cost with nothing to be traded against.
- Building renewal forecasts from install dates and default lives, with no condition data behind them.
- Scoping so wide that the plan describes every component and finishes nothing.
- No link to the maintenance strategy, so the plan and the CMMS task list describe different worlds.
- Silence on the funding gap, which hides the decision that was actually made.
- One version, never updated, with no named owner and no review trigger.
- Treating certification as the goal rather than as evidence of a system that already works.
Building an asset management plan
Scope
Which assets, at what level of the hierarchy, over what period.
Levels of service
What the assets must deliver, measured and costed.
Asset base
Register, hierarchy, condition and failure history.
Criticality and risk
Consequence ranking, so effort follows the risk.
Lifecycle activities
Operate, maintain, renew, upgrade or dispose, by class.
Cost and test
Year by year forecast, against funding and shutdown windows.
Own and review
A named owner, an update cycle and measures that get reported.
Scope
Which assets, at what level of the hierarchy, over what period.
Levels of service
What the assets must deliver, measured and costed.
Asset base
Register, hierarchy, condition and failure history.
Criticality and risk
Consequence ranking, so effort follows the risk.
Lifecycle activities
Operate, maintain, renew, upgrade or dispose, by class.
Cost and test
Year by year forecast, against funding and shutdown windows.
Own and review
A named owner, an update cycle and measures that get reported.
Common questions
What is an asset management plan?
An asset management plan sets out what will be done to a defined group of assets over a planning period, when it will be done, what it will cost, and the level of service it is meant to deliver. It covers the whole life of the assets, from acquisition and operation through maintenance and renewal to disposal.
What is the difference between an asset management plan and an asset management strategy?
The strategy, documented in most organisations as the strategic asset management plan or SAMP, explains how organisational objectives become asset management objectives and how plans will be developed. The asset management plan is the level below it and says what will actually be done to which assets, when and at what cost.
What is a SAMP?
A strategic asset management plan is documented information that specifies how organisational objectives are converted into asset management objectives, the approach for developing asset management plans, and the role of the asset management system in achieving those objectives. ISO 55001 requires one.
What should an asset management plan contain?
Scope and asset base, levels of service, future demand, condition and performance, risk and criticality, the lifecycle activities for each asset class, a year by year financial forecast split between operating and capital, resources and capability, the risks to delivering the plan itself, and an improvement plan.
How many years should an asset management plan cover?
Long enough to show the renewal profile rather than the next budget. Public infrastructure plans in Australia commonly run at least ten years so they line up with long term financial plans. A mine or processing operation usually plans to the life of the operation or the next major renewal, whichever comes first.
Does ISO 55001 require an asset management plan?
It requires asset management objectives and planning to achieve them, documented in the strategic asset management plan and in asset management plans, with resources, responsibilities, timeframes, risk treatment and evaluation. It does not prescribe a template or a length, so the format can suit the industry.
What is a level of service?
A statement of what an asset or service must deliver, with a measure and a target, written in terms its users recognise. For a water utility that might be pressure, continuity and water quality. For a processing plant it is more often availability, throughput at specification and compliance with environmental limits.
Who should write the asset management plan?
Usually an asset manager or reliability engineer, with input from operations, maintenance, finance and planning. The owner has to be someone who can commit to the activities in it, which is why a plan written entirely by an outside party rarely survives its first budget cycle.
Do we need ISO 55001 certification?
Only where a customer, regulator, insurer or tender asks for it. Certification evidences that an asset management system exists and works. The benefit comes from the system rather than the certificate, and an organisation can follow the standard closely without certifying.
How does an asset management plan relate to maintenance planning?
The asset management plan decides what will be done and what it costs across the life of the assets. Maintenance strategy decides which failure modes are managed and by what kind of task. Maintenance planning turns those tasks into scheduled work in the CMMS. Each level should be traceable to the one above it.
Key terms
Plain-language definitions from our glossary for the concepts this article leans on.
Standards and further reading
- ISO 55000:2024 Asset management, vocabulary, overview and principles (ISO)
- ISO 55001:2024 Asset management system requirements (ISO)
- AS ISO 55001:2024 Asset management system requirements (Standards Australia)
- ISO 55002:2018 Guidelines for the application of ISO 55001 (ISO)
- ISO/TC 251, the asset management standards series (ISO)
- Developing and maintaining a strategic asset management plan (SAMP) (Institute of Asset Management)
- International Infrastructure Management Manual (IIMM) (IPWEA)
- Asset Management Landscape v3 (GFMAM)
Related case studies and tools
Related reading
Working through something like this?
See how we approach these initiatives, or tell us what you are dealing with.