EMWN RFI (Final) 2026 04 22.docx

Request for Information (RFI)

1. Purpose This Sources Sought/Request for Information (RFI) is a request to industry to provide information on a comprehensive Emergency Mass Warning and Notification solution that encompasses the services and tools required to provide Department of War (DoW) with a single, unified capability. This RFI is issued solely for information and planning purposes and for market research. It does not constitute a solicitation and shall not be construed as an offer, commitment, or obligation on the part of the DoW or Department of the Army (DA), or the United States Government. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

No reimbursement will be made for any costs incurred in responding to this RFI. Responses will not be acknowledged or returned, nor will respondents be notified of the outcome of the Army 's review of the information received. Additionally, the Army does not intend to hold discussions concerning this RFI with any interested parties. However, the Army reserves the right to contact vendors if additional information is required.

The U.S. Government acknowledges its obligations under Federal Acquisition Regulations and 18 U.S.C. § 1905 to protect confidential information provided to the Government. Pursuant to statute, the U.S. Government is willing to accept any trade secrets or proprietary restrictions placed upon qualifying data in response to this survey and to protect such information from unauthorized disclosure, subject to the following:

Information received shall be marked with the data and time of receipt and transmitted to the designated officials. Information received in response to this RFI will be safeguarded adequately from unauthorized disclosure. FAR Subpart. 15.207 pertains.

2. Background The Department of the Army is the DoW Executive Agent for Emergency Mass Warning and Notification (EMWN).

Currently, DoW organizations employ multiple disparate mass warning and notification products that do not efficiently communicate with each other or do not provide a capability that can clearly and transparently share emergency or mass warning information.

The Secretary of War has directed the implementation of a single, unified system capable of delivering timely, reliable alerts to all DoW personnel worldwide of local, regional, national or international events or situations. Such a system must remain compliant with applicable DoW policies, federal statutes, and regulations.

3. Objective Through this RFI, the Army seeks to:

· Provide industry an overview of the Army’s current baseline EMWN capabilities and performance requirements;

· Enable industry to better understand DoW’s operational needs;

· Solicit industry feedback on efficient, cost effective, and innovative approaches; and

· Obtain rough-order-of-magnitude (ROM) cost and schedule data for commercial off-the-shelf (COTS) solutions that could meet or exceed the described requirements.

4. General Instructions The Army welcomes responses from all responsible sources, including small and other than small businesses to submit a response to this RFI.

A complete response shall not exceed 15 pages (excluding a cover letter, the cost estimate worksheet in Enclosure 1 and the statement of work in Enclosure 2.

Responses should demonstrate capability, not merely affirm the respondent's capability (e.g., The response must go beyond statements like, "XYZ company has extensive experience in operating and maintaining mass warning and notification cloud infrastructure and help desk services.").

Note that a respondent's failure to provide a technical description and a completed cost estimate worksheet will be interpreted to mean that it does not understand the DoW’s needs. Additionally, it will reflect the vendor's lack of understanding of how to provide mass warning and notification tools and services to a large organization.

5. Requested Information and Response Format Responses shall include the following:

a. A technical description of the respondent’s proposed EMWN solution and how it would satisfy the requirements and performance parameters described in Enclosure 2.

b. A fully completed cost estimate worksheet (Enclosure 1) providing ROM pricing for all required functions.

i. − For every line item, enter either an estimated cost or “$0” if no cost is anticipated.

ii. − Include footnotes or a separate assumptions page explaining the basis of estimate, what is/is not included, labor categories, licensing model, recurring vs. non-recurring costs, etc.

c. Explanation of the methodology and assumptions used to develop the ROM cost estimate.

d. Provide a maximum 15-page description of their suggested solution and estimated costs including an explanation of how their estimate was developed, what is and is not included in their services, labor, and software/environment response.

e. Provide a migration schedule of how the time required to migrate the DoW organizations to the vendor suggested solution. This portion of the response will not count toward the overall page count.

Cover page, table of contents page, and suggestions to Statement of Work gaps pages will not count to the 15-page description limit.

On the FACE PAGE of your response, please provide the following:

a) Organization name

b) DUNS number

c) Organization's website

d) Contact Name

e) Contact Telephone

f) Contact E-mail address

g) Size designation and type (i.e., Small Business, etc.)

h) Your organization's FY25 current and gross revenue

i) Your organization's current GSA MAS Schedule number if currently on a schedule Elaborate previous experience on performing similar types of tasks specified in Enclosure 2 – Statement of Work. The elaboration on each experience shall include:

a) Evidence of performing similar types of tasks (including agency and contract numbers).

b) Brief introduction of the project’s objective and scope.

c) Brief description of the methodology and equipment used to perform similar types of tasks.

Do any gaps exist in the Governments Draft Statements of Work? If so, what are they? What changes, additions, updates, and clarifications would you suggest?

6. EWMN Program Data for Cost Estimating Purposes The following data shall be used by responders when developing their rough-order-of -magnitude cost estimates:

