Top OEMs for SCADA & HMI Platforms for Water Utilities

1. Introduction

In the water and wastewater (W/WW) utility sector, Supervisory Control and Data Acquisition (SCADA) systems and Human-Machine Interfaces (HMI) serve as the central nervous system of critical infrastructure. Unlike discrete manufacturing, where operations are often contained within a single building, water utilities manage geographically dispersed assets ranging from remote lift stations and booster pumps to complex, centralized treatment facilities. The SCADA/HMI platform acts as the primary interface for operators to monitor process variables, control equipment, manage alarms, and ensure regulatory compliance.

The selection of a SCADA/HMI platform is a foundational engineering decision that dictates the facility’s operational efficiency for decades. These systems are not merely visualization tools; they are the aggregation point for data integrity, situational awareness, and automated decision-making. In the modern regulatory environment, utilities face increasing pressure to provide accurate, timestamped data for EPA reporting, minimize combined sewer overflows (CSOs), and optimize energy consumption. Consequently, the software platform must be robust, secure, and capable of handling vast historical datasets without latency.

For municipal consulting engineers and utility decision-makers, the “software specification” is often more complex than hardware selection. Hardware life cycles may span 10 to 15 years, but SCADA software evolves rapidly, requiring a platform that supports backward compatibility, virtualization, and integration with diverse communication protocols such as DNP3, Modbus TCP, and Ethernet/IP. Furthermore, the convergence of Information Technology (IT) and Operational Technology (OT) demands that modern platforms adhere to rigorous cybersecurity standards (IEC 62443) while providing business-layer connectivity.

This article analyzes the engineering characteristics, architectural strengths, and limitation profiles of the leading Original Equipment Manufacturers (OEMs) for SCADA and HMI platforms specifically within the context of water and wastewater treatment. The focus is strictly on technical capability, long-term maintainability, and application fit for municipal infrastructure.

2. How to Select a SCADA & HMI Platform

Selecting a SCADA platform requires a holistic engineering approach that evaluates the software architecture against the specific operational realities of the utility. Engineers must look beyond initial licensing costs and consider the Total Cost of Ownership (TCO), which includes development hours, training, annual support contracts, and migration complexity.

Architecture: Client/Server vs. Distributed

The fundamental architecture of the SCADA system defines its scalability.
Standalone/Thick Client: Historically common, where the HMI software runs locally on a PC connected to a PLC. This is simple but creates data silos and maintenance headaches, as every change must be deployed to individual terminals.
Server/Client (Networked): The standard for modern treatment plants. A centralized server (or redundant pair) hosts the tag database and screen definitions. Clients connect to the server to visualize the process. This ensures a “single version of the truth” for data.
Distributed/Web-Based: The emerging standard. Utilizing HTML5 and web technologies allows clients to be OS-agnostic (running on tablets, phones, or Linux terminals) and simplifies deployment, as no software installation is required on the client side.

Redundancy and High Availability

Water treatment is a critical process; therefore, SCADA downtime is unacceptable. Engineers must specify the level of redundancy required.
Server Redundancy: Primary and backup servers synchronized in real-time. Upon failure, the backup assumes control seamlessly (bumpless transfer).
Network Redundancy: Support for dual-path Ethernet rings (like DLR) or parallel network schemes.
Data Buffering: The ability of the platform to handle “Store and Forward” data. If the connection between a remote site and the central server is lost, the local PLC or edge device must buffer data and upload it chronologically once the connection is restored to prevent data gaps in regulatory reports.

Data Historian and Reporting

In W/WW, the Historian is as critical as the real-time control. It stores time-series data (flow rates, turbidity, chlorine residuals).
Selection Criteria: Does the platform use a proprietary flat-file database or a standard SQL database? SQL-based historians generally offer better interoperability with third-party reporting tools (like Hach WIMS or Dream Report) but may require higher storage overhead. Efficient compression algorithms (e.g., Swinging Door) are essential to manage disk space without losing data fidelity.

