Water asset management starts with connecting hydrant, valve, and meter records

Water utilities inspect hydrants, valves, and meters constantly, yet these water infrastructure records remain among the hardest to verify. GIS, CMMS, and field inspection software are often implemented separately, leaving records scattered across systems that don’t talk. Connecting those systems into one record keeps condition assessment data current and turns audit requests from a scramble into a routine pull.

Key insights

• Water utilities inspect hydrants, valves, and meters constantly, yet these are the assets they struggle hardest to document and verify.
• GIS, CMMS, and mobile inspection tools are often adopted separately over time, so none share a common asset ID, and records for the same asset scatter across systems that don’t talk to each other.
• When water utility asset records are not readily available, crews end up re-inspecting assets already checked, and field workers build their own workarounds that never make it back into the official systems.
• Hydrants, valves, and meters each carry a different consequence when records fail: ISO ratings, valve reliability, and billing accuracy all depend on evidence a utility can produce on demand.
• Connecting GIS, CMMS, and field capture from all three assets into one record allows compliance status to stay current and keep audits from being a scramble.

The struggle with high-frequency asset records

Water utilities inspect hydrants, valves, and meters more than any other asset they own. Crews check hydrant caps for corrosion, exercise valves before they seize, and read meters to catch leaks early. Yet these are the assets utilities struggle hardest to document.

The inspection happens, and the record scatters across a paper form, a spreadsheet, and a CMMS export nobody opens. Water asset management depends on knowing what got checked, when, and by whom, and most utility asset management software still assumes assets that stay put and follow a fixed schedule.

That mismatch shows up fastest in the field, where a crew checking a hydrant this morning has no way to confirm whether someone already checked it last week. The safest move becomes checking it again, and that habit repeats across a territory hundreds of times a month. Supervisors trying to verify compliance status end up flipping through binders instead of pulling a report, turning what should take five minutes into an afternoon.

Systems that don’t talk to each other cause that breakdown, and utilities feel the cost of it long before an audit ever forces the issue.

Understanding the EPA asset management framework

EPA guidance organizes an asset management plan around practical questions:

• What capital assets do we own, and where are they?
• What condition are they in?
• Which assets are most critical to the target level of service?
• Which operation and maintenance, asset rehabilitation, or pipeline replacement work should happen next?
• What life-cycle costs and funding will those water infrastructure needs require?

Together, these questions support a practical level of service framework that connects asset condition and investment decisions to the service outcomes customers and regulators expect. Over time, standardized condition and maintenance data can also support predictive analytics by revealing recurring defects, failure patterns, and assets approaching repair or replacement.

Why the most-inspected assets end up the hardest to verify

Utilities built their inspection systems one piece at a time, solving whatever problem was most urgent at the time. A GIS platform came first to map every hydrant, valve, and meter across the territory, followed years later by a CMMS built to manage work orders and maintenance schedules. Mobile inspection tools arrived most recently, often chosen by a field supervisor who needed something faster than paper.

Each system solved its own problem well, but none of them shared a common asset ID or a way to reference records in the others. Matching a hydrant inspection history to its GIS location still requires someone to export data from both systems and match entries by hand, asset by asset.

Without that connection, the utility’s asset management plan cannot reliably compare location, work history, condition, criticality, and cost across capital assets. That makes it harder to prioritize repair, asset rehabilitation, or replacement based on actual water infrastructure needs.

Field crews notice that gap faster than anyone, and some build their own fix without waiting on IT. A meter tech spotting a suspicious reading might photograph it and text the image straight to a supervisor, skipping a system that would take longer than the situation calls for. Legacy GIS and CMMS platforms have no way to accept that kind of field input directly, so crews route around them instead of through them.

Those small workarounds accumulate across a territory with dozens of crews, each running its own quiet fix. Every fix lives outside the official systems, so GIS and CMMS never see the corrections crews are actually making in the field. GIS asset management only works when every system reflects the same reality, and a territory full of unofficial fixes guarantees they don’t.

Hydrants, valves, and meters each break differently

The disagreement between systems doesn’t cost every asset the same amount. A hydrant, a valve, and a meter each depend on a slightly different piece of information holding up, and each one fails in its own way when that piece goes missing.

Fire hydrant inspection ties directly to fire code and insurance ratings, so a completed check that cannot be verified can still affect a community’s (and homeowner’s) ISO score. Hydrant flow testing adds another layer of accountability, since flow and pressure readings need to stay traceable over time to catch a main losing capacity before it becomes a fire suppression risk.

Valves carry a quieter but costlier risk. A valve exercising program supports operation and maintenance across a water distribution system. Crews need to confirm that critical valves can open, close, and isolate service areas when needed. The program only holds value when the record shows exactly when crews exercised each valve.

Water meter inspection connects to a different kind of accountability: billing accuracy and early leak detection. A meter that reads wrong for months can result in significant lost revenue, and the inspection record is the only evidence of when the drift started.

Three asset types carry three different consequences. All three share one requirement: a record that holds up the moment someone asks for it.

What fragmented records cost a utility

None of those consequences stay theoretical for long once a record can’t be produced on demand. An ISO rating, a valve’s reliability, and a customer’s bill all depend on evidence a utility can actually pull up, and fragmented systems make that evidence hard to trust.

Crews re-inspect hydrants and valves someone already checked last quarter, because there’s no quick way to confirm the prior visit. Someone calls around, checks whatever field data collection software the last crew used, or digs through a filing cabinet, and none of it gives a fast answer. Supervisors lose hours every month verifying compliance status one asset at a time.

The cost shows up hardest during an audit. Inspection data management becomes a scramble when a state regulator asks for three years of hydrant flow test results within a week. A utility with connected records can pull up that report in an afternoon. A utility relying on paper, spreadsheets, and unconnected apps assigns a staff member to reconstruct that same history by hand, piecing it together from whatever records survived.

The difference between these two utilities comes down to how well their inspection data holds together.

What water utility asset management looks like when it works

Connecting the systems already doing the work solves the disconnect between GIS, CMMS, and field capture. Once they share the same water utilities field data, an inspection stops living in three separate places and becomes one trusted record.

A Field Operations Management (FOM) platform ties GIS and CMMS together at the point of capture. A crew logs an inspection on a mobile app, and that entry pulls the asset’s GIS location and CMMS work order history into the same record, adding condition notes, photos, and flow test results on the spot.

The record becomes visible immediately to the people who need it next. A supervisor checking compliance status pulls up a live record instead of a report someone assembled after the fact. A regulator requesting flow test history gets the same record, with nothing to reconcile and no second copy to track down.

The practical difference shows up in time saved. Pulling a compliance report for any asset, any date range, takes minutes instead of an afternoon spent cross-referencing binders and spreadsheets.

Water asset management depends on connected records, not more of them

Hydrants, valves, and meters will keep generating more inspection data than almost any other asset a utility owns. Volume was never the real issue. The problems came from GIS, CMMS, and field capture staying disconnected, so that data never became one complete, trusted record. 

An ISO rating, a valve’s reliability, and a customer’s bill all rest on the same foundation: a record a utility can produce the moment it’s asked for. Connecting GIS, CMMS, and field capture is what turns that foundation from an occasional scramble into something a utility can count on every day. 

See your hydrant, valve, and meter records in one place

Fulcrum brings hydrant, valve, and meter inspections into one connected record, tying field crews, GIS, and CMMS together from the moment a crew logs an entry. Compliance status stays current automatically, and an audit trail is ready whenever a regulator asks, with no manual reconciliation required.

If your utility is still stitching together paper, spreadsheets, and disconnected systems, request a free custom demo to see Fulcrum in action.