SOURCES SOUGHT
99 -- AF Enterprise Emergency Mass Notification System
- Notice Date
- 11/16/2021 11:51:42 AM
- Notice Type
- Sources Sought
- NAICS
- 517311
— Wired Telecommunications Carriers
- Contracting Office
- FA8726 AFLCMC HNK C3IN HANSCOM AFB MA 01731-2100 USA
- ZIP Code
- 01731-2100
- Solicitation Number
- EMNS
- Response Due
- 12/15/2021 1:00:00 PM
- Archive Date
- 06/01/2022
- Point of Contact
- Steve Pekunece, Phone: N/A, Terri Rutkiewicz, Phone: N/A
- E-Mail Address
-
steven.pekunece@us.af.mil, terri.rutkiewicz@us.af.mil
(steven.pekunece@us.af.mil, terri.rutkiewicz@us.af.mil)
- Description
- Request for Information (RFI) For Air Force Life Cycle Management Center (AFLCMC) C3I Infrastructure Division (HNI) Emergency Mass Notification Systems (EMNS) 04 Nov 2021 Contents 1.������ Introduction. 3 2.������ Disclaimers. 3 3.������ RFI Purpose and Target 4 4.������ Project Purpose. 4 5.������ Project Details. 4 5.1������� EMNS Support Requirements. 4 5.2������� System Requirements (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) 5 5.3������� Additional System Requirements (not included in AF10-206) 5 5.4������� Notification Requirements (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) 5 5.5������� Personally Identifiable Information (PII) (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) 6 5.6������� Performance Requirements. 6 5.7������� User Interface Requirements. 6 5.8������� Key Characteristics. 7 5.9������� Assumptions/Limitations. 7 5.9.1������� Estimated Number of EMNS Users. 8 5.9.2������� Project Duration. 8 5.9.3������� Technology Maturity. 8 5.9.4������� System Life Cycle. 8 6.������ Initial Questions. 8 7.������ Requested Information. 8 8.������ Data Submission Requirements. 9 8.1������� Written Responses. 9 EMERGENCY MASS NOTIFICATION SYSTEM (EMNS) Introduction The United States Air Force (USAF) Life Cycle Management Center (AFLCMC) Command, Control, Communications, and Intelligence (C3I) and Networks Directorate (HN), C3I Infrastructure Division (HNI) Program Management Office (PMO) is issuing this RFI as part of its effort to sustain the enterprise-wide Air Force (AF) Emergency Mass Notification System (EMNS). Disclaimers This is a Request for Information (RFI), as defined in Federal Acquisition Regulation (FAR) 15.201(e). �Any information submitted by respondents to this request is strictly voluntary.� This is not a request for proposal (RFP), request for quotation (RFQ), or invitation for bid (IFB); nor does its issuance obligate or restrict the U.S. Government to issue an RFP, RFQ, or IFB in the future.� The U.S. Government does not intend to award a contract on the basis of responses from this RFI. Not responding to this RFI does not preclude participation in any future RFP, RFQ, or IFB, if any is issued.� Were the Government to issue an RFP, RFQ, or IFB for the acquisition of an enterprise EMNS solution, any such solicitation would include additional requirements for procurement of the required hosting environment, system installation, training, Technical Order generation, and on-site Interim Contractor Support.� Respondents need not address any of these elements in their submission. Respondents are advised the U.S. Government will not pay for any information provided, the use of such information, the preparation of such information, travel expenses, nor any administrative costs incurred in response to this RFI.� All costs associated with responding to this RFI will be solely at the interested parties� expense. Information received from this RFI will be used for planning and market research purposes.� As such, any response submitted to this RFI constitutes consent for that submission to be reviewed by military personnel, Government civilians, Department of Defense (DoD) contractors and MITRE and/or Software Engineering Institute (SEI) system engineers. MITRE Corporation and SEI are Federally Funded Research and Development Corporations (FFRDCs) and, as such, fulfill an unbiased, non-profit role for the Air Force. The responses may be forwarded to other Government entities in consideration for applicability to other programs. Any proprietary information submitted should be identified as such and will be properly protected from disclosure.� All DoD contractor and FFRDC personnel reviewing RFI responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information.� The U.S. Government shall not be liable for damages related to proprietary information that is not properly identified.� Proprietary information will be safeguarded in accordance with the applicable U.S. Government regulations. Respondents are advised that the Government is under no obligation to provide feedback with respect to any information submitted. Issuance of this RFI does not obligate or restrict the U.S. Government to an eventual acquisition approach. RFI Purpose and Target The purpose of this RFI is to establish a technical understanding of the current state of the industry; market availability; and technical characteristics, cost, and functionality of available Information Technology (IT) tools, applications, or products capable of satisfying the technical, functional, and operational requirements, assumptions, and limitations. This RFI will also focus on programmatic and other non-technical issues (e.g. integration and installation work, training, technical order (TO) development) to be included in the development of the acquisition strategy. Therefore, the PMO is interested in responses from original equipment manufacturers (OEMs) and responses from IT service or integration companies. Project Purpose The purpose of this project is to sustain an AF cloud-based Enterprise EMNS solution, in accordance with Air Force Instruction (AFI) 10-206, �Operational Reporting�. �The Air Force requires a single EMNS to alert and warn 100% of assigned forces quickly and effectively of an emergent event. �The EMNS needs to increase situational awareness for Airmen and their families, regardless of their physical location, to enable protective measures when tragic events or emergencies occur. �This project will address the gaps in the notification process to personnel and their families when on and off duty, as well as on and off the installation.� This project will provide a single AF Enterprise solution to support lifesaving and mission protective measures within the AF. �This system shall have the capability of delivering reliable and secure emergency threat notifications to all personnel at all AF locations on a 24/7 basis. �It must have the capability of disseminating mass notifications via the following means: Networking Alerting System (NAS): email, desktop alert, SMS (text messaging) Telephone Alerting System (TAS): dialing work, home, and mobile telephones Giant Voice: interface directly with installation outdoor speaker system Smart Device Application: with GPS locator (e.g. IOS/Google Play Store) Project Details EMNS Support Requirements Software assurance/technical support, upgrade support, training, and public address/giant voice integration support at all AF locations on a 24/7 basis for both primary and alternate locations. Engineering and Program Support. Any software and hardware required to run the EMNS. System Requirements (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) Network Alerting System (NAS): which consists of e-mail, text messaging, and desktop pop-up notifications to USAF personnel. Telephone Alerting System (TAS): which consists of the capability of dialing work, home, mobile numbers, and Short Message Service (SMS) text. Giant Voice: which consists of the capability to integrate with the EMNS at all Main Operating Bases (MOBs). Smart Device Applications: which consists of the capability for notification and global positioning to alert targeted members/installations/sites within 20 miles of an event, and 100 miles if events escalate. � Cloud Solution: which consists of the capability to decrease the Information Technology (IT) footprint and provide significant savings, while improving end-users� services and cybersecurity. �Cloud solution must meet DoD requirements defined for Certification for Cloud/Commercial hosting. Hierarchical Infrastructure Notification Capability: which consists of connecting installations, MAJCOMs, FOAs, DRUs, and Headquarters Air Force (HAF) to provide rapid interoperable notification of an event. � Minimal Training: which consists of minimal training to begin immediate use of the system (i.e. web-based tutorials for personnel as needed). Dependent Access: which consists of allowing AF personnel the option to allow dependents to receive notifications. EMNS: which consists of providing both alert notifications, as well as confirmation of receipts of notification. Additional System Requirements (not included in AF10-206) Must integrate with existing facilities which have UFC 4-021-01 compliant MNS and facilities without MNS. Must link with off-base EM command and control centers and other DoD emergency control centers. Notification Requirements (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) Within two (2) minutes or less after initiation, the EMNS must reach a target audience of 90% or more of on and off-installation personnel with specific protective action recommendations (mass warning) and 100% of assigned EM resources, including first responders, first receivers, and emergency responders (notification) (T-1). Within one (1) hour after initiation, EMNS should reach 100% of on and off-installation personnel. Alert notifications (i.e. Duress, Field Reporting, etc.) originating from personnel at off-installation facilities should strive to be initiated within two (2) minutes of incident verification, after contact is made to local emergency response forces by dialing 911 (or equivalent emergency center). Capability of seamlessly falling over to a backup system if the primary system should fail. Must notify other DoD command centers within the specified region. Personally Identifiable Information (PII) (AFI10-206, Operational Reporting, Chapter 8 Emergency Mass Notification System) PII data in the EMNS database will be protected as required by all Federal laws and regulations. Global Positioning System (GPS) data will only be accessed by the system to transmit notifications to personnel in the impacted area for the purpose of providing an emergency alert. All generated records and reports will be protected as Controlled Unclassified Information (CUI) IAW DoD 5200.48 and will be shredded/deleted IAW the records disposition schedule. GPS coordinates will only be collected from personal devices when the user voluntarily activates the location/GPS feature. All GPS coordinates will be automatically overwritten immediately after the notification. � Performance Requirements Ensure that alert notifications be issued to anyone connected to the AFNet, as well as manually loaded �.com� e-mail addresses, to total an estimated one (1) million users (military, civilians, and support contractors). Must allow single-click activation of pre-defined emergency scenario alerts. Include provisions for secure communication, authentication, and encryption using DoD and industry-standard PKI-encryption technologies and Common Access Card (CAC) authentication for Government-owned devices. Must support standard network ports and protocols. Must comply with Unified Capabilities Requirements (UCR) 2013 SECTION 3.5 General Mass Notification Warning System, (http://disa.mil/ucco-files/UCR-2013-Change1-Main.pdf). User Interface Requirements Must be manageable by authorized administrative account holders in the Command Post (i.e. Scenario Managers) who can implement the various scenarios built, or create scenarios as needed, to support a particular situation. Data must be accessible on a need-to-know basis through the administrative accounts. Administrative account holders and scenario managers must have the capability to add, edit, delete, and import or export database information for AF personnel. Administrators must be able to generate metric data to support AF leadership personnel accountability metrics to measure successful notification contact. Scenarios must be available command-wide, managed by MAJCOMs, wing or unit driven, and managed by appropriate wing or unit. All deployed PCs are required to communicate through Hypertext Transfer Protocol Secure (HTTPS). Telephone alerting must be provided by a fully integrated TAS capability in a centralized net-centric architecture for use throughout the Air Force by MOB that are run by the Air Force. Response results from telephone voice, SMS text messaging, and email alerts must be fully integrated into existing EMNS reporting capabilities. All TAS capabilities must be 100% interoperable with the NAS. The TAS communication capability must enable dialing to mobile or landline phones, with an audio notification generated automatically using text-to-speech technology. TAS must include a closed loop communication allowing receipt of response from users. EMNS software must include an integrated capability that simultaneously dials user telephone numbers via leased lines through commercial communication centers. Text, email, and smart applications must be the primary method during off-duty hours. Members should be notified of what data is being collected, how the data will be used, how long the AF will maintain the records, how individuals may opt-out of the data collection features, and what costs a user may incur from using the EMNS application. Desktop software must operate with the AF Standard Desktop Configuration. All communication must be capable of Transport Layer Security (TLS) version 1.3, as well as Secure Socket Layer (SSL) version 3.0. Key Characteristics The Key Performance Parameters (KPPs): Timeliness. The time it takes for a target audience to receive a notification. Objective: 90% or more of on/off-installation personnel with protective action recommendations (mass warning) and 100% of first responders and emergency responders within two (2) minutes. �Within one (1) hour, the EMNS must attempt to reach 100% of on/off-installation personnel with protective action recommendations (mass warning). Hierarchy Infrastructure Integration. Consists of connecting installations, MAJCOMs, FOAs, DRUs, and Headquarters Air Force (HAF) to provide rapid and consistent interoperable notification of an event. Objective: An AF enterprise EMNS that is interoperable across all AF installations and that leverages existing capability to execute mass notifications from a single notification input. Connecting Users. Consists of connecting on and off-duty, as well as on and off-installation, AF personnel, dependents, and local first responders, regardless of their location, to AF EMNS capabilities. Threshold: All on and off-duty, as well as on and off-installation, AF personnel able to receive EMNS notifications, regardless of their location, using an AF enterprise EMNS that leverages existing capability. Objective: All on and off-duty, as well as on and off-installation, AF personnel and dependents able to receive EMNS notifications, regardless of their location, using an AF enterprise EMNS that leverages existing capability. Assumptions/Limitations The assumptions and limitations listed in this section are to be considered in designing the technical solution to fill the enterprise remote access requirement. Estimated Number of EMNS Users The PMO estimates the total number of users requiring EMNS capability (military, civilians, and support contractors) to be one (1) million. Project Duration The PMO is targeting system sustainment for one (1) year, plus four (4) option years. Technology Maturity This is not a developmental effort.� The intent is to integrate commercial off-the-shelf (COTS) products into the Air Force Network (AFNet).� No or limited software development is expected; tough extensive configuration is expected.� In terms of Technology Readiness Levels (TRLs) as defined in the DoD Technology Readiness Assessment Guidance revision posted 13 May 2011, the PMO is focused on products and technology that have reached TRL 9 and is not considering anything below TRL 8/9. System Life Cycle The lifecycle of the remote access system is defined by EOL and EOS dates of its components.� As these components become obsolete, the program office will evaluate whether a form, fit, function replacement, or a system redesign presents the best course of action. Please provide the following information: Company Name Headquarters Location Years in Business DUNS # Cage Code # Primary POC Information Current Size Standard under NAICS 517311, Wired Telecommunications Carriers\ �Based on the NAICS code 517311 and a size standard of 1500 employees, please identify all of the following that are applicable, Small Business, HubZone Small Business, 8(a) participation, Veteran-Owned Small Business, Service-Disabled Veteran-Owned Small Business, Small Disadvantaged Business, or Women-Owned Small Business. Do you have a current DCAA Approved Accounting System? List all Multiple Award Contracts that your company is a contract holder with that cover a scope similar to this effort. (Optional) Industry�s opinion on the use of the NAICS Code in question or another NAICS Code is welcomed RELEVANT EXPERIENCE.� Up to three examples showing relevant experience performing efforts of similar value, size, and scope within the last five (5) years including contract number, indication of whether your firm acted as a prime or subcontractor, contract value, Government/Agency point of contact information, and a brief description of how the contract relates to the technical services described herein. Requested Information Based on the above information, the PMO is requesting industry feedback by providing responses to any or all of the following: Identify and describe currently available technical solutions for the EMNS that meets all requirements set forth in this document. �If there is more than one product that can meet the requirements, identify the most viable solution, given the information in this RFI for the AF, and explain why. Identify how you intend on meeting applicable UCR 2013 Section 3.5 requirements. Provide a notional schedule for this project continuation and sustainment. What tasks are dependent on other tasks? Identify the likely cost drivers and/or potential cost savings opportunities. What licensing structures are available?� How does license structure affect total lifecycle cost? Provide any test reports, white papers, past performance citations, or other literature that would help the Government meet the purpose of this RFI. Address methods of registration/management. Are there different groups and/or subgroups (i.e. active duty civilians, dependents, or emergency personnel such as fire, police, flight ops, or medical)? Do you possess the demonstrated capability to disseminate information to a large user base via e-mail, desktop clients, phone messages (work, home, mobile), SMS, and an outdoor Voice Notification system? Can you deploy an Impact Level 5 solution that complies with DISA Secure Technical Implementation Guidelines (STIGs)? Can you support a 24/7/365 notification system? Can you provide a solution that can notify >= 90% of on and off-base personnel and 100% of Emergency Management resources within ten (10) minutes of initiation? Can you target recipients based on GPS location data, IP Address, Computer Name, Rule-based criteria, Org Structures pulled from LDAP or AD, or dynamic groups created by on-the-fly queries of the user directory? An Ombudsman has been appointed to consider and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. Before consulting the Ombudsman concerned parties should first address their concerns, issues, disagreements, and/or recommendation to the Contracting Officer for resolution.� The clause at AFFARS 5352.201-9101 �Ombudsman (Oct 2019)� is applicable to this action. The AFLCMC Ombudsman is Lt Col Brian Miller (Primary), AFMC/AQ-AZ, 1790 10th St. Bldg. 572, Wright Patterson AFB, OH 45433- 7630, Telephone#: (937) 255-5512, Email: brian.miller.15@us.af.mil. Data Submission Requirements The PMO is requesting written responses to this RFI. Written Responses Written responses to this RFI are due no later than 15 Dec 2021 at 4:00 PM Eastern Standard Time.� Submit responses via email to Steve Pekunece at steven.pekunece@us.af.mil and Terri Rutkiewicz, terri.rutkiewicz@us.af.mil. Title e-mail responses in the subject line of the e-mail as follows:� Response to EMNS RFI. Any questions regarding this RFI must be submitted via email to Steve Pekunece at steven.pekunece@us.af.mil and Terri Rutkiewicz, terri.rutkiewicz@us.af.mil. �All questions and their answers will be posted for all interested parties to see. Provide your submission in a Microsoft Word document.� Page sizes will be 8.5� x 11.0� with 1� margins all around. Text will be Times New Roman with font no smaller than 12 pt.� Respondents should identify their company name, address, telephone number, and point of contact (name, phone, e-mail) on the title page.� The company name should appear clearly on every page of the submittal and proprietary information must be clearly marked.� To the maximum extent possible, please provide non-proprietary information. �There is a 10-page limit for the information requested under Section 7. No classified information shall be submitted.
- Web Link
-
SAM.gov Permalink
(https://beta.sam.gov/opp/9c25673b65474261800ecbff7fc1e89b/view)
- Record
- SN06178624-F 20211118/211116230127 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |