# NICE Investigate (MRA and Order 00479378) The pair of 2025-06-13 documents that establishes LRPD's adoption of **NICE Investigate**, a cloud-based digital-evidence-management (DEMS) platform with **unlimited automatic transcription** of all playable video and audio at ingestion, **geo-redundant US storage**, and an explicit **integration with the LRPD [[Fusus]] Real-Time Crime Center**. The agreement is the single most expensive software subscription in the [[CLR-2026-778]] corpus ($100,000 per year, year-over-year, with 84-month average retention). ## What's inside - **`NICE/2025.06.13 NICE Systems Inc. Master Relationship Agreement - FULLY EXECUTED.pdf`** — the framework MRA between NICE Systems, Inc. (Hoboken, NJ) and the City of Little Rock. 39,834 bytes extracted text; ~30 pages. - **`NICE/2025.06.13 NICE Systems Inc. Order 00479378 with Exhibits and Attachments - FULLY EXECUTED.pdf`** — Order No. 00479378, the substantive purchase, with the Statement of Work (SOW), the Cloud Services Exhibit (Exhibit A: Maintenance Windows, Support Matrix, Severity Levels), and the schedule. ## Key takeaways ### Money and capacity - **$100,000 annual fee** (Year 1 fixed) for the NICE Investigate SaaS Solution. - **Initial Subscription Term: 12 months** beginning on the Initiation Date. - **9,423 active-case capacity** in the bundled tier; additional active cases beyond 9,423 are billed at **$15 per case per year**; archived cases beyond bundled capacity at **$3 per case per year**. - **84-month average retention** — cases remain in the system for ~7 years (assuming the customer signs renewals) before permanent removal. ### Capability - **Unlimited automatic transcription** — "all playable video/audio will be transcribed upon ingestion." This is a substantive capability change for LRPD: every body-worn-camera (BWC), in-car-video (MVR), and 911 call ingested into NICE Investigate is automatically transcribed. - **Advanced evidence-redaction tools** (Tier-1 corpus, SOW Attachment 1). - **Geo-redundant storage** for all digital evidence related to cases. - **AES-256 encryption at rest** (Tier-1 corpus). - **CJIS-compliant cloud storage** (relevant to [[CJIS Compliance]]). - **Severity-tiered 24×7 support** — S1 (System Unavailable) targets 60-minute initial response; S2 (System Impaired) targets 4-hour response during the customer's business day; S3 and S4 next business day. ### Integration - **§2.2.4 — Fusus integration.** The Order's Statement of Work 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.) - **Customer-system integrations** named in the SOW: Little Rock RMS (records management), Motorola PremierOne CAD (computer-aided dispatch), Watchguard BWC (body-worn cameras), Prosecutor-by-Karpel (prosecutor case management), and Fusus. ### Data residency — explicit US In contrast to the [[Cellebrite Advanced Services Agreement]] §10.3 (which permits cross-border data transfer), NICE Investigate storage is **explicitly US-resident**. The Order specifies geo-redundant storage within the USA and CJIS-compliant Microsoft Azure Government infrastructure. ### Press-release / marketing-quote clause (§1.3) The Order obligates the customer to assist in producing promotional material: > "Customer shall reasonably assist NICE to develop: (i) a NICE press release stating that Customer has elected to employ the Investigate SaaS Solution for its digital investigation and evidence management software; and (ii) case studies (requiring a single phone call) to demonstrate the benefits derived by use of the Investigate SaaS Solution." (Tier-1 corpus, [[CLR-2026-778]], Order 00479378, §1.3) Routine for enterprise SaaS but worth recording: the City has contracted to produce vendor-marketing material as part of the deal. ### AI-restriction clause (MRA §3.4) The MRA prohibits the customer from using "any generative artificial intelligence or any other machine-based learning application" to "model, replicate, or emulate the functionality, design, or any other aspect of the Services or Software." (Tier-1 corpus, MRA §3.4.) This is the first explicit AI-restriction clause in a corpus FOIA contract; the broader trend in surveillance procurement merits tracking. ### Export-control clause (MRA §7.2) The MRA requires customer compliance with US export laws and prohibits export "to any country subject to an embargo or other sanction by the United States, including the Crimea, Luhansk or Donetsk regions, Cuba, Iran, North Korea, or Syria." (Tier-1 corpus.) The denied-party clause language is standard but notable here because NICE Ltd. (parent) is Israeli and the City has agreed to abide by the same US-export framework even though the operational data does not appear to cross any border. ## Verbatim citations > "1.1 NICE Investigate SaaS Solution ('Investigate SaaS Solution') as further described in the SOW… 1.2 NICE Investigate SaaS fee includes: Unlimited geo-redundant storage for all digital evidence related to cases. Unlimited automatic transcription - all playable video/audio will be transcribed upon ingestion. Advanced evidence redaction tools. Case capacity as follows: Active Cases 9,423 / Archived Cases / Deleted Cases / Total Managed Cases 9,423 / 1 Year Commitment $100,000" (Tier-1 corpus, Order 00479378, §§1.1–1.2) > "Cases Stay Active for 12 months (average). Cases remain in the system for 84 months (average) before being permanently removed assuming customer signs additional year 2-5 contract." (Tier-1 corpus, same) > "evidence tagged with a case number in Fusus will be added to the matching case folder in NICE Investigate" (Tier-1 corpus, same, §2.2.4) > "NICE was founded on September 28, 1986, as Neptune Intelligent Computer Engineering Ltd." (Tier-2 contextualization, NICE FY2024 20-F, [archived 2026-06-05](../../../../web%20archive/2026-06-05/sec.gov/nice-20f-2024-nice-20241231.md)) > "Our subsidiary, NICE Systems, Inc. has been appointed as our Agent for Service in the United States, and is located at 221 River Street, Hoboken, New Jersey 07030." (primary public record, same) > "Customer shall reasonably assist NICE to develop: (i) a NICE press release stating that Customer has elected to employ the Investigate SaaS Solution… and (ii) case studies." (Tier-1 corpus, Order 00479378, §1.3) ## People and orgs mentioned - **[[Christna Plummer]]** — LRPD Major; named the **Notice** contact on the MRA, with email `[email protected]`. (Spelling "Christna" per the document.) - **[[Latreasa Mullins-Sanders]]** — LRPD Administrative Services Finance Manager; routed the procurement on the LRPD side. - **[[NICE Systems]]** — vendor (NICE Systems, Inc., Hoboken NJ — the contracting US subsidiary of NICE Ltd., Ra'anana, Israel). ## Concepts invoked - [[Digital Evidence Management Cloud]] — the product class (DEMS). - [[CJIS Compliance]] — the federal criminal-justice information standard. - [[Real-Time Crime Center (RTCC)]] — the integration target for the Fusus §2.2.4 link. - [[Foreign-Headquartered Surveillance Vendors]] — the Israeli corporate-identity context. ## Events documented - [[2025-06 Little Rock Adopts NICE Investigate Evidence Platform]] — the procurement event. ## Cross-references - [[NICE Systems]] — vendor org page; full corporate-identity context. - [[Fusus]] — the RTCC platform that NICE Investigate cross-tags with (§2.2.4). - [[Competing ALPR Vendors and the Real-Time Crime Center]] — synthesis essay; LRPD's NICE Investigate is the post-incident evidence layer of the operational RTCC the synthesis essay anticipates. ## Open questions / follow-ups - **Whether the 9,423-case capacity has been exceeded.** Not in the production. The City's bundled tier is comfortably above the typical 7-year retention envelope, but a successor FOIA could surface actual case-volume data. - **Whether the transcription is reviewed.** The unlimited-automatic-transcription clause produces text-searchable records of every recorded audio/video event LRPD ingests; whether these transcriptions are reviewed for accuracy before evidentiary use is a procedural question not addressed in this contract. - **What "evidence tagged with a case number in Fusus" actually means in practice.** The §2.2.4 cross-tag is documented but its operational frequency is not. LRPD audit logs of NICE-Fusus cross-tagging events would clarify. - **The volume of LRPD audio/video being ingested.** With ~557 BWC/MVR devices on the Motorola Watchguard side (per the [[CLR-2026-778]] iCloud Quote 2064723) plus 1500+ Fusus camera feeds plus 115 Flock LPR feeds, the daily ingestion volume is potentially substantial. Not documented in the production.