X hits on this document





46 / 66

Ellsworth Sourcewater Protection Plan, Appendix B December, 2004 Page 43 of 63

APPENDIX C (continued)

After the potential hazards that the water system might experience and the vulnerability of the water system’s components have been identified, the planning team can develop the ERP. The ERP must detail what actions should be taken to respond to both potential and actual emergencies in a manner that will ensure continuity of essential services, minimize the duration of the emergency, and protect the safety of its employees. The ERP must be specific in addressing who will respond to the emergency, what actions are required, where key items can be located, when actions should be taken, and how the public will be notified. Such details may include:

    • Identification of an emergency response team.

  • Method of contacting water system personnel during an emergency.

    • Delineation of responsibilities and organizational structure.

    • Designation of personnel to release information to the public.

  • Development of background material for news release (see Attachment F).

  • Protocol for determining what conditions would prompt a water system to discontinue use of a water source.

  • Procedures for restricting water use.

  • Procedures for providing alternate sources of water to the customer.

  • Prioritization of customers’ need for water service.

  • Directory of key personnel and agencies including The Maine Drinking Water Program, Department of Environmental Protection, The Public Utilities Commission, Emergency Response Agencies, local Fire Department, local Police Department, local Board of Health, Newspapers, Radio Stations, Television Stations.

  • Identification of customers with special needs such as schools, hospitals, dialysis centers, nursing homes, large institutions and commercial uses.

  • Identification of contractors that can provide materials, equipment, or services and timeframes for implementation.

  • Identification of necessary security measures.

The process of developing an ERP may identify additional actions that can be taken by the water system in order to be better prepared for an emergency. The following are examples of actions that the water systems might take in order to be better prepared for an emergency:

  • Modify the design and operations of facilities.

  • Determine the time needed to obtain necessary materials during an emergency incident.

  • Acquire redundant components that can be built into the system, available on site, or available from identified contractors.

  • Establish mutual aid agreements that identify the amount of water available and are reviewed periodically.

  • Inventory activities in Zone I/II, Zone A/B, Interim Wellhead Protection Areas (IWPA) and the watershed of Class B drinking water river intakes.

  • Review data from Source Water Protection Program (SWAP).

  • Establish liaison with organizations and people responsible for activities that may have serious impacts on the water system.

  • Establish liaison with local spill response and other emergency response planning agencies.

  • Exercise isolation valves, emergency connections, and other stand-by equipment.

  • Provide emergency response training.

  • Periodically review and update the ERP.

  • Compile Material Data Safety Sheet (MSDS) information of all chemicals used.

  • Develop and update detailed water system map that identifies type, size and location of mains and valves.

  • Determine costs associated with recommended improvements and seek funding.

  • Identify a phased approach to reduce water consumption during drought related water shortages and identify triggering criteria for the various phases of reduced consumption.

Once the initial ERP has been completed, it must be tested and assessed. Staff must to be trained on how to use the document. The ERP must be readily available. Drills should be conducted periodically to assess its effectiveness. The ERP should be reviewed and updated annually.

MRWA Contingency Plan Template 4/03

Page 18

Document info
Document views206
Page views206
Page last viewedThu Jan 19 04:29:09 UTC 2017