Memorandum of Understanding Template for Emergency Alerting to the Public

Similar documents
Participant Agreement. Updated December 1, 2016 and approved by the OK-First Advisory Committee

IPAWS: What Now? IPAWS: What Now. IPAWS: What Now. Integrated Public Alert and Warning System. How do I get assistance?

Template Instructions

Disaster Management (DM) Program Overview

BlackBerry AtHoc Network Crisis Communication. CAP Publishing and Processing Guide

ADDENDUM #1 Boulder Office of Emergency Management Ambulance Services for Boulder County RFS #

Emergency Operations Center Management Exercise Evaluation Guide

Questions 1-3 relate to Item 4 Data Sheet on page 12:

Forward. 1. Purpose. Page 1 of 5 Revision Date

Director, Major Projects and Resilience. To: Planning and Performance Committee 6 November 2014

I. PURPOSE III. PROCEDURE

Red Flag Policy and Identity Theft Prevention Program

Consent to Electronic Delivery of Periodic Statements, Disclosures and Notices

RFM Procedure 3: Certification Body Approval for Chain of Custody Standard. Alaska Responsible Fisheries Management (RFM) Certification Program 17065

Memorandum of Agreement

2. Goals of IRWM Plan Water management goals within the Tahoe Sierra IRWM Plan include but are not limited to:

Office for Interoperability and Compatibility Emergency Interoperable Standards Efforts

Nuclear/Radiological Incident Annex Nuclear Radiological Incident Taskforce National Radiological Emergency Preparedness Conference April 11, 2017

DISADVANTAGED BUSINESS ENTERPRISE PROGRAM. Unified Certification Program OKLAHOMA

