ARFQ HHR25 3 Mass Notification Q&A.xlsx
XLSX spreadsheet 10 KB Posted
- Attached to
- Employee Mass Notification System
- Solicitation number
- ARFQ-0506-HHR2500000003-2
- Issued by
- Kanawha County, West Virginia
About this file
This document is a Questions and Answers (Q&A) spreadsheet for a Mass Notification System Request for Quotation (ARFQ HHR25) involving the Office of Shared Administration. The procurement is for an internal agency notification system with a mobile application-based solution for field staff safety and communication purposes. This is a first-time implementation of a mass notification system, with specific requirements including employee data synchronization, panic button functionality for field staff, and integration with the agency's CGI ERP system. The agency is seeking a mobile app solution for iOS/Android platforms and explicitly stated that a web-based interface would not be acceptable.
The Q&A document reveals that the notification system is intended for internal agency use and does not require FEMA IPAWS certification. The agency will provide employee synchronization data via an Excel file extract, and their security contractor will provide 24/7 monitoring. Key technical requirements include automatic employee data synchronization, mobile panic button functionality for field staff experiencing safety issues, and the ability to send SMS and voice call notifications. The exact volume of daily, weekly, or yearly notifications is currently unknown, as this represents a first-time implementation. The agency has emphasized the need for a comprehensive mobile application solution that can support their internal communication and safety monitoring needs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ARFQ HHR25 3 Mass Notification RFQ.docx | DOCX document | |
| FederalFundsContractClauseAddendum.pdf | ||
| WVCloud-SaaSProcurementAddendum.pdf | ||
| ARFQ HHR25 3 Addendum 1.docx | DOCX document | |
| Property Addresses.xlsx - Google Sheets.pdf | ||
| ARFQ HHR25 3 Mass Notification Cost Sheet.xlsx | XLSX spreadsheet | |
| ARFQ HHR25 03 TCA.pdf | ||
| Final_ARFQ_0506_HHR2500000003_2_WV_ARFQ_FORM.PDF | ||
| ARFQ HHR25 3 WV-43.pdf | ||
| Final_ARFQ_0506_HHR2500000003_1_WV_ARFQ_FORM.PDF |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| 1. What is the average annual number of messages that are currently sent out? | This is a first time implementation. |
| 2. Is the outbound mass notification messaging expected to stay the same, increase, or decrease? | This is a first time implementation. |
| 3. Section 3.1.1.11 states the system must have panic button functionality. How many physical locations (office buildings and other buildings) will be using these panic buttons? | There is no requirement for a physical panic button to be located in any facility. The attached PDF file provides a list of facilities occupied by our staff. |
| 4. What is the plan for the monitoring of these panic buttons? Is this something expected of the awarded vendor? Do you have your own monitoring center that will monitor panic alerts? Will your local PSAP/911 Operations Center monitor these alerts? All of the above? | The Office of Shared Administration will provide 24/7 monitoring through our security contractor. |
| 5. Section 3.1.2.3 states that the system must provide the automatic synchronization of employee data, including updates to contact information. What is the name of the system do you use that the chosen vendor will be synchronization against? | The Office of shared Administration utilizes an ERP system designed by CGI. We will provide the synchronization file via a .xls file extract. |
| 6. For requirement, “3.1.1.11 - System must have remote panic button functionality”, can you please clarify whether the intended panic button should be mobile app-based, personnel-issued hardware, physically located within facilities, or a combination of these options? Can you please expand on how you envision the panic button functionality being implemented? | There is no requirement for a physical panic button to be located in any facility. The intended use is for field staff making home visits to have a mobile panic button if they are experiencing as safety issue. |
| 7. For requirement, “3.1.2.3 - System must provide automatic synchronization of employee data…”, can you please clarify what system(s) we would need to initially integrate with? Should updates from the mass notification system write back to the source? | The Office of shared Administration utilizes an ERP system designed by CGI. We will provide the synchronization file via a .xls file extract. |
| 8. What is the expected volume of daily/weekly/and yearly notifications (SMS and voice calls)? | Unkown, this is a first time implementation. |
| 9. Do you have a notification system that you are currently using? If so, which one? | This is a first time implementation. |
| 10. How many SMS text and Voice Call notifications did you send out in total last year? | This is a first time implementation. |
| 11. Our software can be used on an IOS/Android web browser. Can the agency confirm if a responsive mobile web interface that supports full system functionality is acceptable in place of a mobile app for iOS/Android? | We are seeking an application based solution. A web based interface will not be acceptable. |
| 12. Is this notification system for public alerts or internal agency notifications? | Internal agency notifications. |
| 13. Is the agency FEMA IPAWS certified? | No. |
File details come from the government source that posted it. Updated .