Choose Asset Management Software That Actually Helps Crews, Engineers and Finance
Water utilities do not need another pretty database. They need a system that knows where assets are, what condition they are in, what work was done, what risk is rising, and which mains, valves, pumps, meters, tanks and plants should be funded next.
This 2026 guide is written for utility managers, public works directors, engineers, GIS teams, operators, finance staff and field supervisors who need a practical buying checklist — not generic software marketing.
Quick Answer: What Should Water Utility Asset Management Software Do?
| Searcher intent | Direct answer | Best software capability | Do not buy until you confirm |
|---|---|---|---|
| “Best water utility asset management software” | The best system depends on your GIS maturity, crew size, plant assets, field workflows, integrations and budget. | GIS + work orders + mobile + risk scoring + lifecycle planning. | Whether it handles both linear and vertical assets. |
| “CMMS vs EAM for water utilities” | CMMS focuses on maintenance/work orders. EAM adds asset lifecycle, risk, cost, replacement and capital planning. | EAM if you need CIP and risk decisions; CMMS if you mainly need work order control. | Do not buy a CMMS and expect it to solve capital planning by default. |
| “GIS asset management for water” | GIS-centric systems use map assets as the system of record or tightly sync with GIS. | ArcGIS/Utility Network integration, map-based work, valve isolation, hydrant inspections. | Whether edits sync both ways or create duplicate asset records. |
| “Small utility asset management software” | Start with inventory, condition, criticality, maintenance schedule and financial plan before buying complex software. | Simple cloud asset register, mobile inspections, preventive maintenance, exportable reports. | Whether staff can maintain data after consultant setup ends. |
| “AI predictive maintenance for water utilities” | Useful only if you have reliable history, failure codes, asset attributes, SCADA/AMI/leak data and business rules. | Risk modeling, anomaly detection, break prediction, prioritized renewal lists. | Ask for explainable scoring, not black-box “AI” claims. |
Buying rule: choose the software around your actual work: valve turns, hydrant flushing, leak repairs, meter swaps, pump maintenance, sewer cleaning, lift station PMs, CCTV defects, 811 locates, customer complaints, emergency response and CIP planning.
Must-Have Features for Water Utility Asset Management Software
GIS asset registry
Pipes, valves, hydrants, meters, tanks, pumps, stations, manholes, mains, laterals and plants tied to maps.
Work orders
Corrective work, preventive maintenance, emergency repairs, service requests, crew assignment and closeout.
Mobile field app
Offline maps, photos, forms, inspection checklists, signatures, barcode/QR, GPS and real-time updates.
Risk scoring
Likelihood of failure, consequence of failure, criticality, condition, remaining useful life and business risk.
| Feature | What it should do | Water utility example | RFP wording |
|---|---|---|---|
| Asset hierarchy | Group systems, facilities, zones, assets, components and child assets. | Treatment plant → pump station → pump → motor → VFD. | “Show how parent-child assets are modeled and reported.” |
| Linear asset support | Track pipes by segment, material, diameter, install date, pressure zone and location. | Cast iron main with break history and valve isolation zone. | “Support linear referencing or GIS-based pipe segmentation.” |
| Vertical asset support | Manage mechanical/electrical/process assets at plants, wells, tanks and stations. | Blowers, pumps, valves, generators, chemical feed equipment. | “Support facility equipment PMs, parts, labor and condition.” |
| Preventive maintenance | Generate work based on time, meter reading, condition, events or usage. | Annual valve exercising, quarterly generator run, hydrant flushing route. | “Trigger PMs by calendar, runtime, inspection result and condition threshold.” |
| Inspection forms | Configurable checklists with required fields, photos, defects and pass/fail logic. | Hydrant inspection, pump station checklist, manhole inspection. | “Demonstrate mobile inspection creation without custom code.” |
| Service requests | Convert citizen/customer reports into trackable work orders. | No water, leak in street, sewer odor, low pressure, meter box damage. | “Show request-to-work-order workflow and customer communication.” |
| Inventory and parts | Track warehouse, truck stock, parts used, reorder points and job cost. | Meter boxes, clamps, valves, hydrant kits, pumps, seals. | “Tie parts usage to work orders and asset lifecycle cost.” |
| Capital planning | Rank assets for renewal and export CIP scenarios. | Replace mains by risk score, break history and critical customers. | “Provide 5-, 10- and 20-year renewal scenario reports.” |
| Compliance evidence | Store inspection records, maintenance history and reportable events. | Backflow checks, hydrant flushing, wastewater PM, corrective action logs. | “Produce audit-ready history by asset and date range.” |
Assets the Software Must Handle for a Real Water Utility
Water distribution
- Water mains and service lines.
- Valves and valve boxes.
- Hydrants and flushing points.
- Meters, AMI endpoints and meter boxes.
- Pressure zones, PRVs and backflow assemblies.
Wastewater / sewer
- Gravity mains and force mains.
- Manholes and cleanouts.
- Lift stations, pumps and generators.
- CCTV inspections and defect codes.
- FOG, odor, overflow and cleaning history.
Facilities and plants
- Treatment plant process assets.
- Wells, intakes, tanks and reservoirs.
- Electrical, motors, VFDs and SCADA panels.
- Chemical feed, blowers, filters and basins.
- Buildings, fleet, tools and safety equipment.
Reality check: many utilities fail software projects because the system only models pipes on a map or only models plant equipment in a maintenance system. Water utilities usually need both.
2026 Water Utility Software Scorecard
Use this scorecard before demos. Give every vendor a 0-5 score. A high demo score is not enough if field crews, GIS, finance and operations cannot use the system every day.
| Category | Weight | What a 5/5 looks like | Red flag |
|---|---|---|---|
| GIS integration | 15% | Uses authoritative GIS, supports map-based work, syncs attributes and prevents duplicate asset records. | “GIS export/import” only, with manual spreadsheet updates. |
| Water-specific asset model | 12% | Supports mains, valves, hydrants, meters, stations, manholes, pumps, treatment equipment and zones. | Generic asset fields with no water/wastewater templates. |
| Mobile field usability | 12% | Offline maps, inspections, photos, GPS, parts, labor, safety notes and fast closeout. | Crew must return to office to finish work orders. |
| Work management | 12% | Service request to work order to schedule to closeout to cost history. | Work order screen is separate from asset history. |
| Risk and condition scoring | 10% | Configurable condition, failure likelihood, consequence and business-risk scoring. | Only shows age or last inspection date. |
| Capital planning | 10% | Turns risk, cost and remaining life into renewal scenarios and CIP lists. | No scenario planning or budget export. |
| Integrations | 9% | Works with GIS, utility billing/CIS, SCADA, AMI, finance/ERP, permitting, 811 and document systems. | Integration depends on custom one-off scripts only. |
| Reporting and dashboards | 8% | Dashboards for backlog, PM compliance, breaks, leaks, CCTV defects, high-risk assets and cost. | Reports require vendor support for every change. |
| Security and audit | 7% | Roles, permissions, audit trail, SSO, MFA, data retention and export options. | No clear data ownership or export language. |
| Implementation fit | 5% | Clear migration, training, governance, pilot and post-go-live plan. | Vendor says “just upload your spreadsheet.” |
Vendor Fit: Which Type of Platform Should You Shortlist?
This is not a paid ranking. Use the fit matrix to decide what kind of platform to evaluate, then verify details in live demos and official contracts.
| Platform / category | Best fit | Officially highlighted strengths | Ask before shortlisting |
|---|---|---|---|
| Trimble Cityworks / Unity Maintain | Utilities and local governments that want GIS-centric EAM with strong work management. | Trimble describes Cityworks as GIS-centric asset management for utilities, municipalities and infrastructure, and Unity Maintain as EAM built on Cityworks, AgileAssets and Unity Work Management capabilities. | Which modules are included? Is your deployment Cityworks, Unity Maintain, Respond, Operational Insights, Storeroom or a mix? |
| OpenGov Enterprise Asset Management / Cartegraph | Public works and utilities wanting cloud EAM, Esri map integration, work orders, dashboards and capital planning in a government platform. | OpenGov highlights Esri GIS integration, asset records, work planning, inventory/parts, proactive maintenance, dashboards and government platform connections. | Which water/wastewater templates are included? What is the migration path from spreadsheets or legacy Cartegraph? |
| Esri ArcGIS Utility Network | Utilities whose GIS is the authoritative network model and need detailed connectivity, tracing and operational network behavior. | Esri describes Utility Network as a framework for modeling pipes, valves, devices, zones, connectivity, flow and how events affect the network. | Do you need an EAM/CMMS on top, or will ArcGIS apps handle the work workflow? |
| KloudGin EAM / FSM / CWM | Utilities wanting mobile-first unified asset, field service and construction work management. | KloudGin describes a cloud-native, mobile-first platform for utility EAM, FSM and construction work, including linear and vertical assets, Esri GIS and predictive maintenance capabilities. | How does it integrate with your existing GIS, CIS, ERP, SCADA and field devices? |
| General CMMS/EAM platforms | Utilities mainly focused on work orders, PMs, parts and plant/facility assets. | Often strong for mechanical equipment, storeroom, labor, safety and maintenance planning. | Can it handle pipes, valves, hydrants, service areas and GIS without awkward customization? |
| Small-system tools / spreadsheets / EPA resources | Small systems that need structure before buying enterprise software. | EPA resources emphasize inventory, O&M tasks, financial planning and asset management practice; CUPSS is legacy and not actively updated. | Do you need software now, or a clean inventory and asset management plan first? |
Buyer warning: do not compare vendors by feature list alone. Compare one real workflow: a customer calls about low pressure, crews locate valves, work is performed, parts/labor are captured, asset risk changes, and the replacement plan updates.
Official product/research links:
Real Water Utility Workflows the Software Must Prove
Water main break workflow
- Customer call or field report creates service request.
- Map shows main, valves, hydrants and critical customers.
- Work order assigns crew, traffic control, parts and repair task.
- Valve operation and shutdown notes are captured.
- Break reason updates pipe asset history and risk score.
- Repair cost flows into lifecycle and CIP reporting.
Hydrant inspection workflow
- Seasonal inspection route generated by district.
- Mobile form captures flow, caps, paint, clearance and defects.
- Photo and GPS update asset record.
- Failed inspection triggers repair work order.
- Inspection history remains visible on the map.
- Dashboard shows completion by zone.
Pump station PM workflow
- Calendar or runtime triggers PM.
- Checklist includes pump, motor, generator, alarms and wet well.
- Parts and labor are charged to equipment.
- Defects create corrective work.
- Condition score updates replacement forecast.
Sewer CCTV workflow
- CCTV inspection is attached to pipe segment.
- Defect codes and severity update condition.
- Cleaning or repair work is scheduled.
- High-risk segments flow into renewal plan.
- Overflow history remains linked to asset.
Integrations That Matter in 2026
| Integration | Why it matters | Ask the vendor |
|---|---|---|
| GIS / ArcGIS / Utility Network | Network assets, maps, tracing, zones and field location accuracy. | “Is GIS the source of truth? How are edits synchronized and audited?” |
| Utility billing / CIS | Customer calls, meter swaps, service requests and shutoff/reconnect workflows. | “Can a billing complaint create a work order tied to service address?” |
| AMI / meter data | High usage, continuous consumption, leak alerts and meter replacement planning. | “Can AMI alerts trigger service requests or inspections?” |
| SCADA / historian | Runtime, alarms, pressure, pump starts and plant/station condition signals. | “Can runtime or alarm thresholds trigger PM/corrective work?” |
| ERP / finance | Labor, materials, purchase orders, budgets, depreciation and CIP. | “How do costs flow from work orders to finance and capital reports?” |
| Permitting / development | New mains, taps, meters, as-builts and construction handoff. | “How do new assets move from design/construction into operations?” |
| 811 / locate requests | Damage prevention, utility markings and response tracking. | “Can 811 tickets automatically create locate work orders?” |
| Document management | As-builts, O&M manuals, photos, warranties, inspections and compliance records. | “Are documents searchable from the asset and the work order?” |
Data rule: integrations should reduce duplicate entry. If crews must update GIS, billing, work orders and spreadsheets separately, the “new software” will become another silo.
Implementation Plan: 90 Days to First Value
Clean the asset inventory before configuration
Identify required fields: asset ID, type, location, install year, material, size, condition, criticality, service area, replacement cost, owner and data source confidence.
Pick 3 pilot workflows
Start with high-value workflows such as hydrant inspections, valve exercising, pump station PMs, water main breaks, sewer cleaning or meter replacements.
Configure field forms with crews, not only managers
Operators should test mobile screens, offline maps, required fields, photos, parts, safety notes and closeout steps before go-live.
Build dashboards that supervisors actually use
Start with backlog, overdue PMs, breaks by pipe material, leak repairs, crew workload, inspection completion, high-risk assets and cost by asset class.
Connect asset history to budget decisions
Use condition, failure history, consequence and replacement cost to create a renewal list that finance and leadership can understand.
| Phase | Deliverable | Success measure |
|---|---|---|
| Days 1-30 | Asset data audit, GIS/ERP/billing integration review, pilot workflow selection. | Data gaps and ownership assigned. |
| Days 31-60 | Forms, mobile app, roles, PM schedules, basic dashboards and pilot training. | Crew can complete work order in field without duplicate paper. |
| Days 61-90 | Pilot go-live, data corrections, reporting, cost tracking, backlog review. | Supervisor uses dashboard to assign work and close backlog. |
| After 90 days | Risk scoring, capital planning, integrations and broader rollout. | Asset history influences budget and replacement decisions. |
RFP Questions That Reveal Weak Software Fast
GIS and asset data
- Show a pipe, valve, hydrant, meter, manhole and pump asset record.
- Explain GIS sync, edit ownership and conflict resolution.
- Show asset history from map click to work orders to inspections.
- Show how retired/replaced assets remain in history.
Field work
- Show offline inspection in a no-signal area.
- Close a work order with labor, parts, photos and notes.
- Create follow-up corrective work from a failed inspection.
- Reassign work by map area and crew capacity.
Risk and capital planning
- Show likelihood and consequence of failure configuration.
- Build a replacement list for mains by risk and budget.
- Export a 5-year CIP scenario.
- Explain how scores can be audited and changed.
Security and ownership
- Who owns the data?
- How do we export all records?
- Is SSO/MFA supported?
- What audit trail exists for edits, deletes and approvals?
Pricing Traps and Budget Items to Ask About
| Cost item | Why it matters | Question to ask |
|---|---|---|
| Named users vs field users | Field crews, supervisors, GIS, finance and contractors may need different licenses. | “How many users are included by role?” |
| Mobile app | Some vendors price mobile separately or limit offline access. | “Is offline mobile included for all field users?” |
| GIS integration | Can be included, add-on or consulting-heavy. | “Is Esri/ArcGIS integration included at our tier?” |
| Data migration | Old spreadsheets, GIS, CMMS, paper maps and CAD/as-builts need cleanup. | “How many data sources are included in implementation?” |
| Forms and workflows | Configuration can become expensive if every change needs vendor services. | “Can staff build inspection forms and dashboards without custom code?” |
| Integrations | Billing, ERP, SCADA, AMI and permitting connections can drive cost. | “What integrations are standard, API-based or custom?” |
| Reporting | Leadership needs reports without waiting on vendor support. | “Can we build reports and export raw data ourselves?” |
| Storage | Photos, CCTV videos, as-builts and documents can grow quickly. | “What storage limits and overage fees apply?” |
| Training and adoption | Software fails when crews are not trained on field workflows. | “How many field training sessions and post-go-live hours are included?” |
| Contract exit | Public agencies need long-term access to records. | “What does full data export look like if we leave?” |
Budget warning: the software subscription is only part of the cost. Data cleanup, GIS alignment, mobile devices, integration, staff training, consultant time and change management often decide whether the project succeeds.
Small Utility Path: Do This Before Buying Enterprise Software
Minimum asset inventory
- Asset ID and type.
- Location or map reference.
- Install year or estimated age.
- Material, size and capacity.
- Condition and data confidence.
Minimum maintenance plan
- Recurring tasks by asset class.
- Inspection frequency.
- Emergency repair history.
- Parts and labor tracking.
- Backlog and overdue work.
Minimum financial plan
- Replacement cost by asset class.
- Expected useful life.
- Criticality ranking.
- 5- and 10-year renewal list.
- Grant/loan/rate impact notes.
EPA note: CUPSS is a legacy EPA tool and is not being updated, so small utilities should treat it as a learning/reference option, not automatically as the best modern software path.
Official planning resources:
Common Mistakes That Make Asset Software Fail
| Mistake | Why it hurts | Better approach |
|---|---|---|
| Buying before cleaning asset data | Bad data becomes expensive bad data in a new interface. | Audit asset classes, IDs, locations, duplicates and missing fields first. |
| Ignoring field crews | Crews keep using paper if the mobile app slows them down. | Let operators test field forms before go-live. |
| Making GIS and EAM separate truths | Asset location, condition and work history drift apart. | Define the system of record and sync rules. |
| Tracking work but not cost | Finance cannot prove replacement need or rate impact. | Capture labor, parts, contractor and equipment cost by asset. |
| Using age only for replacement | Old does not always mean high risk; newer assets can fail too. | Use condition, break history, consequence, soil, pressure and critical customers. |
| Over-customizing early | Launch slows and upgrades become painful. | Start with configured workflows, then customize only where value is proven. |
| No data governance | No one knows who can edit assets, retire records or approve changes. | Create asset data owner, field data rules and monthly cleanup process. |
Water Utility Asset Management Software FAQ
What is water utility asset management software?
It is software used to track water and wastewater assets, work orders, inspections, maintenance, condition, costs, risk and replacement planning for infrastructure such as pipes, valves, hydrants, meters, pumps, tanks, manholes and treatment facilities.
What is the difference between CMMS and EAM?
A CMMS mainly manages maintenance work orders and preventive maintenance. EAM usually includes broader asset lifecycle management, condition, risk, cost history, capital planning and replacement strategy.
Do water utilities need GIS-based asset management?
Most water utilities benefit from GIS-based asset management because pipes, valves, hydrants, service areas, meters and sewer assets are location-driven. The key is making GIS and work history stay synchronized.
Which assets should a water utility track first?
Start with critical and high-work assets: mains, valves, hydrants, meters, tanks, pump stations, lift stations, treatment equipment, manholes, sewer mains, force mains and generators.
What features should small water systems prioritize?
Small systems should prioritize asset inventory, location, condition, criticality, maintenance schedule, work history, replacement cost and a simple 5- to 10-year renewal plan before buying complex enterprise tools.
Is EPA CUPSS still a good asset management software option?
EPA describes CUPSS as a legacy software application that is still available but no longer being updated. It can be useful for learning asset management concepts, but utilities should verify compatibility and compare modern options.
What should be in a water utility asset software RFP?
Include GIS integration, asset classes, mobile workflows, service requests, preventive maintenance, risk scoring, CIP planning, reporting, integrations, security, data migration, training and data-export requirements.
How does asset software help reduce water loss?
It can connect break history, leak repairs, valve condition, pressure zones, meter data, inspections and work orders so utilities can find patterns, prioritize repairs and replace high-risk assets earlier.
Can asset management software predict pipe failures?
Some platforms support predictive or risk-based analytics, but results depend on reliable data: pipe age, material, break history, soil, pressure, diameter, location, repair records and consequence of failure.
Should asset software integrate with SCADA and AMI?
Yes, when possible. SCADA can provide runtime, alarms and pressure signals. AMI can support high-usage and leak detection. The software should turn useful signals into maintenance or inspection workflows.
What is the biggest implementation risk?
The biggest risk is weak data governance. If no one owns asset IDs, GIS edits, condition updates, retired assets, work history and reporting rules, the system becomes unreliable.
How long does implementation take?
A focused pilot can show value in 60 to 90 days, but full EAM implementation with integrations, data cleanup, field rollout and capital planning can take several months or more depending on utility size and data quality.
Is this a software ranking?
No. This is a buyer guide and evaluation framework. Always run demos with your own sample workflows, verify official product capabilities, check references and review contract terms before purchasing.
30-Second Buyer Checklist
Start with work: main breaks, valve turns, hydrants, pump PMs, sewer cleaning, CCTV, meter swaps, 811 and service requests.
Demand proof: vendor must show asset history, GIS sync, mobile offline work, risk scoring, cost tracking and capital planning in one workflow.
Protect your data: define source of truth, export rights, audit trail, roles, SSO/MFA and data retention.
Do not overbuy: small systems may need a clean inventory and asset management plan before enterprise software.
Best final test: can the software help your next budget conversation, not just close work orders?