Safe Drinking Water Information System

Safe Drinking Water Information System Safe Drinking Water Information System - Start

2016-06-22 90K 90 0 0

Safe Drinking Water Information System - Description

Compliance Monitoring Data & NextGen. Greg Fabian, PMP. to. Exchange Network National Meeting. Philadelphia, PA. May 30, 2012. Topics. SDWIS State – Usage and Architecture. Current Data Flows. ID: 372834 Download Presentation

Download Presentation

Safe Drinking Water Information System




Download Presentation - The PPT/PDF document "Safe Drinking Water Information System" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.



Presentations text content in Safe Drinking Water Information System

Slide1

Safe Drinking Water Information System Compliance Monitoring Data & NextGen

Greg Fabian, PMP

to

Exchange Network National Meeting

Philadelphia, PA

May 30, 2012

Slide2

Topics

SDWIS State – Usage and ArchitectureCurrent Data FlowsThe National Perspective – SDWIS FedFilling in the Gaps - the Drinking Water StrategyCompliance Monitoring Data – Building a Data FlowData Mapping and the ECOS IPTMoving to SDWIS NextGen

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

2

Slide3

SDWIS State Background

EPA-developed system used by Primacy Agencies to manage their PWSS programsUsed to determine water system compliance with the National Primary Drinking Water rulesIncludes many other features for managing…Engineering information/inspection resultsDrinking water buyer/seller/ownershipAdministrator/Operator/Emergency contactsAssistance and enforcement actionsLaboratories and samples/sample resultsMonitoring and sampling schedules

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

3

Slide4

Guam

Michigan CWS

N. Mariana I.

Puerto Rico

Virgin Islands

Wyoming (R8

)

EPA R2-R8, R10

American Samoa

Michigan NCWS

Navajo Nation

R9 & R1

Tribal

Use SDWIS/State

Considering SDWIS/State

Not Considering SDWIS/State

Primacy Agencies Using SDWIS State

Partially Use or Implementing SDWIS State

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

4

Slide5

SDWIS Components and Data Flows

5

SDWIS Fed

SDWIS State

SDWIS ODS/Web

ODS Extract

SDWIS

FedRep

Standard

Reports Services

ODBC

(Ad Hoc)

SDWIS

FedRep

XML File

Exchange Network Node

State Data System(s)

XML File

Drinking Water Data Warehouse

Extract Transform

Load

SDWIS Operational Data

Store

(ODS)

XML Sampling

Data Entry Apps

Drinking Water Watch

Lab-to-State

CSV

XML

Paper

Sanitary Survey Extract

Desktop Sanitary Survey

Field Notebook

XML File

Migrate

To State

Data Bridge

E-Data Verification

Samples and Sample Results

Submitted by Laboratories

Central Data Exchange (CDX)

XML File

SDWIS State

State Data Entry

Operators

EPA Regions and HQ Users

Public Access to DW Data

State Web Site

Installed at States

Installed at EPA

EPA

Maintained SDWIS Component

State Maintained System/Application

Quarterly Report

EPA Enforcement Staff

eDV

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

Slide6

SDWIS Data Flows – State to EPA using Current SDWA 3.0 XML Schema

All states use FedRep to validate SDWA XML documentFedRep also extracts data from SDWIS StateStates can submit other samples, but it’s voluntary and not loaded into the SDWIS Fed Data Warehouse

SDWIS State

Other System

FedRep

Inventory

Actions

Pb/Cu

Exchange Network

CDX

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

6

Slide7

SDWIS Data Flows – State to EPA using Current SDWA XML Schema

ODS Transformation Services checks the submissions and adds referential integrity to the resulting database objectsSDWIS Fed Data Warehouse (SFDW) creates new objects based on reported and derived data optimized for queryingSFDW extracts go to OECA’s ECHO system, EnviroFacts, and various reports

Inventory

Actions

Pb/Cu

SDWIS ODS Transformation

CDX

ODS

SFDW

ECHO

EFacts

Reports

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

7

Slide8

SDWIS Data Flows – State to EPA using Current SDWA XML Schema

Lab-to-State is a CROMERR-compliant portal where labs can submit sample data as eDWR XML or.csv files.Lab-to-State produces an XML file with lab results documentSDWIS XML Sampling is used to parse the eDWR document and load samples data into the SDWIS State DB

Lab-to-State

XML

XML Sampling

SDWIS

State

eDWR

(xml)

.

csv

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

8

Slide9

Determining Compliance

