1 / 46

Electronic Exchange of Drinking Water Lab Data

Electronic Exchange of Drinking Water Lab Data. Presented by: Mike Matsko NJDEP Exchange Network Users Meeting April 18, 2006. eDWR Project Background. Project was initiated and funded as a 2002 Exchange Network Challenge Grant 5 Participating States: NH, ME, NJ, RI, and VT

Melvin
Download Presentation

Electronic Exchange of Drinking Water Lab Data

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. Electronic Exchange of Drinking Water Lab Data Presented by: Mike Matsko NJDEP Exchange Network Users Meeting April 18, 2006

  2. eDWR Project Background • Project was initiated and funded as a 2002 Exchange Network Challenge Grant • 5 Participating States: NH, ME, NJ, RI, and VT • Project consisted of 2 Phases: • Phase 1: March 2003 to December 2004 • Phase 2: December 2005 to December 2005

  3. eDWR Project Objectives • Flow SDW data into our State SDWIS system from Laboratories • Refine the e-DWR schema to support the data reporting requirements • Develop a set of modular laboratory files that could be used by other environmental data flows • Develop a scalable submission receiving system that can be used for easily leveraged for additional data flows

  4. eDWR Project Phases • Phase 1 • Schema Development • EDI Converter - eDWR XML file conversion to “Sampling via EDI” • Stakeholder Survey - Laboratory Readiness for eDWR system • Best Practices Document - eDWR system recommendations • Implementation Strategy • Security • Account Management • Submission > Validation > Feedback • Phase 2 • Develop a system to support a Lab to State data exchange

  5. eDWR System Development Steps • Used Phase 1 outputs • Purchased E2 software from enfoTech & Consulting, Inc. • Consolidated paper forms to web forms • Revised business process • NJDEP portal integration • Develop system detail design document

  6. What is E2? • Secure web based system to conduct e-business over the Internet • Designed by enfoTech to improve data quality and reduce resources • An intelligent data exchange server that: • Receives reports submitted by regulated facilities • Evaluates reports for meeting reporting requirements • Uploads reports to NJDEP for compliance assessment • Uses Exchange Network web services and XML for data exchange

  7. E2 Capabilities for Labs and Water Systems • Laboratories • Submit new and revised drinking water reports • View meaningful validation results on-line • Save partially completed reports • View and print all previous submissions • View status of all submissions and receive email notification • Water Systems • Authorize a Lab to submit data on their behalf • View submissions and status of all reports submitted on their behalf • Submit new and revised annual water utilization reports • View meaningful validation results on-line • Save partially completed reports • View and print all previous submissions • View status of all submissions and receive email notification

  8. E2 Submission Options • Web Form Entry: A user can data enter each sample using an Online Entry Form and receive immediate validation feedback. • Copy / Paste from Excel: Offline data preparation and then copy the data from a spreadsheet program and paste the data into an online form for conversion to XML. Validation feedback is provided via email after E2 has processed the data. • XML File Upload: A user can upload an XML file or a ZIP file containing one XML file based on the eDWR schema. Validation feedback is provided via email after the E2 has processed the data. • MS Excel XML Template: A user can download and populate an Excel file that will generate a valid XML file for upload. • Note: Not all NJDEP forms are available for electronic submission.

  9. E2 User Types • Laboratory User • Associated with only 1 Certified Laboratory • Submit only Lab Data for multiple Water Systems • Water System User • Associated with 1 or more Water Systems • Submit only MOR Data for Water Systems * 1 user account could be both a laboratory and water system user

  10. E2 User Roles • Laboratory Report Preparer • Laboratory Report Certifier • Laboratory Administrator • Authorize Users to Prepare / Certify Lab Reports for their Lab • Water System Report Preparer • Water System Report Certifier • Water System Administrator • Authorize Users to Prepare / Certify Annual Water Utilization Reports for their Water System • Authorize NO Laboratories to Prepare / Certify Lab Reports • Authorize ALL Laboratories to Prepare / Certify Lab Reports • Authorize Specific Laboratories to Prepare / Certify Lab Reports

  11. Lab User Getting Started

  12. Water System User – Getting Started

  13. Submission System Benefits • Improve data quality • Reduce reporting costs • Reduce reporting burden • Report status on-line • Greater control of data quality for Labs and Water Systems • Decrease State costs • Improve Agency effectiveness with faster response for data analyses, compliance, and decision-making

  14. E2 Next Steps • System release for drinking water reporting • Private Well Testing Act data submissions • New Jersey Quantitative Limit data submissions • Volunteer Water Monitoring data submissions • State to EPA data exchange • State to State data exchange

  15. eDWR Submission System Questions?

  16. New Jersey Architecture Web Servers - Sun v480, Solaris 9 OS, SunOne Web Server 6.x, Server Certificate/SSL App. Servers - Sun v480, Solaris 9 OS, SunOne Application Server 7 EE, Server Certificate/SSL Database Servers - Dell PowerEdge 6650, Red Hat Enterprise Linux AS v2.1, ORACLE 9i Note: In addition to the HW represented here, there is a box in the Secure access layer that acts as a reverse proxy so our Node can talk directly to other Nodes. Without the reverse proxy, NJDEP would not be able to use NAAS.

More Related