<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml.xsl"?><PerformancePlanOrReport xmlns="http://www.stratml.net/PerformancePlanOrReport" Type="Strategic_Plan"><id/><Name>Integrated Public Alert and Warning System (IPAWS): Strategic Plan Fiscal Year 2014 - 2018</Name><Description>During an emergency, Federal, State, territorial, tribal, and local officials and emergency managers provide their communities with life-saving information as quickly as possible. IPAWS modernizes the nation’s alert and warning infrastructure capabilities through the integration of state-of-the-art technologies. IPAWS disseminates alerts and messages through more communications pathways to more people before, during, and after a disaster than any previous system in our nation’s history. In the event of a national emergency, the President will be able to use IPAWS to send a message to the American people quickly, easily, and simultaneously through multiple dissemination channels in order to reduce loss of life and property damage.  In addition, IPAWS provides State, territorial, tribal, and local governments with the capability to integrate their alert and warning systems with the national alert and warning infrastructure, as well as the capability to generate alerts and warnings of their own. In this way, IPAWS increases the resilience of local systems and provides additional means by which life-saving information can be distributed to residents before, during, and after a crisis.</Description><OtherInformation>To provide this next generation capability, the IPAWS PMO continues to embrace the vision, mission, goals, and objectives identified in this strategy. </OtherInformation><StrategicPlanCore><Organization><Name>Federal Emergency Management Agency</Name><Acronym>FEMA</Acronym><Identifier>_f3aea7da-0276-40be-8963-931fdd9d37af</Identifier><Description/><Stakeholder><Name>Antwane V. Johnson</Name><Description>Director, IPAWS PMO, DHS FEMA National Continuity Programs</Description></Stakeholder><Stakeholder><Name>IPAWS Partners</Name><Description>The IPAWS PMO’s partners are divided into five major functional groups: (1) the American people; (2) Federal executive governance and legislative oversight; (3) Federal, State, territorial, tribal, and local alerting authorities; (4) private sector industry; and (5) non-profit and advocacy organizations.    The IPAWS PMO collaborates with recognized Government, industry leaders, and technical experts to ensure that IPAWS incorporates the latest technology, and is practical for public safety officials at all levels of Government. </Description></Stakeholder><Stakeholder><Name>American People</Name><Description/></Stakeholder><Stakeholder><Name>Private Sector Industry</Name><Description/></Stakeholder><Stakeholder><Name>Non-Profit Organizations</Name><Description/></Stakeholder><Stakeholder><Name>Advocacy Organizations</Name><Description/></Stakeholder><Stakeholder><Name>Government Officials</Name><Description/></Stakeholder><Stakeholder><Name>Industry Leaders</Name><Description/></Stakeholder><Stakeholder><Name>Technical Experts</Name><Description/></Stakeholder><Stakeholder><Name>Federal Executives</Name><Description/></Stakeholder><Stakeholder><Name>Legislative Overseers</Name><Description/></Stakeholder><Stakeholder><Name>Federal Alerting Authorities</Name><Description/></Stakeholder><Stakeholder><Name>State Alerting Authorities</Name><Description/></Stakeholder><Stakeholder><Name>Territorial Alerting Authorities</Name><Description/></Stakeholder><Stakeholder><Name>Tribal Alerting Authorities</Name><Description/></Stakeholder><Stakeholder><Name>Local Alerting Authorities</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS Branches</Name><Description>The IPAWS Division is organized around the operational functions required to complete its mission and achieve the requirements established under EO 13407.  The IPAWS PMO consists of four branches/teams: Engineering, Project Management, Business Operations, and Interagency Coordination and Special Studies. Each one plays a critical role in delivering the IPAWS mission and vision.   </Description></Stakeholder>
            <Stakeholder>
                <Name>IPAWS Engineering Branch </Name>
                <Description>The Engineering Branch is primarily responsible for program management, development, and maintenance activities for the IPAWS-OPEN application. The responsibilities include:  </Description>
                <Role>
                    <Name/>
                    <Description>* Identification, integration, and, at times, influence of  standards and specifications that enable interoperability of communications systems * Implement, enhance, and maintain the Commercial Mobile Alert System  (CMAS)/Wireless Emergency Alerts (WEAs) capability  * Act as the Co-Chair for the Technology Working Group and organize, participate in, or lead other groups such as the IPAWS Special Interest Group  * Act as the liaison with the DHS Science &amp; Technology Directorate  * Explore and evaluate emerging technologies and social media applications for inclusion or integration with IPAWS-OPEN when there are opportunities to reach more American people with alerts and warnings</Description>
                    <RoleType>Performer</RoleType>
                </Role>
            </Stakeholder>
            <Stakeholder>
                <Name>IPAWS Project Management Branch </Name>
                <Description>The Project Management Branch has primary responsibility for program documentation, security, National EAS coverage, modernization, and sustainment. The branch is organized to serve specific functions, including:  </Description>
                <Role>
                    <Name/>
                    <Description>* Sustain and provide assurance that EAS is available and operable under all conditions   * Modernize EAS to enhance its capabilities and resilience  * Restore EAS coverage to maintain 90% population coverage of the American people  * Develop, establish, and maintain standards, procedures, and guidelines to promote the security and uninterrupted operation of IPAWS computer-based application systems </Description>
                    <RoleType>Performer</RoleType>
                </Role>
            </Stakeholder>
            <Stakeholder>
                <Name>IPAWS Business Operations Branch</Name>
                <Description>The Business Operations Branch is primarily responsible for providing oversight to the program’s contracts, managing the program’s finances, and adhering to external reporting requirements. The branch’s main responsibilities fall under the following:</Description>
                <Role>
                    <Name/>
                    <Description>* Provide Contracting Officer Representative services and expertise, and execute the associated responsibilities  * Develop and implement internal controls for IPAWS finances, schedule tracking, status reporting, and acquisition activities  * Meet Federal, DHS, FEMA, and NCP financial management and reporting requirements</Description>
                    <RoleType>Performer</RoleType>
                </Role>
            </Stakeholder>
            <Stakeholder>
                <Name>IPAWS Interagency Coordination &amp; Special Studies Branch</Name>
                <Description>The Interagency Coordination and Special Studies Team is responsible for managing certain activities that directly contribute to the IPAWS mission, but are outside of IPAWS-OPEN and PEP architecture. These activities often include strategic outreach and engagement and special studies or research projects. To that end, the team’s responsibilities are to: </Description>
                <Role>
                    <Name/>
                    <Description>* Conduct, oversee, coordinate, and respond to special studies in areas that are of particular importance or interest to IPAWS operations, including:  * Participate and contribute to the National Infrastructure Protection Plan  * Represent IPAWS in the National Level Exercise (NLE) program  * Conduct and manage the strategy and activities for outreach, strategic engagement, education, and training</Description>
                    <RoleType>Performer</RoleType>
                </Role>
            </Stakeholder><Stakeholder><Name>IPAWS Federal Executive Government Partners</Name><Description/></Stakeholder><Stakeholder><Name>The White House, Executive Office of the President</Name><Description/></Stakeholder><Stakeholder><Name>White House Communications Agency (WHCA)</Name><Description/></Stakeholder><Stakeholder><Name>White House Military Office (WHMO)</Name><Description/></Stakeholder><Stakeholder><Name>Department of Defense (DOD)</Name><Description/></Stakeholder><Stakeholder><Name>DOD Joint Interoperability Test Command (JITC)</Name><Description/></Stakeholder><Stakeholder><Name>DOD Space and Naval Warfare Systems Command (SPAWAR)</Name><Description/></Stakeholder><Stakeholder><Name>Department of Health and Human Services (HHS)</Name><Description/></Stakeholder><Stakeholder><Name>HHS Emergency Management Office</Name><Description/></Stakeholder><Stakeholder><Name>Department of Homeland Security (DHS)</Name><Description/></Stakeholder><Stakeholder><Name>DHS Cyber Security and Telecommunications</Name><Description/></Stakeholder><Stakeholder><Name>DHS Executive Leaderships</Name><Description/></Stakeholder><Stakeholder><Name>DHS Office of Civil Liberties, Civil Rights, and Children’s Working Group</Name><Description/></Stakeholder><Stakeholder><Name>DHS Operations</Name><Description/></Stakeholder><Stakeholder><Name>DHS Policy</Name><Description/></Stakeholder><Stakeholder><Name>DHS Science and Technology</Name><Description/></Stakeholder><Stakeholder><Name>Department of Justice (DOJ)</Name><Description/></Stakeholder><Stakeholder><Name>Department of Justice, Office of Justice Programs (AMBER Alerts)</Name><Description/></Stakeholder><Stakeholder><Name>Federal Bureau of Investigations, National Capitol Region Office</Name><Description/></Stakeholder><Stakeholder><Name>Federal Communications Commission (FCC)</Name><Description/></Stakeholder><Stakeholder><Name>FCC Public Safety and Homeland Security Bureau (PSHSB)</Name><Description/></Stakeholder><Stakeholder><Name>Federal Emergency Management Agency (FEMA)</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Acquisition Program Office (APO)</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Emergency Management Institute</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Executive Leadership</Name><Description/></Stakeholder><Stakeholder><Name>FEMA National Continuity Programs Directorate</Name><Description/></Stakeholder><Stakeholder><Name>FEMA National Preparedness Directorate</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Office of External Affairs</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Office of Disability Integration and Coordination (ODIC)</Name><Description/></Stakeholder><Stakeholder><Name>FEMA Regional Communications Coordinators Working Group (RECCWG)</Name><Description/></Stakeholder><Stakeholder><Name>National Oceanic and Atmospheric Administration (NOAA)</Name><Description/></Stakeholder><Stakeholder><Name>National Weather Service (NWS)</Name><Description/></Stakeholder><Stakeholder><Name>NOAA Regional External Affairs</Name><Description/></Stakeholder><Stakeholder><Name>National Security Council (NSC)</Name><Description/></Stakeholder><Stakeholder><Name>Nuclear Regulatory Commission</Name><Description/></Stakeholder><Stakeholder><Name>Chemical Stockpile Emergency Preparedness Program (CSEPP)</Name><Description/></Stakeholder><Stakeholder><Name>Critical Infrastructure Partnership Advisory Council (CIPAC)</Name><Description/></Stakeholder><Stakeholder><Name>Radiological Emergency Preparedness Program (REPP)</Name><Description/></Stakeholder><Stakeholder><Name>State, Local, Tribal, and Territorial Government Coordinating Council (SLTTGCC)</Name><Description/></Stakeholder><Stakeholder><Name>US Park Police</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS Legislative Government Partners</Name><Description>The IPAWS PMO engages with Congressional Committees that have legislative oversight of IPAWS. Quarterly reports are provided to these committees and IPAWS PMO leadership regularly delivers updates on IPAWS implementation to members on these committees. The IPAWS PMO also conducted an interactive end-to-end IPAWS concept of operations demonstration for members of Congress and their staff at the US Capitol Visitors Center.</Description></Stakeholder><Stakeholder><Name>United States Congress</Name><Description/></Stakeholder><Stakeholder><Name>United States Senate Committee on Appropriations</Name><Description/></Stakeholder><Stakeholder><Name>United States Senate Committee on Homeland Security and Governmental Affairs</Name><Description/></Stakeholder><Stakeholder><Name>United States House of Representatives Committee on Appropriations</Name><Description/></Stakeholder><Stakeholder><Name>United States House of Representatives Committee on Homeland Security</Name><Description/></Stakeholder><Stakeholder><Name>United States House of Representatives Subcommittee on Emergency Communications, Preparedness, and Response</Name><Description/></Stakeholder><Stakeholder><Name>United States House of Representatives Committee on Transportation and Infrastructure</Name><Description/></Stakeholder><Stakeholder><Name>United States House of Representatives Subcommittee on Economic Development, Public Buildings, and Emergency Management</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS ALERTING AUTHORITY PARTNERS</Name><Description>IPAWS FEDERAL, STATE, TERRITORIAL, TRIBAL, AND LOCAL ALERTING AUTHORITY PARTNERS -- In addition to the President, alerting authorities include Federal, State, territorial, tribal, and local public safety officials who are designated within their level of government as an authority responsible for communicating emergency alerts and warnings to the American people.
