ISO 55000: The Asset Management Standard Explained

ISO 55000 is the international series of standards for asset management. It describes how organisations get value from their physical assets — machinery, installations, buildings, infrastructure — through a structured asset management system. The series has three parts: ISO 55000 (overview and terminology), ISO 55001 (requirements for the management system) and ISO 55002 (application guidelines). Certification is only possible against ISO 55001, because that is the part containing auditable requirements.

The three parts of the series

The ISO 55000 series is developed by ISO/TC 251, the technical committee for asset management. Each part plays its own role:

• ISO 55000 — Overview, principles and terminology. Defines what an asset is, what asset management means and which principles underpin it. Read this part first: it establishes the vocabulary.
• ISO 55001 — Requirements for the management system. Describes what an asset management system must cover: context, leadership, planning, support, operation, evaluation and improvement. This is the standard audits and certification are based on.
• ISO 55002 — Application guidelines. Provides explanation and examples for the requirements in 55001. No additional requirements, just practical guidance.

One thing worth knowing: the standard does not prescribe how to maintain your assets. It sets requirements for the management system around them — the decision-making, processes and responsibilities you use to manage assets.

Why the standard exists

Many organisations manage assets that last decades and cost millions. Without structure, three recurring problems appear, and the standard was built to address exactly these:

1. 1Value goes undefined. Decisions about maintenance, replacement and investment are made per department or per incident, without weighing cost, risk and performance across the full life cycle. The standard forces you to make that trade-off explicit.
2. 2Nothing is demonstrable. Clients, regulators and insurers increasingly ask for evidence that you are in control of your assets. A documented management system makes that evidence available.
3. 3Strategy and execution are disconnected. Management sets objectives, but nothing changes on the shop floor. The standard requires a continuous line from organisational objectives to concrete activities.

Key concepts you should know

• Asset. Anything that has, or could have, value for the organisation. In practice this usually means physical assets: machines, vehicles, buildings, networks.
• Asset management. The coordinated activities through which an organisation realises value from assets. That is broader than maintenance: it also covers investing, managing risk and disposal.
• SAMP (Strategic Asset Management Plan). The document that translates organisational objectives into asset management objectives and describes how you will achieve them. The SAMP bridges business strategy and the concrete asset management plans per asset group.
• Line of sight. The principle that every activity on an asset can be traced back to an organisational objective — and vice versa. A technician overhauling a pump does so because that pump's availability contributes to, say, security of supply. That line must be visible and substantiated.

Certification: what it involves and who it is for

During certification, an independent certification body assesses whether your asset management system meets the requirements of ISO 55001. This happens through a document review and on-site audits, followed by periodic surveillance audits. A certificate is typically valid for three years. In the Netherlands, NEN publishes the standard as NEN-ISO 55001 and provides background information.

Certification is most relevant for:

• Capital-intensive organisations: energy and drinking water companies, industry, ports, rail and road authorities.
• Infrastructure managers and public bodies that manage public assets and must account for them to regulators or politicians.
• Contractors and service providers in long-term management contracts, where clients include ISO 55001 as a requirement in tenders.

To be honest: for an organisation with a limited asset base and no external parties asking for demonstrable control, the investment in certification often does not outweigh the benefits. You can apply the principles of the standard perfectly well without the certificate. The value lies in working according to the system; the certificate is the proof of it, not the goal.

Getting started with ISO 55000 in practice

You do not need to build an audit-ready system straight away. A realistic sequence:

1. 1Map the current situation. Which assets do you have, what condition are they in, which processes already exist? A gap analysis against ISO 55001 shows where you stand.
2. 2Define policy and objectives. What does the organisation want to achieve with its assets? Record this in an asset management policy and develop it into a SAMP.
3. 3Get your register and data in order. A complete, up-to-date asset register with locations, attributes and history is the foundation. Without reliable data you cannot substantiate risks or demonstrate performance.
4. 4Set up processes. Work orders, inspections, failure recording, investment prioritisation — define who does what and how decisions are made.
5. 5Measure, evaluate and improve. The standard revolves around a cycle: plan, do, check, act.

The relationship with maintenance management and CMMS

ISO 55001 requires documented information about your assets: what you have, what has happened to it and how it performs. That is exactly what maintenance management software records. If you want to understand how such a system works, read what a CMMS is: it records work orders, failures and maintenance history, forming the data foundation under an asset management system.

An EAM system goes a step further and supports the full asset life cycle — the difference is explained in CMMS vs EAM. For the standard, the rule is simple: no reliable records means nothing is demonstrable, and nothing demonstrable means no certificate. If your maintenance data is in order in the platform your organisation uses, most of the evidence for an audit is already in place.