# Digital Evidence Management Cloud A cloud-based platform for **ingestion, retention, search, redaction, and disclosure** of digital evidence — body-worn-camera (BWC) and in-car-video (MVR) footage, 911 audio, surveillance video, smartphone-extraction outputs, and case documents. Marketed as "DEMS" (Digital Evidence Management System) and increasingly with auto-transcription, AI redaction, and chain-of-custody features. ## Five documentary postures across five agencies The corpus does not document a single Arkansas norm. It documents four agency cases making materially different storage and procurement choices. Three involve the same WatchGuard/Motorola product family; LRPD also operates NICE Investigate as a parallel case-evidence cloud. | Agency | Where video lives | Contract basis | Sharing posture | |---|---|---|---| | [[Little Rock Police Department]] | **Dual-vendor cloud** — NICE Investigate for cases, Motorola VideoManager EL Cloud for devices | NICE MRA + Order 00479378 ($100,000/yr); Ord. 22,331 sole source ($850,520 over Sept 2023 - Dec 2025) | Integrated with [[Fusus]] via the § 2.2.4 cross-tag | | [[Faulkner County Sheriff's Office]] | **Vendor cloud as a service** — 100 WatchGuard V300 body cameras bought as a five-year Motorola CommandCentral Video-as-a-Service | Contract `K-22-077`; invoice $320,827.50, CARES Act funded, $176,000 federally reimbursed | Contract expressly includes **"unlimited cloud sharing"**; no sharing configuration was ever produced | | [[Benton County Sheriff's Office]] | **On-premises, cloud expressly declined** | Not produced | Agency states its WatchGuard cameras are "not connected to cloud services" and "download locally via Wi-Fi to on prim storage" | | [[Arkansas State Police]] | **Server-to-cloud replacement ordered; operational cutover not established** — legacy 4RE/VideoManager system described by ASP as server-based, with Year-1 VideoManager Evidence Library cloud later ordered | May 2025 `$4,231,414` review memo; PO `4502304706` for `$708,739.02` including tax; four separate equipment orders cover 550 systems/modems | Produced cloud PO gives no retention, capacity, user/device limit, sharing, audit, export, deletion, or data-residency terms | | [[Van Buren Police Department]] | **Online/offline tier relationship unresolved** — VideoManager EL screenshots select `Online Video` and separately list `Offline archive` without showing its rules | Ordinance 30-2020 plus later asset reports and Policy 2.34; full storage contract not produced | Online categories run seven days to three years, while Policy 4.04 requires at least ten years across a broader MVR scope; see [[T045 - Van Buren Ten-Year MVR Policy vs Shorter VideoManager Retention Rules|T045]] | Benton County's statement is the corpus's only affirmative refusal of the cloud model, and it is the agency's own characterization rather than a contract term; no server architecture, retention rule, or device count accompanied it ([[Benton County SO Camera Locations and System Status]]). The Faulkner posture is the analytically sharpest of the four. The County did not buy cameras and separately buy storage; it bought **camera access as a subscription** in which the vendor holds the footage, the same structural move documented for plate readers in [[Flock Camera-as-a-Service Procurement Model]]. The contract's "unlimited cloud sharing" term means the sharing surface is a purchased capability, not an operational afterthought, which is why the total absence of any produced sharing record is a finding rather than an omission ([[T023 - Faulkner Closure-as-Fulfilled vs Unaddressed Request Categories]]). ## The ASP transition record ASP's record is lifecycle evidence rather than proof of current cloud operation. The May 7, 2025 solicitation-review memo says: > `"This procurement is to replace the existing in car camera system for the ASP Fleet. Current system is end of life (EOL) and server based. The new system is cloud based."` ([[ASP Cloud Fleet Camera Replacement Review Memo]], `SolicitationforReviewMemo_20260730203043.169_X 4600056398.pdf`, p. 1) The memo describes 700 in-car-camera systems—550 initial and 150 replacements—550 modems, and cloud storage, installation, and implementation services. Four produced equipment orders total the 550 initial systems, while PO `4502304706` orders `"Year 1 - Services"` and a `"VIDEO MANAGER EVIDENCE LIBRARY CLOUD SUBSCRIPTION"` for `$708,739.02` including tax ([[ASP 550-System In-Car Camera Purchase Orders 2025]]; [[ASP VideoManager Evidence Library Cloud Purchase Order]], `4502304706.pdf`, p. 1). Neither the memo nor the order establishes the migration date, operational go-live, retention schedule, storage capacity, sharing configuration, or system acceptance. ## The LRPD configuration in detail At LRPD, the digital-evidence cloud layer has two vendors: - **[[NICE Systems]] / NICE Investigate** — the long-term investigative-evidence retention layer (84 months / 7 years). - **[[Motorola Solutions]] / Motorola CommandCentral / VideoManager EL Cloud** — the shorter-term BWC/MVR video-storage layer. The two operate concurrently and the corpus shows them designed to integrate via the [[Fusus]] §2.2.4 cross-tag. ## How it appears in the corpus The [[sources/city-of-little-rock/CLR-2026-778/_overview|CLR-2026-778]] production documents both DEMS vendors at LRPD: | Vendor | Product | Authorization | Annual cost | Capacity | |---|---|---|---|---| | **NICE Systems** | NICE Investigate SaaS | MRA + Order 00479378 (2025-06-13) | **$100,000/yr** | 9,423 active cases; 84-month average retention; unlimited automatic transcription; geo-redundant US storage | | **Motorola Solutions** | VideoManager EL Cloud (within CommandCentral) | **Ord. 22,331 (2023-11-07)** sole-source emergency-clause ordinance | **$850,520 over Sept 2023 - Dec 2025** (Year 3 invoice $390,715) | ~557 devices under cloud-video subscription (300 + 150 + 107 across three tiers) | ## What's distinct about each vendor's offering | Dimension | NICE Investigate | Motorola VideoManager EL Cloud | |---|---|---| | Primary scope | Cases (investigations + courtroom evidence packages) | Devices (BWCs and MVRs uploading video) | | Retention | 84 months / 7 years average | (3-year cloud-storage contract under the iCloud sole source; per-device unlimited within the contract term) | | Auto-transcription | **Yes — unlimited, on ingestion** | (not documented in the corpus contract) | | Integration target | Fusus §2.2.4 cross-tag (RTCC) | Watchguard MVRs (hardware) + Motorola BWCs | | Data residency | Explicit US-only (geo-redundant Azure Government) | (not explicit in corpus contract) | | Corporate parent | NICE Ltd. (Israel) | Motorola Solutions, Inc. (USA) | ## The auto-transcription capability — a meaningful shift NICE Investigate's "unlimited automatic transcription — all playable video/audio will be transcribed upon ingestion" is a substantive capability change. Every BWC, MVR, 911 call, and field-interview audio recording LRPD ingests into NICE Investigate is auto-transcribed into text-searchable form. This converts a forensic asset (recorded audio/video, which historically required officer review to extract narrative content) into a structured-data asset (transcripts that can be keyword-searched at scale, fed into intelligence-analysis workflows like [[i2 Group]] Analyst's Notebook, or pre-staged for prosecutor disclosure). The corpus does not document downstream usage of the transcription output, but the capability is contracted for and available. ## CJIS-compliant cloud storage Both DEMS vendors host on cloud infrastructure with explicit **[[CJIS Compliance]]** representations: - **NICE Investigate** — Microsoft Azure Government Cloud; AES-256 encryption at rest; geo-redundant US storage. - **Motorola VideoManager EL Cloud** — CJIS-compliant infrastructure per Motorola standard terms. CJIS compliance is the federal standard for handling Criminal Justice Information; without it, neither vendor could host LRPD's data. ## RTCC integration — the operational hub [[NICE Investigate (MRA and Order 00479378)]] § 2.2.4 explicitly integrates NICE Investigate with the [[Fusus]] Real-Time Crime Center: > "evidence tagged with a case number in Fusus will be added to the matching case folder in NICE Investigate" (Tier-1 corpus, NICE Order 00479378, § 2.2.4) This is the load-bearing finding that converts the [[Real-Time Crime Center (RTCC)]] from vendor-pitched aspiration (Conway, Fayetteville) to operational reality (Little Rock). ## Stakeholders - **LRPD operators** of NICE Investigate (designated by Major [[Christna Plummer]] per the MRA notice provision). - **LRPD operators** of Motorola CommandCentral / VideoManager EL Cloud (BWC/MVR-equipped patrol officers; civilian video-evidence reviewers). - **ASP Fleet and Fiscal personnel** — [[Donna Williams]], [[Alan Johnson]], [[Jennifer Stallings]], and agency contact [[Jenna Castleberry]] appear on the produced replacement records. - **City of Little Rock procurement** ([[Lisa King]], [[Latreasa Mullins-Sanders]]). - **Vendor entities:** NICE Systems, Inc. (Hoboken NJ); Motorola Solutions, Inc. (Chicago IL). ## Timeline at LRPD - **2006:** LRPD-Motorola relationship begins (per Ord. 22,331 WHEREAS). - **2020:** LRPD begins BWC use; video initially stored on local City servers. - **2023-09:** Year 1 of the Motorola iCloud cloud-storage sole source begins ($104,400). - **2023-11-07:** Ord. 22,331 formalizes the Motorola iCloud sole source with emergency clause. - **2024-01:** Year 2 of the iCloud contract ($355,405). - **2025-01:** Year 3 of the iCloud contract ($390,715 — the actual invoice in the corpus). - **2025-06-13:** LRPD signs NICE Investigate MRA + Order 00479378. NICE Investigate goes live shortly thereafter. ## Timeline at ASP - **2023-2024:** ASP purchase orders document WatchGuard/Motorola 4RE Gen 2 equipment and VideoManager EL licensing for the legacy fleet-camera system. - **2025-05-07:** ASP signs the review memo describing the legacy system as end-of-life and server-based and the replacement as cloud-based. - **2025-06 through 2025-12:** Four Motorola orders list 550 initial in-car-camera systems and modems. - **2025-10-08:** ASP issues the produced Year-1 VideoManager Evidence Library cloud-subscription order. - **Unestablished:** delivery, installation, acceptance, migration, cutover, and current operational status. ## Notes - See [[NICE Systems]] for the corporate identity of the NICE Investigate vendor. - See [[Motorola Solutions]] for the corporate identity of the VideoManager EL Cloud vendor. - See [[Real-Time Crime Center (RTCC)]] for the operational integration target. - See [[Foreign-Headquartered Surveillance Vendors]] for the Israeli-parent context of NICE. - **The storage-posture split has a disclosure consequence.** Where video lives determines who can be asked for it. LRPD's and Faulkner County's footage sits with vendors under contracts the agencies signed; Benton County's sits on its own premises. Under [[Arkansas FOIA Electronic Records and Vendor Custody]], the vendor-hosted posture is the one that invites a custody objection, and Faulkner County's production supplies the pattern: the cloud contract was produced, and nothing describing what the cloud is configured to share was. - The two vendors' product overlap is *contractually distinct* — Motorola handles BWC/MVR per-device video; NICE handles per-case investigative evidence — but the operational boundary between the two systems is the cross-tag in the Fusus integration. A device-level BWC capture in VideoManager EL that becomes evidence in a case will likely be propagated to NICE Investigate via the Fusus tag. - See [[Surveillance Vendor Capture - Roadmap Influence]] for cross-jurisdictional context on the broader DEMS market. ## Van Buren budgetary CCDEMS proposal Motorola's July 2026 Van Buren quote proposes moving evidence for 57 V700 body cameras and 27 total M500 systems to CCDEMS Plus, with multi-user AI-assisted redaction. The `$569,573.32` quote is budgetary, and no executed order, payment, acceptance, or completed migration is produced ([[Van Buren Motorola Video Refresh and Redaction Quotes]]).