Accommodating CSO Flows /Loadings in the Chesapeake Bay Nutrient TMDL

Slides:



Advertisements
Similar presentations
creating a sustainable world The Chesapeake Bay TMDL A Policy Model for Nutrient Pollution Reductions James Noonan October.
Advertisements

RTI International RTI International is a trade name of Research Triangle Institute. Economic Study of Nutrient Credit Trading for the Chesapeake.
What are TMDLs? and What Might They Mean to MS4 Permittees?
Howard County, MD Phase II Watershed Implementation Plan October 6, 2011 Howard Saltzman Howard County Department of Public Works.
Steve McLaughlin, PE Virginia Beach Public Works October 2012.
Stormwater Rulemaking Briefing US Environmental Protection Agency.
Detroit WWTP NPDES Permit Informational Meeting Michigan Department of Environmental Quality October 23, 2014.
Commonwealth of Virginia Chesapeake Bay TMDL Watershed Implementation Plan (WIP) Russ Baxter, Chesapeake Bay Coordinator.
Strategic Process Engineering Liquid Treatment Processes at the Blue Plains Advanced Wastewater Treatment Plant Tier 1 Workshop Blue Plains Users October.
Chesapeake Bay Total Maximum Daily Load (TMDL) Tracking Thursday, May 31, 2012 Martin Hurd, Vladislav Royzman, Tetra Tech, Inc. Brian Burch, Megan Thynge,
Water Quality Monitoring in the Urban Rivers and Upper Bay Presented by: Jennifer Cragan Environmental Scientist.
Legislative Changes Affecting Water Quality at a Local Level October 2011 Robert Kollinger, P.E. Water Resources Manager Polk County Parks and Natural.
Slide 1 EPA Stormwater & Water Regulations: Local Impacts & Balancing Power 2011 Congressional City Conference.
INTRODUCING THE CHESAPEAKE BAY TMDL PROCESS TO VIRGINIA November 2009.
Overview of TMDL Plans TMDL Plan Workshop April 24, 2015 Karl Berger, COG staff Outline: Details Schedule Plan Elements Issues 1.
Chesapeake Bay Restoration An EPA Perspective Jeff Corbin Senior Advisor to the Administrator U.S. EPA.
SLIDE 1 Sustainable Stormwater Management May 6, 2015 Blue Highways: Transportation and Stormwater Management in Virginia Ginny Snead, PE Richmond Office.
MS4 & TMDL Permit Software Analysis and Design for Norfolk, Virginia
Nutrient Trading Framework in the Coosa Basin April 22, 2015.
Update on the District of Columbia’s Watershed Implementation Plan (WIP) for the Chesapeake Bay Total Maximum Daily Load (TMDL) November 18, 2010.
Tom Singleton Associate VP, Director, Integrated Water Resources an Atkins company Linking TMDLs & Environmental Restoration.
Impaired and TMDL Waterbody Listings Impacts on DoD Facilities Bill Melville, Regional TMDL Coordinator
Update on Chesapeake Bay Issues Presentation to the Chesapeake Bay and Water Resources Policy Committee July 17, 2009 Ted Graham & Steve Bieber COG Department.
Chesapeake Bay TMDL Background and Litigation Jon A. Mueller, Vice President For Litigation Chesapeake Bay Foundation William and Mary,
Developing Final Phase II WIPs and Milestones Katherine Antos Chesapeake Bay Program Office Jenny Molloy Water Protection Division DC Draft Phase II WIP.
Status Report: Chesapeake Bay TMDL Clean Up Plan Presented to P otomac Roundtable by Jack E. Frye April 9, 2010.
Total Maximum Daily Loads in MS4 Storm Water Programs.
1 “ Understanding the Local Role of Improving Water Quality” Virginia Association of Counties November 14, 2011 Virginia Association of Counties November.
Update on the Development of EPA’s Chesapeake Bay TMDL and Virginia’s Watershed Implementation Plan Russ Perkinson Potomac Roundtable October 8, 2010.
STATUS OF ECOLOGY’S DRAFT FLOW BLENDING POLICY WATER QUALITY PARTNERSHIP MEETING January 20, 2005.
1 Chesapeake Bay Program Management Board Meeting March 6, 2012 Discussion for the Final Evaluation of Milestones.
Phase II WIP Background & Development Process Tri-County Council – Eastern Shore June 2,
Presentation to the Chesapeake Bay and Water Resources Policy Committee July 30, 2010.
What is the Chesapeake Bay TMDL? Total Maximum Daily Load –Amount of pollutants that a water body can receive and still support designated uses Drinking,
Chesapeake Bay TMDL & Watershed Implementation Plans The Role of Local Governments Jeff Corbin Senior Advisor to the Administrator U.S. EPA Presentation.
Restoring VA Waters the TMDL Way Jeff Corbin Senior Advisor to the Regional Administrator U.S. EPA Region 3.
Briefing on IMA Negotiation Issues Presented to: Blue Plains IMA Negotiating Team Operating Agency Work Group March 11, 2010 District of Columbia Water.
Update on Chesapeake Bay Program Developments Briefing to the Water Resources Technical Committee January 8, 2009 Briefing to the Water Resources Technical.
Suzanne Trevena EPA Water Protection Division Chair Milestone Workgroup December 4,
Status Report on Chesapeake Bay Clean Up Plan Wastewater Sector June 2, 2010.
Chesapeake Bay Policy in Virginia - TMDL, Milestones and the Watershed Agreement Russ Baxter Deputy Secretary of Natural Resources for the Chesapeake Bay.
Deliberative, Pre-decisional – Do Not Quote, Cite or Distribute 1 Chesapeake Bay Water Quality Trading.
1 Discussion Points for IMA Participants – Flow Studies December 19, 2006 District of Columbia Water and Sewer Authority.
2004 Tributary Strategies: Assessment of Implementation Options Steve Bieber Water Resources Program Presented at: COG Chesapeake Bay Policy Committee.
Region 2000 Local Government Council 828 Main Street, 12th Floor Lynchburg, VA March 4, :30 – 8:30 p.m.
John Kennedy VA DEQ - Ches. Bay Program Mgr Tributary Strategies: Point Source Nutrient Controls Potomac Watershed.
MWCOG Water Resource Workshop “Preparing for Regulatory Change” February 20, 2004 Track 2: Panel #4 - Storm Water MS4 Regulation Paula Estornell, USEPA,
Chesapeake Bay Program Partnership’s Basinwide BMP Verification Framework: Building Confidence in Delivering on Pollution Reductions to Local Waters Maryland.
1 Briefing for IMA Participants on Results of Flow Studies October 31, 2006 District of Columbia Water and Sewer Authority.
VACo Environment and Agriculture Steering Committee VML Environmental Policy Committee June 2, 2010 Charlottesville, VA Chesapeake Bay Watershed Roanoke.
Preserving York County 2010 Municipal Educational Series January 28, 2010 Rick Keister, Alliance for the Chesapeake Bay Jake Romig, York County Circuit.
URBAN STORMWATER: A PERFECT STORM FOR CHANGE Jon M. Capacasa Director, Water Protection Division EPA Region III.
Maryland Association of Counties Conference August 12, 2009 Bob Koroncai USEPA Region III The Chesapeake Bay TMDL.
Approaches to CSO Control Adrienne Nemura, P.E. Limno-Tech, Inc.
Chesapeake Bay Watershed Implementation Plans: Why, What, and When Katherine Antos U.S. EPA Chesapeake Bay Program Office MACo Winter Conference January.
Katherine Antos, Water Quality Team Leader Water Quality Goal Implementation Team Coordinator U.S. EPA Chesapeake Bay Program Office Chesapeake Bay Program.
Maryland’s Nutrient Trading Program How Trading Works John Rhoderick Maryland Department of Agriculture.
CITIZENS ADVISORY COMMITTEE SPRING MEETING MARCH 1—2, 2012 CHARLOTTESVILLE, VA EPA’s Evaluation of Bay Jurisdictions’ Draft Phase II WIPs & Final
Northern Virginia Regional Commission MS4 Meeting March 17, 2011 Virginia Phase II Watershed Implementation Plan (WIP) Approach.
Northern Virginia Regional Commission MS4 Workgroup March 17, 2011.
Williamsburg’s Local Strategies to meet the ChesBay TMDL March 2012 Chesapeake Bay Watershed Virginia Maryland Pennsylvania New York Delaware West Virginia.
New York’s Chesapeake Bay WIP
Framework for CSO Control Planning
Update on PI Modeling and Nitrogen Removal at Blue Plains
Moving to Phase II: Watershed Implementation Plans
City of Noblesville Wastewater Utility
Building a Phase III WIP for Wastewater, Stormwater & Septic Systems
What is a Watershed Implementation Plan?
Jim Edward Acting Director Chesapeake Bay Program Office May 23,2018 EPA’s Draft Final Phase III WIP Expectations.
High Rock Lake TMDL Development
Presentation transcript:

