# ATLAS (Arkansas Plate-Query System) **ATLAS** is a trooper-facing query system referenced in ASP's ALPR access and integration threads. Its full definition is not established in this production; what the record shows is that ASP treated ATLAS as a front end from which a trooper could search license-plate reads, and pursued an API to feed ELSAG historical reads into it. ## How it appears in the corpus - **In the analyst-access checklist**, "ATLAS" is one of six systems an ASP analyst is provisioned into (with ELSAG, Motorola LPR, Flock, AR Advance, and ACIC) ([[Cross-Network Analyst Access and the Arkansas State Fusion Center]]; Tier-1 corpus, `RE_ Justin Dennis - Additional Analyst Support_ ICP Accesses (1).msg`). - **In the API-integration thread**, ASP IT analyst [[James Sutton]] describes the goal: *"a Trooper enters plate 'ZZZ980' into ATLAS and is able to see any reads from our LPR system within Arkansas that match 'ZZZ980,'"* to be enabled by an ELSAG API (Tier-1 corpus, `FW_ API Information.msg`). ## Stakeholders - [[Arkansas State Police]] / [[Arkansas State Fusion Center]] — user. - [[James Sutton]] (ASP IT) and "Bhavin at CAPS," with Cisco — the integration effort. - [[ELSAG ALPR Systems]] — the ALPR read source being integrated. ## Notes `confidence: low` — ATLAS is named and functionally described (a plate-query front end) but not defined (vendor, ownership, or whether it is an ASP, fusion-center, or third-party system). "AR Advance" and "CAPS" are similarly named-but-undefined systems in the same threads. Clarifying ATLAS is an open research/FOIA question; the significant fact established is ASP's intent to make ELSAG historical reads queryable statewide by troopers.