Operational control now says life cycle management, which is a larger change than it looks

Ask what operational control means in an asset management system and the answer will describe today.

Work orders raised and closed. Permits issued. Procedures followed. Planned maintenance completed against schedule. Safety systems tested at their intervals. All of it real, all of it necessary, all of it concerned with the current period.

Clause 8.1 of the 2024 edition is titled operational planning and control including life cycle management, and ISO lists the clarification among the main changes from the first edition.

Standards committees do not add clarifications for fun. A clarification is what you write when the text was already capable of the correct reading and nobody was taking it.

What was being missed

The reading being corrected treats operational control as a present-tense discipline. Under it, the asset management system governs how the asset is run, and decisions about what happens to the asset over decades belong somewhere else: to capital planning, to the investment committee, to finance.

That division is not written down anywhere. It arises from organisational structure, and it produces a specific and expensive pattern. The people who know most about the condition of an asset operate it. The people who decide whether to renew, replace or dispose of it sit in a different function, on an annual cycle, working from financial data. The technical knowledge and the decision authority are in different rooms, and the mechanism connecting them is a business case written after the decision to write one has already been taken.

Life cycle management is not a longer version of maintenance planning. It is the question of what should happen to this asset next, asked continuously rather than when something breaks or a budget round arrives.

The sequence the clause is pointing at

Acquire, operate, maintain, renew, replace, dispose. Every asset moves through some version of that, and the interesting property is that the decisions interact.

Deferring a renewal changes the maintenance regime required to keep the asset serviceable in the interim, which changes the operating cost, which changes when replacement becomes cheaper than continuing. Running an asset harder than intended shortens the interval to renewal. Disposing of one asset changes the criticality of the remaining ones and therefore what they should cost to maintain.

Handled as one discipline, those are trade-offs. Handled by separate teams on separate cycles, they are four unrelated budget lines, each optimised locally, and the interactions show up as surprises.

The clearest symptom is an organisation that can tell you its maintenance budget and its capital programme, and cannot tell you what the total cost of owning a given asset class has been over the last five years, because the two numbers live in systems that do not share an asset hierarchy.

Why the two views do not reconcile

Control of change, and what it does not reach

Clause 8.2 covers control of change, and most organisations have a version of it. It is generally attached to physical and operational modification: a management of change procedure, a technical authority, an impact assessment.

It works reasonably well for changes that present as changes. Its weakness is definitional rather than procedural. It can only govern what somebody classified as a change, and a great deal of consequential alteration arrives classified as something else. A deferral is not a change. A temporary arrangement is not a change. An operating regime adjusted to accommodate a fault is not a change until somebody decides it is permanent, which nobody ever does explicitly.

There is also a boundary worth being precise about, because the 2024 edition drew it. Clause 8.2 governs changes to assets and to the delivery of asset management activities. Clause 6.3, planning of changes, is new and sits upstream, governing changes to the asset management system itself. Reorganisations, system replacements, outsourcing decisions and operating model changes belong to 6.3, and almost nowhere are they assessed as changes to anything.

The clause almost nobody has

What examining this looks like

Three questions, and the first is the one that usually settles it.

Who decides when an asset is renewed, and what do they look at? Where the answer is a capital planning function working from age and financial data, the organisation is running life cycle decisions on proxies. Age is a poor predictor of condition and everybody in maintenance knows it.

Can the organisation state the total cost of ownership for one asset class over five years? Not estimate it. Produce it, from records. The inability is common and it is the practical consequence of the two views never having been reconciled.

Is deferred maintenance quantified, and does it appear anywhere the board sees? Deferral is the most frequently used lever in an asset-owning organisation and the least frequently recorded. It creates a liability that accrues silently, and where nobody has put a number on it, the organisation is carrying an obligation that appears in no account.

The regional shape of this

Organisations in this region are arriving at life cycle management from an unusual direction and mostly without noticing.

A great deal of the asset base is young. Assets delivered in the last decade are not yet generating the renewal decisions that force an organisation to build this capability, and youth is easily mistaken for good management. The maintenance regimes currently in force are largely inherited from manufacturer recommendations, which are conservative by design and untested against observed performance because there is not yet enough observed performance to test them with.

That is a genuine window. An organisation that starts collecting condition and cost data now, against an asset hierarchy that finance and engineering share, will have the evidence base when the renewal decisions arrive. One that starts when the first major renewal is due will be making a multi-billion decision on manufacturer defaults and professional judgement.

The framework for this stage sets out the domains, and the predictive action question is where this leads next.

Sources. ISO 55001:2024, second edition, July 2024, ISO standard 83054, Clause 8.1 on operational planning and control including life cycle management, Clause 8.2 on control of change and Clause 6.3 on planning of changes. ISO's list of main changes, including the clarification that operational planning and control includes life cycle management, is published in the foreword. ISO 55000:2024, ISO standard 83053, which gives value and alignment among the three principles. ISO/TS 55010 on the alignment of financial and non-financial functions. Standards published behind a paywall are cited without a link.