Operations & Asset Management
The longest stage, and the one nobody planned for.
ISO 55000 defines asset management as the coordinated activity of an organisation to realise value from assets, across the whole life from planning through to disposal. The 2024 revision extends this into digitalisation and data-driven decision-making. Realising value from an asset requires, at minimum, knowing that the asset exists, where it is, what condition it is in and what it costs to keep.
Most organisations emerging from a major delivery programme cannot answer those four questions. They own a great deal and can describe very little of it. This is not incompetence — it is the predictable consequence of an organisation optimised for delivery inheriting an obligation that requires a different discipline entirely.
Everything downstream depends on the asset register, which is why it is the first thing to build and the thing most consistently deferred. Maintenance planning, capital budgeting, financial reporting, compliance and failure analysis all resolve back to the same question: what do we own?
There is usually more than one answer to that question inside the same organisation. Finance keeps a fixed asset register, built for depreciation, valuation and the balance sheet. Operations keeps a technical asset register, built for maintenance, condition and criticality. The two are rarely reconciled, describe the same physical objects at different levels of granularity, and disagree about how many of them exist. Neither is wrong for its own purpose; the organisation simply cannot state a single position on what it owns.
In the public sector this stops being an internal inconvenience and becomes a reporting obligation. The move from cash to accrual accounting under IPSAS requires entities to recognise, tag and value their assets — which means physically finding infrastructure that may never have been recorded, giving it an identity, and putting a number against it. In Saudi Arabia that transition was mandated for government institutions by Royal Decree in December 2016. The accounting question and the engineering question turn out to be the same question, arriving from different directions.
What typically goes wrong
- 01
The asset register is a spreadsheet that one person maintains and nobody audits.
- 02
The fixed asset register and the technical asset register describe the same assets differently, and nobody owns the reconciliation.
- 03
Assets are valued for the balance sheet without ever being physically located, tagged or condition-assessed.
- 04
Condition is assessed once at handover and never again.
- 05
Spatial information is treated as a mapping exercise rather than as the backbone of the register.
- 06
Capital is allocated by advocacy rather than by evidence, because the evidence does not exist.
Questions worth asking
- ?
Can we produce a list of what we own that finance and operations both accept?
- ?
If we had to tag and value every asset for an accrual opening balance, where would we start, and what would we not find?
- ?
What proportion of our assets have a location, a condition and a criticality?
- ?
Which decisions are we currently making without asset information, and what would change if we had it?
- ?
What is the cost of the information we are missing, expressed as risk rather than as a data project?