a) Primary Subscribers within DoW number 4,000,000 . Primary Subscribers are defined as DoW employees (MIL, CIV) and DoW contractors. Dependents are not included in this definition. Dependents are Secondary Subscribers.

b) All per-seat or per-subscriber costs shall be calculated by dividing the total proposed cost by the DMDC provided number.

c) Contractor-furnished Help Desk operation support shall provide 24 hours per day, 7 days per week, 365 days per year and staffed to immediately receive and process any calls for assistance.

d) Contractor-furnished EMWN operations staff shall perform the functions and capabilities outlined in Enclosure 2 shall be estimated on a 5 day/week, 8-hour/day work schedule.

e) The number of warnings or notifications processed by the EMWN system vary and not every warning or notification generates a voice call or SMS text message. For planning and estimating purposes respondents can use the information in Tables 1 and 2 below to assist in estimating the volume of telephone phone minutes and SMS message units per month.

Table 1 – Estimated Telephone Minutes used during an average monthly period

Table 2 - Estimated SMS Message Units used during an average monthly period

f) The telephone minutes and SMS message units identified in Table 1 and 2 above represent warning/notification messages sent to primary and secondary subscribers. For cost-estimating purposes, knowledge of specific populations by geographic area is not relevant. However, knowing monthly averages allows a vendor to develop a more accurate scale of cost needed to keep DoW personnel informed of events and assist the DoW in costs to be budgeted.

g) The proposed solution may only track a users location in the mobile application. The mobile application will then make the determination if a warning or notification is relevant for the subscriber to be informed. The solutions core application hosted external to the mobile applications may not collect or retain any location information on where a subscriber is or has been.

7. Cost Estimate Definitions (for Enclosure 1 worksheet) Respondents shall outline estimated costs as follows:

a) Labor cost is defined as the human resources that the contractor will require to operate, administer, and maintain the EMWN capability (i.e., the server(s), cloud environment, help desk, any support contracts, etc.).

b) Licensing cost is the cost that is incurred to support all software managing the notification of Subscribers (e.g., commercial mass warning software licenses, mobile application licenses, other subscription fees in support of the overall system, application programming interfaces, etc.)

c) Cloud cost is defined as the DoW Impact Level 5 support environment required to host the licensed software (e.g., cloud processing fees, on-line storage fees, back-up/off-line storage fees, cloud OS license fees, cloud support software or applications). Depending on the vendor's technical solution the cloud may also host the interface software that communicates with voice distribution capability, in turn sending notifications to Subscribers or the SMS text gateway software. The government typically finds voice calling and SMS texting to be supported by third parties. However, this is not required.

d) Telephone Voice Cost is defined as the cost of the minutes spent delivering notification messages to designated subscribers from the EMWN software.

e) SMS Texting is defined as the cost of the used message units used in delivering notification messages to designated subscribers from the EMWN software.

8. Submission Deadline The RFI responses shall be submitted via email only to:

Mr. Linwood Matthews at linwood.l.matthews.civ@army.mil no later than 4:00 PM Eastern Time on 29 MAY 2026.

Subject line shall read: “EMWN RFI Response – [Company Name]”.

Acceptable files: PDF for the technical volume, plus Excel version of the completed Enclosure 1 cost worksheet. Total technical volume (excluding cover letter and Enclosure 1) shall not exceed 15 pages.

Late submissions will not be considered.

9. Questions Vendors may submit questions via email to:

Mr. Kerry Owens at Kerry.f.owens.civ@army.mil.. The Government reserves the right to decide if and how questions will be answered at its sole discretion. Questions must be submitted by 4:00 PM Eastern Time on 8 MAY 2028 Answers to questions, if provided, will be posted at SAM.GOV. It is strongly recommended that respondents not wait for or expect questions to be answered and should submit their best response based on the information already provided.

Attachments Enclosure 1 – Rough order of Magnitude Cost Estimate Worksheet Enclosure 2 – Statement of Work

Enclosure 1 Rough order of Magnitude Cost Estimate Worksheet

Enclosure 2 Statement of Work

Enclosure 2 Page 2-1

Statement of Work Emergency Mass Warning and Notification (EMWN) Capability

1. Introduction

1.1 This Statement of Work (SOW) defines the requirements for a third-party vendor or integrator to provide, operate, sustain, and manage a commercial off-the-shelf (COTS) Emergency Mass Warning and Notification (EMWN) system in a FedRAMP-approved[footnoteRef:1] Impact Level 5 (IL5) cloud environment for the Department of War (DoW). [1: Federal Risk & Authorization Management Program, administered by GSO PMO. ]

1.2 The solution shall utilize an industry-standard mass warning and notification tool. Development of custom software is not required.

1.3 The system shall support four million (4M) primary subscribers, each primary subscriber capable of sponsoring a minimum of four (4) and a maximum of twelve (12) secondary subscribers.

1.4 Only primary subscribers are billable under any cost-per-subscriber pricing model.

