Replacement Notification System

de a web-based system in a Federal Risk and Authorization Program (FedRAMP) approved (see below for levels) environment that provides the ability to access the system via a secure, encrypted internet connection using a US government sanctioned encryption method. from any approved computer, tablet or smart phone in order to initiate alerts and notifications via any mode supported by the system. The proposed system shall be fully hosted by the vendor in a FedRAMP environment certified at Moderate or above and shall only require an internet connected computer to send messages and operate the system. FedRAMP High certification may be given additional credit in solicitation evaluation provided that a risk-benefit evaluation of any features that may not operate in a high configuration determines those features are not required. The proposer�s system shall have a robust hardware and a geographically dispersed components across the United States of America with failover mechanisms in place to ensure the ability to operate under all conditions and provide security and redundancy eliminating any single point of failure. The proposal shall document how this system provides this capability and ensures continued operation in the event of computer equipment failures, loss of utility power, natural disaster or intentionally caused human physical or virtual attack. The proposer�s system will be required to comply with all Federal information technology operating and security requirements in place at the time the solicitation is awarded. In order to accept the system, the vendor will have to support ESS staff to complete the ATF Certification and Accreditations (C&As) process. This is aligned with the NIST SP800-64 �Security Consideration in the Information System Development Lifecycle�, October 2008; it follows the five lifecycle phases of Initiation, Development and Acquisition, Implementation, Operations and Maintenance and Disposition. This five-step lifecycle is closely aligned with ATF Handbook 7200.2B ATF System Life Cycle (SLC). This C&A process will determine if the system can be used to interact with ATF computers and process ATF information. The proposed system must be capable of authenticating users to the vendor hosted system using government provided Personal Identity Verification (PIV) credentials. Proposed system must be technically capable of allowing access to at least 75 users simultaneously and allowing the activation of all types of alerts and notifications (including GIS mapping alerts), database maintenance, system maintenance, report queries, or whatever duties their assigned security level allows without degrading system performance. The proposed system must recognize administrators and authorized users and enforce their privileges based on system security settings in a customer configurable matrix: The proposed system must have a customer editable matrix of common administrator, supervisor and users access tights so that the customer can create the privileges for at least five user-defined levels of access. The proposed system must provide the ability to partition sections of the database to departments within ATF to share the notification components of the system but operate within their own segregated database environment to ensure integrity and confidentiality of their data. The proposed system must have levels of segregation to accommodate a multi-department structure with multiple tiers within each department. A small number of administrators would have global access to manage the entire system, but most privileged users would be limited to their department and data structure. The proposer shall describe how the conduct preventative maintenance and emergency maintenance and how that is managed to ensure the system has 100% availability. 2. Dailing Services Must be capable of sending out multi-modal messages, at a minimum, via: Landline (record voice or text to speech voice) Cell phone (recorded voice or text to speech voice) SMS Text Message (using pre-approved short or long codes provided by the vendor that are immediately available for use by ATF) MMS Text Message (using pre-approved short or long codes provided by the vendor that are immediately available for use by ATF) E-mail VoIP Social media 2. The proposer must describe how they operate their outgoing message infrastructure across all services. If a third-party service is used, they must provide the service level agreement(s) (SLAs) with any third-party vendors to describe how the third-party service operates and continuous operating ability is provided. 3. The proposed system should have the ability to detect local telephone company infrastructure limitations and adjust the volume of calls as needed to increase efficiency. 4. The proposer must describe how the proposer identifies requirements for, and executes, the throttling of calls, Include any provisions for on-going evaluation of throttling requirements beyond the initial deployment phase. 5. The proposer�s system should have ability to throttle calls based upon user designated priorities for notifications. 6. Proposer should describe in their proposal the speed of message delivery by providing an explanation of the capabilities of their system across the different modes of communications. 7. Proposer should propose various service level options at least one of which includes unlimited phone call-out minutes at one set fee regardless of the number of calls made or minutes used during the call, SMS text messages, and emails. 8. The proposed system shall allow customization of displayed caller ID number and readout for the outgoing calls based upon department within the notification system that is initiating the notification. 9.The proposed system must include a feature set that allows messages to be designated sensitive and only be able to be retrieved by the recipient after the enter PIN code assigned to their personal profile in the notification system. 10.The system must include a multi-step process to authenticate users before launching public messages that can be toggled on or off based on an individual users profile or in the permissions matrix. Further: The system should include �fail-safe� features to prevent �unintended test� messages from being launched to the public. The system must meet or exceed �public safety grade� security and reliability standards. The system must be fully Section 508 compliant and ADA compliant. 3. Calling Database Management 1. The government will require at least two distinct databases be operated by the system. The proposer must describe in their proposal, including any cost associated with this requirement, the means for loading contact information into its system (automated upload/download capability accomplished with a simple comma delimited file, or other approved method, via direct entry into proposer�s system). This data transfer must occur in a secure, encrypted fashion in accordance with Department of Justice and ATF information security requirements. The data updated daily will be two separate databases: 2. ATF Employee data from the Microsoft Identity Management System. The data attributes may include the following based on the FedRAMP certification level of the data center: First Name Last Name User ID (Employee ID) Login Name (Employee ID) Employee Type (Employee or Non-Employee) Divi