1 / 17

UIC Data Exchange System Objectives, Data Flow, Challenges

UIC Data Exchange System Objectives, Data Flow, Challenges. Exchange Network National Meeting Marriott New Orleans Convention Center New Orleans, LA April 25-26, 2007. Agenda. Quick Background UIC Program, Business Case for New Data System, Status of Development, Project Management

gregoryi
Download Presentation

UIC Data Exchange System Objectives, Data Flow, Challenges

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. UIC Data ExchangeSystem Objectives, Data Flow, Challenges Exchange Network National Meeting Marriott New Orleans Convention Center New Orleans, LA April 25-26, 2007

  2. Agenda • Quick Background • UIC Program, Business Case for New Data System, Status of Development, Project Management • 2. Proposed UIC System Design • Design Objectives, System Framework, Data Model, End to End Flow thru CDX to Database • 3. “Data Flow In” – Initial Implementation Strategy • Challenges and Progress

  3. Part 1Quick Background UIC Program History, State Primacy, Status of Development, Project Management

  4. UIC Program History • UIC Program: • -- Regulated under the Safe Drinking Water Act. Regulations issued in 1980 • -- EPA works with states to regulate underground injection of fluids to prevent endangerment of underground sources of drinking water (USDW).  • -- More than 570,000 injection wells; potential expansion for new waste streams (e.g., drinking water residuals, CO2 sequestration)  • Five UIC well classes: • -- Class I: Most strictly regulated. Injection of hazardous or municipal waste into deep wells. Haz waste wells co-regulated under RCRA. • -- Class II: Brines & other fluids associated with oil and gas production. • -- Class III: Fluids associated with solution mining of minerals • -- Class IV: Haz/rad wastes into or above a USDW. Banned in most cases. • -- Class V: Injection into or above USDW. Typically shallow systems • Primacy may be granted to a state for all well classes or split by SDWA statutory authority (i.e., Section 1422, Section 1425). EPA Regions directly implement (DI) for those UIC programs not delegated to the states. See next slide.

  5. State Primacy

  6. Status of Development • OGWDW made decision to proceed on development of new UIC database in June, 2006, based on a requirements analysis prepared over 2005 and 2006. • The final data model was approved in Nov 2006; XML schema in testing, to be approved end of April, 2007 • An integrated project team (IPT), comprised of EPA HQ, Regions, States had 1st biweekly mtg Nov, 2006. • EPA is working with 10 states & 9 DI Regions to map their data into UIC database by initial deployment date

  7. Status of Development (cont’d) • Completed to Date: • * Mapping instructions • * XML schema • * Schematron Business Rules • * CDX Node • * UIC Oracle Database • In Progress: • * Integration testing underway • * IPT Pilot Testing – 9 Regions, 10 states • * Data Warehouse: Reports & User Interface Dev • Target date for initial deployment: Aug 31, 2007

  8. Project Management Core Project Management Team Project Manager: Carl B. Reeverts Alternative Project Manager: Trang Le USER Access, Data Security Towana Dorsey UIC Program Contact Robyn Delehanty IT Team Leader: Abe Siegel Data Warehouse Team Leader: Lee Kyle Associate Branch chief Leslie Cronkhite, Roy Simon Integrated Project Team (proposed)

  9. Part 2Proposed UIC System DesignSystem Framework, Data Model,End to End flow thru CDX to database

  10. National UIC Database System Framework (11/2006 ) Data Source’s site Validator • OGWDW Management: • 7520 summary info • UIC PAM Measures • UIC Inventory Reporting Sys • SWP/UIC Integration • Class I Special Needs • Class V Invent. Initiative • Congr/GAO/OMB Questions 70+ Regional and state databases (2) XML Doc ICIS FRS notification (1) CDX (XML Doc Repository) Validator Data Analysis and Report Generation (Monthly, Quarterly, Yrly) Staging Access Database RCRAInfo System Integration Message Reports : 1. Invalid data 2. Changes from last data submission TRI Periodic Data Extraction UIC Database DWPD Data Warehouse

  11. Figure 2 - Relationship among UIC Business Objects Constituent (Class I only) Contact Facility Permit Permit Activity Waste (Class I only) Well Well Type Engineering (Class I and deep wells only) Well Status Geology (Class I and deep wells only) Location Violation MI_Test Enforcement Response Correction Inspection UIC Data Model – ERD

  12. Part 3“Data Flow In” – Initial Implementation Strategy

  13. Initial Implementation We are working initially with 10 states & 9 Regional DI programs to map their data into the new UIC database by the initial deployment date. We have begun discussions through the Regions and GWPC to reach agreement with all other states to provide data in subsequent rounds. State/DI Trading Partners Participating in Initial Phase In: Role of State/DI: To be initial State/DI programs to flow data to new UIC DB by July 31, 2007 Proposed No. of States/DI: 9-15 States, 9 DI Regions Project Period: Sept 2006 – Jul 31, 2007 Estimated Commitment Per State/DI = .15 FTE • State/DI Programs (Proposed): • Round 1: MT, WY, UT, DE, MS, Regions 3, 4, 6, 7, 8, 9 • Round 2 (still in discussion): MA, FL, GA, NC, SC; TCEQ, TRRC; NE, ND, UT, AK, CA (5 other States with Network Exchange grants); Regions 2, 5, and 10

  14. Data Mapping Process 1. Agree on data to transfer – review mapping instructions and agree on data to be transferred. 2. Perform logical mapping – complete the EPA database mapping form. 3. Extract source data – extract the source data and put it in a temporary file or staging tables. 4. Convert extracted data – convert the source data extracted from step 3 to the EPA data format, which is defined in the UIC Data Model Version 7.5 and the Business Rules document, and load the converted data to either an Access database, or an XML file that conforms to the UIC XML schema. 5. Populate XML Data File – if choosing step 4a, run the EPA XML conversion tool to convert data in the Access database into XML file. If choosing step 4b, develop and use an XML conversion tool. 6. Validate XML Data File– run the EPA validation tool against the XML file and correct any invalid entries.

  15. Part 4Challenges and Progress

  16. Challenges: • Mapping to new database from 70 different State and Region databases • UIC program resources sharply constrained to take on new task • UIC programs and data are located in different state agencies, multiple databases or spreadsheets or paper files (particularly for Class V wells) • Shift to electronic commerce to flow UIC data to EPA is a “cultural change” requiring unique state/EPA solutions

  17. Progress: • Reached agreement on single national data model to meet well documented business case that conforms to EPA data standards • EPA data needs will be met through mapping from existing State data bases. • Four EPA Exchange Network grants underway and another 10+ UIC state programs applied for grants in 2007. • Integrated Project Team (IPT) established last Nov to guide and support UIC database dev. • On target for deployment by end of fiscal year.

More Related