2. Contractor Responsibilities

2.1 The vendor will ensure compliance with all tasks and deliverables identified in this RFI. The vendor would be responsible for staffing, training, supervision, security clearances, and meeting all performance standards. The vendor shall coordinate with the Government to ensure successful mission execution.

3. Government Responsibilities

3.1 The Government will provide access to government-furnished information systems, and facilities as required.

3.2 The Government will designate a Contracting Officer Representative (COR) to oversee contract execution and provide guidance, coordination, and approval of deliverables.

4. Period of Performance

4.1 The period of performance for estimation purposes of this RFI will be a 5-year period starting in FY28 and proceed through FY32. The provider will estimate maintaining continuity of operations throughout the entire 5-year period, including transition-in and transition-out activities.

5. Scope

5.1 The EMWN program will include the enterprise-wide COTS (Commercial Off the Shelf) mass warning and notification system hosted in a FedRAMP approved commercial cloud environment at DoW Impact Level 5 with contractor prepared Authority to Operate (ATO) package. The contractor will provide the application, platform, as well as all necessary patches, and maintenance for operability and the associated labor skills to operate and maintain the overall EMWN system and perform all the necessary cyber tasks (E-mass, etc) to ensure a secure operation of the system. The system will be tested by an independent testing specialist prior to connection.

5.2 The vendor shall furnish all personnel, equipment, cloud environment, tools, materials, supervision, and other items and services necessary to perform the functions outlined in this RFI. The provider shall ensure that the EMWN system is maintained, secured, continuously available, and in compliance with applicable Federal, Department of War (DoW), and Army standards.

5.3 System Overview

5.3.1 The DoW requires a single Emergency Mass Notification System to alert and warn 100% of assigned forces quickly and effectively of an emerging event. The Emergency Mass Notification System is used for notification of an installation’s forces and assets, with primary resources used during: Increased Force Protection Conditions, Information Protection Implementation, Recall Situations, Force Generation, Crisis Action Team Recall/Relocation, Personnel Accountability and Emergency Mass Notification (i.e., Active Shooters, Chemical, Biological, Radiological and Nuclear [CBRN] incidents, Natural disasters, etc.).

5.4 System Requirements Document Overview

5.4.1 The DoW EMWN will utilize a solution that provides emergency notifications to all DoW military and civilian, and contractor personnel. The EMWN system will also allow for family members and local DoW mission partners, as needed, to receive warnings. The DoW’s baseline requirements for EMWN are the following components:

a) a Network Alerting System (NAS) for email/text messaging and desktop pop-up notifications to DoW personnel, at work and/or at other locations

b) a telephone alerting systems (TAS) capable of dialing work, home, mobile numbers, and Short Message Service (SMS) text on EMWN-supported commercial phone lines.

6 Services

6.1 Performance Standards

6.1.1 The provider shall meet the following minimum standards:

a) 99.95% system availability

b) Preventive maintenance per OEM and DoW standards

c) Compliance with DISA STIGs and Army directives[footnoteRef:2] [2: DISA Security Technical Implementation Guides. ]

d) Accurate reporting in MSRs and IPT updates

e) Compliance with FISMA regulations and standards

f) DoDD 8140 DoD Cyberspace workforce

g) DoDI 6055.17 DoD Emergency Management (EM) Program

h) If an RFP is pursued, Vendor must provide DoW access to repair materials (hardware and software) that will be used in the vendors estimated solution

6.2 Program Management

6.2.1 Plan, organize, and execute all tasks per this RFI.

6.2.2 Manage contractor personnel to ensure adequate staffing and experience.

6.2.3 [RESERVED]

6.2.4 Establish the appropriate support contracts to perform all support and notification.

6.2.5 [RESERVED]

6.2.6 {RESERVED]

6.2.7 [RESERVED]

6.2.8 [RESERVED]

6.2.9 [RESERVED]

6.2.10 Plan, organize, coordinate, integrate, and execute all tasks and requirements included in this PWS during the entire contract Period of Performance (PoP).

6.2.11 Manage personnel to execute all contract requirements, ensuring adequate quantities, types, and experience levels are maintained.

6.2.12 Ensure personnel complete required government in-processing and training, and provide timely notification of staffing changes/gaps and mitigation strategies to the PMO at weekly meetings.

6.3 Performance Monitoring

6.3.1 Maintain oversight of system performance and recommend improvements.

6.3.2 Maintain continuous oversight of system performance characteristics and infrastructure and recommend adjustments to the Army standards.

6.4 Incident Management

6.4.1 Investigate, diagnose, and resolve incidents with a comprehensive audit trail.

6.4.2 Record all incidents in a ticketing system.

6.4.3 Document lessons learned and escalations.

6.4.4 Provide weekly updates via IPT meetings and MSRs.

6.5 Escalation Procedures

6.5.1 Brief all open problems to Service Managers, Directors of Operations, and government stakeholders.

6.6 Problem Management

