Skip to content
October 2026 · 12 min read

ISO 55001 explained: what the asset management standard requires, and what changed in 2024

ISO 55001 is the requirements standard for an asset management system, and it is widely misread as a maintenance standard. What the ISO 55000 family covers, what each clause asks for, what the 2024 edition changed, when certification is worth it, and how to adopt the standard without the paperwork.

Asset ManagementConsulting
Line drawing of the seven requirement clauses of ISO 55001 arranged as a cycle around the organisation's objectives

Key takeaways

  • ISO 55001 is the requirements standard for an asset management system: the policies, objectives, plans, processes and reviews an organisation uses to get value from its assets. ISO 55000 holds the vocabulary and principles, and ISO 55002 the guidance.
  • It is a management system standard in the same family as ISO 9001 and ISO 14001, built on the same ten clauses, so it describes what has to be in place and reviewed rather than how to maintain anything.
  • The 2024 edition, adopted in Australia as AS ISO 55001:2024, kept the structure and sharpened the requirements on decision making, value, planning, risk, data and knowledge, and the life cycle, and asks whether climate change is relevant to the organisation's context.
  • Line of sight is the idea underneath it: organisational objectives set asset management objectives, which set plans, which set work, and performance reports back up the same line.
  • Certification is optional and is evidence that the system exists and works. The value comes from the system, and most of the benefit is available without certifying.

ISO 55001 is the international standard for asset management systems. It sets out what an organisation needs to have in place so that its physical assets deliver what the business needs from them, at an acceptable cost and risk, across their life. It is a requirements standard, which means it says what must exist and be reviewed, and it is the one organisations certify against.

It is also widely misread. People open it expecting a maintenance standard and find a management system document that never mentions a bearing. That is by design. ISO 55001 belongs to the same family as ISO 9001 for quality and ISO 14001 for environment, built on the same ten clauses, and its job is to make sure that the decisions about assets are made deliberately, with the right information, by people who are accountable for them, and that the results are measured and fed back.

This guide explains what the standard covers, how the ISO 55000 family fits together, what each clause actually asks for, what changed in the 2024 edition, how certification works and when it is worth it, and how to use the standard without turning it into paperwork.

The ISO 55000 family

Three documents make up the core series, with a set of technical specifications around them. Knowing which does what saves a lot of confusion, because only one of them contains requirements.

DocumentWhat it isUse it for
ISO 55000:2024Vocabulary, overview and principlesGetting the terms straight and understanding what the standard is trying to achieve
ISO 55001:2024Requirements for an asset management system, adopted in Australia as AS ISO 55001:2024Building the system, and the audit standard for certification
ISO 55002:2018Guidelines for applying ISO 55001, with a revision in developmentPractical interpretation of each requirement
ISO/TS 55010Guidance on aligning financial and non-financial functionsGetting finance and engineering to plan from the same numbers
ISO 55011, 55012 and 55013Guidance on public policy, on people and competence, and on data for asset managementThe parts most systems handle worst

What the standard asks for, clause by clause

Clauses 1 to 3 are scope, references and terms. The requirements start at clause 4, and they follow the structure every ISO management system standard shares. The table says what each clause asks for in plain terms, and what it usually looks like on a mine or an industrial site.

  1. 4Context. The organisation, its stakeholders, the scope and the SAMP
  2. 5Leadership. Commitment, the policy, roles and accountability
  3. 6Planning. Risks and opportunities, objectives, asset management plans
  4. 7Support. Resources, competence, information and documents
  5. 8Operation. Delivering the plans, managing change and outsourcing
  6. 9Performance evaluation. Measures, internal audit and management review
  7. 10Improvement. Nonconformities, preventive action, continual improvement
Fig. 1 · The seven requirement clauses of ISO 55001, as a cycle around the organisation's objectives
ClauseWhat it asks forWhat it looks like in practice
4 ContextUnderstand the organisation, its stakeholders and the scope of the asset management system, and set the strategic asset management planA SAMP that says which objectives the assets serve, which assets and sites are in scope, and how plans will be built
5 LeadershipTop management commits, sets the asset management policy, and assigns roles and accountabilitiesA signed policy that people can quote, and a named accountable executive
6 PlanningAddress risks and opportunities, set asset management objectives, and plan how to achieve themObjectives with measures and timeframes, asset management plans with activities, resources, responsibilities and cost
7 SupportResources, competence, awareness, communication, information requirements and documented informationThe asset register and data standards, competency frameworks, and control of the documents that matter
8 OperationPlan, implement and control the activities in the plans, manage change, and control outsourcingMaintenance, inspection, projects and contractors delivered as planned, with management of change
9 Performance evaluationMonitor, measure, analyse and evaluate, audit internally, and review at management levelMeasures reported against objectives, internal audits, and a management review that changes something
10 ImprovementDeal with nonconformities and incidents, take preventive action, and improve continuallyRoot causes found and fixed, and the plan updated with what was learnt

