ISO 55000 Asset Management: Why a Maintenance Plan Is Not Enough

How does asset management differ from a maintenance plan?

ISO 55000 defines asset management as the coordinated activity of an organisation to realise value from its assets, which involves balancing costs, risks, opportunities and performance benefits. ^[6] A maintenance plan answers a narrower question: how do we keep the asset working during its operating phase?

The Institute of Asset Management (IAM) stresses that the greatest value goes to organisations that see asset management as much more than an extension of maintenance. ^[6] An asset’s life runs from the initial concept to disposal, through design, acquisition, operation and maintenance, and then renewal or replacement. ^[6] The IAM notes that design decisions can determine as much as 80% of life cycle costs, before the asset ever reaches the maintenance team. ^[6]

The IAM also describes a constant trade-off between caring for an asset through maintenance and using it in operation, where the aim is the right compromise between competing interests. ^[6] The maintenance department cannot settle that trade-off alone, because the other side of it belongs to operations or service delivery.

So a maintenance plan can be technically excellent while the organisation loses value in purchasing, design and replacement decisions that never pass through it.

What is new in ISO 55000:2024?

ISO 55000:2024, “Vocabulary, overview and principles”, is the foundation of the series and provides the context for ISO 55001 and ISO 55002. ^[1] It succeeds the 2014 edition, and the main changes are: ^{[1, 3]}

• Revised principles, and the introduction of the expected “outcomes” of asset management.
• Benefits rephrased and extended.
• Integration of management systems and the concept of organisational asset management maturity introduced.
• Definitions adapted, with a much shorter section on principles, benefits and key concepts.

The series also includes ISO 55001 (requirements), ISO 55002 (guidance), ISO/TS 55010, ISO 55011, ISO 55012 and ISO 55013. ^[1] ISO 55001 alone specifies the requirements for establishing, implementing, maintaining and improving an asset management system, and the organisation chooses which assets the system covers. ^[2]

The three principles: value, alignment and leadership

The 2014 edition rested on four fundamentals: value, alignment, leadership and assurance. The 2024 edition keeps three principles, value, alignment and leadership, and moves assurance into the list of outcomes alongside two new ones, adaptability and sustainability. ^[3]

• Value: assets exist to deliver value to the organisation and its stakeholders, not to be maintained for their own sake.
• Alignment: organisational objectives are translated into decisions, plans and activities on assets.
• Leadership: asset management depends on top management commitment and a culture that reaches every level.

In practice, this shift means confidence that assets will do what they are meant to do is built as a result of applying the three principles, rather than as a separate starting point.

Line of sight: from the organisational plan to the work order

The IAM calls the link between an organisation’s strategic plan and the work its people carry out on assets “line of sight”, also known as alignment. ^[6] The link runs through a chain of documents: an asset management policy derived from the organisational plan, then the Strategic Asset Management Plan (SAMP), which converts organisational objectives into asset management objectives, then the detailed asset management plans. ^[6]

The test for line of sight is simple. Pick a random work order from the maintenance system and ask why it was done this way and at this time. If the answer stops at “because the schedule says so”, without reaching an objective, a service level or a specific risk, the chain is broken.

What does ISO 55001:2024 require that a maintenance plan does not cover?

The 2024 edition of ISO 55001 follows the Harmonized Structure for management system standards, adds new subclauses and strengthens the role of leadership. ^[5] Requirements that a conventional maintenance plan does not address include: ^{[2, 4, 5]}

• Decision-making and value (clause 4.5): the organisation sets up a decision-making framework suited to its size and complexity, and defines what “value” means to it and the decision criteria for delivering it, so that decisions connect across all levels.
• SAMP (clause 6.2.1): contains the decision-making framework and high-level initiatives, actions and timeframes, is retained as documented information, and may be spread across several documents.
• Risks and opportunities (clauses 6.1.2 and 6.1.3): risks cover the assets, asset management and the organisation as a whole; opportunities are planned separately from risks; ISO 31000 can serve as a general risk framework.
• Planning of changes (clause 6.3): risks to asset management objectives are assessed before any change.
• Data and information (clause 7.6): data specifications and a plan for collecting, integrating, improving and sharing data.
• Knowledge (clause 7.7): determining the knowledge needed, acquiring and retaining it, and periodically reviewing it and discarding what is out of date.
• Externally provided items (clause 8.3): broadened from “outsourcing” to cover processes, technologies and products, for example specifications for critical spare parts and checks that what arrives matches them.
• Predictive action (clause 10.3): replaces preventive action and covers potential failures of assets, of asset management and of the system itself, taking account of their frequency and impact.

Hypothetical example: one pump, three decisions

Hypothetical example: a utility operator has a pumping station with a pump that keeps failing. The maintenance plan says the answer is more frequent inspections. Procurement wants to buy an identical pump because it has the lowest price. Finance asks for all spending to be deferred to next year.

In an asset management system the argument is not won by the loudest voice. All three options go through the same decision framework. What does each do to the target service level? What residual risk remains if replacement is deferred? What is the life cycle cost, not just the purchase price? What failure data is available to support each option? Any of the three could win, but the result becomes a documented decision that can be revisited at management review, which must itself evaluate how well the decision framework works. ^[4]

Where to start: practical steps

1. Set the scope: which assets the system covers, and which stakeholders and requirements it will address. ^{[2, 4]}
2. Define value and decision criteria: write down what value means for your organisation and how options will be compared, before any plan.
3. Write the policy and the SAMP: link every asset management objective to an objective in the organisational plan. ^[6]
4. Review the current maintenance plan: tie each activity to a risk or service level, and stop what cannot be justified.
5. Build the data plan: determine the data you need and set specifications for it, then plan how to collect, integrate, improve and share it. ^[4]
6. Assess maturity regularly: the 2024 edition introduces organisational asset management maturity, so measure where you are and identify gaps. ^[1]
7. Bring asset management into management review: the review should cover risks, opportunities, the effectiveness of the decision framework and opportunities for continual improvement. ^{[2, 4]}

Certification and the move to the 2024 edition

Certification is to ISO 55001, and organisations currently certified to the 2014 edition need to transition. A UKAS bulletin states that certification bodies have three years from publication to transition existing certificates, ending on 31 July 2027. ^[5]

The standard itself obliges no one: adopting it is the organisation’s own decision, or a condition set by a contract or a regulator. Sector requirements differ between GCC countries, so check whether the regulator for your sector in your country has its own asset management requirements, and choose a certification body accredited by your national accreditation body.

Conclusion

A maintenance plan answers “how”. Asset management under ISO 55000 answers “why”, “when” and “for what value”. Start by defining value and a decision framework, then reconnect your existing maintenance plan to organisational objectives instead of writing a new one from scratch.