A wastewater lift station is the most failure-prone unmanned asset a utility owns: two pumps, a wet well, a control panel, and a direct line to a sanitary sewer overflow if anything goes wrong quietly. Most utilities run dozens of them, scattered across a service area, with no operator on site. This guide covers what actually matters when you choose a SCADA system to watch them — the alarms that prevent overflows, the protocols your existing RTUs already speak, the telemetry-service-versus-platform decision, and the data trail your TCEQ and EPA reporting depends on.
Look for five things, in this order: native support for the protocols your field hardware already speaks (DNP3 and Modbus above all), alarm delivery with documented speed and escalation, a historian that automatically captures pump runtimes and wet well levels, a cost model that stays sane at thirty or fifty small sites, and a deployment model — cloud or on-premise — that your IT policy will actually approve. Everything else on a vendor's feature sheet is secondary to those five, because lift station monitoring is not a screens problem; it is an alarming-and-evidence problem.
The reason the order matters: a lift station generates very few tags — wet well level, two or three pump run/fail/seal-fail statuses, maybe a flow meter and a power monitor. What makes the application hard is multiplication. Fifty stations means fifty cellular or radio links to keep polled, fifty panels of mixed vintage to integrate, and an alarm philosophy that has to work at 2 a.m. for a two-person on-call rotation. Platforms priced or architected for big single plants often fall over on exactly this shape of system — which is why per-tag and per-seat licensing deserves scrutiny before anything else. Merobix plans (Starter, Professional, and Enterprise) are flat and custom-quoted rather than per-tag, which is the pricing shape that fits many-small-sites topologies.
This article is the lift-station-specific companion to our broader water utility SCADA monitoring guide, which covers treatment plants, wells, tanks, and distribution.
A well-instrumented lift station needs surprisingly few signals, but each one earns its keep. If your telemetry captures the list below at every station, you can prevent most overflows and explain the rest:
The historian side of this is as important as the live side. Runtime and start-count trends drive preventive maintenance scheduling; level trends during wet weather feed inflow-and-infiltration studies; and all of it becomes your evidence when a regulator asks what happened. Our SCADA reporting guide covers turning historian data into the reports operations and compliance actually consume.
Overflow alarming works when a rising wet well reliably interrupts a human before sewage reaches the rim — which means fast delivery, layered triggers, and escalation that survives one person sleeping through a text. A sanitary sewer overflow is the one lift station failure with regulatory, environmental, and public-relations consequences all at once, so the alarm chain deserves engineering, not defaults.
A defensible SSO alarm philosophy has three layers:
Delivery speed and delivery proof are the vendor-selection questions here. Merobix delivers SMS and email alarms in under 30 seconds and logs every notification and acknowledgment — so after an event you can show exactly when the alarm fired, who was notified, and when a human responded. For a deeper treatment of alarm philosophy across platforms, see our SCADA alarm management comparison.
Rule of thumb: if your high-level alarm and your pump-fail alarm arrive through different systems with different on-call lists, you have two half-systems. The overflow will find the seam between them. One platform, one alarm log, one escalation chain is the architecture that holds up — both at 2 a.m. and in the post-incident review.
Almost every lift station built or retrofitted in the last twenty-five years already speaks DNP3 or Modbus, and a modern SCADA platform should poll that installed base as-is — over serial radio, cellular, or Ethernet — without a rip-and-replace of field hardware. The panels themselves range from float-and-relay logic with a bolt-on RTU, to pump controllers with native Modbus registers, to small PLCs running the whole station.
DNP3 earned its place in water and wastewater telemetry for exactly this application: it supports report-by-exception, event buffering with timestamps, and graceful behavior over slow or intermittent links, so a station that loses its radio path for an hour delivers its buffered events when the link returns. Modbus RTU and TCP are simpler and even more widespread — most pump controllers, VFDs, level controllers, and power monitors expose Modbus registers out of the box (our plain-English Modbus guide explains how the register model works). Newer deployments increasingly add MQTT Sparkplug B for cellular-connected edge devices, because publish-on-change traffic is cheap on metered data plans.
Merobix ships 20 protocol drivers across 7 families — including DNP3, Modbus TCP/RTU, OPC UA, EtherNet/IP, Siemens S7, and MQTT Sparkplug B — as part of the platform. Two due-diligence questions apply to any vendor: are the drivers you need included in the plan or licensed per-driver, and has the platform been proven against serial devices behind radio and cellular links, not just Ethernet devices on a plant LAN? The full driver list is on the features page.
Operators comparing dedicated telemetry services like Mission Communications with full SCADA platforms are really choosing between a packaged appliance model and an open platform model. The packaged model bundles an RTU, cellular service, and a hosted portal into a per-site subscription — quick to deploy and deliberately simple. The platform model connects to whatever hardware each site already has, unifies lift stations with plants, wells, and tanks in one system, and hands you a historian you own.
| Attribute | Dedicated Telemetry Service | Full SCADA Platform (e.g. Merobix) |
|---|---|---|
| Field hardware | Vendor's RTU at every site | Your existing RTUs/PLCs via DNP3, Modbus, MQTT |
| Scope | Lift stations and similar small sites | Lift stations + plants, wells, tanks, boosters in one system |
| Screens & trends | Standardized portal pages | Custom dashboards, full historian, custom reports |
| Alarm chain | Built-in notification service | Configurable escalation; Merobix delivers SMS/email in <30s |
| Data ownership | Lives in the vendor's portal | Your historian — cloud-hosted or on your own servers |
| Lock-in surface | Hardware + service tied together | Open protocols; hardware and platform decoupled |
| Deployment | Per-site install as units ship | Merobix cloud live in 3–5 days; on-premise available |
The honest guidance: if you operate a handful of lift stations and nothing else, a dedicated telemetry service is a legitimate, low-friction answer. The case for a full platform strengthens with every asset that is not a lift station — because the alternative is a permanent second system, a second alarm log, and a second place your compliance data lives. It also strengthens every time a vendor-locked RTU fails and the replacement must come from one supplier at one price. A platform that speaks open protocols lets you standardize the software layer while buying field hardware competitively; our guide to remote monitoring of industrial equipment covers that architecture pattern beyond water.
In Texas, sanitary sewer overflows are reportable events to TCEQ, and utilities are expected to notify the agency promptly, document the spill's start time, duration, volume estimate, and cause, and demonstrate corrective action. At the federal level, EPA's CMOM framework (Capacity, Management, Operation, and Maintenance) sets the expectation that collection-system operators run proactive maintenance programs rather than react to failures. Neither regime mandates SCADA by name — but both are dramatically easier to satisfy with a continuous, timestamped record than with paper rounds sheets.
Concretely, lift station SCADA data supports compliance in four ways:
Where the SCADA system runs matters to some utilities here as well. Merobix is one platform sold two ways: cloud-hosted and managed (live in 3–5 days, 99.9% uptime SLA), or on-premise on your own servers or VMs for utilities whose policies require full data residency — including fully air-gapped networks. The uptime side of that decision has its own engineering discipline, covered in our SCADA high availability and redundancy guide, and the platform's security architecture is documented on the security page. To put a number on what fewer overflow events and truck rolls are worth, the ROI calculator is a reasonable starting point before any demo conversation.
Prioritize five things: protocol support for the RTUs and PLCs already in your stations (DNP3, Modbus RTU/TCP, and increasingly MQTT), alarm delivery you can verify — SMS and email with documented delivery times and escalation chains — a historian that captures pump runtimes and wet well levels for compliance records, a per-station cost model that stays affordable across dozens of small sites, and a deployment model that fits your IT reality, whether that is cloud-hosted or on your own servers. Merobix covers all five with 20 protocol drivers, sub-30-second SMS/email alerting, a built-in historian, flat custom-quoted plans, and both cloud and on-premise deployment.
SCADA prevents SSOs by turning the wet well into a continuously watched asset instead of a weekly drive-by. High-level float and transducer alarms reach on-call operators by SMS and email within seconds, pump-fail and pump-in-hand alarms surface dead or bypassed pumps before the well fills, and runtime imbalance trends flag a weakening pump days before it fails outright. When an overflow does occur, timestamped level and pump data establishes the start time, duration, and cause — the exact facts regulators ask for in a spill report.
Yes — DNP3 and Modbus are the two most common protocols in water and wastewater telemetry, and any serious SCADA platform should speak both natively. Merobix includes 20 protocol drivers across 7 families, including DNP3, Modbus TCP and RTU, OPC UA, and MQTT Sparkplug B, so existing RTUs, pump controllers, and PLCs can typically be brought in without replacing field hardware. The practical questions to ask a vendor are whether the driver is included in the plan or licensed separately, and whether it handles serial RTU devices behind radio or cellular links.
Dedicated telemetry services bundle hardware, cellular connectivity, and a hosted portal into a per-site subscription, which makes them fast to deploy for standalone lift station alarming. A full SCADA platform gives you one system across lift stations, treatment plants, wells, and tanks, open protocol support so you are not locked into one vendor's hardware, and a historian you own for compliance reporting. If lift stations are the only thing you will ever monitor, either approach works; if they are part of a larger utility, a unified platform avoids running two systems forever.
Regulators expect utilities to document sanitary sewer overflows and to demonstrate proactive operation and maintenance of the collection system. A SCADA historian provides the evidence base: timestamped wet well levels and alarm records establish when an event started and how long it lasted, pump runtime and start-count trends document preventive maintenance triggers, and alarm acknowledgment logs show who responded and when. Texas utilities reporting spills to TCEQ, and utilities operating under EPA CMOM expectations, both lean on exactly this kind of continuous record — far stronger evidence than paper logbooks filled in after the fact.
DNP3 and Modbus drivers included, SMS/email alarms in under 30 seconds, cloud or on-premise — flat, custom-quoted plans with no per-tag fees.