The standard never says how to maintain an asset. It asks whether the decision was made on purpose, by someone accountable, with the information it needed.

Line of sight, the idea underneath it

If one idea holds the standard together, it is line of sight. Organisational objectives set the asset management objectives. The strategic asset management plan explains how one becomes the other and how plans will be built. The asset management plans say what will be done to which assets, when, at what cost and to what level of service. The work in the field traces back up that line, and performance reporting runs back down it.

That is why a certified system can look so different between a water utility, a mine and a rail operator. The standard fixes the line, not the documents. What matters at audit is whether a task in the CMMS can be traced to an objective the board recognises, and whether a missed objective can be traced down to the assets and decisions that caused it.

Line of sight is also what makes the standard useful rather than bureaucratic. When a budget is cut, it shows what falls over in service and risk. When a plant underperforms, it shows which decision to revisit. A system that cannot do either has the documents without the line.

What changed in the 2024 edition

The first edition was published in 2014. The 2024 revision kept the ten-clause structure, so an existing system is updated rather than rebuilt, and concentrated on making the requirements sharper where the first edition had been read loosely. The areas below are where most organisations find work to do.

  • Decision making: the organisation is expected to set the criteria it uses to make asset management decisions, including how value, cost, risk and performance are traded off, and to apply them consistently.
  • Value: a clearer expectation that the system is there to realise value from assets for the organisation and its stakeholders, with that value defined rather than assumed.
  • Planning: more specific requirements on asset management planning and on what asset management plans contain across the life cycle.
  • Risks and opportunities: the planning requirements treat opportunities alongside risks, in line with the current management system structure.
  • Data and knowledge: stronger requirements on the data, information and knowledge the system depends on, including its quality and management.
  • Life cycle: an expectation that assets are managed across their whole life, from need and acquisition through operation and maintenance to renewal and disposal, rather than within a maintenance window.
  • Climate change: in line with the amendment ISO applied across its management system standards in 2024, the organisation determines whether climate change is a relevant issue in its context and, where it is, addresses it in planning.

The revision did not add paperwork. It asked for the thinking that a good system already did to be visible.

Certification, and when it is worth it

Certification means an accredited body has audited the asset management system against ISO 55001 and found it conforms. The certificate is evidence that the system exists, is implemented and is reviewed. It is not a judgement on the condition of the assets or the quality of the maintenance, which is a distinction worth keeping in mind on both sides of a tender.

It is worth seeking when someone outside the organisation needs the evidence: a regulator that expects it, a customer or alliance partner that asks for it, an insurer, a board that wants an external check, or a tender where it scores. It is also a useful forcing function for an organisation that has started an improvement program and wants a date it cannot slip.

It is not worth seeking as a goal in itself. An organisation that adopts the standard, builds the line of sight, fixes its data and runs the review cycle gets most of the value with or without a certificate. The ones that certify first and build afterwards tend to own a certificate and a shelf of documents nobody uses.

  • Decide the scope deliberately: which assets, which sites, which parts of the business. A narrow, honest scope beats a wide one that cannot be evidenced.
  • Run a gap assessment against the clauses before committing to a date, and treat the data and competence gaps as the long ones.
  • Audit internally at least once with people who were not involved in building the system.
  • Expect the management review to be the clause most often found weak. If it does not change decisions, it is not a review.

Using the standard without the paperwork

The common failure is to read ISO 55001 as a list of documents and produce them. The system then exists on paper and nowhere else. The alternative is to read it as a list of questions and answer each one with something the organisation already does or needs to do anyway.

Most sites already have most of the system. There is a budget process, a maintenance strategy, a CMMS with a hierarchy, a risk register, a set of measures and some kind of review. What is usually missing is the line between them: objectives nobody wrote down, plans that do not trace to them, data that cannot support the decisions the plans claim to rest on, and a review that reports without deciding. Building the system means joining what exists, and the asset management plan is usually the document that does the joining.

