Laserfiche WebLink
portant for auy municipality consider- <br />ing a program to consult with its legal <br />advisors and ensure that the pro- <br />posed solution coincides with state <br />laws and the needs of the community. <br />After six months of research, our <br />department submitted a report to the <br />city council in July 1982 that recom- <br />mended the city create a stormwater <br />management utility with user fees <br />based on contribution to runoff'. By <br />October, the council approved the <br />recommendation. <br />Developing the Utility <br />From its inception, the stormwater <br />management study was planned to <br />maximize both interdepartmental <br />coordination and public participation. <br />Public input would ensure that the <br />study did not proceed in a vacuum. <br />Interdepartmental Coordination. <br />The department first established a <br />city management team to monitor the <br />progress of a drainage finance study <br />and coordinate activities among city <br />departments. The team consisted of <br />representatives from the engineering <br />and highway maintenance divisions <br />of the Metropolitan Sewer District of <br />Greater Cincinnati; the city depart- <br />ments of buildings and inspections, <br />law -civil division, law -real estate divi- <br />sion, planning, finance and neighbor- <br />hood housing and conservation; and <br />the division of research, evaluation <br />and budget in the city manager's of- <br />fice. A representative from each city <br />department would ensure that many <br />diverse needs were accounted for and <br />that public works managers would be <br />involved with the implementation of <br />the program. <br />The team also drafted two ordi- <br />nances tTiis project One au- <br />t zec t e researcTi_an__d pry- <br />nary planning for a stormwater man- <br />agement utility, and the secon a Ot- <br />te or the development <br />p hase o t e project. Although council <br />members were tightening their <br />budget belts, both ordinances passed. <br />The team then recommended that <br />Water Resource Associates, Inc., <br />Kirkland, Washington, prepare a <br />drainage finance study. The goal of <br />the study was to determine an <br />adequate, stable, and publicly ac- <br />ceptable method of financing the util- <br />ity. The final study gave the public <br />works department a functional re- <br />quirements analysis, financing op- <br />tions, a program and financing <br />strategy, a rate structure analysis, <br />and a rate study. <br />After the program and financing <br />strategy phase of the study was com- <br />pleted in mid -1983, we submitted a <br />progress report to the council. The <br />report contained the study's prelimi- <br />nary findings, a summary of the city's <br />needs and functional requirements <br />and a recommendation that the city <br />establish a stormwater management <br />utility. <br />By this time, more than 10,000 com- <br />plaints from residents had accumu- <br />lated in the city's file. <br />Public Involvement. After the <br />council approved the progress report, <br />Water Resource Associates, Inc. <br />began the rate structure analysis. At <br />this time, the real public involvement <br />began, which meant getting to know <br />the people and their particular <br />stormwater - related complaints. To <br />set the groundwork for later public <br />involvement activities and to compile <br />fast," a bimonthly meeting attended <br />by the city manager and the executive <br />boards of the community councils. <br />Our challenge was to present this <br />city -wide problem — which called for <br />a $50 million solution of planned <br />routine and remedial maintenance — <br />and make it a priority in the minds of <br />the public. <br />Our presentation consisted of: 1) a <br />statement of the seriousness of <br />stormwater drainage in Cincinnati; 2) <br />a slide show that demonstrated real <br />drainage problems (inlets blocked <br />with debris, living rooms damaged by <br />flood water, and factory workers <br />wading through a Iocal industrial <br />■ INADEQUATE roadside drainage was creating severe roadway flooding. <br />The city's deteriorating drainage system prompted numerous complaints. <br />information collected by the city man- <br />agement team, several projects were <br />established. <br />Stormwater Functional Require- <br />ment Maps. Since 1958, the depart- <br />ment had kept careful records of the <br />10,000 stormwater complaints. Using <br />these records, the locations of the <br />complaints were noted on neighbor- <br />hood maps. These 48 "Stormwater <br />Functional Requirement Maps" were <br />bound into a separate volume, which <br />provided excellent source material <br />for determining the worst drainage <br />problem areas. <br />Community Council Rapport. Es- <br />tablishing a rapport with the commu- <br />nity councils was crucial. Cincinnati <br />has more than 48 "recognized" com- <br />munities that are established political <br />forces in the city. To ensure their in- <br />volvement, we presented a program <br />at the city manager's "working break- <br />complex); and 3) a presentation of the <br />"utility" solution. <br />Because this first program was so <br />well received, the director of public <br />works asked each of the community <br />councils if we could make a similar <br />presentation at a future meeting. <br />Property owners would be given the <br />opportunity to listen to the proposal <br />and give feedback. Many of the coun- <br />cils accepted the invitation. <br />The key to the community council <br />talks was targeting and tailoring each <br />presentation to an individual commu- <br />nity. For example, in the Mt. Airy <br />neighborhood, we used a map that <br />pinpointed areas of local drainage <br />problems and included locations of <br />resident complaints. Showing photo- <br />graphs of stormwater problems in <br />that community, such as clogged in- <br />lets, basement water destruction, and <br />on <br />(Ctinued on page 150) <br />PUBLIC WORKS for September, 1986 127 <br />