Accommodating CSO Flows /Loadings in the Chesapeake Bay Nutrient TMDL WWP NACWA National Perspectives, Developments and Advanced Urban Wet Weather Solutions 22 April 2010

Why was a working group of CSO communities formed in Virginia and DC? A Long Term Control Plan (LTCP) that is not complete separation needs an allocation. No allocation, no allowable discharge from the combined sewer system under the Total Maximum Daily Load (TMDL) calculation and no loadings for the Watershed Implementation Plan. Reasonable assurance of compliance with the TMDL

Characterization of Combined Sewer Overflow (CSO) Discharges to the Chesapeake Bay 9 October 2009 Limo Tech on behalf of the Combined Sewer System (CSS) Working Group Develop information to be used by the U.S. EPA Chesapeake Bay Program (CBP) and jurisdictional regulatory agencies Characterize CSS pollutant loads for the Chesapeake Bay Nutrient and Total Suspended Solids TMDL study. Calibration of the Chesapeake Bay Water Quality Sediment Transport Model (WQSTM) Development of TMDLs

EPA’s Chesapeake Bay TMDL How was EPA Model Configured before V5.3? EPA Watershed Model includes CSO Area with Urban Stormwater Bay Model Segment Agricultural Area Urban/Suburban Area CSO Area Air Deposition EPA Water Quality Model includes Loads based on WWTP DMRs, which includes WWF Volume & Loads Storage Facilities1 CSO-C CSO-O DWF EPA Watershed Model currently does not recognize CSO controls or storage facilities WWF WWTP CSO Captured (CSO-C) portion of Stormwater may be double counted as part of WWF at WWTP Note: 1. Includes Shockoe Retention Basin, Hampton/ McCloy CSO Tunnel & In-line storage

