The competence you need is not in the asset management function

An organisation appoints a head of asset management. It recruits a small team, perhaps four people, perhaps eight. They are competent, several are certified, and the function begins producing the documents the standard asks for.

Meanwhile, this week, in the same organisation: a procurement officer selects a supplier on lowest compliant price. A design engineer accepts a specification change that removes an access panel. A finance analyst sets a depreciation life from a policy table. A maintenance planner extends an interval to fit the shutdown window. A project manager accepts a handover pack because the alternative is a contractual dispute.

Not one of those people works in the asset management function. Every one of them has just made an asset management decision, and most of them will retire without ever having been told that.

That is the problem Clauses 7.1 to 7.4 are for, and it is why treating them as administrative preliminaries is a category error.

FIG. 01Five decisions of a kind that determines what an asset costs to own. Illustrations rather than a measured distribution, and no proportion is implied. What they have in common is that none is taken inside the function named after the discipline.

What the support clause contains

Clause 7 opens with four subclauses that look unremarkable: 7.1 resources, 7.2 competence, 7.3 awareness, 7.4 communication. Then 7.5 documented information, and then the two that changed most in 2024, data and information at 7.6 and knowledge at 7.7.

The first four are the ones every implementation treats as quick wins. They are also the ones ISO thought worth a companion standard. ISO 55012, published in the 2024 family, covers people involvement and competence in an asset management system, and the word order in its title is not accidental. Involvement comes first.

Competence is a distribution problem

The instinctive reading of Clause 7.2 is that the asset management team needs to be competent. That reading is not wrong and it is nowhere near sufficient, because it locates the requirement in the wrong place.

ISO 55000 is explicit that asset management is organisation-wide. If that is true, then the competence the standard requires is distributed across finance, procurement, engineering, operations and maintenance, and the great majority of the people holding it do not report to the asset management function, were not consulted on its establishment, and have their own functional objectives which occasionally conflict with its own.

So the question Clause 7.2 actually poses is not whether your asset managers are qualified. It is whether the procurement officer knows that a lowest-price award has a whole-life consequence, whether the finance analyst knows that the depreciation life they entered is now the number an engineer will be measured against, and whether either of them has any route to find out.

A competent asset management function inside an organisation that has not been made competent is a small group of people producing correct analysis that arrives after the decision.

This is also why competence cannot be determined before the system is designed, and why this clause sits where it does. You can only specify what people need to be able to do once you know what the system asks them to do, which is settled by the decision criteria and the plan.

Where the criteria that define the roles come from

Awareness is the load-bearing one

Clause 7.3 looks like the most skippable requirement in the standard. Awareness sounds like a poster campaign, an intranet page and a question in the annual survey.

In a distributed discipline it is the clause that determines whether anything else works. Competence answers whether someone could make the decision well. Awareness answers whether they know the decision is theirs to make.

The failure mode is specific and it is not ignorance. The procurement officer is not incompetent, they are optimising correctly for the objective they were given, which is compliant supply at the best price within the approval window. Nobody told them that the objective is incomplete, and nobody gave them a criterion that would let them argue for the more expensive option. Awareness in this sense is not information. It is the transfer of a decision from one that appeared purely functional to one understood to have consequences the function does not measure.

Which is why awareness campaigns that explain what asset management is achieve very little, and briefings that tell a specific group which of their existing decisions are asset decisions achieve quite a lot.

Resources, and the sentence that kills implementations

Clause 7.1 requires the organisation to determine and provide the resources needed. This is the clause behind which sits the single most common way an asset management system fails without anybody recording a failure.

The sentence is: we will do this with existing staff.

It is never obviously wrong when it is said. The work is real but diffuse, no individual increment looks unmanageable, and the alternative is a headcount conversation nobody wants during establishment. So the system is built as an additional duty for people who already have a full one, and it produces the documents, and it does not produce the second-order work, which is all of the work that matters: the data verification, the option appraisals, the challenge to proposals, the conversations with finance.

The diagnosis is simple enough to run. Ask what the asset management system has caused anybody to stop doing. A system that has been resourced by absorption has added tasks and removed none, and the tasks it quietly displaced were the discretionary ones, which in most organisations means the analysis.

Communication, and the register as a translation device

Clause 7.4 asks the organisation to determine what it will communicate, when, to whom and how.

In an asset context the most consequential communication in the organisation is not a report or a briefing. It is the asset register, which is the object through which the finance function and the engineering function describe the same physical things to each other.

When those two functions maintain separate hierarchies, different componentisation and different identifiers, they are not miscommunicating. They have no shared vocabulary at all, and every exchange between them requires manual translation by whichever individual happens to understand both. That person is usually one person, and they are a single point of failure nobody has recorded as one.

What happens when the two views do not reconcile

Why this bites hardest at transition

These clauses are placed here, at handover, rather than in operations, because that is when the absence becomes expensive rather than theoretical.

An organisation moving from delivering assets to owning them has spent years assembling exactly the wrong competence profile, and assembling it deliberately and well. Delivery organisations are built to procure, contract, control cost and finish. Those are difficult skills and the people who hold them are good at them. Almost none of them involve operating anything for thirty years.

At transition the organisation needs condition assessment, reliability engineering, maintenance strategy, asset data governance and whole-life economics. It has procurement, contracts, project controls and construction management. The gap is not a training gap that a course closes. It is a different discipline.

Two things then happen, both predictable. The function is staffed internally from the available pool, which means from delivery backgrounds, producing a team that understands the assets and has never operated one. And the region's organisations all reach this point within a few years of each other, so they compete for the same small number of people who have genuinely done it before.

The examinable version of this is whether the operating roles are filled rather than defined. A structure chart is not readiness, and the distinction is visible in about ten minutes.

The framework page for this stage sets out the full test, and the delivery stage covers the narrower question of whether the people examining a programme understand what they are looking at.

The same question, asked of the reviewers

Sources. ISO 55001:2024, Asset management, Asset management system, Requirements, second edition, July 2024, prepared by ISO/TC 251, ISO standard 83054, for the structure of Clause 7. ISO 55000:2024, ISO standard 83053, for the principles of asset management and the organisation-wide framing. ISO 55012, people involvement and competence, published in the 2024 family and identified by ISO 55001 as additional guidance on this part of the system. ISO/TS 55010 covers the alignment of financial and non-financial functions. The requirement text of these standards is behind a paywall and is described here rather than reproduced.