Alarm Management (ISA 18.2)

Modern specifications should mandate compliance with ISA 18.2 standards for alarm management. The platform must support features that prevent “alarm floods” and “nuisance alarms.” Key features to specify include:
Shelving: Ideally allowing operators to temporarily suppress alarms during maintenance.
State-Based Alarming: Alarms that are only active when equipment is in a specific state (e.g., a low-flow alarm should not trigger if the pump is commanded off).
Escalation: Routing unacknowledged alarms to different user groups or mobile devices.

Graphics and HMI Standards (ISA 101)

The industry is moving away from complex, P&ID-style graphics with 3D animations toward High-Performance HMI (ISA 101). This design philosophy uses muted colors (grayscale) for static equipment and reserves bright colors (red, yellow) strictly for alarms and abnormal states. The selected platform must possess a graphics library capable of supporting this methodology (e.g., sparklines, radar charts, and situational awareness symbols) rather than just static bitmaps.

Licensing Models

Licensing structures vary significantly between OEMs and impact long-term costs.
Tag-Based: Cost increases with the number of I/O points (Tags). This can be restrictive for large utilities that want to track extensive diagnostic data.
Client-Based: Cost is based on the number of concurrent viewers.
Server-Based / Unlimited: A flat fee for the server, regardless of tags or clients. This model encourages data density and broad access but often carries a higher initial server cost.

3. Comparison Table

The following table compares the five primary SCADA/HMI platforms encountered in the North American water sector. Engineers should interpret “Scalability” as the system’s ability to grow from a single lift station to a regional authority without platform replacement, and “Database Openness” as the ease of accessing historical data via standard IT tools (SQL/ODBC).

OEM Platform	Primary Architecture	Licensing Model	Historian Type	Strengths	Limitations	Best-Fit Application
AVEVA (Wonderware / System Platform)	Object-Oriented / Distributed	Tag & Client Count	Proprietary (high compression) & SQL	Extremely scalable “System Platform”; Object-oriented templating allows rapid deployment for standardized assets; massive install base.	High complexity/learning curve for “System Platform”; Licensing can be expensive for medium systems; Legacy migration can be complex.	Large regional utilities requiring standardization across multiple plants.
Inductive Automation (Ignition)	Server-Centric (Web/Java)	Unlimited (Server-based)	SQL Native	Unlimited tags/clients model; Native HTML5 (Perspective); Cross-platform (Linux/Windows); Built-in Python scripting.	Requires knowledge of SQL and Python for advanced customization; Newer paradigm shifts for operators used to legacy systems.	Modernizations, Enterprise-wide SCADA, Utilities desiring IT/OT convergence.
Siemens (WinCC)	Integrated TIA Portal / OA	Tag & Feature based	Proprietary & SQL	Deep integration with Siemens hardware; WinCC OA handles massive tag counts (millions); robust redundancy.	Integration with non-Siemens hardware is possible but less streamlined; Complex licensing tiers (Basic, Comfort, Advanced, Professional, OA).	Plants utilizing Siemens PLCs; Large-scale infrastructure projects (WinCC OA).
Rockwell Automation (FactoryTalk View)	Distributed / Standalone	Display & Screen Count	Proprietary (FT Historian)	Native integration with Allen-Bradley Logix; “Faceplate” synergy; dominant market share in North America ensures support availability.	Proprietary ecosystem; “View SE” distributed architecture can be complex to maintain; historical reliance on ActiveX/VBA (legacy).	Utilities standardized on Allen-Bradley ControlLogix/CompactLogix.
Schneider Electric (EcoStruxure / Citect)	Client/Server / Geo-SCADA	Tag & Client Count	Proprietary	GeoSCADA (ClearSCADA) is exceptional for telemetry/remote sites (DNP3 native); Citect offers high-performance graphics engine.	Fragmentation between different software lines (Citect vs. GeoSCADA vs. Machine SCADA); Learning curve for Cicode.	Remote telemetry networks; Utilities with high DNP3 usage; Schneider hardware bases.

