Gear & Technology
Before the Video Wall: The IT Questions Behind Real-Time Crime Centers
A November 10 planning feature and Tempe’s public guidance highlight the staffing, security and continuity questions behind real-time police operations.

A real-time crime center needs more than camera feeds and a video wall. A November 10 Police1 feature puts the less visible work in focus: technical staffing, cybersecurity, backup arrangements and costs that continue after opening day. For police leaders considering a new center or an expansion, those are operational questions, not details to leave until installation.
The feature accompanies a Policing Matters discussion between host Jim Dudley and Eric Jensen, the city of Tempe, Arizona’s IT manager for service operations. Police1 reports that Jensen developed more than 99 questions for agencies planning a center. Its published overview emphasizes understanding who supports the technology, what vendor integration actually involves and how the operation will function when a system fails.
Tempe provides a concrete example. The city’s Information Technology Department says its police and IT departments partnered to launch the Real Time Operations Center in July 2024. The current news is the November 2026 planning discussion, not a newly opened facility.
What the center connects
According to Tempe’s official RTOC page, the center uses software to map and integrate traffic cameras, 9-1-1 calls and other technologies. The stated purpose is to give first responders information that helps them plan a response and coordinate resources before arriving.
The city describes camera connections from traffic lights, municipal buildings and some parks, alongside feeds from Valley Metro, Arizona State University and other partners. It says the system extends functions of Tempe’s Transit Operations Center, which debuted in 2017.
Tempe describes faster response and improved coordination as benefits. Those statements explain the city’s rationale, but the pages reviewed do not provide an evaluation establishing how much response times changed or which outcomes can be attributed to the center. Agencies comparing investments should keep that distinction between intended benefit and measured result in view.
Support cannot be an afterthought
Police1’s overview highlights the need for substantial IT expertise, whether that expertise sits inside a police department or elsewhere in city government. It also identifies vendor claims that no IT support is needed as a warning sign and encourages scrutiny of what integration means in practice.
The same overview points to basic cybersecurity work, including replacing default camera passwords and keeping software updated. Its continuity discussion includes redundant connections, regular testing and access to help after hours. These are subjects identified in the published episode overview, not a claim that every safeguard has been independently verified in Tempe’s operation.
OfficerList analysis: before approving a purchase, leadership should be able to identify who owns routine maintenance, who responds to an overnight failure and which functions remain available during an outage. A demonstration of several feeds on one screen does not answer those questions. Asking for named responsibilities and a tested fallback process makes the operational commitment clearer.
Camera registration is not live access
Tempe’s public guidance also illustrates why agencies need precise language when describing community camera programs. Through Connect Tempe, residents and businesses can register cameras so investigators know where footage might be requested after an incident. The city explicitly says registration alone does not provide live access.
Integration is a separate option. The city says participants can choose to connect cameras through a FususCORE device, permitting police viewing during nearby criminal activity or emergency situations. Its RTOC page also states that staff review camera footage in response to public calls rather than continuously monitoring it.
Those are the city’s published descriptions. They are not an independent audit of access logs, retention practices or compliance. The distinction matters both to community members deciding what to share and to officers explaining the program.
Questions worth settling before expansion
OfficerList analysis: a useful planning review should connect each proposed capability to a specific operational need, identify ongoing support costs and specify how performance will be assessed. Police1 flags costs that grow after launch; its written overview does not supply a complete budget or savings calculation, so neither should be assumed here.
Leaders should also ask how access is authorized, how outages are communicated to field personnel and how records requests are handled. Tempe directs requests for its RTOC records through the police public-records process, while records produced by partners should be requested from those partners. That published distinction is a reminder that connected systems do not necessarily have a single records custodian.
The practical takeaway is straightforward: evaluate a center as a continuing service, not just a room full of equipment. Technical support, clear access rules and realistic continuity planning deserve attention before a department depends on the information arriving on its screens.
Reporting note: This article draws on Police1’s November 10 written episode overview and Tempe’s public guidance, not an independently reviewed podcast transcript or a technical audit. Sections labeled OfficerList analysis are editorial implications. Additional launch-date context: City of Tempe Information Technology, https://www.tempe.gov/government/information-technology.
Sources and reporting note
This summary is based on the reporting linked below. OfficerList did not independently investigate the incident.