# Federated Incident-Data Sharing **Federated incident-data sharing** is ACIN's stated model for connecting agency records systems across jurisdictional boundaries while leaving ownership and release control with the contributing agency. The public-facing materials call ACIN a "shared investigative support environment - not a centralized ownership system" ([[ACIN Privacy and Security Overview 2026-05-15]], p. 2). The final package supplies contracts, participation terms, policies, and status records that make the proposed architecture more concrete while exposing unresolved limits. ## How it appears in the corpus - The recurring MOU says each agency's RMS is the primary source and that data will be centralized in a cloud platform for AI-assisted searching and linking. The same clause limits the shared content to "ONLY INCIDENT REPORT INFORMATION" and excludes investigative files ([[ACIN Agreements and Participation Terms]], `AGR-201_El_Dorado_PD_MOU_EXECUTED_2026-05-15.pdf`, p. 1). - The executed Peregrine/Carahsoft package identifies 45 agency roles across two phases and a platform for integrating, modeling, searching, analyzing, visualizing, sharing, and acting on multiple data sources. Its Arkansas addendum also requires a separate, source-restricted environment for approved third-party vendors ([[Peregrine and Carahsoft Executed Contract]], `CON-002_Peregrine_Carahsoft_Executed_Contract_2026-03-17.pdf`, pp. 2-5, 20). - The executed LeadsOnline package contemplates continuous automated searching of transmitted case files, complete-case sharing, phone-extraction material, communications, movement, and location analysis ([[LeadsOnline Executed Contract]], `CON-001_LeadsOnline_Executed_Contract_2026-07-13.pdf`, pp. 15-17, 25, 46-47). - The policy manual assigns ownership to the originating agency, requires originating-agency tags and modification/deletion audit trails, and describes ACIN as a shared environment rather than the legal custodian of individual records ([[ACIN Policy and Operations Manual]], `POL-301_ACIN_Policy_and_Operations_Manual_REDACTED_2026-01.pdf`, pp. 16, 43-44). - The March vendor scope, July 44-row project table, and 27-unit agreement set are not one reconciled participant roster. Project labels such as "Integrating" and "Awaiting data access" are not system-generated proof of a funded production connection ([[ACIN Participant and Integration Status]], `STS-301_ACIN_Agency_Status_2026-07-15.pdf`, p. 1). > [!contradiction] Incident-only federation versus investigative-data services > The MOU and integration policy exclude investigative files, but another manual section expressly classifies case notes, attachments, and suspect associations as investigative data, and the LeadsOnline contract covers complete cases and phone, movement, narrative, and location analysis. See [[T030 - ACIN Incident-Report-Only Scope vs Investigative Data Services]]. ## Stakeholders - [[Arkansas Criminal Intelligence Network]] and the [[Sixth Judicial District Prosecuting Attorney's Office]]. - Participating and prospective agencies represented differently across the contract, status table, and agreement set. - [[Peregrine Technologies, Inc.]], [[Carahsoft Technology Corp.]], and [[LeadsOnline]]. - [[ACIN Oversight and Governance Board]] and originating-agency records custodians. ## Notes "Federated" describes ACIN's ownership, integration, and access model; it does not establish that data stays solely inside each originating system. The contracts authorize vendor processing and centralized or shared-service functions. The package contains no completed data dictionary, configuration export, funding-availability notice, acceptance test, or activity log proving which connections and fields became operational. See [[T032 - ACIN Participation Rosters and Agreement Status]].