The 'Small Station' Strategy: Monitoring Assets That Don't Justify SCADA

The wet well is rising. 

It's 2:17 AM, a Thursday in March. Rain has been falling for six hours straight. Your phone is silent. The duplex station on Route 9—the one without monitoring—just lost power. Nobody knows yet. By morning, raw sewage will be pooling in the ditch beside the elementary school parking lot. 

You've seen this scenario before, or something close to it. The big stations have SCADA. They report every pump cycle, every level change, every fault. But the smaller sites—the ones with two pumps and a float switch, the ones you drive past once a week—sit in the dark. If something goes wrong out there, how would we even know? 

That's the gap this framework closes. With a simple tiering approach, you can match every station in your system to a proportional monitoring solution—SCADA where it earns its keep, and cellular alarm/monitoring devices where the goal is eliminating silent failures. The result isn't a downgrade. It's a strategy that gives your entire network visibility without burying your team in complexity. 

A tiered monitoring strategy classifies each station by its criticality, complexity, and control requirements, then assigns SCADA to high-consequence sites and cellular alarm/monitoring devices to smaller or remote assets where essential alert visibility—not full control—is what matters. 

Start Here: The Station Tiering Matrix 

Before debating technology, standardize the decision itself. The Station Tiering Matrix gives your team a repeatable way to classify every asset in the collection system, so monitoring choices follow consistent criteria instead of institutional habit. 

You can classify most stations in about three minutes by working through four questions. How quickly does a problem at this site become a service impact or potential overflow? Does the site require real control logic, sequencing, or remote setpoints? Does it need to feed a central SCADA historian or dashboard with tight integration standards? And is there staff time to maintain and troubleshoot a larger telemetry footprint? The answers will point clearly toward a tier. 

Here's how it works in practice. Picture a small duplex lift station at the edge of your service area—two pumps, gravity-fed, serving 43 residential connections. It runs on simple float control. Your crew visits once a month. There's no VFD, no flow meter, no integration with the treatment plant. That station doesn't need SCADA's telemetry and trending. What it needs is a text at 2 AM when the power drops or the wet well hits high level. That's a Tier 3 site. 

Now picture a different scenario: a remote duplex station with long travel time, minimal controls, and a history of after-hours callouts. The consequence of failure is moderate, not catastrophic—but the response burden is real. That station lands in Tier 2, because rapid alerts matter more than remote control. 

What Tier 1 Looks Like (When SCADA Is Justified) 

SCADA—Supervisory Control and Data Acquisition—is, according to NIST's definition, a computerized system capable of gathering data and applying operational controls over long distances. It's powerful. It's also built for complexity. 

A station justifies SCADA when you'll actually use those capabilities: remote pump control, VFD speed adjustments, flow totalization feeding back to the treatment plant, historical trending for capacity planning. Think of your main lift stations—the ones moving millions of gallons daily, serving large drainage basins, requiring real-time operator interaction. 

SCADA also carries a lifecycle footprint. Integration with your existing network, ongoing software licensing, PLC maintenance, cybersecurity considerations, and the instrumentation and communications infrastructure to support it all come with the territory. A joint advisory from CISA and the EPA (December 2023) has highlighted that internet-exposed human-machine interfaces in water and wastewater systems create additional security surfaces that must be managed. NIST SP 800-82r3 reinforces that operational technology environments carry distinct security requirements—each connected endpoint adds to that surface. For a high-consequence station with real control needs, that overhead is justified. For a two-pump station on a gravel access road, it's disproportionate. 

What Tier 2 and Tier 3 Look Like (When Alerts Are the Priority) 

Essential visibility doesn't mean full control. For Tier 2 and Tier 3 stations, the question isn't "Can we adjust pump speed remotely?" It's simpler and more urgent: "Will someone know if this station fails at 3 AM on a Saturday?" 

The core signals for these tiers typically include high wet well level (a direct indicator of rising risk), power loss (a leading driver of station downtime), and a pump fail proxy—which varies by site but might include runtime anomalies, motor current indication, or alarm relay states. Exact signal selection depends on station design and existing instrumentation. The practical test is straightforward: when the station is unattended, do the alerts provide enough information to trigger the right response without repeated trial-and-error site visits? 

Tier 2 (Alarm-Visibility) sites carry moderate risk. They need reliable, immediate alerts—high wet well level, pump fault, power loss—but don't require the operator to control anything remotely. A cellular alarm/monitoring device delivers those signals via commercial carrier networks directly to a phone, eliminating the need for user-maintained local network infrastructure, dedicated PLC hardware, or custom software integration. 

Tier 3 (Coverage / Blind-Spot) sites are even simpler. These are the stations your crew visits once a month, the ones at dead-end roads or rural edges of the system. The monitoring goal is binary: is this station running, or isn't it? Power-loss detection and a high-level alarm are typically enough to eliminate the blind spot. 

The operational difference between the two tiers matters. Tier 2 alerts are expected to drive after-hours response with minimal ambiguity—the crew knows what's wrong and what to do. Tier 3 alerts primarily eliminate unknown status at sites that would otherwise go unmonitored, with the simplest configuration that still provides actionable notice. 

For level detection hardware, common approaches include float-based or level-sensing arrangements depending on wet well configuration and maintenance preferences. A High Water Level Alarm setup paired with the right wastewater float switch components can address the level-visibility gap at many smaller stations. Where level is the primary monitoring need, a tank level alarm may be the most direct fit. 