COMMUNICATIONS EMERGENCY SUPPORT FUNCTION (ESF #2) FORMERLLY COMMUNICATIONS AND WARNING

Kansas City s Metropolitan Emergency Information System (MEIS)

( Utility Name ) Identity Theft Prevention Program

Bowling Green, KY Stormwater Best Management Practices October Appendix F EPSC Certified Contractor Forms

ach user guide business gateway TABLE OF CONTENTS

Provider Monitoring Process

Subscriber Registration Instructions

UF CEMP Support Group Annex: Public Safety

What should I do when something unexpected happens with an alert or warning?

EMERGENCY SUPPORT FUNCTION (ESF) 13 PUBLIC SAFETY AND SECURITY

Quick Start: Permission requests and approvals

Alberta Reliability Standards Compliance Monitoring Program. Version 1.1

ONBOARDING APPLICATION

ALL-HAZARDS EMERGENCY MESSAGE COLLECTION SYSTEM (HAZCOLLECT) NOTICE: This publication is available at:

HIDTA s Overdose Detection Mapping Application Program ODMAP ODMAP ODMAP free-of-charge

REGIONAL UTILITY COORDINATION PLAN. Portland, Oregon / Vancouver, Washington Metropolitan Area

The South Dakota Unified Certification Program Agreement. 700 Broadway Ave. Pierre, SD

2 ESF 2 Communications

Guidance of NOP Certification system Page 1/8

Glacier Valley Transit ADA & Title VI Complaint Procedures

Please print or type. Complete all areas of Agreement and Enrollment form, unless otherwise indicated.

Florida Health Information Exchange Subscription Agreement for Event Notification Service

TAPS Public Transit Published Charter Rates

NEWTON COUNTY OPEN RECORDS ACT POLICY

MASAS. Overview & Backgrounder Document. Consultation Package. CanOps

Security Standards for Electric Market Participants

WebEOC. User Guide. Version 8.1. County Emergency Managers Edition 6/5/17

TIER Program Funding Memorandum of Understanding For UCLA School of

SOUTHERN COMPANY DISTRIBUTION INTERCONNECTION POLICY

Fire Department Recognition Program

Unified Incident Command and Decision Support (UICDS)

IMPORTANT INSTRUCTIONS:

AUTOMATED RESOURCE MANAGEMENT SYSTEM (ARMS)

E-invoice. Service Description

Mississippi Medicaid. Mississippi Medicaid Program Provider Enrollment P.O. Box Jackson, Mississippi Complete form and mail original to:

End User Agreement Anthem Point of Care (POC)

Incident Reporting SOP

Memoranda of Understanding (MOU) & Memoranda of Agreements (MOA)

Introduction to the National Response Plan and National Incident Management System

OF ELECTRICAL AND ELECTRONICS ENGINEERS POWER & ENERGY SOCIETY

TARGETING CITIZENS WITH LOCATION BASED NOTIFICATIONS.

Section 1 Metrics: Community Adoption

CFC Charitable Giving User Guide

APPLICATION FOR DATABASE PRODUCT

Consensus Report: EMAC and EMS Resources for National Disaster Response. (from the June 20, 2007 EMS Stakeholders Meeting in Arlington, VA)

United Nations Environment Programme

[Utility Name] Identity Theft Prevention Program

National Preparedness System (NPS) Kathleen Fox, Acting Assistant Administrator National Preparedness Directorate, FEMA April 27, 2015

ETSI TS V8.2.0 ( )

March 27, Department of Homeland Security

Data Use and Reciprocal Support Agreement (DURSA) Overview

International Fire Service Accreditation Congress Delegation of Certification Authority

MARPA DOCUMENT MARPA Revision 1.1

MULTI-AGENCY COORDINATION SYSTEM PUBLICATION RESOURCE DESIGNATION SYSTEM FORMS PACKET MACS 400-3

Cell Phone Policy. 1. Purpose: Establish a policy for cell phone use and compensation allowance.

South East Region THIRA

Oracle Mission Critical Support Platform. General. Installation. Troubleshooting. Inventory and Discovery. Frequently Asked Questions Release 2.

FedRAMP: Understanding Agency and Cloud Provider Responsibilities

Webfont License End User License Agreement (EULA)

EMERGENCY SUPPORT FUNCTION #2 Communication, Information and Warning Systems

Reliability Standard Audit Worksheet 1

IA2. Flood (Including Dam Failure)

Emergency Support Function #12 Energy Annex. ESF Coordinator: Support Agencies:

1 Privacy Statement INDEX

Change Healthcare CLAIMS Provider Information Form *This form is to ensure accuracy in updating the appropriate account

Grid Security Policy

Online Banking Wire Transfer Enrollment

EMERGENCY MANAGEMENT

Webinar will start soon

Open Access. Definitions

Document Section: 3. Interoperability

Priority Ranking. Timeframe

FY2016 FCC Form 470 and Competitive Bidding

Therapy Provider Portal. User Guide

MHCC Emergency Notification System (ENS) Protocols

Beam Technologies Inc. Privacy Policy

Staff User Manual. Chapter 3 Contracts

Oracle Utilities Mobile Workforce Management

Response to Santa Barbara County Grand Jury Reports (1) Santa Barbara County Emergency Operations Center (2) Emergency Public Information

Created: Spring 2008; Last Modified: 10/12/2009 Step by Step Process: Please take these steps to complete the Review and Approval process.

Requirements for Initial Certification

Transcription:

Memorandum of Understanding Template for Emergency Alerting to the Public 1 Overview 1.1 Background The Integrated Public Alert and Warning System (IPAWS) provides a powerful tool for notifying the public with important lifesaving information IPAWS was developed to primarily provide a national system for presidential messages, but the system is available to State, local, and tribal entities. The current rules provide access to IPAWS at the county level. Many large cities, which do not represent entire geographical counties, would benefit from access. In addition, many incidents, such as a flood or wild land fire, extend beyond a single county or jurisdiction 1.2 Purpose This Memorandum of Understanding (MOU) template has been developed as a tool for states and counties to develop agreements with neighboring jurisdictions for the purpose of using IPAWS to notify the public of emergency incidents and protective actions. This template can be modified in any way to address local situations to provide the best service to the public and responders. An MOU should be developed for each County or entity that is an approved COG with IPAWS. This will allow the IPAWS Office to correctly set up the permissions for the COG in the IPAWS Integrator. 1.3 References Writing Guide for a Memorandum of Understanding (MOU) by SAFECOM CFR 47 Part 11 EMERGENCY ALERT SYSTEM CFR 47 PART 10 COMMERCIAL MOBILE ALERT SYSTEM

2 Components of a Memorandum of Understanding 2.1 Introduction The introduction describes the reason for the MOU and will serve as a background of the situation that leads to the development of the MOU. The introduction is intended to provide a high-level summary of the MOU. The following questions can guide the development of the introduction: Why is this MOU being created, to include the need being addressed and background? What agencies are participating in the MOU? Why is this MOU necessary? What agreements are set forth by this MOU? 2.2 Purpose The purpose should be a concise statement of the intention of the MOU. It explains how the agencies involved will use the MOU and under what circumstances. The following questions can guide the development of the purpose: When will it be used? How will it be used? 2.3 Scope The scope describes the specific extent of the MOU. It lists the agencies and the jurisdictions included in the agreement and describes their relationship. The following questions can guide the development of the scope: Contact information for all parties. List of FIPS Codes of the entity. List of authorized event codes allowed by the entity. When is the MOU in effect? What are the limits to using the system? 2.4 Definitions The definitions describe the terms and acronyms used in this MOU and for the operation of the systems of the MOU where coordination is required.

2.5 Policy The policy describes the operation of IPAWS to which the MOU is agreeing. This is a high-level description of the intent and operation of the systems. The following questions can guide the development of the policy: Who can use the system? What is permitted to be done on the system? Which event codes can be used. 2.6 Procedures The procedures describe in detail the steps each participant takes to operate in compliance with the policy. This is detailed in step-by-step instructions. 2.7 Changes to Memorandum of Understanding The updates section describes the process of maintaining the MOU over the period of the agreement. The following questions can guide the development of the updates section: How can the MOU be modified? How can the MOU be cancelled? If only one party of an MOU between three of more parties wants to cancel, what happens to the MOU? 3 Sample Memorandum of Understanding Sample text for an MOU is provided for reference and begins on the following page.

Memorandum of Understanding for Emergency Alerting to the Public 1 Introduction The jurisdictions of [insert counties or jurisdiction names here] recognize the need for interagency cooperation to enhance public alerting capabilities. This Memorandum of Understanding (MOU) allows the jurisdictions to improve their ability to warn the public of emergencies in a timely manner, where a multi-jurisdictional impact is likely. 2 Purpose This MOU will allow emergency notifications to reach those affected by an incident and help to eliminate duplicate or conflicting instructions. Each jurisdiction participating in this MOU can activate IPAWS in an emergency. 3 Scope This MOU is effective as of [Month Day, Year] and will continue until revoked by all parties following the procedures listed in section 7 Changes to MOU. The MOU may be used when there is an incident other than a weather event that has occurred in a respective jurisdiction, but which may impact an area outside of the incident jurisdiction and the incident may impact the outside jurisdiction within 30 minutes. Parties to the MOU are: Jurisdiction: POC: Address: City, State Zip: E-mail: Office phone: 24 x 7 phone: Event Codes Allowed: FIPS Code: 4 Definitions FEMA Federal Emergency Management Agency

IPAWS Integrated Public Alert and Warning System Memorandum of Understanding or MOU An agreement between two or more parties for the purpose of formalizing an agreed upon process or procedure. 5 Policy All parties agree that in the event of an emergency incident that meets the following criteria, the jurisdiction where the emergency originated can initiate an alert for any participating jurisdiction to this MOU. Incident Criteria: Event is not a weather emergency. (National Weather Service will lead these incidents.) The incident will impact people outside of the incident jurisdiction within 30 minutes of the onset. The incident s impact to people outside of the jurisdiction may be endangered if action is not taken by the public (such as evacuation or shelter in place) Jurisdiction A may alert for limited areas of the following jurisdictions o Jurisdiction B (FIPS 12345) o Jurisdiction C (FIPS 23456) Jurisdiction B may alert for limited areas of the following jurisdictions o Jurisdiction A (FIPS 34567) o Jurisdiction C (FIPS 23456) A message is limited to the following event codes: o CDW Civil Danger Warning o EVI Evacuate Immediate o FRW Fire Warning o HMW Hazardous Materials Warning o SPW Shelter in Place Alerts to other jurisdictions will be limited to the geographic area impacted, not an entire county or FIPS code. 6 Procedures The originating jurisdiction will use the following procedures: 1) Identify an incident that may impact neighboring jurisdictions. 2) Determine if that impact meets the policy of this MOU 3) Compose an IPAWS message that includes the impacted other jurisdictions geographic area. 4) Send the IPAWS message. 5) Contact impacted jurisdiction to provide detailed information on the incident.

