SANS 241 month-end reporting without the spreadsheet

Most works managers already know SANS 241 from the month-end compliance pack: laboratory results, sampling points, and the spreadsheet that still ties them to what the plant was doing online. What often lags is not the standard — it is getting plant and lab data into one report without copy-paste from SCADA.

What the pack actually needs

A useful water data stack typically covers:

• Continuous process measurements from instruments and PLC/SCADA — turbidity, chlorine residual, flows, levels
• Laboratory results in the same workflow as the online tags, not a second spreadsheet
• Gaps flagged so a missing sample or a dead instrument shows up before month-end
• Reporting that operators and the compliance team can open without rebuilding the numbers

Long-term tag retention helps investigations. It is not the first thing to buy if the month-end pack is still assembled by hand.

What the month-end pack needs from the plant

The compliance pack is not only laboratory results. Turbidity, chlorine residual, flows and alarms from SCADA need to sit beside lab data — with gaps flagged — so problems show up before the spreadsheet is due, not after.

LCT builds that workflow from your tags and lab inputs. We do not replace the utility's compliance officer.

Practical next step

If your water works already has SCADA but the month-end pack is still manual, start with a narrow pilot: the critical quality tags, lab inputs in the same workflow, and one automated daily or weekly report. Add historian storage only when SCADA retention or query speed becomes the limit. Expand after operators trust the numbers.

This is the work we do on water and wastewater sites; the reporting workflow is covered under industrial reporting. Consider a TDengine Historian evaluation only when retention, query speed or tag growth is the actual bottleneck.