SCADA, standby power, emergency pumping, bypass setup, and incident documentation

SCADA and Alarm Response

Supervisory control and data acquisition (SCADA) gives operators remote visibility into wet well level, pump status, alarms, run times, flow, generator status, intrusion, and sometimes discharge pressure or valve position. A programmable logic controller (PLC) or remote terminal unit (RTU) handles local control and reports to SCADA over radio, cellular, or fiber. SCADA is an aid, not a substitute for judgment or for verified field data.

Learn the common alarm categories: high wet well, low wet well, pump fail, motor overload, phase loss, power fail, generator running, generator fail, communication fail, intrusion, and high discharge pressure. A communication failure is not proof the station is normal — it means the operator may have lost visibility into high-level, power-fail, or pump-fail conditions, which is most dangerous during wet weather when inflow peaks.

Standby Power

Pump stations need standby power because a power loss can become a sanitary sewer overflow (SSO) within minutes once the wet well fills. Generator readiness is more than having a generator on site:

Many utilities also keep a manual transfer switch and a generator receptacle so a portable/towable generator can be connected if the permanent unit or ATS fails. Generators are typically exercised under load weekly or monthly and fuel is kept treated and topped off, because stale diesel and a dead starting battery cause far more failed starts than engine wear. After any work on the service or a phase swap by the utility, verify pump rotation before relying on the station — a reversed phase can leave a pump running smoothly while moving almost no flow, which masquerades as a clog on SCADA.

Know the difference between an automatic transfer switch (ATS), which senses the outage and starts and transfers without an operator, and a manual transfer switch, which requires someone on site. A station on a manual switch with no operator nearby during a storm is effectively unprotected, so dispatch priority and response time become part of the overflow-prevention plan, not just the hardware.

Emergency Pumping and Bypass Setup

Emergency conveyance may use portable pumps, vacuum trucks, tanker hauling, or a permanent bypass connection. The setup must keep wastewater contained and must not create a second hazard. A practical bypass plan includes:

• Suction access with screened suction or debris management.
• Pump capacity sized for the expected peak inflow, with a backup unit and adequate fuel.
• Discharge hose routing with restraints at fittings to resist surge thrust.
• Traffic control, spill containment, noise control, and public-access control.
• A discharge point that returns flow to a downstream manhole, force main connection, or treatment facility.

Discharging to a storm drain, ditch, gutter, or waterway is never an acceptable shortcut — that converts a controlled bypass into a reportable SSO with environmental and permit consequences.

Incident Sequence and Documentation

For a station failure or SSO threat, the operator sequence is:

1. Protect people — electrical hazards, traffic, confined spaces, public exposure, site security.
2. Verify the condition — actual level, pump operation, power and generator status, valve positions, and any visible overflow path.
3. Keep flow moving — restart available equipment, start the lag pump, transfer to standby power, deploy bypass pumps, or dispatch vacuum trucks.
4. Contain wastewater — block storm drains, berm and recover sewage where possible, disinfect affected hard surfaces per local procedure, and keep the public away.
5. Notify internally and externally per the utility's discharge permit, state rules, and emergency response plan (many states require initial verbal notice within a set window such as 24 hours).
6. Document the facts — alarm time, arrival time, cause, estimated volume, affected area, receiving water if any, photos, weather, corrective actions, cleanup, notifications, and repair work orders.

Exam traps include resetting the alarm before investigating, waiting to finish paperwork before stopping a discharge, assuming remote status equals actual flow, and skipping documentation because the overflow "was small." Whenever wastewater leaves the system, notification and reporting requirements are driven by the utility's permit and the state agency, not by the operator's judgment of severity.

Estimating Spill Volume

Exam scenarios often ask the operator to estimate an overflow so it can be reported. Two field methods recur. The duration-and-flow method multiplies an estimated overflow rate by the time the overflow ran: if a manhole surcharged at an estimated 50 gallons per minute for 30 minutes, the spill is about 1,500 gallons. The measured-area method estimates the ponded area and average depth, then converts cubic feet to gallons using 7.48 gallons per cubic foot — a 200-square-foot puddle averaging 0.1 foot deep holds roughly 150 gallons.

Document the method and assumptions; a defensible estimate with stated assumptions is acceptable, but a guessed number with no basis is not.

SCADA Security and Data Integrity

Modern SCADA is also a cyber-physical system. Operators keep remote-access credentials controlled, watch for unexplained setpoint or alarm changes, and never assume a screen value is correct if it conflicts with field observation — a frozen or spoofed value reads "normal" while the well overflows. Set reasonable alarm dead-bands and delays so nuisance alarms do not get silenced out of fatigue, because a silenced channel is the same blind spot as a communication failure. The discipline is identical across the chapter: the instrument supports the decision, but verified field reality governs the response.