The EPA estimates that tens of thousands of sanitary sewer overflows occur annually in the U.S., with lift station mechanical or power failures among the documented causes. Many of those overflows happen at smaller stations where nobody received an alert in time. That's the gap Tier 2 and Tier 3 monitoring closes—not with control, but with coverage. 

The Hybrid Model: Standardize Monitoring Across the Whole Network 

Rolling out a hybrid model doesn't require a capital project. It requires a decision framework and a sequence. 

Inventory your assets. List every station, wet well, and remote asset. Include visit frequency, pump configuration, current monitoring status, known failure modes, and where alerts currently go—if anywhere. Document who owns the response. 

Tier each site. Apply the matrix. Be honest about which stations actually use SCADA's control features versus which ones just happen to have it. Document the reason for each tier assignment; that record helps with internal alignment later. 

Define standard signal sets. For Tier 1, instrument and integrate per your SCADA standards. For Tier 2, lock in essential alerts: high level, power loss, and a pump fail proxy where applicable. For Tier 3, define minimum coverage—often level and power loss. 

Pilot one or two stations. Pick a representative Tier 2 site and a Tier 3 site. Install. Confirm alert delivery. Validate power-loss behavior. Verify the escalation path works. Run it for 30 days. 

Scale and document. Once the pilot confirms the alert path works, roll the standard configuration across remaining Tier 2 and 3 sites. Use standardized naming, recipient lists, and acceptance tests to keep configuration consistent and reduce operational burden. Document each classification for your asset management records. 

This documentation matters. When a council member or supervisor asks why Station 14 doesn't have SCADA, your answer isn't a debate—it's a matrix classification with clear criteria behind it. Standardize the decision, not the debate. 

Implementation Checklist for Small Stations 

Before deploying a cellular alarm/monitoring device at a Tier 2 or 3 site, confirm these prerequisites: 

• Alert conditions: Confirm what conditions must generate alerts—high level, power loss, pump fail proxy—based on the station's tier classification and available instrumentation. 

• Sensor inputs: Identify which alarm contacts are available—high-level float, pump fault relay, intrusion switch, level sensor. Match them to the device's input capacity. 

• Power and enclosure: Verify 120V availability at the control panel. Confirm that the monitoring device has backup battery capability so it can report power-loss events. Account for mounting location, environmental exposure, and clear line-of-sight considerations for the cellular antenna. 

• Cellular signal: Test signal strength at the site before committing. Rural and below-grade stations can present connectivity challenges—an external antenna may resolve marginal coverage. 

• Alert recipients and escalation: Confirm primary and backup recipients, including after-hours rules. 

• Acceptance test: Once installed, run a simple verification. Trigger each alarm input manually and confirm the alert arrives at the intended recipients. Simulate a power loss and confirm the power-loss notification fires—verify this behavior matches vendor documentation, since power-fail reporting latencies vary by device. Check that "return to normal" behavior, if configured, does not create unnecessary alert noise. That walkthrough saves you from discovering a configuration gap during an actual event. 

• Station log: Record the results—configuration summary, recipient list, test date, and responsible owner. Keeping acceptance testing consistent across stations is one of the fastest ways to reduce long-term troubleshooting and keep operators confident in their alerts. 

Common Objections (and Neutral Responses) 

"We should just put SCADA everywhere." You could. But SCADA carries integration, licensing, maintenance, and cybersecurity overhead at every site. As noted earlier, expanding your OT footprint increases your attack surface. Every new SCADA endpoint requires distinct security management under NIST frameworks, creating a maintenance tail that simple monitoring devices avoid. For a station with two pumps and no control needs, that overhead is disproportionate to the risk. Proportional monitoring means matching the tool to the job. 

"The recurring connectivity cost isn't justified." Consider what a single undetected overflow costs—emergency response, regulatory reporting, environmental remediation, public trust. A recurring cellular connection fee is a fraction of one after-hours emergency dispatch. The tiering matrix ensures this same logic is applied consistently across the system, framing the cost as risk-weighted operational coverage rather than a line-item expense. 

"Cellular alerts aren't real monitoring." They're not meant to replace your SCADA system. They're a coverage layer, not a control layer. The goal at Tier 2 and 3 sites isn't trending or analytics—it's making sure a silent failure doesn't stay silent. Two different jobs, two right-sized tools. 

What to Do Next 

You now have a framework you can apply to every station in your system this week. Start by running your full asset inventory through the Station Tiering Matrix. Classify each site. Identify your blind spots—the stations with no monitoring and no regular visit schedule. Those are your Tier 2 and Tier 3 candidates. 

Then pick one. Run a pilot at your most obvious blind-spot site. Install a cellular alarm/monitoring device, verify the alert path with a simple acceptance test, and let it run for 30 days. That one station will tell you more about the value of coverage-layer monitoring than any spec sheet ever could. 

The goal for small sites is essential visibility, not full control. Get that visibility in place, and your network stops whispering. It starts reporting. 

For broader regulatory and risk context around overflows, the EPA provides an overview of sanitary sewer overflows and common causes, including operational and system issues. 

Disclaimer: This article is intended for informational and educational purposes only. It does not constitute engineering, regulatory, or procurement advice. Consult your system's engineering standards and local regulatory requirements before making monitoring or infrastructure decisions.