4. Top OEMs / System Integrators

This section details the technical specifications and engineering considerations for the five major SCADA/HMI platforms approved for this analysis.

AVEVA (Wonderware / System Platform)

AVEVA, having acquired the heritage Wonderware brand, offers one of the most prevalent SCADA solutions in the water industry. The portfolio is split primarily between AVEVA InTouch HMI (for machine-level or smaller plant control) and AVEVA System Platform (formerly Wonderware ArchestrA).

System Architecture:
For large water utilities, AVEVA System Platform is the flagship. It utilizes an object-oriented approach based on the “Galaxy” repository. Instead of creating individual tags for every pump, engineers define a “Pump Object” template containing the graphics, alarms, PLC I/O mapping, and historization scripts. Instances of this object are then deployed to the Galaxy. If a change is made to the template, it propagates to all instances automatically. This ensures strict standardization across large facilities.

Technical Strengths:

• Device Integration: The Operations Integration (OI) servers provide robust drivers for virtually every PLC brand, decoupling communication from the application layer.
• Graphics: Industrial Graphics (formerly ArchestrA Graphics) are vector-based and highly customizable, supporting .NET controls.
• Historian: The AVEVA Historian is a high-speed, compressing database capable of handling burst data, making it suitable for process analysis.

Engineering Considerations:
System Platform is resource-intensive and typically requires a significant server infrastructure (often virtualized). The complexity of the “Galaxy” architecture requires specialized training (certified system integrators) to maintain. Engineers should specify System Platform for large, multi-site utilities where the object-oriented efficiency outweighs the initial setup complexity.

Inductive Automation (Ignition)

Inductive Automation has disrupted the SCADA market with Ignition, a platform built on modern IT standards (Java, Python, SQL). It is distinct because it is sold by the server license rather than by tag or client count, which fundamentally changes the architecture design for utilities.

System Architecture:
Ignition acts as a central hub (Gateway). It connects to PLCs via OPC-UA (built-in) and connects to any standard SQL database (PostgreSQL, MS SQL, MySQL) for history.
Perspective Module: A mobile-responsive visualization module that runs purely in a web browser (HTML5/CSS3). It allows operators to view SCADA on mobile devices without app installation, leveraging the device’s sensors (GPS, camera for QR codes).
Vision Module: The classic Java-based desktop client for dedicated control room workstations.

Technical Strengths:

• Interoperability: It bridges IT and OT seamlessly. The platform creates a bridge between PLCs and SQL databases, allowing for complex transaction groups (e.g., “When the backwash completes, write the flow totals to a row in the SQL database”).
• MQTT/Sparkplug B: Ignition has native support for MQTT, making it a leading choice for IIoT and modern efficient telemetry over cellular networks.
• Scripting: Utilizes Python (Jython) for scripting, which is a powerful, non-proprietary language familiar to many modern engineers.

Engineering Considerations:
While the unlimited licensing is attractive, engineers must ensure the hardware specifications (RAM/CPU) are sized correctly to handle the load of a single server managing “unlimited” connections. Redundancy configuration is straightforward but requires two full licenses. It is an ideal fit for utilities seeking to modernize and consolidate data silos.

Siemens (WinCC)

Siemens offers a broad range of HMI/SCADA products under the WinCC umbrella. For the North American water market, the focus is typically on WinCC Professional (within the TIA Portal framework) and WinCC Open Architecture (OA).

System Architecture:
WinCC Professional: Integrated directly into the Totally Integrated Automation (TIA) Portal. This provides a unified engineering environment where the PLC (S7-1500) and HMI are programmed in the same interface. Variables are shared automatically, eliminating tag duplication errors.
WinCC OA: A platform designed for massive scale and complexity. It is object-oriented and supports distributed systems with up to 10 million tags. It allows for dynamic system changes without stopping the runtime engine.

