04.03.2013 Views

Port-Wide Sewer System Management Plan(SSMP) - Port of Oakland

Port-Wide Sewer System Management Plan(SSMP) - Port of Oakland

Port-Wide Sewer System Management Plan(SSMP) - Port of Oakland

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

equipment shall be available to respond to any SSO location and shall be dispatched to the<br />

site <strong>of</strong> a reported SSO immediately. Also, additional maintenance personnel shall be “on<br />

call” should extra crews be needed.<br />

Dispatching duties are normally performed by either the Aviation Maintenance/Construction<br />

Supervisor, Utilities Supervisor, or the Equipment <strong>System</strong>s Superintendent, depending on<br />

the nature <strong>of</strong> the problem. Dispatching personnel should record all relevant overflow<br />

information and dispatch response crews, as needed.<br />

It is the responsibility <strong>of</strong> the first personnel who arrive at the site <strong>of</strong> an overflow in the<br />

aviation area to protect the health and safety <strong>of</strong> the public to the extent possible. Aviation<br />

personnel are responsible for identifying the cause <strong>of</strong> the overflow, requesting additional<br />

resources as needed, taking steps to contain or divert the overflow, and taking steps to stop<br />

the overflow if possible.<br />

Following initial attempts for overflow correction and containment, Aviation personnel<br />

should contact the Environmental Compliance Supervisor for guidance on how to proceed.<br />

For smaller wastewater spills, Aviation staff may be able to use wash-down water to direct<br />

wastewater collected in the spill area back into a manhole and into the collection system.<br />

For larger spills, the Environmental Compliance Supervisor typically contacts a Hazardous<br />

Material Contractor to clean up and disinfect the affected area. Figure 7.1 summarizes the<br />

Aviation SSO Field Response Action <strong>Plan</strong>.<br />

7.2.1.3<br />

Notification <strong>of</strong> Regulatory Agencies<br />

The regulatory agencies that must be notified in the event <strong>of</strong> a SSO vary depending on the<br />

type <strong>of</strong> discharge. Likewise, the time frame in which the appropriate agencies must be<br />

notified depends on the type <strong>of</strong> discharge. Table 3.1 and Section 5.0 <strong>of</strong> the <strong>Port</strong> OERP<br />

provide a summary <strong>of</strong> which regulatory agencies must be notified and under what<br />

conditions. These requirements are the same regardless <strong>of</strong> the responsible <strong>Port</strong> division.<br />

However, the SSO reporting chain <strong>of</strong> communication does vary depending upon the<br />

responsible <strong>Port</strong> division. A flow chart identifying the flow <strong>of</strong> information regarding a<br />

potential SSO in the aviation area is provided in Figure 3.2 and Section 5.0 <strong>of</strong> the <strong>Port</strong><br />

OERP for reference.<br />

7.2.1.4<br />

Emergency Response <strong>Plan</strong> Awareness and Training<br />

Section 7.0 <strong>of</strong> the <strong>Port</strong> OERP contains provisions concerning the distribution, maintenance,<br />

and awareness <strong>of</strong> the provisions presented in that document. Copies <strong>of</strong> the OERP and any<br />

amendments should be distributed to all <strong>of</strong> the aviation personnel that are heavily involved<br />

with the <strong>SSMP</strong> or OERP programs. It is also recommended that the appropriate aviation<br />

personnel be trained concerning the provisions <strong>of</strong> the OERP.<br />

May 2010 7-3<br />

pw://Carollo/Documents/Client/CA/<strong>Port</strong> <strong>of</strong> <strong>Oakland</strong>/8239A00/Deliverables/Ch07 (FinalA)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!