6.6.1 Manage recurring or unresolved incidents.

6.6.2 Conduct trend and root cause analysis.

6.6.3 Record problems with description and actions taken.

6.6.4 Perform problem management for reoccurring incidents or any unresolved incident across the EMWN infrastructure and virtual environment. The Contractor shall conduct trend and root cause analysis.

6.6.5 Document in the ticketing system, via an incident ticket, immediately whenever a problem is recorded, with a brief description and actions being taken until the incident is closed successfully.

6.7 Change Management

6.7.1 Track and manage all requests for change.

6.7.2 Establish a change submission process.

6.7.3 Evaluate all requested changes developing a cost and schedule proposal for government approval.

6.8 Submission of Change Requests

6.8.1 Identify changes to the baseline via approved change requests.

6.9 Patching and Upgrading

6.9.1 Track and apply patches, firmware updates, and version upgrades.

6.9.2 Submit change requests with impact analysis, cost, time, and interruptions.

6.9.3 Track vendor releases of patches, firmware updates, and version upgrades for all system components, including monitoring CERT, DISA, OEM sites, and IAVAs, ensuring timely upgrades to avoid end-of-support products.

6.9.4 Identify required patches/upgrades, submit change requests (including impact analysis, cost, time, and potential interruptions).

6.10 Training

6.10.1 Provide in-person and computer-based training across all DoW locations globally on a regular basis as needed.

6.10.2 Provide training weekly and support off-cycle urgent training needs at times that allow for training during core hours for all global time zones via TEAMS.

6.11 Configuration Management

6.11.1 Create/update/maintain all system diagrams, documentation, training materials.

6.11.2 Maintain accurate equipment inventory.

6.11.3 Maintain change control and configuration management records of all hardware, software, and cloud configurations.

6.11.4 Coordinate changes with Army sponsor, and other entities as requested.

6.11.5 Ensure compliance with all standards regulations, federal law and cyber requirements.

6.11.6 Perform maintaining change control, configuration management, and associated documentation.

6.11.7 Coordinating configuration and changes impacting cybersecurity with Army assigned point of contract.

6.11.8 Coordinating all actions as required with Army assigned point of contract as related to Risk Management Framework (RMF), Cyber, Network Operations or other controlling organizations as appropriate to ensure zero impact to other supporting capabilities or infrastructure in accordance with government guidance/standards/regulations.

6.11.9 Develop and support the ongoing requirements for government Authority To Operate (ATO) processes.

6.11.10 Government must be provided administrator access to all hardware, software server, and cloud capabilities.

6.12 Deliverables

6.12.1 Monthly Status Reports (MSRs).

6.12.2 Weekly IPT meeting updates.

6.12.3 System audit logs, performance reports, and configuration documentation.

6.12.4 Incident and problem management records.

6.12.5 Training materials and attendance records.

7 Acceptance Criteria

7.1 Deliverables will be reviewed and accepted by the Government COR. Acceptance will be based on timeliness, accuracy, compliance with DoW and Army standards, and fulfillment of performance requirements. Failure to meet standards may result in rejection of deliverables and corrective action requirements.

8 Operations

8.1 System Administration

8.1.1 Maintain system Army Cyber and RMF authorizations and provide updates.

8.1.2 [RESERVED]

8.1.3 Perform weekly database backups and maintaining all records IAW NARA.

8.1.4 [RESERVED]

8.1.5 Provide mission application support (updates, releases).

8.1.6 [RESERVED]

8.1.7 Manage, schedule, and test system backups and recovery procedures.

8.1.8 Monitor performance of databases and applications.

8.1.9 [RESERVED]

8.1.10 Manage service requests, troubleshooting, and remediation of network failures.

8.1.11 Provide pertinent authorization and monitoring data.

8.1.12 [RESERVED]

8.1.13 Ensure information regarding EMWN in the prevailing RMF authorization for the system(s) are valid, or provide updated information for the EMWN entry.

8.1.14 Ensure all patches and firmware updates are tested and applied.

8.1.15 [RESERVED]

8.1.16 Ensure the system operates in an active-active configuration with the ability to failover to the standby system to ensure 99.95 percent availability monthly.

8.1.17 Ensure 99.95 percent system availability if primary servers failover to secondary.

8.1.18 Provide support for EMWN software (mission applications) including, but not limited to updates and releases, patches, and Time Compliant Network Orders (TCNOs).

8.1.19 Maintain and examine system/audit logs for failures, failure prediction, and cybersecurity accountability requirements.

8.1.20 [RESERVED]

8.1.21 Perform database recovery, loading new databases, reinitializing and reloading databases upon installation of new software version releases.

8.1.22 Perform database and application performance monitoring: database storage allocation; database and server distribution monitoring; maintaining database configuration.

8.1.23 Perform all tasks to ensure configuration in compliance with the latest version of the DISA STIGs or SRG.

8.1.24 Accept and complete Service Requests (SR)/trouble tickets for EMWN system.

