RFI/RFP Language & NENA Standards

NENA requirements and standards for NG9-1-1 are covered in a number of documents, so reference to a single standard, such NENA-STA-010 (originally 08-003) (`i3’) long term architecture, will not necessarily accomplish the intent in an RFI or RFP for NG9-1-1.

NENA recommends that Public Safety agencies issuing RFIs or RFPs request a commitment from potential vendors to provide software, equipment and/or services that meet, are capable of meeting, and/or that will meet NENA NG9-1-1 requirements and standards now available, or as they become available in the future.

An initial RFI can be used to request information from vendors on their development status, what they have to offer, and if they are following NENA recommendations, requirements, and standards. Examples would include provision of Policy Rules functionality as described in NENA Standards and Info documents, and EIDD capability as described in APCO / NENA 2.105.1-2017. Requiring conformance to this EIDD standard is especially important in NG9-1-1 RFPs because the EIDD is the format for exchanging call and incident data in NG9-1-1 PSAPs, and across the ESInet to other agencies.

If the RFP issuer wishes to speak to time frames, it is also recommended that no less than a six month time frame be specified for complying with NENA standards after formal availability, to allow vendors development and testing time to accomplish compliance.