Seal Beach council hears plan to refresh city parking LPR technology; vendor chosen previously, no vote recorded
Loading...
Summary
Kevin Edwards, the city’s information technology manager, told the Seal Beach City Council on Feb. 24 that staff plans to refresh the city’s aging parking license-plate-recognition (LPR) hardware and software that support parking enforcement and related services.
Kevin Edwards, the city’s information technology manager, told the Seal Beach City Council on Feb. 24 that staff plans to refresh the city’s aging parking license-plate-recognition (LPR) hardware and software that support parking enforcement and related services.
Edwards said the system ties together multiple vendor products — mobile data terminals, handheld devices, vehicle-mounted LPR cameras, pay stations and in-house servers — and that “this is one of the more complex deployments in our city.” He said some equipment is at end of life and maintenance is harder because components come from different manufacturers.
The refresh targets equipment in six vehicles. Edwards said the council previously approved an allocation of about $242,000 for the project. Lieutenant Hendricks, who helped with the city’s RFP, told the council the selected distributor, ComSonics, submitted a proposal “just under $215,000,” which staff said would leave roughly $30,000 of the original allocation unspent.
Why it matters
City staff said failures of older LPR equipment have reduced efficiency, risked parking revenue and interrupted services that rely on the system, including animal control functions that use the same cameras. Edwards and Hendricks described the refresh as both a maintenance and a public-safety issue because modern LPR can inform stolen-vehicle and missing-person checks when properly integrated.
System scope and security
Edwards described multiple data flows and said criminal-justice information is protected. He told the council the police LPR system and the city’s parking LPR system are separate: “The LPRs associated with policing are completely different than the ones associated with parking” and the policing system has higher retention and access controls, Edwards said. He added that parking enforcement data are encrypted and that some police-related standards — he referenced CJIS procedures — govern how certain data are handled.
On operational questions, Edwards said the time from a permit being entered at a pay station to enforcement recognition should be “in worst case scenario no more than 10 to 15 seconds.” He said the city is negotiating with a vendor to allow earlier detection of parking violations so that staff could be flagged before an enforcement officer drives to a lot.
Vendor history
Lieutenant Hendricks reviewed earlier vendor experience: Seal Beach previously used systems from Motorola and Genetec; Motorola did not meet the city’s needs and Genetec-based systems were selected earlier. Hendricks said the city solicited bids from three Genetec distributors and selected ComSonics as the most cost-effective choice that offered coverage and support and that ComSonics reported it negotiated with Genetec to lower equipment costs.
Budget and next steps
Staff said the approved fiscal allocation is approximately $242,000 and ComSonics’ proposal came in below that number; staff said recurring maintenance could be added to the police department budget and that some future maintenance could be funded from annual parking revenue. No formal council vote on vendor award or contract terms is recorded in the meeting transcript; councilmembers asked technical and policy questions during the presentation.
Council questions and public-safety notes
Council members asked whether the parking LPR could detect stolen vehicles or trigger Amber Alerts. Edwards said he has integrated the parking system into the stolen-vehicle and missing-person databases so a hit can be flagged for dispatch to verify, and he emphasized verification steps before law-enforcement action: “We have a number of steps in process, both visually and through the system, to verify that information before we turn on our lights and potentially engage.”
What remains open
Staff did not present a contract or motion for council approval during the item; the presentation detailed the technical rationale, budget numbers and vendor-selection rationale and staff said it would bring procurement documents forward as required. The transcript includes no formal motion or recorded vote approving a contract at this meeting.
Ending
Staff recommended the refresh to maintain enforcement efficiency and public-safety integrations; council members asked technical and privacy questions and heard that the proposal is under the current budget allocation. Staff said they would return with procurement documents and contract language if the project proceeds to award.