SDWIS compares the schedules (when to take certain samples) with the sample resultsIf no samples are loaded within the date range, then SDWIS will generate a candidate M&R violationIf samples exceed certain values, then SDWIS will generate the appropriate MCL, MRDL, TT, or Other candidate violationPrimacy Agencies accept or reject candidate violationsAccepted violations are sent into EPA using the process described earlier

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

9

Slide10

The National Perspective – Data Transformations

State reported data are stored as-is in SFDWDerivations are used to improve query performance and make assumptions about dataInactive water system – active facilityGround water or surface water sourced systemCorrecting coordinates for water system facilities located in Manchuria“Total replace” of data each quarterPreviously reported data not reported in current quarter

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

10

Slide11

Quarterly Reporting Schedule

Primacy agenciesReport data each quarterHave 90 days to report the dataResult = data are 90 days old when received by EPAPrimacy Agencies can optionally report each month

FYQ1

FYQ2

FYQ3

FYQ4

CmpYQ1

CmpYQ2

CmpYQ3

CmpYQ4

CmpYQ1

FYQ4

OCT

Jan

Apr

Jul

Oct

Jul

CYQ1

CYQ3

CYQ2

CYQ4

CYQ3

CY – Calendar

yr

FY – Gov’t Fiscal

yr

Cmp

– Compliance

yr

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

11

Slide12

The National Perspective – an Incomplete Picture

Current data flows to EPA are exception-based and focused on complianceInsufficient data forMeasuring effectiveness of current regulations and treatment technologiesGiving the public a consistent view of the quality of their drinking waterLeaves the drinking water regulatory community with letting others tell the drinking water story at the national level

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

12

Slide13

Administrator’s Drinking Water Strategy Goals – March 2010

Address contaminants as groups rather than one at a time so that enhancement of drinking water protection can be achieved cost-effectivelyFoster development of new drinking water technologies to address health risks posed by a broad array of contaminantsUse the authority of multiple statutes to help protect drinking waterPartner with states to develop shared access to all public water systems (PWS) monitoring data

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

13

Slide14

Data Sharing Goals

Promote the use of advanced technologies for facilitating information and data exchange between states and EPAEnhance compilation and analyses of PWS information to strengthen the analysis of potential drinking water public health concerns without additional on the statesShare powerful data analysis tools with states to target program oversight, compliance assistance, and enforcement to needed areas based upon risk to public healthImplement interactive communication tools enabling states, the utilities, and consumers to obtain timely information for learning more about their drinking water and performance of drinking water systems for public health protection

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

14

Slide15

EPA/ECOS/ASTHO/ASDWA Data Sharing MOU

Negotiated and signed Nov 2010Data Sharing Implementation Work Group (IWG) launched Dec 2010Primary goal: Recommend to the MOU Steering Committee a set of compliance monitoring data (CMD) elements which would eventually would be housed in SDWIS NextGen and shared with EPAUsing SDWIS State as a basis, the IWG identified the set of CMD data elementsSep 2011, IWG issued its report to the MOU Steering Committee recommending the CMD elements

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

15

Slide16

MOU Steering Committee Approved CMD Data Elements

InventoryWater SystemWater System FacilitiesTreatment PlantAnalyte RemovalSampling PointFacility Analyte LevelLegal Entity AffiliationsService AreasGeographic AreasLocationsTreatmentsFlowSamplesSamples/Sample SummariesSample ResultsMDP SummariesMonitoring Period Averages

ActionsSampling PlanSampling PointsCollection DatesSampling ScheduleMonitoring PeriodMCLsViolationsEnforcementsAssociated ViolationsCompliance SchedulesMilestone EventsCompliance ScheduleCompliance Schedule ActivitySite visitsCompliance ScheduleDeficiencies

Based on SDWA 3.0 XML SchemaOriginal Modified New

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

16

Slide17

ECOS IPT – Implementing the CMD Data Flow

IPT launched in Jan 2012Laurie Cullerot, NH and Greg Fabian – co-chairsWork on defining the XML schema began in advanceScope is to go beyond the EPA-Primacy Agency exchange by considering other stakeholdersIdentified additional data elements requested byCDC – Public Health Tracking NetworkAPHL – Lab QA dataSix year review data submission (“ICR”)Developed SDWA 4.0 schema

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

17

Slide18

Possible CMD Flow

Data mapping tool – maps Primacy Agency data sources to the SDWA 4.0 schema and validates/checks errorsIntention is for EPA to provide mapping tool to the Primacy Agencies

18

SDWIS State

Other Database

Excel Workbook

Data Mapping

SDWA

4.0

Mapping Tool

CMD XML Document

EN Node/ Node Client

SDWIS

FedRep

Extract/Validate

CDX Web/ ENSC

SDWIS ODS

