Pump Station Remote Monitoring Without a SCADA Integrator

• What Pump Station Remote Monitoring Needs to Cover
• Your Real Options, Side by Side
• Connecting to Your Station's Equipment
• Getting Told When Something Is Wrong
• Watching Trends Over Time
• A Low-Pressure Way to Try It
• The Bottom Line

Ask an operator what they want watched at a pump station and the list is short, even when the station itself is complicated. Four things account for nearly everything:

• Wet well level. How full the well is right now, and whether it is heading toward an overflow or toward a dry run that can damage a pump.
• Pump run status. Whether each pump is running, stopped, or faulted, and how often it cycles. A pump that used to run twice an hour and now runs every few minutes is telling you something before it fails outright.
• Flow. Influent or effluent flow where a meter is installed, useful for catching infiltration, a stuck check valve, or a station working harder than it should.
• Power and communications. Whether the station has utility power or is running on a generator, and whether the monitoring link itself is still reporting. A station that has gone quiet is not the same thing as a station that is fine, and the two need to be told apart.

That is the whole job for most small systems. A city-wide treatment plant with dozens of process variables and a control room staffed in shifts is a different project entirely. A rural water district, a private lift station serving a subdivision, or a small utility with a handful of remote sites just needs those four things visible from wherever the operator happens to be, and a way to hear about it the moment one of them crosses a line.

The classic route to monitoring a pump station is a full SCADA build, which in practice means engaging a systems integrator to design the panels, wire the signals, program the screens, and commission the result, a project priced and scoped for a utility running far more than a few remote stations. For a station outside the reach of that kind of project, there are, in practice, three ways to get pump station remote monitoring in place, and all three exist precisely so you do not have to hire an integrator.

Dedicated monitoring hardware, the category Sensaphone, OmniSite, NightOwl, and Mission all compete in, is purpose-built for exactly this job. A cellular RTU at the station watches your level switches, pump contacts, and flow meter, and a paired monitoring service calls or texts a contact list when a threshold trips, typically for a monthly fee per station that bundles the cellular data along with the software. These are established products with a long history in water and wastewater, and if an automatic phone call the moment a pump faults is the one requirement you will not compromise on, that is precisely what this category is built to deliver.

The do-it-yourself route, a PLC or hobby controller wired up and reporting through a home-automation tool, can be inexpensive, and some operators make it work well for years. The tradeoff is durability. It depends on whoever built it, and a system only one person can maintain is a real liability for critical infrastructure once that person retires or moves on to another job.

ControlBird, the platform we make, takes a third path: a general-purpose monitoring platform paired with commodity hardware, a standard Modbus-capable PLC or IO module you choose yourself, rather than a proprietary RTU sold bundled with the monitoring service. You get the same wet-well-level, pump-status, and flow visibility, configured yourself with drag-and-drop dashboard tools instead of a vendor's fixed portal, on a subscription that is not metered per station, or on a free self-hosted node if you would rather run it on your own hardware.

None of this works unless the platform can read your station's equipment, and for most pump stations built in the last fifteen years or so, it can, without custom wiring. Modbus is the connection most pump controllers, level transmitters, and VFDs already speak, and it is included free in ControlBird Community Edition alongside MQTT, HTTP, CoAP, OPC UA, and email notification. A level switch or float wired to a discrete input, a pump run contact, and a flow meter's pulse or 4-20mA output feeding an analog input are all standard connections a generic Modbus IO module or PLC already exposes, no proprietary sensor required.

For a station with an intermittent connection back to wherever the monitoring runs, whether that is a self-hosted node in your own office or a managed cloud instance, you still need some network path from the station to it: a cellular router, a private APN, or a VPN link, the same kind of connectivity a dedicated RTU also depends on to reach its own monitoring service. ControlBird does not sell or manage that data connection; it reads whatever is reachable over the network you provide, the same way it would read a device on a wired local network.

Visibility matters, but the reason to set any of this up is so you stop having to look.

In ControlBird, you set a threshold, for example a wet well level above a safe point or a pump that has stopped responding, and a severity mapping expression decides how urgent it is: a slow rise can read as a warning, a full alarm as critical. Deadband and hysteresis keep a level hovering near the line from chattering the alarm on and off, and delay timers ride through a momentary reading before committing to the alarm. When the condition holds, ControlBird sends an email to whoever is set up to receive it. An operator can acknowledge the alarm, which records that someone has seen it without clearing the underlying condition, and shelve a known issue for anywhere from 15 minutes to 24 hours so it stops repeating while it is being worked.

Notification today is email, sent through the platform's built-in SMTP service. There is no automated phone call, no text message, and no retry-until-acknowledged escalation. If an automatic call to your phone the instant a critical pump fault happens is the one thing you are not willing to give up, that is the specific strength of the dedicated hardware vendors covered earlier, and a fair reason to stay with one of them. See the alarms guide for the full reference on severities, delays, and shelving.

A live reading tells you what is happening right now. A trend tells you what is changing. A pump that has quietly started cycling twice as often as it used to is a warning sign well before it fails outright, and a wet well drawing down faster overnight than it used to may be pointing at infiltration or a leak upstream.

ControlBird's built-in historian, which is what makes that kind of trend chart possible, is part of the Cloud plans, starting with Starter, rather than the free Community edition. If watching pump cycling and level trends over weeks is central to how you plan to use this, that is worth knowing before you pick an edition; the live values, alarms, and dashboards described above are available either way.

None of this requires committing to anything up front:

• Check what your panel already has. A Modbus, Ethernet, or serial connection on your existing controller is the fastest path in.
• Click through a live demo. The public demo is a real running instance, no sales call required, and a reasonable way to picture your own station in it.
• Run the free edition yourself. Community Edition is a single command: docker run -d --name controlbird -p 3000:3000 -v controlbird-data:/opt/controlbird/data controlbird/ce:latest

Pump station remote monitoring is a genuine need, and the dedicated hardware vendors, with their automatic phone and text alerts, remain the right answer when that escalation path is non-negotiable. For everyone else, the choice has widened: a do-it-yourself build if you are willing to own the risk of being the only person who understands it, or a general-purpose platform like ControlBird if you would rather configure your own screens and alarms on commodity hardware, with email notification rather than a phone dialer, and a historian on the Cloud tiers if trends matter to your operation.

If you are also weighing this against monitoring a tank or a well pump rather than a lift station, this piece on tank and well pump monitoring covers similar ground, and a tier-by-tier look at what traditional SCADA costs is worth a look if a larger plant is also on the table. Otherwise, the current pricing and the demo above are the fastest way to see whether it fits your station.