<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Re-ordering/Re-arranging Ordinance Articles</title>
	<atom:link href="http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 04 Nov 2011 06:28:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: StormBlog52</title>
		<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/comment-page-1/#comment-31</link>
		<dc:creator>StormBlog52</dc:creator>
		<pubDate>Wed, 18 Nov 2009 16:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://ec.dupageco.org/StormWaterUpdate/?p=85#comment-31</guid>
		<description>Remove the reply &quot;I agree with these comments&quot;  Ihis was entered thjis to resolve problems I was having with reading the first messages I got at Bob&#039;s request.</description>
		<content:encoded><![CDATA[<p>Remove the reply &#8220;I agree with these comments&#8221;  Ihis was entered thjis to resolve problems I was having with reading the first messages I got at Bob&#8217;s request.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StormBlog52</title>
		<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/comment-page-1/#comment-19</link>
		<dc:creator>StormBlog52</dc:creator>
		<pubDate>Tue, 03 Nov 2009 15:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://ec.dupageco.org/StormWaterUpdate/?p=85#comment-19</guid>
		<description>I agree with these comments.</description>
		<content:encoded><![CDATA[<p>I agree with these comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StormBlog42</title>
		<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/comment-page-1/#comment-17</link>
		<dc:creator>StormBlog42</dc:creator>
		<pubDate>Fri, 30 Oct 2009 21:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://ec.dupageco.org/StormWaterUpdate/?p=85#comment-17</guid>
		<description>I agree that the questions and concerns in 1992 are different than those of today so the Ordinance could be reorganized to put requirements up front for ease of use.  And as we move forward and potentially add/change/revise regulations, the organization will need to be discussed further to accommodate revisions.  But I think it’s important that the Ordinance remains a technical document as the target audience should be the design professional.  After all, many parts of the Ordinance require a technical submittal depending on the “development impact”.  In other parts of society we don’t allow just anybody to design and perform technical work, as a certain base of knowledge and experience is required, and the Stormwater Ordinance shouldn’t be any different.  

In my opinion locking hard review deadline time frames into the Ordinance is problematic.  The review time frame issue is a decision that each political body needs to ponder while striking a balance between the turn around times and the cost.  Each public body should be free to set their own review deadlines as a matter of public policy.  Recently, several communities have become complete waiver communities in part so they could control their own review process.  They made the conscious decision to take on the cost of the complete review process in order to balance the desires of their community.</description>
		<content:encoded><![CDATA[<p>I agree that the questions and concerns in 1992 are different than those of today so the Ordinance could be reorganized to put requirements up front for ease of use.  And as we move forward and potentially add/change/revise regulations, the organization will need to be discussed further to accommodate revisions.  But I think it’s important that the Ordinance remains a technical document as the target audience should be the design professional.  After all, many parts of the Ordinance require a technical submittal depending on the “development impact”.  In other parts of society we don’t allow just anybody to design and perform technical work, as a certain base of knowledge and experience is required, and the Stormwater Ordinance shouldn’t be any different.  </p>
<p>In my opinion locking hard review deadline time frames into the Ordinance is problematic.  The review time frame issue is a decision that each political body needs to ponder while striking a balance between the turn around times and the cost.  Each public body should be free to set their own review deadlines as a matter of public policy.  Recently, several communities have become complete waiver communities in part so they could control their own review process.  They made the conscious decision to take on the cost of the complete review process in order to balance the desires of their community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StormBlog23</title>
		<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/comment-page-1/#comment-14</link>
		<dc:creator>StormBlog23</dc:creator>
		<pubDate>Mon, 26 Oct 2009 15:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://ec.dupageco.org/StormWaterUpdate/?p=85#comment-14</guid>
		<description>Yes, the ordinance needs to be reorganized.  It is not user-friendly.  Anyone who doesn&#039;t use it every day will find their eyes glazed over long before they get to page 57 to find what they need to know.  Move all the administrative sections to the back of the ordinance.  Write section headings that make it easier to find the things that infrequent users need to know--floodplain requirements, wetland requirements, tabular submittal requirements, sediment and erosion control, development size and requirements, requirements for property that is not developing, etc.  The primary target audience should be those who don&#039;t use the ordinance daily--developers, homeowners doing small projects, new consultants.

Reorganizing will be a challenge, though.  Many requirements apply to more than one type of project, so if you organize by project type, then you end up repeating a lot.  Suggestion:  Organize by project, but for the sections that apply to more than one type of project, put that information in a later section and include it by reference in the &quot;project type&quot; section.</description>
		<content:encoded><![CDATA[<p>Yes, the ordinance needs to be reorganized.  It is not user-friendly.  Anyone who doesn&#8217;t use it every day will find their eyes glazed over long before they get to page 57 to find what they need to know.  Move all the administrative sections to the back of the ordinance.  Write section headings that make it easier to find the things that infrequent users need to know&#8211;floodplain requirements, wetland requirements, tabular submittal requirements, sediment and erosion control, development size and requirements, requirements for property that is not developing, etc.  The primary target audience should be those who don&#8217;t use the ordinance daily&#8211;developers, homeowners doing small projects, new consultants.</p>
<p>Reorganizing will be a challenge, though.  Many requirements apply to more than one type of project, so if you organize by project type, then you end up repeating a lot.  Suggestion:  Organize by project, but for the sections that apply to more than one type of project, put that information in a later section and include it by reference in the &#8220;project type&#8221; section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StormBlog52</title>
		<link>http://ec.dupageco.org/StormWaterUpdate/index.php/2009/10/19/re-orderingre-arranging-ordinance-articles/comment-page-1/#comment-10</link>
		<dc:creator>StormBlog52</dc:creator>
		<pubDate>Wed, 21 Oct 2009 13:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://ec.dupageco.org/StormWaterUpdate/?p=85#comment-10</guid>
		<description>Thought I would try this and see how it works.  

The issue is is the ordianance user friendly?  Is it easy to find things?  It may be easy for the county staff to use but hard for customers seeking guidance that are not familiar with the ordinance.  This issue brings up a larger question that is are we just tweaking things or are we going to reinvent things or something in between.  I think we need to reorder things to the extent necessary to make the ordinance user friendly.  I am not sure that it is user friendly now.  The administrative process needs to be folded into the ordinanance or added as an appendix.  Review deaadlines need to be locked into hard dates that must be met.  The time element is critical to any public or private project.  We are adding  a new redevelopment section.  THis will be difficult.  Many of the future submittals are likely to be in that category.  So reordering seems to be useful but difficult.</description>
		<content:encoded><![CDATA[<p>Thought I would try this and see how it works.  </p>
<p>The issue is is the ordianance user friendly?  Is it easy to find things?  It may be easy for the county staff to use but hard for customers seeking guidance that are not familiar with the ordinance.  This issue brings up a larger question that is are we just tweaking things or are we going to reinvent things or something in between.  I think we need to reorder things to the extent necessary to make the ordinance user friendly.  I am not sure that it is user friendly now.  The administrative process needs to be folded into the ordinanance or added as an appendix.  Review deaadlines need to be locked into hard dates that must be met.  The time element is critical to any public or private project.  We are adding  a new redevelopment section.  THis will be difficult.  Many of the future submittals are likely to be in that category.  So reordering seems to be useful but difficult.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

