Choosing a SCADA System That Fits a Small Utility
A supervisory control and data acquisition system can give a small water or wastewater utility better visibility, faster response times, and more reliable records. It can also become an expensive source of frustration if the platform is oversized, difficult to maintain, or poorly matched to the utility’s staffing and operational needs.
The right selection process starts with the utility’s actual processes rather than a vendor’s feature list. Pump stations, treatment facilities, storage tanks, lift stations, wells, and remote sites each create different requirements for communications, alarming, control logic, reporting, and cybersecurity.
A practical evaluation should account for the full lifecycle. Hardware, software licenses, cellular service, integration, operator training, support, upgrades, and replacement costs all influence the value of a SCADA system. The best choice is usually a platform that can be operated confidently by the people who will use it every day.
Define Operational Needs Before Reviewing Products
Begin by documenting the decisions operators must make during a normal shift and during abnormal conditions. Identify which measurements require continuous monitoring, which equipment needs remote control, and which events require an immediate alarm. Typical points include flow, level, pressure, turbidity, chlorine residual, motor status, valve position, and power quality.
Separate critical controls from information that is useful but not time-sensitive. A high wet-well level may require an urgent notification, while a weekly pump runtime report can be generated through scheduled analytics. This distinction helps prevent alarm overload and keeps the system focused on protecting public health, equipment, compliance, and service continuity.
Include future needs without purchasing capabilities that will sit unused. A utility may eventually add a new well, advanced metering, energy monitoring, or remote laboratory data. A scalable architecture should support these additions through standard interfaces, clear licensing, and available network capacity rather than requiring a complete replacement.
Match Architecture To Sites And Staffing
Small utilities often operate geographically dispersed assets with limited information technology support. A system may combine programmable logic controllers, remote terminal units, edge devices, radio links, cellular connections, and a central human-machine interface. Decide which functions must continue locally when communications fail. Basic pump sequencing, level protection, and fail-safe shutdowns should generally remain available at the site.
Cloud-hosted SCADA can reduce server maintenance and make access easier across multiple locations, while an on-premises deployment may provide greater control over data storage and network segmentation. Hybrid models are also common. The important issue is clear responsibility for backups, patches, system availability, remote access, and incident response.
Assess the knowledge available inside the utility. If the organization has one controls specialist or relies on outside contractors, a platform with strong documentation, intuitive configuration tools, and broad integrator support may be preferable to a highly customized solution. Vendor demonstrations should include realistic tasks such as acknowledging an alarm, reviewing a trend, changing a setpoint, and adding a new instrument.
Compare Capabilities And Total Cost
A useful procurement comparison looks beyond screen design. Evaluate how each candidate handles historical data, alarm management, mobile access, role-based permissions, audit trails, reporting, redundancy, and integration with laboratory information systems or computerized maintenance management systems. Confirm whether data can be exported in usable formats and whether the utility retains ownership of its historical records.
Licensing deserves close attention. Vendors may charge by tag count, user count, site, server, connection, or software module. A low initial price can become costly when mobile access, advanced alarming, historian capacity, or development tools are added. Request a five- to ten-year cost model that includes implementation, training, support, cybersecurity services, hardware refreshes, and emergency assistance.
| Evaluation Area | Questions To Ask | Evidence To Request |
|---|---|---|
| Reliability | What happens if the central server or network connection fails? | Failover design and recovery procedures |
| Usability | Can operators find alarms, trends, and equipment status quickly? | Scenario-based demonstration |
| Scalability | Can new sites and instruments be added without major rework? | Expansion pricing and reference architecture |
| Security | How are accounts, updates, remote access, and logs managed? | Security documentation and patch policy |
| Ownership | Can the utility access and export its data? | Contract language and sample exports |
| Support | Who responds during a critical outage? | Service-level terms and support contacts |
| Cost | What expenses occur after implementation? | Multi-year total cost of ownership |
Use the same scripted scenarios with every vendor so comparisons remain fair. Ask each bidder to show how the system responds to a communications outage, a bad sensor value, a failed pump, and a simultaneous alarm event. References from utilities of similar size are especially valuable because large agencies may have dedicated staff and budgets that change the operating experience.
Treat Cybersecurity And Resilience As Core Requirements
Cybersecurity should be designed into the control system rather than added after installation. Require unique user accounts, multifactor authentication where appropriate, role-based permissions, encrypted remote connections, network segmentation, secure backups, and a documented patching process. Administrative access should be limited and reviewed regularly.
The utility should also understand its dependence on communications providers and electric power. Cellular or radio systems need coverage testing and a plan for outages. Uninterruptible power supplies, generator connections, local control modes, and manual operating procedures can keep essential processes functioning when the SCADA network is unavailable.
Ask vendors and integrators how vulnerabilities are disclosed and addressed. Clarify who monitors security advisories, tests updates, maintains antivirus or endpoint controls, and verifies backups. A written recovery exercise can reveal gaps that are invisible during a product demonstration.
Plan Data, Alarms, And Integration
A SCADA platform is most useful when information is organized around operational decisions. Establish naming conventions, engineering units, tag descriptions, equipment hierarchies, and consistent time synchronization before configuration begins. Well-structured data makes trend analysis and reporting easier and reduces confusion when staff change.
Alarm philosophy deserves a separate workshop. Define priorities, deadbands, delays, escalation paths, and notification methods. An alarm should indicate that an operator needs to take action; routine status changes should not produce unnecessary notifications. Include procedures for shelving, suppressing, testing, and reviewing alarms so the system remains trustworthy.
Integration may extend beyond process control. Energy meters can reveal inefficient pumping, maintenance records can connect runtime to work orders, and water quality data can improve process oversight. Lessons from commercial water reuse planning also illustrate why monitoring requirements should be considered early when multiple water streams, treatment stages, and reporting obligations are involved.
Build A Defensible Procurement Process
Prepare a requirements document that distinguishes mandatory functions, preferred features, and optional enhancements. Include site conditions, existing equipment, network constraints, standards, training expectations, documentation, testing, warranty coverage, and acceptance criteria. A clear specification reduces change orders and makes vendor responses easier to compare.
A pilot or limited proof of concept can be useful when the utility is uncertain about usability or integration. Select a representative site with several instruments, a real communications path, and common alarm scenarios. Measure configuration effort, screen clarity, response time, reporting quality, and operator confidence before expanding the system.
Professional development can strengthen the evaluation team. Technical events and workshops give utility personnel opportunities to compare approaches with engineers, operators, consultants, and agency staff who have encountered similar controls and automation decisions. Internal participation should include operations, maintenance, management, information technology, and procurement so the selected system has practical support across the organization.
Practical Selection Priorities
A small utility can keep its evaluation focused by giving extra weight to the following decisions:
- Choose reliable local control for essential processes during communications or server outages.
- Require a transparent multi-year cost model instead of comparing purchase prices alone.
- Test alarm handling, trends, reports, and user permissions with realistic operating scenarios.
- Specify data ownership, export formats, backups, cybersecurity duties, and support response times.
- Select a platform that current staff can maintain, with training and documentation included in the contract.
Document the scoring method before proposals arrive. Weight reliability, usability, security, lifecycle cost, and vendor support according to local risk. If a feature cannot be demonstrated or described in enforceable contract language, it should receive limited evaluation credit.
A strong implementation also includes factory testing, site acceptance testing, point-to-point verification, backup validation, and hands-on training. Keep updated network diagrams, tag databases, control narratives, alarm lists, and recovery procedures in a location accessible to authorized staff.
Support Long-Term Utility Performance
SCADA selection is a management decision as much as a technology decision. The system will shape how staff respond to alarms, investigate process changes, document compliance, and plan maintenance for years. Involve operators early, compensate for limited staffing, and avoid designs that depend on one person’s undocumented knowledge.
Recognition and professional connection can reinforce the value of good operational practice. Organizations such as LABS of CWEA highlight achievement across the water environment field through their annual awards program, providing useful perspective on the expertise and teamwork behind dependable utility service.
Move forward with a requirements workshop, a site and communications assessment, and a structured vendor demonstration. By selecting around operational risk, staff capability, cybersecurity, and lifecycle value, a small utility can establish a SCADA system that supports dependable decisions today and adapts to tomorrow’s infrastructure needs.