ISO 55001 requirements per chapter (HLS)

The requirements of ISO 55001 are in chapters 4 to 10. They follow the High Level Structure (HLS), the fixed structure used by all modern ISO management standards. Chapters 1 to 3 cover the scope, the normative references and the terms. The actual requirements start in chapter 4. Read the text of the standard at ISO .

The HLS is useful if you want to set up several systems at once. Chapter 4 always covers context, and chapter 6 always covers planning. More explanation of this structure is on the HLS structure. For an overview of the standard, start at What is ISO 55001?.

For each chapter, an auditor checks whether you have done the work and whether you can demonstrate it. You do not need everything to be perfect, but you must show it.

Which factors affect your assets and who has an interest.4. Context Policy, roles and support from top management.5. Leadership Risks, objectives and the SAMP.6. Planning People, resources, knowledge and information.7. Support Carrying out plans and managing changes.8. Operation Measuring, internal auditing and reviewing.9. Evaluation Resolving nonconformities and improving the system.10. Improvement

The overview in a table

Chapter	Title	What you need to do
4	Context of the organisation	Map factors and interested parties, define the boundary of the AMS
5	Leadership	Adopt an asset management policy, assign roles and responsibilities
6	Planning	Determine risks and opportunities, set objectives, produce the SAMP and asset management plans
7	Support	Arrange resources, competence, awareness, communication, information and documents
8	Operation	Carry out plans, control changes, direct outsourced work
9	Performance evaluation	Measure performance, carry out internal audits, report back to top management
10	Improvement	Address nonconformities and their causes, keep improving the system

4. Context of the organisation

You look at which internal and external factors affect your assets. You also determine who has an interest in how you manage them, and what exactly the asset management system (AMS) covers. That is the boundary of your system.

Example: grid operator Netwerk Oostveld (fictional) notes that heavy rainfall puts extra strain on the cables in the Oostrand district. The municipality also wants works not to take place on the busiest market days. Both factors are reflected in the AMS.

5. Leadership

Top management adopts the asset management policy. It also assigns roles, such as who is ultimately responsible for managing each asset. Without that support, the system stays a plan in a folder.

Example: the director of Netwerk Oostveld signs the policy and appoints an asset manager with a fixed mandate. That manager may approve replacements up to a set amount without further sign-off.

6. Planning

Here you determine which risks and opportunities relate to your assets. You set measurable objectives and produce the strategic asset management plan (SAMP). The SAMP links the organisation’s objectives to the objectives for the assets. You can read more about it on the SAMP.

Example: a pumping station whose failure would affect the whole polder receives a high risk score. A bench in the park receives a low score. As a result, the pumping station is at the top of the replacement list.

7. Support

This chapter covers the conditions that must be in place: people, money, knowledge, communication and information. The documents you use must also be in order. That means an up-to-date register and clear version control.

Example: every switch cabinet in the register has a unique number, a year of construction and the date of its last inspection. A technician who modifies a cabinet updates the register straight away.

8. Operation

You carry out the plans and manage changes to your assets. Work you outsource also falls under this chapter. You make sure the party doing the work keeps to the agreements.

Example: a maintenance company carries out the annual cabinet inspection. The contract sets out the deadlines, the reporting and what happens if a nonconformity is found.

9. Evaluation

You measure whether the system works. You carry out internal audits and discuss the results with top management. These are the proof that the AMS works, not just that it exists on paper.

Example: Netwerk Oostveld tracks each month how many faults occur per cabinet and how much maintenance was carried out on time. Every year a colleague from another team carries out an internal audit.

10. Improvement

When something goes wrong, you look for the cause and adjust the system. This applies to faults, but also to nonconformities in the process.

Example: after a fault caused by a corroded cable tray, Netwerk Oostveld changes the inspection schedule. From now on every cable tray is checked annually, not only during the major maintenance round.

What changed in the 2024 version?

ISO 55001:2024 replaces the 2014 version. The chapters remain the same, but the content gives more emphasis to climate, sustainability and data. Climate change returns as a topic under context. The exact changes per chapter are set out in the standard itself, which you can find at ISO .

This is a broad overview. Check the exact requirements in the standard itself, and ask your certification body when you need to switch if you currently hold a 2014 certificate. You can read more about the versions on ISO 55001 version 2024.

Frequently asked questions about the ISO 55001 requirements

Are the ISO 55001 requirements the same as those of ISO 9001?

The chapters follow the same order, because both standards use the HLS. The content is different. ISO 9001 is about the quality of your products and services. ISO 55001 is about managing your physical assets. See the ISO 9001 overview for the quality standard.

Where do I start if I have nothing in place yet?

Start with chapters 4 and 5. First make clear which assets you have and who sets the policy. Planning in chapter 6 follows after that. The step-by-step plan gives the order in more detail.

How much evidence do I need?

You must be able to demonstrate every requirement, but the evidence does not have to be extensive. A short decision with a date and a name may be enough for a small team. An auditor mainly checks whether the evidence is accurate and whether the system is actually used.