# Vigilant LEARN LPR Network Vigilant's Law Enforcement Archival and Reporting Network, described in the Hot Springs agreement forms as the hosted platform through which authorized agency users access LPR software and law-enforcement plate data. ## How it appears in the corpus - The May 2021 HSPD form selects the Standard LPR package, adding CarDetector Mobile Hit Hunter and Mobile Companion to the Basic hosted-LEARN package ([[Hot Springs Vigilant Agreements and Legacy ALPR]], `VIGILANT Enterprise Service Agreement (ESA).pdf`, p. 6). - The agreement permits HSPD, at its option, to share its agency LPR data with similarly situated LEAs that contract with Vigilant to access LEARN, while stating that Vigilant will not share agency-generated data without the affiliate's permission (same source, p. 5). - The July 2021 L5Q form specifies a hosted LEARN account and six L5Q camera-license keys, but its signature page is blank (same source, `VIGILANT Enterprise Service Agreement (ESA) - L5Q.pdf`, pp. 6, 9). ## Stakeholders - [[Vigilant Solutions, LLC]] - software/platform vendor. - [[Hot Springs Police Department]] - affiliate named in the produced forms. - Authorized agency users and any participating LEAs approved for sharing under the agreement terms. ## Timeline - 2021-05-04 - HSPD signs the agency side of a Standard LPR Enterprise Service Agreement. - 2021-07-06 - a separate L5Q form identifies six camera-license keys but remains unsigned on the produced signature page. - 2023-01-24 - Jacksonville issues Purchase Order `23-131696` for four Vigilant L6Q systems after signing the terms acknowledgement; the later supplement supplies the quote and ordering packet but not the complete master terms or lifecycle record. - 2026-07-14 - Jacksonville's produced VehicleManager reports list ten mobile systems, three standalone systems, 37 camera-channel lines, and a separate 2,807-row all-agencies directory. - 2025-2026 - HSPD negotiates a Flock proposal and seeks ARDOT approval for ten Flock LPR/video sites; the Vigilant system's disposition is not produced. ## Notes The Hot Springs forms define platform capabilities and contractual options. Jacksonville supplies a customer-signed acknowledgement, the four-L6Q purchase packet, five M500 integration-license procurement, a 2026 renewal, and current VehicleManager artifacts ([[Jacksonville Motorola Vigilant Procurement and Renewals]]). The complete master terms, site/lifecycle crosswalk, and termination history remain absent. The 2,807-row all-agencies directory carries no relationship direction or active-access field and is not proof that Jacksonville exchanges data with every listed agency.