EPA’s Chesapeake Bay TMDL Calibration Data Provided to EPA Subtract CSO Area out of Bay Watershed Model Bay Model Segment Agricultural Area Urban/Suburban Area CSO Area Air Deposition Storage Facilities1 CSO-C CSO-O DWF Provide EPA with CSO Overflow (CSO-O) Volume & Loads WWF WWTP Verify that EPA is using the proper Dry Weather Flow and Wet Weather Flow Loads from WWTP DMR Note: 1. Includes Shockoe Retention Basin, Hampton/ McCloy CSO Tunnel & In-line storage

EPA’s Chesapeake Bay TMDL EPA develops Preliminary Load Allocation EPA Modelers to Adjust Loads by Source to meet WQS Bay Model Segment Model Load Control Dial Agricultural Area Urban/Suburban Area CSO Area Air Deposition DCR& DEQ Establishes LAs & WLAs by Locality Storage Facilities1 CSO-C CSO-O DWF EPA to Provide DEQ with Allocation by Source WWF WWTP Note: 1. Includes Shockoe Retention Basin, Hampton/ McCloy CSO Tunnel & In-line storage Note: 2. WLA for MS4 may be an aggregate WLA to an entire watershed segment and revised at the next two year milestone.

EPA’s Chesapeake Bay TMDL Richmond CSO LTCP – Future Controls LTCP Designed to Control Bacteria Bay TMDL IP Schedule should not be tied to LTCP Schedule Bay Model Segment Agricultural Area Urban/Suburban Area CSO Area Air Deposition DCR& DEQ Establishes LAs & WLAs by Locality Storage Facilities CSO-C CSO-O DWF Additional CSO Control Facilities Shift WWF Load Allocation from CSO-O to WWTP (WWF Allocations under Bubble should be considered) WWF WWTP CSO Permitted Bypass for Disinfection

Conclusion of Characterization Report CBP and jurisdictional agencies should ensure that there is consistency between the Long Term Control Plans (LTCPs) developed by the CSS Working Group members and the CSS allocations proposed under the TMDL. This consistency should be expressly acknowledged in the discussion of CSOs and CSO allocations in the final TMDL report.

Chesapeake Bay TMDL Waste Load Allocations for Combined Sewer Systems 20 January 2010 Communication to the Virginia Department of Environmental Quality (DEQ) and follow up to a meeting of 7 December 2009 with the “Communities”. The WLAs should reflect the nutrient and sediment load reductions already achieved by the Communities’ CSO control programs. The combined sewer system WLA-based permit conditions and compliance demonstrations should reflect the fact that combined sewer flows consist largely of storm water and that the resulting flows and loads are highly variable. The WLAs should accommodate load transfers resulting from implementation of CSO controls in the future.

