-------
Table of Contents
Chapter 1 Programming Changes to
Link STORM and SWMM
Introduction 1-1
Modifications and Additions to STORM 1-1
Refinements of STORM 1-6
Corrections of Original Version of STORM 1-6
Interfacing STORM and SWMM 1-7
Changes to RECEIV, the Receiving Water
Body Module of SWMM 1-8
Revisions of the User's Manuals 1-9
Chapter 2 Sanitary Sewer-Wastewater Treatment
Plant Capacity Evaluation
General Description 2-1
Network Numbering 2-5
Detailed Program Description 2-8
Input Variable Dictionary 2-21
Chapter 3 Cost Evaluation Module
General Description 3-1
Description of the Program
and its Subroutines 3-5
Hardware Requirements 3-8
Additions to the Program 3-8
Sample Run 3-9
Input Variable Dictionary 3-16
-------
List of Tables
Page
Table 1-1 Record Formats for Piles Created by STORM 1-3
Table 2-1 Numbering of Links 2-6
Table 2-2 Renumber'ing of Links After Addition
of Relief Sewer 2-8
Table 2-3 Link Characteristics 2-9
Table 2-4 Sanitary Wastewater Flow Values 2-10
Table 2-5 Cell Characteristics 2-11
Table 2-6 Cell Wastewater Allocations 2-12
Table 2-7 System Geometry 2-13
Table 2-8 Link Capacities and Flows 2-14
Table 3-1 Residential Development Test Data 3-10
Table 3-2 Sample Output: Cost Module 3-12
List of Figures
Figure 1-1 Analysis Framework for Storm Water Runoff 1-2
Figure 2-1 Manipulation of Confluences in a Tree Network 2-3
Figure 2-2 Scheme of Sewer Network for Coding 2-4
Figure 2-3 Flow Chart Sewer Routing Module 2-15
Figure 2-4 Flow Chart of ROUTE 2-19
Figure 3-1 Logic of Cost Evaluation Module 3-2
Figure 3-2 Calling Sequence Program 3-6
-------
Chapter 1
Programming Changes to Link STORM and SWMM
Introduction
This chapter describes in detail the programming changes necessary
to link the rainfall-runoff model STORM* with the receiving water body
module (RECEIV) of EPA's Storm Water Management Model** (See Figure
1-1).*** Additional changes were made in the models to simplify the
preparation of input data and to expand several output formats. The
user may refer to Meta Systems' revision of pages 26-26A and 82-104 of
the STORM User's Manual for a description of the changes required in
input data (see Revision of User's Manual pp. 1-9 ff.).
Modifications of and Additions to STORM
Creation of Hydrograph and Pollutograph Files
to Pass Results from STORM to SWMM
Each of these files is fixed-length with output formats coded in
the program. The user may specify his own logical and physical record
lengths for these files as long as the logical record length is a mini-
mum of 30 bytes for each file. JCL must, of course, be specified for
the creation of each file. Typical IBM JCL for a hydrograph file might
be:
//FT18F001 DD DSN=HGPH.1974,UNIT=3330,DISP=(NEW,CATLG),
//DCB=(...),SPACE=(...)
The record formats are shown in Table 1-1.
* Computer Program 723-S8-L2520, Urban Storm Water Runoff, The
Hydrologic Engineering Center, Corps of Engineers, U.S. Department of
the Army, Davis, California, October 1974.
** Storm Water Management Model, User's Manual Version II, EPA-670/
2-79-017, Cincinnati, Ohio, March 1975.
*** Details of the linkage are described in "Land Use-Water Quality
Relationship," Water Quality Management Guidance Document, WPD 3-76-02,
March 1976.
-------
SUB BASINS
Modified STORM
I
RAIN
SIMULATION PERIOD
NO RAIN
LAND USE
URBAN; NON URBAN
DUST & DIRT
ACCUMULATION
NON URBAN-POLL LOADING
Till
RUNOFF
WASH OFF
Selected
Interval
STORAGE
TREATMENT
Pollutograph
Ll
TOTAL
RUNOFF; WASHOFF
L
SORT ROUTINE
Hydrograph
WATER QUANTITY AND QUALITY ROUTING
DO, BOD, SS, MPN, N, P
Single Hydrographs and
Pollutographs for all subbasins
_ . |
SWMM
Figure 1-1 Analysis Framework for Storm Water Runoff
1-2
-------
Table 1-1
Record Formats for Files Created by STORM
(a) Hydrograph file
Field Field Data
Position Name Length Type
NHOUR
NWS
integer
integer
Description
hour # within
given interval
watershed # within
program loop
Hierarchy*
in SORT
9
13
17
21
(b)
1
9
13
17
21
ITEEM
JSW
INTNUM
CFSOFF
4
4
4
10
Pollutograph
JTEEM
I
JSW
INTNUM
PSPLRT(I)
8
4
4
4
10
integer
integer
integer
real
file
integer
integer
integer
integer
real or
scien-
tific
time of day in hours
watershed # (used
externally)
interval #
flow in cfs
time of day in
seconds
pollutant #
watershed #
(external)
interval #
pollution rate
Ibs/day or
MPN/minute
2
3
1
2
3
4
1
* 1 = high-order.
1-3
-------
One hydrograph record will be generated for each hour of each
time interval modeled per watershed. The number of pollutograph records
generated will be the product of the number of hydrograph records and
the number of pollutants modeled (maximum of six). In our study we
allowed for 125 and 750 records, respectively.
These files are sorted subsequent to execution of STORM in order
to be processed by SWMM. The sort itself is described in Interfacing
STORM and SWMM (see pp. 1-7 ff.).
Use of Time Interval Instead of Rain
Event for File Generation
STORM defines an "event" to occur when precipitation causes runoff,
and performs no computations when runoff does not occur. The occur-
.rence of runoff, however, is a function of several factors and is not
easily predictable by the analyst. It is therefore impossible to assign
by inspection an event number in advance of a run to a given time period.
For this reason STORM was recoded to generate hydrograph and polluto-
graph information for "intervals" specified by starting and ending
times hour, day, month, and year. Up to 20 such intervals may be so
specified. SWMM will analyze one such interval per run.
Calculation oE Erosion on an Hourly Basis
The replacement of the "event" concept by that of the "interval"
necessitated a complete receding of the computation of storm erosion.
In addition, SWMM was structured to accept input only in terms of a
rate; pounds per day at each and every input time. It was therefore
necessary to calculate the amount of soil eroded at each hour during a
requested time interval and convert to the specified rate:
MLU
E = T' *SDR- *d-TEFF) *48000 (1-1)
where E = erosion in pounds per day,
T = erosion in tons,
i = land use type,
MLU = number of different land use types,
SDR = sediment delivery ratio, and
TEFF = efficiency of sediment traps.
Addition of Eroded Material to Suspended Solids
This was done straightforwardly on an hourly basis. The suspended
solids, as all other pollutants, were expressed in pounds per hour and
1-4
-------
multiplied by 24 (except for coliforms, which were expressed in MPN per
hours see below). This paralleled the handling of eroded soil in
SWMM's runoff and washoff module.
Introduction of Coliforms as a Sixth Pollutant
This was done to take advantage of SWMM's ability to handle coli-
forms. Note the change in the format of the input F-2 card on page 88
of the User's Manual. Default values for coliforms are those from the
SWMM User's Manual, page 48:
Land Use Type MPN/gram DP
single 1,3 x 106
multiple 2.7 x 106
commercial 1.7 x 106
industrial 1.0 x 106
open 0
These values are multiplied by 4.5 x 101* to convert to MPN/100 pounds DD.
Then the procedures already in STORM were applied to coliforms. In
developing equation (16f) to parallel equations (16a-c) found on pages
12-13 of the STORM User's Manual, however, it was noted that the coeffi-
cients of MU and MUget as programmed in SWMM's model RUNOFF were 0
(see statements QSHD194 and RNBD35-36) which reduced equation (16f) to
MU _._(t) =P _.-(t)*EXPT (1-2)
colif colif
Accumulation of Erosion over the Rain Interval
Although erosion was now calculated on an hourly basis, the land
surface erosion report already in existence was not abandoned. The
calculated erosion was therefore summed in accumulators for each defined
time interval and a report output identical to the original except for
the use of an interval number rather than an event number.
Change in Output Format for Pollutants
The quality analysis report illustrated on page 77 of the STORM
User's Manual was broken up into two reports (which necessitated the
allocation of another direct access device and, in general, different
device allocation numbers for the generated reports (see pages 26-26A
of the Revised User's Manual). The first report includes columns one
through ten and two new columns described in the section following.
The second report includes columns 11 through 23. The large magnitudes
used in calculations involving coliforms necessitated considerable re-
programming for scaling (since STORM used integer variables for this
particular report).
1-5
-------
The pollutographs also had to be reformatted, although the changes
made were not nearly as extensive as those above. Interval numbers were
substituted for event numbers, and two lines were required to print one
hour's worth of information. In other respects the formats were quite
similar when not identical.
Refinements of STORM
Continuous Calculations of Dust and Dirt
The amount of accumulated dust and dirt at the start of each
"event" and the amount left after washoff is printed for each "event"
as part of the first 'of the two quality reports (see above). These
amounts are calculated by taking the calculated suspended solids before
and after each event, dividing by the ratio of SS/DD, and summing over
land use; that is:
MSLG
DD = £ (P ./F .*100) (1-3)
*-? sus,i p,i
where PSUS and Fp have been calculated as before (see pages 11-12 of the
User's Manual).
Input of Land Use Data Using Acres
Instead of Percentages
It was found that the computation of percentages of area was quite
tedious when multiple runs were made reflecing slightly different land
use patterns. All land use areas are now input in terms of acres and
the relevant percentages are calculated by the program. (See the re-
vised input specifications).
Adjustment of BOD Due to Falling Leaves During Autumn
At the user's option, the computed available BOD during the months
of September, October and November will be multiplied by 1.1, 1.2, and
1.1, respectively.
Corrections of Original Version of STORM
The following errors were noted during our testing procedures.
Some were corrected; others were bypassed.
1-6
-------
The Q-card was required by the program logic instead of being
optional as stated in the manual. We found it easier to input a Q-card
specifying sediment traps with an efficiency of 0 than to change the
code: those who wish to correct the coding will find the task trivial.
Some default options stated in the manual did not in fact exist.
These included those for the variables NWSHD, COEF, and RFU. The source
code was not changed.
Precipitation records generated by a previous run will have been
saved on FORTRAN logical unit 12 (as described on page 29 of the User's
Manual) only if no snowmelt computations were made. If snowmelt computa-
tions were made, these records would be available on FORTRAN logic unit 11.
A coding error resulted in the reading of an incorrect number of
D-2 cards when the year in references was an even non-leap year. (Exam-
ple: 1974)
The argument of 80 used in the call to the subroutine CORE (which
replaced the ENCODE-DECODE statements not compatible with IBM FORTRAN)
was changed to 4. The original erroneous argument resulted in unpredict-
able results due to destruction of computer code.
Interfacing STORM and SWMM
This part describes the routines required to sort the hydrograph
and pollutograph files generated by STORM for input to RECEIV, the
receiving water body module of SWMM. Since development and testing took
place on an IBM 370, IBM's SORTD routines were used. Following are the
required input cards:
1+
1. //EXEC SORTD, REGION=72K
2+ 3+
2. //S .SORTIN DD DSN=filenamel , DISP=SHR
2+ 3+
3. //S.SORTOUT DD DSN=filename2 , DISP=(NEW,CATLG), DCB=(...),
SPACE=(...)4+
4. //S.SYSIN DD *
5+
5. SORT FIELDS=(17,4,A,9,4,A,13,4,A),FORMAT=FI,SIZE=E125
6. END
7. /*
+ Numbers refer to explanatory comments.
1-7
-------
8. same as 1.
3+
3+
9. same as 2 except DSN-filenameS
10. same as 3 except DSN=filename4
11. same as 4.
5+
12. SORT FIELDS=(17,4,A,1,8,A,9,4,A,13,4,A),FORMAT=FI,SIZE=E750
13. END
14. /*
Comments
1. Region size may be varied at the discretion of the user.
2. The procedure-name S (as in S_. SORTIN) is installation-dependent.
Check with the installation to ascertain the procedure-name of
the sort-routine and substitute it for the S.
3. Filename^ (where n=l,2,3, or 4) is supplied by the user and
may be any data set name that abides by IBM's conventions.
The four files are hydrograph and pollutograph input and out-
put. The first sort illustrated is that of the hydrograph
file (cards 2-7) ; the second, the pollutograph file (cards 8-
13): they may be executed in either order.
4. In Meta Systems' test runs, files containing approximately
60 hours' worth of data required about three tracks on a IBM
3330 for the hydrograph file and 17 for the pollutograph file.
5. Ennn is the estimated number of records in a file and may vary
considerably. For hydrograph files, Ennn * number of hours x
number of watersheds; for pollutograph files, Ennn =
Ennn, , . x number of pollutants.
hydrograph
Changes may have to be made to these cards if the sort routine is
to be run on a non-IBM system. The files and the sort hierarchy are
described in Modifications and Additions to STORM above.
Changes to RECEIV, the Receiving Water Body Module of SWMM
Meta Systems' revision of the receiving water body module allows
it to accept hydrograph and pollutograph inputs generated by STORM (see
above). This input may, at the user's option, be multiplied by arbitrary
constants or delayed for an arbitrary number of hours, or both. The
+ Numbers refer to explanatory comments.
1-8
-------
input files contain data for many different time intervals determined by
the user when the files were created. Only one such time interval may
be selected for analysis per run of SWMM.
The input hydrograph file is equated to FORTRAN logical unit 18
and the pollutograph file to unit 19. Changes in the directions for
the preparation of input data are detailed below.
Revisions of the User's Manuals
Following is a compilation of revisions to the User's Manuals for
STORM and SWMM. Only those pages which incorporate changes to the
instructions for data preparation have been included. The changes have
been typed on blank pages at the position of the original statements in
order to avoid any problem of identification. The number on the bottom
of the page denotes the original page number of the respective User's
Manual.
1-9
-------
FORTRAN Logical Unit
IN (Input variable)
(see Cl card, P. 84)
ITAPE (Input variable)
(see Dl card, P. 84)
11
12
Option
Input precipitation file if not
read from cards
Input temperature file if not
read from cards
Working storage snowmelt
computation. May be used as
permanent storage for input
precipitation file iff ISNO = 1
(see Bl card, P. 82)
Working storage precipitation
data. May be used as permanent
storage for input precipitation
file iff ISNO = 0
STORM: 26
1-10
-------
13 and 14 Output files for Quality Report
15 Output file for Sediment Report
16 Output file for Pollutograph Report
18 Working storage hydrograph
19 Working storage pollutograph
Files 18 and 19 are subsequently sorted and passed to SWMM (Storm
Water Management Module) for later use.
STORM: 26A
1-11
-------
It is only necessary to use a maximum of seven tape/disk units at
one time. The rainfall/snowmelt computations need not be recomputed
for each job. If no snowmelt computations were specified, the working-
storage file on unit 12 may be saved and used for input on future jobs.
If snowmelt computations were specified, the file on unit 11 may be
saved. The input data would then specify such direct input on unit 11
or 12 and units IN, ITAPE, and 12 (or 11 they would then be mutually
exclusive) would not be necessary. The Input Description, Exhibit 3,
describes the variables necessary to accomplish these tape/disk options.
STORM; 29
1-12
-------
Bl Card (required)
I/O Unit
Field Variable Value Required
0
1
NWSHD
ISNO
NONURB
ISED
IQUAL
IEVNT
INTNUM
Bl
0
1
0
12
Description
Card identification.
Number of watersheds to be analyzed.
Calls for NWSHD sequences of E through
T cards as required.
No snowmelt computations are desired.
Omit D cards.
11 Snowmelt computations are to be made
using D cards.
Nonurban watershed computations will
not be made. Omit H, J, and K cards^
Nonurban watershed computations will
be performed using H, J, and K cards
as required,
15 No land surface erosion computations
will be made. Omit * through R cards.
Land surface erosion computations will
be made using * through R cards.
13,14 No water quality computations will be
made. F2 cards are still required even
though blank.
Water quality computations will be made.
16 No detailed analysis (pollutograph) of
selected events is desired. IPOLMX
(T2-3) will be zero.
Detailed event analysis will be required,
IPOLMX (T2-3) may be greater than zero.
18,19 Number of intervals to be saved on
hydro/pollutograph files (maximum =
20).
STORM; 82
1-13
-------
B3 Cards (required if INTNUM, Bl-7, > 0)
Intervals for which hydrographs and/or pollutographs will be stored on
disk.
Field Variable Value Description
3 INTST + Date (yymmddhh) of start of interval.
4 INTEND + Date (yymmddhh) of end of interval.
Supply n B3 cards where n = INTNUM (Bl-7).
STORM: 83
1-14
-------
Unit number for precipitation data tape/
disk. No C2 cards are read. Format is
same as on C2 card.
Previously generated unformatted binary
tape/disk rainfall/snowmelt records will
be used on FORTRAN logical unit 11 or 12.
(See Bl-2) Omit C2 and D cards. This is a
time saving option in that the basic preci-
pitation and temperature data need only be
processed once. Upon generation of a satis-
factory rainfall/snowmelt file, the tape/disk
on logical unit 11 or 12 should be saved for
future use under this option.
STORM: 84
1-15
-------
1 Max/Min temperatures are on D2 card.
COEF + Degree-day melt rate coefficient.
STORM: 85
1-16
-------
3 MXLG + Number of land use groups modeled (Maxi-
mum = default = 5). MXLG pairs of Fl, F2
cards will be read for land uses as defined
on Fl card.
4 EXPTE + Exponent for dust and dirt washoff, equation
(15) in text;
- e-EXPTE*At)/At
*Default = 4.6
5 REFF + Street sweeping efficiency (ratio of material
picked up to the total material on the street)
as a decimal fraction (default = 0.70).
6 JSW + Watershed number. If > 1 watershed, their
numbers must be in ascending sequence.
STORM: 86 + 86A
1-17
-------
0 E2 Card identification,
1 AREA + Total area, in acres, of the watershed.
Factor by which KRAIN, rainfall array, is
multiplied to obtain average rainfall
RFU +
over urban area.
IQU 0 No hydrographs are to be input on G cards.
STORM; 87
1-18
-------
LAREA + Area, in acres, of this land group. Never
enter a value of 0 if erosion is being
modeled; rather, eliminate the pair of
F1-F2 cards and reduce MXLG (El-3) accor-
dingly.
NCLEAN + Number of days between street sweeping in
each land use group (see Note 1 for default
value)
LEAFSW 1 Available BOD will be increased in September,
October, and November by factors of 1.1, 1.2,
and 1.1 respectively to account for falling
leaves.
0 Available BOD will not be increased.
STORM; 88
1-19
-------
3-7 FRACTN(L,2-6) + Pounds of settleable solids, BOD, nitrogen,
and orthophosphate, and MPN of coliforms
respectively per 100 pounds of dust and dirt.
See Note 1 for default values.
STORM; 88A
1-20
-------
HI Card identification
CN + Runoff coefficient for nonurban area; water
excess will be multiplied by this factor in
order to determine runoff.
STORMs 90
1-21
-------
m. Q Card (required)
Sediment trap data
Field Variable Value Description
0 ICG Q Card identification.
3 TEFF + Trap efficiency desired for the sediment
'detention reservoirs.
STORM: 95
1-22
-------
R. Card (cont.)
Field Variable
PALU
XLTH
XS
Value Description
+ Area, in acres, of this land use cate-
gory that has the soil and slope proper-
ties to be defined on this R card. PALU
values are summed for all R cards speci-
fying the same land use and if this sum-
mation is less than 100 percent R cards
only sample land use in the basin and
that sample will be expanded to include
the entire basin by the program.
+ The length of lot in the direction of the
ground slope expressed in .feet. This must
be an average value for the percent of
land use shown on this R card. (Default=
150 feet).
+ The lot slope is entered in percent and
for those lots sloping away from the
street it should be a plus value. (De~
fault= 0).
GCOV
This is a cropping-management factor in %
(see the universal soil loss equation).
Its values are identified in that refer-
ence. As used here it is a ground cover
factor to ratio erosion from land having
vegetation or some other cover to the
erosion plot values determined by the
equation. (Default= 2).
STORM; 96
1-23
-------
O
2
+
+ . O rH
*.
cn
£
o
rH
rH
O
3
rH
rH
O
rH
tn
X!
rH
*
cy
-p
rd
rl
Q
Q
en
H
ft
cu
0)
co
(fl
2
0
in
<* m
d] o
CH| CD
EH
H
2
CO
0
Q
O
ffl
o
o
tn
EH
W
CO
, i
rH
CO
D
co
H
rH
H
4->
4H
O
O
rH
\
>(
T3
\
XI
rH
O
CO
>1
rd
Q
^
H
id
r(
4->
G
H
O
o
cn
CO
tt)
(V|
k^l
rH
H
s
rd
Q)
CO
D
IT^J
C
rH
fa
0)
rH
cn
rH
CO
1 1
0
rH
X
(N
rH
in
o
0
rH
**o
o
0
{Q
m
CO
o
CO
ro
(N
O
O
cn
to
$
£*"!
rH
.,H
C2
fo
fa
0)
rH
H
4J
rH
s
O
rH
O
i-H
X
[^.
O
O
rH
O
o
[-.
"^
fx.
rH
O
[-^
rH
ro
ro
O
O
CTi
rH
rd
rl
U
r(
0)
g
0
CJ
o
rH
O
H
X
in
^
ro
O
O
*
ro
^ji
o
o
o
ro
!-
r-
\@
^D
^
O
O
CTi
rH
id
rl
}{
jj
CO
rj
fl
C
H
O
LO
O
o
00
^
o
o
o
in
H
rH
rH
rH
H
IT)
H
0
d
0^
»x
rl
rd
CM
^1
o
C
fl)
Sf
STORM;
E
^
4-1
UH
0
l§
G
rd
XI
M
D
in
O
to
4->
U
0)
ft
CO
rtj
C
O
H
P
3
H
rH
0
PU
rl
Q)
P
rd
s
«.
C
o
H
P
id
H
U
O
U)
co
<
co
^
rl
o
s
u
r|
i-H
s
rH
§
u
H
rl
0)
s
0
MH
r^j
Q)
G
H
rd
4->
XI
O
rd
P
id
Q
*
P
J-i
a
s
*.
G
O
H
4->
rd
4J
to
H
C
r|
1
fl!
H
O
M
4->
G
0
U
G
O
H
4->
3
H
H
0
(H
rl
(U
4-1
rd
S
i-l
id
rl
0)
T3
0)
fa
h
W
CU
H
rl
0)
CO
rH
U
M
rd
0)
0) CTi
CH VO
cn
rH i-H
O
JJ r7
G id
O 3
CJ C
rd
G l^
O
H v
4-i in
3 H
H 1
H 0
O
CO
!H id
H
Q
to
T3 Cl)
G 3
Id rH
rd
P >
(0
3 -P
Q H
3
II id
Q fl)
Q Q
+ +
1-24
-------
SUMMARY OF INPUT CARDS
OCf
ECVRT
NOV
DEC
'DEPRS , RECVRT
T JANJ FEBl
MAR I APR* MAY! JUN! JUL I AUG 1 SEP
AREA CPERV CIMP RFU IQU DVU DVUMX WUL ,
HAMEWS
MEV
MXLG EXPTE REFF JSW
JDATE.MAX.MIN.ITEMP in format 5X,I6,2I3,55X,I3
t 5X,I6,2I3,5E
ITAPE IFILE IFREZ IPACK ITMP COEF
ank card indicates end of KRAIN data on cards.
KRAIN in format 2X.I6.24I
t 2X,16,2413
(col. 3-32)
INTST INTEND
I I I
IFILE ISTART IEND I
IFILE IS'
1
NSUMR LEXT LINE LDATE LHR
NWSHD ISNO NONURB ISH) IQUAL IEVNT INTNUM
Titje information for each page heading on this card.
Title
Title
8
10
Note: Bars on left hand side of page indicate where revisions
have been made.
i Required cards. Other cards are required depending upon input options
STORM: 102
1-25
-------
»
blank card indicates end of
I K2 cjrds I I I
.ON
I
I
I
I 1
DQN 1 NDATE
I I
J I
B
I I
I
RECVN
NQ\1
D£(L
1
I
RECVN
JAfl FEBl MAR I APR I MAY I JUNI Jill I Alld SFP
CN RFN IQN
DVN DVNHX
WN.EXPTN,
blank card indicates
G2 Icardsl I
nd of
QU,
QU.
DD FRACTN
IM.NDUS
1
E LARE
2
A FIMF
3
STLE!^
4
1 NCLEA
5
^ LEAF
6
SW
7
8
9
10
Note: Bars on left hand side of page indicate where revisions
have been made.
A Required cards. Other cards are required depending upon input options.
STORi-i: 103
1-26
-------
Comouter
em end-of-job card or another execute
uter system end-of-job card or
card TOiTowed by A cards, etc.
I I
I
I I
NX IPOLMX IPLOT IPRINT.IPRTS .IFRDMX
I
I
I
I
1
PALU XLTH
XS GCOV ECP
SDR
TEFF
I I
PALU XLTH
(S GCOV
ECP
XK SDF
KSP
I
NSG DEPTH
_J I
NSG SLOPE
1
1
MDS MPO MCSC MCSG
I I I I
WF RMI SMEC
Description
of soil series.
I I I I
Comment card. Use as many as needed within sediment
8
10
A Required cards. Other cards are required depending upon input options,
Note: Bars on left hand side of page indicate where revisions have
been made.
STORIl: 104
1-27
-------
If STORM-generated hydrograph/pollutograph input is used, a
data set (input file) must be defined for each. See above
for a detailed description of these files.
SWMM; 273
1-28
-------
If STORM--generated,hydrograph/pollutograph input is used, set
ISWCH(8) = INTNUM, the number of the requested time interval.
SWMM: 280
1-29
-------
Card Groups 22-28. Stormwater Input If STORM-generated hydro-
graph input is used, omit card groups 22, 24, 26, 28, and 29
(note that ISWCH(3) must be set to 1).
SWMMj 283
1-30
-------
If STORM-generated pollutograph input is used, this card group
is omitted.
SWMM: 288
1-31
-------
= 1,Spatially variable rainfall allowed.
Junction inflows computed using card
groups 23-27. Required if STORM- ISWCH(3)
generated hydrograph input is used.
aif both QUANTITY and QUALITY are punched, the program first carries out
quantity, then quality analysis.
SWMM: 289
1^32
-------
36-40 = n, interval number requested ISWCH(8)/
from hydrograph input file. INTKEQ
SWMM; 290
1-33
-------
IF NJSW = 0 ON CARD 5, SKIP TO
CARD GROUP 30.a
IF ISWCH(8) ^ 0 ON CARD 5,
SKIP TO CARD GROUP 23.
SWMM; 298
1-34
-------
Card Variable Default
Group Format columns Description name value
16-20 Multiplier for stormwater
flow, HFACT 1
21-25 Warm-up or delay factor
in hours, IWARM 0
IF ISWCH(8) ? 0 ON CARD
GROUP 5, SKIP TO CARD
GROUP 25
IF ISWCH(8) ^ 0 ON CARD
GROUP 5, SKIP TO CARD
GROUP 27.
SWMM: 299
1-35
-------
IP ISWCH(8) ± 0 ON CARD
GROUP 5, INPUT NTIMST+2
BLANK CARDS, (SEE CARD
GROUP 23 for NTIMST),
SWMM; 300
1-36
-------
21-25 Weighting factor applied to STORM-
generated pollutograph input. PFACT 1
26-30 Delay factor in hours. PWARM 0
SWMM: 302
1-37
-------
IF ISWCH(8) i- 0 ON CARD GROUP 5,
SKIP TO CARD GROUP 40.
SWMM; 305
1-38
-------
Table 8-1 (continued). RECEIVING WATER BLOCK CARD DATA
Card
group Format
Card
columns
Description
Variable Default
name value
KSELCT(l) 0
40 Selection of pollutants to be
anlayzed from STORM-generated
pollutograph input file.
8110 1-10 Pollutant number according to the
following table:
1 suspended solids
2 settleable solids
3 BOD
4 Nitrogen
5 Phosphorus
6 Coliforms
11-20 Second pollutant selected for
analysis
KSELCT(2)
I (max. of 8) pollutant
selected for analysis.
KSELCT(I)
SWMM: 305A
1-39
-------
Chapter 2
Sanitary Sewer-Wastewater Treatment Plant
Capacity Evaluation Module
General Description
Introduction
Much of the network coding used and discussed below is based on
ideas developed in previous work by Meta Systems Inc.* The link network
system is divided into a series of discrete links by defining the two
end points of each to be called nodes according to a set of rules.
A node is defined where:
1. a link crosses a cell boundary;
2. a change in pipe diameter occurs;
3. a confluence of two links occurs; and
4. flows are to be monitored.
It is at these nodes that comparisons of actual flow and capacity will
be made.
Assumptions
Before defining the link types and describing the network numbering
scheme, a few of the assumptions of the model will be presented:
1. The flow capacity of each link is measured in cubic feet per
second (CFS) and is calculated using Manning's equation:
1/2
V = (1.49/N) (H) (S) ' (2-1)
where:
V = velocity in feet per second (FPS),
N = coefficient of roughness,
H = hydraulic radius=(area/wetted perimeter); in our case:
H = link radius (in feet)/2, and
S = link slope in feet/feet.
* "A Program for Simulation of Acid Mine Drainage in a River Basin,"
prepared by Meta Systems for the Appalachian Regional Commission, 1969.
-------
From this:
Q = V x A (2-2)
where:
Q = capacity flow in CFS,
V = velocity in FPS, and
A = cross-sectional link area in square feet.
2. It is assumed that the total wastewater generated within a
cell is uniformly distributed throughout that cell.
3. Each link in the system is assigned a percentage of the flow
generated in the cell in which the link is located'. It may
be found that no drainage links have been allocated to certain
cells. In this case a link (or links) may be chosen or newly
defined so as to receive the cells' flow.
4. This assigned flow drains into the link in a continuous, but
not necessarily uniform, fashion for the length of the link.
5. On the basis of the above assumption, capacity checks will oc-
cur only at the downstream node of each link.
6. Nothing is suggested concerning detailed layout and hydraulic
design of relief sewers. This omission is based on the multi-
plicity of technical factors, many external to the model, which
would play an important role in any such statement. When an
overcapacity flow occurs, the planner, among the many choices,
may select an independent branch of links, or a relief inter-
ceptor. In either case the technical assistance of a sanitary
wastewater engineer will be needed to help determine exact
location, pipe diameters, minimal velocity requirements, and
characteristics.
7. To. account for the temporal variation of flows, we have used
Babbitt's equation* to relate the ratio of peak average flow
to tributary population equivalents:
r = 5/(p)'2 for 1 <_ p <_ 410
and r = 5 for p < 1 (2-3)
and r = 1.5 for p > 410
where p is population in 1,000's and r is the ratio.
* H.E. Babbitt, and E.R. Boumann, Sewerage and Sewage Treatment, 8th
Edition, New York: John Wiley and Sons, 1958; see also Working Paper
No. 3, p. 36.
2-2
-------
8. A peak flow adjustment vector is required for the land uses
to implement sensitivity analysis. By increasing or decreasing
the average flow by land use, the sensitivity of capacity uti-
lization to each land use can be explored.
The following types of links are recognized by the model:
1. Starting link a beginning link of a branch in the network;
2. Continuing link all links lacking the attributes of a
starting, junction, terminal, diversion or pump main link;
3. Junction link the link formed by the confluence of two up-
stream links. The program handles confluences of only two
links. In order to simulate the confluence of three (or more)
links it is necessary to manipulate the model by introducing a
series of confluences, each of two links, as shown in Figure
2-1. The linear distance of link number 3 can be made negli-
gibly small so that the net effect is that of a triple conflu-
ence into link number 5.
Figure 2-1 Manipulation of Confluences in a Tree Network
4. Terminal link final link of the system network, emptying
into a treatment plant or pumping station. Each system must
have exactly one terminal link. Unlike junction links, more
than two upstream links may flow into the terminal link. How-
ever, in order to accomplish this a few restrictions govern:
a. There can be only one discrete, fixed node of intersection
between the terminal link and an upstream link. In general
a system is best arranged with only one link entering the
2-3
-------
Figure 2-2 Scheme of Sewer Network for Coding
LEGEND'
Cell Identification number
Link identification and flow direction
Denotes division of links
a) junction intersection
b) crossing cell lines
c) change in link diameter
d) test points
Denotes a non-fixed point of link intersection
a) diversion links
b) relief links leading into terminal link
2-4
-------
terminal link (as in Figure 2-2), considering only the original
system of links 1-8), with additional links being used to repre-
sent relief sewers.
b. Any additional links draining into the terminal link must
have non-fixed points of intersection; otherwise the terminal
link would constantly have to be redefined as a series of junc-
tion links.
c. The numbering rule that applies to the incoming branches of
junctions must be followed (explanation below).
5. Diversion links a relief sewer designed to carry the over-
capacity flow and a fixed percentage of the full capacity link
flow from the upstream link it intersects.* The percentage
may be fixed such that minimum flow velocities are achieved.
The decision to have non-fixed points of intersection between
diversion links and the upstream link arises from the fact that
the program measures only the end of link flows and thus has no
way of knowing at exactly what point in the link the overflow
occurs. However, this convention serves two functions. It
enables the planner to freely place diversion links in the sys-
tem and measure resulting flow without a detailed layout provi-
ded by the engineer (once the design to place a diversion link
is made then the engineer may be consulted for details). In
addition, as with terminal links, this convention eliminates
the need to divide the upstream link.
6. Pump main link a link carrying into the system flows gener-
ated from an external source, for example from a pumping station.
Network Numbering
Having been defined by type, the links are now numbered in a fashion
similar to that used in the report cited above.** A NEXT vector, contain-
ing the identification number of the next downstream link, and an ITYPE
vector, indicating the type of link, are used in the program logic for
defining the network structure. This method allows for:
1. an arbitrary assignment of identification numbers to the links
except for first links of branches leading into the terminal
and junction links; and
2. an internal network ordering such that link flow capacities and
actual flows can be calculated in one pass of the system each.
* Note: if a relief sewer consists of several links, only the first
link would be designated as a "diversion" link.
** Meta Systems op. cit.
2-5
-------
Links 1 through 8 in Figure 2-2 would have NEXT and ITYPE vectors
as appear in Table 2-1;
Table 2-1 Numbering of Links
Link ID
NEXT
ITYPE
1
7
2
2
4
1
3
5
1
4
7
2
5
1
2
6
0
4
7
8
3
8
6
2
The rules for numbering links are as follows: If there are I links
in the network, link identification numbers must run from i=l to I. The
numbering need not be consecutive except for the first link of the second
branch that flows into a junction link. In the case of a terminal link
with j inflowing .branches, the first link of each consecutive branch from
2 to j must be the next higher integer from the immediate upstream link
of the last branch flowing into the terminal link.
Consider the network system comprised of links 1-8 in Figure 2-2.
Starting with link 3 the numbering proceeds to link 5, link 1, and then
7, which is a junction link. The numbering rule specifies that before
link 7 is examined the next link to be considered must be that one with
the next higher integral identification. In this case the program can-
not route from link 1 to 7 until the left-hand branch is accounted for,
whereupon the branch which starts at link 2 becomes the next link in
the sequence. From link 2 the routines then moves to link 4, and then
to link 7 where the junction is now satisfied because both incoming
branches are completed. Link 7 then leads to link 8 and link 6, the
terminal link of the system.
Data Collection and Input
This section provides an overview of the data that will have to be
collected.
1. For each link the following characteristics are required:
a. link identification number
b. next link identification of next downstream link
c. type link identification of link type
d. diameter in inches of the link
e. length in feet of the link
f. slope of the link (feet per 1,000 feet)
g. Manning's roughness coefficient of the link a default
value of .013 is assigned*
* G.M. Fair, J.C. Geyer, and'D.A. Okun, Water and Wastewater
Engineering, 1969.
2-6
-------
h. infiltration coefficient of the link in gpd/inch dia-
meter/mile a default value of 450 is assigned.*
2. For each cell and each of the four periods (T, T+10, T+25,
T+50), the total population or population equivalents are
required for six land use types.**
a. single family low density
b. single family high density
c. multi-family
d. commercial
e. industrial
f. open-space and recreational,
3. The expected wastewater generation in gallons per capita per
day is required by land use.
4. Peak flow adjustment factors by land use for sensitivity
analysis.
5. Percentage of cell wastewater allocated to each link.
6. The type of unit, treatment plant or pumping station and its
capacity in CFS, receiving flows from the terminal link.
Output
Returning to our original system of links 1-8 (Figure 2-2) we may
find that after running the program for various development projections
an overcapacity flow constantly occurs at link 5, and that the planner
decides to check what the impact would be if a relief sewer consisting
of links 9, 10, and 11 is chosen to remedy the situation. At the same
time a pump main, link 12, is added to help drain some external area
now that the capacity of the system's right-hand branch has been in-
creased by the addition of the relief sewer.
In addition to the necessary new data to be collected, the NEXT and
ITYPE vectors would have to be changed to those as appear in Table 2-2.
* Design and Construction of Sanitary and Storm Sewers, ASCE-Manuals
and Reports on Engineering Practice, No. 37, 1970.
** The population equivalents for commercial, industrial, and open-
space, recreational land uses should be based upon the wastewater flow
value (gpc/d) assigned to one of the land uses; for example, single
family low density.
2-7
-------
Table 2-2
Renumbering of Links After Addition of Relief Sewer
LINK ID
NEXT
ITYPE
1
7
2
2
4
1
3
' 5
2
4
7
2
5
1
2
6
0
4
7
8
3
8
6
2
9
11
5
10
6
2
11
10
2
1?
3
6
Adding these new links creates only a minimal change in the exist-
ing input data.
Results of Sample Run. Tables 2-3 to 2-7 illustrate checking and
display of sample input (discussed above) for validity. Output for the
resulting system in Table 2-8 displays minimum capacity of the sewer
network and of the waste treatment plant, their actual utilization at
various future points in time and overflow of network link as well as
overutilization of the treatment plant.
Detailed Program Description
This part consists of four sections. Immediately below is a sum-
mary of the hardware required to execute the program. This summary is
followed by a generalized flow diagram of the entire module, to give
an overview of its structure (Figure 2-3). Then come descriptions of
the main program and each of the subroutines it calls, with (in one case)
an accompanying flow chart. The final section is an input variable dic-
tionary, which contains every variable input to the module from cards,
Hardware Requirements
This program is written in IBM FORTRAN G. The catalogued procedure
used at the Massachusetts Institute of Technology, (where development
and testing were done) to invoke the FORTRAN compiler required 106K bytes;
catalogued procedures at other installations may have different require-
ments. 48K bytes (exclusive of I/O buffers) are required for execution.
It is recommended that a minimum of 4K bytes be added to I/O buffering,
which could result in a requirement of 52K bytes for execution. Execu-
tion time of the IBM 370/168 in a multiprogramming environment for a
typical test run was 32 seconds. One card reader and one line pi-inter
are required.
2-8
-------
j uj
>~ _j
<_;
< z:
T
tN
2< CCCCOCCOCCCO
< z
a. -
w ^
-j a
«~ o.
a. o
z
h
on z
0-1 UJ
T~ COCCOCCOCOCC
OU- ««
;2a. coaooooocooo
d UJ
1
U-
o ocoooooooooo
S.-< COQOOOOOOOOO
~-J CCOOOOGOOOCC
I
t- t- OOOOOOOOOCtJC
2-9
-------
Table 2-4
SANITARY V.ASrt-hATTR ROW VALITS
l.ANP USE GPC/H
SIN'GLF1 FALMIY (ITU CFNSI1Y) 100.0
SINGLE FAMILY (HIr,H TENSITY) 80.0
Pf-AK FLHlN ACJUSTMfNT FACTORS
STNCLt cAtr-1IY (L')W OfNSITY) 1.00
SINTl r- r^lLY (UGH PTNSIIY) l.OO
M Ul T I - c A M [ L.Y I.00
CDMMFRO TAL 1.00
INntjSTRI AL , -V.OO
OPFN SPACF - RFCRFATinN 1.00
2-10
-------
Table 2-5
C^LL CMfcACTERISTICS
C^LL ID
PC^SF'IT CM«F T' i^0 PSCJECTEO
POPULATION n3
POPULATION EQUIVALENTS
SINGLE FAMILY (LCN DENSITY)
1
2
3
4
5
6
C.= LL 10
T T+10
640 640
_2CO 250
2CO 250
0 0
1 0
0 0
PRESFNT {TIME Tl AND PROJECTED
T + 25
640
400
250
0
0
0
POPULATION OR
SINGLE FAMILY (HIGH CENS
I
2
1
4
c
6
CFLL to
T . .. TvlO
0 0
0 0
940 °00
0 0
0 0
T 0
PP=$FNT (TI^E T) C.NO PKHJfECTEO
T+25
0
0
gon
0
0
0
POPULATION 09
T*50
640
640
250
J
0
0
POPULATION ECUI-VJ-LeNTS-
ITY) _ .
. T*50
a ...-.-
0
940 -
0
0 .
T
PD°ULATinN EQUIVALENTS
MULT l-FAMILV
1
2 -
3
4
5
6
T T+l-0
0 0
c - - ._ .a
1000 1100
0 0
0 0
0 0
T + 25
0
J
1200
0
0
0
T+50
0
j ._ .
1300
0
0
0
2-11
-------
Table 2-6
CFLL VJASTfWATER. ALLOCAT TCNS
I INK ID ASSOCIATFC CFLL ID PERCENT OF ASSOCIATED
CELL FLCW INTO LINK
1 3 40
2 1 100
3 2 100
4 3 40
5 4 50
65 HO
73 ?0
8 5 20
o A 50
10 5 0
11 6 50
122 0
2-12
-------
Table 2-7
SYSTE'* GECMETPV
LINK 10
LINK fYPc
1
2
3
4
5.. _ .
6
7
8
. - 9
10
1X_
It
CCi\T INUING
ST APT IMG
CTf'TINUlNG
CCNTINUING
CLNTINUING
TERMINAL
JUNCTION
CCNT INIJ1NG
QIVFRSICN
f r NTI VJI NG
CC^T INUING . .. .
PIJ^P MAIN
-f
u
c
1
I
0
Q
6
11
6
1C
-3
LICI CF STARTING LINKS
,\UM2£R
1
ICEMTIFICATIOM
2
LliT C' CCNTI'IUING LINKS
10
11
LIST Cf= JUNCTION LINKS
MJ:"t(E« IOENTIF ICATICN
INTFRSECTKN LINKS PESULTTNT, LINK
1. . 1 £NO 4 , . . 7 .
LIST Cr OIVERSICN LINKS
.MJM3E3 IDENTIFICAT ICN
1 _ 9
f£ '.CFMT C^ UPSTRFAM LINK
Fl PW FMTPRING LINK
13
LIST CF PUMP MAIN LINKS
NUMBER IDENTIFICATION
1 12
FLCV IN LINK
l.'JOC
FLCWS BEGINS AT LINK 12
NAL LINK 10 IS 6
2-13
-------
CO
I
on
jj
£ *
9 *
tn
a
W u.
AC
§ - Z
^ § I
U _
LU
>
U_
J
at.
3 >
O O
n*
ocooc^ocoocc
oeoco-'oeocoo
z
a
u- _
C.
Z'
CJ
c; «-.'
c". >~ ** f\)
a S
c.
IT-
c
LL
X. O O O
2 O O C
X. >- ...
t- C O C
X n*. :\J
a: >
> « s
a. c; <-
« i- *-
y c i-
J. o
z
J_
2-14
-------
Figure 2-3
Plow Chart
Sewer Routing Module
Input:
Sewerage network characteristics
by link
2. Land use population or popula-
tion equivalents for present
(Time-T), T+10, T+25, T+50
(single family - low density
single family - high density
fflulti family
commercial
industrial
open-space - recreation)
3. Expected gallons per capita/day
wastewater generated by land use
4. Percent allocation of cell waste-
water to links
5. Peak flow adjustment factors
Reconstruct Network Geometry
Calculate maximum flow capacity of network by
link (using Manning's equation)
Input year (T, T+10, T+25, T+50)
against which system will be checked
Route sewage through system
recording quantity of flow
Print location and amount of overcapacity flows
Print, by link, maximum flow capacity, actual
flows, percent utilization, cumulative over-
flows
2-15
-------
no
End
Figure 2-3 (continued)
Flow Chart
Sewer Routing Module
©
Print percent capacity
utilization of treatment
facilities or pumping station
Input another check year
NO
End
of
run
Decision to add new or
relief links to system
yes
©
yes
1
Change and/or add
appropriate input
data
©
2-16
-------
Program Description
Main Program. Functions:
a. Dimensions; and specifies the variables which will be in COMMON.
b. Assigns the logical unit numbers for the card reader and line
printer the only two input/output devices used by the program.
c. Reads in the status desired for the debugging option. This
option ON causes to be output intermediate variable values and
would be of use to the professional programmer who is altering the
logic of the program. Under normal circumstances the program would
be run with this option OFF.
d. Initiates the execution of all other program segments through
a series of CALL statements.
e. Reads in the planning horizon (scenario) against which the
system is to be checked (card type 11).*
Subroutine IDAPG. Functions:
Numbers pages and prints identification comments on the top of each
output (card type 2).
Subroutine INDATA. Functions:
a. Reads input data (card types 3-10).
b. Assigns appropriate variable default values.
c. Checks actual numbers of diversion and pump main links against
maximum allowed. If there are too many, an error message is printed
and execution terminated.
Subroutine OUTDATA. Functions:
a. Prints the input data.
b. Converts, by link, the infiltration rate from gpd/inch diameter/
mile to gpd/mile.
These card types refer to the input data, as listed below.
2-17
-------
Subroutine KECONS. Functions;
Attempts to reconstruct the network system geometry, as defined
by the input data, by checking:
1. the actual number of starting, junction, continuing, and
terminal links against the maximum number allowed for each; and
2. that the actual numbering scheme is consistent with the number
rules.
Any violation of the above checks results in an error message and pro-
gram termination.
Subroutine GEOPRT. Function:
Prints the system geometry in tabular form.
Subroutine ROUTE. Functions:
a. Calculates the flow capacity of each link (in CFS).
b. Given the scenario calculates the actual flow at each link's
downstream node,
c. Calculates percent utilization by link.
d. Records overcapacity flows and cumulative overflows.
This subroutine, in which the routing of flows is modeled, is by
far the most complex in the program. For each run of the program ROUTE
is executed once to determine link capacity flows and then once for each
scenario input, calculating the actual flows. A sizeable portion of
the routine is devoted to the creation of an internal ordering of links,
using the NEXT and ITYPE vectors, such that all links in the network
system can be checked in one pass. The remainder of the routine con-
sists of two sections one to calculate capacity flows and the other
to calculate actual flows.
Figure 2-4, a flow chart of ROUTE, indicates important details.
Following are definitions of variables referred to in the flow chart,
while a complete list of input variables is presented at the end of the
chapter.
ISL = identification number of the link at which the system
routing begins
I = identification number of the present link in the system
2-18
-------
Figure 2-4
Flow Chart: of ROUTE
Calculate
Total population/population
equivalents of JCELL
Babbit's Ratio
Total amount of flow
entering link I from JCELL
End-of-link flow for link I
Percent utilization
Type
of immediate
downstream I
NXTL)
Is
link I
the last I ink of
the last branch enter
ing link NXTL
7
According to
numbering
rule
I =1+1
No
2-19
-------
NXTL = the identification number of the link immediately
downstream from link I
LB4 = the identification number of the link immediately
upstream from link I
LKT = counter for the number of links thus far encountered
NLINKS = total number of links in the system
JCELL = identification number of the cell in which link I is
located.
Subroutine CAPPRT. Functions:
a. Prints capacity utilization data.
b. Prints capacity utilization of treatment plant pumping station.
2-20
-------
Input Variable Dictionary
Card Variable Card
Type Name Columns
FORMAT
Comments
IDEBUG
IDCARD(I)
NLINKS
NCLS
NITL
1-80
1-3
4-.6
7-9
II
80A1
13
13
13
Debug option - (prints
intermediate output)
=0 - option off
=1 - option on
Identification card -
up to 80 characters -
to be printed on the
top of each page
Number of links in
the system (maximum
of 20)
Number of cells in
grid (maximum of 10)
Number of links flow-
ing into the terminal
link
ISL
1-3
13
ITYPT
TREAT(I)
2-22
II
3F7.2
Identification number
of link at which
routing of flows will
begin
End of terminal link
collector
=0 - pumping sta-
tion
=1 - treatment
plant
If ITYPT = 0:
input into TREAT(l)
the pumping station
capacity in CFS
If ITYPT = 1:
input into TREAT(I)
the following treat-
ment plant capaci-
2-21
-------
Card
Type
Variable
Name
Cards
Columns
FORMAT
Comments
ties in CFS
TREAT(1) = primary
TREAT(2) = secondary
TREAT(3) = tertiary
Input one card type 6 for each link in the system. Card
type 6 must be input in ascending order as ID goes from
1 to NLINKS.
ID
NEXT(I)
1-3
4-6
ITYPE(I)
LDIAM(I)
8-9
6
6
RUFCOF(I)
13
13
II
12
LENGTH(I) 10-14 15
SLOPE(I) 15-20 F6.5
21-24 F4.3
INFIL(I)
25-28
14
Identification number
of link
Identification number
of the link immed-
iately downstream
from link ID
Link type
= 1 - starting link
(max # = 4)
= 2 - continuing link
(max # = 15)
= 3 - junction link
(max # = 6)
= 4 - terminal link
(max # = 1)
= 5 - diversion link
= 6 - pump main link
Link diameter in
inches
Length of link in feet
Slope of link (feet
per 1000 feet)
Roughness coefficient
of link - if no value
is input a default
value of .013 is ass-
igned
Infiltration factor of
link in gpd/inch dia-
meter/mile - if no
value is input a def-
ault value of 450 is
assigned
2-22
-------
Card
Type
Variable
Name
Cards
Columns
FORMAT
Comments
LPCNT
29-31
13
For diversion links
only - percentage of
full capacity of up-
stream link flow ent-
ering the diversion
link
LINKUP
32-34
13
For diversion links
only - ID of the up-
stream intersected
link
FMLF
35-42 F8.3
WASTEF(LU) 1-27
3F9.1
IPE
28
II
PKADJF(LU)
1-36
6F6.2
For pump main links
only - amount of flow
in CFS entering link
from some external
source
Waste flows assigned
to land uses (gpl/
day)
WASTEF(l) =- flow for
low density single
family
WASTEF(2) = flow for
high density single
family
WASTEF(3) = flow for
multi-family hous-
ing
The land use type upon
which population equ-
ivalents for commer-
cial, industrial and
open-space and rec-
reation are based
= 1 - single family -
low density
= 2 - single family -
high density
= 3 - multi-family
Peak flow adjustment
factors by land use
for sensitivity analy-
sis
PKADJF(l) = single
family-low density
2-23
-------
Card
Type
Variable
Name
Cards
Columns
FORMAT
Comments
PKADJP(2) = single
family-high density
PKADJP(3)
family
PKADJP(4)
PKADJF(5)
PKADJP(6)
= multi-
= commercial
= industrial
= open-space
recreation
There are six (one per land use) type 9 cards for each cell
in the grid. Their ID's must be input in ascending order
from 1 to NCLS.
ID
1-3
NCELLS(I,J) 4-40
13 Identification number
of cell
419 For cell I (I=ID) the
population (or popu-
lation equivalents)
for the four time
periods (present =
time T)
NCELLS(I,1) = values
for T
NCELLS(I,2) = values
for T + 10
NCELLS(I,3) = values
for T + 25
NCELLS(I,4) = values
for T + 50
Input one type 10 card for each link in the system. Their
ID's must be input in ascending order from 1 to NLINKS.
10
10
10
ID
1-3
IALOCT(I,1) 4-6
IALOCT(I,2) 7-9
13
13
13
Identification number
of link
ID of cell in which
link I (I=ID) is
located
Percentage of cell
ID's wastewaters that
drains into link I
There may be up to four type 11 cards in a single run
2-24
-------
Card
Type
Variable
Name
Cards
Columns
FORMAT
Comments
11 IPHOR 1 II Planning horizon or
scenario against
which system capacity
is checked
=0 - present (time
T)
=1 - T + 10
=2 - T + 25
=3 - T + 50
A sentinel card such as the IBM /* indicating end of data
is required by the program.
2-25
-------
Chapter 3
Cost Evaluation Module*
General Description
The cost evaluation module is designed to estimate costs incurred
by added development within a community and to provide an allocation of
capital and operation and maintenance costs to those groups sharing the
project's costs. By varying the cost allocation schemes, a planner is
able to generate a range of financial impacts over time on the community.
The current version of the model has provision for calculating the impact
of the following environmental infrastructure cost types (index = j):
1. on-site wastewater disposal;
2. sanitary sewer laterals;
3. sanitary sewer building connections;
4. sanitary sewer trunks/mains;
5. storm sewer laterals;
6. stormwater detention ponds;
7. storm sewer trunks/mains;
8. sewage treatment plant(s).
A general logic diagram of the module is presented in Figure 3-1.
Regardless of the infrastructural cost types j to be estimated, a
set of community and development characteristics is required as input:**
a. Projected population/population equivalents of the community
for six land uses, for four time periods the present (time T)
and 10, 25 and 50 years into the future:
1. single family low density;
2. single family high density;
3.. multi-family;
4. commercial;
* Detailed description of the module is given in Chapter 6 of Land Use-
Water Quality Relationship, Report prepared by Meta Systems Inc for U.S.
EPA under contract #68-01-2622; published by EPA's Water Planning Division
WPD 3-76-02, March 1976.
** It should be noted that some of the data is deliberately in formats
compatible to the sewer capacity evaluation module (Meta Systems Inc, ibid.),
because this module complements that module by analyzing the associated
financial impacts.
-------
Figure 3-1
Logic of Cost Evaluation Module
[INPUT FIXED DATA I
r r INPUT COST TYPE >
TO BE EXAMINED
t
' t , t *
1 ONSITE * SANITARY 3 SANITARY 4 SANITARY
DISPOSAL SEWER SEWER SEWER
LATERALS BUILDING MAINS/TRUNKS
1 TffisT 1 ' CONNEXIONS |
ITYPEJ- 1 1 1
*
"" KJH tACH COS
COST FUNCTION* COST FUNCTIC
TOTAL CAPITAL COST AVERAGE^ ANNU
T TYPE
)N «-
AL
t |
s STORM 6 5TORMWATER T SI
SEWER 5ETENTION §
LATERALS 'ONOS M
1,1-
1
1 N2<^fe8>YE3 .AN
1 ^X. 7 ^"^ U"
J ^xj^ RE
Ii
COST ALLOCATIONS
ACCORDING TO FIXED
SHARING SCHEME
t_
1 1
| FEDERAL GOV'TJ |STATE GOV'T |
1 J
CAPITAL COSTS
PAID IN ONE SUM PROPERf YL -
\ TAX r
0»M COSTS 1
PAID YEARLY A 5 A t
PERCENT OF TOTAL
ANNUAL 0*M COST
FOR
OUTPUT FEDERAL BV L
AND STATE GOV'T
J
[LOCAL GOV'T! oev
. 1 . COI
BY E.ACH MECHANISM
t 0QI\
1
D ISSUE j ^USER CHARGE
l
OUTPUT
CAPITAL AND 0*M COSTS
AND USE IN
t /YEAR
$/$IOOO ASSESSED VALUES
$ / 1OOO GALLONS WASTEWATER
<
^
ANOTHE^vNO OUTPUT SUMMAR
OST^TYPEx* " TABLES
_JYES
t i
PORM 8 SEWAGE
EWER TREATMENT
WNS/TRUNKS PLANT
J
ST FUNCTION *
NUAL 0»M COSt
TIL FULL CAPACITY
ACHED
4
\
ELOPERS
4SUMER)
SPECIAL
ASSESSMENT
|
| |
i OF COSTS '
L j
I
l
i .[So]
3-2
-------
5. industrial;
6. open space recreational;
b. the expected gallons per capita per day of wastewater generated,
by land use;
c. present and projected assessed property values of the community
by land use for the four time periods T, T+10, T+25, T+50;
d. projected assessed property values of the proposed development
by land use for the four time periods T, T+10, T+25, T+50;
e. the numbers and kinds of residential structures to be construc-
ted in the proposed development;
f. expected number of persons per household for the various resi-
dential dwellings within the proposed development;
g. interest and discount rates to be used in calculating the cost
streams.
In addition to this data, development characteristics will be re-
quired by the individual cost types j to satisfy the cost functions.
The details of such input are included in the Input Variable Dictionary
(see last section of this chapter).
For each cost type j there will be a maximum of up to four groups
£ sharing the costs:
H = 1 developer;
£ = 2 local government;
£ = 3 r state government;
SL = 4 federal government.
Having defined the cost types to be studied, the planner decides on
a cost allocation scheme based upon local practices, and state and
federal cost sharing programs. Thus, for each cost type j, input vec-
tors will be required indicating the percent share of the capital costs
(k=l) and the operation and maintenance costs (k=2) to be allocated to
each group £.
From this point otj^, the share of cost in dollars of cost compon-
ent k, for cost type j , to be allocated to group £, is calculated. The
assumptions made concerning the cost calculations and allocations are:
1. all operation and maintenance costs are in average annual cost
except for sewage treatment plants (j=8), for which annual
operation and maintenance costs vary in accordance with the
capacity utilization of the plant and so are calculated on a
yearly basis until full capacity is reached;
3-3
-------
2. any financing of capital costs by the federal or state govern-
ments will be realized in one payment at the beginning of the
construction period;
3. any financing of operation and maintenance costs from the
federal or state government will be realized as an annual fixed
percentage of the costs;
4. within the local government costs may be further broken down
by the method in which funds are raised to finance the project:
a. special assessment a one-time charge is assessed against
the property owners of the development in dollars per $1,000
assessed value;*
b. bond issue the community may decide to float a bond
issue in order to finance the cost type. The revenues required
to then pay off the bond issue will be raised in two ways:
(1) property taxes the additional tax per $1,000 assessed
property values that will be paid by each land use over
the bond issue payback period;
(2) user charge given the total amount of revenues to be
raised by user charges, the equivalent dollars per capita
and dollars per 100 gallons of wastewater generated are
computed by land use.
Required input for the bond issue mechanism includes the pay-
back period, the percentage of the bond issue to be financed
by property taxes and user charges, the percentage of each to
be paid by the six land uses and, for the capital costs fin-
anced with this mechanism, the annual rate of increase in
the amount paid back each year;**
5. costs borne by the developers will generally be passed on to
the consumers within the development in the same fashion as a
special assessment by the local government.
***
* Note: assessed values are obtained from straight line interpo-
lation between time periods.
** If the annual rate of increase in the amount to be paid back is
zero, the annual payback is constant.
*** If the housing market is highly competitive, or developers in near-
by locations do not have to pay as much, the developer may absorb part
of the costs to remain competitive.
3-4
-------
Description of the Program and its Subroutines
Each subroutine of the current version is listed and explained
below:
Main Program
Functions:
a. defines, through a series of COMMENT cards, the variables
and arrays of COMMON;
b. reads in the infrastructure cost type j's to be estimated;
c. reads in the associated percent allocations to each group ij
d. serves as a calling program for nearly all subroutines (see
Figure 3-2).
Subroutine FIXDATA
Function:
Reads in data that is required by the program regardless of the
cost types to be estimated.
Subroutine FIXOUT
Function:
Prints portions of the data read in FIXDATA.
Subroutine PAVPYR
Function:
Calculates the population and assessed property values by land
use for. each year. A method of linear interpolation is employed
between the four input points: present; +10 years; +25 years; +50
years.
The following subroutines are those used to compute capital costs
and operation and maintenance costs of each (infrastructure) cost type
j.* Each of the subroutines reads in data required for the cost
* The equations presently used in each subroutine are fully derived
and referenced in Meta Systems' report (ibid.).
3-5
-------
Figure 3-2
Calling Sequence Program
3-6
-------
estimation functions, computes the costs and places them in COMMON for
use by the allocation, finance mechanisms, and output routines.
Liberal use of COMMENT statements provides easy correspondence between
variables defined in the report and the associated variable names in
the program.
Subroutine CTJ1
On-site disposal.
Subroutine CTJ2
Sanitary sewer laterals.
Subroutine CTJ3
Sanitary sewer building connections.
Subroutine CTJ4
Sanitary sewer trunks/mains.
Subroutine CTJ5
Storm sewer laterals.
Subroutine CTJ6
Stormwater detention ponds.
Subroutine CTJ7
Storm sewer trunks/mains.
Subroutine CTJ8
Sewage treatment plant.
Subroutine CCFJl
Used by CTJ1 for capital cost estimate calculations.
3-7
-------
Subroutine OMJ25
Used by CTJ2 and CTJ5 for operations and maintenance cost estimate
calculations.
Subroutine ALOCAT
Function:
Calculates and prints the financial impact to consumers of property
in the development due to costs borne by the developer (using the finan-
cing mechanism in the report).
Subroutine LCCOM
Function:
Calculates and prints the financial impact to the community and
developer due to costs borne by the local government (using the finan-
cing mechanism defined in the report).
Subroutine SUMRE
Function:
Prints summary tables of the cost types examined and the total costs
allocated to each group £.
Hardware Retirements
The Cost Estimate Module is written in IBM FORTRAN G. Execution
requires a minimum of 144K bytes of storage; if large physical block
sizes are desired for buffering of reader/printer I/O, more core may
be necessary. One card reader and one line printer are required, they
are assigned to FORTRAN logical units 5 and 6 respectively.
Additions to the Program
At present the term CLF (cost of associated leaching field) refer-
red to in the report* is not in the program. The following changes would
be required to introduce this variable:
Meta Systems, ibid., p. 6-34.
3-8
-------
in subroutine CTJ1 change statement #11 ...PMF, CLF
in subroutine CTJ1 change statement #12 ...(3F5.2, F8.0)
in subroutine CCFJ1 change statement #15 C=C+275.+CLF
Subroutine CTJ6 contains at present no capital cost function or
estimate. The planner should provide some variable or function to
compute the capital cost of stormwater detention ponds if they are to
be modeled. Its value should be stored in the variable TCC(J) where
J is the index of the cost type being modeled (in this case equal to 6)
Minimal coding required would be
READ (NR,1) relevant variable(s)
1 FORMAT (as required)
coding to compute the value of TCC(J)
CALL ALOCAT
These statements would be inserted between existing statement numbers
12 and 13.
In general, each cost function is in the form TCC(J) = F(A-j, A~,
. . ., An), where J is the index of the cost types being modeled.
The programmer wishing to change a given cost function need only refer
to the expression(s) involving TCC(J) in the relevant subroutine.
Sample Run
A new residential development is hypothesized to contain 890 dwell-
ing units made up of 590 townhouse units and 10 garden apartments with
30 dwelling units each. The development requires sanitary and storm-
water lateral interceptor sewers. Capital and operating and maintenance
costs for each infrastructure component are allocated hypothetically
to different financing methods.* Costs are assigned to developers and
local, state and federal governments. Within the local government
category expenditures are further classified by revenue source.
Table 3-1 represents a sample of the output which can be generated by
this module.
The program also produces more detailed tables indicating the
temporal allocation of costs, effects upon property taxes, and the
* Note: This allocation scheme does not necessarily correspond to
existing practices.
3-9
-------
1
I
1
1
1
j
1
rH
1
m
0)
,__j
1
3*
£
_J
2
0
t
VI
OJ
1
h-
Z
UJ
X
o
J
UJ
UJ
D
^
H-
z
UJ
o
UJ
oc
i
]
1 i
1
HI -H
UJ
0 I/)
t" "1 I
> SI
I i!
§|5!
!
i Z
-J UJ
* 3
UJ *
s>
o
z
Ul
SI
*° o
o
>
flC
U X
o. <
OC
^
Z '
UJ
i u,
as 8
§ ?
O U
.J oc
< u,
o m
0 3
z
_» UJ
o w>
Uj Ul
a vi
ui -ft
UJ
a
o
>
'U
O
+
~
UJ
ft.
V
H"
h-
O
O
1
1
o o oo
f 1 «
o o o o
in 9 mo
t t
rsi « « M
(SI
(
t-
*/) Ck
-J , UJ
o£ ' ac
UJ UJ
H* ' h-
< . z
-J M
CC ' (£
UJ UJ
2 X
UJ UJ
«/) -J w» _J
< <
ir^ isx
»- < + *- «s +
u o u-o
z z
VI l/>
J
O 0*
3« c o
a a
So
u
, c
: u
1 « v
; i
* o a
00
* ^
(VJ vfl
m -
X
u
u.
X
at
S ^ 5 a
. _j r
S1^ ri c
N O at
* rsi Q^
4 O
(XI < J
u) t-
i/
' UJ U.
t -A i-
' <4
1 *U
z c
ec
O UJ
oc >
vO < X
-t H
oc ': uj u
UJ 3
3 ' 'S5
IU *J _J W
S- ~
X < * < * ?
l£ O O u O
O
VI !
Ul
flk
f
N.
M
O
U
5
|
U
Z
2
g
«
£
o
?
U
H-
O
i
r
<
u
UJ
T
*
0
Cv
0
oc
o
r
Ul
5
0
z
D
ac
UJ
u.
O
>-
Z
<
X
If
z
X?
u
zr
33
UJ
TO.
a.
D aC
OUJ
ae
SSi
*"
-------
required user charges of each cost type among the various land uses.
(See Table 3-2.) After examination of the costs, the planner may
choose to rerun the program with a different local government financing
mechanism.
3-11
-------
01
D
*O
£
CO
o
00 <->
-p
0) 3
rH Q,
S 3
o
»-H
a
3
co
*ft
Q>
* t/
O* i .
fM
=!
"*
I :
Q
S H
UJ
H- «
I
*-
UJ I
X
a.
O
-J I
UJ
UJ
UJ t-
0
i/j */)
UJ U
a i u
!
i
i
a
UJ
U)
0 O O *-
o ^ ui
o
a
-J.
33
o a
a
3) S
5
o
^3
zB
a
_ j »
O UJ
Ul >- OC
»- z <
a uj
13 *l OC
t- J_ ^ X
z a o
t- O < uj
3 t- O X |
U 0 0
UJ OC. DC c£
a. ua uj uJ
H- A- H X
U J 3
l/J
[
1
f 1
^
CD
a.
UJ
CD
O
h-
UJ
a
*
H>
o o i
0 0
* U, t
O
aC
< 1
_j
0 )
O
z
h-
Z
g
0 X. \
JJ <
0 0
UJ Z
0. <
X
^ [3
1 <
t- z
a. tx
O 0^ |
UJ
UJ
a
u.
LJ
LJ
^
X
-J
D
i
i i
i i
! t
IA o» -r
o r» < o -r I
i/l Z O * °* O **>' <
N* 3 r ,
§w» O , ^ «» »
0 X ! i -I,
a. z uj t GO
o -< u o o o o
< OC CO *N( ff»
X uj
M
UJ
co co IA m 3
co ai v* o f"- _J
Z ^ - (N O ff- ,>
trt O ^- O* r- ^ Q
t ac (*> IN o r* uj
irt < O * -O O M
O *^
"- ^- O O O O
o, z o o o o o
< uj ' O
OODOQO , -^
OC Ift * -H , «»
LlJ Nk
CL , «A
: 2 S|
Ul
^ 1
' UJ |
1 H- O Wl 1
oe > ^o z
U 0 ^ 1 0
0. O O _j o 1
O < ui |
-J -j uj ct -J o
UJ 4 ^~ UJ < t j
UJ O * UJ LJ Z j
O -1 "" U. f- Q I
}
O |
UJ |
! < 1
^ Q. i
; j
o i
! W i
; 1
!
{ u |
CJ (
I
! o oo o
t O O O A
' *
XX <
o o a
CL <£ -* UJ
, O U. U, t- "X.
\ ^ z
O O «JJ UJ
UJ UJ LJ ffl
a < a. H
UJ
ui ul ul 3
SaJ X */>
3 < u»
ul 5 ct ~
> >t- O
uj uj wj z
at: at O
t- co
> >- Ul
^ U Q
i_» Z3 ^ ii aJ
OJ tO (/) CC
10 to O O
U. - - UJ Z
a. o u uj
h- a.
^C I >- «rt
3-12
-------
0)
3
c
o
u
(N
I
f ~r ifi it\ *f\ \et & -O «o * O ;
O003OO3OOO... -I'
31390000090 o
UJ Z '
S2
a *- oooooooooo%>>
\U O O O O O* O O O O O
Z oe
UJ <_»
a. uj i
o* '
M fy'Vm'Vt*i(*iffOOO.»O
kO OOOOOOOoOO O
» rnn\-+*r-f>t*\if\-a-Q *
i_} OOUOO(-»OO«O...°
UJ OoOOOOOOOO, O
I
£ 2! I
a ^(MM^tfsfl^o-o-* O
& u. ooooo**ot*oo o
I
s i
s i
OOOOQOOOOO |°
\
,UJ Z I !
*2! '
a.»- oooooooooo-B(V o
uj OOOOOO9OOO O
*U O I i
& UJ I
O *( i I
jOwift «
*d
tH
o XM oo«oooo>t^oooo-< <
o <>/> 3OOOI-»O -^ -^ -^ .. . '
O I
zo
IrtZ
w * * -r as -* o
« h.^.^^.^
«t o o o -« «
o«-a
-------
I I I
IOOOO9OOOOO
ITZ
12 <
oooooooooo.,.
JU OOOOOO9OOO
3*j
o'
OOOOOOOOOO*
oooooooooo
1
H
o
o
CO
0)
«- IA oooooooooo'
O U.Z « .
* OJ OOOOOOOOOO
ZM ooooooouoo' o
-._ __.._.- . . _ _^ t ^ Q
QO*JO<-»WOOO o1'
UJ Q
u
O X
!o o 3 o o o(» o o o -^
loooooo^ooo... o
ooooooooao o
O O'OOO O%..
Zee
UJ tj
Q.UI
Ooe
oooooooooo*
oooooooooo
o
o
I -
jj OOOOOOOOOO
? , I
oooooooooo
ooooutj.auoo*
o o <
> o w o o
z*-> oooooooooo
-------
"8
G
0
O
CN
\
3OQDOOOOOO O'
OO3OOOOO3O » Oi
ooooaooooo o
I
i
I
OLt-i aOOOOOOOOO_'O
zS °':'<=
ss !
ox ;
I
_J
-i OOQOOOOQOO Oi
~ O O O "" O(
t
O O o O'
i I
I
£ o'o*"o"oo' O'
X
r
a
0 !
I ,
>-
at -4
OJ OOOQOO O.O O O O
4 <
LLl I
s ^
4 -4 !
* i :
(/i i
z
O i
_i
3 2.-
o x-^ oooooooooo o
O U. 2 ^ ,
-^ LU OOOOOOOOOO O
"S. OJ Q
** _J
2
3-15
-------
Input Variable Dictionary
Card Variable
Type Name
FORMAT Card
Columns
Comments
IDEBUG
II
IDCARD(I) 80A1
1-80
ICT(I)
811
1-8
DR
F5. 2
1-5
Debug option -
= 0 - option off
= 1 - option on
Identification card -
up to 80 characters
to be printed on the
top of each new page
Punch in column J a 1
for each cost type
to be studied:
J=l - septic tanks
J=2 - sanitary sewer
laterals
J=3 - sewer building
connections
J=4 - sanitary sewer
trunk/main
J=5 - storm sewer
laterals
J=6 - stormwater
detention ponds
J=7 - storm sewer
trunk/main
J=8 - sewage treat-
ment plant
Discount rate in per-
cent
AIR
F5.2
1-5
Interest rate in per-
cent
NACRES
IPOP(LU,
ITIME)
15
419
1-5 Number of acres in
development
1-36 For each of six land
uses (LU) the pro-
jected population/
3-16
-------
Card
Variable
Name
FORMAT
Card
Columns
Comments
APVOT(LU,
ITIME)
4F10.2
1-40
population equivalents
for the community at
four points in time
(ITIME):
LU=1 - single family
(low density)
LU=2 - single family
(high density)
LU=3 - multi-family
LU=4 - commercial
LU=5 - industrial
LU=6 - open space -
recreation
ITIME=1 - present (T)
ITIME=2 - T + 10 yrs.
ITIME=3 - T + 25 yrs.
ITIME=4 - T + 50 yrs.
(six cards)
For each of the six
land uses (LU) the pro-
jected assessed values
of the community at
four points in time
(ITIME) in $1000 (6
cards)
APVOD(LU,
ITIME)
4F10.2
1-40
10
WASTEF(LU) 3F9.1
1-27
10
IPE
II
28
3-17
For each of the six
land uses (LU) the pro-
jected assessed values
of the development at
four points in time
(ITIME) in $1000 (6
cards)
Expected wastewater
flows generated by the
three residential land
uses :
WASTEF(l) - single
family (low density)
WASTEF(2) - single
family (high density)
WASTEF(3) - multi-
family
Land -use against which
-------
Card Variable
Type Name
Card
FORMAT Columns
Comments
11 NSFLDU
16
1-6
population equivalents
will be based for com-
mercial, industrial
and open space - rec-
reational land uses:
= 1 - single family
(low density)
= 2 - single family
(high density)
= 3 - multi-family
Number of single family
(low density) housing
units in the develop-
ment
11 PPULD
12 NSFHDU
F5.2
16
7-11 Number of persons per
unit for single family
(low density) housing
1-6 Number of single family
(high density) housing
units in the develop-
ment
12
13
13
13
PPUHD
NMFB
NUBMF
PPUMF
F5.2
16
16
F5 . 2
7-11 Number of persons per
unit for single family
(high density) housing
1-6 Number of multi-family
buildings in the
development
7-12 Number of units per
multi-family building
13-17 Number of persons per
unit of multi-family
housing
The remaining card types refer to data required for the
individual cost types. As many cost types as desired may
be examined in a single run. The data deck must be pre-
pared as J=l,8 for the cost types to be run.
Card types 14 and 15 are required as the first two data
cards of each cost type J.
3^18
-------
Card
Type
Variable
Name
FORMAT
Card
Columns
Comments
14
15
16
PSOC(J,
PSOC(J,
2,L)
ADJUST(J)
4F5. 2
1-20
4F5.2
1-20
8F5. 0
1-20
COST TYPE J=l - SEPTIC TANKS
1 PSFL F5.2 1-5
Percentage of the capi-
tal cost of cost type
J to be financed by
group L:
L=l - developer
L=2 - local gov't
L=3 - state gov't
L=4 - federal gov't
Percentage of the
operation and main-
tenance cost of cost
type J to be financed
by group L
Multipliers for cost
type J (1-8) adjusting
for local conditions
(Default= 1).
Percentage of single
family (low density)
homes in the develop-
ment to have septic
tanks
PSFH
F5. 2
6-10 Percentage of single
family (high density)
homes in the develop-
ment to have septic
tanks
PMF
CLF
F5. 2
F8. 0
11-15 Percentage of multi-
family housing in the
development to have
septic tanks
16-23 Cost in dollars of the
associated leaching
field (see section Ad-
dition to Program).
COST TYPE J=2 - SANITARY SEWER LATERALS
TH
F6.0
1-6
Number of townhouse
units in the develop-
ment
3-19
-------
Card
Type
Variable
Name
FORMAT
Card
Columns
Comments
GA
F6.0
7-12 Number of garden apart-
ment buildings in
the development
AMRA
F6.0
13-18 Number of medium rise
apartment buildings
in the development
IALPHA
IBETA
SIZEP
II
II
F10.0
19
20
1-10
Slope characteristic
of development:
=1 - flat
=2 - moderate
=3 - steep
Soil type of develop-
ment :
=1 - hard clay and
shales
=2 - loose mud, loam,
gravel, compact-
ed gravel, till
Population size of
development
COST TYPE J=3 - SEWER BUILDING CONNECTIONS
TH
F6.0
1-6
Number of townhouse
units in the develop-
ment
GA
F6.0
7-12 Number of garden apart-
ment buildings in
the development
AMRA
F6.0
13-18 Number of medium rise
apartment buildings
in the development
AL
F6.2
1-6
Average length of
building connection to
single family and town-
houses (in feet)
3-20
-------
Card Variable
Type Name
FORMAT
Card
Columns
Comments
IALPHA
II
IBETA
II
AL
F6.2
1-6
Slope characteristic
of development:
=1 - flat
=2 - moderate
=3 - steep
Soil type of develop-
ment :
=1 - hard clay and
shales
=2 - loose mud, loam,
gravel, compact-
ed gravel, till
Average length of
building connection to
garden and medium rise
apartments (in feet)
COST TYPE J=4 - SANITARY SEWER INTERCEPTORS
1 D
1 FT
COST TYPE J=5
1
1
F
SG
R
DB
F10.2 1-10 Average depth of treach
in feet
F10.2 11-20 Diameter of sewer pipe
in inches
F10.2 21-30 Length of pipe in feet
STORM SEWER LATERALS
Recurrence interval
SIZEP
F10. 4
F10.4
F10. 4
F10. 4
F10.4
F10. 0
1-10
11-20
21-30
31-40
41-50
1-10
Average ground slope
(feet per 100 feet)
Runoff coefficient, C
from rational method
Smallest pipe diameter
in inches
Total capacity of sys-
tem in cubic feet per
second (CFS)
Population size of
3-21
-------
Card
Type
Variable
Name
FORMAT
Card
Columns
Comments
development
COST TYPE J=6 - STORMWATER DETENTION PONDS
no input(at this time)
COST TYPE J=7 - STORM SEWER INTERCEPTORS
1 Z F10.2 1-10 Average depth of
trench in feet
1 D F10.2 11-20 Diameter of sewer pipe
in inches
1 FT
COST TYPE J=8
F10.2 21-30 Length of pipe in feet
SEWAGE TREATMENT PLANT
1 IRP II 1 Community served by
regional or community
treatment plant; =0 -
community; =1 - regional
Card type 2 is required if IRP=1, i.e., regional plant
(card type 1)
PCS
F5.2
1-5
FC
F10.0
6-15
IPCCF(I)
1711
1-17
Percentage of the total
capital cost to be shared
by the community (regional
cost sharing agreement)
Fixed annual charge (in
dollars) to community
(annual share of capital
costs)
Treatment plant charac-
terastics - a 1 in the
associated column indi-
cates the characteris-
tic is included - a
blank indicates not
included:
Biological Treatment -
column characteristic
1 activated sludge
2 filtration
3 sludge pump
3-22
-------
Card Variable Card
Type Name FORMAT Columns Comments
4 sludge diges-
tion
5 holding tank
6 vacuum filtra-
tion
7 incineration
Physical/Chemical
Treatment
8 coagulation &
sedimentation
9 filtration
10 carbon adsorp-
tion (X2.LE.10
MGD)
11 carbon adsorp-
tion (X2.GT.10
MGD)
(X2 from card type 4)
12 chlorination
13 sludge pump
14 sludge digester
15 sludge holding
tank
16 vacuum filtra-
tion
17 incineration
4 X2 F10.3 1-10 Design flow (MGD)
4 F F5.3 11-15 Ancillary works factor
4 C F10.3 16-25 BOD5 of wastewater
(in mg/1)
After each set of cost type J data the following card types
are required - exceptions are noted.
Card types 1-4 refer to input required for capital costs:
1 IFM II 1 Financing mechanism for
local government capi-
tal costs:
=1 - bond issue
=2 - special assess-
ment
If IFM=1 (card type 1) card types 2,3,4 are necessary; if
3-23
-------
Card Variable Card
Type Name FORMAT Columns Comments
IFM=2 they are not included in the data deck.
2 IPP 12 1-2 Payback period' for bond
issue in years (max =
50)
2 PPT F5.2 3-7 Percent of bond issue
to be repaid from
property taxes
2 PUC F5.2 8-12 Percent of bond issue
to be repaid from user
charges
3 PBUC(LU, 6F5.2 1-30 .Percent allocation, by
K) land use, of total
revenues to be raised
from user charges
4 PBPT(LU,
K) 6F5.2 1-30 Percent allocation, by
land use, of total
revenues to be raised
from property taxes
For cost type J=8 only the following card type is necessary:
5 IFCP 12 1-2 Number of years until
full capacity of treat-
ment plant is reached
(max=50)
Cost types J=l and J=8 require no further data.
Card types 6-8 refer to input required for the remaining
cost types for operation and maintenance costs.
6 IPP 12 1-2 Payback period for
operation and mainten-
ance costs (max=50)
6 PPT F5.2 3-7 Percent of operation
and maintenance costs
to be repaid from
property taxes
6 PUC F5.2 8-12 Percent of operation
3-24
-------
Card Variable Card
Type Name FORMAT Columns Comments
and maintenance costs
to be repaid from user
charges
7 PBUC(LU, 6F5.2 1-30 Percent allocation, by
K) land use, of total
revenues to be raised
from user charges
8 PBPT(LU, 6F5.2 1-30 Percent allocation,
K) by land use, of total
revenues to be raised
from property taxes
3-25
-------
-------