Water Utility Software Stack: Choose Tools That Actually Run the Utility
Do not buy “water utility software” as one vague product. Break it into jobs: billing, meters, field work, assets, maps, compliance, cybersecurity, customer service, and executive reporting.
Fast Answer: What Software Does a Water Utility Need?
| Utility job | Software category | Must-have outcome | Do not buy unless it can… |
|---|---|---|---|
| Bill customers accurately | CIS / utility billing | Rates, meter reads, payments, adjustments, shutoff/reconnect, deposits, liens, reports. | Handle water, sewer, stormwater, sanitation, tax, fees, owner/tenant rules, and audit history. |
| Serve customers online | Customer portal + payment processor | One-time pay, login, autopay, paperless billing, payment reminders, service requests. | Show posting rules, fees, receipts, accessibility support, and mobile-friendly account access. |
| Manage pipes, valves, pumps, tanks | Asset management / CMMS | Inventory, condition, criticality, maintenance, replacement planning, capital projects. | Link asset ID to GIS location, work history, cost, inspections, and risk score. |
| Dispatch crews | Work order + mobile field app | Leak, meter, valve, hydrant, sewer, lateral, restoration, and inspection tickets. | Work offline, capture photos, timestamps, GPS, materials, labor, and closeout notes. |
| Map the system | GIS utility mapping | Service lines, mains, hydrants, valves, meters, zones, pressure districts, easements. | Share controlled map layers with office, field, engineering, and emergency teams. |
| Operate treatment/distribution | SCADA/HMI + historian | Monitor pumps, tanks, pressure, flow, chemical feed, alarms, and operational trends. | Separate OT from IT, log operator actions, alert properly, and support recovery. |
| Use smart meter data | AMI / AMR / meter data management | Interval reads, leak flags, high-use alerts, route exceptions, tamper flags. | Reconcile reads to billing and flag exceptions before bills go out. |
| Reduce non-revenue water | Water audit + loss analytics | Track apparent loss, real loss, metering errors, unauthorized use, leakage. | Produce repeatable annual water-loss metrics and action lists. |
| Meet regulatory obligations | Compliance / sampling / LIMS / reporting | Sampling schedules, lab results, CCR support, permit reporting, incident records. | Keep evidence, approvals, deadlines, and exportable compliance records. |
| Model the network | Hydraulic model / digital twin | Pressure, flow, water age, fire flow, valve operations, growth planning, emergency scenarios. | Use current GIS, demand, SCADA, and field data—not a stale model. |
Simple rule: a demo dashboard is not enough. Ask whether the software improves billing accuracy, field response, asset life, compliance evidence, cyber resilience, and customer trust.
Water Utility Software Stack: The 10 Core Tools
1. Utility Billing / CIS
- Rate engine for water, sewer, stormwater, sanitation, taxes, fees.
- Meter reads, estimates, adjustments, deposits, late fees, shutoff/reconnect.
- Owner/tenant/account transfer rules.
- Payment posting, refunds, chargebacks, audit trail.
- Customer notices, billing cycles, delinquency queues.
2. Customer Portal
- One-time pay and login pay.
- Autopay, paperless billing, pay-by-text, reminders.
- High-use alerts and leak notifications.
- Start/stop/transfer service forms.
- ADA-friendly, mobile-safe, multilingual support where needed.
3. GIS Utility Map
- Mains, service lines, valves, hydrants, meters, tanks, pump stations.
- Pressure zones, districts, isolation valves, critical customers.
- Lead/copper service line inventory layers if applicable.
- Field edits with approvals.
- Map links inside work orders and asset records.
4. CMMS / Work Orders
- Reactive and preventive maintenance.
- Valve exercising, hydrant flushing, pump PMs, meter swaps.
- Photo, GPS, labor, materials, notes.
- Offline mobile mode.
- Repeat failures and asset cost history.
5. SCADA / HMI / Historian
- Pressure, flow, tank level, pump, valve, chemical feed monitoring.
- Alarm management and escalation.
- Operator action logs.
- Historian trends for operations review.
- Secure OT access and segmented network design.
6. AMI / AMR / MDM
- Interval meter reads.
- Continuous-flow leak flags.
- Tamper and reverse-flow alerts.
- Read validation before billing.
- Meter exchange and route exception workflow.
7. Compliance / LIMS
- Sampling points, schedules, chain of custody.
- Lab results, exceedance flags, corrective action notes.
- CCR/water quality report support.
- Permit, discharge, and regulatory reporting evidence.
- Document retention and approval workflow.
8. Water Loss / NRW
- Production vs billed consumption.
- Real loss and apparent loss tracking.
- Meter under-registration and unauthorized use flags.
- District metered area / zone analytics.
- Annual audit and recovery plan.
9. Hydraulic Model / Digital Twin
- Pressure, flow, fire flow, water age, tank cycling.
- Valve closure and outage simulation.
- Capital planning and growth scenarios.
- SCADA or AMI calibration path.
- Emergency response scenario library.
10. Cybersecurity / Backup Layer
- MFA, role-based access, audit logs.
- Patch and vulnerability management.
- Incident response plan.
- Immutable or offline backups.
- Vendor access control and OT segmentation.
Best Software Stack by Utility Size
| Utility type | Start with | Add next | Avoid this mistake |
|---|---|---|---|
| Very small system | Billing, asset inventory, basic work orders, compliance calendar, backup plan. | Mobile field forms, leak tracking, simple GIS, cybersecurity checklist. | Buying a complex enterprise suite before asset data and billing rules are clean. |
| Small public water system | Asset management, preventive maintenance, billing accuracy, water-loss audit, sampling reminders. | Customer portal, meter route management, mobile work orders, online forms. | Using spreadsheets with no audit trail for critical maintenance and compliance tasks. |
| Medium utility | CIS, GIS, CMMS, AMI/AMR integration, customer portal, reporting dashboards. | Hydraulic modeling, leak analytics, LIMS, procurement/inventory, cybersecurity monitoring. | Letting GIS, billing, meters, and work orders become four separate versions of truth. |
| Large city / regional provider | Integrated CIS, ERP, GIS, CMMS, SCADA, historian, MDM, cybersecurity governance. | Digital twin, advanced analytics, outage/customer notification, capital planning portfolio. | Modernizing the front-end portal while leaving field, OT, and asset data disconnected. |
| Water + wastewater utility | Separate water and sewer assets, pump stations, lift stations, treatment records, discharge/permit tasks. | Odor, overflow, lateral, FOG, industrial pretreatment, lab, and emergency-response workflows. | Using water-only billing/work-order logic that cannot handle sewer operations. |
Must-Have Features in 2026
Billing accuracy
- Rate version history.
- Exception review before bills print.
- High-use and zero-use flags.
- Owner/tenant/service address logic.
- Audit trail for every adjustment.
Field-first operations
- Offline mobile app.
- GIS map on ticket.
- Photo and GPS capture.
- Barcode/QR asset lookup.
- Work history at asset level.
Executive visibility
- NRW / water-loss dashboard.
- Work backlog by crew/type.
- Asset risk heat map.
- Delinquency and collections trend.
- Compliance deadline view.
Interoperability
- API access.
- GIS sync.
- Meter vendor import/export.
- Payment gateway integration.
- SCADA/historian-safe data path.
Security
- MFA and SSO.
- Role-based permissions.
- Vendor remote access logs.
- Backup restore testing.
- Incident-response export.
Customer trust
- Clear bills.
- Leak alerts.
- Outage/service notices.
- Payment confirmation.
- ADA and multilingual-ready portal.
Asset Management Software: What to Capture
Asset software is not only a map. It should answer: what do we own, where is it, what condition is it in, how critical is it, when should it be repaired/replaced, and how will we fund it?
| Asset class | Fields to track | Why it matters |
|---|---|---|
| Mains | Material, diameter, install year, pressure zone, break history, critical customers, isolation valves. | Capital planning, leak risk, replacement priority. |
| Valves | Valve ID, size, type, turns, operating status, last exercised, GPS, zone. | Emergency isolation and maintenance reliability. |
| Hydrants | Flow test, inspection date, condition, color/class, out-of-service status, fire district. | Fire protection and insurance/community safety. |
| Pumps / motors | Runtime, vibration notes, PMs, repair costs, spare parts, criticality. | Preventive maintenance and failure prevention. |
| Tanks / reservoirs | Inspection, coating, level range, mixing, cleaning, structural notes. | Water quality, storage, pressure, capital planning. |
| Meters | Serial, size, install date, read technology, accuracy, exchange cycle, endpoint ID. | Billing accuracy and revenue recovery. |
| Service lines | Public/private material, install year, lead/copper status, customer side records, verification evidence. | Compliance, public health, replacement planning. |
Small-system note: EPA’s CUPSS remains a useful concept reference for asset inventory and planning, but EPA identifies the downloadable software as a legacy tool that may not be compatible with modern operating systems. Use that as a warning: always check support status, updates, backups, and compatibility before adopting any tool.
Cybersecurity Checklist for Water Utility Software
Billing, SCADA, AMI, customer portals, work orders, and GIS all create risk. The software must support safe operations, not just attractive dashboards.
Govern
- Named system owner for each platform.
- Vendor risk review.
- Cyber insurance / legal / procurement alignment.
- Policy for remote access and admin rights.
Identify
- Full inventory of software, servers, cloud apps, OT devices.
- Data classification: billing, PII, operational, compliance.
- Critical process map: treatment, distribution, billing, dispatch.
Protect
- MFA for admin and remote access.
- Least privilege roles.
- Network segmentation between IT and OT.
- Patch window and change approval.
Detect
- Login anomaly alerts.
- SCADA and remote-access monitoring.
- Audit logs retained and reviewed.
- Vendor activity logs.
Respond
- Incident response playbook.
- Contacts for vendor, IT, OT, management, regulator.
- Manual operations fallback.
- Customer communication template.
Recover
- Offline or immutable backups.
- Restore tests, not just backup reports.
- RTO/RPO by system.
- Clean rebuild documentation.
Non-negotiable: never allow internet-exposed SCADA/HMI, shared admin passwords, unlogged vendor remote access, unsupported operating systems, or backups that have never been restored in a test.
Integration Map: What Must Talk to What?
| Source system | Target system | Data exchanged | Failure symptom |
|---|---|---|---|
| AMI / AMR | Billing / CIS | Meter reads, exceptions, leak flags, tamper flags. | Bad bills, missing reads, too many estimates, customer complaints. |
| Billing / CIS | Customer portal | Balance, due date, account status, payment confirmation, notices. | Customers see wrong balance or cannot trust online payment status. |
| GIS | CMMS / work orders | Asset ID, location, map layer, isolation zone, service line. | Crews work from screenshots or paper maps. |
| SCADA historian | Engineering analytics / model | Flow, pressure, tank levels, pump status, alarms. | Hydraulic model is stale and not trusted by operations. |
| Compliance / LIMS | Document management / reporting | Sampling, lab results, chain of custody, report approvals. | Evidence scattered across email, spreadsheets, and shared drives. |
| Finance / ERP | CMMS / procurement | Inventory, labor cost, materials, purchase orders, project cost. | Asset lifecycle costs cannot be defended in rate or capital planning. |
Implementation Plan: 90 Days to a Safer Selection
List every current system
Include billing, payment, meter reading, GIS, work orders, SCADA, spreadsheets, access databases, paper forms, lab records, and shared drives.
Map 12 real workflows
Use actual tasks: new account, final bill, high bill, leak ticket, hydrant inspection, meter exchange, main break, sampling result, valve exercise, shutoff, customer complaint, and emergency notice.
Clean master data before migration
Standardize account IDs, service addresses, meter IDs, asset IDs, GIS IDs, location names, rate codes, and status values.
Run side-by-side tests
Test a billing cycle, meter import, payment posting, work order closeout, mobile offline use, admin permissions, and backup restore.
Train by job role
Billing clerks, customer service, meter techs, field crews, supervisors, finance, engineers, operators, and managers need different workflows—not one generic training call.
Go live with a rollback plan
Define cutover weekend, freeze window, data validation, customer communication, issue log, vendor support hours, and rollback conditions.
Water Utility Software Selection Checklist
Ask before the demo
- Which utility size and service types do you support?
- Can we see a water/sewer/stormwater billing example?
- Which meter vendors and payment processors are already integrated?
- Can field crews work offline?
- How are rate changes audited?
- Can we export all data if we leave?
Ask during the demo
- Show a high bill from meter read to customer explanation.
- Show a main break work order from call to closeout.
- Show a billing adjustment approval path.
- Show GIS asset history inside a work order.
- Show MFA, roles, audit logs, and vendor access controls.
- Show a backup restore report or recovery test process.
Red flags
- “We can customize anything” but no fixed implementation plan.
- No utility-specific rate engine.
- No clean export rights.
- No offline mobile workflow.
- No MFA or role-based access.
- SCADA integration without security architecture discussion.
Contract protections
- Data ownership and export format.
- Implementation milestones and acceptance tests.
- Uptime/support commitments.
- Security responsibilities.
- Backup/restore obligations.
- Pricing for integrations, storage, users, mobile, API, and training.
Vendor Scorecard: Copy This Into Your RFP
| Category | Weight | What earns a high score | Proof to request |
|---|---|---|---|
| Utility fit | 15% | Water/sewer/stormwater workflows match your real operation. | Demo using your scenarios and sample bill/rate rules. |
| Billing accuracy | 15% | Rate engine, adjustments, deposits, notices, audit trail, exceptions. | Parallel bill test with your historical data. |
| Field operations | 12% | Mobile, offline, GIS-linked work orders, photos, materials, labor. | Crew demo on phone/tablet with no perfect Wi-Fi assumption. |
| GIS / asset depth | 12% | Asset inventory, condition, criticality, maintenance history, capital planning. | Asset lifecycle report and map-linked work history. |
| Integration | 12% | Open API, meter/billing/payment/GIS/ERP compatibility. | Named integrations, data dictionary, API docs. |
| Cybersecurity | 14% | MFA, SSO, RBAC, logs, vulnerability management, backups, vendor access control. | SOC report if available, security questionnaire, incident process. |
| Reporting | 8% | Operational KPIs, compliance evidence, financial reports, water-loss dashboard. | Sample dashboards and custom report process. |
| Implementation risk | 7% | Clear timeline, migration plan, training, acceptance testing, cutover support. | Project plan, data templates, references. |
| Total cost | 5% | Transparent pricing across users, modules, integrations, storage, support. | Five-year cost table with assumptions. |
Practical scoring tip: do not let the lowest subscription price win if data migration, integrations, mobile users, reporting, and support are priced separately.
Questions to Ask Vendors
| Area | Question | Good answer sounds like |
|---|---|---|
| Billing | Can you show a rate change with audit history? | Yes, with effective dates, approver, version, test bills, and rollback. |
| Meters | How do you handle missing, estimated, duplicate, or abnormal reads? | Exception queue before billing, configurable thresholds, and read source history. |
| Customer portal | What does the customer see after payment? | Receipt, confirmation, balance, posting status, fees, and support route. |
| Field app | What happens when crews have no signal? | Offline work orders, cached maps/assets, queued sync, conflict handling. |
| GIS | Which system owns asset IDs? | Clear master-data ownership and sync rules. |
| SCADA/OT | How do you prevent unsafe integration? | Read-only data path where possible, segmentation, no shared admin accounts, vendor access logging. |
| Security | Can we enforce MFA and role-based access? | Yes, with SSO option, privileged roles, audit log export, and review reports. |
| Exit plan | How do we get our data if we leave? | Documented export formats, timing, costs, and full data dictionary. |
AI and Automation: Useful, But Keep Humans in Control
Good AI use cases
- High-use anomaly detection.
- Leak probability scoring.
- Work-order triage.
- Customer-service summaries.
- Asset risk prioritization.
Use with caution
- Rate adjustment suggestions.
- Shutoff prioritization.
- Operational recommendations.
- Chemical-feed or pump-control suggestions.
- Customer-facing answers about safety.
Do not automate blindly
- SCADA control actions.
- Public health notices.
- Regulatory submissions.
- Disconnection decisions.
- Emergency response commands.
AI rule for utilities: AI may rank, flag, summarize, and draft. It should not secretly control pumps, chemicals, shutoffs, compliance statements, or public-health messages without trained human review.
Official and Authority Resources
Water Utility Software FAQ
What is water utility software?
Water utility software is a stack of tools used to manage billing, meters, customer service, work orders, assets, GIS maps, SCADA data, compliance, reporting, and cybersecurity for drinking water and wastewater operations.
What is the most important water utility software module?
For most utilities, billing/CIS and asset/work-order management are the first priorities because they affect cash flow, customer trust, maintenance, and field response.
Do small water systems need enterprise software?
Not always. Small systems often need clean billing, asset inventory, preventive maintenance, compliance reminders, backups, and cybersecurity basics before buying a full enterprise suite.
What is CIS in water utilities?
CIS means Customer Information System. It manages accounts, rates, bills, payments, customer details, service orders, adjustments, delinquency, and account history.
What is CMMS for a water utility?
CMMS means Computerized Maintenance Management System. It manages work orders, preventive maintenance, asset history, labor, materials, inspections, and repairs.
What is AMI or MDM?
AMI is Advanced Metering Infrastructure. MDM is Meter Data Management. Together they collect, validate, analyze, and route meter data into billing, leak alerts, and customer portals.
Should SCADA connect directly to billing or the customer portal?
No. Operational technology should be protected. If SCADA data is used elsewhere, design a secure, controlled, preferably read-only data path with segmentation and logging.
What is EPANET used for?
EPANET is EPA-supported software for water distribution hydraulic and water-quality modeling. Utilities and engineers use modeling to understand pressure, flow, tanks, pumps, water age, and operational scenarios.
What security features should water utility software have?
Look for MFA, SSO, role-based access, audit logs, encryption, vulnerability management, backups, incident-response support, vendor access controls, and exportable logs.
What are water utility software red flags?
Red flags include no audit trail, no data export, no MFA, no offline field mode, weak billing-rate logic, vague integration promises, unsupported operating systems, and no tested backup/restore process.
How should a utility compare vendors?
Use real workflows, not generic demos: high bill, new account, leak ticket, meter exchange, rate change, work order, outage notice, payment posting, and compliance report.
What is the best software for non-revenue water?
The best approach combines production data, billing data, meter accuracy, leak detection, zone/pressure data, and an annual water audit process such as AWWA’s water-loss methodology.
How long does implementation take?
Small modules can go live in weeks, but full CIS/GIS/CMMS/AMI implementations often take months because data cleanup, integrations, testing, training, and billing validation are critical.
Should a water utility use AI software?
AI can help with anomaly detection, work-order triage, leak scoring, and summaries. It should not secretly control treatment, pumps, chemicals, shutoffs, compliance submissions, or public-health notices.
30-Second Buyer Checklist
Start with workflows: billing, meter read, leak, main break, work order, sampling, customer portal, and emergency response.
Demand proof: utility-specific demo, migration plan, integration map, cyber controls, export rights, and restore-tested backups.
Score the stack: CIS, portal, GIS, CMMS, AMI/MDM, SCADA/historian, compliance, water loss, hydraulic model, cybersecurity.
Avoid fake modernization: a pretty dashboard does not fix bad data, weak security, broken integrations, or untrusted bills.