Public works asset management is harder than utility asset management for a simple reason: a public works director owns everything. Streets, sidewalks, signals, stormwater, bridges, fleet, facilities, parks assets, and in many Oregon and Washington cities the water and sewer systems too. The utility director has one asset class, a rate base and a regulator. The public works director has eight asset classes, a general fund and a council.
This guide is for cities and counties under about 100,000 people who need a program that a small team can actually run, not a 300-page plan that sits on a shelf.
What a Program Has to Produce
Strip away the frameworks and a public works asset management program produces four things:
- A register: what you own, where it is, what it is made of, when it was built and what it would cost to replace.
- A condition and risk picture: which assets are in poor condition, which ones matter most if they fail, and the combination of the two.
- A level of service and a plan: the service the council has agreed to pay for, and the renewal and maintenance program that delivers it over 10 to 20 years.
- A defensible number: the annual investment the plan requires, the gap against the current budget, and what the gap does to condition over time.
Everything else, from ISO 55001 alignment to GASB 34 reporting, is a consequence of having those four things in good order.
Start With the Register, and Let GIS Be the Spine
Most small public works departments already have most of a register. It is spread across a GIS layer, a pavement management spreadsheet, a fleet list, a CMMS that half the crew uses and a set of as-builts in a flat file. The first job is not to buy software; it is to decide that GIS holds the authoritative location and identity of every linear and point asset, and that every other system keys to that ID.
A practical minimum per asset: unique ID, asset class, location, material, size, install year, replacement cost basis, and a condition score with the date and method it was taken. Resist adding fields the crew will never fill in.
Condition and Risk Without a Consultant on Every Asset
Use the condition method each asset class already has. Pavement condition index for streets. PACP coding for sanitary and storm pipe from CCTV. Bridge inspection ratings from the state program. A simple 1 to 5 visual rating for everything else, taken during routine work rather than a separate campaign.
Risk is likelihood of failure multiplied by consequence of failure. Likelihood comes from condition, age and material. Consequence comes from what happens when the asset fails: a collapsed trunk sewer under an arterial is not the same as a cracked sidewalk panel. A 5 by 5 matrix is enough. The point is to rank, not to predict, and to be able to explain every rank to a council member in one sentence.
The Level-of-Service Conversation
This is the step small cities skip, and it is why their plans fail politically. A level of service is a plain statement the council adopts: streets will be kept at an average PCI of 70; sanitary sewer will see no more than two overflows a year; every water main break will be repaired within 24 hours. The plan then shows what each level costs, and what a cheaper level means in condition and risk.
Once the council has chosen a level and seen its price, the annual budget request stops being a negotiation and becomes a reconciliation.
Funding: The Slots Where the Plan Pays Off
In Oregon and Washington, an asset management plan is increasingly a condition of money, not just good practice:
- Clean Water State Revolving Fund loans for treatment works require a fiscal sustainability plan, which is an asset management plan under another name. Oregon DEQ and Washington Ecology both administer this.
- Drinking water loan programs through the Oregon Health Authority and the Washington Department of Health reward, and sometimes require, documented asset management.
- Business Oregon's infrastructure finance programs and Washington's Public Works Board weigh the quality of the capital plan behind an application.
- Rate studies, stormwater utility formation and GASB 34 modified-approach reporting all draw directly on the register and condition data.
Build the plan so that each of these can be produced from it, rather than written separately when the funding window opens.
Keeping It Alive
A plan that is not updated is a plan that is wrong. The program needs a yearly cycle: refresh condition where work was done, re-run the risk ranking, compare planned to actual spend, and brief the council on the trend. If the CMMS feeds condition back into the register as crews work, this is a week of effort, not a quarter.
Where AMP Fits
AMP's asset management consulting covers the register and data readiness, condition assessment including PACP, risk-based prioritization aligned to ISO 55001, level-of-service and renewal planning, CIP prioritization and GASB 34 and 96 support, on the GIS, CMMS and Microsoft 365 tools a city already runs. AMP Insight puts the register, the risk ranking and the capital plan on one screen with the inputs behind every number. We work as a direct consultant or as a subconsultant to your engineer of record.
Practical Takeaways
- Make GIS the authoritative register and key every other system to its IDs.
- Use the condition method each asset class already has; do not invent a new one.
- Rank with a 5 by 5 risk matrix you can explain in one sentence per asset.
- Get the council to adopt a level of service and its price before the next budget cycle.
- Write the plan so that the SRF, loan and rate-study deliverables fall out of it.
- Put the yearly refresh on the calendar now.
Not sure where your program stands? The free project controls maturity model and infrastructure failure analyzer take a few minutes each and give you something to bring to the next staff meeting.
Want a second set of eyes on your program?
A 30-minute conversation with a practitioner. Bring your register and your last budget request.