Technical Strengths:

• Hardware Integration: When paired with Siemens PLCs, the diagnostic capabilities are unmatched. System diagnostics (wire break, module failure) are reported to the HMI automatically without additional code.
• WebUX: Provides platform-independent access via HTML5 browsers for remote monitoring.
• Security: “Security by Default” configurations align with IEC 62443.

Engineering Considerations:
WinCC is most effective when the utility is standardized on Siemens hardware (PLCs/Drives). While it supports third-party drivers (OPC), the “special sauce” of integrated diagnostics is lost. WinCC OA is a high-end solution often reserved for the largest metropolitan utilities or complex tunnel automation projects.

Rockwell Automation (FactoryTalk View)

Rockwell Automation is a dominant player in the US municipal market. Their SCADA solution, FactoryTalk View Site Edition (SE), is the standard for facilities utilizing Allen-Bradley ControlLogix and CompactLogix controllers.

System Architecture:
FactoryTalk View SE operates on a distributed architecture utilizing the “FactoryTalk Services Platform.” This directory-based service manages security, alarms, and communications across the network.
View SE Station: A single-computer solution (HMI and Server on one box).
View SE Distributed: Separate HMI Servers, Data Servers, and multiple HMI Clients (Viewers).

Technical Strengths:

• Logix Integration: The “Premier Integration” allows the HMI to directly reference tags in the PLC without creating an intermediate HMI tag database. This reduces development time and memory usage.
• Add-On Graphics (Global Objects): Rockwell’s PlantPAx library provides pre-engineered process objects (e.g., a Motor object) that link automatically to Add-On Instructions (AOI) in the PLC. This enforces a high standard of consistency.
• TrendX: A robust trending tool embedded within the software.

Engineering Considerations:
FactoryTalk View SE relies heavily on Microsoft Windows technologies. Patch management and domain integration are critical. Historically, version mismatch between the FactoryTalk Services Platform and the application could cause issues, so strict revision control is necessary. It is the logical choice for any Rockwell-centric facility.

Schneider Electric (EcoStruxure / Citect)

Schneider Electric’s portfolio includes AVEVA products (due to corporate ownership structure) but also maintains distinct platforms popular in water: EcoStruxure GeoSCADA Expert (formerly ClearSCADA) and Citect SCADA.

System Architecture:
GeoSCADA Expert: Specifically engineered for telemetry and remote SCADA applications. It has a built-in object-oriented database and includes an integrated Historian. Its core differentiator is its native handling of DNP3 and IEC 60870 protocols. It manages the complexities of polling remote sites over low-bandwidth radios, backfilling data from outstations automatically.
Citect SCADA: Known for its high-performance graphics engine and “Cluster” architecture, allowing for flexible redundancy and load balancing.

Technical Strengths:

• Telemetry Management (GeoSCADA): It treats the communication link as a variable. If a radio link goes down, the system knows to retrieve the buffered data from the RTU once the link is restored. This is critical for regulatory reporting on remote lift stations.
• Vector Graphics: Citect offers high-quality scaling without pixelation.
• Driver Library: Extensive support for legacy protocols often found in older water systems.

Engineering Considerations:
For a utility with hundreds of remote sites (pump stations, reservoirs) communicating over radio or cellular, GeoSCADA is often the superior engineering choice due to its specialized telemetry features. For inside-the-fence plant control, Citect or the broader EcoStruxure (System Platform) offerings are used. Engineers must clearly define the use case (Plant vs. Network) to select the correct Schneider tool.

5. Application Fit Guidance

Matching the OEM to the application is critical for long-term success. The following scenarios highlight where specific platforms tend to excel.

Municipal Wastewater Treatment Plants (Inside the Fence)

