In a sewage pump station, a high wet well or imminent overflow alarm is the last-resort warning that inflow is outpacing the pumps and the wet well is filling toward the point where sewage escapes the structure. It sits above the routine high-level alarm and is designed to force human attention before a sanitary sewer overflow reaches the environment. Because a spill is a reportable regulatory event, this alarm is treated far more seriously than a nuisance high level and is usually wired to an automatic operator callout.
Imminent overflow alarm in one line: A high wet well overflow alarm is a critical-priority alarm that activates when the level in a pump station wet well rises near the overflow elevation, indicating that pumping capacity has been exceeded and a spill is imminent. It normally escalates in stages, from a high alarm to a high-high alarm, and triggers automatic notification so an operator responds before sewage discharges.
Most stations use at least two rising setpoints above normal operating range. The first, often called simply the high level, sits above the elevation where all duty and standby pumps should already be running. Reaching it tells operators the station is at or near full pumping capacity and the level is still climbing, which usually points to excess wet weather inflow, a partially blocked pump, or a pump that has failed to start.
The second setpoint, the high-high or overflow-imminent level, sits close to the lowest point at which liquid can escape the wet well, whether through an emergency overflow weir, a nearby manhole, or the top of the structure. Crossing it means the station has run out of margin and a spill is minutes or seconds away. This setpoint is the one that carries the highest priority and drives the most aggressive notification behavior.
The gap between these two levels is deliberately sized to buy response time. Engineers set it using the wet well surface area and the worst-case rate of rise so that an operator alerted at high level has a realistic chance to arrive, clear a blockage, or bring in a bypass pump before high-high is reached. A wet well with a small footprint fills quickly, so the escalation window is short and the callout must be immediate.
A routine high-level alarm is common and often self-clearing. It fires whenever a lag pump is called during a normal peak flow and the level dips again once the extra pump catches up. Operators expect several of these a day at a busy station, so treating every one as an emergency would create alarm fatigue and desensitize staff to the numbers that actually matter.
The imminent overflow alarm is engineered to stand apart from that noise. It is given a distinct, higher priority class, a separate audible and visual annunciation, and frequently a dedicated hardwired float switch that works even if the level transducer or the controller has failed. That redundancy matters because the consequence of a missed alarm here is a permit violation and an environmental release, not just a temporary high reading.
Because the two alarms mean very different things, good pump station design keeps their setpoints, their annunciation, and their response procedures clearly separate. The high level says the station is working hard; the overflow alarm says the station is losing. Confusing the two, or letting the critical alarm hide inside a flood of routine ones, is a recognized contributor to spills that could otherwise have been prevented.
Unstaffed pump stations rely on the alarm reaching a person who is not there. A SCADA or telemetry system watches the level continuously and, on an overflow-imminent condition, initiates an operator callout: a phone call, text message, pager, or push notification to the on-call responder, often with automatic escalation to a second contact if the first does not acknowledge within a set time. Cloud-based monitoring extends this so the alarm and the acknowledgment are visible from any location, not only at a central control room.
The same platform timestamps and logs the event, which is important because regulators require utilities to report sanitary sewer overflows and to document the response. A defensible record of when the alarm fired, when it was acknowledged, and what action followed is often the difference between a well-managed incident and an enforcement finding. Historians retain these events so that recurring near-overflow conditions at a particular station can be identified and addressed with capacity upgrades.
Field operations teams tune the callout logic to their staffing reality. Response drive times, the number of on-call staff, and the rate of rise at each station all feed into how early the callout must go out and how many escalation tiers are needed. The goal is that no imminent overflow alarm ever sits unacknowledged, because at that setpoint the station has already exhausted its automatic defenses and only a human intervention can prevent the spill.
A high-level alarm indicates the wet well is rising and the station is at or near full pumping capacity, and it often clears on its own once a lag pump catches up. An overflow or high-high alarm sits closer to the elevation where sewage can escape the structure, so it signals an imminent spill rather than a busy station. The overflow alarm is higher priority, is often backed by an independent float switch, and triggers an immediate operator callout.
The alarm itself is an internal warning and is not reportable. What must be reported is an actual sanitary sewer overflow, meaning sewage that reaches the ground, a waterway, or a building. Utilities keep the alarm and callout records because they document the response and demonstrate that the operator acted to prevent or minimize a spill, which regulators expect to see after any near-overflow event.
The common causes are inflow exceeding total pumping capacity during heavy rain or infiltration, a blockage such as rags or grease that reduces a pump's output, a pump that failed to start and was not backed up, or a power outage that stopped pumping. Because several of these can occur together, the overflow alarm is designed to fire regardless of the specific cause, so that an operator responds before the level reaches the spill point.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.