# SoundThinking / ShotSpotter and CaseBuilder Correspondence This page collects the SoundThinking (formerly ShotSpotter) correspondence that surfaced inside LRPD's Flock-keyword production PDFOI-2026-1874. SoundThinking is a gunshot-detection and case-management vendor and is distinct from the ALPR vendors elsewhere in this production; its records appear here because the underlying FOIA request (The Markup's FOI #0481) asked for SoundThinking material alongside Flock and Axon, and because vendor newsletters and integration threads tripped the same keywords. The thread covers a January 2025 data-review exchange, a 2024 ShotSpotter-to-Motorola CAD integration that failed for weeks, an 8-month CaseBuilder proposal structured to align with the ShotSpotter contract, and marketing pushing SoundThinking's PlateRanger ALPR product. ## What's inside - A short January 31, 2025 "Follow up" thread between SoundThinking Customer Success Director Kerry Neumann and Lt. [[Courtney Bewley]], arranging a Zoom to review "data." - A 2024 ShotSpotter NAPI integration thread documenting alerts that failed to reach LRPD's Motorola PremierOne CAD endpoint, with SoundThinking, [[Motorola Solutions]], and LRPD personnel troubleshooting. - A page of ShotSpotter activation locations in Little Rock, logged inside the failed-alert troubleshooting (specific addresses present; not reproduced here). - A CaseBuilder procurement thread in which SoundThinking Sales Director Ken Peters revises the proposal to 8 months to make it coterminous with LRPD's ShotSpotter agreement. - A SoundThinking marketing newsletter promoting integration across ShotSpotter, PlateRanger, ResourceRouter, CrimeTracer, and CaseBuilder. ## Key takeaways **The January 2025 "Follow up" thread was a data-review Zoom, not a sales call.** On January 31, 2025, Neumann wrote to Bewley: "Good morning Lt, can you get on a zoom later this morning to review the data | have for you?" (Emails 1-24.pdf p. 1, "Good morning Lt, can you get on a zoom later this morning to review the data | have for you?"). The two exchanged availability across the morning; Bewley replied at 10:44 AM, "Okay. I'm going to try and grab lunch at 11 and then will be back in my office." (Emails 1-24.pdf p. 193, "Okay. I'm going to try and grab lunch at 11 and then will be back in my office."). The record states the meeting was to review unspecified "data" but does not, on these pages, define what data set was reviewed. **Kerry Neumann's role was customer-success / annual account review, framed explicitly as non-sales.** Describing the recurring ShotSpotter Annual Account Review, Neumann wrote: "The ShotSpotter Account Review is an in-person one-hour meeting where | will present a year in review and discuss new features in the ShotSpotter platform. This is not a sales meeting." (Emails 1-24.pdf p. 136, "This is not a sales meeting."). He listed intended attendees as "Chief Helton and the Executive Command Staff, RTCC Command, Patrol Commanders, Investigations Commanders, Gang/Gun/Firearms Investigators and Commanders, Crime Analyst, Dispatch Supervisor, PIO, City Manager, Mayor, etc." (Emails 1-24.pdf p. 136). **The ShotSpotter NAPI integration to Motorola PremierOne CAD failed for weeks in spring 2024.** SoundThinking support engineer Andrenikki Gordon opened the thread on April 30, 2024: "We have noticed several incidents that are not being sent to the endpoint for Motorola Premier One." (Emails 1-24.pdf p. 255, "We have noticed several incidents that are not being sent to the endpoint for Motorola Premier One."). The diagnostics show the connection itself was up but incidents were not arriving: "Telnet:2024-04-30T1 1:06:29-05:00External IP: 35.160.113.226Result: OK" and "The following incidents tried but failed to reach the endpoint:" (Emails 1-24.pdf p. 255). On May 3, 2024, SoundThinking's PJ Ramos escalated to a Motorola contact: "Heartbeat to endpoint is up ... But no incidents go through Can you assist?" (Emails 1-24.pdf p. 254, "Heartbeat to endpoint is up"). The record documents a multi-vendor integration (SoundThinking sensors, Motorola PremierOne CAD/RMS) that LRPD relied on but that was not reliably delivering ShotSpotter incidents to dispatch. **LRPD's own side could not fully troubleshoot the integration, and CAD IDs were missing.** Bewley, then a sergeant in the [[Real-Time Crime Center (RTCC)]], replied on May 3, 2024: "I am still new to taking over ShotSpotter on our end, but! solely work onthe PD side. | am not an admin on the PremierOne side of the house so | don't believe | can troubleshoot that aspect. | see several older alerts below and todays that don't show a CAD ID." (Emails 1-24.pdf p. 252, "I am not an admin on the PremierOne side of the house so | don't believe | can troubleshoot that aspect."). She added that when she searched the RMS for incidents SoundThinking had flagged, "even if there was a 'cad id' when | searched for it in our RMS system it told me that number did not exist." (Emails 1-24.pdf p. 252). **Specific Little Rock ShotSpotter activation addresses are logged in the production.** Within the failed-alert troubleshooting, the record reproduces a page listing several Little Rock street addresses paired with activation timestamps (Emails 1-24.pdf p. 253). The page documents the presence of specific residential-scale activation locations in Little Rock; the individual addresses are not reproduced here. Their presence shows that gunshot-detection activation points, at street granularity, were circulated by email during routine vendor troubleshooting. **The CaseBuilder proposal was deliberately shortened to 8 months to be coterminous with the ShotSpotter agreement.** SoundThinking Sales Director Ken Peters wrote to Bewley on April 1, 2024: "Attached is a revised proposal for 8 months which will allow the city to make the CaseBuilder amendment coterminous with the ShotSpotter agreement." (Emails 1-24.pdf p. 166, "Attached is a revised proposal for 8 months which will allow the city to make the CaseBuilder amendment coterminous with the ShotSpotter agreement."). The attachment is named "CaseBuilder Proposal for Little Rock, AR 020524 Rev 1.pdf" (Emails 1-24.pdf p. 166). Peters later referenced finalizing "a revised contract amendment that references the 8-month pricing and coterminous language" (Emails 1-24.pdf p. 164, "a revised contract amendment that references the 8-month pricing and coterminous language"). The structure ties a second SoundThinking product (CaseBuilder, case management) to the lifecycle of the existing ShotSpotter contract. **The CaseBuilder procurement stalled in the Chief's office, and Peters pressed for access while Bewley managed the relationship.** Bewley reported on April 19, 2024: "Not the best update. It has gotten tied up in the Chief's office again. | am waiting on the opportunity to speak with them directly. | would not recommend you contact the chief's office." (Emails 1-24.pdf p. 161, "It has gotten tied up in the Chief's office again."). Peters repeatedly asked who could sign and whether he should contact decision-makers directly: "If not, who do you recommend | contact. | won't reference you when | call him/her." (Emails 1-24.pdf p. 161, "I won't reference you when | call him/her."), and elsewhere, "A box of chocolates on the right desk often works!" (Emails 1-24.pdf p. 162, "A box of chocolates on the right desk often works!"). By April 25, 2024 the deal remained stalled: "No movement. It is in the chief's office. No further." (Emails 1-24.pdf p. 160, "No movement. It is in the chief's office. No further."). **SoundThinking marketed PlateRanger, its ALPR product, to LRPD alongside ShotSpotter.** A SoundThinking newsletter sent to LRPD's James Sloan on March 26, 2025 promoted "Proven LPR Integration in Your Real Time Crime Center" and a "ShotSpotter and PlateRanger Integration Demo video," closing with: "Integration is at the core of tools like PlateRanger, ShotSpotter, ResourceRouter, CrimeTracer and CaseBuilder, facilitated by an open API that enables seamless interoperability with external public safety systems." (Emails 1-24.pdf p. 234, "Integration is at the core of tools like PlateRanger, ShotSpotter, ResourceRouter, CrimeTracer and CaseBuilder"). This places a gunshot-detection vendor pitching an ALPR product into the same RTCC that runs Flock cameras, which is one reason this material tripped the Flock-keyword search. **A separate, more targeted PlateRanger pitch and an asset-forfeiture funding pitch also appear in the wider production (outside the chunk reviewed here).** The findings digest records that SoundThinking marketed PlateRanger to LRPD as a way to identify suspect vehicles without plate data, using physical descriptors (Emails 36-63.pdf p. 433-435, per digest; case study cited as a Jacksonville Sheriff's Office gang investigation). The digest also records a SoundThinking/ShotSpotter sales contact (named in the digest as Jack Pontious) suggesting agencies fund public-safety technology via leftover recruit salaries and asset forfeiture, referencing the State Homeland Security Grant Program (Emails 36-63.pdf p. 779, per digest). These two items were not in the chunk text reviewed for this page; the verbatim quotes were not independently re-verified here and should be confirmed against the cited pages before being treated as Tier-1. ## People and orgs mentioned - [[Courtney Bewley]] — LRPD; sergeant in the [[Real-Time Crime Center (RTCC)]] during the 2024 CaseBuilder and integration threads, later promoted to lieutenant (Technology & Equipment Unit) by January 2025 (Emails 1-24.pdf p. 1; p. 135, "I was recently promoted and moved back to patrol."). - [[Brittany Gunn]] — LRPD; identified as commander of the RTCC ("Major Gunn who is the commander of the RTCC") when Bewley handed off the SoundThinking relationship (Emails 1-24.pdf p. 135, "I have copied Major Gunn who is the commander of the RTCC."). - [[Heath Helton]] — LRPD Chief; named as an intended attendee of the ShotSpotter Annual Account Review and as a contact Neumann emailed on a survey follow-up (Emails 1-24.pdf p. 135-136). - [[Domikia Davis]] — LRPD police sergeant; the records custodian whose mailbox these messages were exported from and who processed The Markup's FOI #0481 (Emails 1-24.pdf p. 241, "Good evening, your FOI request has been processed."). - [[SoundThinking]] — vendor; personnel in this thread include Kerry Neumann (Customer Success Director), Ken Peters (Sales Director for CaseBuilder), Andrenikki "Nikki" Gordon (Technical Support Engineer), PJ Ramos (SoundThinking Support), Kenneth Peters, and Luke Wester (Emails 1-24.pdf pp. 134-136, 160-166, 230-235, 252-255). - [[Motorola Solutions]] — vendor; its PremierOne CAD is the destination endpoint for ShotSpotter incidents, and a Motorola contact ([email protected]) was added to the failed-alert thread (Emails 1-24.pdf p. 254). - The Markup (Anne Li) — requester behind FOI #0481, which sought LRPD correspondence with Flock, Axon, and SoundThinking (named here as plain text; Emails 1-24.pdf p. 242-243). ## Concepts invoked - [[Real-Time Crime Center (RTCC)]] — the LRPD unit that owned the SoundThinking relationship; both the CaseBuilder procurement and the integration troubleshooting ran through RTCC staff (Emails 1-24.pdf pp. 161, 252). - Gunshot detection to CAD integration — ShotSpotter's NAPI feed into Motorola PremierOne CAD as the operational link between sensor activations and dispatch (Emails 1-24.pdf p. 255). SoundThinking is gunshot-detection technology and is distinct from ALPR vendors in this production. - [[Cooperative Purchasing Vehicle]] — Flock purchases in the broader thread routed through Insight Public Sector; the CaseBuilder thread shows a parallel city procurement path through the Chief's office, Purchasing, and Legal (Emails 1-24.pdf p. 164, "It has been provided to the Chief's office and Purchasing. It will go to legal from there."). ## Events documented - 2024-04-01 to 2024-04-25 — CaseBuilder proposal revised to 8 months and routed through LRPD command and city procurement; deal stalled in the Chief's office (Emails 1-24.pdf pp. 160-166). - 2024-04-30 to 2024-05-03 — ShotSpotter NAPI alerts repeatedly fail to reach LRPD's Motorola PremierOne CAD endpoint; multi-vendor troubleshooting (Emails 1-24.pdf pp. 252-255). - 2024-11-06 to 2024-11-19 — Neumann seeks to schedule the ShotSpotter Annual Account Review; Bewley hands the relationship to Major Gunn after her promotion (Emails 1-24.pdf pp. 135-136). - 2025-01-31 — Neumann/Bewley "Follow up" Zoom to review data (Emails 1-24.pdf pp. 1, 193). - 2025-03-26 — SoundThinking newsletter to LRPD's James Sloan promoting PlateRanger LPR integration (Emails 1-24.pdf pp. 230-234). ## Cross-references - The Markup's FOI #0481, which pulled this SoundThinking material in alongside Flock and Axon, is documented in [[LRPD FOIA Handling and Disclosure Posture]] and [[Flock-Axon API Dispute and the Dual RTCC Stack]]. - A separate City of Little Rock ShotSpotter procurement record set is tracked under FOIA reference CLR-2026-778 (ShotSpotter procurement); it is referenced here as plain text and is not part of PDFOI-2026-1874. - The Flock "Raven" product's dependence on a Motorola Command Central Aware integration ("Raven: you need for a call to be generated from an alert which is contingent on an integration with Command Central Aware," Emails 1-24.pdf p. 191) is a separate Flock-Motorola integration and is distinct from the ShotSpotter-PremierOne integration above; see [[Flock LPR Deployment Expansion and Permitting Delays]]. Do not conflate the two. ## Open questions / follow-ups - What "data" did Neumann review with Bewley on the January 31, 2025 Zoom? The pages establish the meeting occurred but do not identify the data set. - Were the failed April-May 2024 ShotSpotter incidents ultimately resent and delivered to PremierOne, and how many activations were affected? The production shows the failure and the offer to resend ("Would you like us to resend these incidents?", Emails 1-24.pdf p. 255) but not the resolution. - Was the 8-month CaseBuilder amendment ever executed by the City of Little Rock? The thread ends with the deal stalled in the Chief's office; no executed amendment is in this production. - The asset-forfeiture funding pitch and the targeted PlateRanger "identify vehicles without plate data" pitch are documented in the findings digest at Emails 36-63.pdf p. 779 and p. 433-435 but were not in the chunk reviewed here; their verbatim quotes need confirmation against those pages before being cited as Tier-1.