The short answer
Other Platforms
Beyond the platforms with their own pages, a utility meets others: Siemens WinCC inside European packaged equipment and at plants standardized on that ecosystem; distributed control systems from the process industries at large regional plants; independent SCADA products with regional strongholds; hosted monitoring services that put a cellular unit at a lift station and a portal on the web; and open-source tools that appear in pilots and small systems. None of them is wrong in itself. The questions are the same for every platform: whether it will be supported and staffed for the life of the plant, how it is licensed, whether its history and configuration can be exported, how it handles redundancy and remote access securely, and whether the local integrators and the utility staff can maintain it at two in the morning without the vendor.
Key points
- Siemens WinCC, distributed control systems, independent SCADA products, hosted services, and open-source tools all appear in water systems.
- Judge a platform on support life, staffing, licensing, data portability, redundancy, and secure remote access.
- A hosted monitoring service is a contract and a dependency, not just a product; know what happens when it ends.
- Open-source tools need the same backups, security, and ownership as commercial ones, and a person who owns them.
- Standardize: one plant HMI and, where needed, one telemetry SCADA, with a written exit plan for each.
Platforms you may meet
| Platform | Where | Notes |
|---|---|---|
| Siemens WinCC | Packaged equipment from European manufacturers; plants standardized on Siemens | Several products under one name: panel HMI, plant SCADA, and a large distributed version; integrates most directly with Siemens controllers |
| Distributed control systems | Large regional treatment plants and plants with process industry heritage | Controllers, I/O, and operator interface as one engineered system from one vendor; different staffing and lifecycle model from SCADA |
| Independent SCADA products | Regional strongholds and specific integrator bases | Some are excellent; the questions below decide whether one belongs in your utility |
| Hosted monitoring services | Lift stations, wells, and tanks at small utilities | A cellular unit at the site and a vendor portal; alarms by text and phone; monitoring more than control |
| Open-source SCADA and dashboards | Pilots, small systems, and utilities with software staff | No license cost; all the responsibility |
| Cloud SCADA offerings | Emerging at small and medium utilities | The platform in a vendor cloud with local gateways; the security and dependency questions are the whole decision |
Hosted monitoring services
A service that installs a cellular unit at a lift station, brings the floats, the run status, and the level to a web portal, and calls the operator when the wet well is high is attractive to a utility with no SCADA and no staff to run one. It is monitoring rather than control, the data lives with the vendor, the unit is theirs, and the contract decides what the utility gets if it ends: the data export, the equipment, the alarm history. It suits a small utility as a first step and remains useful as a backup path for critical sites; it is not a substitute for a utility-owned SCADA at a plant or on a system that needs control.
Open-source tools
Open-source SCADA products, dashboard tools, and protocol libraries can build a working system at no license cost, and some utilities with software staff do. The system then has no vendor to call, no support lifecycle but the community, and every question of security, redundancy, backups, and updates answered by the utility itself. A pilot on a test network is a fine use; a production system on open-source tools needs a named owner, a documented build, the same change control as any other SCADA, and a plan for the day the owner leaves.
The questions
- Support life
- Will the product and its drivers be supported and patched for the life of the plant, and who provides that support locally.
- Staffing
- Can the utility staff and the local integrators maintain it, and is training available.
- Licensing
- Perpetual or subscription; by tag, by client, by server; what stops working when a subscription lapses.
- Data portability
- Can the history, the alarm log, and the configuration be exported in a standard form, and has anyone tried.
- Redundancy
- What server and communication redundancy it offers and how it is tested.
- Remote access
- How operators reach it from outside, and whether that can be done behind a virtual private network with multi-factor authentication.
- Security
- Accounts and roles, audit trail, patch cadence, and secure protocols to the field.
- Exit plan
- What the migration to another platform would take, written down while nobody needs it.
Frequently asked questions
- A vendor wants to put our plant on their cloud SCADA. Should we?
- Only after the questions above are answered in writing: where the data lives, what runs locally when the internet is down, how the field connection is secured, how the contract ends, and what the utility owns. Local control must not depend on the cloud, and the security review is the decision.
- The packaged system came with its own HMI. Do we integrate it or replace it?
- Integrate it: the skid keeps its own controller and touchscreen, and the plant SCADA reads the interface the manufacturer documented. Replacing the skid HMI voids the support for the equipment and takes on logic the plant does not own.
- Is a distributed control system overkill for a water plant?
- For most plants, yes; for a very large plant with complex chemical and biological processes and a staff used to the model, it can be right. It is a different procurement, lifecycle, and staffing model, and it should be chosen deliberately.
- How do we evaluate an independent product we have not heard of?
- References from utilities of similar size that have run it for ten years, a look at the integrator base within driving distance, the licensing and support terms in writing, and a test of exporting history and configuration.
Related topics
- What Is SCADA?Supervisory control and data acquisition: the layer that collects data from controllers across a system, presents it to operators, records it, and lets them intervene.
- SCADA ArchitectureThe parts of a SCADA system and how data moves between them: I/O servers, the tag database, clients, the historian, the alarm server, and the topologies from a single panel PC to a redundant, distributed plant.
- VPN DesignHow a VPN fits remote access for a control system: it terminates in the DMZ and lands on a jump host, never the control network; site-to-site tunnels carry telemetry; user tunnels require multi-factor and individual accounts; the concentrator is patched fast.
- SCADA BackupsWhat a SCADA backup must contain to bring a system back: the project export, an image of each server, the databases, historian archives, licenses, certificates, scripts, and network device configurations, with frequency, retention, and the restore procedure.
- Design ChecklistA review checklist for a control system design at each stage from concept to issued for construction: documents, architecture, controllers and I/O, panels and power, instruments, networks and security, SCADA and alarms, deliverables, and commissioning.
- VTScadaField notes on VTScada, the Trihedral platform widely used by municipal water utilities: the all-in-one design with historian, alarm notification, and thin clients built in, server redundancy, application versioning, telemetry drivers, and licensing by tags.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.