<\/span><\/h2>\nSilent calibration expiry:<\/strong> a sensor whose calibration expired 45 days ago continues to feed the dosing controller. The controller has no way to know its inputs are stale, and dosing decisions slowly detune.<\/p>\nUndocumented field intervention:<\/strong> a field technician performs an emergency recalibration without recording the standards used. The traceability chain is broken and the sensor is no longer defensible under audit.<\/p>\nMismatched reference chemistry:<\/strong> a pH electrode calibrated with buffers that do not match the process ionic strength. Field readings drift by 0.1\u20130.3 pH units and the dosing loop over-corrects.<\/p>\nStandard aging:<\/strong> the calibration standards themselves have expired or degraded, and every calibration performed against them is subtly wrong.<\/p>\n<\/span>Instrument Design Choices That Support Traceability<\/span><\/h2>\nInstrument suppliers can support traceability at the register level:<\/p>\n
\n- Store the calibration date, calibration standards, and calibrating technician in on-board memory.<\/li>\n
- Expose calibration age as a Modbus register or a status flag.<\/li>\n
- Refuse to enter run mode after a calibration that failed internal quality checks.<\/li>\n
- Provide standardized calibration procedures with clear acceptance criteria.<\/li>\n<\/ul>\n
Shanghai ChiMay’s pH electrode, residual chlorine transmitter, and dissolved oxygen transmitter models expose calibration age and calibration quality flags on documented registers, so autonomous dosing controllers can gate their inputs without custom middleware.<\/p>\n
<\/span>Governance Framework for Autonomous Dosing<\/span><\/h2>\nWater plants running autonomous dosing typically adopt governance rules such as:<\/p>\n
\n- Calibration no less frequently than every 90 days for anchor sensors, or every 30 days for high-consequence variables such as chlorine residuals.<\/li>\n
- Every calibration event producing a signed digital record stored alongside the sensor’s data stream.<\/li>\n
- Autonomous actuation suspended when calibration age exceeds the governance threshold.<\/li>\n
- Random audits by an independent QA function verifying that the traceability chain is intact.<\/li>\n<\/ul>\n
<\/span>Calibration Regimes Compared<\/span><\/h2>\nUtilities generally adopt one of three calibration regimes:<\/p>\n
\n- Calendar-based:<\/strong> every sensor is calibrated on a fixed schedule regardless of condition. Simple to plan, but often replaces calibrations with meaningful drift by calibrations with no drift.<\/li>\n
- Condition-based:<\/strong> the sensor is calibrated when its self-diagnostic drift estimate crosses a threshold. Optimal in labour terms, but requires trustworthy diagnostics.<\/li>\n
- Event-based:<\/strong> the sensor is calibrated after specific events such as maintenance, cleaning, or process upsets.<\/li>\n<\/ul>\n
Modern deployments combine all three: a calendar backbone every 90\u2013180 days, condition-based triggers, and event-driven interventions. That combination yields the lowest lifecycle risk under autonomous dosing.<\/p>\n
<\/span>Practical Field QA Workflow<\/span><\/h2>\nA well-run field QA workflow for autonomous dosing includes:<\/p>\n