Regional Hexagon CAD/Records rollout delayed to Feb. 23, 2026; officials cite complexity and added integrations
Loading...
Summary
Reno and Sparks public-safety partners reported a scheduling delay in the regional Hexagon computer-aided dispatch and records management replacement project and set a new go‑live target of Feb. 23, 2026, while saying the project remains on budget and will include third‑party integrations and new AI tools.
Cody Schittel, director of Reno Public Safety dispatch, told the Sparks City Council on Aug. 25 that the regional project to replace the computer-aided dispatch (CAD) and records management system will not make its original September 2025 target and is now scheduled for a February 23, 2026 go‑live, with training starting in November.
The delay reflects the complexity of a project that now involves 17 end‑user agencies, Schittel said. "We do have a scheduling delay... So what we're looking at now is a March 26 or I'm sorry, February 26 go live. So in that time frame, we're gonna complete our testing," he said. Schittel and Russ Elder, IT development manager for the City of Sparks, emphasized that the team has completed much of the hardware and building configuration work and that the project remains on budget.
Why it matters: Council members and the public have raised concerns about emergency response and 911 reliability. Schittel said the system will be the backbone of regional public‑safety communications — dispatch, records and integrated fire/medical response — and will allow agencies to share the same language and preprogram responses for auto‑aid. He added that a nonlocal disaster‑recovery site is in place so that "911 stays up" if local connectivity is lost.
Project status and technical details: Schittel said roughly 95% of building configuration is complete and about 80% of prioritized third‑party integrations are finished. The team pared an initial list of 57 interfaces to about 34 priority integrations. The system will include a disaster recovery site in another state and will incorporate vendor AI tools to help identify commonalities across incidents in different jurisdictions.
Governance and partners: Schittel described a multi‑board governance structure — a managers board for oversight, an executive operations board and a change advisory board to manage cross‑agency changes. He identified participating entities including the cities of Reno and Sparks, Washoe County, REMSA, University of Nevada police and several tribal and township fire departments.
Next steps: The council asked for clarifications about participating agencies and timeline. Schittel said testing would continue over the next 2½ months, training would begin in November, and a vendor reliability period would follow go‑live. "We are on budget. We feel like we have enough resources," he said. Council members took no formal action; the report was informational.
Ending: Council members thanked staff for the update and said they preferred the slower schedule to ensure reliability. The project team offered to provide additional details about participating agencies and integration status on request.
