Cloud wastewater SCADA for treatment plants and lift stations

No, and that's the point. ControlCom sits on top of your existing SCADA, talking to the same PLCs and RTUs via Modbus, OPC-UA, or BACnet, so nothing about the control layer changes and your operators keep the HMI they know. What the platform adds is the layer a workstation-bound SCADA was never built to deliver: cloud dashboards reachable from anywhere, native mobile apps with alarm routing for the on-call rotation, fleet-wide rollups across every site in the service area, and automated regulatory reporting from the same time-series. The two systems do not fight over the PLCs; reads are non-intrusive, and the edge agent makes outbound-only connections so nothing is opened inbound on the control network. When the on-prem SCADA eventually reaches end of life, you migrate at your own pace with the history already in the platform, rather than under a procurement deadline with a six-figure upgrade quote on the table.

Yes. The platform ships with templates for the common federal and state discharge-monitoring reports (DMR, NPDES, state-DEP variants), plus a Dashboards-as-a-Record PDF export for any custom report your state requires, generated for any historical date range on demand. The numbers, flow totals, chlorine residual, pH, and the rest of the treatment train chemistry, are pulled from the same time-series the platform already collects for operations, so there is no double entry and no spreadsheet copy/paste between the SCADA export and the report form. Scheduled delivery sends the recurring package to a distribution list every cycle without anyone remembering to run it, and because every reading is timestamped and kept, the harder questions have answers too: what the effluent flow was during the storm event, which alarms fired that night, and who acknowledged them. When the regulator changes a form, the template changes; the underlying record does not have to be rebuilt.

Drop the ControlCom edge agent onto a small industrial PC, point it at the lift station's PLC over Modbus or OPC-UA, and it discovers pumps, wet-well levels, and high-water alarms automatically. From there, runtimes, start counts, intertie status, and alarm history land in the cloud within minutes, and the station appears on the service-area map colored by its alarm state. Thresholds evaluate on the edge agent itself, so a high-water alarm fires and routes even if the backhaul is down at that moment, which is exactly when a lift station is most likely to be in trouble. Sites with cellular-only backhaul work the same way; the edge buffers readings locally through outages and forwards them when the link returns, so the trend history has no gaps. Each station accumulates its own runtime and alarm record, which is what turns the maintenance schedule from calendar-based guesswork into something driven by actual pump behavior.

Yes. Native connectors ship for Modbus TCP/RTU, OPC-UA, Ethernet/IP, BACnet, and MQTT, covering Allen-Bradley (Rockwell), Schneider, Siemens, GE, and most other industrial OEMs in production at water utilities. Mixed fleets are the normal case, not the exception: the treatment plant on Allen-Bradley, half the lift stations on Schneider from a nineties build-out, and the newest booster station on whatever the design engineer specified last year. All of them land in the same platform with the same dashboards and the same alarm engine, so the visibility program stops depending on which decade a station was built in. There is no per-device custom integration project and no OEM license call to get the data out; the edge agent polls the registers the PLCs already expose. For anything weirder, a legacy RTU or an oddball serial device, the SDK lets your integrator wrap a custom driver in a weekend.

Common, and the architecture assumes it. The edge agent works on any LTE/5G modem and is designed for intermittent backhaul: it buffers readings locally during outages and forwards them when the link returns, so you don't lose the trend or the alarm history to a dropped connection. Alarm thresholds evaluate on the agent itself, at the station, so a high-water or pump-fail alarm still fires and routes during the outage rather than waiting for the link to come back. Bandwidth budgets stay under 50 MB/month per site for typical telemetry volumes, which keeps a fleet of stations on inexpensive IoT data plans rather than enterprise cellular contracts. Security fits the same constraint: the agent makes outbound-only connections, so no inbound port is exposed on a cellular link that is reachable from anywhere, and telemetry is encrypted in transit. A technician at the station still gets a live local view even with no internet at all.

A single-site pilot (one plant or one lift station) typically goes live within a week of contract: the edge agent installs on a small box at the site, the connectors pick up the PLC, and live data is flowing before the first status meeting. Fleet rollouts to 20+ sites are usually 6 to 10 weeks, depending on how many vendor portals we have to replace and how clean the existing PLC tag naming is; messy tag names are the single biggest schedule variable, because mapping them to a sensible asset hierarchy is where the human judgment goes. The first site establishes the templates, dashboards, alarm groups, and report formats, and every subsequent station inherits them, so the rollout accelerates as it proceeds. There is no on-prem migration project, no SCADA cutover window, and no operator retraining before value shows up; the existing system keeps running while the platform comes up alongside it.