8.1.25 Coordinate problem resolution affecting EMWN system with network services providers as required.

8.1.26 Troubleshoot and remediate network failures for IP based networks affecting EMWN.

8.1.27 Provide pertinent data, when requested, supporting the authorization and continuous monitoring of EMWN.

8.1.28 Perform remote access, account administration, IT device configuration and installation, troubleshooting, monitoring, security, and infrastructure installation.

8.1.29 Manage, support, and maintain physical and virtual IT infrastructure.

8.2 Operating Platform

8.2.1 Perform preventive and remedial maintenance per OEM standards.

8.2.2 Coordinate authorized service interruptions.

8.2.3 Complete material inspections, shipping, and receiving of assets.

8.2.4 Deliver remedial support with documented rational for corrective actions.

8.3 Operating Mode

8.3.1 System must operate 24 hours a day 7 days a week and be 99.95% available with a comprehensive contingency plan to ensure maximum availability.

8.3.2 System may only be accessed via the DoW NIPRnet by administrators, users, and subscribers.

8.3.3 System must have the capability of a mobile application on subscribers personal or government cell phones.

8.3.4 System must be able to meet notification standards identified in DoDI 6055.17.

8.3.5 System must be compliant with DoW ICAM capabilities.

8.3.6 Vendor solution must support DoW zero trust capabilities.

8.3.7 System must use government provided e-mail server.

8.3.8 [RESERVED]

8.3.9 Vendor must identify how their solution will provide SMS notification and operate and maintain that solution throughout the period of performance.

8.3.10 Current system provides subscriber agent that is installed on subscriber workstations.

8.3.11 Vendor must provide similar workstation agent capability.

8.4 User Responsibilities

8.4.1 Users are defined as the government personnel that are authorized to initiate warnings or notifications to be distributed to DoW personnel.

8.5 Subscriber Responsibilities

8.5.1 Subscribers are defined as personnel that have accounts and will receive warnings or notifications of significant public safety events.

8.6 Primary population

8.6.1 Primary population is defined as the DoW military, government civilian, or contractor personnel preforming actively performing DoW business on a day-to-day basis.

8.6.2 Additionally, local civilian agents or companies performing regular work or contact in support of DoW activities are authorized as subscribers if sponsored by an existing primary population member.

8.7 Secondary population

8.7.1 Secondary population is defined as dependent personnel that are directly associated with a primary population person.

8.8 Service Desk

8.8.1 Provide a US-based 24/7/365 service desk.

8.8.2 [RESERVED]

8.8.3 [RESERVED]

8.8.4 Report operational status, trending metrics, and downtime events in MSRs.

8.8.5 Provide comprehensive systems management, reporting, operations, and maintenance, including troubleshooting, patching, backups, and status monitoring.

8.8.6 Assist users with application migration to the hosted environment, provide consultation on user needs, acknowledge incidents/requests within 30 minutes, and offer guidance on host infrastructure, operating systems, databases, cybersecurity (RMF), security, and other application technical parameters.

8.8.7 Provide operational status, trending metrics, monitoring metrics, and incident tickets related to Downtime Events in the Monthly Status Report (MSR).

9 Tool

9.1 Tool Capacity

9.1.1 The system must be capable of demonstrating a compliance of all DoDI 6055.17 warning/notification requirements.

9.2 Tool Capabilities

9.2.1 Functional Aspects

9.2.1.1 The Enterprise Mass Warning and Notification System shall provide a mass warning and notification capability for all DoW personnel (military, civilian, contractor, embedded allies, family members, and others as required). (CONUS & OCONUS).

