Laserfiche WebLink
<br />© 2004-2016 DKF Solutions Group, LLC. All rights reserved. OERP Page 21 <br />For reporting purposes, if one SSO event of any category results in multiple appearance points in a <br />sewer system, a single SSO report is required in CIWQS that includes the GPS coordinates for the <br />location of the SSO appearance point closest to the failure point, blockage or location of the flow <br />condition that cause the SSO, and descriptions of the locations of all other discharge points associated <br />with the single SSO event. <br /> <br />11.2 Complaint Records <br /> <br />The City maintains records of all complaints received whether or not they result in sanitary sewer <br />overflows. The information collected includes: <br />• Date, time, and method of notification <br />• Date and time the complainant or informant first noticed the SSO or occurrence related to the <br />call <br />• Narrative description describing the complaint <br />• A statement from the complainant or informant, if they know, of whether or not the potential <br />SSO may have reached waters of the state <br />• Name, address, and contact telephone number of the complainant or informant reporting the <br />potential SSO (if not reported anonymously) <br />• Follow-up return contact information for each complaint received (if not reported anonymously) <br />• Final resolution of the complaint with the original complainant <br />• Work service request information used to document all feasible and remedial actions taken <br /> <br />The procedure is as follows: <br />1. Public Works Administration receives the call, enters the information into the PublicStuff <br />program, and dispatches via pager to the Sewer Call Truck. Alternatively, the public can report <br />an SSO/Backup online through PublicStuff on the City’s web site or through the PublicStuff <br />mobile app. <br />2. The Maintenance Crew will respond to service request and complete the Sanitary Sewer <br />Overflow Report. <br />3. The Maintenance Crew will forward the SSO Report to the Public Works Supervisor. S/he will <br />review, add/complete any missing info and initiate an SSO file. Once any regulatory reporting <br />required is completed, s/he will close and archive the file in hardcopy and electronic format. <br />4. Public Works Supervisor will archive the service call request (work order/SSO Report/Other) in <br />hardcopy and electronically. <br /> <br />All records will be maintained for a minimum of five years whether or not they result in an SSO. <br /> <br /> <br />12. Post SSO Event Debriefing <br /> ref. SWRCB Order No. 2006-0003-DWQ Element 6(d) <br /> <br />Every SSO event is an opportunity to evaluate the City response and reporting procedures. Each overflow <br />event is unique, with its own elements and challenges including volume, cause, location, terrain, climate, and <br />other parameters. <br />6.2.A. - Page 115