A PSAPs Starter Guide to Creating a RFP for Next Generation 9-1-1
Resources
3 minute read
When drafting a Request for Proposal (RFP) for a Next Generation 9-1-1 system, it’s important to include a comprehensive list of requirements and specifications. A well-written RFP will clearly communicate your PSAP’s needs to potential vendors and enable them to provide accurate and detailed responses. Here are a few key things to consider when creating an NG9-1-1 RFP:
Clearly define the specific features and functionalities that your PSAP requires in a Next Generation 9-1-1 system. This may include things like Automatic Location Information (ALI) database capabilities, emergency call routing, and support for text, video, and data services.
Also, list out additional system requirements, especially for call takers, including wireless call taking, automatic number identification, print capabilities, routing status, TDD detection and communication, RTT communication, call review, and others.
As your PSAP grows, it’s essential that the NG9-1-1 system you choose can scale with it. Ensure that your RFP includes specifications for how the system can adapt to increasing numbers of calls, PSAPs, and emergency responders.
All network connections must include protection from a security attack, both internal and external. Require inclusion of a cybersecurity plan which should include details of security protocols.
Compliance with NENA i3 standards is a priority. It’s important to include specific requirements for data encryption, secure access, data backup, and recovery. In addition, require specifics on acceptance testing and failures identification.
With an increasing number of PSAPs and emergency service agencies adopting Next Generation 9-1-1, it’s crucial that the system you choose can seamlessly communicate with other systems in your area. Therefore, your RFP should include specific requirements for interoperability and integration, and how the vendor plans on executing your requirements. It should also include overflow, routing, and outage capabilities.
If a single system fails, the entire network should not fail. The vendor should describe system architecture and what happens in the event of a component failure. Each critical system module must be protected by a redundant module for tolerance to component failures. Backup and disaster plans should also be included along with emergency contact numbers for each system in the event of a failure.
The vendor should be required to provide training and technical support to your staff. Training for telecommunicators should include call taking, system administration and customization, and reporting, among others.
In addition, documentation for installation, operation, and maintenance for each component should be included, and a parts list for proper maintenance and repair.
Be sure to include details in your NG9-1-1 RFP on the proposed timeline for system implementation. Additionally, include an overview of the ongoing maintenance and support that will be required.
A detailed breakdown of the costs associated with the system, including upfront costs, recurring costs, and any additional costs associated with system upgrades or maintenance should be clearly noted. Also, remember to include costs for additional partnerships that may be necessary for compliance.
Overall, the goal of your NG9-1-1 RFP is to provide potential vendors with a clear understanding of your PSAP’s needs, and to get the necessary detailed information from them to compare vendors and make a selection. If you have questions during this process, please contact our team. We’ll help you navigate this process and answer any questions you may have.