£EPA
United States EPA/600/R-17/255 I February 2018
Environmental Protection
Agency www.epa.gov/ord
WATERSHED MANAGEMENT OPTIMIZATION
SUPPORTTOOL (WMOST) v3
User Guide
Office of Research and Development
National Health and Environmental Effects Research Laboratory
-------
-------
EPA 600/R-17/255 | Februaiy
2018 www.epa.gov
Watershed Management Optimization
Support Tool (WMOST) v3
User Guide
EPA Project Team
Naomi Detenbeck, Amy Piscopo, and Marilyn ten Brink
NHEERL, Atlantic Ecology Division
Narragansett, RI 02882
Chris Weaver
NCEA, Washington, DC 20460
Alisa Morrison and Timothy Stagnitta
ORISE participants at ORD, NHEERL, Atlantic Ecology Division
Narragansett, RI 02882
Ralph Abele, Jackie LeClair, and Trish Garrigan
Region 1
Boston, MA 02109
Abt Associates Project Team
Viktoria Zoltay, Annie Brown, Alyssa Le, Justin Stein, and Isabelle Morin
Abt Associates, Inc.
Cambridge, MA 02138
National Health and Environmental Effects Research Laboratory
Office of Research and Development
U.S. Environmental Protection Agency
Washington, DC 20460
-------
WMOST v3 User Guide
Notice
The development of the information in this document has been funded by the U.S. Environmental
Protection Agency (EPA), in part by EPA's Green Infrastructure Initiative, under EPA Contract No.
EP-C-13-039/ Work Assignment 07 to Abt Associates, Inc. Version 2 ofWMOST was supported through
funding to an EPA Region 1 Regional Applied Research Effort (RARE) project. Versions 1 through 3 of this
document have been subjected to the Agency's peer and administrative review and have been approved for
publication. Mention of trade names or commercial products does not constitute endorsement or
recommendation for use.
Although a reasonable effort has been made to assure that the results obtained are correct, the
computer programs described in this manual are experimental. Therefore, the author and the U.S.
Environmental Protection Agency are not responsible and assume no liability whatsoever for any
results or any use made of the results obtained from these programs, nor for any damages or litigation
that result from the use of these programs for any purpose.
Abstract
The Watershed Management Optimization Support Tool (WMOST) is a decision support tool that
facilitates integrated water management at the local or small watershed scale. WMOST models the
environmental effects and costs of management decisions in a watershed context that is, accounting
for the direct and indirect effects of decisions. The model considers water flows and water quality. It
is spatially lumped with options for a daily or monthly modeling time step. In this version (v3),
management option cost optimization occurs through nonlinear programming. As a screening tool,
WMOST contributes to an integrated watershed management process such as that described in EPA's
watershed planning handbook (EPA 2008). WMOST serves as a public-domain, efficient, and user-
friendly tool for local water resources managers and planners to screen a wide range of potential
water resources management options across their jurisdiction for cost-effectiveness and
environmental and economic sustainability (Zoltay et al., 2010). WMOST includes functions to
evaluate various management practices, including projects related to stormwater (including green
infrastructure [GI] and combined sewer overflow ([CSO] systems), stream restoration, water supply,
wastewater and land resources such as low-impact development (LID) and land conservation.
WMOST can aid in evaluating LID and green infrastructure as alternative or complementary
management options in projects proposed for grant funding. In WMOST v3, the Baseline Hydrology
and Loadings and Stormwater Hydrology and Loadings Modules assist users with input data
acquisition and pre-processing. The Combined Sewer Overflow (CSO) Module allows for the
evaluation of management options to minimize the number of CSO events. The Flood Module allows
the consideration of flood damages and their reduction in assessing the cost-effectiveness of
management practices. The target user group for WMOST consists of local water resources managers,
including municipal water works superintendents and their consultants.
Keywords: Integrated watershed management, water resources, decision support, optimization, green
infrastructure
-------
Table of Contents
Table of Contents
Notice ii
Abstract ii
List of Figures iv
List of Tables iv
Preface v
Acknowledgements viii
1. Background 1
1.1 Objective of the Tool 1
1.2 Overview 1
2. Getting Started 8
2.1 Preparing for a Model Run 8
Defining Hydrologic Response Units 8
Defining the Study Area 10
Defining the Modeling Time Period 10
Performing a Simulation Run for Calibration 11
2.2 System Requirements 12
3. Model Setup and Runs 13
3.1 General Model Setup 13
3.2 Baseline Hydrology and HRU Areas 14
3.3 Managed Hydrology and HRU Areas/Stormwater Management 20
3.4 Water Use and Demand Management 33
3.5 Water Supply Sources and Infrastructure 40
3.6 CSO Module 51
3.7 Flood Module 53
3.8 Measured Streamflow and In-stream Concentrations 53
4. Optimization and Results 55
4.1 Running Optimization 55
4.2 Evaluating Results 56
4.3 Calibration Module 59
iii
-------
WMOST v3 User Guide
5. Flood Damage Modeling with HAZUS 62
5.1 Data Needed 62
5.2 Creating the 100-Year Flood Depth Grid from FEMA NFHL Data 63
5.3 Creating the Flood Depth Grid from Lake Elevation Flooding 66
5.4 Creating Flood Depth Grids for the 10, 50 and 500-Year Events 67
5.5 Creating a Site Specific Building Inventory 68
6. User Tips 72
7. References for Watershed Simulation Models Incorporated into WMOST Hydrology and
Loadings Databases 74
8. User Guide References 75
Appendix A - Module and Page Summary 76
Figure 1-1. Schematic of Possible Loadings Flows and Possible Watershed Components
in WMOST 2
Figure 1-2. Schematic of Potential Combined Sewer Flows in the WMOST 3
Table 0-1. Summary of Development ofWMOST and Supporting Organizations vi
Table 1-1. Summary of Management Goals and Management Practices 5
iv
-------
Preface
Preface
Integrated Water Resources Management (IWRM) has been endorsed for use at multiple scales. The
Global Water Partnership defines IWRM as "a process which promotes the coordinated development
and management of water, land and related resources, in order to maximize the resultant economic
and social welfare in an equitable manner without compromising the sustainability of vital
ecosystems" (UNEP-DHI, 2009). IWRM has been promoted as an integral part of the "Water Utility
of the Future" (NACWA, 2013) in the United States. The American Water Resources Association
(AWRA) has issued a position statement, calling for implementation of IWRM across the United
States and committed the AWRA to help strengthen and refine IWRM concepts.1
Several states and river basin commissions have started to implement IWRM (AWRA, 2012). For
example, in the arid West, both Oregon and California have incorporated integrated water resources
management into their planning strategies.2 Even in EPA Region 1 where water is relatively plentiful,
states face the challenge of developing balanced approaches for equitable and predictable distribution
of water resources to meet both human and aquatic life needs during seasonal low flow periods and
droughts. The state of Massachusetts recently spearheaded the Sustainable Water Management
Initiative (SWMI) process to allocate water among competing human and aquatic life uses in a
consistent and sustainable fashion (MA EAA, 2012). WMOST has been applied in pilot projects
funded by the state of Massachusetts to apply IWRM in the permit planning process.3
Stormwater and land use management are two aspects of IWRM which include practices such as
green infrastructure (GI, both natural GI and structural stormwater best management practices
[BMPs]), low-impact development (LID) and land conservation. In a few notable cases, local
managers have evaluated the relative cost and benefit of preserving green infrastructure compared to
traditional approaches. In those cases, the managers have championed the use of green infrastructure
as part of a sustainable solution for IWRM, but these examples are rare.4
In order to assist communities in the evaluation of GI, LID, and land conservation practices as part
of an IWRM approach, EPA's Office of Research and Development, in partnership with EPA's
Region 1, supported the development of several versions of the Watershed Management Optimization
Support Tool (WMOST). Table 0-1 below summarizes the supporting organizations and development
of WMOST.
1 http://www.awra.org/policy/policy-statements-IWRM.html, January 22,2011.
2 http://www.oregon.gov/owrd/pages/law/integrated_water_supply_strategy.aspx, http://www.water.ca.gov/irwm/,
accessed June 2017.
3 See examples at http://www.abtassociates.com/wma.
4 http://www.crwa.org/blue.html
v
-------
WMOST v3 User Guide
Table 0-1. Summary of Development of WMOST and Supporting Organizations
Version
Year
Released
Supporting Organization(s)
Model Enhancements
Version 1 (vl)
2013
EPA Office of Research and
Development (ORD), EPA Region 1
Version 2 (v2)
2016
RARE grant to EPA Regionl and ORD
collaborators, US EPA ORD's Green
Infrastructure Initiative research
program
Baseline Hydrology and
Stormwater Hydrology
Modules
Flood Damage Module
Version 3 (v3)
2017
US EPA ORD's Green Infrastructure
Initiative research program
Baseline Hydrology and
Loadings and Stormwater
Hydrology and Loadings
Modules
Water Quality Module
CSO Module
Calibration Module
WMOST is based on a prior integrated watershed management optimization model that was created
to allow water resources managers to evaluate a broad range of technical, economic, and policy
management options within an urban or mixed-use watershed (Zoltay, V. I., 2007; Zoltay et al.,
2010). This model includes evaluation of conservation options for source water protection and
infiltration of stormwater on forest lands, green infrastructure stormwater BMPs to increase
infiltration, and other water quantity and quality related management options.
Development of each version of the WMOST tool was overseen by an EPA Planning Team. Priorities
for update and refinement of the original model (Zoltay, V. I., 2007; Zoltay et al., 2010) were
established following review by a Technical Advisory Group (TAG) comprised of water resource
managers and modelers. Case studies for two communities (Upper Ipswich River, and
Danvers/Middleton, MA) were developed to illustrate the application of IWRM using WMOST.
These case studies are available from the WMOST website5. WMOST was presented to stakeholders
in a workshop held at the EPA Region 1 Laboratory in Chelmsford, MA, in April 2013, with a
follow-up webinar on the Danvers/Middleton case study in May 2013. Feedback from the Technical
Advisory Group and workshop participants has been incorporated into the user guide and theoretical
documentation for WMOST.
The development of the Baseline Hydrology, Stormwater Hydrology and Flood Damage Modules in
WMOST v2 was assisted by a TAG with expertise in one or more of these topics. Prior to
development of WMOST v2, US EPA Region 1 solicited communities in the Taunton River
watershed for interest in testing and applying WMOST to solve their problems, and Halifax, MA, was
5 https://www.epa.gov/exposure-assessment-models/wmost
vi
-------
Preface
identified as an interested collaborator. Multiple meetings with stakeholders in the Monponsett Pond
watershed (Halifax, MA) were held to engage the community in a case study application of WMOST
v2. Input from the TAG and community members were incorporated in the final methodology for
WMOST v2 and the modeling case study.
WMOST v2.1 corrected for known errors in WMOST v2, but did not include significant model
changes. The corrections addressed the following issues:
• Aquifer storage and recharge (ASR) facility constraint and cost equations were using
incorrect variable names
• Limits on interbasin transfer volumes
o limit exclusions were not functioning properly
o potential additional interbasin transfer volumes were not being correctly multiplied
by the number of days in the month when modeling with a monthly time step
• Recharge from pervious and disconnected impervious areas was not blended when
calculating total recharge for a hydrologic response unit (HRU)
• WMOST v2 equations inaccurately modeled a time step delay in groundwater discharges
from the ASR facility and the septic system
• Cost equation for insufficient water penalty (make-up water) did not include an annualization
factor
• Calculation of the annualization factor over the modeling period did not take into account
leap years
Two training workshops for WMOST v2.1 were held in summer 2016, the first with joint sessions at
EPA Region 1 in Boston, MA, and at the University of RI - Kingston, RI, in June and the second
during the International LID conference in Portland, Maine, in August. Presentations from the June
workshop were recorded and are available on the WMOST website5.
Development of Version 3 of WMOST was informed by input from stakeholders involved in three
case study applications of WMOST. The first case study, focused on the upper Taunton River
watershed in Massachusetts (Wading, Mill, and Threemile River subwatersheds), was coordinated
with a consortium (Manomet, Audubon, Nature Conservancy, and the Southeastern Regional
Development Commission), which had received a grant from EPA Region 1 to evaluate the potential
uses for and to educate municipalities in the Taunton River watershed about the value of natural and
constructed green infrastructure under both current and future climate and growth scenarios. The
second case study, focused on the Cabin John Creek watershed in Montgomery County, MD, was
designed for the Maryland Department of the Environment (MDE) to evaluate costs and benefits of
different stormwater BMPs while meeting local targets for a sediment total maximum daily load
(TMDL) as well as downstream loading targets for total suspended solids, total nitrogen, and total
phosphorus for the Chesapeake Bay TMDL. The third case study, focused on subwatersheds of the
Middle Kansas River, Kansas, was designed with EPA Region 7 and Kansas Department of Health
5 https://www.epa.gov/exposure-assessment-models/wmost
vii
-------
WMOST v3 User Guide
and Environment (KDHE) to evaluate BMPs (including agricultural BMPs) in a mixed land-use
watershed to meet waters quality targets for local TMDLs. Results of these case studies will be made
available on the WMOST website when complete.
Two ancillary utilities are being developed in conjunction with WMOST v3: a preprocessor (the
HydroProcessor) and a Scenario Comparison Tool (ScenCompare), both funded with support from
EPA's Safe and Sustainable Waters and from EPA's Air, Climate, and Energy research program. The
HydroProcessor facilitates import and formatting of model outputs from hydrological models such as
HSPF and SWAT to provide runoff, recharge, and loading inputs to WMOST. The ScenCompare tool
facilitates comparison of outputs from multiple WMOST runs, e.g., to evaluate the implications of
different climate change scenarios on optimal management actions
Acknowledgements
WMOST builds on research funded by the National Science Foundation Graduate Research
Fellowship Program and published in "Integrated Watershed Management Modeling: Optimal
Decision Making for Natural and Human Components." Zoltay, V. I., Kirshen, P.H., Vogel, R.M.,
and Westphal, K.S. 2010. Journal of Water Resources Planning and Management, 136:5, 566-575.
HSPF-derived hydrology time series in data library for WMOST v2 and v3 were produced by the US
Geological Survey (Jeff Barbara) under separate interagency agreements (DW-14-92400901, DW-
014-92452101).
EPA Project Team
Naomi Detenbeck6, Marilyn ten Brink6, U.S. EPA ORD, NHEERL, Atlantic Ecology Division
Ralph Abele7, Jackie LeClair7 and Trish Garrigan7, U.S. EPA Region 1
Amy Piscopo8, U.S. EPA ORD, NHEERL, Atlantic Ecology Division,
Chris Weaver8, NCEA, Washington, DC
Yusuf Mohamoud9, U.S. EPA ORD, NERL, Ecosystems Research Division
Alisa Morrison1" and Tim Stagnitta8, ORISE participants at U.S. EPA ORD, NHEERL,
Atlantic Ecology Division
Technical Advisory Group for WMOST vl
Alan Cathcart, Concord, MA Water/Sewer Division
Greg Krom, Topsfield, MA Water Department
Dave Sharpies, Somersworth, NH Planning and Community Development
0 Versions 1 through 3
7 Versions 1 through 3
8 Version 3
9 Version 1
10 Version 2
viii
-------
Acknowledgements
Mark Clark, North Reading, MA Water Department
Peter Weiskel, U.S. Geological Survey, MA-RI Water Science Center
Kathy Baskin, Massachusetts Executive Office of Energy and Environmental Affairs
Steven Estes-Smargiassi, Massachusetts Water Resources Authority
Hale Thurston, U.S. EPA ORD, NRMRL, Sustainable Technology Division
Rosemary Monahan, U.S. EPA Region 1
Scott Horsley, Horsley Witten Group
Kirk Westphal, CDM Smith
James Limbrunner, Hydrologies, Inc.
Jay Lund, University of California, Davis
Technical Advisory Group for WMOST v2
Bob Lent, U.S. Geological Survey
Darryl Davis and Chris Dunn, U.S. Army Corps of Engineers, Hydrologic Engineering Center
Matthew Bates, U.S. Army Corps of Engineers, Engineer Research and Development Center
Richard Zingarelli, Massachusetts Department of Conservation and Recreation
Steve Silva, former U.S. EPA and Taunton watershed stakeholder
Tom Johnson, U.S. EPA, ORD, Global Change Research Program
Marisa Mazzotta, U.S. EPA, ORD, NHERRL, Atlantic Ecology Division
Reviewers for WMOST vl
Theoretical Documentation
Marisa Mazzotta, U.S. EPA ORD, NHEERL, Atlantic Ecology Division
Mark Voorhees, U.S. EPA Region 1
Michael Tryby, U.S. EPA ORD, NERL, Ecosystems Research Division
WMOST Tool. User Guide and Case Studies
Daniel Campbell, U.S. EPA ORD, NHEERL, Atlantic Ecology Division
Alisa Richardson, Rhode Island Department of Environmental Management (partial review)
Alisa Morrison, Student Services Contractor at U.S. EPA ORD, NHEERL, Atlantic Ecology Division
Jason Berner, U.S. EPA OW, OST, Engineering Analysis Division
Reviewers for WMOST v2
Theoretical Documentation
Kristen Hychka, ORISE participant at U.S. EPA ORD, NHEERL, Atlantic Ecology Division
Mark Voorhees, U.S. EPA Region 1, Boston, MA
Thomas Johnson, U.S. EPA ORD, NCEA, Washington, D.C.
WMOST Tool. User Guide and Case Studies
Jason Berner, U.S. EPA OW, OST, Engineering Analysis Division
Yusuf Mohamoud, U.S. EPA ORD, NERL, Athens, GA
Stephen Kraemer, U.S. EPA ORD, NERL, Athens, GA
Andrea Traviglia, U.S. EPA Region 1, Boston, MA
Cathy Drinan, Board of Health, Halifax, MA
ix
-------
WMOST v3 User Guide
Reviewers for WMOST v3
Theoretical Documentation
Marissa Mazotta, U.S. EPA ORD, NHEERL, Narragansett, RI
Stephen Kraemer, U.S. EPA ORD, NERL, Los Angeles, CA
Brenda Rashleigh, U.S. EPA ORD, IOAA, Narragansett, RI
WMOST Tool. User Guide, and Case Studies
Jason Berner, U.S. EPA ORD, NRMRL, Washington, DC
Soni Pradhanang, University of RI, Kingston, RI
Dino Marshalonis, U.S. EPA Region 10, Seattle, WA
Mark Voorhees, U.S. EPA Region 1, Boston, MA
Previous Contributors
Yusuf Mohamoud, ORD, NERL, Ecosystems Research Division, Athens, GA 30605
Becky Wildner and Lauren Parker, Abt Associates, Inc.
Nigel Pickering, Horsley Witten Group under subcontract to Abt Associates Inc.
Richard M. Vogel, Tufts University under subcontract to Abt Associate Inc.
x
-------
1. Background
1. Background
1.1 Objective of the Tool
The Watershed Management Optimization Support Tool (WMOST) is a public-domain enhancement to
Microsoft Office Excel 2010, 2013 and 2016 designed to aid decision making in integrated water
resources management. WMOST is intended to serve as an efficient and user-friendly tool for water
resources managers and planners to screen a wide-range of strategies and management practices for cost-
effectiveness and environmental sustainability in meeting watershed or jurisdiction management goals
(Zoltay et al. 2010).
Overall, WMOST is intended to be used as a screening tool as part of an integrated watershed
management process such as that described in EPA's watershed planning handbook (EPA 2008), to
identify the strategies and practices that seem most promising for more detailed evaluation. WMOST
identifies the least-cost combination of management practices to meet the user specified management
goals. Management goals may include reducing damages associated with flooding and meeting projected
water supply demand, minimum and maximum in-stream flow targets, and in-stream and reservoir water
quality targets. The tool considers a range of management practices related to water supply and quality,
wastewater, nonpotable water reuse, aquifer storage and recharge, sewer and CSO systems, stormwater,
low-impact development (LID) and land conservation, accounting for both the cost and performance of
each practice. In addition, WMOST may be run for a range of values for management goals to perform a
cost-benefit analysis and obtain a Pareto frontier or trade-off curve. For example, running the model for a
range of minimum in-stream flow standards provides data to create a trade-off curve between increasing
in-stream flow and total annual management cost.
1.2 Overview
WMOST combines an optimization framework with water resources modeling to evaluate the effects of
management decisions within a watershed context. The watershed system modeled in WMOST v3 is
shown in Figure 1-1. Figure 1-lshows the possible watershed system components and potential water
loadings among the watershed components, including the use of upgraded WTP, WWTP, and septic
systems for additional loadings reductions. Figure 1-2 shows the possible watershed component
interactions when CSO events are modeled. This figure only provides a diagram of the components that
have different possible flows when modeling these events (sewer, wastewater treatment, and surface
water components).
1
-------
WMOST v3 User Guide
Source Water
Treated Water
Wastewater
Water Reuse
from
O from WWTP WWTP
External SW
Private SW
oint Loading
Surface Water
to Storm
Interbasin
Interbasin
Transfer:
Transfe
Water Reuse
Potable
astewater
Facility
Water
Land Use Areas,
Runoff &
Recharge Rates
Storm Sewer
(StS)
from Reservoir
Point Loadings
O
to ASR
Nonpotable Use
Sanitary
5ewer
(SanS)
Baseline HRUs
to SW
Consumptive
Potable WTPI
Upgraded WTP
WWTP
Upgraded
WWTP
Stormwater
Reservoir
Managed
HRUs
6
from SW
to Externa SW
Aquifer Storage
and Recovery
(ASR)
0
from
Sanitary Sewer
Infiltration
Rotable Ui>e
Reservoir Point
Loadings
to External GW
Recharge
Septic Systems/
Enhanced
Septic
Groundwater
Out of
Basin
Infiltration to
Sanitary Sewer
to Reservoir
External GW;
Private GW
oint Loading
Flow in or
out of the system
Component
without storage
Component
with storage
1 All components shaded purple may reduce
loadings via ol" or 1* order decay
2 All component shaded red may reduce
loadinos via treatment or enhanced treatment
Flow jump between
components
Enhanced
Treatment
Loadings
Treated
Loadings
Untreated
loadings
Loadings out
of system
Figure 1-1. Schematic of Possible Loadings Flows and Possible Watershed Components in
WMOST.
SW = surface water, GW = groundwater, HRU = hydrologic response unit, WTP =
water treatment plant, WWTP = wastewater treatment plant, ASR = aquifer storage
and recharge
2
-------
1. Background
Source Water
Treated Water
Wastewater
Water Reuse
External SW:
from WWTP
Private SW
Withdrawal &
ischarges
Surface Water
[SW)
to StS
Interbasin
Interbasin
or CS
Transfer:
Transfe
Water Reuse
Facility
Potable
astewater
Water
Land Use Areas,
Runoff &
Recharge Rates
Combined
Sewer (CS)
Offline
[Storm Sewer '
(StS)3 j
Combined
Sewer (CS)
npotable Use
Storage
'Sanitary Sewer j
JSanS) _ j Lo sw
toASR
Baseline HRUs
from
Reservoir
Consumptive
Stormwater
Managed
HRUs1
Potable WTP
Reservoir
WW IV
from SW
to Externa SW
Aquifer Storage
and Recovery
(ASR)
0
from
SanS or CS
Infiltration
Potable Use
to External GW
Recharge
Groundwater
Out of
Septic Systems
Basin
Infiltration
External GW
Private GW
Withdrawals &
ischarges*
to SanS or CS
Flow in or
out of the system
O Component
with storage
Component
without storage
Flow jump between
components
1 Private GW and SW withdrawals and discharges are water flows only; see water quality flows in Figure 2-
2 Up to ao stormwater management options may be modeled representing traditional, green infrastructure or low impact development practices or combination of practices.
3 Sewer components with dotted outlines indicate a management option for minimizing combined sewer overflow events. Flow may go through either sewer component.
4 This flow represents the fraction of municipal water use that is routed directly to the storm sewer (e.g., hydrant flushing).
Figure 1-2. Schematic of Potential Combined Sewer Flows in the WMOST.
SW = surface water, StS = storm sewer, HRU = hydrologic response unit,
SanS = sanitary sewer treatment plant, CS = combined sewer,
WWTP = wastewater treatment plant
3
-------
WMOST v3 User Guide
The principal characteristics of WMOST include:
• Implementation in Microsoft® Excel 2010, 2013, and 2016® that is linked seamlessly with Visual
Basic for Applications (VBA) and NEOS (Czyzyk et al. 1997; Dolan 2001; Gropp and More 1997),
a free, online optimizer, eliminating the need for specialized software and using the familiar Excel
platform for the user interface;
• User-specified inputs for characterizing the watershed, management practices, and management
goals and generating a customized optimization model (see Table 1-1 for a list of available
management practices and goals);
• Use of BONMIN (Bonami et al. 2008), a mixed integer nonlinear programing (MINLP)
optimization solver (freely available through NEOS), to determine the least-cost combination of
practices that achieves the user-specified management goals (See Section 3-1 in the Theoretical
Documentation report for WMOST for details on BONMIN, MINLP optimization, and the
software configuration);
• Spatially lumped calculations modeling one basin and one reach but with flexibility in the number
ofHRUs,11 each with an individual runoff and recharge rate;
• Modeling time step of a day or month without a limit on the length of the modeling period;12
• Solutions that account for both the direct and indirect effects of management practices (e.g., since
optimization is performed within the watershed system context, the model will account for the fact
1) that implementing water conservation will reduce water revenue, wastewater flow and
wastewater revenue if wastewater revenue is calculated based on water flow or 2) that
implementing infiltration-based stormwater management practices will increase aquifer recharge
and baseflow for the stream reach which can help meet minimum in-stream flow requirements
during low precipitation periods, maximum in-stream flow requirements during intense
precipitation seasons, and water supply demand from increased groundwater supply);
• Ability to specify up to ten stormwater management options, including traditional (detention
basins), green infrastructure, LID, or agricultural runoff control practices;
• Enforcement of physical constraints, such as the conservation of mass (i.e., water and loadings),
within the watershed; and
• Consideration of both water quantity and quality.
The rest of this document is organized as follows. Section 2 provides considerations for model definition
and setup and directions for computer and software preparation. Section 3 leads the user through model
setup with screenshots. Section 4 provides directions for initiating an optimization run, and processing
and analyzing optimization results. Section 5 provides directions for performing flood damage modeling
to derive input data for the Flood Damage Module. Section 6 summarizes tips for the user in performing
model runs and analyzing results, including methodology for conducting sensitivity analyses and trade-off
analyses.
11 Land cover, land use, soil, slope and other land characteristics affect the fraction of precipitation that will runoff, recharge
and evapotranspire. Areas with similar land characteristics that respond similarly to precipitation are termed hydrologic
response units.
12 While the number ofHRUs and modeling period are not limited, solution times are significantly affected by these
model specifications. It is recommended to model a maximum of 32 HRUs and five years at a daily time step.
4
-------
1. Background
A separate Theoretical Documentation report provides a detailed description of WMOST that includes a
mathematical description and internal configuration of the software applications that constitute the model
Case study examples are presented in individual documents and are provided with the WMOST files.
These example applications may be used as a source of default data, especially for similar watersheds in
Region 1 and similar sized water and wastewater systems. Case study examples for WMOST v3 will be
added in the near future.
Table 1-1. Summary of Management Goals and Management Practices13-
MGD = million gallons per day
Management
Practice
Action14
Model Component
Affected
Impact
Land conservation
Increase area of land
use type specified as
'conservable'
Land area allocation
Preserve runoff and recharge
quantity and quality
Stormwater
management via
traditional, agricultural,
green infrastructure or
low impact
development practices
Increase area of land
use type treated by
specified management
practice
Land area allocation
Reduce runoff; increase recharge
and treatment
Agricultural stormwater
runoff management via
traditional and green
infrastructure
Increase area of land
use type treated by
specified management
practice
Land area allocation
Reduce runoff; increase
recharge; increase treatment
Stormwater quality
management via street
sweeping, tree canopy
over impervious/turf,
urban nutrient
management, or other
direct reduction runoff
loadings BMPs
Percent reduction of
runoff loadings
Runoff loadings
Reduce runoff loadings to meet
in-stream or reservoir loading
targets
Riparian buffer land use
management
Increase area of land
use type in the riparian
zone
Land area allocation
and runoff loadings
Reduce runoff; reduce loadings
to stream to help meet in-stream
or reservoir loadings targets
Surface water storage
capacity
Increase maximum
storage volume
Reservoir/Surface
Storage
Increase storage; reduce demand
from other sources
Surface water pumping
capacity
Increase maximum
pumping capacity
Potable water treatment
plant
Reduce quantity and/or timing of
demand from other sources
Groundwater pumping
capacity
Increase maximum
pumping capacity
Potable water treatment
plant
Reduce quantity and/or timing of
demand from other sources
13 The user may specify which practices are available for their study area and are to be included in the optimization.
Directions for this are provided with each practice in the User Manual and WMOST interface.
14 Please refer to the separate Theoretical Documentation for the specific effect of each management practice.
5
-------
WMOST v3 User Guide
Table 1-1 (continued)
Management
Practice
Action14
Model Component
Affected
Impact
Change in quantity of
surface versus
groundwater pumping
Change in pumping
time series for surface
and groundwater
sources
Potable water treatment
plant
Change the timing of withdrawal
impact on water source(s)
Potable water treatment
capacity
Increase MGD
Potable water treatment
plant
Meet potable human demand;
meet water quality treatment
standards
Potable water treatment
upgrade
Increase treatment
Potable water treatment
plant
Further reduce loadings from
potable water treatment
Leak repair in potable
distribution system
Decrease % of leaks
Potable water treatment
plant
Reduce demand for water
quantity
Convert septic to
sewered areas
Increase MGD, reduce
% customers on septic
Wastewater treatment
plant, septic discharge
Maintain or improve water
quality of receiving water
Wastewater treatment
capacity
Increase MGD
Wastewater treatment
plant
Maintain or improve water
quality of receiving water
Wastewater treatment
upgrade
Increase treatment
Wastewater treatment
plant
Further reduction of loadings
from wastewater treatment
Infiltration repair in
wastewater collection
system
Decrease % of leaks
Wastewater treatment
plant
Reduce demand for wastewater
treatment capacity
Water reuse facility
(advanced treatment)
capacity
Increase MGD
Water reuse facility
Produce water for nonpotable
demand, ASR, and/or improve
water quality of receiving water
Nonpotable distribution
system
Increase MGD
Nonpotable water use
Reduce demand for potable
water
Aquifer storage &
recharge (ASR) facility
capacity
Increase MGD
ASR facility
Increase recharge, treatment,
and/or supply
Demand management
by price increase
Increase % of price
Potable and nonpotable
water and wastewater
Reduce demand
Direct demand
management
Percent decrease in
MGD
Potable and nonpotable
water and wastewater
Reduce demand
Interbasin transfer -
potable water import
capacity
Increase or decrease
MGD
Interbasin transfer -
potable water import
Increase potable water supply or
reduce reliance on out of basin
sources
Interbasin transfer -
wastewater export
capacity
Increase or decrease
MGD
Interbasin transfer -
wastewater export
Reduce need for wastewater
treatment plant capacity or
reduce reliance on out of basin
services
14 Please refer to the separate Theoretical Documentation for the specific effect of each management practice.
6
-------
1. Background
Table 1-1 (continued)
Management
Practice
Action14
Model Component
Affected
Impact
Enhanced septic
treatment
Decrease septic
average effluent
concentration
Septic
Use upgraded treatment within
the septic system
Sewer separation
Decrease flows
through the combined
sewer
Storm sanitary, and
combined sewers
Minimize combined sewer
overflow events
Offline storage
Delay flows to the
wastewater treatment
facility through the
sewer system
Combined sewer
Minimize combined sewer
overflow events
Streambank restoration
or stabilization
Apply a loadings
credit to the loadings
target in the stream or
reservoir
Surface water or
reservoir
Meet in-stream or reservoir
loading targets
Outfall enhancement or
stabilization
Apply a loadings
credit to the loadings
target in the stream or
reservoir
Surface water or
reservoir
Reduce loadings to stream or
reservoir to meet in-stream or
reservoir loading targets
Minimum human water
demand
MGD
Groundwater and
surface water pumping
and/or interbasin
transfer
Meet human water needs
Minimum in-stream
flow
ft3/sec
Surface water
Meet in-stream flow standards;
improve ecosystem health and
services; improve recreational
opportunities
Maximum in-stream
flow
ft3/sec
Surface water
Meet in-stream flow standards;
improve ecosystem health and
services by reducing scouring,
channel and habitat degradation;
decrease loss of public and
private assets due to flooding
Target concentration or
loadings
mg/L or lbs
Surface water or
reservoir
Meet in-stream or reservoir
TMDL targets; improve
ecosystem health and services;
improve recreational
opportunities
14 Please refer to the separate Theoretical Documentation for the specific effect of each management practice.
7
-------
WMOST v3 User Guide
2. Getting Started
WMOST is a screening tool for watershed management and planning. One specific application of
WMOST is determining the least cost combination of management options to meet management goals for
a town or watershed's planning horizon. For example, the water works portion of a town's master plan
may ask, "What stormwater practices must be installed, demand management programs created and/or
infrastructure capacity constructed to meet projected human demand for the next 20 years while meeting
minimum and maximum in-stream flow targets and in-stream/reservoir water quality targets to preserve
stream health?" To address such a planning question, all input data must correspond to the conditions
projected to occur by the end of a 20-year planning period. For example, human demand would need to be
projected 20 years from the planning year. Most of the User Guide is written from the perspective of a
user who is screening management practices to address such planning questions. Suggestions are provided
throughout the User Guide and in the case studies15 for how to specify input data appropriately. It is
important to note that while the model does help users identify which management practices are the most
cost effective and understand the state of the watershed and human system at the end of the planning
period if the management practices are implemented, it does not provide an annual implementation plan
or specifics on operations of systems. The following sections describe what input data managers should
assemble for a detailed model run and discuss how to set up a model run and obtain and interpret the
results.
2.1 Preparing for a Model Run
This section describes model specifications the user must consider prior to applying WMOST v3. Data
sources used in the case studies will be detailed in subsequent reports. Some of those data sources, such as
costs for riparian buffer land conversion, are state or national level and can serve as a data source for most
study areas. If this is not the case, environmental or economic data may be found in the literature
(particularly grey literature sources, such as governmental and technical reports or guidelines). The
majority of the data related to the human water system should be available to municipalities from their
own internal sources. Water utilities may need to seek out information from other public works facilities
that operate in the study area, such as separate wastewater and stormwater utilities or neighboring water
districts. Sections 3.2 through 3.5 in this User Guide address both hydrologic and water quality input data.
Users that are interested in hydrologic flows only should disregard any mentions of water quality
considerations.
Defining Hydrologic Response Units
A main input data requirement is time series of both runoff and recharge rates (RRR) and runoff and
recharge loadings (RRL) for HRUs16 in the study area and the corresponding area for each HRU. The
RRR time series are not volumetric but rates that must be input as depth per unit area per time step (e.g.,
15 Case study documents are available on the WMOST website.
10 Land cover, land use, soil, slope and other land characteristics affect the fraction of precipitation that will runoff, recharge and
evapotranspire. Areas with similar characteristics - hydrologic response units (HRUs) - respond similarly to precipitation.
8
-------
2. Getting Started
inches per acre17 per day). The RRL time series are mass rates that must be input as mass per unit area
(e.g., pounds per day). The Baseline Hydrology Module in WMOST v3 assists users in obtaining and pre-
processing the time series data. The Baseline Hydrology Module connects to the runoff and recharge time
series databases stored online via EPA's Estuary Data Mapper (EDM) server18.
If watersheds in the available databases do not have similar slopes, land uses, or soils in the study area's
watershed, the user may derive these data from a calibrated/validated simulation model such as
Hydrological Simulation Program Fortran (HSPF)19, Soil Water and Assessment Tool (SWAT)20 and/or
Storm Water Management Model (SWMM)21. The WMOST HydroProcessor is a tool that processes
HSPF and SWAT model files to create WMOST hydrology and loadings input databases22. Furthermore,
several post-processors such as GenScn and WDMutil in EPA BASINS23 are available to facilitate
extraction of hydrology time series from HSPF model output wdm files.
If a watershed simulation model is not available for the study area (e.g., from U.S. Geological Survey)
and resources do not allow for the creation and setup of a model, then the user may try using default rates
from models run for watersheds with similar characteristics (i.e., similar land-use, soils, climate).
Additionally there may be generic RRRs and RRLs available from state or regional studies (Maurer et al.
2001). The generic rates would specify the HRU characteristics for which the rates are applicable. A
geographic information system (GIS) or local land use data can be used to determine the area associated
with each HRU in the study area. We suggest using 8 to 16 HRUs (with input field limit of 50) in the
model to control the complexity of the optimization problem. HRU types may be aggregated to reduce
this number if the GIS analysis suggests more than 16 HRUs.
In addition to a baseline set of HRUs, up to nine sets of "managed" HRUs may be specified with
corresponding areas, RRRs, RRLs, and management costs. The baseline set is used to specify runoff and
recharge for HRUs for the baseline conditions of the model run. For managed sets, you may specify
runoff and recharge rates that reflect some form of land management practice and the associated cost such
as stormwater management. With such information, the model can evaluate the cost-effectiveness of
stormwater management relative to other practices.
For urban HRUs, the "managed set" may reflect RRRs and RRLs resulting from use of a stormwater best
management practice (e.g., bioretention basin, swales) and/or low impact development with reduced
impervious area. Managed RRRs and RRLs may be used to represent any change in land use or land
17 Runoff depth is actually independent of area; however this value is multiplied by HRU areas in WMOST to yield runoff
volume.
18 The Estuary Data Mapper (EDM) application uses the Remote Sensing Information Gateway (RSIG) web servers as conduits
for accessing data. The datasets that are available can be viewed through the EDM application or found on the EDM Data
Inventory site, https://www.epa.gov/edm.
19 http://water.usgs.gov/software/HSPF/
20 http://swat.tamu.edu/
21 https://www.epa.gov/water-research/storm-water-management-model-swmm
22 The WMOST HydroProcessor is available on the WMOST website.
23 http://water.epa.gOv/scitech/datait/models/basins/framework.cfm#tools
9
-------
WMOST v3 User Guide
management practice that changes runoff and recharge volume or timing. For example, results of detailed
modeling of LID or other practices may be entered as a managed set of RRRs and RRLs. Within
WMOST, the user may model LID that results in less impervious surface. The user must run the Baseline
Hydrology Module in a separate WMOST file to obtain the RRRs corresponding to a developed HRU
with a lower impervious surface percent. These RRRs can be entered as a managed set with a
corresponding cost, if any, in the primary WMOST file. Alternatively, if a BMP with the equivalent effect
is known, it may be requested in the Stormwater Module. In WMOST v3, the Stormwater Hydrology
Module assists the user in pre-processing the time series and other data necessary for including
stormwater management. Alternatively, these managed RRRs and RRLs may be derived using SWMM or
other stormwater management models outside of WMOST and then manually input to WMOST. For
agricultural HRUs, the "managed set" may reflect RRRs and RRLs resulting from implementation of
edge of site BMPs or vegetative filter strips on undeveloped areas.
For each set, you can specify the area of each HRU on which the management practice may be
implemented. For each stormwater managed set, urban BMPs are applied to urban HRUs only, and
agricultural BMPs are applied to undeveloped HRUs only. In addition, if stormwater management exists
in part of the watershed, HRUs may be defined separately for areas that already have stormwater
management and remaining areas that can still be placed under management. Then, the addition of new
stormwater management may be limited to the unmanaged HRUs and excluded for managed HRUs.
Defining the Study Area
Ideally, the study area is the entire land area draining to the stream reach of interest; however,
jurisdictional boundaries often cut across subbasins. This requires that the hydrology and loadings runoff
and recharge time series are modeled at the subbasin or watershed level24 while management practices are
limited to those areas within the jurisdiction(s) cooperating in the management plan. The case study of
Danvers and Middleton, MA, shows the example of how to use the model in such circumstances. The
case study of the Upper Taunton River Basin assumes that the entire watershed is cooperating in the
management strategy such as in a water district and, therefore, management practices are specified to be
applicable for the entire watershed25. In general, we suggest study areas that are roughly the size of a
HUC10 or HUC12 subbasin, or smaller.
Defining the Modeling Time Period
The model may be run on a daily or monthly time step. One exception is that the model must be run at the
daily time step when using the Flood Damage Module to include flood damages in the calculation of the
total management cost. The user may choose the time step depending on the temporal resolution of
available input data, desired management practices and/or known system behavior. For example, if
stormwater management practices will be considered, a daily time step is advised as storm events and
24 In cases where groundwater flows cross the watershed divide, the user can specify groundwater imports and exports beyond the
watershed boundary.
25 If the user wants to model multiple adjacent/downstream study areas, theoretically, the time series of surface water outflow
from the upstream study area may be used an input into the downstream study area. WMOST v3 outputs this time series in
table form via the Advanced Results module. Enhanced spatial modeling is identified as an area for future development so that
all areas or reaches can be optimized simultaneously rather than just consecutively from upstream to downstream reaches.
10
-------
2. Getting Started
their effects are observable on a time scale closer to a daily rather than monthly time step. If the user
desires to know the monthly or approximate water balance for watershed or human system components
such as reservoir storage, then a monthly time step would be sufficient.
The user should run the model for multiple years that cover dry, average and wet years of precipitation.
That is, input time series (e.g., RRRs, RRLs, human demand, and surface water inflow from upstream)
should include a range of potential conditions. This approach will ensure that the management solution
screened by the model will be sustainable over a range of potential future conditions. In addition, the user
is advised to run not only a range of historical conditions but future, projected conditions. The WMOST
EDM data inventory provides a library of time series based on down-scaled climate projections for
specific watershed models. The climate projections available from EDM cover the years 2036-2065.
Users may also derive potential future climate conditions, for example, by adjusting historical conditions
for projected climate change. EPA's Climate Resilience Evaluation and Awareness Tool provides
projected changes in temperature and precipitation for climate stations throughout the United States26.
These values may be used to adjust the detailed watershed simulation model from which watershed time
series data is obtained for WMOST and to adjust the traditional methodology used for projecting human
demand. Model-specific tools are available to adjust weather inputs to SWAT (climate change function),
HSPF (BASIN CAT), and SWMM (SWMM CAT).
Note that running WMOST with data from a specific time period such as 2005-2010 does not necessarily
represent watershed conditions that only occurred during those years but watershed conditions that would
occur in a similar 5-year period of weather, water use and land conditions. Therefore, these data can be
adjusted for climate change or other uncertainties and re-run to determine the sensitivity of the solution,
that is, combination of management practices and costs, to potential future deviations from historical
conditions. In fact, the user is highly encouraged to perform sensitivity analyses especially on input data
with least certainty to determine the robustness of the solution. Section 6 briefly describes the process for
performing sensitivity analyses.
Performing a Simulation Run for Calibration
A simulation run is advised before optimization runs to determine the accuracy of WMOST and the input
data in reproducing streamflow and water quality constituent concentrations. A simulation run excludes
all management decisions; therefore, the input data are run through the model without changes in
management of the system. This requires that certain input data be specified differently from an
optimization setup which is described in the rest of this document.
There are two methods for setting up a calibration run: 1) with demand for water modeled explicitly as
groundwater or surface water withdrawals, or 2) with demand for water modeled as withdrawals managed
by the optimization with the Potable Demand page. The first method is used for calculating the water
balance in your watershed and verifying that your data inputs result in a model that simulates the
historical record. The second method is used for verifying that optimization selects similar quantities and
timing for water withdrawals compared to the historical record. This method can help verify that the
infrastructure costs and capacities are accurate, as those data inputs have an effect on water quantity
26 https://www.epa.gov/crwu/build-resilience-your-utility
11
-------
WMOST v3 User Guide
selections made by the model. The case study of Danvers and Middleton, MA, in the User Guide for
Version 1 and the case study for Halifax, MA, in the User Guide for Version 2 describe the process for
performing a "simulation" run in more detail.
2.2 System Requirements
To open and run WMOST, you will need Microsoft® Excel 32bit version 2010, 2013, or 2016 installed
on your computer. After opening WMOST, choose 'Enable content' or 'Enable macros' if these prompts
are displayed. If using MS Excel 2013, please see "WMOST 2.0 2013 Performance Fix" file available on
the WMOST download site to change configurations to correct an Excel performance bug.
To run the Baseline Hydrology Module of WMOST, users can process their data by 1) downloading
WMOST databases using the Estuary Data Mapper (www.epa.gov/edm)27, or 2) accessing these databases
from the WMOST v3 download. If you have data from a calibrated/validated model already, you can skip
using the Baseline Hydrology Module and manually enter your data on the appropriate input pages.
To run the Stormwater Hydrology Module, you will need to download and install EPA's stormwater
management tool, System for Urban Stormwater Treatment and Analysis Integration (SUSTAIN) Version
1.228. SUSTAIN has been available in two versions: non-GIS and ArcGIS 9.3. The non-GIS version is
compatible with the Stormwater Hydrology Module. To prevent errors, do not move SUSTAIN files
automatically created during installation from their default location.
When using WMOST, you may save various versions that are set up for different scenarios. It is not
recommended that you run multiple scenarios at the same time from the same folder as the optimization
files may be overwritten by a different scenario. When using the Baseline Hydrology and Stormwater
Hydrology Modules, WMOST performs best when saved and run on a local drive, rather than a network
drive, to save processing time. When using the Stormwater Hydrology Module, WMOST must be saved
to a location with no spaces in the file path. Furthermore, most Windows computers cannot handle file
path names that are longer than 260 characters. WMOST saves files to your project folder so ensure that
the project folder path and scenario name are under this character limit.
Running optimization scenarios and the Results Module multiple times in succession can cause the
memory on your computer to fill. If this happens, save and close your WMOST project and re-open to
free up memory and speed up processing.
Finally, if you encounter software errors, please email Naomi Detenbeck at detenbeck.naomi@epa.gov
with the subject "WMOST bug". To register for notices of patches and new releases, please email the
same address with the subject line "WMOST register.
27 The inventory of available models in Estuary Data Mapper is available on the EDM and WMOST websites.
28 https://www.epa.gov/water-research/system-urban-stormwater-treatment-and-analysis-integration-sustain
12
-------
3. Model Setup and Runs
3. Model Setup and Runs
3.1 General Model Setup
When you open WMOST you will see the familiar Excel interface with one worksheet
active called Intro. The Intro page allows you to set general specifications for your
model and navigate to the more detailed input data page (blue section in the screenshot
to the right), create optimization model files and process results (red section), and
evaluate and calibrate results (green section).
Begin setting up your model by typing in a study area name to the appropriate input
field. Input fields that are outlined but shaded white are not required but highly
suggested for model optimization. By contrast, the input field below your study area
name is shaded blue. Input fields that are shaded blue typically require data input29. This
particular input field is already filled in as "Hydrology & Loadings" and if you click on
it, its appearance changes (see below) because it holds a drop-down menu. For any input
field with a drop-down menu, you are limited to the options
listed in the drop-down menu, in this case either Hydrology
ENTER INPUT DATA
Study Area Name:
Hydrology & Loadings |
Proceed to
Input Data
RUN OPTIMIZATION
Scenario Name:
:
Optimize
Hybrid (B-Hyb)
Hydrology & Loadings T
Process Results
EVALUATE RESULTS
Results Table
Advanced Results
Calibration Module
Compare to Measured
& Target Flows
Compare to Measured
& Target Water Quality
& Loadings or Hydrology Only. One type of field that is not represented on the Intro
page are those that are automatically populated, and subsequently, shaded yellow.
Finally, the object below the model type is a button that allows you to navigate to the
Input page. In general, you can identify buttons by hovering your mouse over the object
in question. Your cursor should change from a cross to a pointer.
On this page, you may also enter a study area name or a scenario name. These input fields may help you
document your WMOST projects and differentiate between scenario workbooks. These fields are used to
name the "Scenario Log File", which is a part of the Results Module output. Consequently, you may not
use the following characters in the study area or scenario name: < > : " / \ | ? *.
Please note that any example screenshots (similar to the one above) with values displayed in them are
from the Upper Taunton Wading River case study and are not necessarily appropriate values for your
study area. WMOST performs several basic checks to ensure that input data requirements are met. For
example, it will check that price elasticities are negative and minimum in-stream flow targets are smaller
than maximum in-stream flow targets. If these basic requirements are not met, the user is informed with a
message box and asked to re-enter the information. Appendix D in the Theoretical Documentation
provides additional details on input data checks and user support.
To begin entering data for your study area, press the Proceed to Input Data button to navigate to the Input
page. The Input page consists of seven3" steps that will guide you through inputting the necessary data to
set up your optimization model.
29 Some pages and input fields can be left blank depending on desired management options.
30 If you are modeling Hydrology and Loadings, step 5 (Combined Sewer Overflow module) will not be visible.
13
-------
WMOST v3 User Guide
Throughout the manual, buttons will be underlined and workbook pages will be bolded. A full list of
workbook pages and their related module can be found in Appendix A - Module and Page Summary.
3.2 Baseline Hydrology and HRU Areas
HRUs are areas of similar hydrology based on similar watershed characteristics such as land use, soil
and/or slope. The number of HRUs will likely be determined by the diversity of these characteristics in
your study area and your source of runoff and recharge rates. You have the option to either download
existing hydrologic model outputs ready for input into WMOST or import hydrologic model outputs that
you have prepared for input into WMOST. If you are downloading existing model outputs, continue with
Input Page Step IA Assisted - Baseline Hydrology Module section. If you would like to manually enter
the data, skip to Input Page Step IA Manual - Baseline Hydrology section for instructions.
Input Page Step 1A Assisted - Baseline Hydrology Module
1. Baseline: Data for unmanaged land conditions.
A. Time aeries data:
Use Baseline Hydrology module for assisted data acquisition and entry
-------
3. Model Setup and Runs
1A. Retrieve Data from U.S. EPA's Estuary Data Mapper (EDM): Make watershed selections and retrieve the HRU characteristics and weather data for your model.
1. Locate the EDM WMOSI Database Inventory file on your computer drive:
EDM WMOST Database Inventory File Path
2. Enter the name of your watershed: 3. Select the model type:
4. Select the land use scenario: 5. Select the climate scenario: 6. Lnter the HUC ID for your subbasin:
Taunton j | HSPF
1990s
Baseline | | 0l09000403j
7. After you have made the above selections, use "Retrieve Charcteristics & Weather Data" to initiate the EDM data request:
Retrieve Characteristics & Weather Data
In substeps #2 - 6, enter your model and subbasin selection and press Retrieve Characteristics & Weather
Data. If the dataset selections do not match a model in the inventory. WMOST will inform you of the
error after pressing this button. If the selections have a match, the button initiates the automatic data
retrieval of the weather and HRU database zip file from the server. Once the download is complete.
WMOST unzips your data to a folder labeled "EDM_Scrvcr ZIP" within your project folder, and
autmatically imports the HRU characteristics and the precipitation time series for the available model
time period.
If you would like to use files previously downloaded in a past query, you can import the HRU
characteristics database in Step IB by selecting the file path of your HRU characteristics file. To find and
view the HRU characteristics file, navigate to the "EDM Servcr_ZIP" folder in your project folder, and
search for the Dbase ( dbf) file in the unzipped ""w mostEDM w eather" folder. This file can be opened and
viewed with Excel.
After the files load, the table in Hydro page Step 2 "Hydrologic Response Units (HRUs)" will
automatically populate the HRU types that were modeled in that watershed. Select the HRUs that exist
within your study area and that you will be modeling by placing an "x" in the blue column next to each
HRU name. Then, press Populate Land Use to set up appropriately sized input tables (i.e., Baseline Land
Use table and Baseline Runoff and Recharge Hydrology and Loadings tables on Land Use, Runoff,
Recharge, Runoff L. and Recharge L)
2. Hydrologic Response Units (HRUs). The following HRU types are aflaiLble in the selected watershed.
2A. Select which HRUs exist in your study area by placing an x in blue boxlf|xt Jfthe HRU type 2B. Then press "Populate Land Use" to populate Land Use table with each HRU's name.
HRU types in the selected watershed
infiltration rate and percent effective impervious area.
Forest, Sand & Gravel & Gravel
x
^^PopTrtat^anc^s^^^ |
Open/non-residential, Sand & Gravel & Gravel
X
Medium-low density. Sand & Gravel
X
Medium-high density, Sand & Gravel
X
Commercial-industrial, Sand & Gravel
X
Agriculture, Sand & Gravel
X
Forest, Till & Fine-Grained Deposits
X
Open/non-residential, Till & Fine-Grained Deposits
X
Medium-low density, Till & Fine-Grained Deposits
X
Medium-high density, Till & Fine-Grained Deposits
X
Commercial-industrial, Till &Fine-Grained Deposits
X
Agriculture, Till & Fine-Grained Deposits
X
Cranberry Bog
X
Forested Wetland
X
Nonforested Wetland
X
Water
X
Once the table setups are complete, you will be taken to the Land Use page showing the baseline area,
percent effective impervious area (EIA) and infiltration rate for each HRU. These values were
automatically populated based on the selected watershed model. Review the value for these HRU
characteristics to make sure that they are appropriate for the HRUs in your study area. If you plan to use
the Stormwater Hydrology Module to create adjusted hydrology time series, HRUs with non-zero EIA
15
-------
WMOST v3 User Guide
will be utilized with
any urban BMPs and
HRUs with zero EIA
will be utilized with
any agricultural
BMPs. However, you
can edit any Percent
Effective Impervious
value in the HRU
series to change the
BMP types that are
applied.
Next, return to the
Hydro page and
continue with Hydro
page Step 3 -
selecting the modeling time period. The time period of available data for the selected watershed is
displayed in the yellow box. You may use the View Precipitation Data button to open a new page and see
the entire precipitation time series available for the selected watershed model if you retrieved the data
using the EDM data library. Otherwise, press Load Precipitation Data in Hydro page Step 3B, and select
the hydrology database file to import the precipitation time series. Viewing the precipitation data may
help in selecting wet, dry or average precipitation time periods.
A model setup with a daily time step for five years takes about 5-90 minutes to run, depending on the
complexity of the optimization problem. We do not recommend longer time periods than five years and
instead suggest running scenarios with five-year periods that include wet, dry and average conditions.
Enter the desired start and end of the modeling time period in the appropriate blue input boxes.
Baseline HRU Characteristics
Percent
Infiltration
Baseline Area
Effective
Rate
HRU ID
HRU Name1
[acre]
Impervious1
[in/hr]1
HRU1B
Forest, Sand & Gravel & Gravel
13,647
0.00%
9.5
HRU2B
Open/non-residential, Sand & Gravel & Gravel
2,296
4.26%
8.455
HRU3B
Medium-low density, Sand & Gravel
5,949
4.40%
8.075
HRU4B
Medium-high density. Sand & Gravel
973
15.31%
5.95
HRU5B
Commercial-industrial, Sand & Gravel
2,537
65.72%
3.08
HRU6B
Agriculture, Sand & Gravel
634
0.00%
8.01
HRU7B
Forest, Till & Fine-Grained Deposits
12,553
0.00%
0.938
HRUSB
Open/non-residential, Till & Fine-Grained Deposits
1,083
4.34%
0.832
HRU9B
Medium-low density. Till & Fine-Grained Deposits
2,821
4.40%
0.806
HRU10B
Medium-high density, Till & Fine-Grained Deposits
448
14.93%
0.605
HRU11B
Commercial-industrial, Till & Fine-Grained Deposits
1,104
65.79%
0.336
HRU12B
Agriculture, Till & Fine-Grained Deposits
241
0.00%
0.768
HRU13B
Cranberry Bog
98
0.00%
0.2
HRU14B
Forested Wetland
6,474
0.00%
0.2
HRU15B
Nonforested Wetland
2,132
0.00%
0.2
HRU16B
Water
1,330
0.00%
0
3. Time period
Hydrology data for the selected watershed is available for the following time period: 11/1/1960 to 12/31/20091 View Precipitation Data
Five years of data is the maximum recommended model time period length. You can view the daily precipitation time series to help you determine the period of interest.
3A. If you used EPA's EDM to retrieve your data, the precipitation data is available on the "Precipitation" sheet. You may use "View Precipitation Data" at any time to refer to the data.
3B. If you are using files that have already been downloaded, the precipitation data can be imported by clicking "Load Precipitation Data".
Enter the time period of interest for your modeling study:
Start
1/1/2002
End
12/31/2006
i 1
i/yvw)
i/yyyv)
In Hydro page Step 4, use the drop-down box to indicate whether you will be running a daily or monthly
model. If you intend to include flood damage costs in the modeling, you must run a daily model.
4. Model time step a
To use the Stormwater Module, you must setup a daily model. Would you like to setup a daily or monthly model? | Daily C
Finally, press Retrieve Time Series Data & Populate Time Series in Hydro page Step 5A to retrieve
hydrology and loadings databases from the EDM data library and pre-process and populate the time series
data. This action will download and unzip the appropriate files from the EDM data library using the
16
-------
3. Model Setup and Runs
default unzipping program on your computer. If this process fails, check to make sure the zip file that was
downloaded has files stored in it. If there are files in the zip file (i.e., the zip file size is greater than 0),
then unzip the files to your desired folder, and continue with Hydro page Step 5B to pre-process and
populate the time series data.
If you did not use the EDM data library or your file did not unzip correctly, select the file paths for the
WMOST hydrology and loadings databases in Hydro page Step 5B, and press Process and Populate
Time Series Data. This action pre-processes and populates the runoff and recharge hydrology and
loadings time series data for your watershed of interest.
5A. Use "Retrieve Time Series Data & Populate Time Series" to retrieve the data for your time period, and populate the HRU time series^
Retrieve Time Series Data & Populate Time Series
5B. Select the file path(s) for your time series database(s). Use "Process and Popualte Time Series Data" to process and populate. 1
Select the file that contains the hydrology timeseries for your watershed. Select Hydrology File Path
Process and Populate Time Series Data: Runoff and Recharge
for Hydrology and Loadings
Select Loadings File Path
Select the file that contains for the loadings timeseries for your watershed. 1
Once the processing is complete, you can view the baseline runoff and recharge
time series on Runoff, Recharge, Runoff L, and Recharge L pages. Navigate
back to the Input page using the Return to Input button. The module
automatically enters the number of HRUs you selected with the Baseline Hydrology Module into the blue
box. Check the box next to the Baseline Hydrology Module button to indicate that the data input is
complete (the button color will change from blue to grey once the box is checked). This will help you
track all completed input pages. Continue with data entry and model setup under Input page Step IB.
Return to Input
1. Baseline: Data for unmanaged land conditions.
A. Time series data:
Use Baseline Hydrology module for assisted data acquisition and entry
manually enter your own data.
1. Enter the number of HRUs in your study area: | 16 ^
2. Press "Setup Baseline Tables" button to prepare baseline land
runoff, and recharge input tables
3. Navigate to each input table and enter data:
~ Runoff I ~ | Recharge | ~ | Runoff Loadings j ~ | Recharge Loadings |
Name of Constituent 1:
I. Land use data: Enter HRU areas available for land conservation and associated costs
_Land Ust
Setup Baseline Tables
Baseline Hydrology Module
Input Page Step 1A Manual - Baseline Hydrology
Follow the steps below to enter your own baseline hydrology data manually.
Enter the number of HRU types that you intend to model and the name of your constituent of interest32,
and press the Setup Baseline Tables button. This will automatically prepare appropriately sized input
tables for land use, runoff and recharge data. The process creates blank input tables; therefore, do not
press this button again unless you have your input data saved elsewhere and want to change the number
of HRUs.
32 Any constituent that you have loadings and managed loadings time series for can be entered here. However, when using the
Stormwater module, users should note that default stormwater BMP parameters are only available for TN, TP, TSS, and Zn.
17
-------
WMOST v3 User Guide
1. Baseline: Data for unmanaged land conditions.
A. Time series data:
Use Baseline Hydrology module for assisted data acquisition and entry
OR
manually enter vour own data.
D | Baseline Hydrology Module
2. Press "Setup Baseline Tables" button to prepare baseline land uife, Setup Baseline Tables
runoff, and recharge input tables
3. Navigate to each input table and enter data:
Name of Constituent 1:| TN
~ Runoff | ~ Recharge j ~ Runoff Loadings | ~ Recharge Loadings j
B. Land use data: Enter HRU areas available for land conservation and associated costs
~ | Land Use j
Next, select the Runoff button to navigate to the input table and enter
time series data of runoff rate for each HRU for the modeling time
period. The runoff rate must be input per unit time (e.g., inches per
day). Values can be cut and pasted from another file or imported using Data - (Get External Data) From
Text options in Excel to add contents of a delimited file with no headers. Dates, in the format of
mm/dd/yyyy, are only required for data on the Runoff page. All other pages automatically populate the
dates from the Runoff page.This table requires a time series of runoff rates for baseline HRUs at the daily
or monthly time step. For a monthly time step, the day of the month does not matter. The dates entered in
this table will populate the dates in all other input tables that require a time series. Time series data must
be consecutive and complete, that is, there must not be any missing dates or data. Refer to Defining
Hydrologic Response Units in Section 2.1, for more information regarding data sources for runoff and
recharge rates.
Runoff
Recharge
Quantity in inches/time step
Date
Baseline HRU Set
(mm/dd/yyyy)
HRU1 HRU 2 HRU3
HRU4
HRU5
HRU6
HRU7
HRU8
1/1/2002
1/2/2002
1/3/2002
1/4/2002
1/5/2002
1/6/2002
1/7/2002
1/8/2002
1/9/2002
1/10/2002
1/11/2002
0.019666
0.016656
0.014408
0.013204
0.010676
0.008428
0.135054
0.108846
0.064979
0.042383
0.06827
0.018828
0.015946
0.013794
0.012642
0.010221
0.008069
0.129298
0.104207
0.062209
0.040576
0.06536
0.018801
0.015923
0.013774
0.012623
0.010206
0.008057
0.129112
0.104057
0.062119
0.040518
0.065266
0.016655
0.014106
0.012202
0.011183
0.009041
0.007138
0.114375
0.09218
0.055029
0.035893
0.057816
0.006742
0.00571
0.004939
0.004526
0.00366
0.002889
0.046296
0.037312
0.022275
0.014529
0.023403
0.019666
0.016656
0.014408
0.013204
0.010676
0.008428
0.135054
0.108846
0.064979
0.042383
0.06827
0.014168 0.013553
0.011559 0.011057
0.009873 0.009445
0.009071 0.008677
0.006703 0.006412
0.004656 0.004454
0.190762 0.182481
0.109809 0.105043
0.056952 0.054479
0.033914 0.03;
0
Runoff
1
Recharge
Once you have entered these data, select Return to Input and check the box indicating that this section is
complete. Select Recharge to navigate to the input table for recharge time series. Similar to the runoff
input table, the recharge input table also requires a time series of recharge rates for baseline HRUS at the
daily or monthly time step. Similarly, it should be consecutive and complete.
Once you have entered these data, select Return to Input and check the box indicating that this section is
complete. Select Runoff Loadings to navigate to the input table for runoff loadings time series.
~
CT Runoff Loadings T3
~
Recharge Loadings |
18
-------
3. Model Setup and Runs
| Loadings in lbs/time step |
Date
Baseline HRU Set-CI
(mm/dd/yyyy)
HRU1C1
HRU2C1
HRU3C1
HRU4C1
HRU5C1
HRU6C1
HRU7C1
HRU8C1
1/1/2002
0
0
0
0
0
0
0
0
1/2/2002
0
0
0
0
0
0
0
0
1/3/2002
0
0
0
0
0
0
0
0
1/4/2002
0
0
0
0
0
0
0
0
1/5/2002
0
0
0
0
0
0
0
0
1/6/2002
0
0
0
0
0
0
0
0
1/7/2002
0
0.010022
0.013185
0.04588
0.211938
0
0
0.010206
1/8/2002
0
0.000115
0.000149
0.000517
0.002378
0
0
0.000117
1/9/2002
0
0
0
0
0
0
0
0
1/10/2002
0
0
0
0
0
0
0
0
1/11/2002
0
0.005146
0.006762
0.02353
0.108655
0
0
0.0052411
RunoffLoadings ~
Once you have entered these data, select Return to Input
and check the box indicating that this section is
complete. Select Recharge Loadings to navigate to the input table for recharge loadings time series.
0
0
RunoffLoadings || 0 [ Recharge Loadings |
Once you have entered these data, select Return to Input
and check the box indicating that this section is
complete. This completes Input page Step 1A manual entry. Continue to Input page Step IB.
Input Page Step IB - Land Use and Its Management
Select the Land Use button on the Input page to navigate to the Land Use page. On this page, you must
enter HRU areas for baseline conditions and may enter information for land conservation as a
management option. Within the Baseline HRU Characteristics table, the baseline areas for HRUs can
represent existing conditions or future conditions that you would like to model. For example, if you
intend to run the model to prioritize management options to achieve by 2050, you would enter the
projected area of each HRU in 2050. If you manually entered data for Input page Step 1A, then you must
enter information on the percent effective impervious area and infiltration rate for each HRU if you plan
to use the Stormwater Hydrology Module. If you used the EDM Data Inventory, the baseline HRU areas
are automatically
populated from the
characteristics
database. Otherwise,
you will need to use
GIS to calculate the
baseline area of each
land-use/soil type
combination for your
subwatershed of
interest.
Baseline HRU Characteristics
Percent
Infiltration
Baseline Area
Effective
Rate
HRU ID
HRU Name1
[acre]
Impervious1
[in/hr]1
HRU1B
Forest, Sand & Gravel & Gravel
13,647
0.00%
9.5
HRU2B
Open/non-residential, Sand & Gravel & Gravel
2,296
4.26%
8.455
HRU3B
Medium-low density. Sand & Gravel
5,949
4.40%
8.075
HRU4B
Medium-high density. Sand & Gravel
973
15.31%
5.95
HRU5B
Commercial-industrial, Sand & Gravel
2,537
65.72%
3.08
HRU6B
Agriculture, Sand & Gravel
634
0.00%
8.01
HRU7B
Forest, Till & Fine-Grained Deposits
12,553
0.00%
0.938
HRU8B
Open/non-residential, Till & Fine-Grained Deposits
1,083
4.34%
0.832
HRU9B
Medium-low density. Till & Fine-Grained Deposits
2,821
4.40%
0.806
HRU10B
Medium-high density, Till & Fine-Grained Deposits
448
14.93%
0.605
HRU11B
Commercial-industrial, Till & Fine-Grained Deposits
1,104
65.79%
0.336
HRU12B
Agriculture, Till & Fine-Grained Deposits
241
0.00%
0.768
HRU13B
Cranberry Bog
98
0.00%
0.2
HRU14B
Forested Wetland
6,474
0.00%
0.2
HRU15B
Nonforested Wetland
2,132
0.00%
0.2
HRU16B
Water
1,330
0.00%
0
19
-------
WMOST v3 User Guide
For the Data for Land Conservation Option table (see
screenshot to the left), the following examples are
provided to help guide inputting appropriate values:
• "Minimum" areas for each HRU - For urban
HRUs, this may be the existing area of urban HRUs
since these areas are not expected to be reforested or
otherwise be "undeveloped". For forest lands, it may
be the area of conserved/protected forest lands which
must exist in the future due to their protected status.
• "Maximum" areas for each HRU - For urban
HRUs, this may be the projected, built-out area or
maximum allowable area under zoning regulations. For
forest lands, it may be the existing area of forest land
given that other HRU types will not be used to regrow
forest for urban recreation or start a forestry business.
• Cost to conserve HRUs - It may be environmentally beneficial to purchase and conserve forest or
wetlands. For these HRUs, enter the initial cost of purchasing the land (i.e., capital costs) and any
annual operations and maintenance (O&M) costs that may continue to be associated with the
purchase.
A primary source of the capital cost to conserve data is from records of land purchased by the
municipality for conservation. If records of that kind are not available, you can use real estate appraisal
websites to estimate the cost of open land for a land use type. We typically estimate O&M costs as 5% of
the capital cost. If land conservation is not possible or desirable for an HRU, then enter ""-9" for initial and
O&M costs33 (as shown in the screenshot).
Once both tables are complete, navigate back to the Input page and check the box next to the Land Use
button and continue to Input page Step 2.
1. Baseline: Data for unmanaged land conditions.
A. Time series data:
Use Baseline Hydrology module for assisted data acquisition and entry
HH Baseline Hydrology Module
Name of Constituent 1: | TN
B. Land use data: Enter HRU areas available for land conservation and associated costs 0 Land Use |
3.3 Managed Hydrology and HRU Areas/Stormwater Management
To incorporate stormwater BMPs to manage the land use area within your watershed, you must complete
this step. You have the option to either get assistance with deriving and populating stormwater
33 WMOST allows users to turn any management option "on" or "off when setting up the model. Hie data input "-9" typically
acts as the management option exclusion flag, but only use this flag as directed by this user guide. This data input is different
than a capital cost of zero, which indicates that the management option may be applied and at zero cost to the user.
Data for Land Conservation Option
Initial Cost to
Minimum Area
Maximum
Conserve
O&M C05t
[acre]
Area [acre]
[$/acre]
[$/acre/yr]
13647
13647
-9
-9
2296
2296
-9
-9
5949
5949
-9
-9
973
973
-9
-9
2537
2537
-9
-9
634
634
-9
-9
12553
12553
-9
-9
1083
1083
-9
-9
2821
2821
-9
-9
448
448
-9
-9
1104
1104
-9
-9
241
241
-9
-9
98
98
-9
-9
6474
6474
-9
-9
2132
2132
-9
-9
1,330
1,330
-9
-9
manually enter your own data.
1. Enter the number of HRUs in your study area: | 16
2. Press "Setup Baseline Tables" button to prepare baseline land use, Setup Baseline Tables
runoff, and recharge input tables V '
3. Navigate to each input table and enter data:
0 Runoff J 0 Recharge | 0 Runoff Loadings J 0 Recharge Loadings |
20
-------
3. Model Setup and Runs
management related inputs or manually entering stormwater hydrology and loadings data. If you need
assistance, continue with Input Page Step 2A Assisted- Stormwater Hydrology Module section. If you
would like to manually enter the data, skip to Input Page Step 2A Manual - Stormwater Hydrology for
instructions.
Input Page Step 2A Assisted - Stormwater Hydrology Module
Navigate to the Stormwater Hydrology Module by clicking on the Stormwater Hydrology Module button.
2. Stormwater Management: Data for stormwater managed land conditions. This section is only required if you wish to consider stormwater management.
A. Time series data:
Use Stormwater Hydrology module for assisted data acquisition
and entry
OR
manually enter your own data.
1. Enter the number of HRU sets (baseline plus managtdj:|
~ water Hydrology j
2. Press "Setup Stormwater Tables" button to prepare managed land use, setup Stormwater Tables
runoff, and recharge input tables: \ *
3. Navigate to each input table and enter data:
~ Runoff j ~ Recharge J ~ Runoff Loadings j ~ j Recharge Loadings j
B. Land use: Enter data on HRU areas available for stormwater management and stormwater management costs ~ | Land Use f
C. Water Quality BMPs: If you wish to consider water quality management options to change loadmgs on HRU area or to a waterbody, proceed to the WQ BMPs module. ~ BMPs J
Five steps comprise the Stormwater Hydrology Module. In Stormwater page Step 1, use the drop-down
menu to indicate whether you used the Baseline Hydrology Module or manually entered your own
baseline data. If you used the Baseline Hydrology Module, select "Baseline Hydrology Module" and
press Import Hourly Time Series.
To use this Stormwater Module, you MUST enter baseline hydrology and loadings data first. You may do so manually or via the Hydrology
1. Did you use the Baseline Hydrology arid Loadings Module or manually enter data? [ Baseline Hydrology Module
Mfdule.
*5
If you used the Baseline Hydrology Module, the Import Hourly Time Series button will populate all
additional stormwater data
based on your model setup in
Input page Step 1.
If you manually entered your own data, select "Entered Own Data" and press Manually Enter Hourly
Time Series where you will be asked for additional information.
Additional Stormwater Data: Three types of additional data are required if you entered your own baseline
hydrology:
• Latitude of your study area
• Hourly or daily temperature time series for your study area
• Hourly runoff and runoff loadings time series for your HRUs. More detailed guidance is below.
If you used the Baseline Hydrology and Loadings Module, use the Import Hourly Time Series button to
automatically populate hourly data.
^^^Jnipor^ouH^nmi^enes^^^g^l
To use this Stormwater Module, you MUST enter baseline hydrology and loadings data first. You may do so manually or via the^vdrology Module.
1. Did you use the Baseline Hydrology and Loadings Module or manually enter data? | Entered Own Data
the^Hvdn
V3
If you entered data manually, use the Hourly Time Series button to navigate to the stormwater data
sheet and provide hourly data. ^
JVlanuallvEnterHourlvTime.sprips 3
21
-------
WMOST v3 User Guide
First, enter the model time period. This time period must match the time period of the baseline runoff and
recharge time series. Second, enter the latitude of your study area.
1. Enterthe model time period. Time series data must match the time period of the baseline hydrology.
Baseline hydrology start:
1/1/2002
Baseline hydrology end:
12/31/2006
2. Enterthe latitude of your study area in the blue box.
Latitude (decimal degrees} 42
t match tl
-------
3. Model Setup and Runs
In Stormwater page Step 3, select the stormwater BMP types and indicate the runoff design depths that
you would like to model and the associated 1st order decay rate. You can model up to nine combinations
of BMP type and runoff design
depth. This limitation is imposed to
ensure manageable processing time
and completion. The first 13 of the
BMPs in the drop-down menu are
urban BMPs, which apply to HRUs
with non-zero EIA. The final four
BMPs are agricultural BMPs (with the designation ""Ag"). which apply to HRUs with zero EIA and CN
less than 100. Each selected BMP is simulated on a distinct one-acre drainage area, such that each BMP
receives the runoff from one acre of the HRU.
You can import default decay rates for TN, TP, TSS, and zinc using the Import Default
Decay Rates button. The default decay rates are consistent with values provided in
EPA's OptiTool (US EPA 2017) which were calibrated based on field measurements at
the University of New Hampshire Stormwater Center facilities. For each combination,
the Stormwater Hydrology Module will calculate the appropriate BMP design parameters, run a
simulation for all appropriate HRUs, calculate the final "managed" runoff and recharge time series, and
populate the appropriate WMOST input table. As indicated in Section 2.2, in order for the Stormwater
Hydrology Module to run, the WMOST .xlsm file must be saved in a folder location with no spaces in the
file path.
If you are using agricultural BMPs, you must enter additional
data inputs to run the Stormwater Hydrology Module. Use
the Show Agricultural BMP Inputs button to display the input
tables and fields for this data, which include Stormwater page Steps 4A - 4E. If you are not using any
agricultural BMPs, hide these inputs using the Hide Agricultural BMP Inputs button and continue on to
Stormwater page Step 5.
First, using instructions from Stormwater page Step 4A,
enter the total area that will be managed by the selected
BMP in Stormwater page Step 3. Agricultural BMPs are
typically designed to manage runoff from larger land areas
than urban BMPs. The default managed area is 15 acres.
Then, Stormwater page Steps 4B - 4D provide instructions
for defining special inputs for agricultural BMPs. For all agricultural BMP types, you must provide a CN
for each undeveloped HRU. You may exclude any undeveloped land use from modeling by entering a -9
or a 100 in the CN input field. Furthermore, you may use the Import CN Defaults button to import
default CN values based on the land use name and soil group of your HRUs. The Show/Hide HRU
Defaults button displays the source data for the default values and can be referenced if the Import CN
Defaults button did not return any matches or if it returned multiple matches.
Design Depth For
TN 1st Order
BMP Type
BMP [in]
Decay Rate [l/hr]
Eiofiltration w/UD
0.03
Gravel Wetland
0.13
Infiltration Trench
0.42
Ag: Subsurface Gravel Wetland
0.54
Ag: Sediment Basin
0.1
Ag: Vegetative Filter Strip
0.46
Import Default
Decay Rates
'show Agricultural
BMP Inputs
Hide Agricultural
BMP Inputs
For Sediment Basins only:
Area Managed by
Agriculture BMP [acres]
TN Settling Velocity
[in/s]
NA
NA
NA
NA
NA
NA
15
0
15
0.0035
15
0
23
-------
WMOST v3 User Guide
Then, if you are modeling a sediment basin, you must enter the settling velocity of the
constituent of interest in Stormwater page Step 3 . You may use the Import Default
Settling Velocity of Silt button to import values for fine, medium, or coarse silt.
Finally, enter the additional BMP parameters needed for modeling vegetative filter
strips if you have selected that BMP in Stormwater page Step 3. This must be done
for each undeveloped HRU being modeled. The additional parameters include flow
length, surface depression storage, Manning's N coefficient, and overland slope. You
may use the Import Defaults for Vegetative Filter Strip button to import default
values for modeled HRUs based on their land use.
import Default
SettlingVelocity ,
Show/Hide HR
Defaults
Import CN
Defaults
HRU Name
Percent Effective
Impervious
HydrologicSoil
Group (A,B,C,D)
CN Number
Forest, Sand & Gravel & Gravel
0.00%
A
36
Open/non-residential, Sand & Gravel & Gravel
4.26%
B
NA
Medium-low density. Sand & Gravel
4.40%
B
NA
Medium-high density, Sand & Gravel
15.31%
C
NA
Commercial-industrial, Sand & Gravel
65.72%
D
NA
Agriculture, Sand & Gravel
0.00%
A
68
Forest, Till & Fine-Grained Deposits
0.00%
B
60
Open/non-residential, Till & Fine-Grained Deposits
4.34%
B
NA
Medium-low density, Till & Fine-Grained Deposits
4.40%
C
NA
Medium-high density, Till & Fine-Grained Deposits
14.93%
D
NA
Commercial-industrial, Till & Fine-Grained Deposits
65.79%
D
NA
Agriculture, Till & Fine-Grained Deposits
0.00%
B
79
Forested Wetland
0.00%
A
100
^^mport Defaults fo^^ k
%^egetative Filter Strij^'
Nonforested Wetland
0.00%
A
100
Water
0.00%
A
NA
HRU Name
Percent Effective
Impervious
Flow Length [ft]
Surface Depression
Storage [in]
Manning's Coefficient
[unitless]
Overland Slope [ft/ft]
Forest, Sand & Gravel & Gravel
0.00%
75
0.25
0.3
0.05
Open/non-residential, Sand & Gravel & Gravel
4.26%
NA
NA
NA
NA
Medium-low density, Sand & Gravel
4.40%
NA
NA
NA
NA
Medium-high density. Sand & Gravel
15.31%
NA
NA
NA
NA
Commercial-industrial, Sand & Gravel
65.72%
NA
NA
NA
NA
Agriculture, Sand & Gravel
0.00%
75
0.25
0.3
0.05
Forest, Till & Fine-Grained Deposits
0.00%
75
0.25
0.3
0.05
Open/non-residential, Till & Fine-Grained Deposits
4.34%
NA
NA
NA
NA
Medium-low density. Till & Fine-Grained Deposits
4.40%
NA
NA
NA
NA
Medium-high density, Till & Fine-Grained Deposits
14.93%
NA
NA
NA
NA
Commercial-industrial, Till & Fine-Grained Deposits
65.79%
NA
NA
NA
NA
Agriculture, Till & Fine-Grained Deposits
0.00%
75
0.25
0.3
0.05
Cranberry Bog
0.00%
75
0.25
0.15
0.05
Forested Wetland
0.00%
75
0.25
0.15
0.05
Nonforested Wetland
0.00%
75
0.25
0.15
0.05
Water
0.00%
NA
NA
NA
NA
After entering the BMP management combinations, press Generate input files for stormwater model
under Stormwater page Step 5. This button creates three types of
input files for the stormwater simulation:
• Main input file (Input.inp)
• Climate time series file (Climate.swm)
• Multiple HRIJ runoff time series files based on the number of developed HRUs (HRU#.txt).
CGenerate inputfilesfor
stormwater mode I
24
-------
3. Model Setup and Runs
The input file generation step may take a few minutes to complete. When the files are complete, a
message box stating "Input files are complete. Stormwater model
is ready to be run" will appear. Press "Ok" to continue.
The generated input files are saved to a folder titled "Input" in
same location as the WMOST .xlsm file. Next, press Run
stormwater model and populate WMOST input fields. When the
SUSTAIN simulation is complete, a message box stating "BMP simulation is complete". Press "Ok" to
move on to the stormwater results processing. After the results processing is complete, a message box
stating "Runoff and recharge time series for managed hydrology have been populated. Return to Input
data page to continue" will appear. Press "Ok" to continue.
The stormwater model simulation determines how much of the runoff flow and loadings are infiltrated or
detained by a BMP. Simulation outputs are automatically processed and the appropriate input tables for
managed HRU sets are populated on the Runoff, Recharge, Runoff_L, and Recharge_L pages.
Once the module completes processing, select Return to Input and check the box next to Stormwater
Hydrology Module to indicate that the module and data entry is complete. Enter the total number of HRU
sets including the one created by the Baseline Hydrology Module (always one) and those created by the
Stormwater Hydrology Module (depends on the number of HRUs and BMP types entered onto the
Stormwater page). Proceed to Input page Step 2B using instructions from Input Page Step 2B - Land
Use and Its Management.
3un stormwater model and
Ssj3opulate WMOST inputfiejd
2. Stormwater Management: Data for stormwater managed land conditions. This section is only required if you wish to consider stormwater management.
A. Time series data:
Use Stormwater Hydrology module for assisted data acquisition
and entry
OR
manually enter your own data.
1. Fntprthp nnmhpr nf HRIJ c;pt<; (hacplinp pine manaftpH):| 7
0 Stormwater Hydrology Module
2. Press "Setup Stormwater Tables" button to prepare managed larl^ use. Setup Stormwater Tables
runoff, and recharge input tables: v '
3. Navigate to each input table and enter data:
~ Runoff | ~ Recharge | ~ Runoff Loadings | ~ Recharge Loadings |
Input Page Step 2A Manual - Stormwater Hydrology
For manually entering your own stormwater hydrology data, follow the instructions below.
Decide on the number of BMPs you would like to evaluate, that is, the number of BMP type and size
combinations. For example, assessing a bioretention basin and a detention pond each at the 0.6 inch
and 1.0 inch design depth would require a total of four BMP setups. The runoff and recharge time series
associated with one BMP setup for all modeled HRUs constitutes a managed HRU set.
Enter the number of HRU sets that you intend to model including the baseline set (i.e., add one to the
number of stormwater BMP setups you intend to model).
25
-------
WMOST v3 User Guide
2. Stormwater Management: Data for stormwater managed land conditions. This section is only required if you wish to consider stormwater management.
A. Time series data:
Use Stormwater Hydrology module for assisted data acquisition
and entry
~ Stormwater Hydrology Module
Setup Stormwater Tables
manually enter your own data.
1. Enter the number of HRU sets (baseline plus manaEed):llL 7
2. Press "Setup Stormwater Tables" button to prepare managed land use,
runoff, and recharge input tables:
3. Navigate to each input table and enter data:
~ Runoff | ~ Recharge | ~ Runoff Loadings | ~ Recharge Loadings |
B. Land use: Enter data on HRU areas available for stormwater management and stormwater management costs
Land Use
I
Press Setup Stormwater Hydrology to automatically prepare appropriately sized input tables for managed
land use, runoff and recharge data. The process creates blank input tables; therefore, do not press this
button again unless you have your input data saved elsewhere and want to change the number of HRU
sets.
Managed HRU Set (HRUM1)
HRU1M1
HRU2M1
HRU3M1
HRU4M1
HRU5M1
HRU6M1
HRU7M1
HRU8M1
HRU9M1
HRU10M1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0.007916
0.008172
0.028437
0.122041
0
0
0.008062
0.008176
0.027728
0
0.000394
0.000407
0.001416
0.006078
0
0
0.000401
0.000407
0.001381
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0.012991
0.013411
0.046667
0.200303
0
0
0.013231
0.013418
0.045503
0
0
0
0
0
0
0
0
0
0
0
0.033439
0.03452
0.120121
0.515575
0
0
0.034055
0.034538
0.117125
0
0
0
0
0
0
0
0
0
0
0
0.009511
0.009S1S
0.034164
0.146638
0
0
0.009686
0.009823
0.033312
not matter. Time series data must be consecutive, that
Defining Hydrologic Response Units in Section 2.1, for
runoff and recharge rates.
Next, select Runoff to
navigate to the input
table and enter time
series data of runoff
rate for each HRU.
This table requires a
time series of runoff
rates for each
managed land use set
at the daily or monthly
time step. For a
monthly time step, the
day of the month does
is, there must not be any missing dates. Refer to
more information regarding data sources for
The time series are input vertically and HRUs and HRU sets horizontally. You can exclude an HRU from
a "managed set" by entering ""-9" for the capital and O&M costs associated with managing the HRU; this
action will make the values specified for those HRUs inconsequential. To the right of the Baseline HRU
set, which was completed in Input page Step 1, you will see the continuation of HRU columns for the
managed sets.
0
~
Recharge |
Once you have entered runoff hydrology data, select Return to Input
and check the box indicating that this section is complete. Next select
Recharge to enter time series data of recharge rates for each HRU.
Similar to the runoff input table, the recharge input table also requires a time series of recharge rates for
baseline and each managed land use set at the same daily or monthly time step. Similarly, it should be
consecutive and complete and input as depth per time step (e.g., inches per day). Select Return to Input
and check the box next to the Recharge button indicating that this section is complete.
26
-------
3. Model Setup and Runs
~
Runoff Loadings ~ Recharge Loadings
Next, select Runoff Loadings to navigate to the input table for
runoff loadings time series.
Managed HRU Set (HRUM1C1)
HRU1M1C HRU2M1C HRU3M1C HRU4M1C HRU5M1C HRU6M1C HRU7M1C HRU8M1C
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Once you have entered these data,
select Return to Input and check the
box indicating that this section is
complete. Finally, select Recharge
Loadings to navigate to the input
table for recharge loadings time
series. Input the recharge loadings
data on this page. Once you have
entered these data, select Return to
Input and check the box indicating
0 Runoff Loadings
that this section is complete.
0
Runoff Loadings | 0
Recharge Loadings |
This completes Input page Step 2A manual entry.
Continue to Input page Step 2B.
Input Page Step 2B - Land Use and Its Management
Select the Land Use button to navigate to the Land Use page. Beneath the Baseline HRU Characteristics
input table, you will see table(s) for managed HRU sets. There is one table for each BMP or managed
HRU set. Depending on whether you used the automated or manual version of the stormwater hydrology
input (Input page Step 2A), some fields will be pre-filled.
Enter or verify the name of the BMP in the blue box in the upper right hand corner of each Managed Land
Uses and Their Limits table. The following input data are requested for each HRU:
• Minimum area on which the management practice may be implemented - For urban HRUs,
regulations may require that a specific stormwater management practice is implemented.
• Maximum area on which the management practice may be implemented - For urban HRUs,
some of the HRU may be already managed by a different stormwater practice and is, therefore,
unavailable for that treatment.
• Initial costs associated with the management practice - For example, design and construction
of a bioretention basin to retain one inch of runoff.
• O&M costs associated with the management practice - For example, annual clean out and other
upkeep of the bioretention basin to maintain performance.
The Stormwater Hydrology Module will automatically enter initial costs and O&M costs based on the
cost of stormwater BMPs in terms of dollars per treated cubic feet of stormwater. The unit cost values are
derived from previous applications of SUSTAIN34 and Opti-Tool (EPA 2017). These default costs are for
stormwater BMP retrofits in 2016 dollars. For comparable cost values for BMPs installed in newly
34 U.S. Environmental Protection Agency (EPA) and Massachusetts Department of Environmental Protection (MassDEP). 2009.
Optimal Stormwater Management Plan Alternatives: A Demonstration Project in Three Upper Charles River Communities.
27
-------
WMOST v3 User Guide
developing areas, see the Theoretical Documentation. If a management practice is not applicable or
desirable for an HRU, "-9" is entered for initial and O&M costs.
First Set of Managed Land Uses and Their Limits
1" Biofiltration w/UD
HRU ID
HRU Name
Minimum
Area [acre]
Maximum
Area [acre]
Initial Cost
to Conserve
[$/acre]
O&M Cost
[$/acre/yr]
HRU1M1
Forest, Sand & Gravel & Gravel
0
0
-9
-9
HRU2M1
Open/non-residential, Sand & Gravel & Gravel
0
1710
4570.69
228.53
HRU3M1
Medium-low density, Sand & Gravel
0
3502
4718.34
235.92
HRU4M1
Medium-high density. Sand & Gravel
0
415
16418.77
820.94
HRU5M1
Commercial-industrial, Sand & Gravel
0
1075
70471.9
3523.60
HRU6M1
Agriculture, Sand & Gravel
0
0
-9
-9
HRU7M1
Forest, Till & Fine-Grained Deposits
0
0
-9
-9
HRUSM1
Open/non-residential, Till & Fine-Grained Deposits
0
905
4654.86
232.74
HRU9M1
Medium-low density, Till & Fine-Grained Deposits
0
497
4720.81
236.04
HRU10M1
Medium-high density, Till & Fine-Grained Deposits
0
9
16009.25
800.46
HRU11M1
Commercial-industrial, Till & Fine-Grained Deposits
0
398
70548.68
3527.43
HRU12M1
Agriculture, Till & Fine-Grained Deposits
0
0
-9
-9
HRU13M1
Cranberry Bog
0
0
-9
-9
HRU14M1
Forested Wetland
0
0
-9
-9
HRU15M1
Nonforested Wetland
0
0
-9
-9
HRU16M1
Water
0
0
-9
-9
In the above screenshot, all urban HRUs are receiving biofiltration management. There are no minimum
acres of HRU area that must be managed but the maximum values are entered based on projected build-
out (therefore, same as maximum areas in the baseline table). In addition, as described in Section 2.1 in
the Theoretical Documentation, the maximum area of an HRU that can be managed with bioretention is
limited to the area of that HRU that exists considering land conservation decisions (i.e., land area is
conserved and no more can be treated than exists as decided is optimal by the model). All specifications
are "per acre of HRU"; therefore, the initial cost of $4,571 and O&M cost of $229 for open/non-
residential on sand and gravel surficial geology is the cost to treat one acre of that HRU. The actual
footprint of the bioretention basin will only be a small part of that acre of land. The costs for agricultural
BMPs are also specified as per acre of managed land, but they can be used to manage areas larger than
one acre as specified by the user. WMOST calculates the final costs for implementation taking into
account the quantity of BMPs implemented. Neither SUSTAIN nor WMOST include the associated cost
of land the BMP is constructed upon but users can adjust values accordingly based on local land costs.
Repeat the same instructions for additional BMPs/managed sets. Up to ten stormwater management
options, including traditional, green infrastructure, LID, agricultural runoff control practices or other land
management practices that modify runoff and recharge may be specified. A managed set may include
multiple simultaneous practices that achieve some standard such as retaining a one inch storm event using
rooftop disconnection, bioretention basins and swales.
Once you have entered all the land use information related to managed sets, navigate to the input screen
by pressing Return to Input. Check the box next to Land Use to indicate that you have completed data
entry for this category of input.
28
-------
3. Model Setup and Runs
2. Stormwater Management: Data for stormwater managed land conditions. This section is only required if you wish to consider stormwater management.
A. Time series data:
Use Stormwater Hydrology module for assisted data acquisition
and entry
OR
manually enter your own data.
1. Enter the number of HRU sets (baseline plus managed):) 7
0 | Stormwater Hydrology Module
2. Press "Setup Stormwater Tables" button to prepare managed land use. Setup Stormwater Tables \
runoff, and recharge input tables: V '
3. Navigate to each input table and enter data:
~ Runoff _| ~ Recharge | ~ Runoff Loadings | ~ Recharge Loadings |
B. Land use: Enter data on HRU areas available for stormwater management and stormwater management costs 0 1 Land Use |
Input Page Step 2C - Water Quality BMPs
The water quality BMPs are a suite of optional BMPs that, if implemented, reduce loadings to the stream
or reservoir, which may help the system meet water quality targets in the stream or reservoir. Select the
WQ BMPs button to navigate to the WQ BMPs page.
C. Water Quality BMPs: If you wish to consider water quality management options to change loadings on HRU area or to a waterbody, proceed to the WQBMPs module. D
C WQ BMPs
The first type of water quality BMP models streambank restoration/stabilization and outfall enhancement/
stabilization. Unlike other types of BMPs in WMOST, these BMPs are not associated with specific
HRUs. This water quality BMP requires four data inputs under WQ BMPs page Step 1A or Step IB. The
following input data are requested for each stabilization management option:
• Constituent removal rate - For each unit treated (stream foot or outfall), the mass of the constituent
that is prevented from entering the waterbody at each time step in pounds.
• Capital cost per treatment unit - The cost related to treatment of one stream foot or outfall in dollars
per unit treated.
• Maximum number of units that can be treated- The maximum number of units that are available for
stabilization.
• Waterbody type where stabilization occurs - The waterbody type (stream or reservoir) where the
stabilization project is located, and thus, receives the target adjustment.
The screenshots below display example data inputs for streambank stabilization where the units are feet
of stream length. Outfall stabilization requires corresponding data inputs where the units are outfalls.
1A. Streambank Restoration or Stabilization
Enter the constituent removal rate resulting from a streambank project. Enter the cost per stream length treated and the maximum stream length that can be treated.
|Removal Rate of TN | 0.13|lb/ft/time step
Specify whether the stabilization project applies to the in-stream or reservoir loading target. | In-Stream Loadings Target |
Cost per linear stream length
$152.40
$/foot
Maximum linear stream length
65616.8
feet
The second type of water quality BMP models different types of land management BMPs, including
street sweeping, tree canopy, and urban nutrient management plans. These BMPs are grouped together as
"Runoff Loadings Direct Reduction BMPs" because they all result in reduced runoff loadings and have a
negligible impact on runoff flows. Therefore, WMOST models these BMPs by reducing runoff loadings
on the HRUs receiving the BMP application with a percent reduction.
To model any direction reduction water quality BMPs, continue to WQ BMPs page Step 2.
29
-------
WMOST v3 User Guide
2. Runoff Loadings Direct Reduction BMPs: Apply direct runoff loadings reduction to an HRU area by implementing a direct reduction BMP.
2A. Runoff Loadings Direct Reduction Management Sets
You can model the following three management options:
Select the name of the direct reduction BMP(s)
that you would like to model.
Set No.
Direct Reduction Management Name
DRM1
Street Sweeping
DRM2
Tree Canopy over Impervious/Turf
DRM3
Urban Nutrient Management
1) Street Sweeping
2) Tree Canopy over Impervious/Turf Area
3) Urban Nutrient Management
<=¦
Select the number of dir<
managed sets:
Setup Direct
Reduction Tables
iter the application area, cost of application, and load adjustment for each constituent in the tables below.
If an HRU does not receive any treatment from the management practice, enter 0 for the load removal rate.
First, as shown in the screenshot above, select the number and types of direct reduction management sets
you would like to model. You may model up to three of these BMPs in one model run. If you select the
same management set type more than once in the set of three in order to evaluate varying levels of
treatment and their associated costs, the model is limited such that it will only choose to apply the most
cost-effective option from
those sets. This condition
ensures that the model cannot
apply the same type of
management on the same HRU
type. Press Setup Direct
Reduction Tables to set up the
tables under WQ BMPs page
Step 2B.
For each HRU, you must enter
four data inputs:
• Application area that
receives the management
practice - This area affects
the capital and O&M costs
incurred.
• Initial cost of application of
the management practice - For example, purchase of street sweeping equipment.
• O&M costs associated with the management practice - For example, labor required to operate the
equipment.
• Percentage of loading removed - the resulting reduction in loadings as a result of the management
practice.
For any HRUs within a management set that do not receive the management practice, you must enter "0"
for all four data inputs (e.g., the water FIRU in the screenshot above). Costs associated with each
management practice type vary by region; consult local utilities or stakeholders regarding the capital and
O&M costs required to implement the management practice of interest.
Once this section of the WQ BMPs page is complete, navigate to the input screen by pressing Return to
Input. Check the box next to WO BMPs to indicate that you have completed data entry for this category
of input.
First Set of Direct Reduction Application Areas and their Costs
Application
Initial Cost of
O&M Cost
TP Load Removal
HRU ID
HRU Name
Area [acre]
Application [$/acre]
[$/acre/yr]
Rate [%]
HRU1DRM1
Forest, Sand & Gravel & Gravel
0.00
0.00
0.00
0.00
Open/non-residential, Sand & Gravel
HRU2DRM1
& Gravel
0.00
0.00
0.00
0.00
HRU3DRM1
Medium-low density, Sand & Gravel
494.21
8.09
2.00
10.00
HRU4DRM1
Medium-high density, Sand & Gravel
247.11
12.14
3.50
15.00
Commercial-industrial, Sand &
HRU5DRM1
Gravel
44.48
12.14
15.00
HRU6DRM1
Agriculture, Sand & Gravel
0.00
0.00
0.00
0.00
HRU7DRM1
Forest, Till & Fine-Grained Deposits
0.00
0.00
0.00
0.00
Open/non-residential, Till & Fine-
HRU8DRM1
Grained Deposits
0.00
0.00
0.00
0.00
Medium-low density. Till & Fine-
HRU9DRM1
Grained Deposits
19.77
8.09
2.00
10.00
Medium-high density, Till & Fine-
HRU10DRM1
Grained Deposits
49.42
12.14
3.50
15.00
Commercial-industrial, Till & Fine-
HRU11DRM1
Grained Deposits
1.73
12.14
3.50
15.00
Agriculture, Till & Fine-Grained
HRU12DRM1
Deposits
O.OO
0.00
0.00
0.00
HRU13DRM1
Cranberry Bog
0.00
0.00
0.00
0.00
HRU14DRM1
Forested Wetland
0.00
0.00
0.00
0.00
HRU15DRM1
Nonforested Wetland
0.00
0.00
0.00
0.00
HRU16DRM1
Water
0.00
0.00
0.00
0.00
30
-------
3. Model Setup and Runs
Input Page Step 2D - Riparian Buffers
Riparian buffers are a water quality related BMP that also reduces loadings to the stream or reservoir by
converting land uses in riparian zones from more developed land uses. Loading reductions can be
associated both with the conversion of the riparian area itself and the riparian area's ability to prevent
loadings from upgradient land areas from entering the stream reach. If you want to include riparian
buffers as a management option, select the Riparian Buffers button to navigate to the Riparian Buffer
page.
Enter the number of land use conversions:
(max 10) 10
Enterthe number of relative loadsgroups:
(max 5)
First, indicate the number of land use conversions in the
stream buffer zone that you would like to model and the
number of relative loads groups. Depending on the location
of the riparian area, the buffer receives varying loads from
upgradient land areas. For
example, some riparian areas
with urban HRUs upgradient may receive relatively high loadings in
comparison with riparian areas with undeveloped HRUs upgradient. Next,
press Setup Riparian Buffer Tables.
After your table has been set up, choose the HRU name that you are converting from and the HRU name
that you are converting to for each land use conversion in the buffer zone. The From HRU ID and To
HRU ID columns will be automatically populated.
Setup Riparian Buffer
rabies
Land Use
Conversion No.
From HRU ID
To HRU ID
From HRU Name
To HRU Name
RBM1LC1
2
1
Open/non-residential, Sand & Gravel & Gravel
Forest, Sand & Gravel & Gravel
RBM1LC2
3
1
Medium-low density. Sand & Gravel
Forest, Sand & Gravel & Gravel
RBM1LC3
4
1
Medium-high density. Sand & Gravel
Forest, Sand & Gravel & Gravel
RBM1LC4
5
1
Commercial-industrial, Sand & Gravel
Forest, Sand & Gravel & Gravel
RBM1LC5
6
1
Agriculture, Sand & Gravel
Forest, Sand & Gravel & Gravel
RBM1LC6
8
7
Open/non-residential, Till & Fine-Grained Deposits
Forest, Till & Fine-Grained Deposits
RBM1LC7
9
7
Medium-low density. Till & Fine-Grained Deposits
Forest, Till & Fine-Grained Deposits
RBM1LC8
10
7
Medium-high density, Till & Fine-Grained Deposits
Forest, Till & Fine-Grained Deposits
RBM1LC9
11
7
Commercial-industrial, Till & Fine-Grained Deposits
Forest, Till & Fine-Grained Deposits
RBM1LC10
12
7
Agriculture, Till & Fine-Grained Deposits
Forest, Till & Fine-Grained Deposits
Then, for each land use conversion, you must enter four additional data inputs:
• Riparian area available for land use conversion - Riparian areas differ in the relative amount of loads
removed depending on land use, soil, and slope.
• Capital cost of riparian area conversion - For example, costs related to planting forests or vegetation
and landscaping.
• O&M costs related to riparian area upkeep and management- For example, landscaping and erosion
protection.
• Load adjustment efficiency, or percent reduction or addition of upgradient loads as a result of the
riparian area conversion.
31
-------
WMOST v3 User Guide
• Buffer conversion implementation mode—users may select "Excluded" to exclude a conversion from
modeling, "Simulation" to ensure that the conversion is implemented, or "Optimization" to
determine whether the conversion is implemented in a least-cost optimized solution. If this cell is left
blank, the conversion will be considered in the optimization scenario.
Riparian Area,
Riparian Area,
Riparian Area,
Riparian Buffer
Relative Loads
Relative Loads
Relative Loads
Initial Cost to
O&M Cost
TN Load Adj
Implementation
Group 1 [acre]
Group 2 [acre]
Group 3 [acre]
Convert [$/acre]
[$/acre/yr]
Efficiency [%]
Mode
0.96
16.75
38.38
2153.43
3599
-60
Excluded
0.96
56.76
58.02
2153.43
3599
-60
Excluded
0.00
21.49
12.97
2153.43
3599
-60
Excluded
0.30
49.72
67.51
2153.43
3599
-60
Optimization
0.00
6.37
22.75
2153.43
1865
-60
Simulation
1.11
16.75
4.59
2153.43
3599
-60
Excluded
3.48
33.05
5.78
2153.43
3599
-60
Excluded
0.52
12.37
0.44
2153.43
3599
-60
Excluded
0.44
27.94
5.85
2153.43
3599
-60
Optimization
0.00
2.S2
3.26
2153.43
1865
-60
Simulation
Each relative loads group signifies riparian areas that receive similar loads from upgradient areas. In
Riparian Buffers page Step IB, enter the acres that are upgradient or upland from the riparian areas for
each relative loads groups.
HRU ID
HRU Name
Upland Area,
Relative Loads
Group 1 [acres]
Upland Area,
Relative Loads
Group 2
[acres]
Upland Area,
Relative Loads
Group 3
[acres]
RBM1HRU1
Forest, Sand & Gravel & Gravel
0.00
0.00
0.00
RBM1HRU2
Open/non-residential, Sand & Gravel & Gravel
249.45
1,006.51
518.90
RBM1HRU3
Medium-low density. Sand & Gravel
1,457.23
3,506.52
857.65
RBM1HRU4
Medium-high density, Sand & Gravel
811.86
542.25
83.56
RBM1HRU5
Commercial-industrial, Sand & Gravel
520.54
1,857.49
860.58
RBM1HRU6
Agriculture, Sand & Gravel
24.19
267.29
293.69
RBM1HRU7
Forest, Till & Fine-Grained Deposits
0.00
0.00
0.00
RBM1HRU8
Open/non-residential, Till & Fine-Grained Deposits
255.73
628.12
148.13
RBM1HRU9
Medium-low density, Till & Fine-Grained Deposits
591.39
1,756.33
625.71
RBM1HRU10
Medium-high density, Till & Fine-Grained Deposits
435.23
263.97
57.33
RBM1HRU11
Commercial-industrial, Till & Fine-Grained Deposits
393.31
1,015.34
315.48
RBM1HRU12
Agriculture, Till & Fine-Grained Deposits
21.24
58.93
117.45
RBM1HRU13
Cranberry Bog
0.00
0.00
0.00
RBM1HRU14
Forested Wetland
0.00
0.00
0.00
RBM1HRU15
Nonforested Wetland
0.00
0.00
0.00
RBM1HRU16
Water
0.00
0.00
0.00
One tool available for identifying potential riparian areas for restoration based on upgradient loads is the
Riparian Analysis Toolbox35. WMOST v3 case studies will be added to the WMOST web site will
35 http://ches.cominunitymodeliiig.org/models.php#buffer
32
-------
3. Model Setup and Runs
illustrate this approach. Costs associated with riparian buffer land conversion or restoration may be found
in technical reports, guidance, or homeowners resources. National Resource Conservation Services
(NRCS) provides an Environmental Evaluation Planning Tool that includes guidelines for estimating
capital and O&M costs, and its state offices may provide regional fact sheets36. Once Riparian Buffers
page Step IB is complete, navigate to the input screen by pressing Return to Input. Check the box next to
the Riparian Buffers button to indicate that you have completed data entry for this category of input.
3.4 Water Use and Demand Management
On the Input page, enter the number of water user types. Do not include unaccounted-for-water (UAW)
as it is automatically included in all relevant input tables. UAW in WMOST is assumed to be real losses
from the system lost as leakage to the subsurface.
Press Setup Input Tables to automatically prepare input tables for potable, nonpotable, demand
management, and septic components of your system. The process creates blank input tables; there fore, do
not press this button again unless you have your input data saved elsewhere and want to change the
number of water user types.
3. Water use and demand management.
Enter the number of water use types but do not include unaccounted water; it is automatically included:
Press "Setup Input Tables" button to prepare appropriately sized input tables for potable and nonpotable demand and"
Navigate to each input tab associated with water use.
Potable
Nonpotable
l_- Demand
Septic and
Demand
Demand
Management
Sewer Systems
c systems data based on number of water use types.
Setup Input Tables<
Input Page Step 3A - Water Users and Water Demand
Select Potable Demand to navigate to the input table.
~
Potable
Demand
~
Nonpotable
Demand
~
Demand
Management
~
Septic and
Sewer System5
This table requires a time-series of the total water demand for all users entered for Input page Step 3,
plus demand attributable to unaccounted-for-water. This time series should be: 1) at the time step of your
model, that is, the same time step as runoff and recharge rates; 2) complete and consecutive; and 3) the
exact same time period as the runoff and recharge rate data.
30 https://www.nrcs.usda.gov/wps/portal/nrcs/main/national/teclinical/ecosciences/ec/
https://www.co.benton.or.iis/sites/default/files/fileattachments/comnuinity_development/page/2516/willametteripcost030310.p
df
33
-------
WMOST v3 User Guide
Date
Total Water Demand [million gallons/time step]
Residential
Commercial
{mnn/dd/yyyy)
Unaccounted
Residential
Institutions
/Business
Agricultural
Industrial
Municipal Other
1/1/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/2/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/3/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/4/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/5/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/6/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/7/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/8/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/9/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
1/10/2002
0.36
2.46
0.03
0.36
0.00
0.17
0.14
0.02
This section also includes an input table for the average percent consumptive water use37 by month. These
values can reflect any seasonal changes in consumptive use over the year, such as increased outdoor
watering in the summer and among water user types.
Water withdrawal and demand and consumptive use data may be available from state or regional sources.
For example, in Massachusetts, the Department of Environmental Protection receives such data in the
form of Annual Statistical Reports from water utilities38.
Enter data in blue input fields for each water use for each month.
Average Percent Consumptive Water Use (%)
Municipa
Residenti Commerc
l.lnstituti
al.lnstitu
ial.Busin Agricultu
onal.Non
Month
Residential
tions
ess ral
Industrial .profits Other
January
4
4
4
4
4
4
4
February
4
4
4
4
4
4
4
March
4
4
4
4
4
4
4
April
6
6
6
6
6
6
6
May
20
20
20
20
20
20
20
June
26
26
26
26
26
26
26
July
29
29
29
29
29
29
29
August
25
25
25
25
25
25
25
September
20
20
20
20
20
20
20
October
4
4
4
4
4
4
4
November
4
4
4
4
4
4
4
December
4
4
4
4
4
4
4
The final table on this page specifies the loadings added by each user type to potable water use and sent to
the wastewater treatment plant. The value should reflect the loadings added by the total number of users
in the watershed for each user type (e.g., if each user adds 0.2 lbs per time step, then multiply 0.2 lbs by
the user type population in your study area). Per
capita loading rates to wastewater or septic flow
can be applied to the public water population;
these values may be found in the literature.
® Consumptive water use is water removed from the system and not returned to the ground or stream. Examples include water
used for cooking, watering lawns, agriculture, and evaporation. Consumptive use may vary depending on the time of year so
the average percentage value may be entered by month.
http://www.mass.gov/eea/agencies/massdep/service/approvals/public-water-supply-annual-statistical-reporting.html
Enter average daily wastewater loadings of each constituent from each potable water user.
Loadings (lbs/time step)
Constituent Residential Residenti; Commerci Agricultur Industrial Municipal Other
TN 386.177506 0 0 0 0 0 0
34
-------
3. Model Setup and Runs
Select Return to Input and check the box next to Potable Demand when this section is complete. Next,
select Nonpotable Demand to navigate to the Nonpotable Demand page.
Septicand
Sewer Systems
Demand
Management
Nonpotable
Demand
Input Page Step 3B - Nonpotable Water Use
The total water demand can be attributed to potable and nonpotable water use. Enter the percent
nonpotable water use and percent consumptive use for nonpotable applications. The percent nonpotable
water use is the
maximum amount of
potable use that could be
met using nonpotable
water such as toilet
flushing or outdoor
irrigation. The values in
the columns or rows do
not need to add to 100%
for either table.
Maximum Potential Nonpotable Water Use (%)
Month Residential Residential.lnst Commercial.Bu; Agricultural Industrial Municipal. Other
January
45
45
45
45
45
45
45
February
45
45
45
45
45
45
45
March
45
45
45
45
45
45
45
April
45
45
45
45
45
45
45
May
45
45
45
45
45
45
45
June
45
45
45
45
45
45
45
July
45
45
45
45
45
45
45
August
45
45
45
45
45
45
45
September
45
45
45
45
45
45
45
October
45
45
45
45
45
45
45
November
45
45
45
45
45
45
45
December
45
45
45
45
45
45
45
Based on these
nonpotable input
data, the consumptive
use percent of potable
water is recalculated.
It is possible to enter
values for Maximum
Potential Nonpotable
Water Use and
Average Percent
Consumptive
Nonpotable Water Use that result in Adjusted Consumptive Potable Water Use values that are outside of
the feasible range of 0-100%. To help the user confirm that nonpotable input data do not create infeasible
Adjusted Consumptive Potable Water Use values, a third table on the Nonpotable Demand page pre-
calculates these adjusted values (see below). If any of the values are outside of the feasible range, they are
highlighted in red. In addition, the model will not run and the user is prompted with an error message to
change input values for Maximum Percent Nonpotable Use and/or Average Percent Consumptive
Nonpotable Water Use. Therefore, ensure that values are not highlighted in red in the table shown below
before proceeding.
Average Percent Consumptive Nonpotable Water Use (%)
Month Residential Residential.lnst Commercial.Bus Agricultural
Industrial
Municipal. Other
January
1
1
1
1
1
1
1
February
1
1
1
1
1
1
1
March
1
1
1
1
1
1
1
April
3
3
3
3
3
3
3
May
17
17
17
17
17
17
17
June
21
21
21
21
21
21
21
July
24
24
24
24
24
24
24
August
20
20
20
20
20
20
20
September
14
14
14
14
14
14
14
October
1
1
1
1
1
1
1
November
1
1
1
1
1
1
1
December
1
1
1
1
1
1
I 1
35
-------
WMOST v3 User Guide
Adjusted Consumptive Potable Water Use (%)
Month Residential Residential.lnst Commercial.Buf Agricultural Industrial Municipal. Other
January
6
6
6
6
6
6
6
February
6
6
6
6
6
6
6
March
6
6
6
6
6
6
6
April
8
8
8
8
8
8
8
May
22
22
22
22
22
22
22
June
30
30
30
30
30
30
30
July
33
33
33
33
33
33
33
August
29
29
29
29
29
29
29
September
25
25
25
25
25
25
25
October
6
6
6
6
6
6
6
November
6
6
6
6
6
6
6
December
6
6
6
6
6
6
6
The final table on this page specifies the loadings added by each user type to nonpotable water use and
sent to the wastewater treatment plant. The value should reflect the loadings added by the total number of
water users in the watershed for each user type. Per capita loading rates to wastewater or septic flow can
be applied to the public water population; these values may be found in the literature.
Enter average daily wastewater loadings of each constituent from each nonpotable water user.
Loadings (lbs/time step)
Constituent Residents Residentia Commerci Agricultur Industrial Municipal Other
TN 315.9634 0 0 0 0 0 0
Select Return to Input and check the box next to Nonpotable Demand when this section is complete. Press
Demand Management to enter information about how changes in price and other demand management
practices may affect demand in your study area.
Septic and
Sewer Systems
Nonpotable
Demand
Potable
Demand
Demand
Management
Input Page Step 3C -Demand Management
The first option is
reducing demand
by increasing the
price of water
services. Specify the price elasticity - percent change in water use divided by percent change in price -
for each type of water user. Price elasticities should be negative given that an increase in price is expected
to decrease water use. Price elasticities may be found in the literature but will depend on existing pricing
and other local conditions39. For example, if the consumer's purchase price of water is relatively high,
price elasticities will be smaller than if the existing pricing is relatively low. This reflects the fact that
increasing price indefinitely will not decrease demand indefinitely; therefore, it is not a linear effect. The
Price Elasticities [% demand reduction / % price increase]
Residential
Residential Commercial/
Institutions Business
Agricultural Industrial
Municipal Other
-0.2
-0.2| -0.2
-0.51 -0.1
-0.2| -0.2
39 For example, http://www.liks.harvard.edii/fs/rstavms/Monographs & Reports/Pioneer Olmstead Stavins Water.pdf
36
-------
3. Model Setup and Runs
user may specify the maximum price change possible within the planning horizon, which may be used to
limit price change over the range where the response is expected to be linear4".
Initial cost
23,000
$
O&M cost
2,300
$/yr
Maximum price change
49
%
Maximum percent increase in price of water services from existing price over the duration of the planning horizon
The initial cost may reflect the cost of a study to determine effective pricing structure and values, billing
frequencies, changes in billing logistics, and consumer outreach to convey the importance of efficient use
of water resources and the planned change in pricing. O&M costs may reflect smaller studies to re-
evaluate pricing every year or five years; however, be sure to enter the expected annual cost of such
evaluations.
The second option is direct demand reductions that may be achieved using rebates for water efficient
appliances, as well as changing
building codes, educational outreach,
and other practices. Initial and O&M
costs may be specified for the
aggregate cost of direct demand
reduction practices. The aggregate
effect of these practices should be
specified as a percent reduction of overall demand.
EPA's WaterSense website provides a calculator that together with local or Census data (e.g., number of
households) can be used to determine the total potential reductions in water use with the installation of
water efficient appliances41. When acquiring input data for these practices, the user must be aware of the
potential reduction in the individual effectiveness of demand management practices when multiple
practices are implemented simultaneously42
For any options that are not possible or desirable, enter "-9" for costs.
Select Return to Input and check the box next to Demand Management when this section is complete.
Press Septic and Sewer Systems to enter information about these systems in three sets of input tables.
0
Potable
Demand
0
Nonpotable
Demand
0
Demand
Management
Septic and^^
Sewer System^
40 The effect of price on water is assumed to be linear with WMOST v3 but nonlinear assumption may be implemented in future
version.
41 http://www.epa.gOv/watersense/our_water/start_saving.html#tabs-3
42 For example, rebates for water low flow shower heads will reduce the gallons per minute used in showering. If an increase in
water rates is implemented at the same time, the anticipated water use reduction may not be as large with a low flow shower
head as with a high flow shower head even if the new water rates induce shorter shower times.
Initial cost
200,000
$
O&M cost
4,000
$/yr
Total demand reduction
0.75
MGD
Total demand reduction value should equal the MGD reduction in demand across all
user types achieved by all management practices encompassed in the initial and
0&M cost.
37
-------
WMOST v3 User Guide
Input Page Step 3D - Septic and Sewer Systems
Of the three sets of input tables on the Septic and Sewer Systems page, set 1 is mandatory for all users,
set 2 is mandatory for users using the CSO Module, and set 3 is mandatory for users modeling water
quality.
In input table set 1 (see screenshot below), you must enter the percent of customers with septic systems
inside and outside of your study area that are on public water. Customers that are not on public water
should be represented as private withdrawals and discharges on the Surface Water or Groundwater
Customers with Public Water & Septic Systems Recharging Inside Study Area (%)
Residential Residential.lnstit Commercial.Busi Agricultural Industrial Municipal.institu Other
62 62 62 62 62 62 62
Customers with Public Water & Septic Systems Recharging Outside Study Area (%)
Residential Residential.lnstit Commercial.Busi Agricultural Industrial Municipal.Institu Other
0 0 0 0 0 0 0
For public water users, it is important to distinguish public water customers who are on septic systems but
are outside of the watershed of the study area being modeled. These septic systems do not recharge the
groundwater and do not contribute to the baseflow of the stream in the study area's watershed.
Input table set 2 on the Septic and Sewer Systems page specifies the capacities of the sewer system.
WMOST inherently models a storm and/or sanitary sewer system when the CSO Module is not in use
(i.e., routing all runoff through the storm sewer and all flows to the WWTP through the sanitary sewer).
Therefore, when the CSO Module is not in use, users can enter "-9" in the corresponding cells to exclude
defining sewer capacities. However, when the CSO Module is in use, WMOST has the option to model a
separate storm/sanitary sewer system from the combined sewer system, making it necessary for sewer
capacities to be set.
Storm Sewer
To exclude limits on
Maximum capacity of storm sewer
3
MGD
the storm sewer, enter -9.
When the CSO Module is not in use, the storm sewer
receives all flows from the runoff and any municipal
flows that go directly to the sewer system and routes
them to the surface water system. When the CSO
Module is in use and sewer separation is a
management option, the model will choose a
percentage of flows that are intended for the
combined sewer to flow through the storm sewer.
Regardless of whether or not the CSO Module is in
use, if the study area watershed includes municipal
water users, users can enter the percentage of
municipal water use that flows directly to the sewer
system (screenshot to the left). If the study area
watershed does not include any municipal water users, the percentages can be set to "0".
pages depending
on their source
and discharge of
water (see Input
page Step 4 below
for description of
these input pages).
Municipal flows that go directly to sewer system (%)
Month Municipal
January
February
March
April
May
June
July
August
September
October
November
December
38
-------
3. Model Setup and Runs
Similar to the storm sewer, when the CSO Module is not in use, the sanitary sewer receives flows from
potable and nonpotable users and routes them to the wastewater treatment plant. When the CSO Module
is in use and sewer separation is a management option, the model will choose a percentage of flows that
are intended for the combined sewer to flow through the sanitary sewer.
Sanitary Sewer
To exclude limits on the
Maximum capacity of sanitary sewer
5
MGD
sanitary sewer, enter -9.
The Septic and Sewer Systems page requires additional data inputs for modeling water quality that can
be input into table set 3. If you are not modeling water quality, continue to Input Page Step 4A - Surface
Water & System Targets.
For water quality users, first enter the average effluent
concentration of your constituent from the septic system.
Average septic effluent concentrations may be found in
septic system guidelines, design reports, or in the literature.
For example, EPA Office of Water provides guidelines in the report "Qnsite Wastewater Treatment
Systems Manual"' (2002).
Next, you have the option to enter inputs for upgrading septic systems in your watershed to "enhanced''
septic treatment to reduce loadings to the groundwater.
To consider sewer system upgrades, you must enter the following data:
• Enhanced treatment average effluent concentration from the enhanced septic systems
• O&M cost related to enhanced septic treatment
• Maximum capacity of enhanced septic system upgrades. The maximum capacity should represent
the sum of the maximum capacity for all potential system upgrades. To exclude this management
option, enter "-9" in the management option exclusion input field.
Enter the daily average effluent concentration
for septic treatment of each constituent.
Constituent Concentration (mg/L)
TN 24
Enter the daily average effluent concentration
for enhanced septic treatment of each constituent-
Constituent Concentration (mg/L)
TN
16
Enhanced Septic Treatment
O&M cost for enhanced septic capacity 800
$/MG
Maximum capacity of enhanced septic 1
MGD
To exclude enhanced
septic treatment, enter -9.
Select Return to Input and check the box next to Septic and Sewer Systems when the section is complete.
Proceed to Input Page Step 4.
Septicand
Sewer Systems
Potable
Demand
Demand
Management
Nonpotable
Demand
39
-------
WMOST v3 User Guide
3.5 Water Supply Sources and Infrastructure
Input Page Step 4A - Surface Water & System Targets
Press Surface Water & System Targets to navigate to five sets of input tables.
^urface Wate™
& System 1
Targets
~ 1
~
Groundwater |
~
Interbasin
Transfer
~
Infrastructure |
In input table set 1 of this section (screenshot below), you can enter reservoir or surface storage properties
and costs. Reservoir and surface storage may represent reservoirs, lakes or ponds used for water supply
and/or surface storage tanks. Surface storage in wetlands or other lakes may be modeled as surface
storage or as a separate HRU. Initial volume is the volume at the start of modeling period. Minimum
target volume may represent the volume of water always maintained in storage for emergencies or
inactive storage volume which is inaccessible due to the height of the storage outlet. Existing maximum
volume is the total volume of existing storage.
To exclude new/additional capacity for a surface water storage, enter -9.
-9
Cost for make-up surface water penalty
1,000,000
$/MG
To exclude make-up water penalty, enter -9.
Finally, reservoir outflow can either be entered as a data time series or included as a decision variable
based on the input to the field below. In this example, the model will optimize the outflow from the
reservoir.
Enter Yes to use Reservoir/Sw Outflow as data time series
or No to allow Reservoir/Sw Outflow to be a decision.
No
Initial reservoir/surface storage volume
SO
[MG]
Minimum target reservoir/storage volume
33
[MG]
Existing maximum reservoir/storage volume
1,240
[MG]
Initial construction cost
0
[$/MG]
O&M costs
0
[$/MG]
Maximum additional reservoir/storage volume
0
[MG]
Initial construction cost
should include the costs to
plan, design and build
additional surface storage
volume. O&M cost should
include the annual cost for
maintaining surface storage
capacity in operational
condition. Maximum additional volume is the volume that may be added by building surface storage
volume. To exclude an increase in reservoir/surface storage volume as a management option, enter "-9" in
the input field shown below.
Make-up water represents virtual water that the model needs to "purchase" to reach a feasible solution. To
allow the model to use make-up water in the reservoir system, enter a cost in the input field shown and
leave the exclusion flag input box blank (see screenshot below). Costs related to make-up water should be
sufficiently high so that selecting this option is a last resort for the model.
40
-------
3. Model Setup and Runs
In input table set 2 (screenshot below), you may enter information about other withdrawals and discharges
of surface water such as industrial users that are not on public water. These data may be available from
state sources such as the Department of Environmental Protection or regional sources (e.g., regional EPA
offices). In addition, if the stream into which your study area drains receives inflow from an upstream
reach, enter a time series for the inflow of this surface water. These data should be available from the
model from which you may have obtained your RRRs. If a reservoir exists in your study area, you may
enter information on surface reservoir withdrawals, discharges, or outflow requirements. Withdrawals and
discharges to reservoirs may be related to human activity or natural hydrologic processes over the
reservoir, such as precipitation and evapotranspiration. Precipitation and evapotranspiration for water
modelled as HRUs are automatically calculated by WMOST but must be specified for storage reservoirs.
Date (mm/dd/yyyy)
Other Sw Other Sw External
Withdrawal Discharge Sw Inflow
[MG/time step] [MG/tirne step] [cfs]
Withdrawals Discharge to
from Reservoir Reservoir
[MG/tirne step] [MG/time step]
Outflow from
Reservoir
[MG/time step]
1/1/2002
0.794189
3.629
0
0
0
0.00
1/2/2002
0.794189
3.629
0
0
0
0.00
1/3/2002
0.794189
3.629
0
0
0
0.00
1/4/2002
0.794189
3.629
0
0
0
0.00
1/5/2002
0.794189
3.629
0
0
0
0.00
1/6/2002
0.794189
3.629
0
0
0
0.00
1/7/2002
0.794189
3.629
0
0
0
0.00
1/8/2002
0.794189
3.629
0
0
0
0.00
1/9/2002
0.794189
3.629
0
0
0
0.00
1/10/2002
0.794189
3.629
0
0
0
0.00
1/11/2002
0.794189
3.629
0
0
0
0.00
These time-series must be at the temporal resolution of your model (i.e., daily or monthly) and over the
same time period as other time series. The dates will be pre-filled for you based on the time series on the
Runoff page. As with other time series data, they must be complete and consecutive. For any of the time
series, if you do not have data or they do not exist, enter "-9" for all dates. Note that upstream inflow is
critical, especially if you will be specifying any streamflow requirements.
In input table set 3, you may provide
management goals for minimum and/or
maximum in-stream flow on a monthly
basis. In addition, any requirements for
flow to a downstream reach may be
specified. Requirements or guidelines
for minimum and/or maximum in-
stream flow may be found at the state
or regional level. For example, in New
England, there are Stream Flow
Recommendations43 and in
Massachusetts, there is a Sustainable
43 http://www.fws.gov/newenglaiid/pdfs/Flowpolicy.pdf
For minimum and maximum values, enter -9 and the model will not apply the constraint
Minimum
Maximum
Minimum
Maximum
Sw Outflow
Sw Outflow
In-Stream
In-stream
to External
to External
Month
Flow [cfs]
flow [cfs]
Sw [cfs]
Sw [cfs]
January
16.6
-9
-9.0
-9.0
February
19.1
-9
-9.0
-9.0
March
17.3
-9
-9.0
-9.0
April
19.4
-9
-9.0
-9.0
May
15.9
-9
-9.0
-9.0
June
18.5
-9
-9.0
-9.0
July
18.4
-9
-9.0
-9.0
August
18.7
-9
-9.0
-9.0
September
18.8
-9
-9.0
-9.0
October
17.5
-9
-9.0
-9.0
November
17.5
-9
-9.0
-9.0
December
17.1
-9
-9.0
-9.0
41
-------
WMOST v3 User Guide
Water Management Initiative Framework44. If any of these flow requirements do not exist in your study
area, enter ""-9" for each month of that set.
The Surface Water & System Targets page requires additional data inputs for modeling water quality.
If you are not modeling water quality, continue to Input Page Step 4B - Groundwater.
In input table set 4, you must enter data inputs related to the constituent's behavior in the stream and
reservoir. First, enter the initial concentration of your constituent in the reservoir on the first day of your
time period. Initial concentration for surface water is determined by the model. Next, enter the 0th or 1st
order decay rate of your constituent in the reservoir. Decay rates may be found in the model
documentation from which you may have obtained your RRRs. Representative rates can also be obtained
from regional SPAtially Referenced Regressions On Watershed attributes (SPARROW)45 models. You
may exclude modeling of decay by entering "-9" in both input fields.
Finally, enter the stream or reservoir concentration or loadings target for your constituent. Of the four
possible target types, you may only select one target type per model run. The in-stream concentration and
loadings target apply to the water quality in the stream. The reservoir concentration target applies to the
concentration in the reservoir, while the reservoir loadings target applies to the loadings from the stream
to the reservoir (i.e., the loads entering the reservoir, not the loads stored in the reservoir). Requirements
or guidelines for maximum concentrations or loadings may be found at the waterbody, state or regional
level (e.g., Total Maximum Daily Load [TMDL] allocations).
In-stream
Reservoir
TN
TN
Initial Condition: Enterthe initial concentration of the reservoir.
Concentration (mg/L)
-
0.4
Decay/Settling Rate: Enter a removal rate value and -9 forthe excluded removal rate.
|oth order rate (mg/L/time step)
-
-9
OR
1st order rate (l/time step)
-
0.1
Target Concentration/Loadings: Enter-9 if target concentration or loadings do not need to be met.
|Target concentration (mg/L)
1
-9
OR
OR
|Target loading (lbs)
-9
-9
|Yes | Enter Yes if modeling 1st order removal in proportion to surface area or
No if modeling removal based on decay rate only.
| Reservoir surface area (acres) | 10p|lfyes, enter the surface area of the reservoir in the blue box at left.
In this section, you have the option to proportionally model
first order decay based on the surface area of your reservoir
similar to the methods for estimating the fraction of the
contaminant mass transported through a reservoir segment
used within the SPARROW model. To do this, enter "Yes"
in the first input field and the surface area of your reservoir
44 http://www.mass.gov/eea/docs/eea/water/swmi-framework-nov-2012.pdf
45 https://water.usgs.gov/nawqa/sparrow/
TN Loadings Time Series
Private Reservoir External Sw
Private Sw Point Source Loadings Loadings
Loadings [Lbs/time step] [Lbs/time step] [Lbs/time step]
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
199.27
0.00
0.00
42
-------
3. Model Setup and Runs
in the second input field. To exclude this option, enter "No" in the first input field and leave the second
blank.
In input table set 5, you may enter information about point source loadings to the stream or reservoir via
private dischargers, and loadings entering the system via external surface water inflow. To calculate these
time series, you can apply the concentration of the point source discharge to the "Other Surface water
(Sw) Discharge" hydrology time series in your system to calculate the point source loadings time series.
Point source discharge concentration data may be available from EPA's Discharge Monitoring Tool46
(DMR).
Select Return to Input and check the box next to Surface Water & System Targets when this section is
complete. Select Groundwater to navigate to the next five sets of input tables.
0
Surface Water
& Streamflow
Targets
~
. Groundwater B
~
Interbasin
Transfer
~
Infrastructure
Input Page Step 4B - Groundwater
The same state and regional data sources used to populate the Surface Water & System Targets page
are recommended for populating the Groundwater page. Within input table set 1, information about
groundwater storage characteristics will likely be derived from the same model that you obtained the
runoff and recharge rates. These data include:
• Groundwater recession coefficient or baseflow coefficient - fraction of groundwater volume that
flows to the stream reach each time step
• Initial groundwater volume - volume of the active groundwater aquifer at the start of the modeling
period
• Minimum volume - this volume may be based on the depth of wells which are used for water supply
below which water is inaccessible and/or the volume at which the water table will be below the
stream bed and therefore no longer emptying to the stream
• Maximum volume - this value represents the total storage capacity of the aquifer.
Groundwater recession coefficient
0.09
[1/time step]
To exclude make-
up water penalty,
enter -9.
Initial groundwater volume
1,000
[MG]
Minimum volume
10
[MG]
Maximum volume
80,000
[MG]
Cost for make-up groundwater
1,000,000
$/MG
The maximum volume can be obtained from information available from model documentation or from
ancillary documents describing groundwater resources for a region of interest.
If you used the Baseline Hydrology Module, you may use Calculate and Populate the Groundwater
Recession Coefficient button to calculate
this value.
40 https://cfpiib.epa.gov/drnr/
If you used the Baseline Hydrology module, you may automate the
calculation of the groundwater recession coefficient.
Calculate and Populate the Groundwater Recession Coefficient
43
-------
WMOST v3 User Guide
Within input table set 2, similar to the Surface Water & System Targets page, you can enter time series
data for other groundwater withdrawals, discharges and inflow into the study area.
Depending on the model used, if you downloaded your baseline recharge time series from the EDM Data
Inventory and used the Baseline Hydrology Module to create your baseline recharge time series, a small
part of the water balance
may not yet be present in
the model. During
preprocessing, all negative
recharge values in the
baseline recharge time
series have been removed
from the recharge time
series in order to be
compatible with WMOST.
The negative recharge
values are retained as
positive values in the
WMOST recharge
adjustment files. If this applies to your watershed, the data are available as a CSV file in the folder
labeled: "\EDM_Server_ZIP\w mostEDM_recharge" within your WMOST project folder. Enter the sum
of all the recharge values for your HRUs and time period into the model as a part of the other
groundwater withdrawals time series.
In input table set 3, similar to the Surface Water & Streamflow
Targets page, you can enter requirements for groundwater flowing
out of the basin. In most cases, this groundwater flow will not exist
as the groundwater will drain to the stream reach; however, this
option provides flexibility in defining a study area or when
groundwater and surface water watersheds do not overlap. If
groundwater and surface water watersheds are coincident, enter all
"Os" in this table.
The Groundwater page requires additional data inputs for modeling
water quality. If you are not modeling water quality, continue to
Input Page Step 4C - Interbcisin Transfer
In Part 4, you must enter the initial concentration of your constituent in the groundwater system. You also
have the option of specifying a 0th or 1st order attenuation rate. Attenuation rates may be found in the
model documentation from which you may have obtained your RRRs. You may exclude modeling of
attenuation by entering ""-9" in both input fields.
Other Gw Other Gw External Gw
Withdrawal Discharge Inflow [MG/ti
Date [mm/dd/yyyy] [MG/time step] [MG/time step] step]
me
1/1/2002
3.02
4.45
0.00
1/2/2002
3.02
4.45
0.00
1/3/2002
3.02
4.45
0.00
1/4/2002
3.02
4.45
0.00
1/5/2002
3.02
4.45
0.00
1/6/2002
3.02
4.45
0.00
1/7/2002
3.02
4.45
0.00
1/8/2002
3.02
4.45
0.00
1/9/2002
3.02
4.45
0.00
1/10/2002
3.02
4.45
0.00
1/11/2002
3.02
4.45
0.00
Enter a minimum value or zero if the ground and
surface watersheds are coincident.
Minimum External
Gw Outflow
Month
[MG/time step]
January
0.00
February
0.00
March
0.00
April
0.00
May
0.00
June
0.00
July
0.00
August
0.00
September
0.00
October
0.00
November
0.00
December
0.00
44
-------
3. Model Setup and Runs
Groundwater
TN
Initial Condition: Enter the initial constituent concentration in groundwater.
Concentration (mg/L)
0.1
Attenuation Rate: Enter a removal rate value and -9 for the excluded removal rate,
Oth order rate (mg/L/time step)
-9
OR
1st order rate (l/time step)
0.05
TN Loadings Time Series
Private Gw Point External Gw
Source Loadings Loadings
[Lbs/time step] ^Lbs/time step]
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
254.07
0.00
In Part 5, you may enter information about point source loadings to the
groundwater via private dischargers, and loadings entering the system via
external groundwater inflow. To calculate these time series, you can
apply the concentration of the groundwater discharge to the "Other
Groundwater (Gw) Discharge" time series in your system to calculate the
point source loadings time series. Groundwater point source
concentrations depend on the type of discharge and the region. These data
may be available from state sources such as the Department of
Environmental Protection or regional sources (e.g., regional EPA offices).
Select Return to Input and check the box next to Groundwater when this
section is complete. Select Interbasin Transfer (IBT) to navigate to three
sets of input data tables.
0
Surface Water
& Streamflow
Targets
0
Groundwater
~ <
Interbasin .
V. Transfer
Infrastructure
Input Page Step 4C - Interbasin Transfer
In input table set 1, you can enter data for:
• Initial costs for water and wastewater rights in addition to any existing agreements including costs for
any new infrastructure to utilize the additional rights 47
• Costs to purchase water and wastewater from systems outside of your study area, which is what the
utility pays to the provider of the imported source or the external wastewater facilities.
If you do not want IBT as a management option, enter -9 for costs AND 0 for flow limits.
Purchase cost for potable water
670
[$/MG]
Purchase cost for wastewater
946
[$/MG]
Initial cost for new/increased IBT potable water limit
-9
[S/MGD]
Initial cost for new/increased IBT wastewater limit
-9
[S/MGD]
47 The case study of Danvers and Middleton, MA provides costs associated with initial connection for water with the
Massachusetts Water Resources Authority, a large regional water and wastewater provider.
45
-------
WMOST v3 User Guide
In input table set 2, enter any existing monthly limits for interbasin transfer of water and wastewater in
the left table and daily or annual limits in the right table. Depending on the time step of your model, the
daily, monthly, and/or annual limits are adjusted to specify appropriate constraints in the model.
Enter existing limits on IBT for daily, monthly and/or annual basis. If flow is not limited, enter -9.
Existing Limits on IBT [MG per month]
Existing Limits on IBT
Month
Water
Wastewater
Water
Wastewater
January
-9.00
-9.00
Daily [MGD]
3.34
0.58
February
-9.00
-9.00
Annual [MGperyear]
-9.00
-9.00
March
-9.00
-9.00
April
-9.00
-9.00
May
-9.00
-9.00
Additional Capacity
June
-9.00
-9.00
Water
Wastewater
July
-9.00
-9.00
Daily [MGD]
0.00
0.00
August
-9.00
-9.00
September
-9.00
-9.00
October
-9.00
-9.00
November
-9.00
-9.00
December
-9.00
-9.00
The following guidelines for specifying limits and initial costs for increasing limits are important to note:
• If von do not have interbasin transfer as an option, you must enter "0 "for limits. Entering ""-9" will
indicate no restriction, that is, unlimited interbasin transfer is available. As such, if you enter ""-9" for
daily, monthly or annual limits, then you must specify the initial cost for new/increased IBT.
• If additional water or wastewater services can be purchased with no additional initial costs or entry
fees, then enter the current agreement limit for services and specify $0 for initial cost for a
new/increased limit (i.e., do not enter "-9" for the existing limit).
• If your system provides water services to customers outside of the basin without a return flow via the
wastewater treatment plant or septic systems, you may specify these customers as a separate water
user type that entirely drains to septic outside of the study area. If your system provides out of basin
wastewater services that discharge in your basin, you may enter this flow as a private discharge of
surface water (or groundwater, depending on where the wastewater treatment plant discharges).
WMOST does not support routing out of basin wastewater to the wastewater treatment plant. It may
be added as functionality in future versions.
• If your system's wastewater is treated outside of the basin at a larger, central facility and you want to
model returning the treated wastewater for discharge locally, then you may enter a capital cost for a
wastewater treatment plant that represents the construction of infrastructure necessary to return and
discharge the treated wastewater. In addition, enter O&M costs that reflect the IBT O&M cost and
exclude the use of IBT for wastewater. This will effectively model the desired scenario. If the
returned wastewater will be discharged to groundwater rather than surface water, follow the same
procedure but apply it to the aquifer storage and recharge facility rather than the wastewater treatment
plant. See below under Input Page Step 4D - Infrastructure for input data tables related to wastewater
treatment plant and aquifer and storage recharge facility.
The Interbasin page requires additional data inputs for modeling water quality. If you are not modeling
water quality, continue to Input Page Step 4D - Infrastructure.
46
-------
3. Model Setup and Runs
In input table set 3, you must enter the average
concentration of your constituent in the potable
interbasin flow if your system is using or
considering using interbasin transfer for potable
water. This concentration should reflect the
concentration of the interbasin potable flow to users after the raw water has been treated.
Select Return to Input and check the box next to Interbasin Transfer when this section is complete. Select
Infrastructure to navigate to the next section, where you can enter information about costs and capacity
limits for a range of water and wastewater facilities. This section consists of six sets of input tables.
Enter average concentration of constituent in
interbasin transfer flow into the watershed.
Constituent Concentration (mg/L)
TN 1.2
0
Surface Water
& Streamflow
Targets
0
Groundwater
0
Interbasin
Transfer
~ f Infrastructure J
Input Page Step 4D - Infrastructure
In input table set 1, you enter the planning horizon for large capital improvement projects and the interest
rate for loans for such projects. For any management option for which a project lifetime is not requested,
the planning horizon is used for the lifetime over which the initial cost is annualized. The specified
interest rate is used for the annualization of all initial and capital costs. For mathematical equations
describing the annualization of capital costs, please refer to Section 3.2 in the Theoretical Documentation.
Planning horizon [years]
20
Interest rate [%]
3.00
In input table set 2 (see screenshot on the next page of the user guide), enter data related to providing
water services including:
• Consumer's price for potable water from the local utility-this may be specified as a monthly fixed fee
and/or volume based fee
• Facility data for groundwater pumping, surface water pumping and water treatment plant including
o Capital costs - cost for increasing capacity or cost for replacing existing capacity beyond the
remaining lifetime
o O&M costs - cost for operating based on the size and flow through the facility;
o Existing maximum capacity of the facility
o Lifetime remaining on existing infrastructure or the number of years expected to remain before
major capital rehabilitation or new facility must be built
o Lifetime of new infrastructure - the expected lifetime of new construction before major capital
rehabilitation or new facility must be built
• Potable distribution system data including
o Initial cost for surveying the distribution system for leaks and repairing to the maximum
percent feasible
o O&M costs representing annual costs for maintaining repairs made to the distribution system
47
-------
WMOST v3 User Guide
o Maximum percent of distribution system leaks that can be fixed - this value may be less than
100% due to practical limitations of many miles of pipes
If no water treatment plant exists in your study area (i.e., all water is from interbasin transfer), then enter
"0" for maximum capacities and remaining lifetimes. However, still enter the price that is charged for
customers for water services. To exclude the option to increase facility capacity, enter "-9" in the
"Exclude New/Additional" field for the appropriate facility.
Users can obtain data on the facility costs and capacities from the facility managers (likely the public
works utility or water district). Data inputs may be derived from utility budgets or facility usage reports.
If the cost data are not available, users can utilize the data from example case studies of WMOST as cost
estimates, but these values should be used with caution and analyzed using sensitivity analyses.
Water services
Value Units
To exclude new and additional capacity for
Consumer's price for potable water: Fixed fee
84,942
$/month
enter -9 in the corresponding blue box.
Exclude New/Additional Capacity
Consumer's price for potable water: Variable, volume-based fee
4.56
$/HCF
Groundwater (Gw) Pumping
-9|
Capital cost for additional capacity
5,787,037
$/MGD
Exclude New/Additional
Operation & Maintenance (O&M) costs
670.02
$/MG
Existing maximum capacity
5.45
MGD
Lifetime remaining on existing infrastructure
25
yrs
Lifetime of new construction
25
yrs
Surface Water (Sw) Pumping
-9|
Capital cost for additional capacity
467,621
$/MGD
Exclude New/Additional
O&M costs
184.95
$/MG
Existing maximum capacity
6.00
MGD
Lifetime remaining on existing infrastructure
25
yrs
Lifetime of new construction
25
yrs
Water Treatment Plant (WTP)
-9|
Capital cost for additional capacity
6,229,186
$/MGD
O&M costs
0.00
$/MG
Existing maximum capacity
7.16
MGD
Lifetime remaining on existing infrastructure
25
yrs
Lifetime of new construction
25
yrs
Unaccounted-for-Water/ Potable water distribution system leak
Initial cost for survey & repair
455,000
$
O&M costs for maintaining reduction in UAW
45,500
$/yr
Maximum percent UAW that can be fixed
0.00
%
Users modeling water quality
need to enter additional data
inputs within input table set 2
(see screenshot to the right). Of
the additional data inputs, only one, the average daily effluent concentration, is required. If your plant has
a maximum daily influent concentration, you can enter the concentration as a treatment facility constraint.
If there is no maximum daily influent concentration, enter ""-9".
Users also have the option of upgrading the level of treatment in the water treatment plant. If selected, this
management option partitions flows within the water treatment plant, such that a portion of the flows
receives the upgraded level of treatment and the remaining flows receive the current level of treatment.
Water Treatment Plant (WTP) Loadings
Value Units
Maximum daily influent concentration
-9
mg/L
Average daily effluent concentration
0.1
mg/L
48
-------
3. Model Setup and Runs
This management option would be useful for meeting in-stream or reservoir target concentrations and
maximum influent concentrations at the wastewater treatment plant. To consider a treatment upgrade,
enter data (see screenshot below) related to the upgraded water treatment plant including:
• Capital cost - cost for
new capacity or cost
for replacing existing
capacity beyond the
remaining lifetime
• Lifetime of new
infrastructure - the expected lifetime of new construction or for replacing existing capacity beyond
the remaining lifetime
• Average daily effluent concentration - the effluent concentration achieved by the upgraded treatment
system. This concentration must be lower than the effluent concentration of the water treatment plant.
The O&M costs and capacity that apply to the water treatment plant also apply to the upgraded water
treatment plant. To exclude the option to upgrade treatment capacity, enter "-9" in the "Exclude New
Treatment" input field for the upgraded water treatment plant.
In input table set 3, enter similar data for wastewater services as for water services including consumer's
price, capital and O&M costs, lifetime of new and existing infrastructure, and repair of infiltration into
collection system. Two additional types of information are requested:
• "Are wastewater fees charged based on metered water or wastewater?" - Most wastewater utilities in
the U.S. charge for wastewater services based on metered potable water delivered to a customer.
However, the option is provided to charge based on metered wastewater to determine the effect of
separating metering.
• "Existing Gw infiltration into collection system" - Specify the percent of wastewater inflow to the
wastewater treatment plant that represents groundwater infiltration (infiltration/inflow).
Wastewater Treatmerit Plant (WWTP)
Value
Units
Exclude New/Additional
Consumer's price for wastewater services: Fixed fee
262,918
5/month
-g|
Consumer's price for wastewater services: Variable, volume-based fee
6.30
$/HCF
Are wastewater fees charged based on metered water or wastewater?
water
water or wastewater
Capital cost for additional capacity
16,266,433.00
$/MGD
O&M costs
946.33
$/MG
Existing maximum capacity
3.14
MGD
Lifetime remaining on existing infrastructure
25
years
Lifetime of new construction
25
years
Infiltration into wastewater collection system
Existing Gw infiltration into collection system
0
% of WW Inflow
Initial cost for survey & repair
0
$
O&M costs for maintaining reduction in infiltration
0
$/yr
Maximum percent of infiltration that can be fixed
0.00
%
To exclude the option to increase wastewater treatment plant capacity, enter "-9" in the "Exclude
New/Additional" input field.
49
Upgraded Water Treatment Plant (WTP) Units Exclude New Treatment
Capital cost for additional treatment
500000
$/MGD
Lifetime of new construction
25
yrs
Upgraded WaterTreatment Plant (WTP) Loadings Reduction
Average daily effluent concentration
0.05|mg/L
-------
WMOST v3 User Guide
Users modeling water quality need to enter
additional data inputs in input table set 3 (see
screenshot to the right). Of the additional data
inputs, only one, the average daily effluent
concentration, is required. If your plant has a maximum daily influent concentration, you can enter the
concentration as a treatment facility constraint. If there is no maximum daily influent concentration,
enter "-9".
Like the upgraded water treatment plant option, users can consider a wastewater treatment plant upgrade
that will treat a portion of
the flows through the
wastewater treatment plant
to a higher treatment level.
This option would be useful
for meeting in-stream or
reservoir target concentrations. In addition, if your watershed experiences combined sewer overflow
(CSO) events, this management option could be used to meet the minimum level of treatment that is
presumed to meet water quality-based standards. Enter similar data (screenshot to the right) for the
upgraded wastewater treatment plant as for the upgraded water treatment plant, including:
• Capital cost - cost for new capacity or cost for replacing existing capacity beyond the remaining
lifetime
• Lifetime of new infrastructure - the expected lifetime of new construction or for replacing existing
capacity beyond the remaining lifetime
• Average daily effluent concentration - the effluent concentration achieved by the upgraded treatment
system. This concentration must be lower than the effluent concentration of the water treatment plant.
To exclude the option to upgrade treatment capacity, enter "-9" in the "Exclude New Treatment" input
field for the upgraded wastewater treatment plant.
In input table set 4, enter data for a water reuse facility (WRF) similar to water and wastewater facilities
including the ability to exclude new and additional capacity.
Water Reuse Facility (WRF)
Value
Units
Exclude New/Additional
Capital cost for additional/ new capacity
18,544,791
$/MGD
"9
O&M costs
1,305,135.00
$/MG
Existing maximum capacity
0.00
MGD
Lifetime remaining on existing infrastructure
0
yrs
Lifetime of new construction
35
yrs
If no water reuse facility exists in your study area, then enter ""0" for maximum capacities and remaining
lifetimes. If you want to model the addition a new water reuse facility, enter the associated capital and
O&M costs. To exclude the option to increase facility capacity, enter "-9" in the "Exclude
New/Additional" input field.
Users modeling water
quality need to enter an
additional data input in
Wastewater Treatment Plant (WWTP) Loadings
Value Units
Maximum daily influent concentration of Consl
-9
mg/L
Average daily effluent concentration
3.4
mg/L
Upgraded Wastewater Treatment Plant (WWTP)
Exclude New Treatment
Capital cost for additional treatment
1200000
$/MGD
1
Lifetime of new construction
25
yrs
Upgraded Wastewater Treatment Plant (WWTP) Loadings Reduction
Average daily effluent concentration
1.8|mg/L
Water Reuse Facility (WRF) Loadings
Value Units
Average daily effluent concentration
0
mg/L
50
-------
3. Model Setup and Runs
input table set 4. Enter the daily effluent concentration achieved by the water reuse facility. As shown in
the screenshot above, the user is not modeling a water reuse facility and, accordingly, set the average
daily effluent concentration to 0 mg/L.
In input table set 5, enter data for a nonpotable water distribution system which are similar to the other
facilities but, in addition, specify the price that would be charged to customers for the provision of
nonpotable water.
Nonpotable Water Distribution System
Value
Units
Exclude New/Additional
Consumer's price for nonpotable water: Fixed fee
0
$/month
-s|
Consumer's price for nonpotable water: Variable, volume-based fee
3.11
$/HCF
Capital cost for additional capacity
12,529,440
$/MGD
O&M costs
1,768.00
$/MG
Existing maximum capacity
0.00
MGD
Lifetime remaining on existing infrastructure
0
yrs
Lifetime of new construction
35
yrs
In input table set 6, enter data for an aquifer storage and recovery (ASR) facility similar to the other
facilities.
Aquifer Storage and Recovery (ASR)
Value
Units
Exclude New/Additional
Capital cost for additional/new capacity
10,807,824
$/MGD
-9
O&M costs
3,883.00
$/MG
Existing maximum capacity
0.00
MGD
Lifetime remaining on existing infrastructure
0
yrs
Lifetime of new construction
35
yrs
Users modeling water quality need to enter an additional data input in input table set 6. If the ASR facility
uses a treatment system, enter the average daily effluent concentration achieved by the ASR facility. The
capital cost and lifetime of existing or new construction for the ASR facility will apply to both flows and
loadings, similar to the O&M costs and capacities. To exclude the option to model water quality, enter
""-9" in the "Exclude Treatment" input field.
Aquifer Storage and Recovery (ASR) Loadings
Value
Units
Exclude Treatment
Average daily effluent concentration
0
mg/L
-9
Select Return to Input and check the box next to Infrastructure when this section is complete.
Surface Water
0 & Streamflow
Targets
0
Groundwater
0
Interbasin
Transfer
0
Infrastructure
3.6 CSO Module
To apply management options that minimize the number of combined sewer overflow (CSO) events,
press CSO Module— to navigate to the CSO page, which includes three steps.
! The CSO Module button is only visible when modeling hydrology only.
51
-------
WMOST v3 User Guide
5. CSO Module. If you wish to model the application of combined sewer overflow (CSO) management, proceed to the CSO module.
Iii CSO page Step 1 (see screenshot
on left), you must first indicate the
maximum allowable number of CSO
events. Then, you must define the
conditions that define a CSO event.
CSO events, within WMOST, are
instances where: 1) the runoff
fraction routed to the combined
sewer exceeds the specified hydraulic
capacity of the combined sewer, or 2)
the sum of the runoff fraction, flows from potable and nonpotable water users intended for the wastewater
treatment plant, and groundwater infiltration exceeds the specified hydraulic capacity of the interceptor
sewer that flows to the WWTP. In order to determine whether a CSO event occurs, enter the hydraulic
capacity of the combined sewer and the hydraulic capacity of the wastewater treatment plant.
CSO Module
1. Combined Sewer Overflow Events
Enter the hydraulic capacity of runoff and the hydraulic ca
and the number of times those hydraulic capacities can
3acity of sewage flows through the combined sewer
be exceeded annually.
Enter the maximum number of CSO events.
4|event(s)/yr |
Enter the hydraulic capacity for runoff
routed through the combined sewer.
9|MGD
Enter the hydraulic capacity for sewage
flows to the wastewater treatment plant.
io.i|mgd
2. CSO Management Options
Enter the specifications for the management options available for minimizing the annual number of CSO events.
2A. Offline Storage
Enter the O&M cost per MG and the maximum capacity of the offline storage.
O&M cost for offline storage
20000
$/MG
Maximum offline storage
10
MGD
Exclude Offline Storage
To exclude offline storage as a
management option, enter -9.
2B. Sewer Separation
Enter the capital cost for sewer separation and the lifetime of the new construction.
Exclude Sewer Separation
~^]to exclude sewer separation as c
management option, enter -9.
Capital cost for sewer separation
5000
$/MGD
Lifetime of new construction
35
yrs
In CSO page Step 2, you can specify whether or not offline storage or sewer separation are available
management options for minimizing CSO events. If offline storage is an available management option,
you must enter the O&M cost of using the offline storage and its maximum capacity in CSO page
Step 2A. Similarly, if sewer separation is an available management option, you must enter the capital cost
for sewer separation and the lifetime of that new construction in CSO page Step 2B. Costs related to
offline storage management or sewer separation may be found in project-specific feasibility or evalution
reports (such as Washington State's King County Comprehensive CSO Control Program Review [2011]
or the CSO Control Program Reevaluation by the Narragansett Bay Commission [2017]) or in guidance
from the EPA (such as the Impacts and Control of CSOs and Sanitary Sewer Overflows [SSOs] Report
to Congress (2004) or CSO Management Fact Sheets [1999]).
If either offline storage or sewer separation are not available management options, you must enter "-9"
in the appropriate exclusion input field. Other management options that are not present on the CSO page
include storniwater management BMPs (land use "managed" sets) and additional capacity at the WWTP
(Infrastructure page).
52
-------
3. Model Setup and Runs
Capacity of the combined sewer
9
MGD
Finally, in CSO page Step 3, you must define the combined sewer system (CSS) by its capacity
(screenshot below) and the HRU areas that are serviced by the CSS (screenshot on next page of the user
guide). The areas specified for each HRU must not exceed the baseline HRU area. Additionally, since the
CSS routes flows from potable and nonpotable users to the WWTP, the CSS capacity should not exceed
the WWTP capacity.
HRU Area Serviced by Combined Sewer System
HRU ID
HRU Name
Area serviced by combined
sewer system [acres]
HRU1B
Forest, Sand & Gravel & Gravel
39.08
HRU2B
Open/non-residential, Sand & Gravel & Gravel
1.34
HRU3B
Medium-low density, Sand & Gravel
42.80
HRU4B
Medium-high density, Sand & Gravel
0.00
HRU5B
Commercial-industrial, Sand & Gravel
0.00
HRU SB
Agriculture, Sand & Gravel
0.00
HRU7B
Forest, Till & Fine-Grained Deposits
6.08
HRUSB
Open/non-residential, Till & Fine-Grained Deposits
1.09
HRU9B
Medium-low density. Till & Fine-Grained Deposits
12.32
HRU10B
Medium-high density. Till & Fine-Grained Deposits
0.00
HRU11B
Commercial-industrial, Till & Fine-Grained Deposits
1.20
HRU12B
Agriculture, Till & Fine-Grained Deposits
0.00
HRU13B
Cranberry Bog
0.00
HRU14B
Forested Wetland
0.00
HRU15B
Nonforested Wetland
0.00
HRU16B
Water
0.00
Select Return to Input and check the box next to CSO Module when this section is complete.
3.7 Flood Module
To include flood damage costs in the optimization of management costs, select Flood Module to navigate
to the Flood page. The Flood Module requires at least three sets of data for average daily streamflow,
return period, and flood damage. If you do not have these data, refer to Section 5 for information on
existing flood damage studies and conducting your own flood damage modeling using publicly available
data and software. Note that engaging the Flood Module creates substantially larger optimization
problems resulting in significantly longer model solve times.
6. Flood module. If you wish to consider the cost of flood damages in the total annual management costs, proceed to the flood module. ^ flood Module
3.8 Measured Streamflow and In-stream Concentrations
Press the Measured Data button to navigate to the Measured Data page. These data are used to create an
output graph showing both measured and modeled in-stream flow and concentration to assess the
accuracy of the model in reproducing measured flows and constituent concentrations. These data may be
7. Measured data.
If available, enter measured streamflow and water quality data. D '
.Measured Data J
53
-------
WMOST v3 User Guide
acquired from the U.S. Geological Survey49 or from the model from which you may have obtained
baseline hydrology data.
Measured
Measured In-
Concentration of
Date (mm/dd/yyyy)
Stream Flow (cfs)
TN (mg/L)
1/1/2002
45
1.60
1/2/2002
42
1.71
1/3/2002
40
1.79
1/4/2002
37
1.94
1/5/2002
36
1.99
1/6/2002
37
1.94
1/7/2002
56
1.28
1/8/2002
68
1.06
1/9/2002
67
1.07
1/10/2002
64
1.12
Select Return to Input and check the box next to Measured Data when
this section is complete.
0
Measured Data
49 http://waterdata.usgs.gov/nwis for streamflow data; https://water.usgs.gov/nawqa/sparrow/ for water quality data
54
-------
4. Optimization and Results
4. Optimization and Results
Unlike WMOST v2, which used a linear programming solver, WMOST v3 uses a mixed integer nonlinear
programming (MINLP) solver to find the least-cost solution to the optimization problem in WMOST. The
consideration of both water quantity and quality necessitated the switch from a linear solver to a nonlinear
solver to accommodate the increased complexity. In order to solve the optimization problem, WMOST
users can access the BONMIN (Basic Open-source Nonlinear Mixed INteger programming) (Bonami et
al. 2008) solver via the online NEOS server5" (Czyzyk et al. 1997; Dolan 2001; Gropp and More 1997).
This section first describes how to use the NEOS Server to run the optimization and retrieve your results,
and then it describes how to process and evaluate your results, including model calibration.
4.1 Running Optimization
RUN OPTIMIZATION
Scenario Name:
Optimize
Hybrid (B-Hyb)
Once all sections discussed in Section 3 are complete, you may run the
optimization model by returning to the Intro page and pressing the red
Optimize button. This will initiate the writing of the optimization file to your
project folder. Before using the Optimize button, you may enter a "Scenario
Name" to help you identify the scenario that is stored in the WMOST file. You
also must select the solver algorithm you would like to use. The algorithm
"Hybrid (B-Hyb)" is the default. Refer to the Theoretical Documentation for
guidance on selecting the proper solver algorithm. For the majority of users, the default algorithm is
preferred. The Intro page will display again once the optimization files have been written.
When you press the Optimize button, three optimization files are written by WMOST and saved to the
WMOST project folder:
• Wmodel.mod - model file with variable definitions and
constraints
• Wdata.dat - data file with parameter values
• Wcommand.amp - command file defining optimization
specifications
After locating the optimization files, navigate to the NEOS Server
BONMIN site51. On this site, you will see four buttons for uploading
the model optimization files. Upload the three files created by the
Model File
Enter the location of the AM PL mo
-------
WMOST v3 User Guide
an update when your model run is complete (screenshot on left). If you do not include your email, you
can instead access your results using the job number and password provided by NEOS when the model
optimization run is submitted. Note that there is an option to run your model as "Short Priority" or "Dry
run". Users should not select these options because they provide results that cannot be processed by the
Results Module. After the optimization files have been selected, press Submit to NEOS to initiate your
model run. Most model runs take about 10-15 minutes to solve, but some model runs may take up to eight
hours. The optimization time will depend on the complexity of the model and the model time period. The
NEOS Server imposes a limit of eight hours on solve times so results will not be provided if the model
takes longer than eight hours to solve.
After you submit the model run, the NEOS page will reload and provide you with a job number,
password, and the job queue. The job number and password can be used to view the job queue, view job
results (after optimization is complete), or kill/dequeue a job52. The current page may reload again after a
few minutes without the job queue displayed. You can either keep this page open or close out as you wait
for the solver to finish.
Once you receive an email indicating your model run has completed, you can view the optimization
results in the following ways:
1. If you've kept the job number and
password page up, you can refresh
this page.
2. You can input the j ob number and
password on the NEOS Admin
site52, which is also provided in the
results email. Select "View Job
Results" to view the optimization
results.
To run the Results Module in WMOST, you must copy the optimization results into a new text file. First,
open a text editor, such as Notepad. Next, use CTRL+A to select all of the optimization results text on the
web page. Finally, copy the selected text and paste it into the text editor. Save the file with a name that
will help you identify the scenario and save it to your WMOST project folder.
4.2 Evaluating Results
After you save your optimization results, you can now run the Results Module
to process and display results in WMOST. Navigate to the Intro page, and
press the red Process Results button. This button will display a File Explorer
dialog box. Navigate to your optimization results file and select it to initiate the
Results Module. The Results Module may take 1-15 minutes to run depending on the length of your
time period. Users should refrain from using their computer's copy function while the Results Module is
processing because it is used by the Results Module macros and may affect the results outputs.
52 Users can enter the job number and password on the NEOS Server at https://neos-server.org/neos/admin.htnil
Enter the job number and the password of the job you wish to kill/view.
You can leave these blank if viewing the queue.
Enter the job number
Enter the password for job:
© View Job Queue
® View Job Results
© Kill or Dequeue Job
submit
Process Results
56
-------
4. Optimization and Results
After running the Results Module, WMOST provides four outputs:
• A summary table of management practices and associated costs that met specified goals
(e.g., minimum demand, minimum in-stream flow) with the least cost on the Results page
• A time series table of flow, loadings, and concentrations variables on the Adv_Results page
• Scenario log file containing the scenario input data and results for analysis in ScenCompare53
• Four graphs displaying modeled and measured in-stream flow data, including:
o Modeled in-stream flow and baseflow compared with user-specified measured in-stream flow
o Modeled in-stream flow and baseflow and user-specified minimum and/or maximum in-
stream flow targets (if applicable)
o Modeled in-stream concentration compared with user-specified measured in-stream
concentration
o Modeled surface water or reservoir concentrations or loadings and user-specified minimum
and/or maximum surface water or reservoir concentrations or loadings targets (if applicable)
Results represent estimated conditions at the end of the planning horizon if all management practices
were implemented. For example, the modeled in-stream flow and baseflow are estimated to occur if
recommended management practices are implemented and human demand is at the projected rate input by
the user with the expected weather patterns (i.e., the user-input runoff and recharge rates). The flows over
the modeling period represent estimated flows over a variety of potential weather conditions represented
by the years in the modeling period. The length of the modeling period and the variety of climate
scenarios it represents determine the robustness and sustainability of the solutions recommended by the
model.
Results are most meaningful if compared relative to results from a simulation run (Section 2.1) and other
optimization scenarios. In addition, performing sensitivity analyses is highly recommended especially for
input data with least certainty to further determine the robustness of results (Section 6). By varying the
input data, you can determine the robustness of results over a variety of potential climate and
development scenarios that may occur by the end of planning period.
To view the summary table of results, press the Results Table button on the
Intro page to display the management decisions and associated costs. Capital
and O&M costs are presented separately in WMOST v3. Some facilities or
management practice may only have a capital cost or only have O&M costs due to the nature of the
selected management practice(s).
Excerpts from the summary table of results are as follows:
53 WMOST ScenCompare is an external MS-Excel application designed to view and compare WMOST scenario results. The tool
and instructions for its use are available from the WMOST website. Refer to the tool's instructions and Section 6 of this
document for more information about the tool's use and its capabilities.
57
-------
WMOST v3 User Guide
RESULTS
Due to solver precision, there may be neglible changes in HRU areas that round to zero displayed as 0 or (0).
ANNUALIZED COSTS
(million $/yr)
Return to Intro j
All Management Practices (including penalty and flood)
$0.7
ANNUALIZED REVENUES
(million $/yr)
Water Revenue
$8.9
Wastewater Revenue
$14.0
MANAGEMENT PRACTICES Quantity | Units | Annual Sub-Costs ($/yr)
Demand Management
Consumer Rate Change
0
%
$0
Direct Demand Reduction
0.00
MGD
$0
Land Conservation | 0 | Acres | $0
Infrastructure
New Construction Costs (add on or new facility)
Operations and Maintenance Costs
Total Costs
Quantity
Units
Annual Sub-Costs ($/yr)
Quantity
Units
Annual Sub-Costs ($/yr)
Annual Cost ($/yr)
SW Pumping
0.00
MGD
$0
7,198.53
MG
$266,274
$266,274
GW Pumping
0.00
MGD
$0
0.00
MG
$0
$0
Reservoir/ Surface Water Storage
0.00
MGD
$0
NA
MG
$0
$0
WaterTreatment Plant
0.00
MGD
$0
7,198.53
MG
$0
$0
Potable Distribution System Repair
0
% Leaks Fixed
$0
NA
NA
$0
Wastewater Treatment Plant
0.00
MGD
$0
1,045.19
MG
$197,830
$197,830
Infiltration Repair
0
% Leaks Fixed
$0
NA
NA
$0
Interbasin Transfer of Water
0.00
MGD
$0
0.00
MG
$0
$0
Interbasin Transfer of Wastewater
0.00
MGD
$0
1,059.08
MG
$200,378
$200,378
To view the time series table of advanced results, select the Advanced Results
button on the Intro page to display the flow, loadings, and concentration time
series. The Advanced Results table provides time series of the model decision
variables. Refer to the theoretical documentation for variable definitions.
An excerpt from the hydrology and water quality sections of the advanced table of results are below:
All flows are MG/time step.
,i. i x Return to Input
All volumes are MG at that time step.
Runoff
Total
SW Balance
Error
Date
(mm/dd/yyyy)
Runoff
7,614.86
Surface Water Balance
0.000
QRu
QRuStS
QRuCS
QRu_Total
QStSSw
QExtSw
QPtSw
QGwSw
QWwtpSw
QWrfSw
QSwRes
DQSwWtp
DQSwAsr
QSwPt
SW Balance
1/1/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
12.780
1.202
0.000
13.982
0.000
0.000
0.000
0.000
1/2/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
12.667
1.202
0.000
13.869
0.000
0.000
0.000
(0.000)
1/3/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
12.375
1.202
0.000
13.577
0.000
0.000
0.000
(0.000)
1/4/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
11.974
1.202
0.000
13.176
0.000
0.000
0.000
(0.000)
1/5/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
11.538
1.202
0.000
12.740
0.000
0.000
0.000
(0.000)
1/6/2002
0.185
0.000
0.000
0.185
0.000
0.000
0.000
10.979
1.202
0.000
12.181
0.000
0.000
0.000
(0.000)
1/7/2002
29.070
0.000
0.127
29.197
0.000
0.000
0.000
10.327
1.328
0.000
11.656
0.000
0.000
0.000
0.000
1/8/2002
0.488
0.000
0.002
0.490
0.000
0.000
0.000
19.215
1.204
0.000
20.418
0.000
0.000
0.000
(0.000)
1/9/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
24.490
1.202
0.000
25.692
0.000
0.000
0.000
(0.000)
1/10/2002
0.000
0.000
0.000
0.000
0.000
0.000
0.000
26.240
1.202
0.000
27.441
0.000
0.000
0.000
(0.000)
All loadings are lbs/time step (denoted by an "L").
All concentrations are mg/L at that time step (denoted by an "X").
SW Loads
Balance Error
Water Quality Variables
0.000
LRul
LUseNpSewerl
LStSSwl
LExtSwl
LPtSwl
LGwSwl
LWwtpSwl
LWrfSwl
LSwl
LSw Balance
0.000
0.000
0.000
0.000
3.302
0.000
12.112
0.000
15.413
(0.000)
0.000
0.000
0.000
0.000
3.302
62.013
12.112
0.000
77.426
(0.000)
0.000
0.000
0.000
0.000
3.302
87.517
12.112
0.000
102.930
0.000
0.000
0.000
0.000
0.000
3.302
110.643
12.112
0.000
126.056
(0.000)
0.000
0.000
0.000
0.000
3.302
131.906
12.112
0.000
147.320
0.000
0.000
0.000
0.000
0.000
3.302
151.278
12.112
0.000
166.692
(0.000)
Advanced Results
58
-------
4. Optimization and Results
Select the Compare to Measured & Target Flows button on the Intro page
to display the two hydrologic flows graphs:
• Graph comparing measured in-stream flow to modeled in-stream
flow and baseflow
• Graph comparing modeled in-stream flow and external outflow to
the corresponding streamflow targets. If you did not set any
streamflow targets, this target graph is not created; and thus is not
displayed.
Select the Compare to Measured & Target Water Quality button on the Intro page to display the two
water quality graphs:
• Graph comparing modeled in-stream concentrations to user-specified in-stream concentrations
• Graph comparing the water quality targets to their corresponding water quality flows. If you did
not set any water quality targets, this target graph is not created; and thus is not displayed.
Results may be either printed from the Excel interface with the same options as any Excel file or copied
and pasted into Word or other text editing applications.
4.3 Calibration Module
If you are in the process of calibrating your WMOST model, you may want to
employ the Calibration Module to help analyze your simulation results and
compute statistics for goodness-of-fit between measured and modeled in-stream
flow and concentrations. To use this module, press Calibration Module on the
Intro page to navigate to the Calibration page.
At the top of this page, you will see two options for running the Calibration Module:
• Process calibration statistics before processing the results -before using the Results Module by
pressing the Process Calibration button
• Process calibration statistics after processing the results54—after using the Results Module by
pressing the Calibration Statistics button.
Therefore, if you already ran the Results Module with your simulation results, you can quickly compute
calibration statistics using Calibration Statistics under option B. If you are analyzing multiple calibration
runs and do not care to have the full suite of results viewing options, you can use Process Calibration
under option A to import a new results file and compute relevant statistics. This option will only run the
results routines that are necessary for producing calibration statistics, thus expediting the calibration
process.
54 Calibration statistics are not automatically processed by the Results Module.
Compare to Measured
& Target Water Quality
Compare to Measured
& Target Flows
Calibration Module
59
-------
WMOST v3 User Guide
ClearCalibrationRuns
This procedure calculates the model statistics forthe
results that were last processed with the results routine.
B. Process Calibration Statistics After Process Results
Calibration Statists
A. Process Calibration Statistics Before Process Results
This procedure runs the processes that are necessary for
calculating statistics (without running the full routine).
Process Calibratioi
Return to
input J
Hydrology and Loadings Calibration Module
Follow the step-by-step directions to process goodness-of-fit statistics for a calibration run.
After you use one of the calibration processing options, the Calibration Module copies your measured and
modeled in-stream flow and concentration time series data to the time series table on the Calibration
page. With each additional
calibration run, the module
will insert new columns
containing your modeled
in-stream flow or
concentration in the time
series tables and new rows
containing computed
goodness-of-fit statistics in
the statistics summary
tables.
The screenshot to the left shows the time series table after three calibration runs have been processed by
the module. You can use these tables to compare your in-stream flow and concentration results on this
page or construct a graph that compares measured data to multiple modeled results run at once (as
compared to the Measured Flows graphs, which only compare measured data to a single results run).
In the statistics summary table (see above), you can see five different goodness-of-fit statistics computed
based on your measured and modeled flows. These statistics include:
Hydrology Calibration
Run ID
Run Name
Objective Cost
Average
Measured Flow
NSE Value
R2 Value
Relative
Percent Error
Average Bias
Median Bias
1
Flow Run#l
664804.62
155.5283759
0.415 217S8
0.536199378
68.76265836
38.21449443
24.57075386
2
Flow Run#2
664481.66
155.5283759
0.417517021
0.536255051
67.69767941
37.56779065
24.15494307
3
Flow Run#3
664481.66
155.5283759
0.415974096
0.536214412
68.86602764
38.07161803
24.4788887
• Nash-Sutcliffe Efficiency (NSE), a statistic used to assess the predictive power of hydrological
models (NSE values range between negative infinity and 1. An NSE value of 1 corresponds to a
perfect match and a negative NSE value indicates that the measured average is a better predictor
than the model results.)
• R2, a statistic used to measure how close the data are to the fitted regression line (R2 values range
between 0 and 1. An R2 value of 1 corresponds to a perfect match.)
• Relative Percent Error, a statistic used to analyze the precision of the data
1
Hydrology Calibration
Measured In-Stream
In-Stream Flow,
In-Stream Flow,
In-Stream Flow,
Date
Flow (cfs)
Run#l
Run#2
Run#3
1/1/2002
45
142.421
141.8139546
141.795
1/2/2002
42
133.760
132.6519386
133.140
1/3/2002
40
125.308
124.1613666
124.725
1/4/2002
37
117.228
116.0527518
116.675
1/5/2002
36
109.673
108.474354
109.134
1/6/2002
37
102.889
101.6748454
102.354
1/7/2002
56
201.719
200.5256586
201.214
1/8/2002
68
118.296
117.0773799
117.798
1/9/2002
67
127.371
126.1318069
126.900
60
-------
4. Optimization and Results
• Average Bias and Median Bias, statistics used to evaluate the difference between the modeled
values and the measured values (average bias computes the average difference between modeled
and measured data, while median bias computes the median of the same calculation)
In addition to comparing measured streamflow and concentrations to the WMOST results, users should
also compare the costs generated by the simulation run. The costs related to operating the system during
the baseline period should accurately reflect the costs borne by the utility during the same period. For
example, if WMOST estimates WTP costs of $250,000 per year, then the user should verify that the
utility spent an equivalent amount on WTP operation. If that is not the case, the unit costs for operation of
the WTP may be inaccurate.
61
-------
WMOST v3 User Guide
5. Flood Damage Modeling with HAZUS55
HAZUS-MH is used to generate the flooding cost curve data which are entered into the WMOST v3
Flood Module table. HAZUS-MH is a multi-hazard loss estimation tool developed by the Federal
Emergency Management Agency (FEMA) which provides a nationally applicable and standardized
methodology for estimating flood (and earthquake) losses on a regional scale. HAZUS is designed to run
with ESRI's ArcMap GIS. The Flood Model is designed with three levels of analysis, from Level I using
the default HAZUS-supplied building stock and flood modeling procedures to Level III which requires
extensive hydraulic modeling and high quality building data56. The following steps will guide the user
through methodology to determine the 100-year flood depth grid using data from the FEMA National
Flood Hazard Layer and to create 10, 50 and 500-year grids. Additionally, this guide will assist users in
creating a user-defined building inventory from the available data to improve upon existing default
settings in HAZUS and perform a Level II analysis. By running several flood levels, the user is then able
to create a flood depth (return interval)-damage curve for use as input into the WMOST tool.
Note: This example uses data for Plymouth County in Massachusetts. Some data sources may not be
available in other states or regions.
5.1 Data Needed
• FEMA National Flood Hazard Layer (NFHL) data
o Data can be downloaded for the entire state (where available) or by county.
(https ://msc .fema.gov/portal/advance Search)
• Elevation data-Accuracy of solutions may vary with resolution of input data. HAZUS can be run
either with 10- or 30-meter resolution data from USGS or with finer resolution LIDAR data if
available for the area of interest.
o National Elevation Data can be obtained at the National Elevation Dataset from the
National Map (http://viewer.nationalmap.gov/viewer/).
o LiDar data can be found and downloaded from NOAA Digital Coast website
(http://coast.noaa.gov/digitalcoast/data/coastallidar) or from state specific GIS websites
where available.
It is important that the ground elevation grid and the FEMA flood elevations are in the same vertical-
projection (NAV88).
The generalized method to creating a flood depth grid for any region is to create a flooding surface using
available information and subtract the ground elevation. Areas where the flood surface minus the ground
elevation is positive represent flooded regions. Areas where the flood surface minus the ground elevation
is negative represent non-flooded areas.
55 HAZUS Level 2 Site Specific Flood Model: FEMA Region VIII Standard Operating Procedure for Riverine Flood Hazard and
Site Specific Loss Analysis, prepared by Jesse Rozelle, Austen Cutrell, Doug Bausch, and H.E. Longenecker.
56 Multi-hazard Loss Estimation Methodology Flood Model HAZUS-MH, Users Manual, FEMA
(www. fema. go v/plan/prevent/hazus).
62
-------
5. Flood Damage Modeling with HAZUS
5.2 Creating the 100-Year Flood Depth Grid from FEMA NFHL Data
These preprocessing methods require the use of ArcMap to maintain compatibility with FEMA's
HAZUS tool.
1. Open ArcMap.
2. Add the Base Flood Elevation (BFE) shapefile (S_BFE.shp) from the NFHL dataset to the map.
The shapefile has an attribute "ELEV" which is the Base Flood Elevation (BFE) at each section.
3. Add the Stream Profile Centerline and the Flood Hazard Area shapefiles from the
NFHL( S PROFIL BASLN slip and S FLD HAZ AR. shp).
Hd cat «• trotrt Srted
\ vv 4-
Qe5M& 6" •
(rjem
nuue-tn • _
frid OJB ii
- 0
= JO
¦ 0 1JH
a SB SJIDjfiJ*
m-
c":
^ ; Ml,Ml
* - A • O
U4 *|'0 1 1 J ^ - ' -
4. Create points at each vertex of the BFE lines (Data Management Tools»Feature»Feature
Vertices to Points).
IB Cartography Tools
l ( Conversion Tools
IB % Data Interoperability Tools
^ Data Management Tools
i Si %¦ Data Comparison
Si %• Database
Distributed Geodatabase
! IS %• Domains
+j Feature Class
: b% Features
^ Add XY Coordinates
\ Adjust 3D Z
Bearing Distance To Line
Check Geometry
*\ Copy Features
*\ Delete Features
Dice
Feature Envelope to Polygon
Feature To Line
Feature To Point
: Feature To Polygon
Minimum Bounding Geometry
*\ Multipart To Singlepart
A' Points To Line
Polygon To Line
Repair Geometry
\ Split Line at Point
\ Split Line At Vertices
Ar :T;.r Iboxj ^ Table Of Contents [
Jc y & c
*5 LI
B sjs
~ -MJtJ
63
-------
WMOST v3 User Guide
5. Using the point feature generated in Step 4, create the 100-year flood surface by inverse distance
weighting using the ELEV attribute (Spatial Analyst»Interpolation»IDW).
ArcToolbox
ffl ^ Editing Tools
(S"Q Geocoding Tools
IS ^ Geostatistical Analyst Tools
ffl Q Linear Referencing Tools
ffl ^ Multidimension Tools
ffl ^ Network Analyst Tools
ffl ^ Parcel Fabric Tools
ffl ^ Schematics Tools
ffl Q Server Tools
S ^ Spatial Analyst Tools
ffl^ Conditional
ffl %• Density
ffl Distance
Extraction
ffl %s Generalization
ffl Groundwater
ffl % Hydrology
S %• Interpolation
IDW
Kriging
Natural Neighbor
• Spline
Spline with Barriers
Topo to Raster
Topo to Raster by File
Trend
ffl Local
ffl Map Algebra
ffl %< Math
55 AtcTc-albex EMJ'ahl* 1 ; '.'cnrprts
» • £ £ n g a ' ***¦ • ~. ¦
Jclid t AC* ' t - I 'MOM -^33^5!! :•
0 »jo
H O mtUfiJ
J*1*' 6X
Vfi
% £
~
\
Nr °
^ _14M J-.
'••t % A l_. • A * * " / U ± • > * •
6. Subtract the ground surface elevations from the flood surface layer created in Step 5
(Map Algebra»Raster Calculator or Math»Minus) to determine a water depth gnd.
The resulting layer will have negative values where the ground surface is above the flooded
elevation (areas of no flooding) and positive values in flooded areas.
S3 Q Linear Referencing Tools .a.i
SI ^ Multidimension Tools
ffl ^ Network Analyst Tools
ffl ^ Parcel Fabric Tools
ffl Schematics Tools
ffl Q Server Tools
- Q Spatial Analyst Tools
ffl ^5 Conditional
ffl %• Density
£ %' Distance
Extraction
ffl %< Generalization
ffl Groundwater
ffl%, Hydrology
ffl Interpolation
ffl %• Local
S %• Map Algebra
Raster Calculator
B %. Math
C+3 % Bitwise
ffl %' Logical
ffl &• Trigonometric
\Abs
Divide
A, Exp
\ ExplO
\ Exp2
\ Float
I \lnt
\ LoglO
\Log2
^ Minus
\ Mod
Negate
\ Plus
Power
Round Down
Round Up v
¦^ArrTuulboj:::
64
-------
5. Flood Damage Modeling with HAZUS
7. Eliminate negative values using a conditional statement (SpatialAnalyst»Math»Logical
»Greater than Equal). Setting the flood elevation grid greater than zero will result in a true/false
condition where positive values will have a grid code of 1 and negative values will have a grid
code of 0.
® iQl P.tcri Fnbnr Tnnk
a Q loote
Si Q Swvar Toufe
- 3pat»ai Analyst Toofe
3 ^ Cumftiuwl
IX r«*K*y
*. %
a %< Eiti«tiun
® GMWHtaattan
i> %¦ brouxtattr
a %¦ HyA'Juyy
8) 1n«rpi*km
* L«d
a %¦ M» Aijdjrt
U % Ma*h
it. %• Bf-rtlMJ
B
Uootesnflfvd
'r\ RaoipjtnOr
*\ ttooleanXOr
^CwitiulwialA/d
^ Cai&wtaVi Of
*\ CwitmaKosi XOr
lo
* _ 'oiMtw Tlun
\ Crnanv Ttun Fqu.i1
inort
U-ISW
Usslhan
LesslSeotoiMl
Nut Equ4
Over
13 Tngnnnmrtrtf
AC 05
ACuiH
¦% A
3i£3sm-T«*wx: -:i *«*«*<
=;>
* m»thodt,mxd - ArcMsp - Arclnfo
Fte Edt View Ueetesart? !n«rt JeietMr, Cecfrocesdnq CuawiK Wrdows Met)
ii^ro :::: * •- * o & — ;
.liiBfi O x • • *- nan » k/i l'i
HA7U5RT- Oivwr*:- Owwtal- \ !&. N;
¦ i.
as.
T.ihlp Of Con»*rtt
- a SJ*<*Jl_RAVM
= a«j«
b a S.BFE
a O RtwfcAertlOO
¦
a (~1 ItawWwnlOO
a
» n S_PID_HAZ_W>
a ~ IbuKridlOO
Y+JB
p Hqh • 15.0605
Lew - 0.W365X
X a Srtrthaniuo
A I"! mrucjdniOQ
X ~ lA*Il»
3 CI rosidjt_2
Vdui
^ rtgh ! &H.761
ION! a7iB05
{!r5 I-aUecf Content*
aw«iQ- * - A ¦
-70-878 4?j043DanntfO«^**i
8. Detennine the flood extent boundary polygon by first converting the conditional raster created in
Step 7 to a polygon. Then, export polygons with a GRIDCODE=l to a new data layer delineating
the flood extent boundary.
, % »o g>» % »',
xafii- b
•us »• ';b
M JJfeWtlJAUV
CTIEj®
QES
~ BE
~son rai
GD
~ I_FID 1«>R
. i M
9. Mask the water depth grid (Step 6) by the flood extent boundary (Step 8) to create a flood depth
grid.
65
-------
WMOST v3 User Guide
Untitled - ArcMap - Arclnfo
BIB
® ~ grtrthanlOO
S3 ~ minusJdwlOO
IB ~ idwlOO
B CD malid_ft_2
Value
High : 634.761
ArcToolbox iT^ Table Of Contentsj i
Drawing' Pfc C°"i H ~ ' A ' 0
B ~ FloodExtentlOO
~ ~ floodpolygonlOO
~
® ~ 5_FLD_HAZ_AR
B 0 iiffHIWIfi'ii
Value
| High : 45.0803
' Low : -0.0626526
H? _ + -
File Edit View Bookmarks Insert Selection Geoprocessing Customize Windows Help
^gtgj]o ;;;; * ¦»
-------
5. Flood Damage Modeling with HAZUS
5.4 Creating Flood Depth Grids for the 10, 50 and 500-Year Events
The next set of steps demonstrate how to create a flood depth grid from the 10, 50 and 500-year data in
the published Flood Insurance Study books.
1. FEMA Flood Insurance Studies (FlS)are county-specific and can
be obtained from the FEMA Map Service Center
(www.msc.fema.gov). The flood profile graphs show flood
elevations along the centerline of the stream
(S PROFIL BASLN shp). The profiles show the elevation of the
100-year flood as well as the 10, 50, and 500-year floods. The
profiles also show locations of streets, elevation of the streambed
and other hydraulic structures.
2. For each stream in the study area, locate the profile plot in the FIS
along with the corresponding stream in ArcMap. Each stream has
both cross-section locations (S XS.shp) and Base Flood Sections
locations(SBFE.shp).
3. In the S BFEhe existing attribute ELEV represents the 100-year
base flood elevation. Add attribute fields to S_BFE.shp
representing the 10, 50 and 500-year flood. The attribute labeled
ELEV is the BFE. Although the SBFE.shp file is easily replaced, it is a good idea to make a
copy of this file to use as a working platform.
Table
Ei * H' frji ~ £ x
FloodElevation_5ections
SOURCE_CIT
500_YR
ELEV
50_YR
10_YR
A-
25023C FIS1
0
77
0
0
25023C FIS1
0
69
0
0
25023C FIS1
0
64
0
0
25023C FIS1
0
79
0
0
25023C FIS1
0
40
0
0
25023C FIS1
0
82
0
0
25023C FIS1
0
84
0
0
25023C FIS1
0
47
0
0
~
25023C FIS1
0
27
0
0
25023C_FIS1
0
31
0
0
25023C FIS1
0
42
0
0
V
<
25023C FIS1
0
16
0
0
M 4 9 ~
H ^ (0 out of 1376 Selected)
FloodElevation_Sections
ontents llH Tabjej
ligfrl ArcToolbox EH Table Of C
FLOOD
INSURANCE
STUDY
PLYMOUTH COUNTY,
MASSACHUSETTS
(ALL JURISDICTIONS)
-1
Federal Emergency Management Agency
67
-------
WMOST v3 User Guide
4. For each BFE line, locate the corresponding location on the profile plot and transfer
these elevations to the appropriate attribute field. The cross-section labels on the map correspond
to the cross-section labels across the bottom of the profile plot. Although the BFE lines are not
shown on the profile plot, their location can be easily estimated. Cross-section locations are NOT
the same as BFE locations
Table
FloodElevations
456 Polyline
(1 out of 561 Selected)
FloodElevation_Sections | S_PROFIL_BA5LN | FloodElevations
Arc!oolbox Table Of Contents j lUi Table!
5. Repeat this procedure for all section lines.
6. Once all elevations are determined, the methodology to create the 100-ylear flood grid can be
utilized to create flood depth grids for the 10, 50 and 500-year intervals.
5.5 Creating a Site Specific Building Inventory
To determine flood damage, FIAZUS assumes that all buildings are distributed evenly throughout a
census tract, hi order to get a more accurate assessment of the potential damage, it is helpful to build a
user-defined building inventory. To create a detailed building inventory, the following information is
necessary: structure location, foundation type, first floor height, building value, contents value, occupancy
type, design level and number of stories.
1. Create point locations of buildings within the floodplain. This can be accomplished in several
ways, depending on the type of available data and the amount of time and effort available to spend
on this step. The best data source is a shapefile of building footprints. If there is not a field labeled
Area, add a field and calculate the area of each building. If the building footprint data are not
available, parcel data can be used as well. For parcel data, the centroid of the parcel can be used as
a substitute for building location. If neither of these is available, it is possible to manually locate
each building from available orthoimagery. Only primary structures are necessary. Structures such
as garages, sheds and small out-buildings should be excluded from the dataset. Buildings smaller
than 400 square feet are often accessory structures. Aerial photographs such as the NAIP 1-meter
imagery can be helpful in determining building use.57 One can also perform a spatial join with the
building points and the parcel layer to determine parcels with more than one building to help
locate secondary, accessory structures on a property.
Available from https://gdg.sc.egov.usda.gov/.
68
-------
5. Flood Damage Modeling with HAZUS
*- methods.mxd - ArcMap - Arclnfo
File Edit View Bookmarks Insert Selection Geoprocessing Customize Windows Help
Editor
HAZU5-FIT' Riverine
Table Cf Contents
Layers
~ JOOyrftoatf*..! CCrrbifi
^ Layers
S ~ BldgPts_in_500yrFloodplain_100mbuff<
0 btructuw mer^s
¦ I
~ HoodMWtbUJ
Q 0 Structures_merge
B ~ FloodExtent500
S ~ 500yr_floodplain_buffer
GS ~ Zoning by General Use (Transparent)
Residential
Commercial
Industrial
Conservation
Other
3 0 NAIP\Massachusetts_2012_1 m_NC
|TI Zcnrig by 5Mi«alijse(7r arawrent.il
Bk PeiderCal
ComiwojI
' It&k&mI
C nnnv<4in
other
0 JiarpVMrfv-* I tisHu_?ni
__ -v,- nf ^
US Table Of Contents [§3 ArcToolbox
Drawing " ^ «! D-A-
•71 009
2. HAZUS needs several attributes for each building: occupancy class, first floor height above
ground level, design level, number of stories, building value and foundation type. These can
be obtained from a number of sources, such as tax assessor databases and zoning information.
Table
1 U - H - % Q X 1
1 BldgPts _in_500yrl
Floodplain_100
mbufferjjnder700sf
:_parcelinfoj
5lev_zoning
X
BLD_AREA
RESAREA
STYLE
STORIES
OCC_Class
FFH |
Foundation
HUM_ROOMS
E /v
2396
1804
Two Family
2
RES3A
2
4
11
1
6214
3532
Two Family
2
RES3A
2
4
9
95/
6458
3351
Conventional
1.75
RES1
2
4
9
98.6
2231
836
Ranch
1
RES1
2
4
4
1
3078
3078
ClubsA-odges
1
COM1
2
7
0
87 .S
2522
1530
Conventional
1.75
RES1
2
4
8
1
1976
973
Ranch
1
RES1
2
4
5
1
2630
1383
Conventional
1.75
RES1
2
4
6
1
2780
1008
Ranch
1
RES1
2
4
5
1
6010
3301
Apart OS
2
RES3C
2
4
17
1
6356
2128
Clubs.'Lodges
2
COM1
2
7
0
94.7
2559
1280
Conventional
1.5
RES1
2
4
6
1
2314
1276
Colonial
1.75
RES1
2
4
6
1
2350
1160
Raised Ranch
1
RES1
2
4
7
3592
2357
Raised Ranch
1
RES1
2
4
7
1
<
3583
1945
Cape Cod
1.75
RES1
2
4
4
V
¦I
1 H i 0 ~ M
[Hi ^ (0 out of 9919 Selected)
BldgPtsJn_500yrFloodplain_100rnbuffer_under700sf _parcelinfo_elev_zoning
| EH Table Of Contents 1l^J ArcToolbox J||l Table;
Fields should be created in the attribute table for each of these necessary attributes.
69
-------
WMOST v3 User Guide
3. HAZUS has specific values for occupancy class and foundation type and these must
correspond exactly in order to map correctly. The HAZUS Technical Manual58 has various
default values to aid in assigning these attributes. In New England, 81% of residential
structures have basements, so all residential structures were assumed to have a basement type
foundation with the first floor height 4 feet above the existing ground. Commercial and
industrial structures were assumed to have a slab type foundation with first floor height one
foot above existing ground. Once completed, this attribute table should be exported to a
database table and properly formatted for use in HAZUS. The HAZUS Users Manual gives
detailed instructions to import the user-specified inventory.
| H UDFJMecklenburgJSC : Table
.|n|x
Field Name
Data Type
Description
ID
Text
Field Size: 8
Name
Text
Field Size; 40
Address
Text
Field Size; 40
City
Text
Field Size; 40
State
Text
Field Size: 2
ZipCode
Text
Field Size; 10
Contact
Text
Field Size; 40
Phone
Text
Field Size; 14
Occupancy
Text
Field Size; 5
BldgType
Text
Field Size; 15
Cost
Currency
Field Size;
YearBuilt
Number
Field Size; Integer
Area
Number
Field Size; Single
NumStories
Number
Field Size; Byte
DesignLevel
Text
Field Size; 1
FoundationType
Text
Field Size; 1
FirstFloorHt
Number
Field Size; Double
ContentCost
Currency
Field Size;
BldgDannageFnld
Text
Field Size; 10
ContDamageFnld
Text
Field Size; 10
InvdamageFnld
Text
Field Size; 10
FloodProtection
Number
Field Size; Long Integer
ShelterCapacity
Number
Field Size; Integer
BUPower
Yes/No
Field Size:
Longitude
Number
Field Size: Decimal (11,6)
Latitude
Number
Field Size: Decimal (11,6)
County
Text
Field Size; 40
Comment
Text
Field Size: 40
d
E
Proper formatting schema for database table in Access
The following figure shows typical output from HAZUS for user-defined facilities. Damages are listed by
occupancy type, damage percentage, building loss cost, content damage percentage and content loss cost.
The figure shows only building-related damages but the user may wish to include estimates of other
flood-related damages from HAZUS output as well.
58 HAZUS MR4 Technical Manual, Department of Homeland Security, Federal Emergency Management Agency, Mitigation
Division, Washington, D.C. (http://www.fema.gov/plan/prevent/hazus/)
70
-------
5. Flood Damage Modeling with HAZUS
Table ~ X
El * ill * % SSi
UserDefinedFacilities X
OccupancyC
Controllin
BIdgDmgPct
BldgLossUS
ContDmgPct
ContentLos
Inventory!.
AnalysisOp
RES1
R
66.358566
92039.331042
60
41610
0
0
RES1
R
69.112408
102493.701064
60
44490
0
0
RES1
R
69.945282
106946.336178
60
45870
0
0
RES1
R
44.59601
84821.61102
42.39734
40319.87034
0
0
~
RES1
R
15.103155
18667.49958
9.765048
6034.799664
0
0
RES1
R
50
60200
49.759718
29955.350236
0
0
RES1
R
33.106655
53103.07462
26.927986
21596.244772
0
0
RES1
R
56.994598
0
54.991897
0
0
0
RES1
R
20.483168
28041.456992
19.483168
13336.228496
0
0
RES1
R
57.004348
68918.256732
55.006522
33251.442549
0
0
RES1
R
16.967435
39262.64459
12.747896
14749.315672
0
0
RES1
R
36.476012
59091.13944
31.095015
25186.96215
0
0
RES1
R
41.96305
63951.6882
37.75566
28769.81292
0
0
COM2
R
17.798485
49853.556485
60.59697
169732.11297
186538.11297
0
RES1
R
19.404114
27223.971942
16.404114
11507.485971
0
0
IN02
R
45.388669
196169.827418
73.796223
478420.913709
336235.275806
0
RES1
R
56.545074
105286.927788
54.317611
50569.695841
0
0
<
£
III
J ~
14 4 1 ~ M
^ (0 out of 1108 Selected)
UserDefinedFacilities
Typical output from HAZUS for user-defined facilities (buildings).
For each HAZUS flood depth grid corresponding to a unique flood recurrence interval, the user will need
to sum the flood-related damages and enter these into the flood cost table on the Flood page.
Average Daily
Streamflow (cfs)
Return Period
(years)
Flood Related
Damages ($)
Flood cost curve in WMOST Flood Module
71
-------
WMOST v3 User Guide
6. User Tips
The following tips are provided for troubleshooting, interpreting results and modeling specific situations
or scenarios.
• If the objective cost section of the results does not contain feasible results, the Results Module
informs you that there was an optimization error and what type of error was reported by the NEOS
Server. This means the scenario run was infeasible, and that the specified management goals and/or
continuity constraints could not be met with the user-provided input data. Refer to the Theoretical
Documentation for constraints that are defined in the optimization model. You may need to adjust
your management goals or identify erroneous input data. Future versions of the model will support
identifying constraints and data that contribute to infeasible solutions.
• If you want to test the effect of a management option but the model is not selecting it, you can enter
""0" for cost. You can also adjust the cost of a management practice to see the cost at which that
practice is selected by the model and, therefore, assessed as cost effective.
• To exclude replacement costs for existing infrastructure, set the remaining lifetime to be greater than
the planning period. This tells the model that the infrastructure does not need replacement within the
planning period and the model will not calculate replacement costs. It will only calculate capital costs
for new or additional capacity of infrastructure and O&M costs.
• A "calibration run" is advised before optimization runs to determine the accuracy of WMOST in
modeling in-stream flow relative to measured data or data from the detailed watershed simulation
model from which RRRs may have been acquired. Calibration runs can be used to ensure that the
WMOST model closely matches the hydrologic and water quality conditions of your watershed. They
can also be used to error check constraint and target values to ensure that they are feasible Case study
applications in the WMOST User Guide for Versions 1 and 2 describe the process for performing a
"simulation run" with WMOST
• If your model runs are infeasible, review all constraints, targets, and initial values. The constraints or
targets may be too limiting and preventing the optimization from finding a solution. Furthermore, if
initial concentrations or volumes differ in orders of magnitude from the average concentrations of
volumes calculated by the model, the initial values should be adjusted so that the optimization
solution is running the optimization from a reasonable starting point.
• Avoid groundwater volumes near zero as this can lead to infeasible model runs. In calibration, set the
initial groundwater volume near the maximum in wet years in order to get a reasonable low volume
estimate. Low flow accuracy is critical for effluent dominated streams, especially when applying
loading or concentration targets, so consider potential influence of groundwater volume on
concentrations during low flow periods.
• If your model cannot meet the maximum daily load target specified, consider the maximum loads
during the times of greatest biological activity. Separate out non-point source loaddings from point
source loadings to determine the contribution of point source loadings to total stream loads and to
72
-------
6. User Tips
determine what level of nonpoint source pollutant load reduction is likely to be feasible based on
application of BMPs.
• Sensitivity analyses should be performed with the most uncertain input data. For example, if the price
elasticity for industrial water use is most uncertain, then the model should be run multiple times over
a range of potential values as follows:
1. Starting with the best estimated value, determine the range of potential values e.g., -0.5 with
a potential range of -0.2 to -0.7.
2. Run the model with the same input data varying only the price elasticity for industrial water
use. For example, run the model five times with values of -0.2, -0.3, -0.5, -0.6, and -0.7.
3. Save the results of each run, that is, either use the "save as" function in Excel to save a
different version of the file/model with each run or copy and paste the results tables into
a separate Excel file.
4. Determine the effect of the price elasticity on results. Does it change whether demand
management via pricing is implemented? Does it change the mix of other management
options? How does it change the total annual cost?
Ideally, change only one of the input data values at a time at first so that you can determine the individual
effect of each variable. Once you know the individual effects and you have more than one uncertain input
data value, you may want to run the model varying more than one data value at a time to determine their
combined effects. You may consider "worst" and "best" case scenarios. For example, vary all uncertain
data in the direction of higher costs to determine the worst case scenario for total cost if all uncertain data
were to be truly in the higher cost direction. Alternatively, run the highest cost for a specific management
practice to determine the whether it is still a cost effective practice that is chosen by the model and,
therefore, a "no regrets" option. For more guidance, please refer to EPA's "Sensitivity and Uncertainty
Analyses" website59. You may also employ WMOST ScenCompare to facilitate sensitivity analyses using
the scenario log file produced by the Results Module. Refer to the ScenCompare User Guide for detailed
instructions regarding the use and capabilities of ScenCompare.
• Trade-off analyses are similar to sensitivity analyses but with a different purpose. With trade-off
analyses the question may be "How does cost change with increasing in-stream flow? Is it linear?
Are there points at which the increasing investment in management practices (i.e., total cost) results
in less increase in in-stream flow than the first $X?" To answer these questions, follow the same steps
as for the sensitivity analysis. For the in-stream flow example, increase the minimum in-stream flow
requirement with each run and record the results. Then, examine the effect of this increase on the
combination of management practices that are suggested and the total costs and revenues. A trade-off
curve may be created by plotting total cost versus percent of in-stream flow requirement to create
a visual understanding of the trade-off and results. An example of the process is shown in the case
study of Danvers and Middleton, MA.
59 https://www.epa.gov/modeling/sensitivity-and-uncertainty-analyses-training-module
73
-------
WMOST v3 User Guide
7. References for Watershed Simulation Models Incorporated into
WMOST Hydrology and Loadings Databases
AQUA TERRA Consultants, and HydroQual, Inc. 2001. Modeling Nutrient Loads to Long Island Sound
from Connecticut Watersheds, and Impacts of Future Buildout and Management Scenarios. Prepared
for CT Department of Environmental Protection. Hartford, CT. 138 pg, plus CD.
Barbara, J.R. 2007. Simulation of the Effects of Water Withdrawals, Wastewater-return Flows, and
Land-use Change on Streamflow in the Blackstone River Basin, Massachusetts and Rhode Island: U.S.
Geological Survey Scientific Investigations Report 2007-5183, 98 p.
Barbara, J.R., and Sorenson, J.R. 2013. Nutrient and Sediment Concentrations, Yields, and Loads in
Impaired Streams and Rivers in the Taunton River Basin, Massachusetts, 1997-2008: U.S. Geological
Survey Scientific Investigations Report 2012-5277, 89 p., available at
http://pubs.usgs.gov/sir/2012/5277/.
Barbara, J.R., and Zarriello, P.J. 2006. A Precipitation-runoff Model for the Blackstone River Basin,
Massachusetts and Rhode Island: U.S. Geological Survey Scientific Investigations Report
2006-5213, 85 p.
Bent, G.C., Zarriello, P.J., Granato, G.E., Masterson, J.P., Walter, D.A., Waite, A.M., and Church, P.E.
2011. Simulated Effects of Water Withdrawals and Land-use Changes on Streamflows and
Groundwater Levels in the Pawcatuck River Basin, Southwestern Rhode Island and Southeastern
Connecticut: U.S. Geological Survey Scientific Investigations Report 2009-5127, 254 p., available
at http://pubs.usgs.gOv/sir/2009/5127.
Charles River Watershed Association and Numeric Environmental Services. 2011. Total Maximum Daily
Load for Nutrients in the Upper/Middle Charles River, Massachusetts. Massachusetts Department
of Environmental Protection, Division of Watershed Management, Worcester, MA. Report Number
MA-CN 272.0.
Donigian, Jr., A.S., and J.T. Love. 2002. The Connecticut Watershed Model - Tool for BMP Impact
Assessment in Connecticut. Presented at WEF-Watershed 2002, February 23-27, 2002. Ft. Lauderdale,
FL.
U.S. EPA. 2013. Watershed Modeling to Assess the Sensitivity of Streamflow, Nutrient, and Sediment
Loads to Potential Climate Change and Urban Development in 20 U.S. Watersheds (Final Report). U.S.
Environmental Protection Agency, Washington, DC, EPA/600/R-12/058F, 2013.
U.S. EPA. 2017. Opti-Tool Version 2. U.S. Environmental Protection Agency, Region 1, 2017.
Zarriello, P.J. and K.G. Ries, III. 2000. A Precipitation-Runoff Model for Analysis of the Effects of
Water Withdrawals on Streamflow, Ipswich River Basin, Massachusetts. U.S. Geological Survey
Water Resources Investigations Report 00-4029.
Zarriello, P.J., Parker, G.W., Armstrong, D.S., and Carlson, C.S. 2010. Effects ofWater Use and
Land-use on Streamflow and Aquatic Habitat in the Sudbury and Assabet River Basins, Massachusetts.
U.S. Geological Survey Scientific Investigations Report 2010-5042, 160 p.
74
-------
8. User Guide References
8. User Guide References
American Rivers. 2010. Putting Green to Work: Economic Recovery Investments for Clean and Reliable
Water. American Rivers, Washington, D.C.
American Water Resources Association (AWRA). 2012. Case Studies in Integrated Water Resources
Management: From Local Stewardship to National Vision. American Water Resources Association
Policy Committee, Middleburg, VA.
Bonami, P., Biegler, L.T., Conn, A.R., Cornuejols, G., Grossman, I.E., Laird, C.D., Lee, J., Lodi, A.,
Margot, F., and Waechter, A. 2008. An Algorithmic Framework for Convex Mixed Integer Nonlinear
Programs. Discrete Optimization 5(2), 186-204.
Czyzyk, J., Mesnier, M.P., and More, J.J. 1998. The NEOS Server. IEEE Journal on Computational
Science and Engineering 5(3), 68-75.
Dolan, E. 2001. The NEOS Server 4.0 Administrative Guide. Technical Memorandum ANL/MCS-TM-
250, Mathematics and Computer Science Division, Argonne National Laboratory.
Gropp, W. and More, J.J. 1997. Optimization Environments and the NEOS Server. Approximation
Theory and Optimization, M.D. Buhmann and A. Iserles, eds., Cambridge University Press, p 167-182.
King County Department of Natural Resources and Parks. 2011. Comprehensive Combined Sewer
Overflow Control Program Review: Cost Estimating Methodology for CSO Control Faciltiies.
Waterwater Treatment Division, Technical Memorandum 620.
MA EAA. 2012. Massachusetts Sustainable Water Management Initiative Framework Summary
(December 21, 2015); http://www.mass.gov/eea/agencies/massdep/water/watersheds/sustainable-water-
management-initiative-swmi .html.
Maurer, E.P., G.M. O'Donnell, D.P. Lettenmaier, and J.O. Roads, 2001: Evaluation of the Land Surface
Water Budget in NCEP/NCAR and NCEP/DOE Reanalyses using an Off-line Hydrologic Model.
J. Geophys. Res., 106(D16), 17,841-17,862.
NACWA, WERF, and WEF. 2013. The Water Resources Utility of the Future: A Blueprint for Action.
National Association of Clean Water Agencies (NACWA), Water Environment Research Foundation
(WERF) and Water Environment Federation (WEF), Washington, D.C.
Narragansett Bay Commission. 2017. CSO Control Facilties Phase III Amended Reevaluation Report
Volume 1. Prepared by MWH and Pare Corporation.
United Nations Environmental Programme (UNEP)-DHI Centre for Water and Environment. 2009.
Integrated Water Resources Management in Action. WWAP, DHI Water Policy, UNEP-DHI Centre for
Water and Environment.
United States Environmental Protection Agency (EPA). 1999. Combined Sewer Overflow Management
Fact Sheet: Sewer Separation. EPA Office ofWater. Report No. 832-F-99-041.
United States Environmental Protection Agency. 2004. Reprtto Congress: Impacts and Control of CSOs
and SSOs. EPA Office ofWater. Report No. 833-R-04-001.
Zoltay, V.I. 2007. Integrated watershed management modeling: Optimal decision making for natural and
human components. M.S. Thesis, Tufts Univ., Medford, MA.
Zoltay, V.I., R.M. Vogel, P.H. Kirshen, and K.S. Westphal. 2010. Integrated watershed management
modeling: Generic optimization model applied to the Ipswich River Basin. Journal ofWater Resources
Planning and Management. 136:566-575.
75
-------
WMOST v3 User Guide
Appendix A - Module and Page Summary
Page Names
Associated Module
Intro
Hydro
Baseline Hydrology and Loadings Module
Precipitation
Runoff1
Recharge1
RunoffL1
RechargeL1
Land Use1
Stonnwater
Stonnwater Hydrology and Loadings Module
Stonnwater-Data
WQBMPs
Water Quality Module
Riparian Buffers
Potable Demand
Nonpotable Demand
Demand Mgmt
SepticSewer
Surface Water
Groundwater
Interbasin
Infrastructure
CSO
CSO Module
Flood
Flood Damage Module
Measured Data
Results
Results Module
AdvResults
Calibration
Calibration Module
1 These pages also apply to the Stonnwater Hydrology and Loadings Module
76
------- |