# Hot Springs Flock Procurement and Deployment Status The Hot Springs record establishes a serious, site-specific Flock acquisition process and fully executed P1977 authorization, but it stops short of proving Flock contract execution or operational completion. A non-binding one-year quote, the Chief's term negotiation, the City Manager's purchase representation, the countersigned permits, and an approved ten-site engineering plan converge on advanced implementation work. Missing Flock order/payment, installation, activation, acceptance, and current-platform records prevent the stronger conclusion that all ten sites entered service. ## Evidence - Quote `Q-162122` proposes ten solar multi-purpose LPR-and-fixed-video units for 12 months and $35,000 after a $9,000 discount, while calling itself a "non-binding proposal" ([[Hot Springs Flock Quote and Procurement Negotiation]], `Flock Safety Contract.pdf`, pp. 1-4). - Chief [[Billy Hrvatin]] said a three-year, $105,000 arrangement exceeded the relevant approval limit; Flock approved a one-year structure (same source, pp. 5-7). - City Manager [[Bill Burrough]] told ARDOT the City "has purchased several 'LPR/PTZ' cameras" ([[Hot Springs P1977 Flock Camera Plan]], `P1977...pdf`, p. 3). - ARDOT issued P1977 and approved-as-noted a ten-site plan containing exact LPR-plus-video coordinates and directions (same source, pp. 1, 5, 8-17). - The later ARDOT copy is signed by both the City and Department; the District special permit is also signed and says Flock's required `$10,000` bond was received ([[Hot Springs P1977 Countersigned Permits and Execution Chain]], cited permit pages). This resolves T019's signature conflict. - No construction completion, as-built, inspection, final acceptance, activation, or current-inventory record appears in ARDOT's five-file response; [[T054 - Hot Springs P1977 Executed Authorization vs Missing Closeout and Operational Proof]] preserves that separate lifecycle boundary. - The 2021 Vigilant forms document a prior LEARN/Standard-LPR track but leave present status and migration unresolved ([[Hot Springs Vigilant Agreements and Legacy ALPR]]). ## Caveats - Procurement intent, a City purchase representation, and executed right-of-way permits are different evidentiary stages from a fully executed Flock contract, payment, installation, activation, acceptance, and present operation. - The exact ten plan points are intentionally mapped, but as final engineering-plan records rather than current camera inventory. - Quoted Flock network, audit, hot-list, NCIC, and video capabilities are not proof of tenant configuration or use. - The public-framing document's recommended safeguards are not evidence that HSPD adopted them. - The record does not establish whether Vigilant equipment was retired, retained, or integrated during the Flock process. ## Open questions - Where are the executed Flock order/MSA, purchase order, invoices, payments, delivery, validation, activation, and acceptance records? - Where are the P1977 construction schedule, completion return, as-built, inspection, final acceptance, and activation records? - What is HSPD's current complete camera inventory and native platform/GIS export? - Which Flock tenant, sharing, access, retention, audit, policy, training, and six-month-report records currently exist? - What is the disposition of HSPD's legacy Vigilant/LEARN system?