Laserfiche WebLink
Task 2 —Emergency Response Plan (ERP) <br />Following the RRA, Arcadis will work with the City in developing an AWIA-compliant ERP. The <br />customized all -hazards ERP will be based upon current water sector guidance documents and <br />procedures including AWWA M19: Emergency Planning for Water and Wastewater Utilities (5th <br />edition) and G440: Emergency Preparedness Practices. Arcadis will also ensure the ERP meets <br />other state and federal requirements, as well as adapt the plan to the City's specific conditions and <br />needs as determined during the project. <br />Task 2.1— ERP Kickoff and Initial Planning Meeting <br />A separate kickoff meeting will be held for the ERP as this task will likely include different team <br />members both for Arcadis and the City. Again, the kickoff meeting will take place at the City <br />offices with local Arcadis team members and subject -matter experts. <br />For efficiency and to minimize travel costs, and in light of the team's recent work with the City on <br />the Gap Analysis, this meeting could be combined with the first ERP planning meeting. This will <br />focus on the establishment of the project team and a plan for necessary ERP development. Gaps in <br />the existing ERP will be reviewed and discussions will be facilitated to decide what items need to <br />be changed, as well as synchronization that needs to occur with other City plans. Arcadis will assist <br />in developing the ERP structure based on templates we have developed. <br />Deliverables: <br />0 ERP structure which meets regulatory requirements <br />Task 2.2 — Development Support and Planning Meetings <br />Two additional in -person meetings are proposed with Arcadis ERP development experts to support <br />content development. Before each meeting, Arcadis and the City will review the current content. <br />Support via email and phone calls will be provided as needed throughout the development process. <br />It is anticipated that Arcadis will provide significant support for content development, though <br />information and development by City staff will be required. <br />In a mid -development meeting, Arcadis will assemble, review, and disseminate the current content. <br />A review and discussion of updates and progress made on the ERP core content, annexes, and <br />appendices will be performed at the meeting, and additional information requests may be made to <br />the planning team to further develop and enhance the plan. <br />This meeting will also include interactive, scenario -based discussions for staff responsible for plan <br />implementation and response activities. This will support development of hazard- or function - <br />specific response flow diagrams and may require inclusion of additional staff and partners. <br />In preparation for a final planning meeting, Arcadis will assemble the latest ERP content and the <br />ERP development experts will review it. During the meeting, gaps will be discussed and <br />comments/questions from the planning team regarding the draft ERP will be discussed and <br />validated. At the completion of this meeting, final edits including to annexes and appendices will be <br />identified and assigned. <br />Task 2.3 — Plan Review and Finalization <br />Once assigned content has been completed, a final draft of the plan will be distributed to select staff <br />and leadership to provide review comments. Staff will be given two to three weeks, with more time <br />being added if requested by the City based on other needs and priorities. Arcadis will make limited <br />updates based on comments, and the City will receive a tracked changes version of the final plan so <br />they can review any changes and ensure concurrence. <br />Exhibit A, Scope of Basic Engineering Services <br />EJCDC E-520 Short Form of Agreement Between Owner and Engineer for Professional Services. <br />Copyright ©2009 National Society of Professional Engineers for EJCDC. All rights reserved. <br />Page 4 <br />