Organizations representing public safety officials include:</Description></Stakeholder><Stakeholder><Name>Association of Public Safety Communications Officials (APCO)</Name><Description/></Stakeholder><Stakeholder><Name>Community Emergency Preparedness Information Network (CEPIN)</Name><Description/></Stakeholder><Stakeholder><Name>International Association of Chiefs of Police (IACP)</Name><Description/></Stakeholder><Stakeholder><Name>International Association of Emergency Managers (IAEM)</Name><Description/></Stakeholder><Stakeholder><Name>International Association of Fire Chiefs</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS Originator Practitioners’ Working Group (OPWG)</Name><Description/></Stakeholder><Stakeholder><Name>National Center for Missing and Exploited Children (NCMEC)</Name><Description/></Stakeholder><Stakeholder><Name>National Emergency Managers Association (NEMA)</Name><Description/></Stakeholder><Stakeholder><Name>National Emergency Number Association (NENA)</Name><Description/></Stakeholder><Stakeholder><Name>Regional Emergency Communications Coordination Working Group (RECCWG)</Name><Description/></Stakeholder><Stakeholder><Name>State Homeland Security and Emergency Management Offices</Name><Description/></Stakeholder><Stakeholder><Name>U.S. First Responders Association</Name><Description/></Stakeholder><Stakeholder><Name>Various Urban Area Security Initiatives (UASIs)</Name><Description/></Stakeholder><Stakeholder><Name>The Weather Channel</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS PRIVATE SECTOR INDUSTRY PARTNERS</Name><Description>Private Sector Industry partners are comprised of representatives from private sector companies with recognized equities in the alert and warning field. Because the majority of the infrastructure needed to accomplish the IPAWS mission is owned and operated by the private sector, the private sector is a key partner in the development and implementation of IPAWS.
</Description></Stakeholder><Stakeholder><Name>Emergency Interoperability Consortium </Name><Description/></Stakeholder><Stakeholder><Name>Alliance for Access to Technology</Name><Description/></Stakeholder><Stakeholder><Name>Alliance for Telecommunications Industry Solutions (ATIS)</Name><Description/></Stakeholder><Stakeholder><Name>American Cable Association</Name><Description/></Stakeholder><Stakeholder><Name>Association of Public Television Stations</Name><Description/></Stakeholder><Stakeholder><Name>Cellular Telecommunications and Internet Association --The Wireless Association (CTIA)</Name><Description/></Stakeholder><Stakeholder><Name>Commercial Mobile Service Providers (CMSP)</Name><Description>(e.g. Sprint, Verizon, AT&amp;T, T-Mobile, etc.)</Description></Stakeholder><Stakeholder><Name>Sprint </Name><Description/></Stakeholder><Stakeholder><Name>Verizon</Name><Description/></Stakeholder><Stakeholder><Name>AT&amp;T</Name><Description/></Stakeholder><Stakeholder><Name>T-Mobile</Name><Description/></Stakeholder><Stakeholder><Name>EAS-CAP Industry Group</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS Disseminator Practitioners’ Working Group (DPWG)</Name><Description/></Stakeholder><Stakeholder><Name>Latino Public Radio Consortium</Name><Description/></Stakeholder><Stakeholder><Name>National Alliance of State Broadcasters Associations (NASBA)</Name><Description/></Stakeholder><Stakeholder><Name>National Association of Broadcasters (NAB)</Name><Description/></Stakeholder><Stakeholder><Name>National Cable and Telecommunications Association</Name><Description/></Stakeholder><Stakeholder><Name>National Federation of Community Broadcasters (NFCB)</Name><Description/></Stakeholder><Stakeholder><Name>National Public Radio (NPR)</Name><Description/></Stakeholder><Stakeholder><Name>Primary Entry Point Advisory Committee (PEPAC)</Name><Description/></Stakeholder><Stakeholder><Name>Public Broadcasting Service (PBS)</Name><Description/></Stakeholder><Stakeholder><Name>Satellite Broadcast &amp; Communications Association (SBCA)</Name><Description/></Stakeholder><Stakeholder><Name>Society of Broadcast Engineers (SBE)</Name><Description/></Stakeholder><Stakeholder><Name>Society of Cable Telecommunications Engineers (SCTE)</Name><Description/></Stakeholder><Stakeholder><Name>State Chapter Broadcaster/Cable/Satellite Associations</Name><Description/></Stakeholder><Stakeholder><Name>State Emergency Communications Committees (SECC)</Name><Description/></Stakeholder><Stakeholder><Name>Telecommunications Industry Association (TIA)</Name><Description/></Stakeholder><Stakeholder><Name>Telecommunications Sector Government Coordinating Council (GCC)</Name><Description/></Stakeholder><Stakeholder><Name>IPAWS NON-PROFIT AND ADVOCACY PARTNERS</Name><Description>Executive Order 13407 specifically requires IPAWS to, “include in the public alert and warning system the capability to alert and warn all Americans, including those with disabilities and those without an understanding of the English language.”
Thus, the IPAWS PMO continuously seeks to engage a number of intra-governmental, non-profit, and advocacy organizations and their members to ensure they are kept informed of IPAWS progress, as well as solicit support for the adoption and use of IPAWS.</Description></Stakeholder><Stakeholder><Name>Intra-Governmental Organizations</Name><Description/></Stakeholder><Stakeholder><Name>The Council of State Governments (CSG)</Name><Description/></Stakeholder><Stakeholder><Name>The International City/County Management Association (ICMA)</Name><Description/></Stakeholder><Stakeholder><Name>National Academy of Public Administration (NAPA)</Name><Description/></Stakeholder><Stakeholder><Name>National Association of Counties (NACo)</Name><Description/></Stakeholder><Stakeholder><Name>National Conference of State Legislatures (NCSL)</Name><Description/></Stakeholder><Stakeholder><Name>National Congress of American Indians (NCAI)</Name><Description/></Stakeholder><Stakeholder><Name>National Governor’s Association (NGA)</Name><Description/></Stakeholder><Stakeholder><Name>National League of Cities (NLC)</Name><Description/></Stakeholder><Stakeholder><Name>Nuclear Energy Institute (NEI)</Name><Description/></Stakeholder><Stakeholder><Name>People with Disabilities</Name><Description/></Stakeholder><Stakeholder><Name>People with Access and Functional Needs</Name><Description/></Stakeholder><Stakeholder><Name>American Association of People with Disabilities/Coalition of Organizations for Accessible Technology (AAPD/COAT)</Name><Description/></Stakeholder><Stakeholder><Name>The Coalition of Organizations for Accessible Technology (AAPD/COAT)</Name><Description/></Stakeholder><Stakeholder><Name>Consortium for Citizens with Disabilities and the National Disability Rights Network</Name><Description/></Stakeholder><Stakeholder><Name>Hearing, Speech &amp; Deafness Center</Name><Description/></Stakeholder><Stakeholder><Name>Interagency Coordinating Council on Emergency Preparedness and Individuals with Disabilities</Name><Description/></Stakeholder><Stakeholder><Name>Massachusetts Statewide Independent Living Council</Name><Description/></Stakeholder><Stakeholder><Name>National Adult Protective Services Association</Name><Description/></Stakeholder><Stakeholder><Name>National Association of Councils on Developmental Disabilities</Name><Description/></Stakeholder><Stakeholder><Name>National Association of the Deaf</Name><Description/></Stakeholder><Stakeholder><Name>National Center for Accessible Media (NCAM)</Name><Description/></Stakeholder><Stakeholder><Name>National Council on Disability (NCD)</Name><Description/></Stakeholder><Stakeholder><Name>National Council on Independent Living (NCIL)</Name><Description/></Stakeholder><Stakeholder><Name>National Disability Rights Network</Name><Description/></Stakeholder><Stakeholder><Name>National Federation of the Blind</Name><Description/></Stakeholder><Stakeholder><Name>National Institute on Disability and Rehabilitation Research (NIDRR)</Name><Description/></Stakeholder><Stakeholder><Name>National Organization on Disability/Emergency Preparedness Initiative</Name><Description/></Stakeholder><Stakeholder><Name>United States Access Board</Name><Description/></Stakeholder><Stakeholder><Name>WGBH National Center for Accessible Media </Name><Description/></Stakeholder><Stakeholder><Name>World Institute on Disability</Name><Description/></Stakeholder><Stakeholder><Name>Universities</Name><Description/></Stakeholder><Stakeholder><Name>Carnegie Mellon University</Name><Description>Robotics Institute Quality of Life Technology Center</Description></Stakeholder><Stakeholder><Name>Gallaudet University</Name><Description>Technology Access Program</Description></Stakeholder><Stakeholder><Name>Georgia Institute of Technology</Name><Description>Information Technology Technical Assistance &amp; Training Center (ITTATC)</Description></Stakeholder><Stakeholder><Name>North Carolina State University</Name><Description>Center for Universal Design</Description></Stakeholder><Stakeholder><Name>Rochester Institute of Technology</Name><Description>National Technical Institute for the Deaf (NTID), Center on Access Technology</Description></Stakeholder><Stakeholder><Name>Temple University</Name><Description>College of Education Institute on Disabilities</Description></Stakeholder><Stakeholder><Name>University at Buffalo</Name><Description>Center for Inclusive Design &amp; Environmental Access (IDEA)</Description></Stakeholder><Stakeholder><Name>University of Washington</Name><Description>The National Center on Accessible Information Technology in Education (AccessIT program) </Description></Stakeholder><Stakeholder><Name>University of Wisconsin-Madison</Name><Description>The Trace Center</Description></Stakeholder><Stakeholder><Name>Older Americans</Name><Description/></Stakeholder><Stakeholder><Name>American Association of Homes and Services for the Aging (AAHSA)</Name><Description/></Stakeholder><Stakeholder><Name>National Association of Area Agencies on Aging (n4a)</Name><Description/></Stakeholder><Stakeholder><Name>National Association of States United for Aging and Disability (NASUAD)</Name><Description/></Stakeholder><Stakeholder><Name>National Council on Aging Children</Name><Description/></Stakeholder><Stakeholder><Name>National Center for Missing &amp; Exploited Children (NCMEC)</Name><Description/></Stakeholder><Stakeholder><Name>Charities</Name><Description/></Stakeholder><Stakeholder><Name>Foundations</Name><Description/></Stakeholder><Stakeholder><Name>Health Organizations</Name><Description/></Stakeholder><Stakeholder><Name>American Health Care Association</Name><Description/></Stakeholder><Stakeholder><Name>National Association of State Mental Health Program Directors (N ASMHPD)</Name><Description/></Stakeholder><Stakeholder><Name>Safe America Foundation</Name><Description/></Stakeholder><Stakeholder><Name>US Red Cross</Name><Description/></Stakeholder><Stakeholder><Name>Standards Based Organizations</Name><Description/></Stakeholder><Stakeholder><Name>IEEE Advancing Technology for Humanity</Name><Description/></Stakeholder><Stakeholder><Name>Organization for the Advancement of Structured Information Standards (OASIS) Limited English Proficiency</Name><Description/></Stakeholder><Stakeholder><Name>LEP Advocacy Interpreter Standards Committee</Name><Description/></Stakeholder><Stakeholder><Name>National Limited English Proficient (LEP) Advocacy Task Force</Name><Description/></Stakeholder></Organization><Vision><Description>Timely alert and warning to American people in the preservation of life and property using the most effective means for delivering alerts that are available at any given time.</Description><Identifier>_55cf2e04-1b89-11e4-ad5b-b49f7ff9137d</Identifier></Vision><Mission><Description>To provide integrated services and capabilities to Federal, State, territorial, tribal, and local authorities that enable them to alert and warn their respective communities via multiple communications methods.</Description><Identifier>_55cf30ca-1b89-11e4-ad5b-b49f7ff9137d</Identifier></Mission><Value><Name>Integrity</Name><Description>Faithfully reporting, Accurate system Performance information, Including negative information, to ensure we adequately prioritize corrective actions </Description></Value><Value><Name>Honesty</Name><Description>Being forthright in communications, particularly within the IPAWS Division, to ensure everyone operates with accurate information.</Description></Value><Value><Name>Credibility</Name><Description>Accurately describing strengths and shortcomings so that partners can knowledgeably cooperate with IPAWS.</Description></Value><Goal><Name>Alert &amp; Warning</Name><Description>Create, maintain, and evolve an integrated interoperable environment for alert and warning</Description><Identifier>_55cf3264-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Rapid advances in data and communications technology provide opportunities to evolve into a more robust alert and warning system that allows effective communications to the American people at all times. This goal incorporates principles necessary to: * Establish an environment that enables the integration of today’s relevant technologies with the technologies of the future * Continue a conversation between public and private sector partners from conception to testing to risk mitigation in order to expand reach and penetration * Make the system accessible and interoperable in order to serve as the primary alert dissemination tool for State, territorial, local, and tribal alerting authorities, in addition to the President of the United States * Remain effective and technologically relevant through collaboration amongst partners and constant connection with Government and industry leaders and technical leaders to continually build a stronger alert and warning system with further reach, including Americans with Disabilities and Others with Access and Functional Needs community and those who do not speak English Achieving this goal entails accomplishing the following objectives:</OtherInformation><Objective><Name>Reach &amp; Penetration</Name><Description>Develop capabilities to expand IPAWS reach and penetration</Description><Identifier>_55cf335e-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>O&amp;M</Name><Description>Transition existing developmental activities into Operations &amp; Maintenance (O&amp;M)</Description><Identifier>_55cf3502-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Effectiveness</Name><Description>Make alert and warning more effective</Description><Identifier>_55cf35fc-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>A continuous Federal commitment to an effective alert and warning infrastructure is vital. However, IPAWS will only be as effective as our partners’ awareness, understanding, adoption, and use of the capabilities. To that end, this goal requires IPAWS to:  * Execute a holistic education and outreach program to disseminate knowledge of IPAWS to the Federal, State, territorial, tribal, and local alerting authorities, Federal partners, private sector, non-profit and advocacy organizations, and the American people – how it functions, what it is for, what it provides, and how to respond   * Encourage state, territorial, tribal, and local alerting authorities to adopt IPAWS as their primary tool for issuing emergency alerts and warnings  * Engage non-federal alerting authorities so that they believe in the effectiveness of IPAWS and are willing to gain the knowledge, skills, and abilities needed to perform key tasks while creating a community of IPAWS practitioners that can source innovative ideas for improvements in process and technology   * Enable competence and hands-on familiarity with IPAWS among alerting authorities to derive maximum benefit from IPAWS as the standard for nationwide emergency alerts  * Collaborate to ensure new technologies integrate using the common standards that make rapid dissemination and interoperability possible   Achieving this goal entails accomplishing the following objectives: </OtherInformation><Objective><Name>Branding</Name><Description>Brand IPAWS as the standard for nationwide emergency alerts</Description><Identifier>_55cf36ec-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Awareness &amp; Understanding</Name><Description>Increase the awareness and understanding of IPAWS by all partners and the American people</Description><Identifier>_55cf3804-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Adoption &amp; Use</Name><Description>Increase the adoption and use of IPAWS by all partners </Description><Identifier>_55cf39a8-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Resilience</Name><Description>Strengthen the resilience of IPAWS infrastructure </Description><Identifier>_55cf3a98-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The American People need to trust that in times of emergency, IPAWS will deliver urgent alerts and warnings. In order to establish that trust, IPAWS must:   * Assess functionality and validate the speed, effectiveness, and efficiency of capabilities   * Test the adequacy of policies, plans, procedures, and protocols in a risk-free environment  * Categorize the infrastructure and assets necessary to execute the IPAWS program’s mission as critical infrastructure in the context of Homeland Security Presidential Directive (HSPD) – 7 and the National Infrastructure Protection Plan (NIPP)   * Institute procedures, in collaboration with both the public and private sectors, to enhance the resiliency of IPAWS infrastructure using the programs and tools developed as an integral part of the NIPP  Achieving this goal entails accomplishing the following objectives:</OtherInformation><Objective><Name>Testing &amp; Exercise Program</Name><Description>Develop and implement a national test and exercise program that verifies IPAWS is available when needed and operable as required</Description><Identifier>_55cf3b7e-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Mitigations</Name><Description>Work with partners to put in place the mitigations identified during national tests</Description><Identifier>_55cf3e44-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Modernization</Name><Description>Modernize existing IPAWS infrastructure to enhance resilience and sustainability</Description><Identifier>_55cf3f52-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Availability</Name><Description>Achieve IPAWS-OPEN resilience that results in 99.99% availability</Description><Identifier>_55cf4218-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Vulnerability Assessments</Name><Description>Conduct EAS and OPEN vulnerability assessments and apply or coordinate necessary mitigations</Description><Identifier>_55cf43f8-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Partnerships</Name><Description>Strengthen existing partner relationships and develop new partnerships and interests </Description><Identifier>_55cf44fc-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>3.6</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Monitoring &amp; Measurement</Name><Description>Enhance the means for monitoring and measuring success</Description><Identifier>_55cf465a-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name>Citizens</Name><Description/></Stakeholder><OtherInformation>The measure of the IPAWS program’s success lies in the actions taken by citizens once they receive an alert or warning via one of the dissemination channels. As this can be difficult to measure, it is vital that IPAWS enhance the means for monitoring and measuring the success of the program and its initiatives. To accomplish this, the IPAWS PMO must:  * Actively monitor the Key Performance Parameters (KPPs) defined in the IPAWS Operational Requirements Document (ORD), derived from E.O. 13407 and Presidential Memorandum to the Director of FEMA dated September 15, 1995 outlining the Emergency Alert System (EAS) Statement of Requirements, along with other key measures, using metrics that accurately evaluate performance and identify deficiencies  * Institute a corrective action process to address any deficiencies as they are identified   * Conduct regular reviews of the program’s performance to evaluate the overall delivery of the mission and continue to enhance the alert and warning capabilities.  Achieving this goal entails accomplishing the following objectives:</OtherInformation><Objective><Name>Performance Measurement Plan</Name><Description>Develop and implement a comprehensive plan for measuring performance across all aspects of the IPAWS Program</Description><Identifier>_55cf5118-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Corrective Action</Name><Description>Determine the process for corrective action per data shown in performance measures, when required</Description><Identifier>_55cf5119-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Technical &amp; Operational Review</Name><Description>Develop and implement a technical and operational review process</Description><Identifier>_55cf511a-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>4.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Workforce</Name><Description>Develop an IPAWS PMO workforce that is well-trained and satisfied </Description><Identifier>_55cf511b-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>To successfully deliver the requirements established under E.O. 13407, IPAWS requires a strong workforce to support the mission, vision, and goals of the program. The IPAWS PMO must take deliberate steps to fulfill the requirements, including:  * Focus on its people to ensure they are well-trained and satisfied for successful delivery of the IPAWS mission  * Enhance personnel development, consisting of understanding individual’s strengths, clearly defining and maintaining roles and responsibilities, and promoting strong teamwork amongst staff.   Achieving this goal entails accomplishing the following objectives:</OtherInformation><Objective><Name>Personnel Strengths &amp; Positions</Name><Description>Understand personnel strengths and clearly define positions</Description><Identifier>_55cf511c-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>5.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Coordination &amp; Collaboration</Name><Description>Enhance coordination and collaboration within an integrated program office  </Description><Identifier>_55cf511d-1b89-11e4-ad5b-b49f7ff9137d</Identifier><SequenceIndicator>5.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2013-10-01</StartDate><EndDate>2018-09-30</EndDate><PublicationDate>2014-08-03</PublicationDate><Source>http://www.fema.gov/media-library-data/1399922391607-309e1f4e8c48fa60a62923713abaad32/IPAWS Strategic Plan FY14-FY18 FINAL-Signed (04252014).pdf</Source></AdministrativeInformation><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></PerformancePlanOrReport>