Project Management Group

1. Project Management Group Status Report to the Commercial Mobile Service Alert Advisory Committee March 12, 2007 Jeffery Goldthorp, PMG Leader (Designee)

2. PMG Mission • The Program Management Group (PMG) is the overall management entity of the Commercial Mobile Service Alert Advisory Committee (Advisory Committee). The PMG will manage and oversee the work of the Advisory Committee’s informal working groups (Working Groups), and will act as principal liaison between those groups and the Committee. The PMG will be tasked with overall responsibility for ensuring that the Working Groups operate in a manner consistent with the statutory objectives of the WARN Act. Responsibilities include: • Establish a master schedule with major timelines and deliverables for each Working Group. • Report to the Advisory Committee Chair on a monthly basis regarding the progress of the Working Groups. • Assemble the work product of the Working Groups into the draft recommendations called for by the WARN Act and deliver these draft recommendations to the Advisory Committee Chair in sufficient time to allow the Chair to present the recommendations to the full Committee for review, vote, and submission to the FCC by October 12, 2007, one year of enactment of the WARN Act.

3. PMG Participants • FCC – Lead • FEMA – Alerting Interface Group Leader • Contra Costa County, CA - Deputy • Verizon Wireless – Alerting Gateway Group Leader • CTIA - Deputy • AT&T/Cingular – Communications Technology Group Leader • Sprint-Nextel - Deputy • City of New York – User Needs Group Leader • T-Mobile - Deputy

4. PMG Status • Held monthly face-to-face meetings with interim conference calls. • As of 2/15/2007, held 3 face-to-face meetings • Began work on a set of end-to-end draft requirements using inputs from Informal Working Groups. • Agreed on a set of initial PMG Working Assumptions at 2/15 meeting. • Assigned a series of questions to Informal Working Groups to address by March meeting. • Facilitating coordination among Informal Working Groups. • On track for making recommendations to the Advisory Committee in a timely fashion.

5. PMG Draft Conclusions • The alerting initiation platform should perform an alert aggregation function, presenting an integrated alert interface to the alerting gateway that includes alerts from all authorized sources. This alerting initiation platform should be administered by a government agency to ensure authenticity and prioritization of alerts. • The Commercial Mobile Alerting System (CMAS) must only be used for the dissemination of public alerts regarding immediate, serious and likely threats to life, health or property; and for updates, amendments and cancellations of such alerts. • The CMAS must be available for alert origination only on the authority of federal, tribal, state and local government officials with responsibilities for public safety, health and security. • The CMAS must support a method for credible and reliable authentication of authorized originators. • The CMAS must support a method for ensuring the integrity of message content as delivered to the carrier, ensuring that the alerts delivered to that point accurately reflect the originator’s input. • The CMAS must provide reliable attribution of each alert message to its authorized originator.

6. PMG Draft Conclusions • Responsibility for the accuracy, completeness and appropriateness of CMAS alert content must rest solely with the originating agency. • Within the constraints of a standard input format, the CMAS must not filter, edit, amend or restrict any authorized originator’s message content or intent, with the exception of such automatic and consistent transformations as may be required for technical purposes. • The CMAS must deliver all alerts to the carrier from authorized originators without avoidable procedural or technical delays. However, where multiple alerts are in process at the same time, they may be sequenced on the basis of the urgency, severity and certainty of the alert information. • The CMAS should, if possible, provide a unique and consistent user experience to all alert recipients, using, for example, standardized audio tones, vibration cadences and language-independent visual symbology. These standard signals must be available for authorized use within the CMAS without charge, but must be legally protected against other uses. • The CMAS must, to the greatest extent feasible, restrict alert delivery to recipients located in the geographic area at risk and minimize delivery in other areas.

7. PMG Draft Conclusions • The alert may be retransmitted in the geographic area until the alert expires, is updated, or is cancelled subject to the capabilities of the delivery technologies. Any mobile device users entering the target area may receive the emergency alert subject to the delivery technologies, device capabilities and inter-carrier roaming agreements. • The CMAS must provide a consistent technical interface to alert origination applications using the OASIS CAP format, which must be available at multiple geographic and network locations. Any authorized originator must be able to submit an alert through any reachable instance of the input interface. • The CMAS must provide reasonable redundancy to avoid, to the greatest extent feasible, the creation of a single point of failure. • The CMAS must implement a comprehensive trust model for the issuance and maintenance of access credentials. • Specific legal authority must be established for prohibiting unauthorized or improper use of the CMAS or for willful interference with its functioning.