Asset Management for Water & Sewer Utilities

Water and sewer utilities operate the most invisible critical infrastructure in any city. The mains under the street, the lift stations behind the chain-link fence, the manholes nobody notices until something is wrong. The asset management problem in water and sewer is harder than in any other public works division — more assets, more locations, more regulatory oversight, and far less institutional memory once the foreman who knew the system retires.

This article is the practical version of "how to build a water/sewer asset program" for a small-to-mid-sized utility. No GASB 34 essays, no enterprise asset framework theory. Just what to put in the system and why.

The asset classes that matter

You do not need 200 asset categories. You need these, organized in a hierarchy:

• Linear assets: water mains, sewer mains, force mains, laterals, storm drains.
• Point assets on the network: hydrants, valves, manholes, cleanouts, meters, backflow preventers.
• Stations: lift stations, booster stations, pressure-reducing stations, treatment plants.
• Treatment process equipment: pumps, motors, blowers, clarifiers, filters, chemical feed systems.
• Storage: elevated tanks, ground storage, reservoirs.
• Instrumentation: SCADA points, flow meters, pressure transducers.

Every asset belongs to a class. Every class gets a default PM template. Every asset can override the template if needed. That is the entire data model.

Why GIS belongs at the center

Water and sewer assets live on a map. Trying to manage them in a flat list is fighting gravity. The right architecture is:

• ESRI ArcGIS holds the spatial system of record — what is where, in what configuration.
• The CMMS holds the operational system of record — what was done to which asset, when, by whom, for how much.
• The two systems sync bidirectionally. An asset added in GIS appears in the CMMS automatically; a maintenance event added in the CMMS shows on the GIS map automatically.

If the CMMS you are evaluating treats GIS as an export target rather than a peer system, you will spend years working around it. More on what to ask vendors here.

What to capture per asset

Resist the temptation to track 40 fields per asset. Crews will not fill them in, and partial data is worse than no data because it gives false confidence. The minimum viable record:

• Asset ID (matches the GIS feature ID)
• Asset class
• Location (lat/lng or station/offset)
• Install date (or estimated)
• Manufacturer / model / size
• Material (for mains: ductile iron, PVC, AC, cast iron)
• Last condition assessment (date + score)
• QR / barcode tag (for in-field lookup)

Everything else — warranty, contractor, drawings, manuals — is an attachment. Unstructured data attached to a structured record beats structured data nobody fills in.

Required PM and compliance work

Most water and sewer utilities have non-negotiable recurring work driven by regulation. A CMMS earns its keep by making this work auditable. Common examples:

• Hydrant flow testing (annual or biennial, AWWA standards)
• Backflow assembly inspection (annual)
• Valve exercising (annual)
• Lift station preventive maintenance (monthly + quarterly + annual cycles)
• Manhole inspection (varies by jurisdiction)
• SSO reporting (any sanitary sewer overflow, in many states)
• Meter testing and replacement schedules

Every one of these should be a recurring PM template in the CMMS, with completion records that survive personnel changes. That is the audit defense.

The locate ticket workflow

Underground utility damage is the single most expensive avoidable event in this industry. Locate tickets — 811, MissDigg, Utilisync, depending on your state — should flow into the same system as everything else: a ticket arrives, it gets assigned to a locator, the locator marks it complete with photos, and the record is queryable later. If your locate tickets live in a separate inbox from your work orders, you have two systems and one risk.

Capital planning from operational data

The point of an asset registry is not just maintenance. It is to answer the capital question: which $50M of pipe do we need to replace in the next 10 years? A clean operational record gives you the inputs:

• Failure history per pipe segment
• Material and install year (proxy for remaining useful life)
• Customer impact per failure
• Cost per failure (labor, parts, customer notifications, regulatory)

An AI summarization layer on top of that data is starting to produce defensible capital prioritization that is better than the gut-feel approach most utilities still use. More on AI in operations here.

What success looks like in 12 months

1. Every critical asset (every lift station, every hydrant, every backflow assembly) has a record with location, install year, and recent inspection.
2. Every regulatory PM is on a schedule with auto-generated work orders.
3. Every locate ticket is in the same system as work orders.
4. Crews can scan a QR tag in the field and see the full asset history before they touch a tool.
5. You can produce the year's PM-compliance report in five minutes.

None of this requires an enterprise EAM. A modern CMMS with native GIS integration covers it.

---

WorkmanIQ ships bidirectional ESRI ArcGIS integration, locate-ticket workflows, and water/sewer asset templates in the base platform. See the modules →