1-11 Routine Sample Results including Additional samples and samples triggered by high source water turbidity CFR §141.852 TCR - When routine sample result is entered with either Sampling or on-line SDWIS/STATE Sampling Entry pages Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service Existing SDWIS/STATE functions apply when routine sample result is entered with either SDWIS/XML Sampling or on-line SDWIS/STATE Sampling Entry pages Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service (Primacy agencies continue to maintain standard methods and certification) 1-12 Enter Repeat Samples including dual GWR/RTCR source water samples CFR §141.852 TCR - When repeat sample result is entered with either SDWIS/XML Sampling or on-line SDWIS/STATE Sampling Entry pages, Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service Existing SDWIS/STATE functions apply
1-13 1 TTT tracking-- triggered when routine TC positive, E. coli negative with insufficient repeats tracking CFR §141.859 (a)(1)(iii) GWR – Positive Result Validation process uses Standard Response to create candidate Compliance Activities (type Address Contamination) Compliance Officer uses existing Bridge functions to review, edit, and migrate candidate compliance schedule RTCR-Compliance officer enters Compliance Schedule Activity or, as described in Table 2, the TCR Repeat M/R Compliance Check (Row process creates candidate Level 1 TTT types of Compliance Schedule Activities associated to violation type 2A- LEVEL 1 ASSESS, TC POS RT NO RPT (RTCR) using standard response Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate Compliance Schedule Activity Compliance officer uses existing SDWIS/STATE to update Achieved Date when assessment is conducted ∞ 3.3 Instructions Enabled 1-14 Level 1 TTT tracking-- triggered when systems taking 40 or more (routine and repeat) samples per month, the system exceeds 5.0% total coliform-positive samples for the month or for systems taking fewer than 40 (routine and repeat) samples per month, the system has two or more total coliform-positive samples in the same month. CFR §141.859 (a)(1)(i) and (ii) GWR – Positive Result Validation process uses Standard Response to create candidate Compliance Activities (type Address Contamination) Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate compliance schedule RTCR- Compliance officer enters Compliance Schedule Activity or, as described in Table 2, the Non-Acute MCL Compliance (Row 2-12) process creates candidate Level 1 TTT types of Compliance Schedule Activities associated to violation type 2A- LEVEL 1 ASSESS, MULTIPLE TC POS (RTCR) using standard response Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate Compliance Schedule Activity Compliance officer uses existing SDWIS/STATE to update Achieved Date when assessment is conducted ∞ 3.3 Instructions Enabled
≈ 3.3 Script Enabled 2-6 Failure to speciate Routine Total Coliform TCR - Routine M/R Compliance Check process creates Candidate (TCR), ROUTINE MAJOR RTCR – TCR Routine M/R process creates candidate violation: Instead of a Violation Type (TCR), ROUTINE MAJOR; creates a Violation Type 3D- MONITORING, LAB CERT/METHOD ERROR (RTCR) ≈ 3.3 Script Enabled 2-7 Temporary Routine/Additional Monitoring Compliance CFR §141.860 (c)(1) TCR - Routine M/R Compliance process creates Candidate 23-MONITORING (TCR), ROUTINE type violation Candidate 24- MONITORING (TCR), ROUTINE MINOR type violation RTCR – TCR Routine M/R Compliance process creates candidate violations: Instead of a Violation Type (TCR), ROUTINE creates a Violation Type F- MONITORING, ADD. ROUTINE, MAJOR (RTCR) Instead of a Violation Type (TCR), ROUTINE MINOR MONITORING (TCR), creates a Violation Type 3B- MONITORING, ADD. ROUTINE, MINOR (RTCR) ≈ 3.3 Script Enabled 2-8 Seasonal Period of RTCR Sample Schedule Enforced CFR §141.854 (i)(2)(i) TCR - Sample Result associated to monitoring period associated to water system which falls within sample schedule dates and sample collection dates RTCR – TCR Routine M/R Compliance process enforces TCR sample schedule’s seasonal period and creates candidate monitoring violations as described in Row 2-5 and potentially additional MCL candidate violations and candidate repeat schedules RTCR - Positive Result Validation function: Uses sample result in candidate E. coli MCL compliance determination as described in Row 2-4 Creates candidate repeat TCR sample schedule as described in Row 2-3 MONITORING
when Routine Sample Result is E. coli negative CFR §141.859 (a)(1) & 26- (TCR), REPEAT MINOR Violation 2A- LEVEL 1 ASSESS, TC POS RT NO RPT (RTCR) or 2B- LEVEL 2 ASSESSMENT, 2ND LEVEL 1(RTCR) based on following criteria: If routine monitoring is annual and existing 1 or 2 TTT in previous calendar year; use standard response named ‘LEVEL 2 TTT 2ND LVL 1 IN 2 YR INSUF RPT’ Else, existing Level 1 or 2 TTT in previous 12 months; use standard response named ‘LEVEL 2 TTT 2ND LVL 1 N 12 MN INSUF RPT’ Else use standard response named ‘LEVEL 1 TTT ORIG EC NEG INSUFF REPEATS’ Compliance Officer uses existing SDWIS Bridge functions to review, edit and migrate candidate compliance schedule(s) ∞ 3.3 Instructions Enabled
Else, existing 1 or 2 TTT in previous 12 months; use standard response named ‘LEVEL 2 TTT 2ND LVL 1N12 MN MULT TC POS’ Else; use standard response named ‘LEVEL 1 TTT MULTIPLE TC POS’ Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate compliance Schedule Activity ∞ 3.3 Instructions Enabled Table 3 – Partial Support for RTCR in Existing SDWIS/STATE No. RTCR Activity Existing Function (Partial Implementation) 3-1 Automated addition of Compliance Schedule Activities for Sampling Plans CFR §141.853 (a)(1) Compliance Schedules not automatically created for sampling plans; however can use on-line pages or SDWIS/Migration to State to add Compliance Schedule Activities associated to violation type 5A-Sample Siting Plan Errors (RTCR) ≈ 3.3 Script Enabled
3-8 Automated Compliance determination that water system has monitored at the appropriate location, including specification of a pool of sampling points, establishing frequency of monitoring at each location and compliance determination that monitoring occurred at the designated location CFR §141.853 Use online Sampling Point Maintenance to designate frequency of monitoring at that sampling point Queries may be developed to determine sampling has occurred at required locations and Violation Maintenance used to enter type 5A- Sample Siting Plan Errors (RTCR) ≈ 3.3 Script Enabled 3-9 Automated addition of Compliance Schedule Activities for Seasonal Start-up CFR §141.854 (i)(1) Compliance Schedules not automatically created for seasonal start-up; however can use on-line pages or SDWIS/Migration to State to add Compliance Schedule Activities associated to violation type 2D- Treatment Technique Startup Procedures ≈ 3.3 Script Enabled 3-10 Designation of sanitary defect types of significant deficiencies CFR §141.859 (b) Use SDWIS/STATE System Administration to maintain description of the deficiency type used to denote this is a sanitary defect type of finding. ∞ 3.3 Instructions Enabled
3-12 Consistent with other drinking water rules implemented in SDWIS/STATE, no automated support for violation types categorized as “reporting” violations (no automated support for RTCR type 4* violations) Use SDWIS/STATE online maintenance pages to record Reported Date for Compliance Schedule Activities late Sample Result PWS Notified Date Sample Result State Notified Date Sample Result timestamp Use online Violation Maintenance to type 4A- Reporting, Assessment Forms (RTCR) 4B- Report Sample Result/Fail Monitor RTCR 4C- Report Startup Procedures Cert Form RTCR 4D- Notification, E Coli Positive (RTCR) 4E- Notification, E. coli MCL (RTCR) 4F- Notify L1/L2 TT Vio, Correct Action RTCR Queries can be developed to determine reporting violations for Violation Types: 4A- Reporting, Assessment Forms (RTCR) 4B- Report Sample Result/Fail Monitor RTCR 4C- Report Startup Procedures Cert Form RTCR 4D- Notification, E Coli Positive (RTCR) 4F- Notify L1/L2 TT Vio, Correct Action RTCR ≈ 3.3 Script Enabled
Seasonal Start-up Compliance CFR §141.860 (b)(2) CCR - Schedule Activity Compliance Report Use existing SDWIS/STATE Schedule Activity Compliance Report with RTCR Compliance Schedule type and/or Activity type SDWIS/STATE existing functionality creates appropriate Candidate type 2D- Treatment Technique Startup Procedures RTCR violation associated to Compliance Activity ≈ 3.3 Script Enabled 1-19 Automated addition of Compliance Schedule Activities for Seasonal CFR §141.854 (i)(1) Compliance Schedules not automatically created for seasonal start-up; however can use on-line pages or SDWIS/Migration to State to add Compliance Schedule Activities associated to violation type 2D- Treatment Technique Startup Procedures ≈ 3.3 Script Enabled 3-9 Routine Sample Schedules Schedule Routine Monitoring CFR §141.854(a) and §141.855(a) TCR - Sample Schedule Use existing TCR Sample Schedule maintenance function 1-5 Maintain Routine Monitoring with Inventory Changes CFR §141.854(a) and §141.855(a) TCR - Sample Schedule Evaluation Existing SDWIS/STATE TCR sampling schedule evaluation function continues to propose changes to TCR sampling schedule based on Inventory changes 1-6
Maintain Routine Reduced Monitoring Schedules for Community on Inventory Changes CFR §141.855(d) TCR - Sample Schedule Evaluation Primacy Agencies have the option of modifying Monitoring & Conditions tables to enable reduced quarterly monitoring. Once the tables have been modified, existing TCR sampling schedule evaluation function continues to propose changes to TCR sampling schedule based on Inventory changes. Changes based on non-Inventory criteria (MCL Violation, Treatment Technique Triggers, etc.) are not maintained. 1-7 Maintain Routine Reduced Monitoring Schedules for Non-Community based on Inventory Changes CFR §141.854(e) TCR - Sample Schedule Evaluation Primacy Agencies have the option of modifying Monitoring & Conditions tables to enable reduced annual monitoring. Once the tables have been modified, existing SDWIS/STATE TCR sampling schedule evaluation function continues to propose changes to TCR sampling schedule based on Inventory changes. Changes based on non-Inventory criteria (MCL Violation, Treatment Technique Triggers, etc.) are not maintained. 1-8 Indicate that a PWS is on reduced monitoring GWR – Enter Water System Indicators which are reported with SDWIS/FedRep as Additional PWS Reporting Use SDWIS/STATE System Administration to add new Water System Indicator types and values. Then enter new types of Water System Indicators ≈ 3.3 Script Enabled 1-27
Increase Routine Monitoring Frequency Community to Monthly CFR §141.855 (e)- MCL Viol Queries/reports may be developed to display TCR sample schedules eligible for increased monitoring and Sample Schedule Maintenance used to modify routine TCR sample schedule 2 TTT TT Violation 2 monitoring violations in rolling 12 months ∑ 3.3 Script and Instructions Enabled(including for queries/reports) 4-2 Increase Routine Monitoring Frequency CFR §141.854 to MN Queries/reports can be created to display TCR sample schedules eligible for increased monitoring and Sample Schedule Maintenance used to modify routine TCR sample schedule MCL Viol Level 2 TTT TT Viol 2 monitoring violations in rolling 12 months 1 monitoring violations & 1 Level 1 TTT ∑ 3.3 Script and Instructions Enabled(including for queries/reports) 4-3
Reduce Routine Monitoring Frequency for Community to Quarterly based on changes CFR §141.855(d) and (e) Use existing SDWIS/STATE TCR Sample to modify the Sample Schedule OR use existing SDWIS/Migration to State to update the Monitoring and Conditions table indicators after reviewing results of queries (you may develop to determine if a water system qualifies for reduced monitoring based on following data elements: MCL Violation Level 2 TTT Two Level 1 TTT TT Violation Two monitoring violations in rolling 12 months Loss of Certified operator) 3-3 Reduce Routine Monitoring Frequency for Non-Community to Quarterly based on changes CFR §141.854 (e) and (f) Use existing SDWIS/STATE TCR Sample to modify the Sample Schedule OR use existing SDWIS/Migration to State to update the Monitoring and Conditions table indicators after reviewing results of queries (you may develop to determine if a water system qualifies for reduced monitoring based on following data elements: MCL Violation Level 2 TTT 2 Level 1 TTT TT Violation 2 monitoring violations in rolling 12 months 1 monitoring violation & 1 Level 1 TTT) 3-4 Sample Result Collection and Storage Maintain Monitoring Periods TCR - System Administration Monitoring Period Maintenance Use existing SDWIS/STATE functionality 1-9
Associate Monitoring Periods to Systems to State TCR Compliance Check Online SDWIS/STATE Monitoring Period Use existing SDWIS/STATE functionality to State Online SDWIS/STATE Monitoring/Planning/Associate Monitoring 2A$EPeriod 1-10 Enter Routine Sample Results including Additional samples and samples triggered by high source water turbidity CFR §141.852 TCR - When routine sample result is entered with either SDWIS/XML Sampling or SDWIS/STATE Sampling Entry pages Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service Existing functions apply when routine sample result is entered with either SDWIS/XML Sampling or on-line SDWIS/STATE Sampling Entry pages Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service (Primacy agencies continue to maintain standard methods and certification) 1-11 Enter Repeat Samples including dual GWR/RTCR source water samples CFR §141.852 TCR - When repeat sample result is entered with either SDWIS/XML Sampling or SDWIS/STATE Sampling Entry pages, Laboratory certification processes verify supplied method and certification Results are associated to correct monitoring period Positive coliform result triggers Positive Result Validation web service Existing SDWIS/STATE functions apply 1-12
Lab Certification and Methods Monitoring violations for laboratory certification and/or method (RTCR Violation Type 3D) CFR §141.852 Use SDWIS/STATE online Violation Maintenance Consistent with other drinking water rules implemented in SDWIS/STATE, no automated candidate violation creation support for laboratory certification method error (RTCR Violation Type 3D) as these sample results are rejected by SDWIS/STATE ≈ 3.3 Script Enabled 3-6 Repeat and Additional Sample Schedules Modify Routine Monitoring (Temporary CFR §141.854 (j) TCR - Positive Result Validation determines if system is collecting less than 5 samples per month: Closes current routine schedule, Creates temporary routine schedule for 5 samples the next month, Creates new routine TCR schedule (to return to previous routine monitoring frequency) beginning with following monitoring period RTCR - Positive Result Validation determines if water system is not on monthly monitoring: Closes current TCR routine schedule, Creates temporary/additional routine TCR schedule for 3 samples the next month, and Creates new routine TCR schedule (to return to previous routine monitoring frequency) beginning with following monitoring period 2-2 Additional Monitoring Sample Schedule can be waived or modified CFR §141.854 (j) Use SDWIS/STATE online TCR Sample Schedule Maintenance to modify Temporary/Additional Sample Schedule 3-5
Tracking of triggered routine RTCR coliform sample taken within 24 hours of Source Water Turbidity Sample which exceeds 1 NTU CFR §141.857(c) Use SDWIS/STATE online Violation Maintenance to add/maintain violation for failure to collect a source water coliform sample following a high turbidity sample Use existing SDWIS/STATE to enter Compliance Schedule Activities associated to new RTCR violation type 3C-MONITOR COLIFORM TURBIDITY TRIGGER RTCR Use existing SDWIS/STATE Schedule Activity Compliance Report with RTCR Compliance Schedule type and/or Activity type SDWIS/STATE existing functionality creates appropriate Candidate type 3C-MONITOR COLIFORM TURBIDITY TRIGGER RTCR) RTCR violations associated to Compliance Activity ≈ 3.3 Script Enabled 1-25
Automated Compliance determination that water system has monitored at the appropriate location, including specification of a pool of sampling points, establishing frequency of monitoring at each location and compliance determination that monitoring occurred at the designated location CFR §141.853 Use online Sampling Point Maintenance to designate frequency of monitoring at that sampling point Queries may be developed to determine sampling has occurred at required locations and Violation Maintenance used to enter type 5A- Sample Siting Plan Errors (RTCR) ≈ 3.3 Script Enabled 3-8 Compliance determination that water system has monitored evenly throughout the monitoring period CFR §141.853(a)(2) Queries may be developed to determine sampling has occurred throughout the monitoring period and Violation Maintenance used to enter type 5A- Sample Siting Plan Errors (RTCR) ≈ 3.3 Script Enabled (including for queries/reports) 4-1
Level 1 TTT tracking-- triggered when routine TC positive, E. coli negative with insufficient repeats tracking CFR §141.859 (a)(1)(iii) GWR – Positive Result Validation process uses Standard Response to create candidate Compliance Activities (type Address Contamination) Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate compliance schedule RTCR-Compliance officer enters Compliance Schedule Activity or, as described in Table 2, the TCR Repeat M/R Compliance Check (Row 2-5) process creates candidate Level 1 TTT types of Compliance Schedule Activities associated to violation type 2A- LEVEL 1 ASSESS, TC POS RT NO RPT (RTCR) using standard response Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate Compliance Schedule Activity Compliance officer uses existing SDWIS/STATE to update Achieved Date when assessment is conducted ∞ 3.3 Instructions Enabled 1-13
Level 1 TTT tracking-- triggered when systems taking 40 or more (routine and repeat) samples per month, the system exceeds 5.0% total coliform-positive samples for the month or for systems taking fewer than 40 (routine and repeat) samples per month, the system has two or more total coliform-positive samples in the same month. CFR §141.859 (a)(1)(i) and (ii) GWR – Positive Result Validation process uses Standard Response to create candidate Compliance Activities (type Address Contamination) Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate compliance schedule RTCR- Compliance officer enters Compliance Schedule Activity or, as described in Table 2, the Non-Acute MCL Compliance (Row 2-12) process creates candidate Level 1 TTT types of Compliance Schedule Activities associated to violation type 2A- LEVEL 1 ASSESS, MULTIPLE TC POS (RTCR) using standard response Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate Compliance Schedule Activity Compliance officer uses existing SDWIS/STATE to update Achieved Date when assessment is conducted ∞ 3.3 Instructions Enabled 1-14
Non-Acute MCL Compliance CFR §141.859 (a)(1)(i) and (ii) TCR - Non-acute MCL Compliance creates candidate (TCR), MONTHLY Violations RTCR – Non-acute MCL Compliance no longer creates type 22 candidate violation but instead creates candidate TTT Compliance Schedule Activity associated to violation types 2A-LEVEL 1 ASSESS, MULTIPLE TC POS (RTCR) or 2B- LEVEL 2 ASSESSMENT, 2ND LEVEL 1(RTCR) based on following criteria: If routine monitoring is annual and existing Level 1 or 2 TTT in previous calendar year; use standard response named ‘LEVEL 2 TTT 2ND LVL 1 N 2 YR MULT TC POS’ Else, existing Level 1 or 2 TTT in previous 12 months; use standard response named ‘LEVEL 2 TTT 2ND LVL 1N12 MN MULT TC POS’ Else; use standard response ‘LEVEL 1 TTT MULTIPLE TC POS’ Compliance Officer uses existing SDWIS Bridge functions to review, edit, and migrate candidate compliance Schedule Activity ∞ 3.3 Instructions Enabled 2-12
Assessment Category Evaluation Recording Due to restrictions on changing user interface, unable to display permitted value D - Sanitary Defect as a new value for existing Category Evaluation fields. When a Sanitary Defect is found during Site Visit, user can specify existing permitted value Deficiency (on Category Evaluation fields) with an assessment type of site visit to denote this is a Sanitary Defect. [SDWIS/FedRep 3.4 extracts value stored in SDWIS/STATE Site Visit Category Evaluation field and will to same with SDWIS/FedRep 3.5. However, as “D-Sanitary Defect” is not among list of existing SDWIS/STATE Site Visit Category Evaluation permitted values from which you may select, this value will not be available for SDWIS/FedRep 3.5 to extract.] 3-11 Designation of sanitary defect types of significant deficiencies CFR §141.859 (b) Use System Administration to maintain description of the deficiency type used to denote this is a sanitary defect type of finding. ∞ 3.3 Instructions Enabled 3-10 Sanitary Defect Recording GWR - Site with associated significant deficiencies Use existing Deficiency Maintenance page to enter a significant deficiency associated to site visit RTCR – Due to restrictions on changing user interface, unable to display Sanitary Defect found during Site Visit on Deficiency Maintenance page 1-20
Sanitary Defect Corrective Action Tracking GWR - Apply deficiency standard response to create compliance schedule and associated compliance schedule activity(ies) associated to type 45 violation type Apply existing SDWIS/STATE deficiency standard response to create associated Compliance Schedule Activity(ies) associated to 2C-TT, Corrective/Expedited Actions (RTCR) violation type ∑ 3.3 Script and Instructions Enabled 1-22 Sanitary Defect Corrective Action Compliance Determination GWR - Schedule Activity Report Use existing SDWIS/STATE Schedule Activity Compliance Report with RTCR Compliance Schedule and/or Activity type SDWIS/STATE existing functionality creates appropriate 2C- CORRECTIVE/EXPEDITED ACTIONS (RTCR) type of candidate RTCR violation associated to Compliance Activity ∑ 3.3 Script and Instructions Enabled 1-23 Reporting Violations Tracking of water system notification to the primacy agency that a violation has occurred and compliance determination when a violation is not reported CFR §141.860 (d) Use SDWIS/STATE Violation Comments field of violation to denote notification by the water system to the primacy agency and online Violation Maintenance to enter type 4B- Report Sample Result/Fail Monitor RTCR 4E- Notification, E. coli MCL (RTCR) ∑ 3.3 Script and Instructions Enabled(including for queries/reports) 4-4
Support for Entry/ Maintenance of RTCR Record- Keeping Violation Types listed in Revised Total Coliform Rule Violations + RTC Table October 16, 2014 Use SDWIS/STATE online Violation Maintenance to add/maintain violations for which automated candidate violation creation support is not really possible Use SDWIS/STATE online Violation Maintenance to add/maintain record keeping (type 5B-RECORDKEEPING VIOLATIONS (RTCR)) RTCR violations ≈ 3.3 Script Enabled 1-24 Automated Return to Compliance Use Compliance Schedule Activity or PN Activity Maintenance page to record Achieved Date; when prompted, create the SOX/EOX type of enforcement action Queries can be developed to determine if monitoring and MCL violations have returned to compliance due to on-going monitoring. Use SDWIS/STATE Violation Maintenance to enter the associated Enforcement Action 3-13