September 22, 1993
MEMORANDUM
SUBJECT: New Version of SWMM 4.21
FROM: Jerry LaVeck. Chief, Watershed Modeling Section
TO: SWMM Users
o onH review is a diskette of the windows interface to SWMM and
Enclosed for your use ^^^™, Draft ™fjM ™«— ^^ UsCT>*
are not SWMM experts.
in addition to the mstallation procedures listed in the users guide, two more steps must
be completed for the program to work correctly.
Copy the two files listed below pn the distribute diskette into your VwindowsXsystem
directory.
' S M Sstm widows for workgroups - it will overwrite
your eS^fnTe. » i* a superset of the Wmdows 3.1 file.
If Windows is loaded on Drive C:. and your distribution disk is in Drive B:, you would
type:
COPY B-' DLL C:\WINDOWS\SYSTEM - and press return.
-------
-------
at least 530K of DOS memory to run. Be sure you have that much available, since the
Windows front end cannot detect failure of SWMM-DOS to run correctly. We are also
developing a back end for SWMM which will be available in the near future. If you
find any problems or have any comments or questions about the front end, please wnte
or call:
Jerry LaVeck
U.s' EPA, Office of Water
Office of Science & Technology
401 M St. S.W. (mail code 4305)
(202) 260-7771 or 260-9830 (fax)
-------
-------
GSC-TR-EI-93-004
SWMM Windows Interface User's Guide
DRAFT
Prepared for:
Office of Science and Technology
Standards and Applied Science Division
U. S. Environmental Protection Agency
401 M Street, S. W.
Washington, D. C. 20460
Prepared by:
General Sciences Corporation
6100 Chevy Chase Drive
Laurel, MD 20707
June 1993
-------
-------
Table of Contents
1. INTRODUCTION 1
2. TECHNICAL SUMMARY AND BACKGROUND 3
2.1 Overview of SWMM 4.2 3
2.2 Model Structure and Description of Blocks 3
2.3 Data Requirements 6
2.4 Output 7
3. TECHNICAL DESCRIPTION OF THE SWMM IMPLEMENTATION
IN WINDOWS 9
3.1 MET 10
3.2 RUNOFF 13
3.3 USEHP 15
3.4 TRANSPORT 16
3.5 EXTRAN !!'.'.'.'. 20
3.6 Limitations of SWMM Windows Interface 20
4. MINIMUM SYSTEM REQUIREMENTS AND SYSTEM LOADING . 23
4.1 Minimum System Requirements 23
4.2 Loading the System 23
5. USING THE SWMM WINDOWS INTERFACE . 25
5.1 Accessing an Existing File or Opening a New File 25
5.2 SWMM File Naming Conventions . 26
5.3 Saving Input Files 26
5.4 Setting Up a Default Editor for Viewing Output Files 26
5.5 Submitting an Input File to the Model 28
5.6 SWMM Windows Interface Commands and Function Keys .... 28
5.7 Manual Run Option 31
6. EXAMPLE RUNS . 33
6.1 Example 1 - A User-Defined Hyetograph (A Screening-Level
Example) 35
6.2 Example 2 - Steven's Avenue Drainage District in Lancaster, PA
(MET, RUNOFF, and TRANSPORT) 39
6.3 Example 3 - Simulation of a Simple one-Pipe System with Two
Manholes (USEHP & TRANSPORT) 42
6.4 Example 4 - Basic Pipe System (USEHP and EXTRAN) 44
APPENDIX A: SWMM WINDOWS INTERFACE DESIGN 49
REFERENCES 79
-------
Tables and Figure
Table 2.1 Summary of Computational Blocks in SWMM 4
Table 3.1 Data Category and Screen Input in MET interface 12
Table 3.2 Screen Input Sequence in RUNOFF Interface 14
Table 3.3 Screen Input Sequence in USEHP interface 15
Table 3.4 Screen Input Sequence in TRANSPORT Interface 18
Table 3.5 Different Element Types in Transport Block 19
Table 3.6 Screen Input Sequence in EXTRAN Interface 22
Table 5.1 Naming Conventions of SWMM Interface 27
Table 6.1 Example Run Matrix for SWMM Windows Interface 34
Table 6.2 Example Input files with SWMM Windows and SWMM 4.2 ... 35
Table 6.3 A User-Defined Hyetograph in MET 36
Table 6.4 User-Defined Hydrograph and Pollutographs in USEHP 43
Table A. 1 Input Variables and Screen Sequence in MET 50
Table A.2 Input Variables and Screen Sequence in RUNOFF 51
Table A. 3 Input Variables and Screen Sequence in USEHP 61
Table A.4 Input Variables and Screen Sequence in TRANSPORT ...... 62
Table A.5 Input Variables and Screen Sequence in EXTRAN . 69
Figures
Figure 3.1 SWMM Windows Interface Functions 10
Figure 6.1 Basic System with Free Outfall 45
-------
SWMM Windows Interface User's Guide
1. INTRODUCTION
The EPA's Storm Water Management Model (SWMM) is a large, complex model
capable of simulating the movement of precipitation and pollutants from the ground
surface through pipe and channel networks, storage/treatment units, and finally to
receiving waters. Both single-event and continuous simulation may be performed on
catchments having storm sewers, combined sewers, and natural drainage, for prediction
of flows, stages, and pollutant concentration.
The model may be used for both planning and design. The planning model is used for
an overall assessment of the urban runoff problem and proposed abatement options.
This model is typified by continuous simulation for several years using long-term
precipitation data. Catchment schematization is usually "coarse" in keeping with the
planning level of analysis. A design-level, event simulation also may be run using a
detailed catchment schematization and shorter time steps for precipitation input.
The SWMM Windows interface was developed to assist the user in data input and
model execution and to make a complex model user-friendly. The Windows interface
was developed for the Office of Science and Technology, Standards and Applied
Sciences Division of the* U.S. Environmental Protection Agency to assist them with the
Total Maximum Daily Load (TMDL) program. This user's guide provides guidance
on the use of the SWMM interface and illustrates its use with four example runs. The
Windows interface integrates the SWMM model and data handling needs to make the
model implementation user friendly. A brief description of the SWMM model structure
is presented in order to facilitate subsequent discussions.
This guide is divided into six sections. Section 2 gives you a technical summary on the
SWMM model, as well as the model structure, the interaction between the various
blocks of SWMM, the input requirements, and the output. Section 3 describes the
Windows Implementation of the blocks, including descriptions of the screens sequences,
the corresponding blocks, changes made for ease of use, and limitations of the
implementation. Section 4 provides you with minimum requirements and loading
information for the Windows SWMM. Section 5 provides you with the information
necessary to use the SWMM interface, including:
Page 1
-------
SVtMM Windows Interface User's Guide
How to access an existing file or opening a new file
File-Naming Conventions
Saving Input Files
Setting Up a Default Editor for Viewing Output Files
Sending an input file to the model
SWMM commands and function keys
Using the Manual Run option
Section 6 contains four example runs that highlight user entry and model output.
Appendix provides the screen structure and variable descriptions for the Windows
interfaces.
Page 2
-------
SWMM Windows Interface User's Guide
2. TECHNICAL SUMMARY AND BACKGROUND
2.1 Overview of SWMM 4.2
SWMM simulates most quantity and quality processes in the urban hydroiogic cycle on
the basis of rainfall (hyetograph) and other meteorological inputs and system
characterization (catchment, conveyance, storage/treatment). Storm sewers, combined
sewers, and natural drainage systems can be simulated as well.
2.2 Model Structure and Description of Blocks
SWMM is constructed in the form of "blocks" as follows:
Computational Blocks: Runoff, Transport, Extran, Storage/ Treatment
Services Blocks: Executive, Rain; Temp, Graph, Statistics
Each block has a specific function, and the results of each block are entered on working
storage devices to be used as part of the input to other blocks. A typical run usually
involves only one or two computational blocks together with the Executive Block. A
summary of the four computational blocks in SWMM are shown in Table 2.1. This
table explains the model capability, flow routing characteristics, and quality by block.
The Runoff Block is a critical block to the SWMM simulation. This block receives
meteorological data from either Rain and/or Temp Blocks or user defined hyetographs
(rainfall intensity vs. time) and then simulates the rainfall-runoff process using a
nonliner reservoir approach, with an option for snowmelt simulation. Groundwater and
unsaturated zone flow and outflow are included using a simple lumped storage scheme.
At the end, the Runoff Block produces hydrographs and pollutographs at inlet locations.
This block may be run for periods ranging from minutes to years. Simulations less
than a few weeks will henceforth be called single event mode and longer simulations
will be called continuous mode. With the slight exception of snowmelt, all
computations are done identically for the two cases (Huber and Dickinson, 1988).
Quality processes in the Runoff Block include generation of surface runoff constituent
loads through a variety of options: 1) build-up of constituents during dry weather and
wash-off during wet weather, 2) "rating curve" approach in which load is proportional
to flow rate to a power, 3) constant concentration (including precipitation loads), and/or
4) Universal Soil Loss Equation (Donigian and Huber, 1991). The overall catchment
may be divided into a maximum of 200 subcatchments and 200 channel/pipes plus
inlets. The Runoff Block transfers hydrographs and pollutographs for as many as 200
inlets and 10 constituents through an assigned interface file to other SWMM blocks.
Page 3
-------
SWMM Windows Interface User's Guide
Table 2.1 Summary of Computational Blocks in SWMM
l
if
-
i
-
Mir
**11
4iH
1 5 s * -a
* I l-s I
H
Z 3
i !
ii]
111
1
i
!
iii
[[
il
-
,
J!
11B l
jlljji
5].i]
ilili .
Hi In
I
ti
31
at-
jiS
•9 r i
j
H
Page 4
-------
SWMM Windows Interface User's Guide
The Transport block is one of the subsequent blocks, which performs the detailed flow
and pollutant routing through the sewer system. In Transport Block, flow routing is
accomplished using kinematic wave method, while quality processes include first-order
decay and simulating scour and deposition within the sewer system based on Shiled s
criterion for initiation of motion, and generation of dry-weather How and quality. The
Transport Block uses inlet hydrographs and pollutographs generated either from the
Runoff Block via the interface file or from the user defined option as the input, then
determines the quantity and quality of dry weather flow, the system infiltration,
pollutant loadings for each channel/pipe, and study area.
The Storage/Treatment (S/T) Block is a special type of element in the Transport Block.
The S/T Block simulates the routing of flows and up to three pollutants through a dry-
or wet-weather S/T tank containing up to five units or processes. It also simulates
removal in S/T devices by 1) first-order decay coupled with complete mixing or plug
flow, 2) removal functions (e.g., solids deposition as a function of detention time), or
3) sedimentation dynamics. Additionally, capital cost and operation and maintenance
cost can be estimated for each unit.
The Extended Transport (EXTRAN) Block provides the SWMM with dynamic wave
simulation capability (CDM, 1988). The EXTRAN Block is the most comprehensive
simulation program available in the public domain for a drainage system domain and
simulates branched or looped networks; backwater resulting from tidal or nontidal
conditions; free-surface flow; pressurized flow or surcharges; flow reversals; flow
transfer by weirs, orifice; and pumping facilities; and storage at on-line or off-line
facilities. EXTRAN uses a link-node description of the sewer system that facilitates the
discrete representation of the physical prototype. The conduit system is idealized as a
series of links and channels/conduits, which are connected as nodes or junctions. Links
and nodes have well-defined properties which, taken together, permit representation of
the entire pipe network. Links permit flow from node to node. Nodes are the storage
elements of the system and correspond to manholes or pipe junctions in the physical
system. Inflows, such as inlet hydrographs, and outflows, such as weir diversions, take
place at the nodes of the idealized sewer system.
These four computational blocks can be run either independently or in any sequence.
Additionally, service blocks are available for supporting the computational blocks.
They are statistical analysis of the output time series (Statistics Block), input and
manipulation of precipitation, evaporation, and temperature time series (Rain and Temp
Blocks), line printer graphics (Graph Block), and output time series manipulation
(Combine Block).
Page5
-------
Data Requirements
'
Categories of Data:
1) Weather Data:
2) Surface quantity:
3)
5)
6)
Storage/sedi
-------
SWMM Windows Interface User's Guide
7) Dry-weather flow constant or on basis of diurnal and daily quantity/quality
variations, population density, other demographic parameters.
8) Panicle size distribution, Shields parameter decay coefficients for channel/pipe
quality routing and scour/deposition routine (optional).
9) Storage/treatment: parameters defining pollutant removal equation; parameters
for individual treatment options such as particle size distribution, maximum flow
rates, size of unit, outflow characteristics; optional dry-weather flow data when
using continuous simulation.
10) ' Storage/treatment cost: parameters for capital and operation and maintenance
costs as function of flows, volumes and operating time.
In order to create SWMM input files, the users have to follow certain sequences within
one particular block or between blocks. In the Runoff Block, for example, the Group
Identifiers, i.e., SWMM ED, are defined as the order of input data and are
characterized into five sections: general input and control data, meteorological data,
surface quantity, surface quality, and print control. Each section may be divided into
subsections, e.g., meteorological data include snow data, precipitation data, and
evaporation data. Many individual parameters are entered in those data categories.
2.4 Output
SWMM produces a time history of flow, stage and constituent concentration at any
point in the watershed for Runoff, Transport, Storage/Treatment Blocks. Seasonal and
annual summaries are also produced, along with continuity checks and other summary
output. Simulation output in the Extran takes the form of water surface elevations and
discharges at selected system locations.
Page 7
-------
SWMM Windows Interface User's Guide
This page is intentionally blank.
Page 8
-------
SWMM Windows Interface User's Guide
3. TECHNICAL DESCRIPTION OF THE SWMM
IMPLEMENTATION IN WINDOWS
The SWMM Windows interface is designed to be as user-friendly to the user as
possible. The SWMM Windows interface consists of five functions: METeorological
data (MET), RUNOFF, USEr defined Hydrographs and Pollutographs (USEHP),
TRANSPORT, and EXTRAN. Basically, the MET function acts as the Rain and Temp
blocks. The RUNOFF, TRANSPORT, and EXTRAN interfaces perform the same
functions as the Runoff, Transport, and EXTRAN Blocks do in SWMM 4.2. The
USEHP function allows the user to define time series of flows and concentrations at
desired inlets.
A key feature of the design of a "Windows" user interface for SWMM 4.2 is the
separation of meteorological data from the Runoff Block of user input. Users will
access the MET interface to create and edit meteorological data. Selection of
meteorological data for use in a RUNOFF run will occur as part of the RUNOFF
function. The goal of this function is to consolidate user interaction and input of
meteorological data. From a user's perspective, all meteorological data will be
accessed unambiguously by a single file name. The difference in the RUNOFF
interface is, therefore, to eliminate meteorological data entry in the RUNOFF input file.
Similar consideration made in the TRANSPORT and EXTRAN functions is the
separation of user defined hydrographs and pollutographs from the TRANSPORT and
EXTRAN user input. The USEHP function was developed to handle the user supplied
flows and concentrations.
The normal execution sequence for the SWMM Windows interface is indicated by an
arrow symbol as shown in the screen in Figure 3.1. Usually, MET should be executed
first to create interface files that are required input to the Runoff Block. Likewise,
RUNOFF creates an interface file that is required input to the Transport and EXTRAN
Blocks. USEHP serves the same function for input to the Transport and EXTRAN
Blocks as the runoff interface file does. TRANSPORT or EXTRAN can be executed
independently when either a Runoff interface file or a USEHP file exists.
NOTE: In order to differentiate the Windows Interface blocks from the
actual SWMM blocks (even if they are practically the same thing
in some instances), the Windows Interface Blocks will be in
capital letters and will be identified as an interface or option
instead of block.
Page 9
-------
SWMM Windows Interface User's Guide
MET
RUNOFF
USEHP
TRANSPORT
EXTRAN
Figure 3.1 SWMM Windows Interface Functions
3.1 MET
As mentioned earlier, MET allows the user to create and edit meteorological data.
Input data in MET consists of three data components: general meteorological
parameters, precipitation and evaporation, and snow data. Those three elements take
a total of six screens (see Table 3.1). The first screen describes the control variables
in MET, such as the types of meteorological data and units associated with the MET
data. The selections on the first screen determines which screens are accessible. The
next two screens contain raingage stations and precipitation data. The fifth screen
defines monthly average evaporation and/or wind speed. Air temperatures are stored
on the third screen for contiguous snowmelt simu'ition, and on the last screen for single
event snow melt simulation. RAIN (precipitation) and evaporation data are always
required in MET. Wind speed and temperature data are needed when the snowmelt is
simulated .
Precipitation data are the single most important group of hydrologic data required by
SWMM. SWMM requires a hyetograph of rainfall intensities versus time for period
Page 10
-------
SWMM Windows Interface User's Guide
of simulation. For single event simulation, this is usually a single storm, and data for
up to ten raingages may be entered. For continuous simulation, hourly, daily or other
continuous data from at least one gage are required. RAIN data can be selected from
a NOAA data file, an existing user created file, or a new file. NOAA data files are
obtained from the EPA Environmental Research Lab in Athens, Georgia They contain
35-year daily weather data for all NOAA first order stations in the United States.
Please note that at present only one raingage is available when the user selects the
NOAA data option from our meteorological database. The RAIN data should be
entered in the Rain Data Table on Screen No. 3. Input variables for this screen are
listed in Table A.I. The format used in Rain Data Table is the same one stored in the
Rain BlocK interface file of SWMM, which is an unformatted binary file. Thus, the
RAIN data can be handled through the Rain Data Table instead of using the Rain Block
and E1-E3 data groups in Runoff Block.
Evaporation can be input either by entering monthly average rates or using default rates
that are internally supplied in the SWMM model. Wind speed and temperature data are
needed, if snowmelt simulations are included. Similar to evaporation rates, a monthly
average wind speed should be provided. When a daily NOAA data file is selected,
MET will automatically compute monthly values for evaporation and wind speed.
Air temperature can be entered on either Screen No.3 or Screen No. 6 based upon the
types of snowmelt simulation. Continuous snowmelt simulation requires a complete
time history of daily maximum and minimum temperatures on Screen No. 3. These
maximum/minimum temperatures are supplied on the NOAA data file. A single event
snowmelt simulation receives air temperatures from Screen No. 6 for a given time step
entered on the first screen. The temperatures are constant over the time interval.
After all the data are entered, the MET will generate four MET interface files: a RAIN
data interface file, a TEMP data interface file, an evaporation and wind speed file
CEVAWIND), and a single event snow melt temp file (SINAIR). The first two
interface files are the SWMM scratch files processed during the execution of the Runoff
block. The other two files would be processed into the Runoff Block input file. The
evaporation and wind speed data from the EVA WIND file will be placed on Fl and C2
data group lines in the RUNOFF input file, respectively. The air temperature from the
SINAIR file will be input to C5 data group line.
Page 11
-------
SWMM Windows Interface User's Guide
Table 3.1 Data Category and Screen Input in MET interface
I
i
A
•c .9
i
I
e
i
i
JS
2
GO
AP
Sg
il
3
'5.
I
rs
g
(U
«73
O
Page 72
-------
Windows Interface User's Guide
3.2 RUNOFF
The RUNOFF interface is designed to closely follow the input representation order in
the Runoff Block. Input data in RUNOFF are divided into five data elements: general
control parameter, meteorological data, water quality, description of a drainage system,
and print control. The general control parameter includes identifying a MET file, unit,
simulation length, starting date, time step, and type of simulations. These selections
determine whether subsequent screens or controls are accessible. The meteorological
data include precipitation, evaporation, temperature, and wind speed, which should be
generated through the MET function. Water quality simulation requires the user to
specify up to ten pollutants and appropriate parameters to buildup and washoff
mechanisms, and up to five land uses to characterize different subcatchments. Erosion
and groundwater simulations are optional. A drainage system can be described as
number of subcatchments (subwatersheds) connected with channels/pipes. Necessary
inputs associated with subcatchmem are surface area, width, ground slope, Manning's
roughness coefficient, and infiltration rates. Channel descriptions are the length,
Manning's roughness coefficient, invert slope, diameter for pipes, and cross-sectional
dimensions of the channel. Other inputs are discussed in Section 2.1.
There are a total of twenty-three screens in the RUNOFF interface. The screen input
sequence (see Table 3.2) reflects an overall structure of the Runoff Block. Screen
numbers are assigned corresponding to the data elements and to cover all the input
requirements. Table 3.2 also shows the relationship between the screen numbers in the
RUNOFF interface and SWMM ID (Group Identifiers) in a RUNOFF input file.
Furthermore, a spreadsheet (see Table A.2) is generated to identify the controls
(variables) for each screen. This table defines the following for RUNOFF:
1. variable name in the Runoff Block,
2. the description of the variable,
3. SWMM ID in the Runoff Block,
4. screen number,
5. control number,
6. control type, item, range, default, and unit.
Page 13
-------
SWMM Windows Interface User's Guide
Table 3.2 Screen Input Sequence in RUNOFF Interface
1 SUCCN Nu
SWMM U>
•
1
j
|
'
a
j
*
•
j
2
a
•
i
£
!
f
1
i
•i
j
i
s
I
4
1
i
I
I
1
I
a
in
6
j
it
Ub
1
i
1
}
•r
V
u
t
•
t
1
I
i
i
4
2
f
4
s
&
1
4
i
3
a
8
U
t
J
.
5
o
«
1
1
1
I
I
4
Z
1
i
*
«
j
J
i
^
Z
s
I
. *
j
4
C
=
1
..
*
3
a
-»
f
li
>
M
•
a
*
a
•»
i
•
•
i
4
n
fi
i
-------
SWMM Windows Interface User's Guide
Each variable in the Runoff Block for SWMM 4.2 has a unique control number on a
particular screen in the RUNOFF interface. For example, if you refer to the first page
of Table A.2, a variable WET in SWMM 4.2 is interpreted as Wet time step (sec).
which is the eighth control on the first screen. For WET, the SID (SWMM ID) should
be under Group Bl, the type is floating, the range must be equal or greater than one,
the default should be 3600.0 seconds, and the unit is in seconds. The relationship
between variables of SWMM 4.2 and controls of SWMM interface can be easily
checked in Table A.2.
3.3 USEHP
The USEHP function is designed to store inlet flows and concentrations. This option
is preferable to the RUNOFF interface file option for those users who wish mainly to
use the Transport Block or the Extran Block. For EXTRAN, the user should provide
only inlet hydrographs in USEHP since EXTRAN is not capable of simulating water
quality. Any quality information is input to EXTRAN is ignored by the program.
There are a total of five screens in the USEHP interface and input requirements are
listed in Table 3.3. USEHP will generate four USEHP Mies as input to the Transport
and Extran Blocks. As shown in Table 3.3., in a Transport input, the values stored in
the USEHP file will be placed the variables (NINPUT and NCNTRL), II line, and Rl
lines for inlet hydrographs; a variable (NPOLL) and Fl lines for pollutographs. In
Extran input, the values will be placed a variable (NJSW) and K1-K3 lines for inlet
hydrographs.
Table 3.3 Screen Input Sequence in USEHP interface
Data
Componcot
1
2
Category
General Control
Parameters
List of Inlet Numbers
Pollutant Name Table
Time of day
Hydrograph/Pollutograph
Table
Data Requirement
Units, * of inlets, * of
pollutants, # of data points
Inlet number
Pollutant name, input and
output unit
Time in hours
Time series of flows and
concentrations
Transport
Block
NINPUT
NPOLL
11
Fl
Rl
Extran
Block
NJSW
K2
No
K1.K3
Screen
No.
1
2
3
4
5
Page 15
-------
SWMM Windows Interface User's Guide
3.4 TRANSPORT
The Transport Block was implemented following the same procedure as used for the
Runoff Block. Table 3.4 indicates the screen input sequence in the TRANSPORT
interface as compared to in the SWMM model. The TRANSPORT interface is
characterized into six data components, namely TRANSPORT simulation control, sewer
system description, water quality, infiltration and dry-weather How, study area
description, and print control. TRANSPORT simulation control defines an inlet
hydrograph and pollutograph file, computational parameters, units, and types of
simulation. Sewer system description provides the physical characteristics of the
conveyance system. Quality data identify pollutants to be routed and their
characteristics. Infiltration and Dry-Weather Flow (DWF) data describe the necessary
drainage area characte-sties to permit the computation of the respective inflow
quantities and qualities. Print control reports a time history of inlet hydrographs and
pollutographs, and a time history of channel depths.
The physical representation of the sewer system is a key input to the TRANSPORT
simulation. The sewer system is classified as a certain type of "element." All elements
in combination form in a manner are similar to that of links and nodes (Hubcr and
Dickinson, 1989). Bements in a real system can be described as a network of conduits
(e.g., channels/pipes) joined with non-conduits such as manholes. Conduits themselves
may be of different element types depending upon their geometrical cross-section.
Non-conduits must be located at points corresponding to inlet points for hydrographs
generated by either the RunoffBlock or USEHP. According to SWMM documentation,
there is a total of twenty-five types of elements that are available for use in Transport
Block (See Table 3.5). Eighteen of them are conduit elements and seven are non-
conduit elements. For the elements with regular shapes, data requirements are usually
the tabulation of shape, dimension, slope, and roughness parameters. While for the
elements with irregular shapes, supplemental data are required, such as flow-area and
depth-area relationships of the elements. The irregular shapes are new shapes and
natural channels with HEC-2 format for conduit elements and storage tanks for non-
conduit elements.
Only up to four pollutants can be handled for water quality simulation in the Transport
Block. PoUutants may be introduced to the sewer system by either the RUNOFF
interface or USEHP using the data group II and Rl in the Transport input file.
The TRANSPORT interface contains a total of seventeen screens. The data components
associated with screen numbers in the interface and SWMM ID in SWMM 4.2 are
presented in Table 3.4. Table A.3 contains a description of the TRANSPORT data
requirements including variable definitions, SWMM ID, screen number, control
Page 16
-------
SWMM Windows Interface User's Guide
number, control type, control item, type, range, default, and units. This table was
designed to assist in assembling data for implementing WINDOWS processes of
SWMM and give a clear picture of identifying the variable used in TRANSPORT
interface as compared to SWMM 4.2.
The TRANSPORT interface reads the data for conduit and non-conduit elements from
the Sewer System Table on Screen No. 3. Different element types supplied with the
TRANSPORT block and corresponding element names used in the TRANSPORT
interface are listed in Table 3.5. Three irregular shapes of elements are a natural
channel, a user supplied shape, and a storage unit. They are treated as special elements
and to be separate functions in the TRANSPORT interface. Currently, the
TRANSPORT allows the user to specify three types of files, which correspond to three
types of sewer elements. The files must contain the input parameters required by the
TRANSPORT input. The three types of files are XHEC2###.PIP for a natural channel,
XSHAP###.PIP for a user supplied shape, and XTANK###.PIP for a storage unit.
Page 17
-------
SWMM Windows Interface User's Guide
Table 3.4 Screen Input Sequence in TRANSPORT Interface
1,
«<»
j
S
a
u
i
Sj
I
2
Q
]
^
1
«t
I
m
M
4
f
^
i
-
I
s
|
I
i
1
i 9
r 4
5
J
|
1
3
.
J
1
1
i
CJ
^
:
i
•
«
i
1
J
-
, i
}
J
*
s
,
ii:
i <•
s
I
\
3
J
J
1
u
75
-------
SWMM Windows Interface User's Guide
Table 3.5 Different Element Types in Transport Block
NTYPE
Transport Block
TRANSPORT interface
CONDUIT ELEMENTS
1
2
3
. 4
5
6
7
8
9
10
11
12
13
14
15
16
17, 18
Circular
Rectangular
Phillips standard egg shape
Boston horseshoe
Gothic
Catenary
Louisville semieiliptic
Basket-handle
Semi -circular
Modified basket-handle
Rectangular, triangular bottom
Rectangular, round bottom
Trapezoid
Parabolic
Power Function
HEC-2 Format - Natural Channel
User supplied
.Circular
Rectangular
Egg shape
Horseshoe
Gothic
Catenary
Semieiliptic
Baslet-Handle
Semi-circular
Modified B-H
R + tri bottom
R + round bottom
Trapezoid
Parabolic
Power F
XHEC2***.PIP
XSHAPMMf.PIP
NON-CONDUIT ELEMENTS
19
20
21
22
23
24
25
Manhole
Lift station
Flow divider
Storage unit
Flow divider - weir
Flow divider
Backwater element
Manhole
Lift station
Flow divider
XTANK***.PIP
Flow divider/weir
Flow divider
Backwater
Page 19
-------
SWMM Windows Interface User's Guide
3.5 EXTRAN
There are three data components included in the Extran Block: EXTRAN simulation
contro sewer system description, and output print and plot. The EXTRAN s ™
control detmes the emulation, an inlet hydrograph file. computationaVconttol
s.mulaaon methods. Like the TRANSPORT interface, EXTRAN gets inlet
m , -A H EXTRAN. The sewer system description
are further divided into two sections: identification of channels/conduits and junctions
The cross sections of channels/conduits can be regular or irregular. For S
channels, input data are relatively simple. For irregular channels however, daTare
complex and a detailed description to define cross sections for each channel is n^
Juncnon data can be described as regular junctions and special flow delicts
diver, samtary sewage out of a combined sewer system or relieve the
sanitary interceptors. The five types of junctions are storage, orifice
d°±h Uke.iTlar channels- *<>« *Peci* Junctions^ reTu
descnbmg a nme-history curve for stage, volume, flow, etc. Output prim
determine number junctions and channels for printing and plotting
There are twenty-three screens for the EXTRAN interface, as shown in Table 3 6
Sixteen ofthese screens are for inputs for channels and junctions. T^lol
are developed to handle large input depending upon the type of channel ju
Variable input sequences on each screen are given in Table A.4, which define
udSption of variable' SWMM
for namnl channels- wwch
3.6 Limitations of SWMM Windows Interface
1.
to the RUNOFF W-ndows interface, the naximum number of watersheds and
channels .aUowed » 100. For the SWMM Model 4.2, the maximum number
allowed » 200. to the TRANSPORT and EXTRAN Interfaces, the
* * '
and channels allowed in the SWMM model is 200.
Page 20
-------
SWMM Windows Interface User's Guide
2. Due to problems with the subcatchment number variable, which would not
accept names, all IDs in all the Windows interfaces have to be integers instead
of characters. You cannot enter a name for pipes, subcatchments, inlet
numbers.
3. Due to problems encountered with the snow melt simulation and with the
conversion of the pan evaporation data, daily evaporation rate and wind speed
data from the MET interface for continuous snowmelt simulation will be
converted to monthly data.
4. The post-processor in SWMM has not been implemented in Windows.
Page 21
-------
SWMM Windows Interface User's Guide
Table 3.6 Screen Input Sequence in EXTRAN Interface
al
(N 2
u
UJ
I
i!
3
M
33
l!
I
i
I
1
1
1
-------
SWMM Windows Interface User's Guide
4. MINIMUM SYSTEM REQUIREMENTS AND
SYSTEM LOADING
4.1 Minimum System Requirements
The system runs under Microsoft* Windows. The minimum system requirements are
provided below:
• Windows Version 3.0
• 80386 Processor
• 4 Megabytes RAM
• 10 Megabytes hard disk space
NOTE: A math co-processor is recommended but not required.
4.2 Loading the System
STEP 1. Go to DOS and create a directory on the hard disk: MD\SWMM.
NOTE: You must have 10 Megabytes of space on the hard disk drive on
which you are installing SWMM.
STEP 2. Place the disk marked SWMM Disk *1 in either drive A: or
drive B:. Go to the directory that you created (CD\SWMM) and
enter the following command from that directory:
A:INSTALL A:
or
B:INSTALL B:(if the disk is in drive B:)
STEP 3: Follow the instructions for copying.
STEP 4. Once you have finished copying the files, create an icon in the
Windows Main Menu using the NEW option in the FILE menu
under the program manager. The executable for which you
should create an icon is described below:
Executable Description
SWMM. EXE The main SWMM executable. This executable
allows you access to the two SWMM options:
Page 23
-------
SWMM Windows Interface User's Guide
The Windows Interface Option:
This option calls .up all the windows
implementations of the various blocks of SWMM
as explained in Section 3.
Manual Run Option:
For experienced users of SWMM and those
familiar with the structure of the input files, this
option allows you to edit input files directly using
a data editor.
You may choose to have SWMM be a separate group under the
Program, have it as one of the items in the STARTUP menu so
that it is available whenever you log into the Windows or make
it an item under the MAIN MENU so that you can access it when
you wish to use. Refer to your Windows Manual for information
on creating an icon for SWMM.
The working directory option should be the one containing the
executables since SWMM requires certain table Mies in order to
create the input Mies.
STEP 5. You are now ready to use SWMM.
Page 24
-------
SWMM Windows Interface User's Guide
5. USING THE SWMM WINDOWS INTERFACE
Once you have finished loading the software, you will be ready to access the SWMM
Windows Interface and Manual Run interface. When you select the Windows Interface
option, you will see a flow-chart that is shown in Figure 3.1 that shows the various
blocks that are available and the sequence you should follow in accessing them. All the
blocks share certain characteristics since they are all in Windows. This section details
how to use the capabilities available in the various interfaces in SWMM. In addition,
it will detail the Manual Run option as well. This section describes the following:
How to access an existing file or opening a new file
File-Naming Conventions
Saving Input Files
Setting Up a Default Editor for Viewing Output Files
SWMM Windows Interface commands and function keys
Using the Manual Run option
5.1 Accessing an Existing File or Opening a New File
When you first enter any of the Windows SWMM Blocks, you will be automatically
assigned a new file. The new file name and number will appear at the top of the screen
in parentheses.
To access an existing file, click on the EDLE option on the very top line, select the
QPEN option and select the file that you want from the list that appears. When you
click on the FILE option, you will be asked to verify that you actually wish to open a
new file. This is to remind you that calling a new file will overwrite all the values
contained in the file that you are in presently.
NOTE: The input files must be in the same location as the *.EXE files
(the SWMM executable files). If you elect to read in an existing
file from a different directory, the directory that the file is in
becomes the default directory for SWMM. All the data files for
SWMM must exist in the default directory. So we strongly
recommend that you do not save input files in any location other
than the SWMM directory.
If you selected an existing file to edit, when you choose to save the file, the existing
file will be rewritten ^ith the sew values unless you choose the SAVE AS option and
assign a new file name. Please remember, if you are assigning a new name to a file,
Page 25
-------
SWMM Windows Interface User's Guide
to follow the naming conventions followed by SWMM explained in the next subsection.
5.2 SWMM File Naming Conventions
The naming convention of files in SWMM is as follows: the first five characters are the
function name, the next three digits are sequentially assigned numbers that indicate the
number of the input file that you are currently creating, and the file extension indicates
the file type. Table 5.1 summarizes naming conventions of the SWMM interface for
each function. There are two file extensions in the MET input files. One extension is
.MET which indicates user defined meteorological data, and the other is .ATM which
indicates long term meteorological data obtained from the EPA Athens Lab. The file
extensions in the RUNOFF and TRANSPORT interfaces are also standardized. For
instance, MNP is the input file and ".OUT is the output file.
5.3 Saving Input Files
SWMM will ask you whether you wish to save the input file when you exit the
interface functions or when you reach the last screen of an interface function.
However, if you have accessed an existing file and made all the changes before
reaching the last screen, you may save the input file by proceeding to the FILE option
and selecting the SAVE option. Once you have completed an input file, you may
submit it to the SWMM model or the appropriate model for execution. When you
submit the input file to the model, the input file will be validated by the Windows
interface. If any errors are detected during the validation, you will be informed of
them and brought to the incorrect entry so that you might effect the change
immediately.
5.4 Setting Up a Default Editor for Viewing Output Files
The default editor for viewing and editing SWMM output or input files (through the
Manual Run Option) is the NOTEPAD program in Windows. The NOTEPAD program
will not allow you to view files larger than 64 Kilobytes (K). Most of the SWMM
output files generated by the interface options are larger than 64 K. You may choose
any other editor for viewing the output by selecting the Utilities option on the second
line of the screen. Click on Setup Output File Viewer. You will then be required to
enter the location and executable name of the output file editor when you select this
option.
Page 26
-------
SWMM Windows Interface User's Guide
Table 5.1 Naming Conventions of SWMM Interface
SWMM Interface
METeorologictl
dau editor
(MET)
RUNOFF
USEr defined
Hydrofraphs mad
PoUuiofrapha
|(USEHP)
TRANSPORT
EXTRAN
RbNaOM »
S MET M* MET
•ATH
SMET«*MT1
SMETMTMT?
SMCTMf.Mn
SMETJWMT4
RNOFFAM.INP
RNOFFAM.RUN
RNOFFMf.OUT
RNOmef.INT
U3BHPMV.HP
U38HMM.HF1
U3OVMV.HP2
USEHFMW.Hn
USEHPtM.HM
TRANMM.INF
XTANKMtnP
XSHANSV.nF
XHEC2Mf.Pir
TtAHaJW.lUN
TtANMM.OUT
TKANttM.INT
eXTBJWM.INP
EXTItNMf.RUN
EXTRNMf.OUT
EXTtNMMNT
File Type fFmt)l
Input (A)
Input (A)
Output/Input (B)
Input (A)
Input (A)
Output (A)
Output (B)
Input (A)
Output/Input (A)
Input (A)
Output (A)
Output (B)
Input (A)
Output (A)
Output (B)
Content
MET Windows interface input.
Consist* of daily meteorological dau for all NOAA first order
tuuons in the U.S. Provided by the EPA Enviro. Res Lab in
Athens. GA.
A Rain interface file that contains precipitation data. An input *
file to the Runoff Block.
A Temp interface file that contain* maximum and minmum
temperatures. This is an input file to the Runoff Block.
An monthly evaporation and wind speed file. To be placed in
FI and C2 lines in a Runoff input file.
A air temp data file for single snow melt simulation. To be
placed in C5 line in a Runoff input file.
RUNOFF Windows interface input.
RUNOFF run file which can be executed under DOS.
Runoff output generated by SWMM.
RunnofT interface file generated by SWMM, caa be ueed for
subsequent blocks.
USEHP Windows interface input.
Aa inlet bydrognph and/or poUutofnph file. To be placed in
the NINPUT, NPOLL, Fl, 11. and Rl lines in a Transport
input file.
An inlet hydrograph file to be placed in K1-K3 lines and
NJSW ia ETRAN input file.
TRANSPORT Windows interface input.
Storage tank data file defined by the user.
New shapes dau file defined by the user
Natural channel (HEC-2 format) data fife defined by the user.
TRANSPORT run file which can be executed under DOS.
Transport output generated by SWMM
Transport interface file generated by SWMM, which caa be
used for subsequent blocks.
EXTRAN Windows Interface input
EXTRAN run file which caa be executed under DOS.
Extna output generated by SWMM
•
E it ran latanace file, caa be uaed for subsequent bkxks.
File format caa IM either ASCII (A) or Binary (B).
Page 27
-------
SWMM Windows Interface User's Guide
5.5 Submitting an Input File to the Model
When you have completed the input file for the interface that you are in, select the
RUN button to run the model with the input file you created. When you select the
RUN option, all the entries in the file will be validated. If any errors are detected
during the validation, SWMM will put up a message informing you of the type of error
detected and will then take you to the prompt that is incorrect. Once all the values are
valid, the file is submitted to the appropriate model for execution. An icon will appear
at the bottom of the screen for those blocks for which the SWMM model is called.
When the processing of the input file is complete and the output results, SWMM will
ask whether you wish to view them. If you indicated that you did wish to view the
output file, SWMM will show them using a data editor allowing you to annotate the
results if you so choose. To exit from the Data File Editor, press the ALT and F4
function keys simultaneously. You will be returned to the interface function that you
were in previously.
5.6 SWMM Windows Interface Commands and Function Keys
The Windows Interface options all have a series of "buttons" designed to make using
the system as easy as possible. These buttons and the commands they represent are
accessible in three ways: (1) click on the button with the mouse key to access the
function that button represents, (2) press the ALT along with the underlined letter in
the button title (e.g. ALT/H for Help), or (3) select the TOOL option and select the
option under there from the list presented.
The buttons and the commands they represent are explained below:
The NEXT Button This option allows you to move to the next screen in the
interface. If there are incorrect values on the screen that
you are in currently and you attempt to move to another
screen, SWMM will inform you of the error and allow
you the option of going back (and correcting the error at
a later time) or correcting the error. The cursor will
blink at the prompt with the incorrect entry, if you elect
to correct the error before moving on.
The BACK button This button allows you to move back one screen. If there
are incorrect values on the screen that you are in
currently and you attempt to move to another screen,
SWMM will inform you of the error and allow you the
option of going back (and correcting the error at a later
Page 28
-------
SWMM Windows Interface User's Guide
The INDEX Function
time) or correcting the error. The cursor will blink at the
prompt with the incorrect entry, if you elect to correct the
error before moving on.
Instead of moving backwards and forwards through the
screens, you may use the INDEX feature to hop back and
forth between screens.. To access this feature, move your
cursor over the INDEX button and click with the mouse
button, or enter ALT, N. All the screens available in this
option will be displayed with the screen title and the
screen numbers. Certain screens will be grayed out.
This indicates that these screens are not accessible due
to selections made on other screens. The screen that
you were in when you selected the INDEX button will
be highlighted in blue text
If you wish to see the prompts that appear on each
screen, press the EXPAND button at the bottom of the
INDEX screen. The screen names and numbers will then
include all the prompts contained in the screens. You
may contract the screen again to the normal display of
just the screen names and number by clicking on the
CONTRACT button.
To move to the screen that you want, move your cursor
over the screen number of any non-gray screen and click
the left mouse button. You are taken immediately to that
screen. To exit the INDEX screen and return to the
previous screen, click on the CANCEL button.
This option allows you access help information on that
interface. You have two different types of help: Prompt-
Level Help which contains information on the specific
prompt that your cursor is on or on which you are
entering data and General Help which contains a general
description of the SWMM system.
To access General Help, move your cursor to the tool
bar and the select the HELP option, or enter ALT, H
from the keyboard. A menu will appear. Select the
HELP INDEX option or enter I from the key board.
The HELP Button
Page 29
-------
SWMM Windows Interface User's Guide
To access Prompt-Level Help, move your cursor over to
the prompt on which you would like information and
press either the Fl function key or move your cursor over
to the HELP button and click.
A window will appear in either case displaying broad help
or prompt-specific help. If you are accessing prompt-
specific help, you may browse through the helps for all
the additional prompts that are related to the prompt you
are on by accessing the forward and backward BROWSE
keys.
All words or sentences that are in green and underlined
have further information on them. Move your cursor
over the phrase on which you would like further
information and click. You will be taken to that option.
There is a search function within the HELP functions that
allows you to type in a word and find all the help
available on the word that you typed. To access this,
select the SEARCH key in the HELP window and follow
instructions.
When you are through viewing help, exit the help window
by either entering ALT, F4 from the keyboard or by
moving the cursor over to the icon on the top left corner
of the window and double clicking the left mouse button.
You will be returned to the screen that you were in
previously.
This option allows you to access the Calculator Function
within Windows, should you require the use of a
calculator at any screen in SWMM.
This option allows you to move to the first screen in
SWMM from any screen without having to use the
INDEX function.
This option allows you to submit an input file that you
have created to the SWMM model for execution. If you
have incorrect entries in the file when you click on this
The CALC Burton
The TOP Button
The RUN Button
Page 30
-------
SWMM Windows Interface User's Guide
button, SWMM will inform you that you have incorrect
values and take you to the appropriate prompt so that you
may correct the value and resubmit the file.
The RESTORE Button This option allows you to restore the default values that
were in the file before you started making changes for
this screen. This is an option that allows you to start
again without having to exit the system or go back to
every variable that you changed.
5.7 Manual Run Option
This option is one of two main options available to you in the SWMM main menu.
This option allows you to edit input files and submit the appropriate ones to the model.
Table 5.1 gives you a summary of all the input and output files generated by SWMM
and their file formats. Refer to it if you have any questions about any of the files.
You may only edit ASCII files. This option requires some expertise in SWMM, so we
recommend that you use the Windows interface option to familiarize yourself with the
SWMM Model prior to using this option. To change the default file editor, select the
Utilities option at the top of the screen. Click on Setup Output File Viewer. You will
then be required to enter the location and executable name of the output file editor when
you select this option.
You have two options for the SWMM Input files:
EDIT You may edit two types of files using this option: *.RUN, which are the
files generated by the RUNOFF, TRANSPORT, and EXTRAN
interfaces for input to SWMM or *.DAT files, which are the traditional
files created for the DOS model version of SWMM that you may have
created previously or came with the SWMM model (the example runs
that are provided, see Section 5).
RUN Once you have edited either the *.RUN files or the ".DAT files, you
may submit them for processing by the SWMM model by selecting this
button.
Page 31
-------
SWMM Windows Interface User's Guide
This page is intentionally blank.
Page 32
-------
SWMM Windows Interface User's Guide
6. EXAMPLE RUNS
This section contains four example runs to illustrate how to best use the SWMM
Windows interface. The example runs are selected in an attempt to exercise the major
portions of the SWMM interface. A matrix of SWMM interface with the various runs
is shown in Table 6.1. The SWMM interface contains five functions: MET, RUNOFF,
USEHP, TRANSPORT, and EXTRAN. Each function has its own components, and
each component may be divided into sections if applicable. Five SWMM interface
functions and their subdivisions are listed in the first column. The four example runs
are given on the top row of Table 6.1. For a given example, two or more functions
may be used depending on the level of complexity of the simulation. Example 2 shown
in Table 6.1, for instance, illustrates the combination of three functions: MET,
RUNOFF, and TRANSPORT. It includes the applications on 1) how to generate
precipitation data for a single event simulation using MET; 2) how to describe a
drainage system with channels and subwatersheds and simulate runoff and water quality
using RUNOFF; and 3) how to apply TRANSPORT on a sewer system for the
simulations of infiltration, dry weather, and water quality.
These examples were obtained from the EPA and demonstrated the applications on the
Rain, Temp , Runoff, Transport, and Extran Blocks in the SWMM model. The
interface runs can be checked using the input files supplied by EPA along with the
distribution package for SWMM. The example input files prepared for testing the
SWMM Windows interface and corresponding ones used for SWMM 4.2 are listed in
Table 6.2. This table indicates the relationship between functions used in the SWMM
interface and Blocks in SWMM 4.2 for each example run. The first example is a
screening level example: the rainfall-runoff was simulated through a single watershed.
The first run shows the use of the MET and RUNOFF functions, while the second one
presents a user supplied hyetographs utilizing MET, RUNOFF, and TRANSPORT.
The sequence of running the SWMM Windows interface are given in the FUNCTION
column of Table 6.2. In example 1, MET produces an input file called
SMET001.MET, and further generates a Rain interface file after a RUN button is
selected. This is equivalent to running the Rain Block using two input files:
RAIN8.DAT and USRN4.DAT. A RUNOFF input file, RNOFF001.INP, generated
by the interface can be checked with a Runoff Block input file, RUNOFF36.DAT.
Page 33
-------
SWMM Windows Interface User's Guide
Table 6.1 Example Run Matrix for SVVMM Windows Interface
FUNCTION EXAMPLE RUN -
MET
Precipitation
Rain gage
Evaporation
Snow
1
Single
Multi
Default rates
Monthly rates
Wind Speed
Temp - Single Event
Continuous
RUNOFF
Drainage System
Snow
Groundwater
Water Quality
Erosion
Channels/Pipes
Watersheds/
Subcatchments
Single Event
Continuous
TJSEHF"
Inlet
Flow
Pollutant
Single
Multi
IRANSFOKT
Sewer System
Infiltration Inflow
Dry Weather Inflow
Water Quality
Storage Tank
New Shape
Natural Channel
RUNOFF Interface
USEHP
KXTRAN
Sewer System
Inlet Hydrographs
Channels
Junctions (one free outfall)
Boundary Conditions
RUNOFF Interface
USEHP
Page 34
-------
SWMM Windows Interface User's Guide
Table 6.2 Example Input files with SWMM Windows and SWMM 4.2
Example
1
2
3
10
SWMM User Interface
Function
MET
RUNOFF
MET
RUNOFF
TRANSPORT
USEHP
TRANSPORT
USEHP
EXTRAN
Input File
SMET001.MET
RNOFF001.INP
SMET002.MET
RNOFF002.INP
TRANS001.INP
USEHP002.HP
TRANS002.INP
USEHP001.HP
EXTRN001.INP
SWMM 4.2
Block
Rain
Runoff
Runoff
Transport
Transport
Extnn
Input File
RAIN8.DAT
USRN4.DAT
RUNOFF36.DAT
RUNOFF3.DAT
TRANS1.DAT
TRANS35.DAT
EXAM1.DAT
6.1 Example 1 - A User-Defined Hyetograph (A Screening-Level Example)
This is an example of a user-defined time series of rainfall with a total precipitation of
28.0 mm. A user defined hyetograph is shown in Table 6.3. The format (see Table
6.3) required by MET is the same one used in Rain Block interface file. A single
catchment with a total drainage area of 300 hectares receives rainfall through an inlet.
The catchment characteristics are 20% of impervious area, 100 meters long for
catchment width, and 0.001 for ground slope. The total simulation length lasts 3 days.
This example is there to show you how to use MET and RUNOFF together to perform
a Runoff Block Run. Only hydrologic simulation is involved.
Page 35
-------
SWMM Windows Interface User's Guide
Table 6.3 A User-Defined Hyetograph in MET
Julian Date
88001
88001
88001
88001
88001
88001
88001
88001
88002
88002
88002
Hour1
(second)
3600
7200
10800
25200
26100
27900
30600
34000
37800
41400
45000
Time Interval
THISTO
(second)
300
300
300
300
300
300
300
300
300
300
300
Rainfall Intensity
(mm/hr)
12
24
0
12
12
12
24
42
54
66
78
1 Daytime (starting storm) hour in seconds from midnight
The steps that you must follow for this screening-level example are explained in detail
below:
STEP 1. Select the SWMM Windows Interface option from the main SWMM
menu. Next, select the MET option, which is the first option in the flow
chart, by clicking on the option.
STEP 2. Select the example MET data that has been created for you by clicking on
the FILE option, followed by the QPEN option. Select the first file listed:
SMET001.MET. The file will be loaded into the MET interface. Move
through the screens and familiarize yourself with the MET option. Use
the HELP button to answer any questions you may have. Compare the
input to Table 6.3 to make sure that it is the right file.
Page 36
-------
SWMM Windows Interface User's Guide
STEP 3. Next, click on the RUN button. MET will then generate a Rain Block
interface file. You must have used the RUN button before you may
proceed to the next block in SWMM.
STEP 4. Exit the MET option by pressing the ALT key and F4 function key. You
will be returned to the SWMM Windows Interface menu. Select the
RUNOFF option.
STEPS. Click on the EILE option, select the QPEN File option. A list of Runoff
Input Files will appear. Select the RNOFF001.INP file for this example
run. Once you select this option, the parameters for this example run will
be entered from the file. The first screen for the RUNOFF block also
allows you to enter the Meteorological Input file. If the file that you
created for the MET option does not show in the input option for the file
name, click on the arrow key to the right of the option. A list of existing
meteorological file names will appear. Select SMET001.MET. Please
note that, if you did not use the RUN button from the MET interface,
you will not be able to use the MET data since the interface file will
not exist. You will be informed by the interface that the input file
could not be read if you did not create the Rain Block Interface file
in MET.
STEP 6. Familiarize yourself with the screens in the RUNOFF option by moving
through the screens using either the NEXT, BACK or INDEX options.
Refer to Section 5 for more information on these buttons. Certain
important screens are detailed below.
Screens 1 and 2:
The hydrologic simulation starts at January 1, 1988 and the simulation
length is three days. Three time steps should be entered. Screen 2 in
RUNOFF determines the complexity of the simulation. In this case,
snowmelt is not included; default evaporation rates are used; and metric
units are selected. Screens 3 through 8 are grayed because no snowmelt
is simulated.
Screen 10:
This screen gives you the physical representation of the watershed. For
this example, you have a single watershed without a connecting channel.
One inlet is defined as a raingage station in MET for this watershed.
Please note that the raingage station in MET must match the hyetograph
number in RUNOFF. For this example, raingage station number is 1.
Page 37
-------
Windows Interface User's Guide
Screen 12:
You will notice that two infiltration equations are available to you in this
screen: (i) the Horton and (2) the modified Green-Ampt equation The
Morton model is empirical and is perhaps the best known of the infiltration
equations. Many hydrologists have a "feel" for the best values for its
three parameters despite the fact that little published information is
available.
The Green-Ampt equation is a physically-based model that can give you
a good description of the infiltration process. The Mein-Larson (1973)
formulation of the Green-Ampt equation is a two-stage model The first
step predicts the volume of water, which will infiltrate before the surface
becomes saturated. From this point onwards, infiltration capacity is
predicted directly by the Green-Ampt equation. This equation is
applicable also if the rainfall intensity is less than the infiltration capacity
at the beginning of the storm. New data have been published to help
users evaluate the parameter values (e.g. Carlisle et al. 1981) Both
equations require three different coefficients. The user will be required
to enter these coefficients in Screen 13. The Windows interface has an
additional function to help users with these coefficients. Depending on the
equation selected by the user, definitions of each of these coefficient will
appear when the user clicks on the appropriate variable.
For this example, the Green-Ampt equation has been selected. The three
coefficients are 4.0 for the average capillary suction of water, 1 0 for the
saturated hydraulic conductivity of soil, and 0.34 for the initial moisture
deficit for soil.
STEP 7. Submit the RUNOFF input file to the SWMM model for execution by
clicking on the fcUN button. An icon will appear on the bottom of the
screen with the words SWMM MODEL EXECUTION on the icon
When the processing is complete, the output will be shown in the default
output file viewer. View the output carefully and see how the SWMM
model functions in this screening level example. Press the ALT/F4
sequence to exit when you are through. You will be returned to the
RUNOFF block. Press the ALT/F4 sequence again until you are back at
the SWMM main menu.
Page 38
-------
SWMM Windows Interface User's Guide
6.2 Example 2 - Steven's Avenue Drainage District in Lancaster, PA (MET,
RUNOFF, and TRANSPORT)
The 67 hectare Stevens Avenue Drainage District in Lancaster, Pennsylvania is a
relatively steep (average slope = 0.046) combined sewered catchment with its overflow
tributary to Conestoga Creek. It has been the site of intermittent monitoring activity
since 1972 due to its selection as the location of a swirl concentrator as an EPA
demonstration grant. Although several storms were monitored prior to construction
activities, the measurement technique was by use of a Manning's equation rating curve
for depths in a supercritical How pipe section ("manhole 51" of SWMM
schematization). As a result, measured flows (at 1.5 minute intervals) are very "flashy"
and erratic; 6-min averages have been used in the SWMM calibration using the storm
of November 28, 1973, taken from the EPA Urban Rainfall-Runoff-Quality Data Base
(Huber et al., 1981). Further information about the catchment and sampling is given
in the Data Base report and by Heaney et al. (1975). Quality concentration data have
also been used for SS, BOD5, and COD calibrations using the same storm. Artificially
high COD values are input at selected manholes to produce dry-weather flow COD
values since the dry-weather flow generated by subroutine FILTH cannot generate any
COD. 7
This watershed is a complex drainage system and is divided into 29 subwatersheds and
35 channels. There are 15 inlets in the drainage system. Seven pollutants are included
for water quality simulations: (1) Total Solids (TS), (2) Total Suspended Solids (TSS),
(3) BOD-5, (4) COD, (5) Total Coliform, (6) Ammonia nitrogen (NH,-N), and (7)
Total Phosphate (T-PO4-P). Each subcatchment supplies one of five land uses: single
family residential, multi-family residential, commercial, school, and parkland. The
storm of November 28, 1975 with a rainfall duration of 40 minutes is used in the
simulation. This example shows you the use of MET, RUNOFF, and TRANSPORT
The steps and the sequence of blocks that you must go through for this example run
explained below:
are
STEP 1. Select the SWMM Windows Interface option from the main SWMM menu
and select the MET option.
STEP 2. Select the example MET data that has been created for you by clicking on
the FILE option, followed by the QPEN option. Select the first file listed:
SMET002.MET. The file will be loaded into the MET interface. Move
through the screens and familiarize yourself with the MET option. Use
the help information available to you through the HELP button to answer
Page 39
-------
SWMM Windows Interface User's Guide
any questions you may have about any prompts. Next, click on the £UN
button. MET will then generate a Rain Block interface file. You must
have used the RUN button before you may proceed to the next block in
SWMM.
STEP 3. Exit the MET option by pressing the ALT key and F4 function key. You
will be returned to the SWMM Windows Interface menu. Select the
RUNOFF option.
STEP 4. Click on the £ILE option, select the QPEN File option. A list of Runoff
Input Files will appear. Select the RNOFF002.INP file for this example
run. Once you select this option, the parameters for this example run will
be entered from the file. The first screen for the RUNOFF interface also
allows you to enter the Meteorological Input file. If the file that you
created for the MET option does not show in the input option for the file
name, click on the arrow key to the right of the option. A list of existing
meteorological file names will appear. Select SMET002.MET. Please
note that, if you did not use the RUN button from the MET interface,
you will not be able to use the MET data since the interface file will
not exist. You will be informed by the interface that the input file
could not be read if you did not create the Rain Block Interface file
in MET.
STEP 5. Familiarize yourself with this input file and the screens in the RUNOFF
option by moving through the screens using either the NEXT, BACK or
INDEX options. Refer to Section 5 for more information on these
buttons.
Screens Six through Eight and Eighteen are controlled by the selection of
water quality simulation and will become available for data entry when
you select the water quality simulation option on Screen 2. You will be
required to enter all the input values related to the water quality
simulation. For water quality variable estimates, the user should read the
file called README.2ND that is supplied with the SWMM 4.2 model
released by the EPA (it will be in the SWMM directory). This file has
more infOitnation on the sample uata files.
You may easily change a row of values in an array screen using a feature
available within array screens (screens where the same variable requires
a row of entries). If you click on the variable name in these screens, you
will be able to access an arithmetic function that allows you to add,
Page 40
-------
SWMM Windows Interface User's Guide
subtract, multiply or divide for any single or range of values for this
variable. You may therefore change all zero values for a variable to a
single default by adding the default value that you want to all the zero
values in the array.
STEP 6. Submit the RUNOFF input file to the SWMM model for execution by
clicking on the £UN button. An icon will appear on the bottom of the
screen with the words SWMM MODEL EXECUTION on it. If you click
on this option, you will see the processing of the DOS SWMM model 4.2.
When the processing is complete, the output will be shown in the default
output file viewer. View the output carefully. The Runoff Block has
generated 15 inlet hydrographs in a file named RNOFF002.INT. This file
is used as the hydrograph and pollutograph input file for the Transport
Block. You are now ready to move to the next and final block in this
sequence, the TRANSPORT interface.
STEP 7. Exit from RUNOFF by pressing the ALT key and F4 function key
simultaneously. Select the TRANSPORT interface from the SWMM
Windows Interface Menu. You will be taken to the Transport Block.
STEP 8. Select the transport input file for this example by clicking on the f ILE
option, followed by the QPEN option. Select the TRANS001.INP file.
The first screen in the TRANSPORT interface also contains the option for
the selection of the Inlet Hydrograph file. RNOFF002.INT, which is the
file that you just created in the RUNOFF Block, should be the default file.
Please note that, if you did not use the RUN button in the RUNOFF
interface, you will be able to use the data since the interface file, i.e.,
RNOFF002.INT will not exist. You will be informed by TRANSPORT
that the input file could not be read if you did not have a RUNOFF
interface run. In this file, seven constituents (pollutants) have been
simulated. However, since the TRANSPORT is limited to a maximum of
four constituents, we will select only BODS, TSS, Total Coliform and
COD for this run. Please note that the CUNTT and TYPE UNIT variables
on Screen 4 have been grayed since both units will be the same as that
entered earlier in the RUNOFF block.
Sewer infiltration inflow and dry-weather sewage inflow are simulated in
this example. You have to enter the number of pollutants in Screen 2
only if the RUNOFF interface file has been selected, as is the case for this
example.
Page 41
-------
SWMM Windows Interface User's Guide
Please note that Screen 3 is a critical screen in this block since it contains
the parameters necessary for describing a complete sewer system. The
process of describing a complex sewer system can be difficult. The
process can be simplified by using the following structured approach.
First, identify the non-conduit elements such as manholes and conduit
elements, e.g., channel/pipes. Next, assign a number to each non-conduit
and conduit element. For this example, the sewer system contains 19
manholes, one lift station, one flow divider, and 24 channels. Manhole
50 is an outfall.
STEP 9. Use the NEXT, BACK and INDEX buttons along with the HELP button
to move through the screens and familiarize yourself with both the
TRANSPORT block and with this input file. When you have done so,
submit this input file to the RUN button. The SWMM model icon will
appear in the bottom of the screen with the title SWMM model execution.
When the processing is complete, you will be asked whether you wish to
see the output file that has been created. If you indicate YES, you will
view the output file using the Output File Editor. Examine the output file
carefully and press the ALT/F4 sequence to exit when you are through
You will be returned to the TRANSPORT block. Press the AJLT/F4
sequence again until you are back at the SWMM main menu.
6.3 Example 3 - Simulation of a Simple one-Pipe System with Two Manholes
(USEHP & TRANSPORT)
We are simulating a simple one-pipe system with a small slope and water quality for
a Transport run. The one-pipe system has two manholes. The first manhole is
specified through the USEHP interface. The constituents TSS and BOD5 with decay
are simulated without scour/deposition. A user-supplied hydrograph and two
pollutographs for inlet number 1000 are shown in Table 6.4 below.
Page 42
-------
SWMM Windows Interface User's Guide
Table 6.4 User-Defined Hydrograph and PoUutographs in USEHP
Time
(hr)
0
1.0
2.0
3.0
24.0
Flow
(cfs)
1.0
100.0
1.0
1.0
1.0
TSS
(mg/L)
10.0
100.0
10.0
10.0
10.0
BOD
(mg/L)
10.0
100.0
10.0
10.0
10.0
The steps that you must follow for this screening-level example are explained in detail
below:
STEP 1,
STEP 2.
STEP 3.
STEP 4.
STEPS.
Select the SWMM Windows Interface option from the main SWMM
menu. Next, select the USEHP option.
Select the example USEHP file that has been created for you by clicking
on the OLE option, followed by the QPEN option. Select the first file
listed: USEHP002.INP. The file will be loaded into the USEHP
Interface. Move through the screens and familiarize yourself with this
option. Use the help information available to you through the HELP
button to answer any questions you may have about any prompts.
Compare the input to Table 6.4 above to make sure that it is the right file.
Next, click on the BUN button. USEHP will then generate the USEHP
interface files as input to the Transpor Block. You must have used the
RUN button before you may proceed to the next block in SWMM.
Exit this option by pressing the ALT key and F4 function key. You will
be returned to the SWMM Windows Interface menu. Select the
TRANSPORT option.
Click on the £ILE option, select the QPEN File option. A list of
Transport Input Files will appear. Select the TRANS002.INP file for this
example run. Once you select this option, the parameters for this example
run will be entered from the file. The first screen for this interface also
allows you to select the USEHP file created before. As explained in the
introduction to this example, this is a simple system containing one pipe
Page 43
-------
SWMM Windows Interface User's Guide
and two manholes. The first manhole is the inlet that was specified in the
USEHP002.INP file. The sequence of entering this system is to start with
an inlet, then follow the channel and end with-a manhole, i.e., an outfall.
There are a total of nine screens available to you in this example.
STEP 6. Familiarize yourself with the screens in this option by moving through the
screens using either the NEXT, BACK or INDEX options. Refer to
Section 5 for more information on these buttons. Also use the HELP
buttons for any questions that you might have on any prompt. When you
have completed your run-through, submit the input file to the SWMM
model by clicking on the RUN button. The output file will be displayed
to you when it is ready.
6.4 Example 4 - Basic Pipe System (USEHP and EXTRAN)
This example is obtained from the EXTRAN user's manual described as Example 1:
Basic pipe system. Figure 6.1 below shows a typical sewer system of conduits and
channels conveying stormwater flow. The system consists of nine channels and ten
junctions with one free outfall. In this example, conduits are designated with four-digit
numbers, while junctions have been given five-digit numbers. There are three junctions
or inlets that receive inflows, which will be defined using the USEHP interface. The
total simulation length is eight hours.
Two SWMM interfaces are used in running Example 4. First, the user should select
the USEHP function to specify three inlet hydrographs. The user then should access
EXTRAN in order to select an inlet hydrograph file that has been just generated by
USEHP, and to enter a drainage system and simulation information for a EXTRAN
run. A USEHP001.HP file and an EXTRN001.INP file are the input files for this
example.
The steps in this example are explained below.
STEP 1. Select the SWMM Windows Interface option from the main SWMM
menu. Next, select the USEHP option.
Page 44
-------
SWMM Windows Interface User's Guide
^^^
3
a
§
Figure 6.1 Basic System with Free Outfall
(After Camp. Dresser, and McKee, 1988)
Page 45
-------
SWMM Windows Interface User's Guide
STEP 2. Select the example USEHP data that has been created for you by clicking
on the f ILE option, followed by the QPEN option. Select the first file
listed: USEHP001.HP. The file will be loaded into the USEHP interface.
Move through the screens and familiarize yourself with this option. Use
the help information available to you through the HELP button to answer
any questions you may have about any prompts. Next, click on the RUN
button. USEHP will then generate four USEHP interface files. You must
have used the RUN button before you may proceed to the next block in
SWMM.
STEP 3. Exit the USEHP option by pressing the ALT key and F4 function key
You will be returned to the SWMM Windows Interface menu. Select the
EXTRAN option.
STEP 4. Click on the fILE option, select the QPEN File option. A list of
EXTRAN Input Files will appear. Select the EXTRN001.INP file for this
example run. Once you select this file, the parameters for this example
run will be entered from the file. The first screen for this interface also
allows you to enter the USEHP file. Please note that, if you did not use
the RUN button in the USEHP interface, you will not be able to use
the data since the interface Hies will not exist. You will be informed
by the interface that the input file could not be read if you did not
create the USEHP Interface file.
STEP 5. Use the NEXT, BACK and INDEX buttons along with the HELP button
to move through the screens and familiarize yourself with both the
EXTRAN block and with this input file. When you have done so, submit
this input file to the RUN button. The SWMM model icon will appear in
the bottom of the screen with the title SWMM MODEL EXECUTION.
When the processing is complete, you will be asked whether you wish to
see the output file that has been created. If you indicate YES, you will
view the output file using the Output File Editor. Examine the output file
carefully and press the ALT/F4 sequence to exit when you are through.
You will be returned to the EXTRAN block. Press the ALT/F4 sequence
again until you are back at the SWMM main menu.
Summary of output from EXTRAN:
The first section is an echo of the input data and a listing of conduits created internally
by EXTRAN to represent outfalls and diversions caused by weirs, orifices, and pumps.
Page 46
-------
SWMM Windows Interface User's Guide
The next section of the output is the intermediate printout. This lists system inflows
as they are read by EXTRAN and gives the depth at each junction and" flow in each
conduit in the system at a user-input time interval. A junction is surcharge is indicated
by printing an asterisk beside its depth. An asterisk beside a conduit flow indicates that
the flow is set at the normal flow value for the conduit. The intermediate printout ends
with the printing of a continuity balance of the water passing through the system during
the simulation. Printed outflows from junctions not designated as outfalls in the input
data set are junctions which have flooded.
The final section of the output gives the time history of depths and flows for those
junctions and conduits input by the user, as well as a summary requested plots of
junctions heads and conduit flows.
Page 47
-------
SWMM Windows Interface User's Guide
This page is intentionally blank.
-------
Windows Interface User's Guide
APPENDIX A:
SWMM WINDOWS INTERFACE DESIGN
This appendix contains the structures and variables for the five window interface
portions of SWMM. There are five tables in this appendix:
Table A.I Input Variables and Screen Sequence in MET
Table A 2. Input Variables and Screen Sequence in RUNOFF
Table A.3 Input Variables and Screen Sequence in USEHP
Table A.4 Input Variables and Screen Sequence in TRANSPORT
Table A.5 Input Variables and Screen Sequence in EXTRAN
The screen design for the interfaces that are the same as the SWMM Model 4.2 blocks
(RUNOFF, TRANSPORT and EXTRAN) provide the following information:
I. The variable name for the model block in SWMM (if there is one),
2. the description of the variable
3. SWMM ID
4. screen number
5. control number
6. control type, item, range, default, and unit.
You are therefore able to match the Windows Interface variable name with the SWMM
Model Variable names, see where it occurs in the interface, read a description, see
what type of variable, the unit type and the range, all by referring to the table for the
block in which you are interested.
For those for which there are no corresponding blocks in SWMM (MET and USEHP),
the following is provided:
1. Screen Number
2. Variable Name
3. Definition of the variable
4. Unit Type
This will give you all the information about each variable k the interface. Please refer
to Sections 2 and 3 for more general information about SWMM and the Windows
implementation.
Page 49
-------
5VWA/ Windows Interface User's Guide
Table A.I Input Variables and Screen Sequence in MET
i
J
!
|
J*
1 Deecnplioa of lau nm
}
£
I
2
1 lapm amlnomto|icd aala aa*ta cttor ia U.S. uaiu or |
e
i
j
I
'i
•8
j
s
1
^
1 NaaaSer of aala valaaa for pracipMalwa oa Scraea No. ]
4
5
i
| Tiaw ialervd for aiafte aveal aaowawfc uaaibiioa
i
*
1
Naater of valaaa for air iMaperanjra oa Scraea No. 6
I
j
i
i
\ Niuaber of oala valaaa for TEMP Data Table oa Scraea
4
a.
1
ii
-
4
\
§
j
STATION
"
Aa Micfer for to Jaliaa aala ia to fonaal YYDDD
U)
a
J
3
1
[ A red muaber for to eaytiaw boar fiuai audaifbl
at
1
i
<
i
4
a
A red aaaaber for to liaat iaicrval botwoca praclpilalKN
vMiabk liaas ialcrvd ia dkwMai)
THISTO
1
i
"I
i
j
i
'i
1
i
i
1
1
1
1
1
<
;
!
f
!
1
!
«
1
I
i
~
Aa iaieicr for to Jaliaa elate ia to fonaal YYDDD
a
J
'i-
4
j
j
.
MAXTEM
4
j
j
i
i
z
I
*
I
j
I
1
f
i
i
a.
Ul
_
j
1
i
I
1
f
f
i
i
p
WINDSPEE
-
~
f
z
3
a
A red aaaaber for air Iraaj^rataia for uagle eveal «>wi
i
-
-------
Windows Interface User's Guide
_
Table A. 2 Input Variables and Screen Sequence in RUNOFF
•3-3-3
555
u u u
999
A * M
•I
CO :•* O— <•* n » O O O — O O O
* * 188
^ 3 «s » • .
• n *» ^ A —
c 66600 A o* o* o o" o" o —
a. - u u u
>«
•
5: • • : • '• '',''••
M - «N n « i0;tfl.uj e r* ( . . (DioifOt •- rMin:vno.«>p«!ao « o - *N
0; , ..'•••-•';'' . - -•*-
8; ' . : ' ' : i • ! • .1 ,
< eo:ateD:0!aaiaiia ' S:2'3 CD aiaiaiaia1 e
' ' : ' ; 1 i ! . • : :
i •... l i ! : III i
S e § "a • ! : ; ; S : • i "S1
u § .-c • ; ' :* : ' . • • ^.
ji : 1 2 * ' : 5 i| I il»i
ijiilir 1 ' !| , IP bjJlLi i :ll
2>OC 3!2i«fliJ5 O 1
-------
Windows Interface User's Guide
c s s =
r — £ 1
sis
• 0 •
J * J
•* c *
*r .= -a
3 O
o o
o - o
o — o o o o
o o a o
o o —
o o
o
9 o
o o
A A
eD;o>,O:
eo at,
UIUI .Ul IU
eni
U!
!!
n
li *' 5l 1 *
E i •*"
SliS;
*"—•£!
Ij
'll
i
- 3
i
8 o ft, §i S c. f'SiS .6 o 2
Sl w'5i°iSlr i^S!0 5'«'5
c >
u
J'I> :*-ui t>u
ill 'jsill :i;8
1 J —
:& ii:
!$
w
I fr
-------
SWMM Windows Interface User's Guide
o o **
® n
O O O O S 3 O
o o o o o c
o — «N
O — «N O — r^•^»r»if^-^»ri»ip«
i
• i 1 • i ' I I
i • i I i
gl^ ^!^i !„!„;„(,.,
• n
i-'
•6 Si IB
Is:s
in
ill
1
<3
LI;
i!£lZ;Zlui2!2i>!3
-------
Windows Interface User's Guide
Ml t/l
> >
•5 -5
5 3D 35
o o o o
o o o o o
o o o o o
o o o
o
«N r* T
O
fi-
I ' i
'£!
I I !
I ; i
! • ! !
III!
i i
i
II
i
I
III
il
.
liilai
.' *'
't'
.Ol '
•1-21
:U
Si
i'i
v|i5:|J5i5
null
Page 54
-------
SWMM Windows Interface User's Guide
OO
oo
O o o
on-
o «-
••' CM I -**»t /Pipa Tabto
AME
HA/INLET f
YPE
rapezoi
ircular
z
3
fl
-
i--4
{
„ *
* S pi
55
-------
SWMM Windows Interface User's Guide
IJ*f || HI! r-
5 s s |
£
5
ooooooooooo oo ooooSo
Q
0 - 0 -
•
1 5 =-
a
M>
E - i i ' i . • ' - ' i . : : '
» - *,,« «.,a.:io-r*,« « 2:z:2;2'3i ' — « «' , ,-»• •e:«J^:«.o> o
5> • • , . . . . ! • -. ; i i : i . ' '""I -:-;—-:---
w « r:s:z:x r:r:x:z:x.z:x;x:r;r! x!x'x!x z ' ?!?!?!5!S'5'
i ' i ill! i i i 1 i ' .
Ml! ! i ! i ! i i ! i i
1 • : • • i ' i •• i i ' i ! I ' :
• i i . \ •••..- ! ; ; : ; ; ! ; i
1 • M M i : ; : i ; ! i ; ; : ;
1 , ; ! i 1 ! : . ; ' i . : i ! . ' :
I 4 i i = :•.•' 1 1 ! 1 i M : i
"' '3 i . ' • '* : • < •':..,
1 2: | : . . • i
* j: :*" ' • ; : ; . .
<• « ' • . •: • '
5 * ' Si ' - ' ; :
:« 1 : ' '
1 1 : 1
•l| I* ; i ; a; -• . . , ! .
II III JJiiii,;!
. • • : j Mi ! • . : M i M i
1 : MM M. !. • ' M [ ' | ! |
!« ^ iio = s^i 2ii;Siii i > > ?•! i M> i !
IB •.'liiiliiiniHlSlMllir :| !»i«iu^
Page 56
-------
SWMM Windows Interface User's Guide
i
•
• £
c <
O <
^
9
OB
J
o
%
9 m«
WJ-X'X
i ,
1 1
Description
GEXPON
CHCOEFF
i
*i . . «
> S 5
•
^
—
5
3
l
e
s
r»
e
=
<
c
r
t
X
kU
(J
S
i
3 C
3 C
IO
:x
1
•
GCCOEFF
3
— —
1 s
^ ^
•£
3 C
3 C
i
X
1 j
PROSITY
i
§"* V "* w (j {j
B _ e » iiii|2|j~~
V S y ' ^* . ^^ *• ^*»
~ i— .S .S 5 s • • • •
•* ^s jj * £ * E
- e E
3OOCOOOOOO OOOOOOOOOOOO
3OOOOOOOOO OOOOOOOOOO«Nfs
^^ ^^
; . : ! • : j i ' . i ! . : • ""
! ' : ' ; ! ! : i : • ! 1 , : . ! ' ' ! ' • :~ ""
!pi!«nir»i«ir>i^;^i»!» '•. •'!•''' • ! .
;x:x:x;x:x:xix:x.x ; r:r:±:r:=:=:r:r: jr; r-r- «
1 ! i ! ; ' ' , • i i i 1 • • i ;
Mi ! ' ; ! 1 ! :
i ! ' ^ : i ' . . : ! I ; i : ; i i
j ' • . i i i i J ' . t ! C |
i !' ' ' : ' 1 ' • ' ' 1 ' ' ' < '*
' | ' t j ' 1 ' . ! ^S |
'. \ , \ . i •*!
' ' : ! -: ' ' ' ' ' • : : • •!
i ' i • • ' S'
ii j . 31
i i ' : • l ' : i ! : i : -S
• i ; 2 ' ; ' i ^''
' • 01 ''.'.:' : 5!
: I .. ': ; : : ' . . i
. 1! ' 1
S oi, i jll£|i(!iicl i II If
i^i^ls^ ^lii§Iilii$ g i* II
1 ! Ill
i I i 1
1 '. 1 ' • 1 1
i i • .-.—-. • • '!
• • .•';-.*? s « i.! a.
1 | • i ; s; z »' i "• - i
^ri;§i2!5!iS ; illhll! 1 ii ;
Page 57
-------
SWMM Windows Interface User's Guide
.
£ S •* U U — ;j .
5 « J • J •
. h *i.
i i 1
O O O oooooooo bbobb o c
p p p o o
bbobb
b b b b b
: i i ! •• ' !
1 • i i • : : ; ; , ; : :
• . : M I • i 1
' i • ' ; ' > ! : i ! M '
Mi |! M. | lih!
! M : M M ; I
1 ' i '
i i ' • .
i i ' • : ! ' ! i ' : ; ' •
: : • • '_
'• ' '
; ' ' :l! ' ' ; li
J5 ; • i .»-! ;
5 ' ' ! '' 51 '
' 2 M • nl '
C ; ; j ; Cj , . .
i id il
iillfllS! !i!hiiil I!JH
PagcS*
-------
SWMM Windows Interface User's Guide
*
I
oooo o oo oo
000
!l
s
O • :0»!0};0»! A. O)l AiOtlOHAlAiOtiaiOl . O:O.
S • ; : ; I * : • ; : : i i ! • ' i ! i • : •
8: : ! ! i ! 1 j | , 1 ' j— 1 ' e* « i«N« ;
3'3'3> a OIB oj.ojiflD.B'B >a: • ,8:2: ' ' | '2:2 '2'
1 M I j I i |
' ' i 1 i j i ; ! ' : S
. : : ! : : !
: i ! . ' i ' ,i5
! ; • i i ' ! •' ! = ' .2 : ' ' S
• : ' i • : - ; ; : i ; ..: ' i I
2 : ; : ; : : i i : ! ; ; , ;!. ; . • 1
o ; . ' , • i ! i : *H II i
r'-! I " !': ti: if« ' !
2' • : . o> «. . i 16 ^— : 3| £
1 ! i ; !|;1 : >. llil* I' -5
® s ' ;?:'i-| 5>.1.5.S:*ii f1!^- s I Q ^' i! z
ill 1 i^HiMl^fpffUli fija 1 f
I "I 1 ^nipHiiifitiifi, li|| i i
a: i i 111 Jii^J'lIilsloi'J s t !^ : li&S Ji 5
1 ! ! ; ' : i i =c ' i ;
1 ! l!i : 1 C C ; i
s » ! ! i • , j Hi
Ihs il i ' ! ! - -j §1
1 * * I : ' ! ! i ii§ 5 s ;i
>' c c i I' i I ! 's 5 i!
-------
SWMM Windows Interface User's Guide
Page 60
-------
Windows Interface User's Guide
Table A.3 Input Variables and Screen Sequence in USEHP
H
1
I
1
>
J^
j Deacnptiua of Uus OM
I
—
a
i
|
i
M
3
.9
j
P
Z
:
4
j
f*
i
i
i
!
i
i
s
1
y
1
Number of date poMto to defe* •
pullmofraplM
i
1
j
. -
J
INLET f
(S
!
I
H
|
i
i
1
z
i
•a
-
™
^
^"
?
a
1
I
2
H
2
fc
-
i
£
1
S
GL
«
}
1
a
1
1
o
Ul
'
_
1
2
laid nuabcf wppliad on Scnem 2
IIIHH of day provided on Sciwi 4
II
^
?
u
1
i
1
r
i
i
I
u.
i
i
i
1
i
Coacotfmioji for pottutoM f 1
|
|
-
1
i
]
I
If PM|n||nd JOJ •OtfUIOKMOJ
H
5
I
J«
i
1
5
i
|
$
}
s
i
•a
I
!
C
J
I
61
-------
SWMM Windows Interface User's Guide
Table
i
' <•
1
i
1
A.4 Input Variables and Screen Sequence in TRANSPORT
-s ^ ^
^« (N i
— c —
= it
3 0 gOO^O- 00000 0 000 —
!" r* § o
o o
- — — — o - * -
o o* o' o' o
(N
» ~ U U U O
c
5
— v m. ~
• • ' ,--,;!
: i i 1 ' ' •' • • ' '•• ' '
1 ; 1 i i : ' : '
; i '
1 ' ; . i : : -j .
Hli : ? :f |j ' . ' l! '
iij ijititii ? jj. i fi:
SH fii:Ull|: Hj f .! !i
|»* If**'1':!-!: iiljjl -ff* .?!•;,,,
i • i . i . . . • . . i • . . i . . i . . .
li i: «8!B8! f I-5-- i -fpr
i
i
62
-------
SWMM Windows Interface User's Guide
(ft
o
o o o o o o o
o o o o o — o
O —-
i ! !
• • • !
Z!«N'!
-------
SWMM Windows Interface User's Guide
i
cooooooooao
ooooooooooo
I 5
i s;g.l'§:S;s-si ?•
J.?
-------
SWMM Windows Interface User's Guide
Irrr in
o o o o
— o — o o o o
tfl O O
OOOO O O O
OOOO O O O
o o
o o
,« oj
^;
CD i 9: flO I
o»io»io> «j:
0:0 o a
\
2222 I 222222^
e«if>l|««i|l w ..
OlOlOl O O
i I
,
«< si ;
•1! ;s! :
II *li;|!» I 5:2!
t|i|ii:-si I*
UV))t
> 0 Z O:
^•Z:2'
65
-------
SWMM Windows Interface User's Guide
•
.
i 225 5 a a
— s s ^ £ 5
* m » j*
' N
O O O O O O O
O O O O O O
1
O
1
*-
1
r
*•
u
• U;M
1 I :
: • i • i 1
1 !OI
2 2!2i .1 i .«! • :«: , :eiT™" — JN OHM
.i.J i i ' j i I ! : i 1 i ! • ' '
Blow ' ' • 'a \ '5i • i iSi • 5'SiS
1 j ! i ! M ! i i I i i '
i : ' , j : i : ' ' •
i •(•'!' 1 i : ' i '
I ' i ' | ! i ' | : ' ' i ' ' ; '
M j ' • ! : '•• I ] '• ' , :
: ! i : ! !
• : ! ' i • . : , ' :
1 . • . '
1 •' '. '• \
1 .1 i ' ! '
! • ! ' '
i . . i i ,
! ' 0 *:
*' i *. : • i 'Tl'£' 9 '
«' *• 1 ! 1 ""'I • '
:SI :*«:|lif»,I 11 3 : • '•
siiiiil 1*1 1 1 -IPs i IS'o
:ii!li!Jiiiiiiiiii:sii^il«
; i , i 1 i ; ; ;
11 ! ! i i I HI
-------
SWMM Windows Interface User's Guide
2 5 "«• 2 I -
22 « it *i
* 5
5 5
CO O C O
o o o o o
JJ O O O X)
o 1
OOO
OO
?
o o
I I
^
(N C*! ,
-------
SWMM Windows Interface User's Guide
Ol
(0
I I i
•al
11
I •!
•
!
1
.Si
2!
'*i
it
-,
! SI
I
|
•
si:
i
Page 68
-------
SWMM Windows Interface User's Guide
Table A.5 Input Variables and Screen Sequence in EXTRAN
0 0 -
O —
-------
SWMM Windows Interface User's Guide
_5_
i
o o a o o
o o o o 6
et
o»
o o
o o
. — • -^:u»i ,«o;r*.<
! '. • ! ' i
n rMJ
U
i i i i | I
O! OlOIOiUlo!
I ' !
s
51
'»«.
en Si
iij
i
_
4; f
M
01
'
O
i-2
'*«
§i S' Ol
!f!£;
1 ••
51*0' 5!
scream par juncl
Screens No. 6-tfl
ta
Da
Iii!^(.i!
s
al
io
i:i:J!li
nction
nction
=
Sis
Page 71
-------
SWMM Windows Interface User's Guide
0 O 0 0
o o
o o
j*-'«N:Oi^.KJHO.p»,.ao; 0) o
<8'<'2'
Jirs
^ !
ftiSli
II
§!§
Pflge 72
-------
SWMM Windows Interface User's Guide
y r i i ' -i :
:'i -5;1 «:|i '1 M i = : ;5'1 c
H - *| |;1 ill : : ^ ;i.*l 1
M 8^il til I- : -r- i
a ?l iliiil iT J^l ; * 1 1 8
.J'S s.llii tl *!*. lllli S
i 11 iiiBUrfi IBS, i silfili
1 s |: I»S : IJiJifci^'S'l'J :;i2i25 ^iiilM^i1!
6 • ,>iO ^i4! H..dJ-h- O OiH- O'O
IH H; M? Ill lifl H
> O O ' ' X! Z 1: • < O,» > > > S'ill
-------
SWMM Windows Interface User's Guide
£ E
ESS
5 2
o o c o
o o o -
= 000
o o o -
• .i.
| ! 1 ; 1 1
Mi
o
WiCMUNiWi
oicvr»'«'«!«i«irv«n
M-tt'u..u.i
ICIOl
oo' o
II
ei {I
li
in;
•s.Si
il
•N1
•'•8
2
: •
il
|S!£
.«.
«:'
's
: |?U§!??|
• is!^"n.>-'i*'iS:r!r:>!<
ii*"
ii
-^'
• i C' * '"Ul
|l«:-5t ;|>
^ I ^ 8
i: j!2i£ »
? 0^2 ^i
l
fc 5
n
rs
list
i
74
-------
SWMM Windows Interface User's Guide
J2 -2 -8 nnnn g g EEEE
HI Jijj. ZI ~~
£ E
M
O
! I
tO tfl
<0i<0j p*.r» ^ rx»
»l
x:x:x
z:x,x
'x:x:x:xi 'x:x: 'x:x,x,x!
! i I
x:x!
I
ol
I
i
I . I
I ' !
I I
! i I
I I I
I ! ii
5; i *'fl S
'|! €i 5:5!2!s
• *' o^ ««,«•'«•
.ij:?|;^
I I.I
1
^m > •—• i
C,J
in
I
llll
flop 75
-------
SWMM Windows Interface User's Guide
S 5 S £ S
I
f»l
i
(O r* oo en o
I ! . I
cn-oai , ' i .0101
MINI
iiijju
U :» i : i
' . :8I : ! '
II
1.1
il
I
t\
:!;
If
.JSicn KtH-
>ui
••I . 5, •!
II *^
•SI z-Ml
• ;*!
• .5 :
Si
«!
:
il1^
• §
:*5i,
!§:*;
j: si
!• 31-
s
s
MI
Page 76
-------
SWMM Windows Interface User's Guide
«•
j
fN<
-------
51WA/ Windows Interface User's Guide
This page is intentionally blank.
Page 78
-------
SWMM Windows Interface User's Guide
REFERENCES
Ambrose, R. B. Jr. and T. O. Barnwell, Jr. 1989. Environmental Software at the U.S.
Environmental Protection Agency's Center for Exposure Assessment Modeling.
CEAM, EPA, Athens, GA, Environmental Software 4(2):76-93.
Camp, Dresser and McKee, Inc., "Storm Water Management Model Version 4. Pan
B: EXTRAN Addendum", PB88-236658, Annandaie, VA, June, 1988.
Donigian, A.S. and W.C. Huber, "Modeling of Nonpoim Source Water Quality in
Urban and Non-urban Areas," U.S. Environmental Protection Agency, EPA-600-3-91-
039,'June, 1991.
Heaney, J.P., Huber, W.C., Sheikh, H., Medina, M.A., Doyle, J.R., Peltz, W.A.,
and Darling, J.E., "Urban Storm water Management Modeling and Decision Making,"
EPA-670/2-75-022 (NTIS PB-242290), Environmental Protection Agency, Cincinnati,
OH, May 1975.
Huber, W.C., Heaney, J.P., Aggidis, D.A., Dickinson, R.E. and Wallace, R.W.,
"Urban Rainfall-Runoff-Quality Data Base," EPA-600/2-81-238 (NTIS PB82-221094),
Environmental Protection Agency, Cincinnati, OH, October 1981.
Huber, W.C. and Dickinson, R.E., "Storm Water Management Model, Version 4:
User's Manual," Dept. of Enviro. Enginr. Sci., University of Florida, Gainesville, FL,
August, 1988.
Metcalf and Eddy, Inc., University of Florida, and Water Resources Engineers, Inc.,
"Storm Water Management Model, Volume I - Final Report," EPA Report 11024 DOC
07/71 (NTIS PB-203289), Environmental Protection Agency, Washington, DC, July,
1971a.
Page 79
-------
------- |