Attachment 1 IPAWS Synopsis - Industry Day Webinar.pdf
Date Originally Posted
May 14, 2021, 11:53 a.m.
Page 1 of 4 FEMA – National Continuity Programs (NCP) SYNOPSIS: Integrated Public Alert and Warning System (IPAWS) Management Support Services Contract - Industry Day WebinarThe Department of Homeland Security, Federal Emergency Management Agency, NCP-IPAWS Division will be conducting an Industry Day Webinar for Management Support Services Contract. The IPAWS requirement is hereby synopsized in accordance with FAR 5.207 Preparation and Transmittal of Synopsis: Description: IPAWS Industry Day Webinar – Please see announcement flyer.Registration Deadline: Friday, June 4, 2021, 5:00 p.m., Eastern StandardTime (EST).The IPAWS Program Office will be accepting a one-page business capability statement for Market Research purposes sent to: FEMA-INDUSTRY-REGISTRATION@FEMA.DHS.GOVSubject title: IPAWS Business Capability – Your Company NameDeadline: Friday, June 4, 2021, 5:00 p.m., Eastern Standard Time (EST)This event will speak to the IPAWS pre-solicitation requirements and allow general questions regarding the program’s mission. Please send questions to: FEMA-INDUSTRY-REGISTRATION@FEMA.DHS.GOV Subject Title: IPAWS Questions Deadline: Friday, June 4, 2021, 5:00 p.m., Eastern Standard Time (EST)This contract has a small business plan obligation which will be discussed during the IPAWS Industry Day.RFI posted April 16, 2021 and closing May 14, 2021 (Notice ID FEMA-RFI-2022IPAWS)Background: The Integrated Public Alert and Warning System (IPAWS) is a national system that supports local alerting through integrated systems, services, and capabilities to Federal, state, territorial, tribal, and local alerting authorities (AA) and emergency managers, enabling them to provide emergency alerts to people in their respective communities. In close collaboration with their critical stakeholders, IPAWS provides Page 2 of 4 an integrated architecture and enables a concept of operations to alert the nation to a wide variety of incidents (e.g., disasters, AMBER alerts). IPAWS coordinates with over 1,500 public alerting authorities across 50 states, and 3 U.S territories, including law enforcement, military agencies, emergency managers, and Native American tribes. IPAWS is made up of 77 Primary Entry Point (PEP) Radio Stations across the U.S. and its territories. Current State: IPAWS currently has contracts in place that will soon expire. VISION: Acquire centralized and flexible support that serves as a single point of contact for IPAWS leadership to manage all facets of program management support which includes but is not limited to information collection, communications, and support for program activities that guide strategic and tactical approaches developed to meet IPAWS mission requirements. Scope: IPAWS has a requirement for Management Support Services to include but not be limited to: A.Program/Project Management SupportB.Stakeholder OutreachC.Policy Development and AnalysisD.Engineering SupportDescription of Requirements A.Program/Project Management Support Services The IPAWS program managementoffice (PMO) is responsible for complete lifecycle management of the IPAWS Program.The PMO requires support to the IPAWS staff in all aspects of acquisition and systemslifecycle program management to include planning, budgeting, organizing, executing,controlling, and reporting necessary to execute the mission of the IPAWS whilemaintaining program documentation in accordance and compliance with applicableFEMA, DHS, and OMB program acquisition and systems lifecycle requirements, policiesand Federal rules and regulations.The awardee/s must set repeatable procedures and tools to initiate, assign, perform,monitor, and control work, guided by a Project Management Framework (PMF) andtailored to meet IPAWS specific needs. The PMF should be based on the ProjectManagement Body of Knowledge (PMBOK) best practices from the Project ManagementPage 3 of 4 Institute (See SOO for additional details). B.Stakeholder Outreach IPAWS Stakeholder Outreach/Engagement is critical to theprogram to provide information and gather feedback from a wide range of stakeholdersincluding the public. There are numerous activities required to meet engagementobjectives, beginning with support for IPAWS Stakeholder Engagement Branch (SeeSOO for additional details).C.Policy Development and Analysis Congress, the Federal Communications Commission(FCC), DHS, and FEMA are all sources for IPAWS mandates. Additionally,technological advances and evolving threats or emergencies also drive IPAWS policychanges. IPAWS requires support to maintain its flexibility and establish policies thatcontinue to direct Program activities focused on meeting the mission (See SOO foradditional details).D.Engineering Support Central to IPAWS mission is management of the IPAWS nationalsystems infrastructure as described in the SOO. FEMA designs and builds systems tomeet requirements elicited from stakeholders, from regulatory changes, from statute, andbased on emerging technical and performance demands. Engineering support providesthe management, tracking, and technical oversight necessary to ensure the systems meetthe program and stakeholder objectives.FEMA ensures IPAWS is operating properly through several technical activities,primarily relying on User Acceptance Testing (UAT). UAT ensures that the IPAWS-OPEN web services perform at an acceptable level for the intended interoperablesystems. IPAWS Program Management Office (PMO) representatives conduct testingactivities and document results independent of IPAWS-OPEN development teams. Testswere carried out from the perspective of external interoperating system developersperforming interoperable system acceptance testing of the IPAWS-OPEN capabilities.End-to-end testing from origination source through IPAWS and out to all disseminationsources, including through CMSP Gateways to Gateway controlled end-user devices, isbeyond the scope of the UAT. IPAWS has no control or visibility into carrier managednetworks and processes. UAT covers only what IPAWS can control. Table 4 of the SOOdescribes example deliverables that should be considered for supporting TechnicalDirection and Oversight Support.The Engineering Support task is integral to the requirements elicitation process to ensurestakeholder needs and program goals are properly captured, categorized, and are testable.This activity requires the knowledge, skills, and abilities embodied in the systemsengineering and software engineering disciplines.In order for FEMA to position IPAWS to adapt to and utilize emerging technologies andto adapt to changes to current technologies, the Engineering Support task must seek out,monitor, and at times influence the direction of standards and technologies by followingdevelopments in bodies such as the Alliance for Telecommunications Industry SolutionsPage 4 of 4 (ATIS), the International Telecommunication Union (ITU), the Organization for the Advancement of Structured Information Standards (OASIS), and the Consumer Technology Association (CTA). Disclaimer: The information contained within this Synopsis is notional and subject to change at the discretion of the Contracting Officer or the IPAWS Program Office.