Extract-Transform -Load

Data

Warehouse

Reporting Agency

Exchange Network

CDX

SDWIS

Fed

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

Slide19

Data Mapping Pilot

Started late April, scheduled completion June 11AR, LA, NH, NY and OROH used by contractor as a basis for mappingGoal is toTest the SDWA 4.0 schemaEvaluate efficacy of using off the shelf data mapping toolsAltova Map Force selected for the pilotTransmit data using SDWA 4.0 through to CDXIf the mapping tools prove useful, EPA willDevelop scripts for mapping SDWIS State dataProvide mapping tools to the primacy agenciesOffer some training in tool use

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

19

Slide20

Additional Flows to Test

Focus right now is on CMD flow from Primacy Agencies to EPAOther flows need to be tested, such as:Labs to Primacy AgenciesTribes and Territories to EPA RegionsPrimacy Agencies to CDCFlows between agencies within a state and regionsFlows between Utilities and Primacy Agencies

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

20

Slide21

Beyond SDWIS to NextGen – Architectural Highlights

Cloud-based hostingOne app, one database with secure areas within the database for each Primacy Agency“Componentized” application using Service Oriented Architecture (SOA)Leverages Business Process Management (BPM) for workflow management and compliance determinationSupports process improvements geared to reducing the amount of time users spend in the systemDelivered to the end user through their web browser

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

21

Slide22

NextGen and its Stakeholders

22

EPA Regions

NextGen

Real

time data uses

?

Billing, permitting, plan

r

eview, other apps/data

Inventory, actions, compliance monitoring data

Sample results

Inventory,Reports

Occurrence data

Drinking water quality

Primacy Agency Systems

Water Systems

Laboratories

Primacy Agency Users

EPA HQ

Public

Other Federal Agencies

Compliance, enforcement, inventory/engineering, sampling, schedules

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

Slide23

Regulatory Users

Primacy agency users are the end users and will use NextGen as part of their day-to-day activitiesPrimacy agency systems interface with NextGen and provide additional features specific to each agencyEPA Regional users have oversight responsibilities for their states and may have different access needs than EPA HQ usersEPA HQ users have program oversight responsibilities at the national levelIncludes OGWDW and OECA uses of data reported to EPA

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

23

Slide24

Non-Regulatory Users

Other federal agencies, such as CDC and DHS, are consumers of SDWIS data (occurrence, locations, etc.)The public can view data pertinent to the quality of their drinking water or for other studies and purposesLaboratories may submit sampling data and results to SDWIS NextGen*, which may route the data to the cognizant stateUtilities may…*Approve samples submitted to SDWIS NextGenView/request modification of certain data elementsThere are probably other use cases yet to be defined

*Requires further analysis

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

24

Slide25

NextGen Value Proposition

Primacy Agencies…Will spend less time “feeding the system” because of process improvements built into NextGenBeginning effort to identify business process improvementsDo not have to maintain their own IT infrastructure and the staff needed to support NextGenReduced cost for upgrading/easier access to upgradesEPA…Reduced software maintenance cost – one app, one versionReduced operating cost – cloud hosting

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

25

Slide26

Some NextGen “Gotchas”

ODBC connectivity to the NextGen databaseMany Primacy Agencies have “add-on” applications that connect to SDWIS State using ODBCWeb services can be used instead in many casesPerceived loss of control of dataData are no longer physically located in a state data centerEnsure Primacy Agencies can control access to their dataCost model still being worked outPrimacy Agency cost sharing with EPA using grants?

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

26

Slide27

What’s Next?

Complete the data mapping pilot and other flowsDistribute data mapping tools to Primacy AgenciesBegin flowing CMD and 6-year dataComplete NextGen Business Process and Requirements Analysis by Oct 2012Establishing parts of the solution architecture – BPM/BRE and SOA/ESBFull Next operational capability in Sep 2014Decommission SDWIS State Sep 2015

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

27

Slide28

Questions?

5/30/12

Office of Water | Office of Ground Water and Drinking Water | USEPA

28

Greg Fabian

f

abian.gregory@epa.gov

(202) 564-6649

Slide29

Slide30

Slide31

Slide32

Slide33

Slide34

Slide35

Slide36

Slide37

Slide38

Slide39

Slide40

Slide41

Slide42


About DocSlides
DocSlides allows users to easily upload and share presentations, PDF documents, and images.Share your documents with the world , watch,share and upload any time you want. How can you benefit from using DocSlides? DocSlides consists documents from individuals and organizations on topics ranging from technology and business to travel, health, and education. Find and search for what interests you, and learn from people and more. You can also download DocSlides to read or reference later.