My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
06-13-11 Council Agenda & Packet
sbend
>
Public
>
Common Council
>
Common Council Agenda Packets
>
2011
>
06-13-11 Council Agenda & Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2011 3:38:12 PM
Creation date
6/9/2011 2:48:43 PM
Metadata
Fields
Template:
City Council - City Clerk
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
217
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
enforcement action against a User for a bypass, unless <br />i. Bypass was unavoidable to prevent loss of life, personal <br />severe pro <br />or se property damage, <br />injury, e._ r dama <br />ii. There w_ ere no feasible alternatives to the bypass, such <br />as the use of auxiliary treatment facilities,_ retention of <br />untreated wastes, . or maintenance during normal periods of <br />equipment downtime. This condition is not satisfied if <br />ade uate_ back -u a uipment should have .____ <br />_ q p q been installed in <br />the of reasonable engineering judgment to prevent <br />a bypass which occurred during normal periods of <br />equipment downtime or preventive maintenance; and• <br />iii. The User submitted as required under <br />fore. -going Subsection (3) of this section. <br />0) The Director may approve an anticipated bypass, after <br />considering its adverse effects if the Director determines that it <br />will meet the three conditions listed in paragraph (d)(1) of this <br />Section 17 -14. <br />LX) U,pset <br />Q) For the purposes of this Section- upset means an exceptional <br />incident in which there is unintentional and temporary noncompliance with <br />categorical_ Pretreatment Standards because of factors beyond the <br />reasonable control of the User. An upset does not include noncompliance <br />to the extent caused by operational error, improperly designed treatment <br />facili.ties,_.inadeguate_ treatment facilities, lace of preventive maintenance <br />or careless or improper operation. <br />An upset shall constitute an affirmative defense to an action <br />brought_ for noncompliance_ _with categorical Pretreatment Standards if the <br />requirements ofparagrraph (c), below, are met. <br />A_ User who wishes to establish the affirmative defense of upset <br />shall demonstrate _through properly signed, contemporaneous operating <br />logs, or other relevant evidence that: <br />La) An upset occurred and the User can identify the caase(sl of <br />the upset-, <br />67 <br />
The URL can be used to link to this page
Your browser does not support the video tag.