Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Public Safety Data Contracts topic
No spam. Unsubscribe anytime.
Chickasha council approves updated LexisNexis crime-analytics contract amid privacy and accuracy concerns
Summary
The Chickasha City Council approved a 36-month update to its crime analytics contract with LexisNexis that raises the city's annual fee; police officials said the change addresses data-translation problems after a prior vendor split, while some council members expressed concern about scope and citizen privacy.
The Chickasha City Council voted to accept an update to the city's crime-analytics module contract with LexisNexis, approving a three-year agreement that raises the city's initial annual payment from about $2,500 to $4,100 with scheduled increases in later years.
Police officials told the council the update is necessary after the department's prior analytics arrangement through Motorola/Spillman fractured and produced inconsistent reports. The police chief said staff found the department was contributing both RMS and CAD data and that translating those data sets requires an additional $1,600 annually, which drove the new Schedule A price.
Council members pressed for details about the vendor's data collection and scope. Councilmember Charlie asked whether the city had previously been protected under a contract and raised concerns about the vendor being "in the data collection business" beyond what citizens might expect. The chief responded that the city had used an analytics module integrated with Spillman Motorola since 2020 and that a later split between Motorola/Spillman and LexisNexis left the city with inconsistent analytics output.
The chief described operational problems that prompted the change: he said the city could run the same report on different days and get different numbers, a problem that affected grant accounting and federal reporting. City staff told the council LexisNexis engineers identified the need for a new contract to translate both RMS and CAD feeds correctly.
A motion to accept the update carried in roll call; one council member voted no and one abstention was recorded in related later votes. Council members who voted in favor indicated they wanted to ensure continuity of analytics while also pressing for clear documentation on what data the vendor processes and how it is used.
The council did not adopt any new data-use policy as part of the vote. The update approved the revised Schedule A pricing and the multi-year term; staff said the item represented an increase over the city's previously discounted rate, and that price increases reflect the technical work LexisNexis must do to ingest both CAD and RMS data.
Council members asked staff to track ongoing costs and to provide clearer documentation of what the city shares with the vendor and how analytics outputs are produced.
Notes: The council discussion referenced the earlier Motorola/Spillman analytics arrangement and an April 30 drop-dead date previously given by Motorola; the chief said the prior product produced inconsistent analytics. The vote record in the transcript shows a majority approval with one recorded no vote.
