1 / 23

Pennsylvania DEP’s Underground Injection Control Data Flow

Pennsylvania DEP’s Underground Injection Control Data Flow. May 31, 2012 Jen Gumert, PA DEP. Underground Injection Control Data Flow. What is Underground Injection Control? Why PADEP selected the UIC Data Flow Designing and Developing the Process Challenges.

bedros
Download Presentation

Pennsylvania DEP’s Underground Injection Control Data Flow

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. Pennsylvania DEP’s Underground Injection Control Data Flow May 31, 2012 Jen Gumert, PA DEP

  2. Underground Injection Control Data Flow • What is Underground Injection Control? • Why PADEP selected the UIC Data Flow • Designing and Developing the Process • Challenges

  3. What is Underground Injection Control ? The Underground Injection Control Program: regulates the construction of, permits, inspects, identifies violations, tracks enforcements, and tracks closures of injection wells that place fluids underground for storage or disposal.

  4. What is Underground Injection Control ? 5 Types of Underground Injection Control: Class 1: (none in PA) Below DW Source Class 2: OG Brines and Fluids injected below DW Source Class 3: Hazardous Waste injected into or above (OUTLAWED) Class 4: RCRA or CERCLA cleanup Class 5: Anything built to receive water waters including recovery of water from creeks

  5. What is Underground Injection Control ? EPA Region 3 is primacy of the Underground Injection Control Program in Pennsylvania. Historically, UIC data has been shared with DEP on an ad hoc basis, through email, when needed by various programs. The manual process of acquiring and loading this data is time and labor intensive. This effort will automate the receipt and processing of UIC data to make it routinely available to PA’s Oil and Gas and Water Programs through their GIS and Ad Hoc Tools

  6. Why PADEP Selected the UIC Data Flow

  7. Why PADEP Selected the UIC Data Flow

  8. Why PADEP Selected the UIC Data Flow Benefits of PADEP UIC Dataflow • Automate the flow of this data to DEP programs in order to provide more timely access for: • Risk assessment and potential sources of contamination • Aid in ground water contaminant investigations • Aid to track where Marcellus frack water originated • Aid in identifying potential responsible parties of contaminations of water supplies • Aid in permit assessments (potential violators, large volume injectors)

  9. Designing and Developing the UIC Dataflow • Obtain TEST XML File from EPA Region 3 • Create Staging and ODS Tables • Create ETL Process • Identify Data Quality Issues • Provide access to GIS and Ad Hoc Tools • Create GIS Layers • Create Ad Hoc Objects

  10. Designing and Developing the UIC Dataflow • Obtain TEST XML File from Region 3 • Create Staging and ODS Tables • Create ETL Process • Identify Data Quality Issues • Provide access to GIS and Ad Hoc Tools • Create Ad Hoc Objects • Create GIS Layers

  11. 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 Designing and Developing the UIC Dataflow National UIC Database

  12. Designing and Developing the UIC Dataflow • Obtain TEST XML File from Region 3 • Create Staging and ODS Tables • Create ETL Process • Identify Data Quality Issues • Provide access to GIS and Ad Hoc Tools • Create Ad Hoc Access • Create GIS Layers

  13. Designing and Developing the UIC Dataflow • Obtain TEST XML File from Region 3 • Create Staging and ODS Tables • Create ETL Process • Identify Data Quality Issues • Provide access to GIS and Ad Hoc Tools • Create Ad Hoc Objects • Create GIS Layers

  14. PADEP_Well Location Geology Contact Well Type Well Status API Id PADEPOwner/Operator Permit PADEP Violation Drilling PADEP Enforcement Provide Access to Ad Hoc and GIS Tools PADEP Reporting Objects Program Specific Business Area PADEP Inspection

  15. UIC_Facility PADEP_Well Location Geology Contact Well Type Well Status API Id UIC_Well Location Geology Contact Well Type Well Status API Id UIC_Permit • Permit Activity Class I • Constituent • Waste • Engineering PADEPOwner/Operator Permit PADEP Violation UIC_Violation Drilling PADEP Enforcement UIC_Enforcement Provide Access to Ad Hoc and GIS Tools PADEP Reporting Objects Program Specific Business Area UIC Business Area UIC_MI_Test UIC_Inspection PADEP Inspection

  16. UIC_Facility PADEP_Well Location Geology Contact Well Type Well Status API Id UIC_Well Location Geology Contact Well Type Well Status API Id UIC_Permit • Permit Activity Class I • Constituent • Waste • Engineering PADEPOwner/Operator Permit PADEP Violation UIC_Violation Drilling PADEP Enforcement UIC_Enforcement Provide Access to Ad Hoc and GIS Tools PADEP Reporting Objects Program Specific Business Area UIC Business Area UIC_MI_Test UIC_Inspection PADEP Inspection

  17. Provide Access to Ad Hoc and GIS Tools Data Access through Ad Hoc Tool Oracle DISCOVERER Data Integration through API Id State Ids Visual Access and Integration Location Data and GIS Tools

  18. Provide Access to Ad Hoc and GIS Tools Wells Drilled Wells Permitted Jan – Feb 2012

  19. Provide Access to Ad Hoc and GIS Tools Wells Permitted Jan – Feb 2012

  20. Provide Access to Ad Hoc and GIS Tools UIC and WellHead Protection Areas

  21. Provide Access to Ad Hoc and GIS Tools UIC and Community Water Systems

  22. Challenges and Recommendations • Refresh Process – Incremental or Full • Source of Data • Data Quality • Data Integration

  23. Questions PADEP Exchange Node Team Jen Gumert jgumert@state.pa.us Narendra Mehta nmehta@state.pa.us Darryl Ragantesi dragantesi@state.pa.us Sanjay Shah c_sanjshah@state.pa.us

More Related