9.2.1.2 The EMWN shall provide dissemination of alert notifications to target authorized recipients by means of multiple notification devices simultaneously (workstation agent, e-mail, phone call, SMS text, mobile app, and or other external modalities (e.g. giant voice or audio/visual interfaces).

9.2.1.3 All recipients shall be able to register in the single system with a single login regardless of affiliation, multiple affiliations or attribute. The EMWN will only be accessible to the NIPR network and via the associated mobile application.

9.2.1.4 The EMWN system shall allow CAC holders to sponsor/register up to 12 dependents. These dependents shall have their own contact and attribute information.

9.2.1.5 The EMWN system shall treat these dependents as separate entities for accountability and will contact the dependents as necessary based on the emergency.

9.2.1.6 The system will allow for notifications to be sent to any primary or secondary population set as selected by the message originator based on the nature of the emergency as selected by the message originator.

9.2.1.7 The EMWN system shall provide the recipient the ability to select an alert response option from any of the targeted devices.

9.2.1.8 The EMWN system shall be capable of reattempting to alert those users not successfully reached until acknowledged by one of the multiple recipient devices alerted.

9.2.1.9 The EMWN system shall be able to configure the number of re-attempts to alert telephone numbers not successfully reached.

9.2.1.10 The EMWN system shall provide desktop alerting via installed agent that will maintain connectivity with the EMWN system.

9.2.1.11 The desktop alerting must be capable of both audio and visual alerting. No user action shall be required by the user to receive desktop notifications (the subscriber must be logged on to receive desktop notifications) if they are already registered with the EMWN.

9.2.1.12 The desktop notification must be persistent until acknowledged by the recipient If a recipient logs into a computer capable of desktop alerts after an alert has been sent, and while the alert is still active, the desktop alert shall be delivered to that device.

9.2.1.13 Desktop alerting must be able to operate normally in a Virtualized Desktop Environment in which only the Roaming App Data folder and user documents folder is synchronized.

9.2.1.14 [RESERVED]

9.2.1.15 The system shall support desktop client check-in as often as every 3 minutes across the enterprise.

9.2.1.16 The desktop alerting will authenticate with PKI and authenticate during every server check-in and validate the certificate.

9.2.1.17 The EMWN system shall provide telephone alerts, as provided by subscribers, including landline and cellular.

9.2.1.18 The EMWN system shall provide voice alerting capability to registered telephone numbers. Telephone numbers will be standard commercial access numbers from all countries.

9.2.1.19 The EMWN system shall leave voice messages if the call is not answered.

9.2.1.20 The EMWN system shall provide a method for the user to respond to the voice-mail as their acknowledgement response.

9.2.1.21 The EMWN system shall record which phone numbers were successfully delivered, when/if the phone was answered and if a response successfully delivered, or if the message went to voice-mail or failed to reach the end device.

9.2.1.22 The EMWN system shall provide mobile client alerts.

9.2.1.23 The EMWN will provide a mobile app for the following operating systems: iOS and Android.

9.2.1.24 The applications shall provide audio and visual warning notifications to the user of the mobile device.

9.2.1.25 Mobile application notifications shall be able to notify subscribers based solely on geographic targeting.

9.2.1.26 The mobile application will not transmit any GPS information outside of the phone.

9.2.1.27 The mobile application shall be able to notify subscribers based on attributes.

9.2.1.28 The EMWN system shall be capable of sending SMS texts, directly or via a third party provider.

9.2.1.29 The EMWN will record which SMS texts failed to be delivered.

9.2.1.30 The EMWN will record which SMS texts were successfully delivered.

9.2.1.31 The EMWN system shall provide e-mail alerts.

9.2.1.32 All e-mails must be sent using the DoW's e-mail servers.

9.2.1.33 The EMWN system shall be capable of sending e-mail to DoW e-mail addresses.

9.2.1.34 The EMWN system shall be capable of sending e-mails to e-mail addresses outside the DoW.

9.2.1.35 The EMWN system shall be capable of sending digitally signed e-mails and this setting shall be configurable for both work and home e-mail addresses independently.

9.2.1.36 The EMWN system shall be capable of sending unsigned e-mails and this setting shall be configurable for both work and home e-mail addresses independently.

9.2.1.37 The EMWN system shall have a dashboard or report capability to display the live or historical situation of any active or historical notification(s) recorded in the system and maintained IAW NARA.

· The EMWN dashboard shall be capable of displaying notifications that impact personnel inside of Users' notifications authority but originated from another DoW entity outside of their authority.

· EMWN shall be capable of displaying an enterprise-wide or global view for all notifications, and further have the ability to provide custom filters to view and manage subordinate organizations

9.2.1.38 The EMWN system shall disseminate alert notifications to target authorized subscribers.

9.2.1.39 EMWN users authorized to perform group management tasks shall be able to:

a) create distribution list(s) assign individual subscribers to new distribution list(s)

b) assign individual subscribers to existing distribution list(s)

c) remove subscribers from existing distribution list(s)

d) delete distribution list(s)

9.2.1.40 [RESERVED]

9.2.1.41 The EMWN users who are authorized to perform distribution list management tasks shall be able to define Static subscribers groups composed of a selected list of subscribers (“roster”) .

9.2.1.42 EMWN users authorized to perform distribution list management tasks shall be able to define Dynamic subscriber groups composed of lists based on data queries on assigned attributes of subscribers.

9.2.1.43 EMWN users having the requisite authorization shall be able to assign delivery devices to be used when alerting a subscriber or a group.

9.2.1.44 EMWN users having the requisite authorization shall be able to create and initiate non-templated alerts. The user designates the target recipients and/or groups, the preferred delivery devices, the contents of the alert message, and the timing of the alert.

9.2.1.45 EMWN user having the requisite authorization shall be able to target recipients for alert notification based on: organization structure (all or part), distribution list physical location, on a GIS map by a radius defined by the operator or an irregular shape imported via KML location names (i.e., Installation name, city name, etc.) roles/responsibilities custom attributes phone number device type.

9.2.1.46 The EMWN users having the requisite authorization shall be able to create a new group by copying from an existing group and editing the newly created group without changing the existing group and share premade groups with others.

