1 / 18

Understanding the ICIS-NPDES Policy Statement

Understanding the ICIS-NPDES Policy Statement. Betsy Smidinger, Deputy Director Enforcement Targeting and Data Division Office of Compliance Office of Enforcement and Compliance Assurance US EPA Expanded Steering Committee Meeting February 13, 2006. Overview.

dpool
Télécharger la présentation

Understanding the ICIS-NPDES Policy Statement

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. Understanding the ICIS-NPDES Policy Statement Betsy Smidinger, Deputy Director Enforcement Targeting and Data Division Office of Compliance Office of Enforcement and Compliance Assurance US EPA Expanded Steering Committee Meeting February 13, 2006

  2. Overview • Why do we need a Policy Statement? • What is the Policy Statement? • How was the Draft Policy Statement Developed? • What Data does the Policy Require? • RIDE • Implementing RIDE • Putting RIDE into Perspective • Benefits of the Policy Statement

  3. Why do we need a new Policy Statement? Program Change leads to Policy Change… • The CWA NPDES program has evolved greatly over the past • 20 years requiring new tools and policies. • Increased focus on the “wet weather” sources. • Increasing attention on the non-major sources (90,000) in addition to the Majors (6,700) • Government Performance Results Act (GPRA) • OMB’s Program Assessment Rating Tool (PART) Additional Data Drivers ICIS-NPDES Policy Statement includes expanded data element requirements to meet the program management needs.

  4. What is the Policy Statement? ICIS-NPDES Policy Statement Purpose “To ensure that ICIS-NPDES contains accurate, complete, consistent, and timely information, which will support effective management of the NPDES program and ensure that the human health and environmental protection goals of the Clean Water Act (CWA) are met.” • Replaces the PCS Policy Statement originally issued in 1985. • Establishes ICIS-NPDES as the national database of record for CWA NPDES permitting and enforcement information. • Sets forth Required ICIS-NPDES Data Elements (RIDE).

  5. How was the ICIS-NPDES Policy Statement Developed? • Six NPDES Data Requirements Workgroups • 36 state participants representing 21 states • Identified: • Data Requirements for the modernized system • Subset of data critical for each area considered in this effort • Data Requirements Workgroup recommendations sent out for Regional and State review and comment (April 30, 2002) • Strawman Workgroup (March 2004) • EPA, Regions (5 & 6), States (Iowa, Georgia) • Developed framework for the content and scope of a new Policy Statement • Recognized resource constraints: • Required universe represents a significant increase in the volume of data to be entered into the database • States/regions will need sufficient resources to fully implement

  6. How was the ICIS-NPDES Policy Statement Developed? (continued) • PCS Steering Committee Meeting (March 2005) • Discussed 1st working draft of the ICIS-NPDES Policy Statement • Result of the March meeting: • Modified Transition Plan • RIDE Data Uses (see handout) • 2nd Draft Policy, revised based on meeting comments, circulated to Steering Committee for comment. • Expanded Steering Committee (December 2005) • Received 3rd Draft ICIS-NPDES Policy Statement

  7. Required ICIS-NPDES Data Elements (RIDE) What data does the Draft Policy Require? • Required elements expanded for special regulatory programs. • No distinction between majors and non-majors. • More enforcement data required from states: • Formal actions & penalties for state actions • Compliance schedules • Additional compliance monitoring data: • DMRs for non-majors • Single event violations (inspection driven) for non-majors

  8. Biosolids • Annual sludge management data • Land application, surface disposal & incineration pollutant data • Vector & pathogen reduction • CAFOs • Livestock data • Contract operations • Manure management & capacity data • CNMP & other Plans • CSO/SSOs • CSO collection systems • SSO satellite systems • CSO & SSO overflow events • NMC & plans implementation • Pretreatment • Pretreatment program requirement • PCI/Audit data • Pretreatment summary data • Storm Water • MS4 descriptive data • Storm water event data • Annual report data • Industrial sectors ICIS-NPDES RIDE Core Requirements Facility Data Permitting Data Compliance Monitoring Data Enforcement Data Permit Components

  9. ICIS-NPDES Policy Statement: Implementing RIDE • Transition Plan provides a strategy for entering the new RIDE 3 years after a direct user state begins using ICIS-NPDES. • Existing PCS WENDB elements expected to be up-to-date. • Enforcement and Compliance data, even for new elements, entered as activities occur. • States given 9 months to adjust to ICIS-NPDES, then submits plan. • Region approves state plan. • Transition plan incorporated into PPA or EPA-state management agreement. • Batch states’ plan will focus on changes needed to state systems to flow data in accordance with XML schema, and will have 3 years from issuance of the final Policy Statement to enter the new RIDE.

  10. ICIS-NPDES Policy Statement: Implementing RIDE - continued Direct User State Example Submit Transition Plan to Region State launches in ICIS-NPDES ICIS-NPDES RIDE Transition complete Region approves plan March 2006 December 2006 April 2007 March 2009 9 months 3 years

  11. Putting RIDE into perspective • 47% of RIDE data (156 of 332 elements) relate to special program areas. • RIDE data entry varies greatly due to frequency (e.g., once every 5 years) and activities undertaken (e.g., enforcement action). • Data entry effort depends on the size and location of the state, the quality of their data in PCS, and their current electronic reporting capabilities. • The majority of the RIDE Core Data is WENDB now in PCS. Current data in PCS will be migrated to ICIS-NPDES. • Many states are making significant progress toward tracking DMRs for non-majors in PCS.

  12. Biosolids CAFOs 57 CSO/SSOs 20 Pretreatment 39 Storm Water 7 Putting RIDE into perspective:1. RIDE in Special Program Areas Core Data Requirements # of Data Elements Facility 25 Permitting 75 Compliance Monitoring 37 Enforcement 39 Total 176 NOTE: 145 RIDE elements are system required Additional 156 Special Regulatory Elements 33 Total RIDE Elements = 332 *Numbers subject to change based on completion of software development.

  13. Putting RIDE into perspective:2. Data Entry Frequency

  14. Putting RIDE into perspective:3. Data entry for ICIS-NPDES will vary greatly by state.

  15. Putting RIDE into perspective:4. Facility Universe Estimates It is difficult to assess the number of facilities in PCS for many of the special regulatory areas. *For each POTW with a pretreatment program, ICIS requires the aggregate number of SIUs/CIUs, not information on each and every SIU/CIU. Rather than 30,000 entries, there are only 1,500 and then in a once in a five-year cycle. **Stormwater Construction facilities are only RIDE if there has been compliance monitoring or enforcement activity.

  16. Putting RIDE into perspective:5. Status of Non-majors Data Entry • Permit limits must be entered prior to entering discharge monitoring reports (DMRs). • 46% of 92,061 non-major individual and general permits currently have limits in PCS. • 32 out of 59 states/territories have entered permit limits for greater than 50% of their individual and general non-majors. • eDMRs significantly reduce the burden associated with entering DMRs for both majors and non-majors.

  17. Non-major permit universes and limit entry rates in PCS, by EPA Region

  18. Benefits of Implementing the ICIS-NPDES Policy Statement • Nationally consistent data to respond to “data drivers”. • Permit/facility inventory. • More effective management of NPDES permitting and compliance programs. • Improved understanding of non-compliance beyond DMR-based violations by majors. • Cost savings by improving inspection targeting. • Public access to more complete information on NPDES program.

More Related