Microplastics reporting is still being written into shape. California’s State Water Resources Control Board has already established a standard method and reporting framework for microplastics in drinking water, and monitoring orders issued under it require supporting water-quality data — turbidity, total organic carbon and related parameters — to be submitted alongside the microplastics results. Whatever the jurisdiction, the reports that hold up combine laboratory concentration values with a defensible record of the continuous barrier signals a plant maintained between laboratory events. Continuous sensor data does not replace laboratory measurement, but it is often what an auditor asks for when the question is whether the reported concentration was representative of ordinary operation or an unusual sampling day.
Turbidity, suspended solids and, where relevant, transmembrane pressure form the core of that sensor-side package. Shanghai ChiMay’s application team has helped drinking-water and reuse operators structure it to satisfy both internal quality officers and external regulators.
Table of Contents
The Two Questions a Compliance Report Actually Answers
When a regulator reads a microplastics compliance report, they are trying to answer two questions. The first is straightforward: what was the measured concentration in the finished water? The second is harder: was that measurement representative of how the plant was actually running? Laboratory data answers the first. Sensor data — organised, retained and referenced — answers the second.
Operators who prepare only for the first question find themselves scrambling when auditors ask the second. Sensor data that was collected but not curated, not time-aligned with the sampling event, or not paired with instrument calibration records adds little and can raise questions the operator did not intend to invite.
Core Sensor Streams to Include
Not every process signal belongs in a microplastics compliance report. The streams that do are the ones describing the barrier and its recent behaviour:
- Turbidity on finished water and permeate lines — the primary continuous surrogate for particulate barrier integrity.
- Suspended solids on MBR and membrane pretreatment lines — a complementary indicator that captures the coarser end of the size distribution.
- Transmembrane pressure and flow across ultrafiltration or nanofiltration racks — hydraulic evidence of membrane condition, which correlates with turbidity trends.
- Conductivity and pH on advanced oxidation loops — evidence that chemical barrier steps were operating inside their design envelope.
Each stream should be reported at a resolution fine enough to see event-scale changes. One-minute values retained for at least ninety days around any microplastics sampling event is the working recommendation.
Metadata That Makes Sensor Data Defensible
Raw trends are not enough. Regulators expect the following metadata alongside each stream:
- Instrument identity — make, model and serial number of the sensor.
- Calibration record — dates of the last two calibrations and the standards used.
- Firmware version — the version running during the reporting window.
- Sampling location — with a piping-and-instrumentation diagram reference.
- Alarm history — every excursion during the reporting window and the operator’s response.
Without this metadata, a trend can be dismissed as anecdotal. With it, the trend becomes evidence. Shanghai ChiMay’s sensor gateway stamps its output with the first four items automatically; the alarm history comes from the plant SCADA or historian.
Time Alignment with Laboratory Samples
The single most common weakness in a microplastics compliance report is a lab result reported to the minute next to a sensor trend reported to the day. A regulator reading such a report cannot verify that the sample was drawn under typical conditions. The remedy is time alignment: every laboratory result paired with a sensor snapshot covering at least the twenty-four hours before and after the sample was taken.
This is a low-cost practice — most historians can produce the snapshot in seconds — and it upgrades the report from “here is what we found” to “here is what we found, and here is why that finding is representative”.
Baseline Documentation
Regulators increasingly ask for a baseline: a description of the plant’s ordinary sensor behaviour — rolling means, standard deviations, characteristic response to weather, seasonal patterns — over a defined period. The baseline lets an auditor judge whether the sampling day was ordinary or unusual.
For turbidity and suspended solids, a rolling ninety-day baseline that is refreshed every quarter, or whenever a process change occurs, is a workable standard. The baseline belongs in the compliance report, not in an internal folder.
Excursion Handling
Every plant sees excursions. What matters for a compliance report is not their absence but their documentation. For each excursion during the reporting window, the report should include:
- Start and end time.
- Peak and duration of the deviation.
- Root-cause conclusion, or an open item if the investigation is ongoing.
- Corrective action.
- Whether any laboratory sample was drawn during the excursion, and its result.
An excursion closed cleanly, with a documented cause and correction, strengthens a compliance report rather than weakening it.
What Should Not Be in the Report
Two categories of data should generally stay out:
- Unrelated process signals — flow rates on ancillary loops, ambient temperature and similar streams add noise without adding evidence.
- Legacy sensor data from decommissioned instruments — unless a specific investigation calls for it, historical streams from replaced sensors confuse auditors.
The report should be lean, targeted and defensible. Shanghai ChiMay’s template, available to customers on request, reflects that discipline.
Data-Layer Integration
The practical work of producing a compliance report falls to whoever manages the plant historian. Two integration points matter:
- Read access for compliance staff — the historian should expose the relevant streams to compliance officers without requiring them to navigate plant SCADA.
- Export format — regulators are converging on CSV or Parquet with time-stamped records; PDF-only exports slow their review.
Shanghai ChiMay sensors expose data via Modbus RTU/TCP and OPC UA, which lets the historian build those export paths cleanly.
Closing Note
A microplastics compliance report succeeds when its laboratory numbers are surrounded by a curated, well-documented layer of sensor evidence. The guidance above reflects what we have seen work in practice, on plants that have already faced formal microplastics scrutiny. The rules are still being written, but the shape of what regulators want is already clear.
