INFRASTRUCTURE ASSET MANAGEMENT: THE RECORD PROBLEM
Infrastructure asset management depends on knowing what you own, where it is, what has been observed about it and when. Most portfolios struggle not because analysis is weak but because the record is fragmented across inspection reports, spreadsheets and individual memory. A persistent per-asset record with dated evidence is the foundation everything else stands on.
UPDATED 2026-09-01 · WRITTEN FOR: ASSET OWNERS AND MANAGERS IMPROVING PORTFOLIO RECORDS AND PRIORITISATION.
THE PROBLEM IS CONTINUITY, NOT DATA
Most organisations already hold a great deal of asset information. It is scattered across inspection PDFs, consultant reports, maintenance systems and the knowledge of people who have been there a long time. When those people move on, the portfolio effectively loses part of its history.
A persistent record — one object per asset, holding everything observed about it with dates and sources — converts that scattered information into something the organisation owns rather than remembers.
WHAT AN ASSET RECORD SHOULD HOLD
- Identity and precise location, with the boundary or extent it refers to.
- Dated observations, from inspections and from remote sources, each with provenance.
- Change over time — what differs since the last look, and when it appeared.
- Decisions and their reasoning, including deferrals.
- Explicit unknowns: what has not been established and what would establish it.
PRIORITISE ATTENTION, NOT EVERYTHING
No portfolio can inspect everything at the frequency it would like. The realistic aim is to direct limited inspection capacity toward assets where something has changed or where the record is weakest — and to be able to justify that allocation with evidence afterwards.
- Remote observation cannot assess structural or engineering condition; that requires qualified inspection.
- Earth observation coverage depends on third-party sources, revisit intervals and cloud cover.
- Asset records reflect the information supplied and observed; gaps remain gaps.
- AXARA does not provide engineering advice, condition certification or maintenance decisions.
- Persistent asset records that accumulate evidence and reasoning over years.
- AXARA Attention surfaces assets where observed change may warrant a closer look, with the evidence shown.
- A change timeline per asset and per portfolio.
- Explicit known / supported / indicated / unknown status instead of a single condition score.
- Ask AXARA to interrogate the portfolio record, with sources visible.
What is infrastructure asset management?
The coordinated management of physical assets across their life — knowing what exists, understanding its condition and risk, planning inspection and maintenance, and recording decisions.
Can remote data replace physical inspection?
No. Remote observation indicates where and when something changed. Condition assessment remains a qualified human activity.
What is the most common weakness in asset records?
Discontinuity — records that do not survive staff changes, system migrations or consultant handovers, so history has to be rebuilt.
How should inspection frequency be set?
By risk, consequence and evidence, including how long it has been since the asset was last observed and whether anything has changed since.
Does AXARA replace an asset management system?
It provides the persistent record and observed-change intelligence layer. Operational maintenance systems continue to do their own job.