1 / 36

SDWIS Prime & Compliance Monitoring Data Portal

Learn about the SDWIS Prime & Compliance Monitoring Data Portal and its success in improving data management, reducing errors, and increasing efficiency in monitoring drinking water quality. Highlights from the past year and upcoming priorities will be discussed, including updates to method-analyte pairings, training, additional sample validations, and operational data improvements.

brentmccoy
Download Presentation

SDWIS Prime & Compliance Monitoring Data Portal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SDWIS Prime & Compliance Monitoring Data Portal Association of State Drinking Water Administrators, March 26th 2019 Michael Plastino, Infrastructure Branch Chief Tina Chen, SDWIS Prime / CMDP Team & Project Lead Justin Wright, SDWIS Prime Transition Lead Patti Fauver, SDWIS Prime Product Owner

  2. Thank You!Pilot / UAT Group • AK – Maria Ridgeway -> Marci Irwin • CT – Chris Roy • ID – Monica Van Bussum • IN – Sara Pierson • NH – Leah McKenna • NV – Linh Kieu • PA – Jason Minnich • UT – Colt Smith, Patti Fauver • ASDWA – Anthony DeRosa, Darrell Osterhoudt • EPA Region 7 – Jay Hua

  3. Thank You!Interfacing Applications Work Group OR - Chuck Michael TX - Jonathan Haynes UT - Colt Smith VA - Christine Harrison ASDWA - Anthony DeRosa ECOS - Kurt Rakouskas EPA Region 5 - Cary McElhinney EPA Region 6 - Mark McCasland EPA Region 8 - Shirley Mlachak • AK - Tom Stock • ID - Troy Rademacher • LA - Johan Forsman • NC - Eric Chai • ND - Barrett Brown (State Co-Chair) • NH - Leah McKenna • NJ - Mike Matsko, Freddie Grier • NM - Richard Asbury • OH - Brian Tarver • OK - Steven Wright

  4. Thank You!ASDWA Data Management Advisory Committee • ID - Monica Van Bussum • MA – Damon Guterman • MT – Manley Byrne • ND - Barrett Brown • OR – Chuck Michael • UT – Rachael Cassady (State Co-Chair) • ASDWA – Darrell Osterhoudt, Anthony DeRosa • EPA Region 5 – Kris Werbach • EPA Region 9 – Karl Banks

  5. EPA Prime/CMDP Team • Tina Chen (DWPD/IB) - Prime/CMDP Team Lead / Project Lead • Elinor Keith (OW PMO) - Prime/CMDP Acting Project Manager • Patti Fauver (DWPD/IB on ½ time detail from UT) – Prime Product Owner • Deric Teasley (DWPD/IB) - CMDP Lead, Prime/CMDP Support Procurement Lead • Justin Wright (DWPD/IB) – Prime Transition / Pilot Group / Interfacing Applications • Trang Le (DWPD/IB) – Prime/CMDP Transition Blanket Purchase Agreement • Renee Morris (DWPD/IB) – Prime/CMDP Data Migration Lead, DMAC • Alex Porteous (DWPD/IB) – Prime/CMDP Data Migration Support, DMAC, Outreach • Towana Dorsey (DWPD/IB) – Prime/CMDP Help Desk, All Things SDWIS

  6. Overview of remainder of session • CMDP and Prime – Highlights of past year, goals & priorities for the year ahead • Prime – Highlights of past and upcoming releases • Prime – Activities for bulk data transfer, data migration, interfacing applications • Prime – Pilot Group priorities for first state uses of Prime • Prime – Product Owner perspectives, UT perspectives

  7. Compliance Monitoring Data Portal (CMDP) • Highlights from the past year • Increase from 3 to 10 states in production • Increase from 9 to 200+ labs / operators flowing data • Upcoming Priorities • Resumption of limited support for new states moving into production • Highest impact improvements for burden reduction, data quality • Process for updating of method-analyte pairs with each CMDP / Prime release (approximately one release per quarter) • Including pairs for contaminants beyond federally regulated contaminants

  8. States with high uses of CMDP by Labs / Operators • UT: 1 large lab, 12 other labs / local health departments • AZ: 2 labs / 3 Public water systems • 70% of data through the CMDP • AK: 40 labs • MT: 10 labs • NC: 140 Private labs • 79,000+ samples this year alone

  9. Success Stories from CMDP State Users • Less errors in data submitted from labs / systems: • 20,000+ data submission rejections (2018) -> Less than 300 rejections (2019) • 80% reduction in errors • 50% reduction in errors • Reduction from 20% error rate to 0.4% error rate • Reduction from 4% error rate to 0.3% error rate • Less staff time need for managing lab / system data: • Reduction from 3 FTE to 1 FTE for data management • 50% reduction in staff data management time • Opportunity for staff career advancement beyond data entry • “We no longer receive paper” • States that already had electronic reporting tool -> ready to utilize SDWIS Prime

  10. Requested Improvements • Method / Analyte Pairings Updates • Training on Use • Additional Sample Validations • Operational Data / Composite Sample Data Improvements • Retraction / Replacement Samples (Sample ID Reuse)

  11. SDWIS Prime – Highlights from the Past Year (through 2019 Release 1) What is the BRE? Built on commercial software, the BRE is separate but coupled with the SDWIS Prime UI software. The BRE applies drinking water rules logic with respect to rules applicability, schedules, violations, and return to compliance. • User Interface (UI): Increase from 5 to 12 (out of 14 total) functional areas developed • Business Rules Engine (BRE): • Increase from 3 to 12 (out of 13 total) drinking water rules / rule groupings supported • Increase in BRE support from 85% to 91% of violation occurrences in ETT (and in SDWIS Fed) • System integration through 38 Test Cases • API web services – prototype services for microbial samples data upload, access framework design What is a Test Case? A Test Case demonstrates correct functioning as data flows through various components of the UI and the BRE as a state performs data management functions for common rules management scenarios.

  12. Business Rules Engine SDWIS Prime Common User Interface (UI) In Pre-Production Components in Pre-Production LCR RTCR GWR Water Systems Facilities Sampling Points Developed within the Past Year IOC SOC NO2 SDWIS Prime UI and BRE – 2019 Release 1 Legal Entities User Management VOC NO3 DDBP Developed within the Past Year Upcoming Development CCR PN RAD Monitoring Schedules Scheduled Activities Enforcement Upcoming Development Violations Deficiencies SWTR Samples Site Visits/Sanitary Surveys Reporting to SDWIS FED System Administration

  13. SDWIS Prime – The Year Ahead • Goal – 1 to 3 states (& EPA Region 7) using SDWIS Prime by mid 2020 • Key actions: • Completion of LRDR & Bulk Upload Tool with VES (Exchange Network Grants) • Completion of data migration improvements • Completion of automated migration data quality checks • Completion of last 2 of 14 User Interface modules • Completion of last drinking water rule (SWTR) support in BRE • Completion of additional Test cases to bring automated support up to at least 93% of violation occurrences in ETT • Continued API work as needed for above work • Preparation for a new contract support period (beginning April 2020)

  14. Vision for Interaction of State Tools and Prime/CMDP Prime User Interface CMDP Bulk Data Upload Tool Existing State Interfacing Applications (e.g., op cert, public reports) VES APIs are long-term solution BRE Prime/CMDP Database #2 UT/Multi-State Exchange Network Grant for bulk data upload tool development. Local Data Repository (SDWIS-State 3.3 format) VES #1 – EPA / ECOS Exchange Network (EN) Virtual Exchange Services (VES) – Configured, initial tests with VA EN Grant Legend Red Objects – State Owned Blue Objects – EPA Owned

  15. SDWIS Prime – Longer Term • After first states in production, begin shifting some resources from continued development toward production user support • Explore potential for states pooling funds to supplement EPA funds for continued improvements and additions to SDWIS Prime and CMDP (comparable to past state supplemental efforts to EPA funded SDWIS State improvements) • Continue to develop and publish APIs as needed for longer term state interfacing applications needs, make SDWIS Prime code available to states • Continued EPA support for SDWIS State until 1-year after 2 states are fully using SDWIS Prime (are no longer using SDWIS State for compliance determination) • States may continue to use SDWIS State on their own after this 1-year period

  16. CY18 Release 4 - Summary of Deliverables   • Test cases across 12 Drinking Water Rules, various common scenarios:RTCR, LCR, GWR, IOC, VOC, SOC, Nitrite, Nitrate, D/DBP, RAD, CCR, and PN • The test cases demonstrate the Rule Applicability, Sample Result Evaluation, M&R Compliance, Activity Evaluation, and Monitoring Schedule Determination • The test cases demonstrate functionality across the following Prime modules:Inventory, Samples data entry, Monitoring Schedules, Violations, Scheduled Activities, Sanitary Surveys / Site Visits • Based on Pilot UAT and community feedback we are working to address performance issues with the Pre-production environment • ASDWA created a website area to collect testing feedback from non-Pilot / UAT states (http://feedback.asdwa.org/forums/916879-sdwis-prime-issue-tracking)

  17. CY19 Release 1 - Summary of Deliverables   • 7 additional test cases • Data migration fixes / enhancements to support interfacing applications (Part 1), security upgraded • Design for infrastructure to allow state access to API web services • Currently in deployment process, goal for community availability in mid-April • Will update community on status via All Things SDWIS call and ASDWA Prime Blog

  18. CY19 Release 2 – Summary of Deliverables • Data migration fixes / enhancements (Part 2) • System Admin additions (Part 1) • Surface Water Treatment Rule (Part 1 – Design) • CMDP - Resumption of limited support for new states moving to production, limited improvements to reduce burden / errors for existing states in production • Development completed by contractor mid-May, available to community mid-June to mid-July

  19. CY19 Release 3 – Scoping Process • Pilot / UAT Group meeting March 11-14, 2019  • ROM delivery early to mid-April • EPA will review ROM and recommend priorities for CY19 Release 3 • EPA will present CY19 Release 3 priorities to SDWIS Advisory Board for feedback • Final CY19R3 priorities will be provided to the contractor and a formal scope document will be created for CY19R3 

  20. CY19 Release 3 – Summary of Functionality Priorities • High priority test cases / functionality for first state adopters • Data migration fixes / enhancement (Part 3 – Completion) • System Admin additions (Part 2 - Completion) • Surface Water Treatment Rule (Part 2 – Completion) • Enforcement functions (Part 1 – Design) • CMDP - Continuation of limited support for new states moving to production, limited improvements to reduce burden / errors for existing states in production • API web services work as needed to support first state uses of Prime

  21. CY19 Release 4 – Summary of Draft Priorities • High priority test cases / functionality for first state adopters • Data mapping to support data migration and bulk data exchange (Part 1) • Enforcement functions (Part 2 – Completion) • Reporting to EPA functions (Part 1 – Complete as much as doable – dependent on data mapping completion) • CMDP - Continuation of limited support for new states moving to production, limited improvements to reduce burden / errors for existing states in production • API web services work as needed to support first state uses of Prime • Will obtain Pilot / UAT Group input and Advisory Board feedback in July through September period

  22. Interfacing Applications: Exchange Network Virtual Exchange Services (VES) & the Local Replication Data Repository (LRDR) • Data out solution to allow states to continue use of interfacing applications • The Local Replication Data Repository (LRDR) is a SDWIS State 3.3 formatted set of data tables, housed on a Primacy Agency’s server, serving as a repository for the regular replication of a Primacy Agency’s production data in SDWIS Prime • Can be a new instance of SDWIS State 3.3 or your existing SDWIS State database • A Primacy Agency’s interfacing applications can then continue to connect to the Primacy Agency’s LRDR like they currently do to SDWIS State U.S. Environmental Protection Agency

  23. Vision for Interaction of State Tools and Prime/CMDP Prime User Interface CMDP Bulk Data Upload Tool Existing State Interfacing Applications (e.g., op cert, public reports) VES APIs are long-term solution BRE Prime/CMDP Database #2 UT/Multi-State Exchange Network Grant for bulk data upload tool development. Local Data Repository (SDWIS-State 3.3 format) VES #1 – EPA / ECOS Exchange Network (EN) Virtual Exchange Services (VES) – Configured, initial tests with VA EN Grant Legend Red Objects – State Owned Blue Objects – EPA Owned

  24. VES/LRDR Status • Proof of concept established under Exchange Network Grant on Systalex server and with Virginia • Set up LRDR and flow data from Prime staging to server • After Prime – SDWIS State 3.3 data mapping is complete, pilot transfer of data from Prime to LRDR via VES • Working with Utah & EPA Office of Mission Support (formerly Office of Environmental Information) to connect VES with cluster servers U.S. Environmental Protection Agency

  25. VES/LRDR Next Steps • Following Utah work, Systalex will refine instructions and recommendations for next states • Next, will work with 2nd wave customers (priority on Exchange Network grant recipients) • Will make instructions available to all Primacy Agencies U.S. Environmental Protection Agency

  26. Bulk Data Upload Tool: Overview • Plan to develop an option to upload data into SDWIS Prime rather than creating it in Prime or CMDP. Types of data: • Parametric data which does not come through CMDP • Monitoring Schedules • Scheduled Activities • Water Systems – Sampling Point • Site Visits (surveys, assessments, enforcement, etc.) • Inventory information (facilities and water systems) • Enforcement Actions • Replaces current SDWIS State Data Bridge and Migrate to State applications U.S. Environmental Protection Agency

  27. Vision for Interaction of State Tools and Prime/CMDP Prime User Interface CMDP Bulk Data Upload Tool Existing State Interfacing Applications (e.g., op cert, public reports) VES APIs are long-term solution BRE Prime/CMDP Database #2 UT/Multi-State Exchange Network Grant for bulk data upload tool development. Local Data Repository (SDWIS-State 3.3 format) VES #1 – EPA / ECOS Exchange Network (EN) Virtual Exchange Services (VES) – Configured, initial tests with VA EN Grant Legend Red Objects – State Owned Blue Objects – EPA Owned

  28. Bulk Upload: Status • Multi-state grant (UT, PA, AK, MT, ND); currently working with Exchange Network Grant Team and Systalex to obligate funding • Final product will include an interface to upload files to SDWIS Prime in XML format along with data validation functions • Plan to use VES to process files from Bulk Data Upload Tool into Prime U.S. Environmental Protection Agency

  29. Exchange Network Grants Community of Practice • Use of outstanding EN grant funding, centered around: • CMDP Adoption • VES/LRDR Setup • Data Migration • Beginning in April U.S. Environmental Protection Agency

  30. Data Migration: Data Quality Check Process • Process to move large data files from Primacy Agencies to SDWIS Prime in a SDWIS State 3.3 common format • DQ checks on format, referential integrity, and data quality • Checks have been provided from States, FedRep, and CMDP • Indiana and Region 7 data will run through the full DQ check process starting in April • Pilot agencies and EN Grant recipients can use DQ checks beginning in May • Expectation is to start on additional states by end of 2019 • POC: Renee Morris

  31. Short Term Vision: UT, IN, CT Critical Functionality • User Interface and Business Rules Engine: • Ability to run all of the SDWA drinking water rules (including basic SWTR functionality) • Enforcement Module • Custom fields and values • Federal Reporting ability • Data Migration complete • Data out: VES/LRDR • Bulk upload tool

  32. EPA Product Owner Perspectives – Business Rules Engine Functionality by Violation Code • Occurrence of violations from the Jan 2018 ETT’s list of violation for the preceding 5 year period – 361,910 • Description of Metrics: • >90% Covers 90% or more of the scenarios which lead to the violation code • 01 – Single Sample MCL 3931 • 02 – MCL 25436 • 03 – M/R 35625 • 3A – RTCR monitoring – 29289 (began 4/16) • 1A – MCL E coli – 734 (began 4/16) • Activity Added: violation created when the manually added Scheduled Activity is not complied with • 48 – GWR – Failure to Address Contamination – 23 • 57 – Lead and Copper OCCT Study Recommendation - 737 • 32 – Failure to submit Source water monitoring plan -624

  33. EPA Product Owner Perspectives – Business Rules Engine Functionality by Violation Code • Description of Metrics (continued): • Only Manual - Violation is complex to program or very rare • Violation 29 – Filter Profile - 45 violations • Violation 33 – Failure to Submit a Bin determination - 13 violations • To be developed • 36 SWTR Monitoring -6262 • 41 SWTR Failure to Maintain Microbial Treatment - 3077

  34. EPA Product Owner Perspectives • BRE Support Metrics: • Occurrence of violations from the Jan 2018 ETT list • Evaluation used • Test Case scenarios • Off script common scenarios • Results (through 2019 Release 1) • >90% coverage = 88.93% • Activity added = 2.10% • Only Manual = 1.67% • TBD = 6.36% - mostly SWTR • Note: All violation types can at least be manually entered in the current pre-production release

  35. Utah Perspectives • Current SDWIS/State • Working under a Security Exemption • Desire to build to the future not the past • Leverage technology • CMDP and electronic sample reporting • Develop on-line tools • PWS data access • Public transparency • Freedom of Information Act requests • Operator Certification training 35

  36. Utah Perspectives • Ready to jump when: • Prime can house all of our data • Run the drinking water rule including our state specific analytes • Run our interfacing applications • Allow for Bulk Upload of data • Manage Enforcement • Report to EPA Fed • Performance 36

More Related