6) Coordinate further alerts with all impacted jurisdictions. The impacted jurisdiction will use the following procedures: 1) Monitor IPAWS feeds for all incidents or messages for the jurisdiction. 2) Coordinate with originating jurisdiction for any ongoing alerts or follow up messages. 7 Changes to Memorandum of Understanding This MOU will be reviewed and reaccepted each year in January. The originating jurisdiction will send notification to each other party to the MOU that the MOU has been reviewed and notice of changes requested. If changes are requested to this MOU, the requesting jurisdiction will submit the respective changes to all other parties. Each party will review and provide acceptance, modification or rejection to the originating jurisdiction. Should all parties agree to the change(s), the originating jurisdiction will prepare a new version of the MOU for signature by all parties. If a jurisdiction elects to revoke the MOU, the respective jurisdiction will notify all other parties of the MOU in writing with a 30 day notice. Each other party will notify their intent to remain a party to the MOU. Remaining parties can continue the MOU in areas that do not pertain to the jurisdiction which has left the MOU. The jurisdiction wishing to revoke the MOU will prepare a new version without their jurisdiction s participation for signature by the other parties. The MOUS is fully revoked when there is only one or no parties remaining. The State needs to be notified of any changes to the MOU including changes of participants. A completed copy of the MOU will be forwarded to the State and to the Federal Emergency Management Agency (FEMA) IPAWS office.