Every asset management plan makes claims. This watermain before that one. This budget year, not the next. Rehabilitate here, replace there.
When council, a regulator or a ratepayer asks why, the plan’s answer is only as good as the chain of evidence underneath it. If the inventory is incomplete, the condition data is scattered across binders, or the “location” of an asset is a line someone drew from memory, the plan’s priorities are opinions with formatting.
Fixing that chain is unglamorous work, and it comes before the plan — not after.
Four inputs, one structure
An asset plan for buried infrastructure draws on four streams of evidence, and they answer different questions:
- Inventory — what do we own?
- Location — where is it, exactly?
- Condition — what state is it in?
- Maintenance history — what has already been done to it?
Each stream can exist and still be useless if they don’t share a structure. A CCTV report that can’t be tied to a specific mapped segment, or a work order filed against “the main on 5th”, breaks the chain at the join. The fix is structural: one asset identity that inventory, mapping, inspection and maintenance records all reference.
Condition scoring you can defend
Condition data earns its place in a plan when it is scored against a published framework rather than local judgment. For sewers, laterals and manholes, NASSCO’s PACP, LACP and MACP coding assigns observed defects a severity grade from 1 to 5. The grade matters less than what it makes possible: two inspections, years apart, by different crews, that can still be compared — and a defensible line between “monitor”, “rehabilitate” and “replace”. Tierra’s inspection work applies these frameworks to produce condition evidence owners can carry into planning.
Tie condition to the location record
A Grade 4 pipe means little if no one is sure which pipe it is. Condition evidence pays off when it lands on a specific asset in a maintained location record — the mapped segment, with its attributes, history and source data. That connection is what turns an inspection report into a planning input: the plan can see not just that something is failing, but where it sits, what feeds it, and what it would disrupt.
Frameworks are references, not badges
ISO 55000 describes what good asset management looks like as a management system, and it is a useful reference for structuring the work. Ontario municipalities also carry a specific obligation: O. Reg. 588/17 requires municipal asset management plans for core infrastructure. Neither document collects your data for you. The evidence chain is what makes any framework’s requirements answerable — the foundation fits into whatever governance and planning process the owner already runs.
Start where risk and data gaps overlap
Few owners can afford to rebuild every dataset at once, and few need to. The practical starting point is the overlap between consequence and ignorance: the systems where failure costs the most and the record says the least. Close that gap first, structure it properly, and each following campaign — inventory, inspection, locate capture — extends a chain that is already holding.