9.2.1.47 The EMWN users shall be able to clone static lists for any given alert, operators having the requisite authorization shall be able to retrieve and display the count of targeted subscribers and view the coverage of existing contact details per the selected notification devices against the count of targeted subscribers prior to activating the alert. When creating an alert, the EMWN system shall display the number of people that will be targeted by each selected method of notification.

9.2.1.48 Access to EMWN functions, assets, and resources are governed by the permissions assigned to the user or subscriber.

9.2.1.49 EMWN users can be assigned management permissions for a specific recipient attribute, specific hierarchy and geographic area .

9.2.1.50 EMWN user having the requisite authorization shall be able to generate scenario templates. These scenarios include: content of the alert subscriber response option(s) target specific subscriber selectable devices duration of the notification.

9.2.1.51 EMWN users having the requisite authorization shall be able to trigger templated alert notifications.

9.2.1.52 EMWN users having the requisite authorization shall be able to specify the start time and date of the alert to be sent (including test, exercise, and real world alerts) immediately at a specific date/time .

9.2.1.53 EMWN users having the requisite authorization shall be able to track the delivery of each alert status by individual user or individual user device .

9.2.1.54 EMWN user having the requisite authorization shall be able to track subscriber response status of notifications that were sent via phone, e-mail, sms and desktop client.

9.2.1.55 For any given alert, operators having the requisite authorization shall be able to retrieve and display the:

a) count of targeted subscribers (except for mobile app)

b) actual number of subscribers (except for mobile app)

c) the number of subscribers who responded with each response option

d) the names of subscribers who responded with each response option

e) Outcome of each attempt to contact targeted subscribers

f) time stamps for each contact attempt

9.2.1.56 The EMWN users having the requisite authorization shall be able to initiate an alert from a web browser.

9.2.1.57 The System Administrator shall be able to add custom attributes to the custom attribute field in a drop down list and be defined as public or private.

9.2.1.58 The EMWN system shall provide pre-defined reports that highlight performance and timeliness of the delivery systems and recipient responses for each alert.

9.2.1.59 The EMWN system shall provide pre-defined reports that breakdown all subscribers responses.

9.2.1.60 The EMWN system shall provide the option for custom report generation. The capability must give operators the ability to generate reports on specific criteria either on registered users/ subscribers, notifications or reporting via custom queries.

9.2.1.61 The EMWN system shall be able to centrally track, in real-time, all alerting activities for each recipient, including sending, receiving, and responding to alerts, and be able to generate reports based on tracked information.

9.2.1.62 The EMWN system shall be able to cancel an ongoing alert and stop all notification methods in less than 1 minute after the alert was cancelled.

9.2.1.63 The EMWN system shall have a Web-based interface for users or System Administrators to publish and track alerts, monitor notifications in real time, and perform administrative tasks.

9.2.1.64 The Web-based interface shall be role and permission based, and only those capabilities allowed by the operator’s authorization shall be available.

9.2.1.65 The EMWN system shall support the ability for subscribers to update their personal information to ensure up-to-date contact information for purposes of emergency alert notification. Any information that is imported/synced from other database must not be editable by subscribers.

9.2.1.66 [RESERVED]

9.2.1.67 [RESERVED]

9.2.1.68 The EMWN system shall interoperability with internal and external sources System must have configurable API to transmit CAP messages that allows for full CAP field configuration, have a free to use API , a written Interface Design Document and accept any existing CAP already inherent in the system.

9.2.1.69 The system shall be compliant with the CAP most recent version.

9.2.1.70 The system should be able to write or post to various endpoints that support REST and SOAP endpoint interfaces.

9.2.1.71 The EMWN connectivity with external modalities such as Giant Voice/ Indoor Voice systems shall not replace the existing Giant Voice/ Indoor Voice activation method, but shall have the ability to communicate with Indoor Voice systems through an EMWN API to include CAP for unified notification scenarios. This connectivity will not require the use of a server or server software locally installed at the installation.

9.2.1.72 The EMWN system shall be capable of leveraging Enterprise data to populate and maintain a comprehensive database of subscribers including all contact information necessary for the EMWN to send alert notifications to the recipients. (Subscriber receipt information shall be retained for 2 years).

9.2.1.73 [RESERVED]

9.2.1.74 [RESERVED]

9.2.1.75 [RESERVED]

9.2.1.76 [RESERVED]

9.2.1.77 The EMWN system shall manage response of alert messages to ensure that once a subscriber acknowledges, no further alerts will be sent to the subscriber. Once acknowledged, the alert not yet sent to other recipient devices shall be cancelled. The EMWN would also cancel any re-attempts to other subscriber devices that received the alert, but not yet answered.

9.2.1.78 The EMWN system shall meet DoW policies

9.2.1.79 The EMWN system shall comply with all information assurance policies

9.2.1.80 The EMWN system shall meet all applicable IAVAs, OPORDS, CTOs and FRAGOs for IA. Meet Privacy Act of 1974, 5 U.S.C. and 8510.01 RMF covering but not limited to; Physical access control, logical access control, System and Information Integrity, Personnel Security, and Incident Response.

