16.3 O&M Reports, Regulatory Reports, Compliance, Customer Response & SOP Updates

16.3 O&M Reports, Regulatory Reports, Compliance, Customer Response & SOP Updates

2025 WPI alignment: This section teaches completing operation/maintenance and regulatory reports, ensuring compliance, responding to customers, and establishing/updating SOPs in Security, Safety, and Administrative Procedures, the 15-question area containing 9 recall, 6 application, and 1 calculation item.

Why this responsibility matters

Administrative competence converts plant work into accurate records, required reports, accountable follow-up, useful customer response, and current procedures. Records must be timely, traceable, factual, and consistent with source data.

Core program elements

Work sequence

1. Capture contemporaneous operating and maintenance source data with clear units, instrument/sample identity, status, and initials/electronic attribution.
2. Review daily trends, alarms, work orders, lab/QC, bypasses, chemical inventories, customer contacts, and unresolved actions at shift and supervisory levels.
3. Prepare reports from controlled source records, applying the correct calculations, qualifiers, averaging, and permit definitions.
4. Complete independent review and authorized certification; submit by the governing deadline and preserve receipt/audit trail.
5. Investigate complaints respectfully and safely, communicate verified facts, coordinate field/lab checks, and document closure.
6. Update affected SOPs, drawings, training, alarm responses, and compliance calendar through document control after change or event.

Warning signs and response

Calculation, decision, or documentation connection

Reports may require arithmetic mean, geometric mean, percent removal, loading, inventory, or other relationships. Use the exact permit definition and WPI formula where applicable. Preserve individual daily values when reporting an average and do not substitute zero for a nondetect unless the governing instruction explicitly specifies that treatment. Recalculate from source data during review and document any correction.

Worked supervisory scenario

A monthly report spreadsheet shows 12 mg/L, while the signed laboratory record shows 21 mg/L and the lower number avoids an exceedance. The supervisor stops submission, preserves both records, determines whether the cause is transposition, formula, or improper edit, corrects it transparently, evaluates notification, and strengthens review controls. Changing the lab record would compound the problem.

Common exam traps

• A favorable average does not erase an applicable daily maximum.
• Never change valid source data to make a report fit expectations.
• A customer complaint deserves documented investigation even when the plant initially appears normal.
• Updating an SOP requires approval, revision control, distribution, and training—not simply editing a desktop copy.

Field-to-exam checklist

• Build reports from traceable, reviewed source records and exact permit definitions.
• Maintain a compliance calendar with owners and backup.
• Respond to customers with verified facts, investigation, and documented follow-up.
• Use changes, incidents, and recurring errors to update controlled SOPs and training.

Customer communication boundaries

Acknowledge the concern, collect precise observations, explain what will be checked, and give a realistic follow-up path. Do not speculate about health risk, liability, or cause before evidence and authorized communication are available. Preserve caller details under privacy policy and connect repeated complaints to maps, weather, process events, maintenance, and sampling. Close the loop even when no plant cause is found by documenting the investigation and the verified information provided.

Reporting mechanics and averaging arithmetic

NPDES discharge monitoring reports are submitted electronically under the federal e-Reporting Rule, through NetDMR or an approved state equivalent. The certifying signature belongs to a responsible corporate or municipal official, or to a duly authorized representative whose delegation is on file with the permitting authority — a designation an operator should confirm rather than assume.

Two reporting clocks matter. Standard permit conditions require that noncompliance which may endanger health or the environment be reported orally within 24 hours of becoming aware of it, with a written submission within 5 days unless the permitting authority waives it. Other instances of noncompliance are reported with the next scheduled discharge monitoring report. Anticipated noncompliance — a planned bypass for construction, for example — is reported in advance.

Averaging must match the permit's definition. A monthly average is normally the arithmetic mean of the daily values reported that month. Bacteriological limits are usually geometric means. Percent removal is calculated from the monthly average influent and effluent concentrations, not as the mean of the individual daily percentages — a distinction that can change the reported number.

Worked averaging comparison. Daily BOD results of 12, 18, 9, and 21 mg/L give an arithmetic mean of (12 + 18 + 9 + 21) / 4 = 15.0 mg/L. The geometric mean of the same four values is the fourth root of 12 x 18 x 9 x 21 = 40,824, which is about 14.2. The geometric mean is always the lower of the two for a varying data set, which is exactly why the permit specifies which one applies rather than leaving it to the preparer.

Records are retained at least three years under standard permit conditions — including calibration and maintenance records, original strip-chart or electronic monitoring data, and copies of all reports — and longer if the permitting authority requests it.