New Search
7 <br /> STORMWATER QUALITY MANAGEMENT PROCESS/LUCU RELATIONSHIP a <br /> Meeting with PW Engineering and Planning Staff of May 15, 2001 - r A.".C�iw1 tAl- <br /> )_uCu al F< ' <br /> Timeline for Adoption of Stormwater Quality Design Standards: <br /> <Tub) June-1 ; 2001 - Meeting with Planning Commission to give them a general overview. <br /> August 6, 2001 -Planning Commission Worksession. „�,; <br /> September 1., 2001 -Planning Commission Public Hearing Geld. 2,t4 j'sv- <br /> October;2001 - City Council Process. S"�n <br /> November,-2001 - Targeted for-adoption. -(4 N!e o4,!e <br /> Issues to Discuss: <br /> 1) Conflicting code criteria and how we handle it(examples: density and street connectivity). <br /> 2) Pre-development conferences and/or optional special stormwater management plan <br /> conference. <br /> 3) Change in submittal requirements to include Stormwater Quality Standards: Application <br /> forms,Property Review Checklist... <br /> 4) Incorporation of water quality features into mandatory landscaping.- e Wk.karebu e/`r''es4 4 <br /> 5) Adding stormwater to the "adjusting standards" section of LUCU?^L ot.kct 01`P4h2"''``• �) <br /> 6) Relationship of Stormwater Quality BMPs to Goal 5 natural resources. <br /> 7) Time frame for application review—when application is less than complete it's a problem. <br /> 8) Attempt to minimize types of applications that need a land use process because of <br /> Stormwater(commercial building permits—trying to address this in the ordinance). <br /> 9) Difference between needed housing standards and more subjective standards - level of <br /> specificity vs. conceptual. <br /> 10) Headwaters requirements. <br /> Conflicting Standards <br /> How resolved now: Usually the Hearings Official modifies staff recommendations after the <br /> public hearing. <br /> problem: Developers are hearing from different people in the organization, getting conflicting <br /> priorities based on areas of expertise. We don't want to become too certain about one standard <br /> too early in the process,because we may not be aware of the effects on the overall design. <br /> possible Solutions: <br /> a) Request developers to submit a specified set of baseline data early on(tree survey, geotech <br /> report,request of Property Review Checklist...). Have this baseline data reviewed by a team <br /> of internal professionals in a meeting. <br /> b) Check in with designers/developers while they are still designing (limited consultation). <br /> c) Pre-application form—design the form to require baseline data. Staff meet prior to the pre- <br /> application meeting to talk about the site/development. <br /> d) Allow developer to choose between providing baseline data or requesting the city provide <br /> baseline data for a charge. <br />