The data is where the work hides. A sound hierarchy, a register that matches the field, and master data that can carry a criticality, a strategy and a cost are what let the system make the decisions it promises. Without them the clauses are satisfied by assertion.

Answer the standard with what the business already does, joined up. Documents written to satisfy a clause are the ones nobody opens.

Standards that work alongside it

ISO 55001 sets the system and leaves the methods to other standards. These are the ones most often used to answer its requirements in mining and industrial settings, each an option rather than a requirement of the standard itself.

ReferenceWhat it coversWhich part of the system it serves
ISO 14224Equipment taxonomy and reliability dataThe information requirements in clause 7, and the data behind performance evaluation
ISO 31000Risk management principles and guidelinesRisks and opportunities in clause 6
SAE JA1011 and IEC 60812RCM criteria, and FMEA and FMECA methodDeciding the activities in the asset management plans
ISO 17359Condition monitoring and diagnostics of machinesMonitoring in clause 9, and the condition data decisions rely on
ISO 15663 and ISO 15686-5Life cycle costing, for petroleum and gas and for constructed assetsThe whole of life cost decisions the plans are built on
GFMAM Asset Management LandscapeThe subjects that make up the disciplineScoping a gap assessment or an improvement program

Adopting ISO 55001

  1. Set the scope

    Which assets, sites and functions the system covers, agreed with leadership.

  2. Assess the gaps

    Each clause against what exists, with data and competence treated as the long items.

  3. Write the line of sight

    Policy, SAMP and asset management plans that trace objectives to work.

  4. Fix the data

    Hierarchy, register and master data able to carry the decisions.

  5. Run the cycle

    Measures, internal audit and a management review that changes something.

  6. Certify if it serves a purpose

    When a regulator, customer, insurer or board needs the evidence.

Common questions

What is ISO 55001?

ISO 55001 is the international standard that sets out the requirements for an asset management system. It describes what an organisation needs to have in place, from policy and objectives through planning, support, operation, performance evaluation and improvement, so that it manages its assets to deliver value against its objectives. It is the standard organisations are certified against.

What is the difference between ISO 55000, ISO 55001 and ISO 55002?

ISO 55000 gives the overview, principles and vocabulary. ISO 55001 holds the requirements and is the auditable standard. ISO 55002 gives guidance on applying ISO 55001. The 2024 revision updated ISO 55000 and ISO 55001 together, and a revised ISO 55002 is in development.

What changed in ISO 55001:2024?

The ten-clause structure stayed, so existing systems do not need rebuilding. The revision sharpened requirements on decision making and the criteria behind it, on realising value from assets, on asset management planning and the content of plans, on risks and opportunities, on data and knowledge management, and on managing assets across their life cycle. In line with other ISO management system standards revised since early 2024, it also asks the organisation to determine whether climate change is a relevant issue in its context.

Is ISO 55001 certification required?

No. Certification is a choice, usually made because a regulator, customer, tender, insurer or board asks for it. The standard can be adopted without certifying, and many organisations use it as a framework for an improvement program and never seek a certificate. A certificate is evidence that a system exists and operates, not proof that the assets are well managed.

What is an asset management system?

The set of interrelated elements an organisation uses to establish its asset management policy and objectives and the processes to achieve them. In practice it is the policy, the strategic asset management plan, the asset management plans, the roles and competencies, the information and data, the operational processes, the measures and the review cycle, taken together. The assets themselves are managed by the system; they are not part of it.

What does ISO 55001 say about maintenance?

Very little directly. It requires that the activities needed to deliver the asset management plans are planned, controlled and monitored, and that outsourced activities are controlled. How to develop a maintenance strategy, which techniques to use and what intervals to set are left to other standards and to the organisation. ISO 55001 is about whether those decisions are made deliberately, resourced and reviewed.

Who should use ISO 55001?

Any organisation whose performance depends on physical assets: utilities, mining and processing operations, rail and road operators, ports, oil and gas facilities, manufacturers and public infrastructure owners. It is written to apply to any asset type and any size of organisation, which is why it says what rather than how.

Key terms

Plain-language definitions from our glossary for the concepts this article leans on.

Standards and further reading

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.