9.2.1.81 The following regulations 10 U.S.C. 2224 - Defense Information Assurance Program and USCODE-2011 title 44, Chap 35- Subchapter; 3544. Vendor estimate must be flexible to account for the DoW changing requirements of the information assurance program that may develop in the future.

9.2.1.82 The EMWN will be hosted in a vendor provided and accredited IL5 FEDRAMP cloud facility that is fully integrated with the NIPRnet.

9.2.1.83 The EMWN will have failover capability to provide active-active support either multiple hosting locations or cloud based configurations. The current government system fully supports active-active with geographic separation of greater than 100 miles for resiliency.

9.2.1.84 The EMWN system shall meet all applicable requirements for integration with DoW Secure Host Baseline.

9.2.1.85 All vulnerabilities must be mitigated within the CYBERCOM regulated timelines

9.2.1.86 The EMWN system shall meet all applicable Security Technical Implementation Guidelines (STIGs) and/or Security Requirements Guides (SRGs) Digitally signed software installation files Upon software delivery, hash values of software installation files Authentication

9.2.1.87 The EMWN system shall ensure that any credential used for identity authentication shall be issued by an approved DoW identity credential provider or a DoW-approved Federal or industry partner identity credential provider

9.2.1.88 The EMWN system shall uniquely identify and authenticate before establishing a connection.

9.2.1.89 The EMWN system shall uniquely identify and authenticate source and destination points be for information transfer.

9.2.1.90 The EMWN system shall employ the principle of least privilege, allowing only authorized accesses for subscribers (or processes acting on behalf of subscribers) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions.

9.2.1.91 The EMWN system shall be Section 508 compliant unless an exemption is obtained

9.2.2 Content

9.2.2.1 Subscribers shall be able to self register their information and include the following information:

a) EDIPI

b) Name

c) Rank

d) Command

e) UIC (Up to 100 per recipient and with date range)

f) Installation (Up to 100 per recipient and with date range)

g) Building (Based off ingestion of GIS maps info)

h) Personal device phone number (Optional)

9.2.2.2 The EMWN system must be able to import data from DMDC with :

a) Custom Attribute (Up to 100 per recipient) and be accessible as a drop down menu

b) Home Address (Up to 100 per recipient)

c) Work Address (Up to 100 per recipient)

d) Personal Phone (Up to 100 per recipient)

e) Work E-mail (Up to 100 per recipient)

f) Personal E-mail (Up to 100 per recipient)

g) Other Address (Up to 100 per recipient)

h) Work Phone (Up to 100 per recipient)

i) Command/Unit affiliation

9.2.3 Registration

9.2.3.1 The system must support self registration capability.

9.2.3.2 The system must also support the ability to bulk update subscriber information for later activation

9.3 Warning/Notification External Modality Interfaces

9.3.1 The EMWN tools does not include the system hardware or software, Giant Voice or Inside Voice but does include the interfaces to those systems.

9.3.2 Voice Notification

9.3.2.1 The system must have the ability to notify subscribers via a phone call and verbally pass or provide the initiators notification or warning

9.3.3 Automatic Text to Speech

9.3.3.1 The system must ensure that calls or use of external modalities such as Giant Voice or inside voice have the ability to process a submitted incident text description and provide speech

9.3.4 SMS Text Notification

9.3.4.1 The system must support an automated interface or API to one or more SMS gateways to distribute SMS text notifications

9.3.4.2 The system must use the DoW NIPRnet to establish contact to any SMS Gateway capability that will perform the SMS functions of delivering notifications or warnings

9.3.5 Workstation Agent Notification

9.3.5.1 This capability is a separate module that must be able to be provided to the DoW master workstation image maintainers

9.3.5.2 The vendor must coordinate all modifications made to the workstation agent thru the DoW maintainers

9.3.5.3 The vendor help desk must accept and provide a solution to all callers regarding problems with the workstation agent

10 Training

10.1 Develop, provide regular training for all roles established in the tool.

10.2 The vendor must be capable of providing training in multiple configurations

10.3 The vendor must support subscriber on-site training if requested

10.4 All on-site training travel will be separately reimbursed by subscriber agencies and not be included in the RFI estimate

10.5 The vendor on-site training personnel will be accounted for in this RFI estimate image1.emf

Microsoft_Excel_Worksheet.xlsx Sheet1

Vendor Estimate

90 day period 90 day period

Non-recuring Costs

Transition In FY28 FY29 FY30 FY31 FY32 Transition Out Total Cost

Labor $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Licencising $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Cloud Costs $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Telephone Voice Expense $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

SMS Texting Expense $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

$ - 0 Grand Total

Recurring Costs

Transition In FY28 FY29 FY30 FY31 FY32 Transition Out Total Cost

Labor $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Licencising $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Cloud Costs $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

Telephone Voice Expense $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

SMS Texting Expense $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0

$ - 0 Grand Total