When the Storm Hits at 2 AM
The rain hasn't stopped in nine hours.
You're sitting on the edge of the bed, phone on the nightstand, running through a mental checklist of every remote lift station in the district. Station 7 lost power last quarter during a storm half this size. The flashing red light on that panel did its job — but nobody was there to see it. By the time a crew arrived the next morning, the wet well had already overflowed into a drainage ditch, and the regulatory paperwork took longer than the cleanup.
Will tonight be a repeat?
A tank level alarm detects the problem. Cellular monitoring delivers the message to your phone — even when the station's power is dead and the internet is down. Together, they form what we call the Reliability Stack: a layered system that pairs a physical sensor with an independent cellular communication path so that critical alerts reach you when it matters most, not when it's already too late.
This guide walks through two failure modes every municipal operator should understand, three layers of the stack, one diagram you can hand to your manager, and a checklist to determine which stations need it first.
What a "Reliability Stack" Means in Municipal Monitoring
A Reliability Stack is a layered monitoring approach designed so that no single component failure can silence an alert. The concept breaks into three parts: a sensor that detects a condition, a cellular path that transmits the alert, and resilience design that keeps both working during outages.
Think of it this way: when the station loses power at 2 AM, does anything still have a path to reach you?
If the answer is "only if someone drives out there and sees the light," you have a single layer — and a single point of failure. The Reliability Stack eliminates that gap by combining two distinct functions into one system. The tank alarm acts as the sensor — it detects when water reaches a critical level. Cellular monitoring acts as the voice — it transmits that detection to your phone, independent of local power and local internet. Neither layer works alone. Both layers working together remove the silence from a silent failure.
This isn't more technology for its own sake. It's a practical answer to a municipal reality: critical sites are frequently unattended, and the incidents that matter most happen outside normal staffing windows. EPA materials on sanitary sewer overflows (SSOs) highlight that power failures are among the contributing causes of overflows — and the operational theme is consistent: outages and surges happen, and the system has to stay communicative when they do.
The Two Failure Modes: Sensor-Only vs. Connectivity-Only
Every monitoring gap falls into one of two categories. Understanding them makes the case for the full stack almost self-evident.
"A sensor without a voice is useless; a voice without a sensor is blind."
Sensor-Only Failure: The Alarm Nobody Hears
Picture a remote lift station equipped with a standard high-water alarm — a local light and horn mounted on the control panel. During normal operations, an operator visits weekly. A storm rolls through on a Tuesday night, the wet well rises past the high-level float, and the red beacon starts flashing. The horn blares into an empty field. By Wednesday morning, wastewater has backed up into a residential line. The alarm did exactly what it was designed to do. The problem is that its only audience was a concrete wall.
This failure mode is common because it feels safe during commissioning: the light turns on during the test, so it must be reliable. The missing piece is notification.
Connectivity-Only Failure: The Signal with Nothing to Say
Now imagine the opposite. A station has a remote telemetry connection — maybe through a Wi-Fi bridge or a landline dialer — but the float switch was never wired into the system. The connection is live. Data flows. But when the wet well rises, there's no trigger to report. The system can talk, but it has nothing meaningful to say about the one condition that actually matters: water level.
The data pipeline may be modern, but the tripwire isn't resilient. A site can still fail silently if the trigger never reaches the communication layer.
These two scenarios aren't hypothetical edge cases. They're the most common monitoring gaps in small and mid-sized municipal collection systems, and they're entirely preventable.
Layer 1: Tank Alarms as the "Sensor" (What They Detect and How)
The first layer of the stack is the physical detection device — the tank alarm itself. In municipal wet well applications, this is typically a float switch set to trigger at a predetermined high-water level. The switch responds directly to a physical condition, it can be exercised during commissioning and routine checks, and operators can reason about its behavior without specialized training.
A high-level condition signals that water in the wet well has risen beyond the normal operating range — usually because a pump has failed, power is out, or inflow has exceeded capacity. A low-level condition can indicate a pump that won't shut off or an unexpected drop in flow. For most municipal operators, high-level detection is the critical minimum because it's the condition most likely to result in a sanitary sewer overflow (SSO), which carries regulatory consequences under the Clean Water Act.
A quick note on dry contacts: you'll see this term on spec sheets. A dry contact is simply an electrical switch that opens or closes a circuit without carrying its own voltage. It's the universal language between a float switch and an alarm device — when the float rises to the trigger point, it closes the contact, and the connected alarm unit registers the event. If your station already has float switches wired to a local panel, they almost certainly use dry contact outputs, which means they can connect directly to a cellular alarm unit without rewiring.
One practical caveat worth noting: the specifics of float selection, mounting, and set points are installation-dependent. Wet well geometry, turbulence, grease buildup, and pumping cycles all influence how a switch behaves in the field. The general principle holds — a physical sensor creates a reliable trigger — but installation details determine the quality of that trigger.
The TextLight Wastewater Level Monitoring Kit pairs a 120V cellular alarm unit with a wastewater float switch designed specifically for wet wells and open water tanks. For non-wastewater applications, the TextLight Tank Level Monitoring Kit pairs the same cellular alarm unit with a tank level switch for monitoring non-caustic liquids. For stations that already have functioning floats, the TextLight base unit accepts a dry contact input — so you can overlay cellular alerting onto existing infrastructure without replacing what already works.
Layer 2: Cellular Monitoring as the "Voice" (How Alerts Get Out During a Blackout)
Detection without delivery is just a blinking light in an empty room. The second layer gives your sensor a communication path that doesn't depend on the station's power, internet, or local network.
Unlike Wi-Fi-based alarm systems that route alerts through your local router, then to an internet service provider, then to a cloud server, and finally to your phone, cellular monitoring sends a text message directly from the device through the carrier's cellular network to your phone. With direct cellular transmission, the message travels from the device through the cellular network to your phone. There's no local router in the chain, no on-site ISP connection, and no dependence on your local facility’s network infrastructure.
In operational risk terms, this distinction matters more than it might first appear. Alerting is the difference between a detected event — known only at the panel — and a managed event, known to the responder with time to act. When staffing is thin, responders are covering multiple assets, and weather windows are short, the cellular layer directly reduces the burden of storm-watch anxiety. Instead of driving to check a site "just in case," an operator can reserve trips for alerts that indicate real change.
When a storm knocks out power at a station, the Wi-Fi router dies immediately. Even if you have a UPS on the router, a widespread outage may take down the cable connection point in the yard, rendering the entire local network useless. A cellular alarm device with a backup battery sidesteps all of that. Cell towers carry their own backup generators and built-in redundancy, so the outbound communication path stays alive even during a regional power event.
The TextLight's 6VDC rechargeable battery maintains operation for 12+ hours during a power loss — long enough to cover most outage windows and give you time to respond.
The subscription reality: All PumpAlarm.com devices require an annual cellular subscription to maintain connectivity to the cellular network. TextLight units carry an annual fee of $75, while PumpAlarm devices run $49.99 per year. That's a real, recurring cost. It's also the cost of keeping a communication path open 24 hours a day, 365 days a year, to a station that might only need to scream for help once — but that one time could prevent an overflow, a fine, or a public health incident.
Layer 3: Power and Communications Resilience (Removing Single Points of Failure)
With the sensor and the voice in place, the final layer is making sure every link in the chain can survive the conditions that cause the emergency in the first place. Three things must stay alive for an alert to reach you:
The sensor trigger. The float switch itself is a mechanical device — it doesn't need external power to detect a water level. As long as it's physically intact and properly positioned, it works.
The alarm device's power. The TextLight runs on 120V station power under normal conditions and automatically falls back to its internal rechargeable battery when that power is lost. This is the bridge that keeps the device awake during exactly the scenario you're most worried about.
The outbound communication path. Cellular transmission removes the dependency on local internet infrastructure. Cell towers are engineered for resilience, with backup power systems designed to maintain coverage during the types of events — storms, floods, widespread outages — that create the emergency in the first place. CISA's resilient power best practices reinforce this principle: critical communications infrastructure should not share failure modes with the systems it's designed to monitor, and critical facilities should plan for continuity during outages using backup power concepts and risk-informed planning.
When all three links hold, an alert generated by a rising water level in a dark, powerless pump station still reaches your phone as a text message — even at 2 AM, even in a storm.
The Architecture: A Simple Stack Diagram You Can Show Your Manager
Here's the full Reliability Stack in a single flow you can sketch on a whiteboard or paste into a memo:
The Reliability Stack (alert path that survives a power outage):
Float switch / tank alarm detects high-level condition in wet well
→ TextLight cellular unit receives dry contact signal, runs on backup battery
→ Verizon cellular network, independent of local power and internet
→ SMS delivered to operator phone(s), up to three numbers
The failure chain without the stack (what happens with Wi-Fi only):
Float switch triggers local alarm panel ✓
→ Wi-Fi router attempts to send alert...
→ Router loses power during outage ✗
→ No outbound alert. Station fails silently.
The contrast is the entire argument. One path has a single break point that fails under exactly the conditions that create the emergency. The other path is designed to survive those conditions. Even when each component in a Wi-Fi chain is "usually reliable," the chain is only as strong as its weakest link. The Reliability Stack aims to shorten the chain for critical alarms.
Decision Guide: When You Need the Full Stack (and When You Don't)
Not every station requires the same level of monitoring. Use this checklist to identify which sites are highest priority for a Reliability Stack deployment:
Is the station remote or unattended? If no operator is routinely on-site, a local-only alarm is functionally invisible during off-hours.
Does the station have a history of power interruptions? Repeated outages mean repeated windows of vulnerability.
What are the overflow consequences? Stations that discharge near waterways, residential areas, or environmentally sensitive zones carry higher regulatory and public health risk. The EPA's SSO overview underscores that SSOs can threaten public health and water quality and are treated as regulated discharges — operator awareness is the first line of defense.
Is there on-site staff within 15 minutes? If not, early notification is the only way to shrink response time.
Does the station justify full SCADA expansion? For smaller or more remote stations where extending SCADA infrastructure isn't practical, the Reliability Stack often serves as the right-sized answer — delivering the critical alerting capability without the engineering overhead.
Does existing monitoring have blind spots? Local-only alarms, unstable internet paths, or no redundancy all signal gaps worth closing.
If you checked three or more of those boxes for a given station, that site is a strong candidate for a pilot deployment.
When the stack may be simplified: A lighter approach can be reasonable when the asset is staffed or frequently inspected and local annunciation is reliably observed, when consequences are limited and response windows are generous, or when an existing SCADA layer is already resilient across both power and communications with proven performance. Even in those cases, the key question isn't how much technology is in place — it's whether a single point of failure can create a silent event.
Common Objections (and Clear Rebuttals)
When you bring the Reliability Stack concept to your manager or procurement team, three objections tend to surface. Here's how to address each one directly.
"We can't justify another monthly fee."
The annual subscription for a TextLight unit is $75. Frame that against the cost of a single undetected overflow: emergency crew callout, environmental remediation, regulatory reporting, and potential civil penalties under the Clean Water Act. The penalty structure under 40 CFR Part 19 adjusts for inflation and can reach into the tens of thousands per violation per day. The subscription isn't a line item — it's the operational visibility that prevents a far larger line item.
"We already have SCADA."
SCADA is powerful, but it has dependencies: network connectivity, server uptime, and — critically — station power to run the local RTU and communications equipment. The Reliability Stack doesn't replace SCADA. It operates as a redundant alert layer that survives when SCADA's dependencies fail. The question isn't "SCADA vs. cellular" — it's what happens when SCADA is unavailable or its communications path fails. Think of it as a backup notification path, the same way you'd keep a flashlight even though the building has emergency lighting.
"Cellular won't work in a concrete wet well."
Concrete does attenuate signal, and this is a legitimate concern — not something to dismiss. The practical answer is to treat coverage as a commissioning requirement, not a hope. Place the device at the proposed mounting location and send a test message. The TextLight's enclosure is rated NEMA 4 equivalent for indoor and outdoor use, and its integrated antenna is designed for harsh environments. In many cases, mounting the unit on or near the control panel — above the wet well, not inside it — provides adequate signal. If signal is marginal, an external antenna or adjusted placement typically resolves it. Test at one station before you roll it out to twelve.
Implementation and Testing: The Minimum Reliable Routine
Installing the stack is straightforward — a typical deployment takes one to two hours per station. But installation without verification is just hope with a receipt. Reliability isn't only equipment choice; it's operational discipline. Here's the minimum routine that turns hardware into a reliable system.
Commissioning test (do this on day one):
Simulate a high-level condition by manually triggering the float switch
Confirm the TextLight registers the alarm (LED pulses at 3Hz when in alarm state)
Confirm power-loss alerting behavior during a planned, safe test window
Verify that text messages arrive on all configured phones
Confirm escalation contacts are correct and the message content is clear
Document test results and re-test after any wiring or panel changes
Ongoing verification (quarterly at minimum):
Repeat the alarm simulation to confirm the full alert chain is intact
Check the backup battery status — the device will warn you when battery is low, but proactive checks prevent surprises
Audit the contact list — people change roles, change phone numbers, leave the department
Re-test after storms, electrical work, or panel modifications
Document each test with date, result, and any corrective actions
One PumpAlarm.com customer captured the value of this routine well. Minty J., who monitors a complex water treatment system, described testing the sensors and receiving text alerts in roughly 15 seconds. The result was the kind of assurance that lets you stop lying awake wondering whether a valve has failed or a pressure relief has blown. That peace of mind — knowing you'll hear about the problem before it becomes a disaster — is the operational payoff of the Reliability Stack.
Frequently Asked Questions
Will this connect to my existing float switches?
In most cases, yes. The TextLight accepts a dry contact input, which is the standard output type for float switches used in municipal wet wells. If your station already has functioning floats wired to a local alarm panel, you can connect them to the TextLight without replacing the switches themselves. Compatibility depends on the specific switch type and wiring configuration, so confirm during planning.
Who receives the alerts, and how many numbers can I add?
Alerts can be sent to up to three phone numbers. Each configured number receives the same text message when an alarm triggers. You can set these numbers during activation and update them as staffing changes. Configuration should match your organization's escalation plan rather than personal preference.
What happens during a power outage at the station?
The TextLight switches to its internal 6VDC rechargeable backup battery, which maintains operation for 12+ hours. Because the alert path is cellular — not Wi-Fi — the device can still transmit messages even when station power and local internet are both down. Actual duration can vary with conditions and should be validated during commissioning.
Will cellular work in concrete wet wells, and what if signal is weak?
Concrete can reduce signal strength, but the device is typically mounted on or near the control panel, not submerged in the wet well. The TextLight carries an integrated on-board antenna and is rated for harsh conditions (NEMA 4 equivalent, operating temperature range of -20°F to 150°F). If signal is marginal at a given site, test at the proposed location first. Antenna placement adjustments or an external antenna can improve reception.
Do I need SCADA for this to be useful?
No. The Reliability Stack operates independently of SCADA. It's designed for stations where SCADA expansion isn't practical or where you want a redundant alerting layer that doesn't share SCADA's dependencies. If you already have SCADA, the stack adds a backup notification path. If you don't, it delivers the most critical alerting function — high-level and power-loss notification — as a standalone system.
Your next step depends on where you are in the process. If you're evaluating whether the Reliability Stack fits your stations, the Cellular vs. Wi-Fi comparison breaks down the reliability and redundancy argument in detail. If you're ready to pilot a single station, explore the TextLight Wastewater Level Monitoring Kit to see exactly what's included. For tank-level applications, review the Tank Level Alarm kit. And if you have site-specific questions — signal concerns, wiring compatibility, or deployment planning — reach out to the support team directly.
That 2 AM phone call is only a disaster if it never comes. With the right stack in place, it's just a text message — and the 17 minutes of lead time that keeps an overflow from becoming a headline.
Sources
U.S. Environmental Protection Agency — Sanitary Sewer Overflows (SSOs)
40 CFR § 19.4 — Statutory Civil Monetary Penalties (Inflation-Adjusted)
CISA — Resilient Power Best Practices for Critical Facilities and Sites
Our Editorial Process: Our expert team uses AI tools to help review and analyze information from trusted sources to create helpful, accurate content. All articles are reviewed by our editorial team before publication.
About the Pumpalarm.com Insights Team
The Pumpalarm.com Insights Team is made up of trusted reliability and monitoring experts who specialize in cellular alarm systems, redundancy planning, and real-world emergency prevention. We create practical, operator-focused content to help you prevent disasters before they happen. BBB Business Profile
