In dry weather a lift station handles a predictable trickle of sewage and its control logic is tuned to run pumps gently, alternate them for even wear, and keep energy use low. When a storm hits and rainfall infiltrates the collection system, inflow can multiply within an hour and the same gentle logic can fall behind, letting the wet well climb toward an overflow. Storm-flow mode is an automatic operating mode that detects this high-inflow condition and switches the station's priorities: it raises start levels, brings on every available pump, and accepts higher energy use and rougher cycling in exchange for maximum capacity. When the storm passes and inflow subsides, the station hands control back to its normal, efficiency-minded logic.
Storm-flow mode in one line: Storm-flow mode is an automatic high-inflow operating mode for a pump station that, when it detects rapidly rising level or high inflow, raises pump start levels, calls all available pumps at once, and prioritizes pumping capacity over energy efficiency to prevent an overflow. It differs from normal alternation, which runs one pump at a time and rotates duty for even wear and low cost. As inflow subsides the station automatically hands control back to its normal mode.
The whole point of a distinct storm mode is that the station recognizes wet weather on its own rather than waiting for an operator to react. The most direct trigger is the rate of change of the wet well level: in dry weather the well fills slowly between pump runs, but during a storm the level climbs fast even with a pump running, and that rapid rise is a reliable signal that inflow has jumped. A control can also watch the derived inflow rate, or simply notice that the lead pump cannot pull the well down and the level keeps advancing toward the high alarm despite the pump running continuously.
Level thresholds provide a second, simpler trigger. If the well reaches a high setpoint that it never sees in normal operation, that alone can promote the station into storm mode, on the logic that only a large inflow could push the level that high with pumps running. Some stations combine signals, requiring both an elevated level and a fast rise rate before switching, which avoids false promotions from a brief inflow surge or a single large slug of flow. The design goal is to react early enough to get ahead of the storm but not so trigger-happy that ordinary variations kick the station into its aggressive, energy-hungry mode.
Because inflow to a wastewater system responds to rainfall with a lag and then a long recession, the trigger logic is asymmetric on the way out. The station is quick to enter storm mode when the level surges, but it does not drop straight back to normal the instant the level dips, because a storm's inflow arrives in waves and a premature handoff would leave the station undersized for the next surge. Instead it typically waits until the level and the inflow rate have both settled comfortably back into their normal range for a sustained period before releasing the extra pumps, so the transition back is deliberate rather than twitchy.
In normal operation a multi-pump station is tuned for gentleness and economy. It runs one pump at a time whenever one can keep up, alternates which pump is the lead so wear and running hours spread evenly across the fleet, and stops pumps promptly once the well is drawn down to save energy and reduce start-stop wear. Start levels sit at their ordinary setpoints and the standby pump stays idle in reserve. This is the right strategy for the great majority of the year, when inflow is modest and the priority is long equipment life and a low power bill.
Storm mode inverts those priorities. Instead of one pump, it calls all available pumps, including the standby, so the station runs at its full hydraulic capacity. It raises the start levels so pumps come on sooner and the well has more usable buffer before the level threatens an overflow, and it lets pumps run longer and cycle harder than efficiency would otherwise allow. Energy efficiency and even wear, which dominate normal logic, are deliberately set aside, because during a storm the only thing that matters is moving water fast enough to keep the well from overtopping and causing a sanitary sewer overflow with its environmental and regulatory consequences.
This trade-off is a conscious one, not a malfunction. Running every pump at once costs more energy, stresses the pumps and force main, and concentrates wear, but those costs are trivial next to the cost of an overflow, so the station accepts them for the duration of the event. The distinction is essentially between a station optimized for the great majority of hours that are dry and quiet, and a station optimized for the rare hours when it is fighting to keep up. Storm mode is the mechanism that lets one set of control logic serve both regimes by switching cleanly between them.
Storm mode is fundamentally a supervisory behavior, so it fits naturally into a cloud SCADA layer that sees the whole station and, ideally, the whole network. In a platform such as Merobix the triggers, the raised start levels, and the all-pumps call are configurable per station, and every promotion into and out of storm mode is logged as an event with the level and inflow that caused it. That record lets an operator confirm after a storm that each station reacted when it should have and released its extra pumps only once the surge had truly passed, and it provides the evidence trail that regulators often want after a wet-weather event.
Seeing storm mode across a collection system, rather than one station at a time, changes what an operator can do during the storm itself. When many stations enter storm mode together as a rainfall band moves across the service area, a fleet dashboard shows the wave of high inflow propagating downstream, which gives the operators at the receiving plant advance warning of the load about to arrive and lets them stage capacity ahead of it. A single station's controller cannot see this bigger picture; only a system that aggregates every station's state and inflow can turn a scatter of local storm-mode events into a coherent view of how the network is coping.
After the event, the same trending supports the slower work of understanding and reducing wet-weather load. Comparing how high each station's inflow rose against the rainfall that fell reveals which parts of the system suffer the worst infiltration and inflow, pointing maintenance at leaking pipes and manholes that turn a modest storm into a capacity crisis. Because storm-mode entries, level trends, and inflow estimates are all captured together, a utility can quantify how close each station came to overflowing and prioritize the collection-system repairs that would give the most relief, rather than reacting station by station to whichever one nearly overtopped last.
The most reliable trigger is a fast rate of level rise in the wet well, because during a storm the level climbs quickly even with a pump running, which signals a jump in inflow. Reaching a high level setpoint that never occurs in dry weather can also promote the station, and some designs require both an elevated level and a fast rise before switching. The aim is to react early enough to get ahead of the storm without being kicked into the aggressive mode by ordinary flow variation.
Because during a storm the overriding priority is moving water fast enough to keep the wet well from overflowing, which carries serious environmental and regulatory consequences. Running all pumps at once, including the standby, costs more energy and concentrates wear, but those costs are minor next to the cost of a sanitary sewer overflow. The station deliberately sets aside the efficiency and even-wear goals that dominate its normal logic for the short duration of the event.
It does not drop back the moment the level dips, because storm inflow arrives in waves and a premature handoff would leave the station undersized for the next surge. Instead it waits until both the level and the inflow rate have settled back into their normal range for a sustained period, then releases the extra pumps and resumes single-pump alternation. This makes the transition back deliberate rather than twitchy.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.