Troubleshooting, System Records, and SCADA Basics

Why Troubleshooting, Records, and SCADA Matter

A licensed water or wastewater operator is accountable for keeping safe, reliable service flowing every day. That accountability rests on three connected skills: diagnosing problems quickly from operational data, documenting every action accurately, and using monitoring technology to stay ahead of failures. State licensing exams test all three areas because regulators know that a misdiagnosed pump fault or a missing maintenance record can lead to service outages, contamination events, or regulatory violations.

Structured Troubleshooting

Good troubleshooting is systematic, not random. When a pump or distribution component behaves abnormally, work through a logical sequence rather than guessing.

Step 1 – Gather data. Read all available instruments: pressure gauges, flow meters, motor ammeters, vibration, and temperature readings. Compare current values to the pump's design curve and your system's baseline records.

Step 2 – Define the symptom precisely. "Low flow" is vague. "Flow dropped from 800 gpm to 400 gpm while discharge pressure rose 15 psi" is actionable.

Step 3 – List probable causes. Use your knowledge of how the system works. Common causes of pump problems include:

• Cavitation – suction pressure too low, causing vapor bubbles that collapse violently inside the impeller. Signs: crackling or rattling noise, vibration, reduced flow, pitting damage on impeller over time.
• Air binding – air trapped in the casing prevents the pump from moving water. Signs: pump runs but little or no flow, lower-than-normal amperage.
• Worn impeller or wear rings – reduced flow and head despite normal amperage. Confirmed by comparing actual performance to the pump curve.
• Rapidly cycling pressure switch – a waterlogged or undersized pressure tank causes the pump to start and stop many times per hour, overheating the motor and shortening switch life.
• High motor amperage with low flow – possible causes include a partially closed valve on the discharge side, a mechanical obstruction, or impeller running backwards (wrong rotation after rewiring).
• Unexplained pressure drop in a district meter area (DMA) – suggests an undetected main break, a large unauthorized draw, or a stuck-open PRV.

Step 4 – Test one variable at a time. Check the simplest possibilities first (valve position, strainer plugging) before opening equipment.

Step 5 – Correct and verify. After the repair, confirm the system returns to normal operating parameters and document the outcome.

Safety reminder: Before working on any pump or motor, follow lockout/tagout (LOTO) procedures per OSHA 29 CFR 1910.147. De-energize, isolate, lock, tag, and verify zero energy before opening equipment. Wear appropriate PPE—at minimum, safety glasses and insulated gloves when near electrical panels. Confined-space entry rules apply if you must enter a wet well or vault.

System Records as Legal Documents

Regulators and courts treat operator records as legal documents. A record that is incomplete, altered without explanation, or falsified can result in permit violations, fines, or loss of your operator license. Complete every required field—if a measurement was not taken, write the reason, not a blank space.

Key records every distribution operator maintains:

• Pump maintenance log – dates of inspection, lubrication, seal replacement, bearing temperatures, vibration readings, and who performed the work.
• Valve exercise record – valve ID, location, date exercised, number of turns, direction, condition noted, and any corrective work. Many utilities exercise each valve on a set schedule to prevent seizure.
• Work order – documents a specific task from request through completion: problem description, materials used, labor hours, and final system restoration steps. A main break work order must note the time service was interrupted, which customers were affected, and when pressure was restored—information regulators may require.

Write clearly, use consistent units, and sign and date every entry. Never erase; draw a single line through errors, write the correction, and initial it.

SCADA System Basics

Supervisory Control and Data Acquisition (SCADA) systems use sensors, remote terminal units (RTUs) or programmable logic controllers (PLCs), communication links, and a central human-machine interface (HMI) to give operators a real-time picture of the distribution system.

At a booster station, a typical SCADA screen shows:

• Pump run status (on/off/fault)
• Suction and discharge pressure
• Flow rate
• Motor amperage
• Tank or reservoir level
• Valve position (open/closed/intermediate)
• Active alarms (highlighted, often color-coded)

When an alarm appears, the operator acknowledges it in the HMI—this confirms the alarm has been seen—but acknowledging an alarm does not fix the underlying problem. The operator must then determine what field action is required and either dispatch a crew or take remote corrective action (such as starting a standby pump or adjusting a setpoint) if the system allows.

SCADA does not replace field verification. If the system shows a high-pressure alarm, an operator should confirm with a local gauge before concluding the sensor itself is not faulty. Always treat a SCADA fault alarm as real until field inspection proves otherwise.

SCADA data logs are also official records. Many systems automatically archive readings at set intervals; these logs support compliance reporting and incident investigations.

Linking It All Together

Troubleshooting, record-keeping, and SCADA monitoring reinforce each other. The SCADA system flags an abnormal condition; the operator diagnoses it using operational knowledge and a structured approach; field work corrects it; and the records capture every step. On licensing exams, questions about these topics test whether you can move fluently among all three.