# Real-Time Crime Center (RTCC) A centralized police capability — a facility, a software platform, or both — that aggregates live and recorded data feeds (video cameras, ALPR, computer-aided dispatch, records management, body-worn camera, drone, and 911 data) for real-time monitoring, alerting, and investigative search. In the corpus the RTCC is the stated destination toward which ALPR adoption is the first step, and the organizing concept of both vendors' sales pitches to Fayetteville PD. ## How it appears in the corpus - **FPD's stated objective.** Capt. French's 2025-10-16 Flock pricing briefing frames the project as one that provides "a clear path to a Real-Time Crime Center in the future" ([[Flock Safety Procurement Courtship]]). - **Axon's roadmap.** Axon's 2026-03-27 meeting recap lists, as a Fayetteville next step, "Begin internal alignment on RTCC priorities (Existing Avigilon, Cameras, LPR + Fusus as initial focus)," and commits Axon to "budgetary modeling" for "Fusus / RTCC components" ([[Axon RTCC and Surveillance Ecosystem Pitch]]). Axon's RTCC platform is **Fusus**. - **Flock's pitch.** Flock's tiered proposal positions its LPR-plus-live-view bundle as the foundation of the same real-time-operations end state ([[Flock Safety Procurement Courtship]]). ## Stakeholders - **The agency** — gains a centralized surveillance-and-response capability; also assumes the staffing, policy, and oversight obligations an RTCC implies. - **The vendors** — Axon (via Fusus) and Flock each market the RTCC as the destination that justifies buying their full product stack. - **The public** — an RTCC concentrates multiple surveillance feeds into one continuously monitored system; the corpus contains no public-facing policy governing it. ## Timeline - 2025-10 — FPD command briefed on a Flock package offering "a clear path to a Real-Time Crime Center." - 2026-03 — Axon names RTCC "internal alignment" as a Fayetteville next step and offers RTCC budgetary modeling. ## Notes The RTCC reframes an ALPR trial: a plate reader is not an endpoint but the first feed into a larger real-time surveillance architecture. Both vendors competing for Fayetteville sell the ALPR capability as the entry product and the RTCC as the goal. No RTCC plan, budget, staffing model, or governing policy appears in the production — only the vendor-stated trajectory and FPD's expressed interest. ## Aspiration to operation: the Little Rock evidence (CLR-2026-778) The [[sources/city-of-little-rock/CLR-2026-778/_overview|CLR-2026-778]] production converts the RTCC from a Conway/Fayetteville **vendor-pitched aspiration** to a Little Rock **documented operational reality**. The key documents: 1. **Resolution 15,763 (2022-09-06)** — Authorized $128,937/yr × 3 years for the Fusus RTCC platform, funded from **Seized Funds Account 270529-G3514**. See [[2022-09 Little Rock Funds Fusus RTCC from Seized Funds (Resolution 15763)]]. 2. **Resolution 15,702 (2022-06-07, referenced)** — Approved funding "to equip and operate the Real Time Crime Center and to outfit the designed workspace in the LRPD Headquarters Building." This is the *physical RTCC buildout* — the room, the workstations, the displays — predating the Fusus software contract by three months. 3. **[[Fusus]] Service Agreement Proposal (2022-08-18)** — Detailed the Enterprise Package: fususONE (Real-Time Crime Center in the Cloud, 1,500 data points + 1,500 video feeds); fususCORE (edge appliances); fususREGISTRY (community camera registry); fususVAULT (CJIS-compliant evidence vault); fususOPS, fususTIPS, fususAlert, fususANALYTICS. 4. **[[NICE Investigate (MRA and Order 00479378)]] §2.2.4** — The 2025 NICE Investigate Order explicitly integrates NICE Investigate with Fusus: "evidence tagged with a case number in Fusus will be added to the matching case folder in NICE Investigate." This is the load-bearing cross-tag. LRPD's [[Real-Time Crime Center (RTCC)]] is therefore operationally documented via: - **The integration platform:** [[Fusus]] (now an [[Axon Enterprise, Inc.]] subsidiary) - **The video / ALPR layer:** [[Flock Safety, Inc.]] (115 cameras, $345K/yr; explicitly tasked to the RTCC per the Phillips memo and Resolution 16,846) - **The link-analysis layer:** [[i2 Group]] (Analyst's Notebook + iBase, "used by Special Investigations, Real time Crime Center, and Gun Crimes Intelligence Unit") - **The in-vehicle connectivity layer:** [[Utility Associates]] (POLARIS / Rocket modems on 225 patrol vehicles; "RTCC funding allocation 108529-S52C458") - **The post-incident evidence layer:** [[NICE Systems]] (NICE Investigate, $100K/yr, 84-month retention, cross-tagged with Fusus) - **The gunshot-detection layer:** [[SoundThinking]] (ShotSpotter + CaseBuilder) - **The in-car / body-camera video layer:** [[Motorola Solutions]] (Watchguard M500 + CommandCentral + VideoManager EL Cloud) The RTCC is funded across two distinct LRPD account streams: - **Seized Funds Account 270529-G3514** — Fusus original procurement (Res. 15,763) - **RTCC funding allocation 108529-S52C458** — i2, Utility (and others) RTCC carve-out - (Plus general fund 105225-63360 for Flock, ARPA 270529-G0601 AR52A for ShotSpotter, Salary Savings 105201-613 for Motorola iCloud, etc.) See [[Competing ALPR Vendors and the Real-Time Crime Center]] (synthesis) for the cross-jurisdiction analytic arc: Conway and Fayetteville show the RTCC as vendor-pitched aspiration; Little Rock shows it operational. ### In PDFOI-2026-1874 (LRPD Flock emails) The LRPD production documents the RTCC as the operational hub of a **dual stack** — Flock LPR alongside Axon Fusus (fususOne) — rather than a single-vendor platform. Fusus release notes are routed to a small set of named LRPD users, and fususOPS Mobile integrates LRPD's Axon body-worn and in-car device fleet into the RTCC app, while the Flock layer supplies the LPR feed and hot-list alerting ([[Flock-Axon API Dispute and the Dual RTCC Stack]], Emails 25-35.pdf pp. 476, 503-504). The RTCC runs its own Flock alert account, `[email protected]`, which appears as a registered hot-list **Alert Owner** ("RTCC RTCC") across many overlap and deconfliction tables, confirming RTCC ownership of hot-list alerts ([[Flock-Axon API Dispute and the Dual RTCC Stack]], Emails 36-63.pdf pp. 1167, 1456). RTCC technician Debra Pitts runs weekly Flock camera health checks, including camera #29 `W Roosevelt Rd WB @ Main St`; the production's complete sixteen-device directional register is at [[Flock LPR Deployment Expansion and Permitting Delays]] and [[Arkansas ALPR Camera Coordinates and Directional Nomenclature]]. The same hot-list infrastructure distributes ALPR-derived BOLOs/deconfliction advisories to LRPD Alert Owners. Chief Heath Helton frames data-compilation as a defense of the RTCC's value: forwarding a Fortune article on Flock cancellations, he directed Lt. Courtney Bewley to "continue to effectively compile our data to show how we're utilizing our systems professionally and ethically," anticipating criticism "from some of those who see no value in the RTCC" ([[Chief Helton RTCC Defense Thread]], Emails 36-63.pdf p. 405). ## Notes (extended) - The RTCC at LRPD is the documented integration point for at least seven distinct surveillance/investigative product lines from at least seven distinct vendors. The architecture is multi-vendor; the integration is contractually documented via the NICE §2.2.4 Fusus cross-tag. - The [[Asset-Forfeiture Funding for Surveillance Procurement]] thread documents the funding-source pattern at LRPD: the Fusus RTCC platform was originally funded from Seized Funds (asset-forfeiture proceeds); subsequent buys (Motorola Watchguard M500, parts of the connectivity/intelligence stack) follow the same forfeiture-funded pattern. - The corpus does not produce **public-facing policy governing the RTCC** at LRPD — staffing, hours of operation, oversight mechanisms, retention rules, or community-reporting obligations. These are absent from the procurement-records production. A successor FOIA could ask LRPD's RTCC standard operating procedures, audit logs, and oversight reports.