# Competing ALPR Vendors and the Real-Time Crime Center The corpus's two jurisdictions reveal automatic-license-plate-reader adoption in Arkansas as a competitive, multi-vendor market — and one in which the competition itself shapes what agencies acquire. **More than one vendor, more than one product.** [[Conway Police Department]] runs a Flock Safety system and, before it, operated six Genetec license-plate-reader cameras ([[Automatic License Plate Reader (ALPR)]]). [[Fayetteville Police Department]] trialed Axon's Fleet 3 mobile ALPR and is, separately, weighing a Flock Safety purchase. Three vendors — Flock, Axon, Genetec — appear across two jurisdictions. ALPR in Arkansas is not a single-company story. **Head-to-head competition for the same agency.** Fayetteville is the clearest case. Across late 2025 and into 2026, FPD was simultaneously the subject of an Axon ALPR trial and a broader Axon ecosystem sales effort ([[Axon RTCC and Surveillance Ecosystem Pitch]]) while a Flock Safety account executive ran a parallel courtship — an on-site demo, a camera deployment plan, and tiered pricing ([[Flock Safety Procurement Courtship]]). The agency was, in effect, a contested account, weighing competing vendors for the same capability at the same time. **An interoperability feud.** The competition is not only commercial. The corpus retains a February 2025 customer broadcast from Axon's founder and chief executive stating that Axon had terminated its partnership with Flock, alleging that Flock charged "excessive fees for API integrations between Flock and Axon systems ranging from $10,000 to $50,000 per year" and had refused to let Axon-platform customers pull ALPR data from their own Flock cameras ([[Axon RTCC and Surveillance Ecosystem Pitch]]). Whatever the merits of that account, the dispute carries a concrete implication for agencies: the portability of an agency's own ALPR data between platforms is contested between the vendors. A jurisdiction that adopts one vendor's system may find its data harder to use with another's — a lock-in dynamic that is a product of the vendor competition, not of any agency's deliberate choice. **A shared destination: the Real-Time Crime Center.** For all their rivalry, the vendors sell toward the same end-state. Axon frames Fleet 3 ALPR as one feed in an integrated stack — Outpost and Lightpost fixed LPR, the Fusus platform, AI tools — explicitly oriented toward a [[Real-Time Crime Center (RTCC)]]; its meeting recap lists "RTCC priorities" as a Fayetteville next step ([[Axon RTCC and Surveillance Ecosystem Pitch]]). Flock's pricing briefing to Fayetteville command frames its LPR-and-live-camera bundle as providing "a clear path to a Real-Time Crime Center in the future" ([[Flock Safety Procurement Courtship]]). In both pitches the plate reader is the entry product; the RTCC — a standing, multi-feed surveillance operation — is the destination each vendor names. **Why it matters.** Read together, the two productions suggest that an Arkansas law-enforcement agency considering ALPR is not making a discrete, bounded decision about license-plate cameras. It is choosing an entry point into a vendor ecosystem — in a market where vendors compete partly by making each other's systems harder to leave, and where every vendor's roadmap leads to the same expanded surveillance capability. On the evidence here, the question "should we adopt a plate reader" and the question "should we build toward a real-time crime center" are marketed to agencies as the same question. ## Evidence - **A multi-vendor field.** Conway's current Flock fleet and prior Genetec cameras ([[Automatic License Plate Reader (ALPR)]]); Fayetteville's Axon Fleet 3 trial ([[Axon Fleet 3 ALPR Trial]]) and concurrent Flock courtship ([[Flock Safety Procurement Courtship]]). - **Concurrent competing pitches.** Axon's trial-plus-ecosystem effort and Flock's tiered proposal both ran at Fayetteville PD across 2025–2026 ([[Axon RTCC and Surveillance Ecosystem Pitch]], [[Flock Safety Procurement Courtship]]). - **The feud.** A 2025-02 letter from Axon's CEO to customers announces the termination of Axon's Flock partnership and alleges Flock integration fees of "$10,000 to $50,000 per year" and the blocking of Axon-platform access to customers' Flock-camera data ([[Axon RTCC and Surveillance Ecosystem Pitch]]). - **RTCC convergence.** Axon's roadmap names a Real-Time Crime Center as Fayetteville's destination ([[Axon RTCC and Surveillance Ecosystem Pitch]]); Flock's briefing promises "a clear path to a Real-Time Crime Center" ([[Flock Safety Procurement Courtship]]). ## Caveats - The Axon–Flock feud is documented through one party's account (Axon's CEO letter, retained in an FPD mailbox). The wiki records it as evidence of what Axon told its customers, not as an adjudication of the dispute or an endorsement of either vendor's claims. - Genetec appears only as a prior Conway vendor named in passing; its procurement and its terms are not in the corpus. - Two jurisdictions; this market characterization is a hypothesis that future productions will test. - This page is the author's analytical synthesis, demarcated as such. Every factual claim above is anchored to a source page and, through it, to a raw FOIA document. ## Open questions - Which vendor, if any, does Fayetteville ultimately select — and on what timeline? - ~~Do the other filed jurisdictions (Arkansas State Police, Little Rock PD, Pulaski County SO) show the same multi-vendor competition, or single-vendor entrenchment?~~ — **partially answered for LRPD by [[CLR-2026-778]]: LRPD documents at least seven distinct vendor relationships in the surveillance/investigative-technology stack, with Flock as the primary ALPR vendor (115 cameras since 2020) and Axon (via the Fusus acquisition) as the RTCC integration platform — a multi-vendor pattern in active deployment, not single-vendor entrenchment.** - ~~How far have any Arkansas agencies moved from ALPR toward an actual operational Real-Time Crime Center?~~ — **answered by [[CLR-2026-778]]: LRPD documents an operational RTCC.** See the Status section below. ## Status — operational RTCC at LRPD (2026-06-05 update) The 2026-06-04 production [[CLR-2026-778]] documents — for the first time in the Arkansas Surveillance corpus — an **operational Real-Time Crime Center** at the [[Little Rock Police Department]]. The keystone evidence: 1. **The 2022 Fusus procurement (Resolution 15,763, $128,937 × 3 years).** Authorized the **Real Time Crime Center in the Cloud** (fususONE), with 1,500 simultaneous public/private video feeds and a CJIS-compliant evidence vault. See [[Fusus]]. 2. **The 2022 RTCC physical buildout (Resolution 15,702, June 7, 2022).** Approved funding "to equip and operate the Real Time Crime Center and to outfit the designed workspace in the LRPD Headquarters Building" — establishing that LRPD has a physical RTCC space, not just a software subscription. 3. **The 2025 NICE Investigate integration (Order 00479378 §2.2.4).** Explicitly cross-tags NICE Investigate (the digital-evidence-management cloud) with Fusus: "evidence tagged with a case number in Fusus will be added to the matching case folder in NICE Investigate." See [[NICE Investigate (MRA and Order 00479378)]]. 4. **The 2025 Flock LPR Renewal (Resolution 16,846, $690K, 115 cameras).** Explicitly tasks the Flock cameras to "the Little Rock Police Department Real Time Crime Center" per the Phillips originating memo and the resolution text. See [[Flock LPR Renewal (Resolution 16846)]]. 5. **The vendor ecosystem under RTCC operational scope.** [[i2 Group]] (link analysis, "used by… the Real Time Crime Center"); [[Utility Associates]] (in-vehicle connectivity, "RTCC funding allocation 108529-S52C458"); [[SoundThinking]] (gunshot detection — feeds the RTCC alert layer); [[Motorola Solutions]] (Watchguard MVR, CommandCentral records management, VideoManager EL Cloud). Each is contractually integrated into the LRPD surveillance stack the RTCC oversees. **LRPD's operational RTCC is multi-vendor.** The Fusus integration platform is Axon-owned (post-2024 acquisition); the Flock LPR feeds it from one side; the NICE Investigate evidence layer cross-tags with it from another; the Motorola CommandCentral records-management suite ties into the same workflow. This converts the synthesis essay's central observation — that the RTCC is "the destination each vendor names" — from aspiration to a documented multi-vendor operational reality at the corpus's third Arkansas jurisdiction. **The Axon-Flock feud — operational implications at LRPD.** The feud documented in this synthesis (Axon's 2025-02 customer letter alleging Flock charged "excessive fees for API integrations") takes on new significance at LRPD: Axon now owns Fusus (the LRPD RTCC platform), and Flock is the primary ALPR feed into that platform. Whether the Axon-Flock integration friction affects LRPD's operational data portability — i.e., whether LRPD can in fact pull Flock data into Fusus the way the architecture implies — is a downstream operational question the corpus does not directly answer. The [[Fusus]] product line includes "Integration of Computer Aided Dispatch, AVL, drone feeds, covert cameras, and license plate readers as required" per the 2022 Service Agreement Proposal; whether the LRPD's specific Flock data reaches Fusus through that integration, or via Flock's own native interface, is not documented in this production. ## Confidence Confidence remains `medium`. The LRPD operational-RTCC finding is firmly documented (the synthesis update above moves the central open question from speculative to settled). The vendor-competition framing is confirmed across all three documented Arkansas jurisdictions (Conway = Flock entrenched + Genetec historical; Fayetteville = active Axon vs Flock courtship; Little Rock = Flock + Axon-via-Fusus + multi-vendor stack). The interoperability-feud caveat persists — the Axon-Flock dispute is documented through one party's account; whether the operational integration at LRPD is in fact friction-free is not directly observable from procurement records.