For centralized treatment plants with high I/O counts and complex process loops (Aeration, Digestion), AVEVA System Platform and Rockwell FactoryTalk View SE are the market leaders. Their ability to handle complex redundancy, large-scale historization, and standardized object libraries makes them ideal for mission-critical process control where high availability is paramount.

Water Distribution and Collection Systems (Telemetry)

For systems that are geographically dispersed (Water Towers, Lift Stations) relying on radio or cellular telemetry, Schneider Electric’s GeoSCADA (ClearSCADA) and Inductive Automation’s Ignition are top contenders. GeoSCADA is purpose-built for buffering data from remote terminal units (RTUs). Ignition’s MQTT capabilities allow for “Report by Exception” bandwidth efficiency, which reduces cellular data costs and improves response times compared to traditional polling.

Small to Medium Municipalities (Cost-Conscious)

For smaller utilities where IT support is limited, maintaining a complex distributed server architecture is challenging. Ignition is often favored here due to its simplified licensing (one server cost) and ease of backup/restore. AVEVA InTouch (standalone) is also a frequent choice for single-workstation applications due to its reliability and ease of use for operators.

Retrofit and Heterogeneous Environments

When a utility has a mix of PLC brands (e.g., old Modicon, new Allen-Bradley, and some Siemens), Ignition and AVEVA shine due to their platform-agnostic nature. They can aggregate data from diverse hardware more easily than hardware-centric platforms like WinCC or FactoryTalk, which favor their own hardware families.

6. Engineer & Operator Considerations

Installation and Deployment

Modern SCADA deployment is shifting towards virtualization. Engineers should specify that the SCADA system runs on Virtual Machines (VMware or Hyper-V). This decouples the software from the physical server hardware. If a server fails, the SCADA image can be spun up on a new physical host in minutes.
Best Practice: Ensure the OEM platform supports “thin client” deployment for operator stations to eliminate the need for maintaining software on desk computers.

Cybersecurity and Network Segmentation

The SCADA network must be segmented from the business (enterprise) network, typically separated by a DMZ (Demilitarized Zone) with firewalls.
Integration Challenge: Engineers must verify that the chosen OEM platform supports Active Directory (AD) integration for user management. This ensures that when an operator leaves the utility, their access is revoked centrally. The platform should also support encrypted communications between the server and the clients (HTTPS/SSL).

Maintenance and Long-Term Support

Software maintenance agreements (SMA) are mandatory for receiving security patches. Engineers must budget for these recurring costs.
Version Control: A common failure mode in SCADA management is “version drift,” where different machines run different versions of the runtime software. Centralized deployment (ThinManager or web clients like Ignition Perspective) eliminates this risk.

Human Factors (HMI Design)

Operators are the primary users. The design must minimize cognitive load.
Grayscale Efficiency: Specify that the OEM platform must support High-Performance HMI libraries. A screen full of animated 3D pumps and flowing water pipes distracts from critical data. The HMI should be boring; if it looks exciting, something is wrong.

7. Conclusion

The selection of a SCADA/HMI platform for water and wastewater utilities is a decision that balances current operational needs with future scalability and cybersecurity requirements. There is no single “best” platform; rather, there is a “best fit” based on the utility’s specific architecture and legacy infrastructure.

Rockwell Automation and Siemens offer unparalleled integration when the underlying control hardware is uniform. AVEVA provides a robust, object-oriented framework ideal for large, standardized regional utilities. Inductive Automation has redefined the market with a flexible, IT-friendly licensing model and modern web standards that appeal to utilities seeking digital transformation. Schneider Electric remains a powerhouse for telemetry-heavy applications where data integrity from remote sites is the priority.

For the consulting engineer and utility manager, the goal is to specify a system that delivers reliable data, complies with environmental regulations, and empowers operators to make informed decisions. By focusing on open standards (SQL, HTML5, OPC UA) and robust redundancy, utilities can invest in platforms that will remain viable and secure for the long term.

source https://www.waterandwastewater.com/top-oems-for-scada-hmi-platforms-for-water-utilities/