# Cross-Network Analyst Access and the Arkansas State Fusion Center Two threads document that ASP's ALPR reach is **multi-vendor and cross-network**: an ASP analyst is provisioned across six systems — ELSAG, Motorola LPR, Flock, AR Advance, ATLAS, and ACIC — coordinated through the [[Arkansas State Fusion Center]], and ASP separately pursues an **API integration** so a trooper can query historical ELSAG plate reads from inside the [[ATLAS (Arkansas Plate-Query System)|ATLAS]] system. This is the first corpus evidence that ASP taps [[Flock Safety, Inc.|Flock]] and [[Motorola Solutions|Motorola]] plate data, not only its own ELSAG cameras. ## What's inside ### `Justin Dennis - Additional Analyst Support / ICP Accesses` (2025-01-07 → 01-08) Criminal Analyst [[Suzanne Diel]] (signing *"Arkansas State Fusion Center // Arkansas Counterdrug"*) lists the access an ASP analyst needs, system by system: > *"1. ELSAG: Lt Overton may you coordinate this? / 2. Motorola LPR: Overton/Patterson initiate / 3. Flock: Overton/Patterson initiate / 4. AR Advance: Suzanne will request / 5. ATLAS: Suzanne will request / 6. ACIC: Mike, may you coordinate this?"* (Tier-1 corpus, `RE_ Justin Dennis - Additional Analyst Support_ ICP Accesses (1).msg`). [[Dennis Overton|Overton]] forwards the access request to Josh Middleton (`[email protected]`), framing the work: > *"Looks like this targeting initiative is going to really start producing some good results. Bryan Sparks is leaving for a 6 week training assignment and his counterpart is Justin Dennis will be assisting us… Can you assist with getting Justin access to the ALPR's as well?"* (Tier-1 corpus, same file). ### `FW_ API Information` (2025-09-15 → 09-17) ASP IT Infrastructure Analyst [[James Sutton]] describes an integration goal to Overton, for relay to ELSAG: > *"Bhavin at CAPS reviewed the documentation provided but did not see a way to use the API to get historical reads and wanted to ensure it is possible to query historical reads from a search function with the API. IE: a Trooper enters plate 'ZZZ980' into ATLAS and is able to see any reads from our LPR system within Arkansas that match 'ZZZ980'… Can you send this over to your contacts at ELSAG…?"* (Tier-1 corpus, `FW_ API Information.msg`). Leonardo's Rob Ryan replies that the vendor side is ready: *"the API from our side is already built out and available… put them together with Cisco for discussions on the actual process."* (Tier-1 corpus, same file). *("ZZZ980" is an illustrative placeholder plate used in the email, not a real registration.)* ## Key takeaways - **ASP analysts are provisioned across six ALPR/data systems — including Flock and Motorola.** The Fusion Center's own checklist enumerates ELSAG, Motorola LPR, **Flock**, AR Advance, ATLAS, and ACIC (Tier-1 corpus, `RE_ Justin Dennis - Additional Analyst Support_ ICP Accesses (1).msg`). This is the corpus's first documentary evidence that ASP accesses [[Flock Safety, Inc.|Flock]] data — the investigation's anchor vendor — alongside its own ELSAG deployment. - **ACIC sits in the access stack.** [[Arkansas Crime Information Center|ACIC]] appears as item 6, coordinated by [[Mike Patterson]] (Tier-1 corpus, same file). ACIC — the candidate state-level CJIS-Systems-Agency and outstanding FOIA target — is one of the systems ASP analysts are provisioned into. - **ASP is building a statewide plate-query capability via ATLAS↔ELSAG API.** The stated goal is for a trooper to enter a plate in [[ATLAS (Arkansas Plate-Query System)|ATLAS]] and *"see any reads from our LPR system within Arkansas that match"* (Tier-1 corpus, `FW_ API Information.msg`). ELSAG confirms the API is built and available. This wires ASP's fixed-ALPR read history into a queryable trooper-facing system. - **The Fusion Center / Counterdrug is the coordinating node.** Access is organized through the [[Arkansas State Fusion Center]] ("// Arkansas Counterdrug"), with Overton and Patterson as the ALPR-side coordinators (Tier-1 corpus, `RE_ Justin Dennis…`). This situates ASP's ALPR access inside the state fusion-center apparatus. - **Bearing on the coordination tension.** Cross-network provisioning (Flock, Motorola, ACIC) and a statewide plate-query build are a broad data-reach posture. It does not, by itself, establish ASP *oversight* of the agencies that own those Flock/Motorola systems — but it complicates a clean reading of ASP as merely a single-camera operator. See [[T006 - ASP ALPR Oversight Disclaimer vs Statewide Coordination Role|T006]]. ## Cross-references - [[ASP–Houston HIDTA MOU and ELSAG Domain Architecture]] — the ELSAG-side provisioning this access rides on. - [[Federal Public Defender FOIA and the No-LPR-System Position]] — the "use vs. have" question, sharpened by documented cross-network *use*. - [[Flock Safety, Inc.]] — accessed by ASP per this thread; the corpus's analytic anchor. ## Open questions / follow-ups 1. **What are "AR Advance," "ATLAS," and "CAPS"?** ATLAS is the trooper-facing plate-query front end; AR Advance and CAPS (where "Bhavin" reviewed the API docs) are named but not defined in the record. See [[ATLAS (Arkansas Plate-Query System)]]. 2. **Whose Flock and Motorola systems does ASP access, and under what agreement?** The checklist shows ASP obtaining Flock and Motorola LPR access but not which agencies' deployments or on what legal basis. 3. **Did the ATLAS↔ELSAG historical-read API go live?** The record shows intent and vendor readiness (with Cisco), not confirmed deployment.