911 QA - second set_.pdf
PDF 137 KB Posted
- Solicitation number
- RFP 202591102
- Issued by
- Blaine County, Nebraska
About this file
This document is Solicitation Addendum 5 for the State of Nebraska's Solicitation Number 202591102 for a Next Generation (NG) 911 Data Analytics Reporting System, with an opening date of September 2, 2025, and an addendum effective date of August 21, 2025. The addendum provides a comprehensive set of questions and answers related to the solicitation, addressing technical specifications and requirements for the proposed 911 data analytics system. Key details include statewide call volume data for 2023 (1,012,225 calls) and 2024 (954,264 calls), and confirmation that users will be able to designate specific Key Performance Indicators (KPIs) and create custom/ad hoc reports.
The addendum clarifies several technical requirements for the system, including a 24-month online, queryable retention window for i3 LogEvents, compliance with NENA-STA-010.3 logging service standards, and confirmation that i3 functional elements will expose the NENA Logging Service over the Emergency Services IP network (ESInet). No external systems beyond the ESInet/NGCS provider and their customer management portal will consume the log events. The state expects strict conformance to logging service and LogEvent schemas from all vendors and functional elements, with no expectation of normalization for non-conformant implementations.
View the file
Other files
Show all 38
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
SPB Form 26 Last Revised 4-17-2025
SOLICITATION ADDENDUM 5
QUESTIONS AND ANSWERS – Second Set
SOLICITATION NUMBER: 202591102
NG 911 Data Analytics Reporting System Opening Date: September 2, 2025
Addendum Effective Date: August 21, 2025
Questions and Answers
Following are the questions submitted and answers provided for the above-mentioned solicitation. The questions and answers are to be considered as part of the solicitation. It is the responsibility of bidders to check the State Purchasing Bureau website for all addenda or amendments.
Question
RFP
Section
Reference
RFP
Pg #
Question State Response
1.
Operational Performance
6 Is the expectation that the user would be able to designate specific KPIs and have them create custom/ad hoc reports?
Yes.
2. Project Requirements and Scope of Work
4 What is the state estimated total call volume specifically for i3 events?
2024 Call Volume was 954,264. Not i3 specified.
3. Project Requirements and Scope of Work
4 What is the final statewide 9‑1‑1 call volumes for calendar years 2023 and 2024, with monthly distribution and peak busy‑hour figures?
Statewide call volumes:
2023 – 1,012,225 2024 – 954,264
4. System Reporting & Data Collection Requirements
9 Will all deployed i3 Functional Elements expose the NENA Logging Service over the ESInet per NENA‑STA‑010.3, or will any elements require PSAP‑local collectors/agents to forward LogEvents?
Yes the i3 functional elements will follow
NENA STA-010.3
5. System Reporting & Data Collection Requirements
9 What is the required online, queryable retention window for i3 LogEvents used in operational reporting and analytics (e.g., 12/24/36 months)?Logging, and Data Collection”?
24 months
SPB Form 26 Last Revised 4-17-2025
This addendum will be incorporated into the solicitation.
Question
RFP
Section
Reference
RFP
Pg #
Question State Response
6. System Reporting & Data Collection Requirements
11 Is cold storage required for long‑term access to i3 LogEvents? If so, specify the retention period (e.g., 7–10 years), retrieval‑time SLA (e.g., restore within ≤4 hours).
Yes - retain for 24 months
7. System Reporting & Data Collection Requirements
9 Beyond the solution’s built‑in statewide activity reporting, what external systems will consume i3 LogEvents via QueryLogEvents / ReplicateLogEvents and ElementState/ServiceState subscriptions?
None, other than the ESInet / NGCS provider and their customer management portal
8. System Reporting & Data Collection Requirements
9 Will Nebraska enforce strict conformance to NENA‑STA‑010.3 Logging Service and LogEvent schemas for all vendors/Functional Elements (with conformance testing and discrepancy reporting), or should the logging solution normalize and accept non‑conformant implementations? If normalization is expected, then this is a significant burden on the I3 logging vendor?
Conformance to NENA STA-010.3 is the expectation.
| SOLICITATION NUMBER: 202591102 |
| NG 911 Data Analytics Reporting System |
| Questions and Answers |
File details come from the government source that posted it. Updated .