Item_10_-_ EPA_Stormwater_Guidance.pdf
PDF 2 MB Posted
- Attached to
- Southwest Rectangle EcoDistrict - 10th Street, SW and Maryland Avenue, SW, Washington, DC
- Solicitation number
- NCPC-RFI-10-01
- Issued by
-
National Capital Planning Commission
About this file
EPA Stormwater Guidance
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Technical Guidance on Implementing the Stormwater Runoff Requirements for Federal Projects under Section 438 of the Energy Independence and Security Act
United States Environmental Protection Agency
Office of Water (4503T) Washington, DC 20460
EPA 841-B-09-001
December 2009 www.epa.gov/owow/nps/lid/section438
Section 438 Technical Guidance December 2009
Technical Guidance on Implementing the Stormwater Runoff Requirements for Federal Projects under Section 438 of the Energy Independence and Security Act
INTRODUCTION
In December 2007, Congress enacted the Energy Independence and Security Act of 2007.
Section 438 of that legislation establishes strict stormwater runoff requirements for federal development and redevelopment projects. The provision reads as follows:
“Storm water runoff requirements for federal development projects. The sponsor of any development or redevelopment project involving a Federal facility with a footprint that exceeds 5,000 square feet shall use site planning, design, construction, and maintenance strategies for the property to maintain or restore, to the maximum extent technically feasible, the predevelopment hydrology of the property with regard to the temperature, rate, volume, and duration of flow.”
The intent of Section 438 of the Energy Independence and Security Act of 2007 (EISA) is to require federal agencies to develop and redevelop applicable facilities in a manner that maintains or restores stormwater runoff to the maximum extent technically feasible. Until recently, stormwater programs established to address water quality objectives have been designed to control traditional pollutants that are commonly associated with municipal and industrial discharges, e.g., nutrients, sediment, and metals. Increases in runoff volume and peak discharge rates have been regulated through state and local flood control programs. Although these programs have merit, knowledge accumulated during the past 20 years has led stormwater experts to the conclusion that conventional approaches to control runoff are not fully adequate to protect the nation’s water resources (National Research Council, 2008).
Implementation of Section 438 of the EISA can be achieved through the use of the green infrastructure/low impact development (GI/LID) infrastructure tools described in this guidance.
The intention of the statute is to maintain or restore the pre-development site hydrology during the development or redevelopment process. To be more specific, this requirement is intended to ensure that receiving waters are not negatively impacted by changes in runoff temperature, volumes, durations and rates resulting from federal projects. It should also be noted that a performance-based approach was selected in lieu of a prescriptive requirement in order to provide site designers maximum flexibility in selecting control practices appropriate for the site.
Section 14 of the Executive Order 13514, Federal Leadership in Environmental, Energy, and Economic Performance
On October 5, 2009, President Barack Obama signed Executive Order 13514, “Federal Leadership in Environmental, Energy, and Economic Performance.”
Section 14 of the Executive Order provides:
Stormwater Guidance for Federal Facilities. Within 60 days of the date of this order, the Environmental Protection Agency, in coordination with other Federal agencies as appropriate, shall issue guidance on the implementation of section 438 of the Energy Independence and Security Act of 2007 (42 U.S.C. 17094).
This provision contains two significant elements. First, for the first time, EPA is formally assigned the responsibility to write and issue the Section 438 guidance, in coordination with other federal agencies. Second, it establishes a deadline for EPA to do so by December 5, 2009.
Purpose and Organization of this Guidance
The purpose of this document is to provide technical guidance and background information to assist federal agencies in implementing EISA Section 438. Each agency or department is responsible for ensuring compliance with EISA Section 438. The document contains guidance on how compliance with Section 438 can be achieved, measured and evaluated. In addition, information detailing the rationale for the stormwater management approach contained herein has been included.
This document is intended solely as guidance. This document is not a regulation nor does it substitute for statutory provisions or regulations. This guidance does not impose any legally binding requirements on federal agencies and does not confer any legal rights or impose legal obligations upon any member of the public. This document does not create a cause of action against the EPA, other federal agencies, or the United States.
The following information is presented within this document:
Part I: Implementation Framework
A. Background B. Benefits and outcomes of the new stormwater performance requirements C. Applicability and definitions D. Tools to implement the requirements of Section 438 E. Calculating the 95th percentile rainfall event
Part II: Case Studies on Capturing the 95th Percentile Storm Using Onsite Management Practices Case studies representing typical federal installations have been included. The case studies were selected to demonstrate the feasibility of providing adequate stormwater control for a range of site conditions and building designs. To the maximum extent technically feasible, each case study includes a description of a method that can be used to determine the design objectives of the project based on retaining the 95th percentile storm. Examples of onsite technologies and practices have also been provided. The case studies are intended to provide examples of modeling procedures that can be used to quantify treatment system performance and processes for assessing sites and determining appropriate control techniques to the maximum extent technically feasible.
Part I: Implementation Framework
A. BACKGROUND
This section contains background on the causes and consequences of stormwater discharges, solutions that can be used to address the causes and consequences of stormwater discharges and how to implement those solutions to comply with Section 438 of EISA.
Alterations to Natural Hydrology and the Impact on Stormwater Runoff In the natural, undisturbed environment rain that falls is quickly absorbed by trees, other vegetation, and the ground. Most rainfall that is not intercepted by leaves infiltrates into the ground or is returned to the atmosphere by the process of evapotranspiration. Very little rainfall becomes stormwater runoff in permeable soil, and runoff generally only occurs with larger precipitation events. Traditional development practices cover large areas of the ground with impervious surfaces such as roads, driveways, sidewalks, and buildings. Under developed conditions runoff occurs even during small precipitation events that would normally be absorbed by the soil and vegetation. The collective force of the increased runoff scours streambeds, erodes stream banks, and causes large quantities of sediment and other entrained pollutants to enter the water body each time it rains (Shaver, et al., 2007; Booth testimony, 2008).
As watersheds are developed and impervious surfaces increase in area, the hydrology of the watersheds fundamentally changes over time which results in degraded aquatic ecosystems. In recognition of these problems, stormwater managers employed extended detention approaches to mitigate the impacts of increased peak runoff rates. However, wet ponds and similar practices are not fully adequate to protect downstream hydrology because of the following inherent limitations of these conventional practices (National Research Council, 2008; Shaver, et al., 2007):
Poor peak control for small, frequently-occurring storms;
Negligible volume reduction; and Increased duration of peak flow.
Detention storage targets relatively large, infrequent storms, such as the two and 10-year/24-hour storms for peak flow rate control. As a result of this design limitation, flow rates from smaller, frequently-occurring storms typically exceed those that existed onsite before land development occurred and these increases in runoff volumes and velocities typically result in flows erosive to stream channel stability (Shaver, et al., 2007). Section 438 is intended to address the inadequacies of the historical detention approach to managing stormwater and promote more sustainable practices that have been selected to maintain or restore predevelopment site hydrology.
A 2008 National Research Council report on urban stormwater confirmed that current stormwater control efforts are not fully adequate. Three of the report’s findings on stormwater management approaches are particularly relevant (National Research Council, 2008).
1. Individual controls on stormwater discharges are inadequate as the sole solution to stormwater in urban watersheds;
2. Stormwater control measures such as product substitution, better site design, downspout disconnection, conservation of natural areas, and watershed and land-use planning can dramatically reduce the volume of runoff and pollutant load from new development; and
3. Stormwater control measures that harvest, infiltrate, and evapotranspire stormwater are critical to reducing the volume and pollutant loading of small storms.
Pre-development Hydrology. Courtesy of C. May, University of Washington.
Post-Development Hydrology. Courtesy of C.
May, University of Washington.
Figure 1. Pre-Development and Post-Development Hydrology. (USDA).
Figure 1 contains two sets of diagrams depicting the water balances at undeveloped and developed sites. Runoff patterns will vary based on factors such as geographic location, local meteorological conditions, vegetative cover and soils. The first set of figures represents conditions in the Pacific Northwest where storms have a long duration and low intensity, i.e., the volume of rain in an individual storm is small. The second set of figures from the U.S.
Department of Agriculture represents a more generalized set of conditions, but was included to illustrate that heavily urbanized areas typically cause large increases in runoff.
Land cover changes that result from site development include increased imperviousness, soil compaction, loss of vegetation, and loss of natural drainage patterns, which result in increased runoff volumes and peak runoff rates. The cumulative impacts of the land cover changes result in alterations of the natural hydrology of a site, which disrupts the natural water balance and changes water flow paths. The consequences of these impacts include:
1. Increased volume of runoff. With decreased area for infiltration and evapotranspiration due to development, a greater amount of rainfall is converted to overland runoff which results in larger stormwater discharges.
2. Increased peak flow of runoff. Increased impervious surface area and higher connectivity of impervious surfaces and stormwater conveyance systems increase the flow rate of stormwater discharges and increase the energy and velocity of discharges into the stream channel.
3. Increased duration of discharge. Detention systems generate greater flow volumes and rates. These prolonged higher discharge rates can undermine the stability of the stream channel and induce erosion, channel incision and bank cutting.
4. Increased pollutant loadings. Impervious areas are a collection site for pollutants. When rainfall occurs these pollutants are mobilized and transported directly to stormwater conveyances and receiving streams via these impervious surfaces.
5. Increased temperature of runoff. Impervious surfaces absorb and store heat and transfer it to stormwater runoff. Higher runoff temperatures may have deleterious effects on receiving streams. Detention basins magnify this problem by trapping and discharging runoff that is heated by solar radiation (Galli, 1991; Schueler and Helfrich, 1988).
The resulting increases in volume, peak flow, and duration are illustrated in the hydrograph in Figure 2, which is a representation of a site’s stormwater discharge with respect to time. The hydrograph illustrates the impacts of development on runoff volume and timing of the runoff.
Individual points on the curve represent the rate of stormwater discharge at a given time. The graph illustrates that development and corresponding changes in land cover result in greater discharge rates, greater volumes, and shorter discharge periods. In a natural condition, runoff rates are slower than those on developed sites and the discharges occur over a longer time period.
The predevelopment peak discharge rate is also much lower than the post-development peak discharge rate due to attenuation and absorption by soils and vegetation. In the post-development condition there is generally a much shorter time before runoff begins because of increased impervious surface area, a higher degree of connectivity of these areas and the loss of soils and vegetative cover that slow or reduce runoff.
t
Q
Post-Development Condition
Pre-Development Condition
Figure 2. Post-Development Hydrograph.
(Q = volumetric flow rate; t = time)
Figure 3. Stream Displaying the Effects of Stormwater Runoff and Channel Downcutting.
The Solution: Preserving and Restoring Hydrology A new approach has evolved in recent years to eliminate or reduce the amount of water and pollutants that run off a site and ultimately are discharged into adjacent water bodies.
Figure 4. Parking lot bioswale and permeable pavers in Chicago.
The fundamental principle is to employ systems and practices that use or mimic natural processes to: 1) infiltrate and recharge, 2) evapotranspire, and/or 3) harvest and use precipitation near to where it falls to earth.
GI/LID practices include a wide variety of practices that utilize these mechanisms. These practices can be used at the site, neighborhood and watershed/regional scales. In this document the focus is on site-level practices, which is most consistent with the terms used in Section 438:
“project,” “facility,” and “property.” Although these performance requirements apply at the project site-level, flexibility exists to utilize nearby areas or areas directly adjacent to the facility to manage the runoff, i.e., evapotranspirate, infiltrate or harvest and use. Where justifiable, it also may be appropriate to evapotranspirate, infiltrate or harvest and use an equivalent or greater amount of runoff offsite as long as the runoff is discharged or used in the same receiving subwatershed or watershed.
The purpose of EISA Section 438 is to replicate the pre-development hydrology to protect and preserve both the water resources onsite and those downstream. For example, if prior to development, twenty five (25) percent of the annual rainfall runs directly into the stream and the remainder infiltrates into the ground or is evapotranspired into the air, then the post-development goal should be to limit runoff to twenty five (25) percent of the annual precipitation while maintaining the correct aquifer recharge rate. This has the benefit, in most cases, of delivering water to the stream at approximately the same rate, volume, duration and temperature as the stream had naturally evolved to receive prior to development. The result will be to eliminate or minimize the erosion of streambeds and streambanks, significantly reduce the delivery of many pollutants to water bodies, and retain historical instream temperatures.
Restoring or maintaining pre-development hydrology has emerged as a control approach for several reasons. Most importantly, this approach is intended to directly address the root cause of impairment.
Current control approaches have been selected in an attempt to control the symptoms (peak flow, and excess pollutants), but this strategy is not fully adequate because of the scale of the problem, the cumulative impacts of multiple developments and the need to manage both site and watershed level impacts.
With current approaches, it is also difficult to adequately protect and improve water quality because the measures employed are not addressing the main problem which is a hydrologic imbalance.
Designing facilities based on the goal of maintaining or restoring pre-development hydrology provides a site specific basis and an objective methodology with which to determine appropriate practices to protect the receiving environment.
Using pre-development hydrology as the guiding control principal also allows the designer to consider climatic and geologic variability and tailor the solutions to the project location. Thus the need for a one size fits all approach is rendered unnecessary since the design objective is dictated by the pre-development site conditions and other technicalities of the project site and facility. Instead of prescribed approaches dictating discharge volumes or flow rates, site assessments of historical infiltration and runoff rates will inform the designer and provide the basis for a suitable design. The use of this approach will minimize compliance complications that may arise from prescriptive design approaches which do not account for the variability of precipitation frequencies, rainfall intensities and pre-development land cover and soil conditions that influence infiltration and runoff.
B. BENEFITS AND OUTCOMES OF THE NEW STORMWATER PERFORMANCE REQUIREMENTS
Implementation of these new stormwater performance requirements in EISA Section 438 provides numerous environmental and economic benefits in addition to reducing the volume of stormwater runoff:
Benefits to Water Resources:
Cleaner Water. The use of plants, soils and water harvesting and use practices can reduce stormwater runoff volumes and pollutant loadings and the frequency and magnitude of combined sewer overflows (volume and pollutant loading reductions). These practices are part of a larger set of practices called green infrastructure/low impact development.
Clean and Adequate Water Supplies. GI/LID approaches using soil based vegetated infiltration systems can be used to recharge ground water and maintain stream base flow. By recharging ground water aquifers, aquatic ecosystem health is maintained and base flows are increased which helps ensure more constant flows for drinking water withdrawals. Harvesting and reusing rainwater also reduces the need to use potable water for all uses and can reduce both the infrastructure and energy needed to treat and transport both drinking water and stormwater.
Source Water Protection. GI/LID practices provide pollutant removal benefits, thereby providing some protection for both ground water and surface water sources of drinking water. In addition, GI/LID provides ground water recharge benefits.
GI/LID approaches are a set of management approaches and technologies that utilize and/or mimic the natural hydrologic cycle processes of infiltration, evapotranspiration and use. GI/LID practices include green roofs, trees and tree boxes, rain gardens, vegetated swales, pocket wetlands, infiltration planters, porous and permeable pavements, vegetated median strips, reforestation and revegetation and protection of riparian buffers and floodplains.
These practices can be used almost anywhere soil and vegetation can be worked into the urban or suburban landscape. They include decentralized harvesting approaches such as rain barrels and cisterns that can be used to capture and re-use rainfall for watering plants or flushing toilets.
Other Social and Environmental Benefits:
Cleaner Air. Trees and vegetation improve air quality by filtering many airborne pollutants and can help reduce the amount of respiratory illness (Vingarzan and Taylor, 2003).
Reduced Urban Temperatures. Summer city temperatures can average 10ºF higher than nearby suburban temperatures (Casey Trees, 2007). High temperatures are also linked to higher ground level ozone concentrations. Vegetation creates shade, reduces the amount of heat absorbing materials and emits water vapor – all of which cool hot air (Grant, et al., 2003). Reductions in impervious surface and the use of light colored pervious surfaces (e.g., permeable concrete) also can mitigate urban temperatures.
Moderate the Impacts of Climate Change. Climate change impacts and effects vary regionally, but GI/LID techniques can provide adaptation benefits for a wide array of circumstances. They can be used to conserve, harvest and use water, to recharge ground waters and to reduce surface water discharges that could contribute to flooding. In addition, there are mitigation benefits such as reduced energy demand and carbon sequestration by vegetation.
Increased Energy Efficiency. Green space helps lower ambient temperatures and, when incorporated on and around buildings, helps shade and insulate buildings from wide temperature swings, decreasing the energy needed for heating and cooling. Diverting stormwater from wastewater collection, conveyance and treatment systems can reduce the amount of energy needed to pump and treat the water. Energy efficiency not only reduces costs, but also reduces generation of greenhouse gases.
Community Benefits. Trees and plants improve urban aesthetics and community livability by providing recreational and wildlife areas. Studies show that property values are higher when trees and other vegetation are present. Increased green space also has public health benefits and has been shown to reduce crime and the associated stresses of urban living.
C. APPLICABILITY AND DEFINITIONS
Applicability
1. Who is a “Sponsor” of a project?
Section 438 applies to the “sponsor of any development or redevelopment project involving a Federal facility . . .” Section 438 requires that the “sponsor . . . shall use . . . strategies for the property to maintain or restore . . . the predevelopment hydrology. . .” The “sponsor” should
Figure 5. Rain water cistern.
generally be regarded as the federal department or agency that owns, operates, occupies or is the primary user of the facility and has initiated the development or redevelopment project. If the federal agency hires another entity to perform activities such as site construction or maintenance, the agency should nonetheless be regarded as the sponsor and be responsible to assure compliance with the requirements of Section 438. The agency sponsor is free to contract out various duties and responsibilities that are associated with achieving compliance.
2. What is a “Federal facility”?
Section 438 provides that its requirements apply to the “sponsor of any development or redevelopment project involving a Federal facility . . .” Section 401(8) of EISA states: “The term `Federal facility' means any building that is constructed, renovated, leased, or purchased in part or in whole for use by the Federal Government.”
3. What is a “footprint”?
Section 438 applies to a federal facility “with a footprint that exceeds 5,000 square feet.” For the purposes of this guidance, any project involving a federal facility that disturbs 5,000 square feet or more of ground area is covered by this guidance. Existing facilities that have an overall footprint of 5,000 square feet or greater that disturb less than 5,000 square feet of land area as part of any single development or redevelopment project are not subject to Section 438 requirements. Consistent with the purpose of Section 438 to preserve or restore pre-development hydrology, the term “footprint” includes all land areas that are disturbed as part of the project.
4. What is “the property”?
Section 438 provides that the project sponsor “shall use site planning, design, construction, and maintenance strategies for the property to maintain or restore, to the maximum extent technically feasible, the predevelopment hydrology of the property.” This clause has been interpreted to mean that the land surrounding the project site is available to implement the appropriate GI/LID practices where optimal.
Although the performance requirements of EISA Section 438 apply only to the project footprint, the flexibility exists to utilize the entire federal property in implementing the stormwater strategies for the project.
Definitions
95th percentile rainfall event. The 95th percentile rainfall event represents a precipitation amount which 95 percent of all rainfall events for the period of record do not exceed. In more technical terms, the 95th percentile rainfall event is defined as the measured precipitation depth accumulated over a 24-hour period for the period of record that ranks as the 95th percentile rainfall depth based on the range of all daily event occurrences during this period.
The 24-hour period is typically defined as 12:00:00 am to 11:59:59 pm. In general, at least a 20- 30 year period of rainfall record is recommended for such an analysis. This raw data is readily available and collected by most airports across the county. Small rainfall events that are 0.1 of an inch or less are excluded from the percentile analysis because this rainfall generally does not result in any measureable runoff due to absorption, interception and evaporation by permeable, impermeable and vegetated surfaces. Many stormwater modelers and hydrologists typically exclude rainfall events that are 0.1 inch or less from calculations of rainfall events of any storm from their modeling analyses of rainfall event frequencies. See, for example, the Center for Watershed Protection's Urban Subwatershed Restoration Manual 3 (available at www.cwp.org).
Federal facility. The term “federal facility” means any buildings that are constructed, renovated, leased, or purchased in part or in whole for use by the federal government as defined in section 401(8) of the Energy Independence and Security Act.
Development or re-development. For the purposes of this provision this term applies to any action that results in the alteration of the landscape during construction of buildings or other infrastructure such as parking lots, roads, etc, (e.g., grading, removal of vegetation, soil compaction, etc.) such that the changes affect runoff volumes, rates, temperature, and duration of flow. Examples of projects that would fall under “re-development” include structures or other infrastructure that are being reconstructed or replaced and the landscape is altered. Typical patching or resurfacing of parking lots or other travel areas would not fall under this requirement.
D. TOOLS TO IMPLEMENT THE REQUIREMENTS OF SECTION 438
Section 438 of the Energy Independence and Security Act of 2007 reads as follows:
Section 438. Storm water runoff requirements for federal development projects.
The sponsor of any development or redevelopment project involving a Federal facility with a footprint that exceeds 5,000 square feet shall use site planning, design, construction, and maintenance strategies for the property to maintain or restore, to the maximum extent technically feasible, the predevelopment hydrology of the property with regard to the temperature, rate, volume, and duration of flow.
The intention of EISA Section 438 is to preserve or restore the hydrology of the site during the development or redevelopment process. To be more specific, this requirement is intended to ensure that aquatic biota, stream channel stability, and historical aquifer recharge rates of receiving waters are not negatively impacted by changes in runoff temperature, volumes, durations and rates resulting from federal projects. A performance based approach was selected in lieu of a prescriptive requirement in order to provide site designers maximum flexibility in selecting control practices appropriate for the site.
To meet these performance objectives, technically feasible stormwater control practices that are effective in reducing the volume of stormwater discharge should be used. To implement EISA Section 438, this guidance recommends that the federal facility use all known, available and reasonable methods of stormwater retention and/or use to the maximum extent technically feasible (METF). Tools to implement the requirements of Section 438 are described below and illustrated in Figure 8.
http://www.cwp.org/�
Establishing Section 438 Performance Design Objectives Described below are options site designers can use to comply with Section 438. There may be situations where Option 1 (retaining the 95th percentile rainfall event) is not protective enough to maintain or restore the predevelopment hydrology of the project (for example, in some headwater streams). In these cases, Option 2 (site-specific hydrologic analysis) could be used to determine the types of stormwater practices necessary to preserve predevelopment runoff conditions. Option 2 could also be used if predevelopment runoff conditions can be maintained by retaining less than the 95th percentile rainfall event. Because a performance based approach was selected in lieu of a prescriptive requirement in order to provide site designers maximum flexibility in selecting control practices appropriate for the site, Option 2 was provided in recognition that there are established methodologies that can be utilized to estimate the volume of infiltration and evapotranspiration based on site-specific hydrology and thus establish the predevelopment hydrology performance design objectives.
One approach to establishing the performance design objectives is to design, construct, and maintain stormwater management practices that manage rainfall onsite, and prevent the off-site discharge of the precipitation from all rainfall events less than or equal to the 95th percentile rainfall event to the maximum extent technically feasible (METF). This objective should be accomplished by the use of practices that infiltrate, evapotranspire and/or harvest and use rainwater. The 95th percentile rainfall event is the event whose precipitation total is greater than or equal to 95 percent of all storm events over a given period of record. For example, to determine what the 95th percentile storm event is in a specific location, all 24 hour storms that have recorded values over a 30 year period would be tabulated and a 95th percentile storm would be determined from this record, i.e., 5% of the storms would be greater than the number determined to be the 95th percentile storm. Thus the 95th percentile storm would be represented by a number such as 1.5 inches, and this would be the design storm (example 95th percentile storm events for selected cities are presented in Table 1). The designer would then select a system of practices, to the METF, that infiltrate, evapotranspire or harvest and use this volume multiplied by the total area of the facility/project footprint. Methods and data used to estimate the 95th percentile event are discussed in Part II of this document.
For the purposes of this guidance, retaining all storms up to and including the 95th percentile storm event is analogous to maintaining or restoring the pre-development hydrology with respect to the volume, flow rate, duration and temperature of the runoff for most sites. This 95th percentile approach was identified and recommended because this storm size represents the volume that appears to best represent the volume that is fully infiltrated in a natural condition and thus should be managed onsite to restore and maintain this pre-development hydrology for duration, rate and volume of stormwater flows. In general, only large storms generate significant runoff. In addition, this approach was identified because it employs natural treatment and flow attenuation methods that are presumed to have existed on the site before construction of infrastructure (e.g., building, roads, parking lots, driveways,) and is intended to infiltrate or evapotranspirate the full volume of the 95th percentile storm. Because this approach necessitates the use of practices that generally preclude extended detention, it will also typically address the
Option 1: Retain the 95th Percentile Rainfall Event
Figure 6. Bioretention facility in Oregon.
issue of maintaining predevelopment temperatures. However, in cases where there are discharges to cool water streams or other sensitive receiving waters, additional strategies may be needed to ensure that stormwater discharges do not result in greater thermal impacts than would occur in pre-development conditions (Schueler and Helfrich, 1988).
Where technically feasible, the goal of Option 1 is that one hundred percent (100%) of the volume of water from storms less than or equal to the 95th percentile event over the footprint of the project should not be discharged to surface waters. In some cases, runoff can be harvested and used and ultimately may be discharged to surface waters or a sanitary treatment system; such direct or indirect discharges must be authorized or allowed by the regulatory authority. For example, if runoff is captured for nonpotable uses such as toilet flushing or other uses that are not irrigation related, these waters potentially could be discharged into the sanitary sewer system.
Preferred mechanisms for retaining discharges from storms greater than the 95th percentile event are through overflow or diversion for the volume that exceeds the 95th percentile amount.
Because standard underdrains typically discharge from smaller storms as well, underdrain designs, if employed, should ensure adequate retention capacity for the 95th percentile event volume. For structures such as roofs and paved surfaces that can increase the temperature of stormwater runoff, materials that minimize temperature increases (e.g., concrete vs. asphalt;
vegetated roofs) should be considered and used as appropriate.
Retaining 100 percent of all rainfall events equal to or less than the 95th percentile rainfall event was identified as Option 1 because small, frequently-occurring storms account for a large proportion of the annual precipitation volume, and the runoff from those storm events also significantly alters the discharge frequency, rate and temperature of the runoff.
The runoff produced by these small storms and the initial portion of larger storms has a strong negative cumulative impact on receiving water hydrology and water quality. In areas that have been developed, runoff is generated from almost all storms, both small and large, due to the impervious surfaces associated with development and the loss of soils and vegetation.
In contrast, natural or undeveloped areas discharge little or no runoff from small storms because the rain is absorbed by the landscape and vegetation. Studies have shown that increases in runoff event frequency, volume and rate can be diminished or eliminated through the use of GI/LID designs and practices, which infiltrate, evapotranspire and capture and use stormwater.
Option 1 was identified because it is a simplified approach to meet the intent of Section 438 in contrast to Option 2 which requires the designer to conduct a hydrologic analysis of the site based on site-specific conditions.
Table 1. Example 95th Percentile Storm Events for Select U.S. Cities (adapted from Hirschman and Kosco, 2008).
City
95th Percentile Event Rainfall
Total (in) City
95th Percentile Event Rainfall
Total (in)
Atlanta, GA 1.8 Kansas City, MO 1.7
Baltimore, MD 1.6 Knoxville, TN 1.5
Boston, MA 1.5 Louisville, KY 1.5
Buffalo, NY 1.1 Minneapolis, MN 1.4
Burlington, VT 1.1 New York, NY 1.7
Charleston, WV 1.2 Salt Lake City, UT 0.8
Coeur D’Alene, ID 0.7 Phoenix, AZ 1.0
Cincinnati, OH 1.5 Portland, OR 1.0
Columbus, OH 1.3 Seattle, WA 1.6
Concord, NH 1.3 Washington, DC 1.7
Denver, CO 1.1
0.0
1.0
2.0
3.0
4.0
5.0
6.0
7.0
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Percentile
R ai n fa ll D ep th in ch es
95%
Figure 7. Rainfall Frequency Spectrum showing the 95th percentile rainfall event for Portland, OR (~1.0 inches)
Calculating the 95th Percentile Rainfall Event Section E of this guidance contains information on how to calculate the 95th percentile rainfall event for a specific area. A long-term record of daily rainfall amounts (ideally, at least 30 years) is needed to calculate the 95th percentile rainfall.
Designers opting to use Option 1 need to do the following:
1) calculate or verify the precipitation amount from the 95th percentile storm event (this number would be typically expressed in inches, e.g., 1.5”, and
2) employ onsite stormwater management controls to the METF that infiltrate, evapotranspire or harvest and use the appropriate design volume.
The 95th percentile event can be calculated by using the following procedures below (summarized from Hirschman and Kosco, 2008, Managing Stormwater in Your Community: A Guide for Building an Effective Post-Construction Program, Center for Watershed Protection):
Obtain a long-term rainfall record from a nearby weather station (daily precipitation is fine, but try to obtain at least 30 years of daily record). Long-term rainfall records can be obtained from many sources, including NOAA at http://cdo.ncdc.noaa.gov/pls/plclimprod/poemain.accessrouter?datasetabbv=SOD&countr yabbv=&georegionabbv=.
Remove data for small rainfall events that are 0.1 inch or less and snowfall events that do not immediately melt from the data set. These events should be deleted since they do not typically cause runoff and could potentially cause the analyses of the 95th percentile storm runoff volume to be inaccurate.
Using a spreadsheet or simple statistical package, sort the rainfall events from highest to lowest. In the next column, calculate the percentage of rainfall events that are less than each ranked event (event number/total number of events). For example, if there were 1,000 rainfall events and the highest rainfall event was a 4” event, then 999 events (or a percentile of 999/1000, or 99.9%) are less than the 4” rainfall event.
Use the rainfall event at 95% as the 95th percentile storm event.
Another approach to establishing the performance design objective is to design, construct, and maintain stormwater management practices that preserve the pre-development runoff conditions following construction. Option 2 allows the designer to conduct a site-specific hydrologic analysis to determine the pre-development runoff conditions instead of using the estimated volume approach of Option 1. Under Option 2, the pre-development hydrology would be determined based on site-specific conditions and local meteorology by using continuous simulation modeling techniques, published data, studies, or other established tools. If the designer elects to use Option 2, the designer would then identify the pre-development condition of the site and quantify the post-development runoff volume and peak flow discharges that are equivalent to pre-development conditions. The post-construction rate, volume, duration and
Option 2: Site-Specific Hydrologic Analysis http://cdo.ncdc.noaa.gov/pls/plclimprod/poemain.accessrouter?datasetabbv=SOD&countryabbv=&georegionabbv� http://cdo.ncdc.noaa.gov/pls/plclimprod/poemain.accessrouter?datasetabbv=SOD&countryabbv=&georegionabbv� temperature of runoff should not exceed the pre-development rates and the predevelopment hydrology should be replicated through site design and other appropriate practices to the maximum extent technically feasible. These goals should be accomplished through the use of infiltration, evapotranspiration, and/or rainwater harvesting and use. Defensible and consistent hydrological assessment tools should be used and documented. Additional discussions of appropriate methodologies to use in assessing site hydrology have been included in the technical sections of this document. See, for example, the discussion of spreadsheet versions or curve numbers based on the Natural Resource Conservation Service Technical Release 55 (TR-55) Method in Appendix A of this document.
Development The pre-development hydrologic condition of the site is the combination of runoff, infiltration and evapotranspiration rates and volumes that typically existed on the facility site before "development" on a greenfields site (meaning any construction of infrastructure on undeveloped land such as meadows or forests). In practice, determining the pre-development hydrology of a given site can be difficult if there is no suitable reference site. As a result, reference conditions for typical land cover types in the locality often are used to approximate what fraction of the precipitation ran off, soaked into the ground or was evaporated from the landscape. The use of reference conditions can be problematic if suitable data are not available or unique site conditions exist that do not fit within a typical land use cover type for the area, e.g., meadow or forest. In cases where suitable data from comparable conditions cannot be found or is otherwise inadequate to be used in conducting an Option 2 analysis for the specific area being considered for development or redevelopment, the project sponsor should use the Option 1 analytical framework.
Re-development For re-development sites, existing site conditions and uses of the site can influence the amount of runoff that can be managed on site through infiltration, evapotransporation and harvest and use and thus the performance design objective. In these cases the design process in Figure 8 and Scenario 9 illustrate the decision processes that can be used.
In the context of some re-development projects, fully restoring predevelopment hydrology can be difficult to achieve and Congress recognized this potential difficulty by including the METF language in the statute. In these cases, Congressional intent can be best carried out by using a systematic METF analysis to determine what practices can be implemented at the site to maintain or store the hydrologic condition of the site. Scenarios 1-8 provide examples of METF analyses that demonstrate that pre-development hydrology can be achieved. Scenario 9 provides an example of an METF analysis that demonstrates that pre-development hydrology cannot be fully achieved and illustrates the extent to which pre-development hydrology can be restored.
Note: It should also be emphasized that the performance based approach in Option 1 is intended to be a surrogate for determining the pre-development reference condition and this standard is intended to be used in cases where it is more practical, cost effective, and/or expeditious than Option 1, or where it is difficult or infeasible to identify the relevant reference conditions for the site.
Determination of Maximum Extent Technically Feasible
Compliance with Section 438 requires that stormwater management measures are implemented to the maximum extent technically feasible (METF) to maintain or restore the pre-development hydrology conditions specifically with respect to temperature, rate, volume, and duration of flow.
Performance or design goals based on the pre-development hydrology can be established by using options such as the following: Retention of the 95th percentile rainfall event (Option 1), or through a site-specific hydrologic analysis that estimates the volume of infiltration, evapotranspiration or onsite stormwater harvesting and use based on site-specific hydrologic conditions (Option 2).
Technical Infeasibility
For projects where technical infeasibility exists, the federal agency or department sponsoring the project should document and quantify that stormwater strategies, such as infiltration, evapotranspiration, and harvesting and use have been used to the METF, and that full employment of these types of controls are infeasible due to site constraints. Some western states place restrictions on harvesting and use due to water rights, however, these requirements do not necessarily preclude the sponsor of the project from implementing strategies such as infiltration and evapotranspiration. Documentation of technical infeasibility should include, but may not be limited to, engineering calculations, geologic reports, hydrologic analyses, and site maps. A determination that the performance design goals cannot be met on site should include analyses that rule out the use of an adequate combination of infiltration, evapotranspiration, and use measures. Examples of where site conditions may prevent the full employment of appropriate management techniques to the METF include a combination of:
The conditions on the site preclude the use of infiltration practices due to the presence of shallow bedrock, contaminated soils, near surface ground water or other factors such as underground facilities or utilities.
The design of the site precludes the use of soil amendments, plantings of vegetation or other designs that can be used to infiltrate and evapotranspirate runoff.
Water harvesting and use are not practical or possible because the volume of water used for irrigation, toilet flushing, industrial make-up water, wash-waters, etc. is not significant enough to warrant the design and use of water harvesting and use systems.
Modifications to an existing building to manage stormwater are not feasible due to structural or plumbing constraints or other factors as identified by the facility owner/operator.
Small project sites where the lot is too small to accommodate infiltration practices adequately sized to infiltrate the volume of runoff from impervious surfaces, Soils that cannot be sufficiently amended to provide for the requisite infiltration rates, Situations where site use is inconsistent with the capture and use of stormwater or other physical conditions on site that preclude the use of plants for evapotranspiration or bioinfiltration.
Retention and/or use of stormwater onsite or discharge of stormwater onsite via infiltration has a significant adverse effect on the site or the down gradient water balance of surface waters, ground waters or receiving watershed ecological processes.
State and local requirements or permit requirements that prohibit water collection or make it technically infeasible to use certain GI/LID techniques.
Compliance with the Section 438 requirements would result in the retention and/or use of stormwater on the site such that an adverse water balance impact may occur to the receiving surface waterbody or ground water.
Please note that a single one of these characteristics is very unlikely to preclude meeting the performance standard, but a combination of factors may.
In cases where the facility has a defensible showing of technical infeasibility and can provide adequate documentation of site conditions or other factors that preclude full implementation of the performance design goal, the facility should still install stormwater practices to infiltrate, evapotranspire and/or harvest and use onsite the maximum amount of stormwater technically feasible. Note: Facilities must still comply with all other applicable federal, state and local requirements.
Figure 8. Section 438 Implementation Process
Documenting EISA Section 438 Implementation Each agency or department is responsible for ensuring compliance with Section 438. It is recommended that: 1) the final design and as-built drawings of each facility shall be reviewed by a registered professional engineer and 2) the agency or department develop and maintain documentation of the following design criteria for each project subject to Section 438:
Site evaluation and soils analysis Calculations for the 95th percentile rainfall event or the pre-development runoff volumes and rates to identify the volume of stormwater requiring management Documentation of modifications to the performance design objective based on technical constraints (site-specific METF determination) The site design and stormwater management practices employed on the site Design calculations for each stormwater management practice employed The respective volume of stormwater managed by each practice and the system as a whole Operations and maintenance protocols for the stormwater management system
The information should provide the necessary documentation and detail to demonstrate compliance and operation of stormwater management practices for the entire site.
Common Green Infrastructure/Low Impact Development Tools to Implement Section 438 Although Congress did not prescribe specific practices to be used to implement Section 438 it can be inferred that one of the goals of the Act was to promote the use of innovative stormwater management approaches, designs and practices that better protect receiving water quality, flow regimes and provide other important environmental benefits. GI/LID are preferred practices, to be supplemented with or replaced with conventional controls when site specific conditions dictate.
The GI/LID management approaches and technologies that federal agencies would typically use enhance and/or mimic the natural hydrologic cycle processes of infiltration, evapotranspiration, and use. Federal agencies can also use footprint reduction practices (e.g., building up instead of out) to reduce their stormwater impact. GI/LID approaches include biological systems and engineered systems. These include but are not necessarily limited to:
Rain gardens, bioretention, and infiltration planters Porous pavements Vegetated swales and bioswales Green roofs Trees and tree boxes Pocket wetlands Reforestation/revegetation using native plants Protection and enhancement of riparian buffers and floodplains Rainwater harvesting for use (e.g., irrigation, HVAC make-up, non-potable indoor uses).
GI/LID practices are recommended to implement EISA Section 438 for the following reasons:
cost savings in many cases
Figure 9. Disconnected downspout discharging to planter box.
overall environmental performance pollutant loading reduction capability pollution prevention focus effectiveness in managing runoff volumes and rates energy efficient and energy conservative appropriate in a wide range of site condition and locations appropriate for new development and redevelopment projects appropriate at multiple scales of development, e.g., site, neighborhood, region
For more information on specific GI/LID practices and how they function, visit:
www.epa.gov/gree…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .