Section 64256 - Sampling and Monitoring(a) A local primacy agency shall notify each small water system under its jurisdiction in writing of the monitoring requirements for that system pursuant to Title 22, Division 4, Chapters 15, 15.5, 17, and 17.5 of the California Code of Regulations. The notice shall identify the specific contaminants to be monitored, the type of laboratory analyses required for each contaminant, the frequency of sampling and any other sampling and reporting requirements applicable to that system.(b) A local primacy agency shall ensure that each small water system under its jurisdiction complies with the sample siting plan requirements of section 64422.(c) A local primacy agency shall establish a tracking system to assure that all required sampling and laboratory analyses are completed and reported by the small water systems pursuant to Title 22, Division 4, Chapters 15, 15.5, 17, and 17.5 of the California Code of Regulations. The tracking system shall include the date the sample was collected, the type or purpose of the sample, and the laboratory result.(d) A local primacy agency shall maintain an ongoing record of the status of compliance with monitoring and reporting requirements of California Code of Regulations, Title 22, Division 4, Chapters 15, 15.5, 17, and 17.5 of each small water system.(e) A local primacy agency shall establish a system to assure that the water quality monitoring data submitted by the small water systems is routinely reviewed for compliance with the requirements of Title 22, Division 4, Chapters 15, 15.5, 17, and 17.5 of the California Code of Regulations. The monitoring reports shall be reviewed each month for each small water system and the data entered into the data management system at least monthly.Cal. Code Regs. Tit. 22, § 64256
1. New section filed 4-2-93 as an emergency; operative 4-2-93 (Register 93, No. 14). A Certificate of Compliance must be transmitted to OAL 8-2-93 or emergency language will be repealed by operation of law on the following day.
2. Certificate of Compliance as to 4-2-93 order transmitted to OAL 7-29-93 and filed 9-8-93 (Register 93, No. 37).
3. Amendment of subsections (a), (c)-(e) and NOTE filed 12-11-95 as an emergency; operative 12-11-95 (Register 95, No. 50). A Certificate of Compliance must be transmitted to OAL by 4-9-96 or emergency language will be repealed by operation of law on the following day.
4. Refiling of 12-11-95 order, including amendment of NOTE, filed 4-9-96 as an emergency; operative 4-10-96 (Register 96, No. 15). A Certificate of Compliance must be transmitted to OAL by 8-8-96 or emergency language will be repealed by operation of law on the following day.
5. Certificate of Compliance as to 12-11-95 order transmitted to OAL 8-7-96 and filed 9-16-96 (Register 96, No. 38).
6. Amendment of section and NOTE filed 5-22-2012; operative 6-21-2012 (Register 2012, No. 21). Note: Authority cited: Sections 116350, 116375, 131052 and 131200, Health and Safety Code. Reference: Sections 116330, 116375, 116385 and 116400, Health and Safety Code; and 40 Code of Federal Regulations 141.
1. New section filed 4-2-93 as an emergency; operative 4-2-93 (Register 93, No. 14). A Certificate of Compliance must be transmitted to OAL 8-2-93 or emergency language will be repealed by operation of law on the following day.
2. Certificate of Compliance as to 4-2-93 order transmitted to OAL 7-29-93 and filed 9-8-93 (Register 93, No. 37).
3. Amendment of subsections (a), (c)-(e) and Note filed 12-11-95 as an emergency; operative 12-11-95 (Register 95, No. 50). A Certificate of Compliance must be transmitted to OAL by 4-9-96 or emergency language will be repealed by operation of law on the following day.
4. Refiling of 12-11-95 order, including amendment of Note, filed 4-9-96 as an emergency; operative 4-10-96 (Register 96, No. 15). A Certificate of Compliance must be transmitted to OAL by 8-8-96 or emergency language will be repealed by operation of law on the following day.
5. Certificate of Compliance as to 12-11-95 order transmitted to OAL 8-7-96 and filed 9-16-96 (Register 96, No. 38).
6. Amendment of section and Note filed 5-22-2012; operative 6-21-2012 (Register 2012, No. 21).