Laserfiche WebLink
2. The Plant Management shall assess the effectiveness of the evacuation drill <br />exercise and shall insure that corrective actions are implemented and <br />documented in the event the EA/CP evacuation protocol should fail. <br />8.6 Post -Emergency Response Protocol <br />QB REBUILDERS' EA/CP post emergency response actions are designed to mitigate the <br />opportunity of a secondary incident and prevent the recurrence of the incident through <br />investigation and corrective action. <br />8.6.1 Mitigation of Secondary Incident <br />1. The Plant Management shall take all necessary steps to prevent a secondary <br />incident as follows: <br />a. Monitor all pressure valves; <br />b. Inspect for any leaks or cracks in pipes, valves, tanks, drums and <br />cylinders; <br />C. Inspect for gas generation; <br />d. Segregate potential non -compatible materials; <br />e. Shut down all potentially impacted operations <br />2. The Plant Management shall specify the frequency of monitoring or <br />inspection based on the nature of the initial emergency incident, types of <br />materials or operations/processes involved and the likelihood of a secondary <br />incident. <br />3. All operations that were shut down in response to the incident shall not be <br />reactivated until the Plant Management has given the "ALL CLEAR" order <br />and only after the incident has been abated and is under control. <br />8.6.2 Incident Investigation and Implementation of Corrective Actions <br />1. The Plant Manager, or his designated representative, shall be responsible <br />for initiating all post -incident investigations to determine incident cause and <br />corrective actions, including employee debriefing and retraining. <br />2. The Plant Manager shall conduct debriefing of site personnel and local <br />agencies to assess preparedness and prevention activities, response <br />activities , injury control and evacuation procedures. <br />3. Based on the investigation, corrective actions shall be identified and <br />implemented. <br />Draft HMMP <br />March, 2000 HMMP-39 <br />