Proposed Chesapeake Bay TMDL Waste Load Allocations and Footnotes for Combined Sewer Systems 24 February 2010 Communication to the Virginia Department of Environmental Quality (DEQ) and follow up to a meeting of 27 January 2010 with the “Communities”. Communities’ proposed CSS WLAs derived using the approach outlined in a letter to DEQ and discussed during our January 27, 2010 meeting. Proposed language for the footnotes to the Communities’ CSS WLAs. Designed to ensure that the basis for the WLAs is clearly stated in the TMDLs. Provide permit writers sufficient guidance and direction to ensure that the CSS-related conditions in the Communities’ VPDES permits are consistent with the assumptions and requirements of the WLAs as required by 40 CFR § 130.7 and 9 VAC 25-31-220.D.1.f.

Establishing WLAs The WLAs for the Communities’ treatment plant dry weather design flow capacities should be kept separate from the WLAs for CSS flows discharged from the plants; The WLAs for Richmond’s and Lynchburg’s CSO outfalls and the WLAs for CSS flows discharged from their treatment plants should be aggregated; and The WLAs for Alexandria’s CSO outfalls and the WLAs for CSS flows discharged from ASA’s treatment plant should be kept separate because they are separate permit holders. This approach will require the following seven WLAs for each of the three pollutants (total nitrogen, total phosphorus, and sediment) for which TMDLs are being established: Two WLAs each for Lynchburg and Richmond (an individual WLA for the dry weather design flow capacity of each city’s treatment plant and an aggregated WLA for each city’s CSO outfalls and CSS flows discharged from each city’s plant); Two WLAs for ASA (an individual WLA for the treatment plant’s dry weather design flow capacity and an individual WLA for CSS flows discharged from the plant); and One WLA for Alexandria (an individual WLA for the City’s CSO outfalls).

Footnotes While this language is proposed as “footnotes” to the WLAs, it is not mean to suggest that it must be included in footnotes. Some or all of this language can be included in the TMDL and Watershed Implementation Plan documents as other than footnotes so long as it is clear that the language is tied to the Communities’ CSS WLAs.

Richmond WWTP Historical Annual Average Flow ‘93-’95 Ave WWTP Load Discharged TN = 1.3 M lbs/yr (54.7 mgd & 8 mg/L) 1994 WWTP Load Discharged TN = 1.4 M lbs/yr (58.0 mgd & 8 mg/L) Critical Period: Bay Model Indicates 1993 thru 1995 63.0 mgd 54.7 mgd 2004 WWTP Load Discharged TN = 1.5 M lbs/yr (63.0 mgd & 8 mg/L) Randomness of Annual Rainfall makes it Infeasible to Calculate Annual Loading Limitation 70 65 60 55 41.55 inches of Rainfall 41.54 inches 34.44 inches Annual Average WWTP Flow 50 Wet Weather Flow Annual Average Treated at WWTP 45 DWF Capacity 40 35 Dry Weather Flow about 37 mgd 30 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 Year

Wastewater Flows Typical Wet Weather Flow Pattern Phase II WWF: 75 mgd Future Phase III: 85 to 90 mgd 10 20 30 40 50 60 70 80 90 100 Date WWTP Flow Rate (mgd) May 13, 2002 May 14, 2002 May 15, 2002 WWF DWF

Chesapeake Bay TMDL Source Sector Allocation Worksheet 25 Feb 2010 EPA EXPECTATIONS FOR WIP: CSO compliance with their approved Long Term Control Plan. Approach to Develop WLA: Determine the nutrient/sediment loads from CSO discharges based upon complete implementation of the approved LTCP for the critical period. Establish WLA for nutrient and sediment loads discharged from VA CSO outfalls and combined flows conveyed to WWTP for full treatment.

In Summary: CSO communities have developed LTCPs in accordance with the national CSO policy as stated in the Clean Water Act. Controls are being implemented under LTCPs for pathogens, floatables, total suspended solids and biochemical oxygen demand. Now, TMDLs look at different goals, different modeling segments, different hydrologic time periods, change the target for pathogen control, and look to control additional pollutants (nitrogen, phosphorus, PCBs, sediment) and pollutant characteristics (chlorophyll A) from CSO communities. A CSO community must secure WLAs in each TMDL whether the LTCP is complete separation or not.

Conclusion You are the only stakeholder who cares that CSOs secure a WLA and if you pass on participating in the TMDL process the outcome and your future will be determined by others. The general idea is to let you the CSO communities have flexibility with the WLAs, so that you can get the most bang for the buck you implement your LTCP and to make sure the TMDL doesn’t actually end up impeding progress toward achieving WQS.