# Jacksonville Police Department First Production The [[Jacksonville Police Department]] delivered an expiring SharePoint/OneDrive folder on 2026-07-27 at 11:32 CDT. The preserved package contains **17 files**: 13 PDFs totaling **215 pages**, one native CSV with 84,143 event rows, and three PNG screenshots. The downloaded ZIP and every extracted file were hashed before the package was copied into the immutable raw layer. Image-only pages and screenshots were OCRed and visually checked; integrity details are recorded in `_phase0_workdir/jacksonville-first-production-ingest-manifest-2026-07-27.md`. ## What's inside - [[Jacksonville Flock and Wing Camera Location Export]] — a three-page Flock tenant export with 126 rows: 117 camera rows and nine compute-box rows, all carrying exact coordinates. - [[Jacksonville Flock Access Analytics and Event Logs]] — a 349-row outside-agency-access printout, hot-list analytics, a native 84,143-row tenant event log, and a dashboard map screenshot. - [[Jacksonville VehicleManager System and Data-Sharing Reports]] — a Motorola/Vigilant system-camera report, device screenshot, retention screenshot, and a 178-page all-agencies directory. - [[Jacksonville LPR Policy and Retention Settings]] — Policy 10-28 plus produced Flock and VehicleManager retention settings. - [[Jacksonville Flock Wing Order and Motorola-Vigilant Acknowledgements]] — a customer-signed Flock Wing order and isolated Motorola and Vigilant terms acknowledgements. - [[Jacksonville ARDOT Permit 1916 and SP-06-2026-0005]] — a signed TCD permit page, mayoral permit request, and a six-page special-permit packet for F#003 and F#008. ## Key takeaways 1. **The location export accounts for the public 117-camera figure.** Its 126 rows break down as 14 `LPR Camera`, 101 `Video Integration`, two `Video Camera`, and nine `Compute Box` rows. Excluding the nine non-camera compute boxes leaves **117 camera rows at 102 distinct exact coordinate strings** (`Flock Camera Location Data.pdf`, pp. 1-3). 2. **Wing is operationally documented in Arkansas for the first time in this corpus.** The 101 integration rows are divided between `Jacksonville AR PD (Wing)` and `Jacksonville AR PD - (PD Wing)`. The produced order separately describes a 128-stream Wing gateway and says FlockOS Advanced integrates third-party live video cameras (`PO- Flock Safety - Documents (003).pdf`, pp. 2, 5). 3. **The order does not procure the 14 fixed LPRs.** It lists one 128-stream Wing gateway, a 45-day opt-out, 30-day retention, a $14,500 first-year total, and $14,000 annual recurring subtotal. Jacksonville's signature is dated 2024-10-21; the produced vendor signature fields are blank (pp. 2-3). 4. **The native Flock event log is substantial but not a complete configuration export.** It has 84,143 rows from 2025-01-13T19:35:31Z through 2026-07-24T13:09:08Z. Machine grouping yields 55,949 updates, 26,340 reads, 1,768 creates, and 86 deletes; `stream` is the dominant entity type with 79,301 rows (`FLOCK - event-logs.csv`, header and data rows 1-84143). 5. **The Flock access printout is a permissions view, not a bidirectional topology export.** It displays 349 `Access` rows. Search is shown enabled on 343 rows and disabled on six; hot-list access is enabled on 287 and disabled on 62. The artifact does not define direction, history, or whether Jacksonville data are shared back (`Devices - Jacksonville AR PD - Admin - Flock Safety - OUTSIDE AGENCY PARTICIPATION.pdf`, pp. 1-12). 6. **The VehicleManager artifacts do not reconcile the City's historical 80-camera/20-location description.** The one-page system report names ten mobile systems and three standalone systems with 37 listed camera channels, while the device screenshot displays six mobile companion devices and two L6Q rows. No lifecycle, replacement, or complete site export explains the different scopes (`VM-System_Cameras_Report_07-14-2026-12-20-23-466.pdf`, p. 1; `VM Camera Location Data.png`). 7. **Local policy requires operational records that were not produced.** Policy 10-28 requires records identifying approved deployments and their results, dispositions for alerts/hits, reasons for manual hot-list entries, and a secondary-dissemination log (`JPD Policy 10-28 License Plate Readers.pdf`, p. 2). 8. **Permit evidence advances F#003 and F#008 beyond proposal, but the closeout remains unresolved.** ARDOT's February 3, 2026 letter grants special permit `SP-06-2026-0005` for the two points and records a $2,000 standing bond, while the acknowledgement and completion fields in the produced packet are blank (`permit hwy 294.pdf`, pp. 1, 3-6). The current Flock export lists both cameras at near-identical, higher-precision coordinates. ## Safety and integrity The ZIP contained no unsafe paths. All PDFs are valid and unencrypted, and no JavaScript, launch action, embedded file, rich media, XFA, submit action, open action, or additional action was detected. Microsoft Defender reported no threat. Raw hashes were rechecked after preservation. ## People and organizations - [[Brett Hibbs]] — Police Chief; signed the Motorola acknowledgement, Vigilant acknowledgement, Flock order, and Policy 10-28. - [[Jeff Elmore]] — Mayor; requested ARDOT permitting for Jacksonville's LPR/PTZ placements. - [[Joseph D. Hawkins]] — ARDOT TSMO Division Head; signed the Department side of TCD Permit 1916. - [[Jacksonville Police Department]]; [[City of Jacksonville]]; [[Flock Safety, Inc.]]; [[Motorola Solutions]]; [[Vigilant Solutions, LLC]]; [[Arkansas Department of Transportation]]. ## Events documented - [[2023-01 Jacksonville Signs Vigilant Terms Acknowledgement]] - [[2023-03 Jacksonville Signs Motorola Online Terms Acknowledgement]] - [[2024-10 Jacksonville Signs Flock Wing Order]] - [[2024-11 Jacksonville Implements LPR Policy 10-28]] - [[2025-10 Jacksonville and ARDOT Sign TCD Permit 1916]] - [[2026-02 ARDOT Grants Jacksonville Special Permit SP-06-2026-0005]] ## Open questions / follow-ups - Native CSV/XLSX/GIS/platform exports and field definitions for the complete camera-location data, including status and lifecycle fields. - Fully executed procurement records, purchase orders, invoices, payment records, renewals, and site schedules for all 14 Flock LPRs and the Wing deployment. - Complete Motorola/Vigilant master agreements, addenda, statements of work, ordering documents, pricing, inventories, lifecycle records, and current-versus-retired status. - Current and historical native Flock SharedNetworks, role, permission, user/access, organization-access, and audit exports showing both access directions. - The six-month reports required by Ark. Code Ann. § 12-12-1805 and the operational records required by Policy 10-28. - Final acknowledgement, installation, inspection, acceptance, closeout, relocation, and current-status records for ARDOT case 767333, Permit 1916, and `SP-06-2026-0005`. - Category-by-category confirmation of no records, referral, or exemption for anything not produced.