A strategic asset management plan that has never stopped anything is a description

Ask an organisation for its strategic asset management plan and you will generally be given a document. It will be well produced. It will describe the asset base, restate the organisational objectives, set out a maturity roadmap, and contain a diagram with four quadrants.

Then ask what it has stopped. What was proposed, tested against the plan, and not funded as a result.

The answer is usually nothing, and usually nobody has been asked the question before. That is the difference between a plan and a description, and it is not a difference of quality. Some of the most carefully written asset management plans in existence have never influenced a single allocation.

What changed in 2024

In the 2014 edition, the strategic asset management plan was mentioned in several places without ever being gathered into a requirement of its own. You could read the standard carefully and still be unclear whether the SAMP was a document, a process, or a way of describing the relationship between two other things.

The second edition made it Clause 6.2.1, sitting at the head of the objectives clause, before asset management objectives at 6.2.2 and planning to achieve them at 6.2.3. ISO lists the change among the main differences from the first edition, alongside the new decision-making subclauses and knowledge.

Something else moved in the same revision. Among ISO's listed changes is this:

a stronger emphasis on leadership and its role in supporting the enablement and success of the asset management system.

Enablement is a carefully chosen word and it is not the same as support. It is worth sitting with, because it identifies what actually goes wrong.

What the SAMP is for

The SAMP is a translation layer. It sits between what the organisation is trying to achieve and what the organisation is going to do about its assets, and its function is to make the second follow from the first.

Without that layer, asset decisions are made on some other basis, and the basis is nearly always precedent. Maintenance budgets become last year plus or minus a percentage. Renewal programmes reflect which manager argued hardest. Capital proposals compete on the quality of their business cases rather than on their contribution to anything.

None of that is irrational behaviour by the people involved. In the absence of a translation layer it is the only available behaviour, because there is no shared standard by which one proposal is better than another, so persuasion is the mechanism that remains.

This is also why the SAMP has to come after the decision criteria and after the policy, and why an organisation that produces it first ends up with a document that describes rather than allocates. A plan is an application of criteria to a specific asset base under a specific constraint. Written before the criteria exist, it has nothing to apply.

Where the criteria come from

, read: ISO 55001 now requires you to write down how you decideISO 55001 now requires you to write down how you decide

Why most of them describe instead

Three reasons, in ascending order of how uncomfortable they are.

It is written for an assessor. If the immediate purpose is demonstrating conformity, the document optimises for coverage. It will address every clause and commit to nothing, because a commitment creates a finding if it is not met, whereas a description cannot fail an audit.

Describing is easier and looks the same from a distance. A section explaining how the organisation approaches renewal planning takes an afternoon. A section stating what will not be renewed in the next five years, and what the consequence is, takes months and requires condition data most organisations do not have.

Allocating means declining. A plan that prioritises is a plan that deprioritises. Every asset class that moves up moves another one down, and the manager of the second one has a name, a budget and an opinion. A document that has never produced that conversation has not been applied.

The obstacle only leadership can remove

Here is the structural problem that no asset management plan can fix from inside, and it is the reason ISO's word is enablement.

On most large asset-owning organisations, capital and operating budgets sit in different parts of the organisation, are approved on different cycles by different committees, and are the responsibility of people who do not report to each other until several levels up. Capital is usually the more senior, better resourced and more politically visible of the two.

Every whole-life argument the SAMP wants to make runs directly across that boundary. Spend more here now to spend less there later is a sentence that requires one budget holder to accept a cost so another can avoid one. There is no version of a well-written plan that overcomes this, because the obstacle is not analytical. It is structural, and it can only be removed by someone with authority over both sides of it.

That is what leadership means in Clause 5, and it is why a stronger emphasis on it was worth adding. Not sponsorship, not a signed foreword, not attendance at the steering committee. The specific act of making a decision possible that the organisation's structure otherwise prevents.

The same boundary, seen from the contract side

, read: You cannot buy an outcome you cannot specifyYou cannot buy an outcome you cannot specify

An asset management function reporting three levels below the people who control both budgets can produce an excellent plan and will not be able to execute it. This is worth establishing early, because it is diagnosable on day one from an organisation chart, and it determines what the function can realistically achieve far more than its competence does.

Policy, and what it is for once criteria exist

Clause 5 puts the policy at 5.2, between leadership and commitment at 5.1 and roles, responsibilities and authorities at 5.3.

Written in the right order, after the decision criteria, a policy does something a policy written first cannot. It states the intent that governs how the criteria get applied when they conflict, which they will. Safety against cost. Service continuity against renewal. Carbon against capital. The criteria say what is weighed; the policy says which way the organisation leans when weighing produces a tie.

That is a short document and a useful one. What it is not is a statement that the organisation will manage its assets to maximise value while ensuring safety, sustainability and compliance, which is true of every organisation that has ever existed and therefore distinguishes nothing.

Clause 5.3 then requires that roles, responsibilities and authorities are assigned and communicated. The word to attend to is authorities. Responsibility without authority is the standard condition of asset management functions, and it is the condition in which plans get written and not applied.

Establishing this while inheriting an estate

For organisations in this region moving from delivering assets to owning them, the leadership problem has a particular shape.

Leadership attention was built around delivery, because for a decade delivery was the whole task, and the reporting lines, committee structures and seniority all reflect that. The asset management function arrives into a structure optimised for a job that is finishing.

The practical consequence is that the function is usually established at a level appropriate to a support service rather than to something that will eventually govern the majority of the organisation's balance sheet. That decision is taken quickly, early, and by people with other priorities, and it is considerably harder to reverse than to get right initially.

Two things are worth settling at the outset, both of which are organisational rather than technical. Whether the function has access to the person who controls both capital and operating budgets. And whether its plan is an input to the budget process or a document produced after the budget is set. The second question has only one right answer and a great many organisations discover they have the wrong one in their second year.

The assurance framework sets out how to test the line from the plan to a funded activity, and separately how to test whether anyone estimated the cost of ownership while the decisions that fixed it were still open.

---

Sources. ISO 55001:2024, Asset management, Asset management system, Requirements, second edition, July 2024, prepared by ISO/TC 251, ISO standard 83054. Clause 5 and Clause 6.2 structure, and the quoted change on leadership, are taken from the contents and foreword as published by ISO. ISO 55000:2024, ISO standard 83053, gives leadership as one of the three revised principles of asset management, alongside value and alignment. Guidance on applying ISO 55001 is published separately as ISO 55002, and guidance on people involvement and competence as ISO 55012. The requirement text of these standards is behind a paywall and is described here rather than reproduced.