From the Public Safety edition of September 26, 2026
Cincinnati’s $360k ALPR replace/expand bid still opaque with eight unnamed companies
The Cincinnati Exchange · Independent local journalism · Cincinnati, Ohio, United States
- Publisher
- The Cincinnati Exchange
- Original publication
- September 26, 2026
- Source retrieved
- 2026-09-27
- Event date
- 2026-09-26
What happened
On Sept. 26, 2026, The Cincinnati Exchange reported Cincinnati set aside $360,000 from a $5.42 million public-safety package (Ordinance 290-2025, Sept. 17, 2025) to replace and expand police license plate readers under RFP265X901108 (posted Sept. 19, 2025; proposals due Oct. 21, 2025). A Jan. 22, 2026 City Manager Sheryl Long memo states evaluation scores were submitted and a corresponding request for a 90-day trial of the top three of eight respondents went up for approval—but “doesn’t say whether anyone approved that trial, and it doesn’t name a single company.” As of Sept. 25, DemandStar still listed the bid Under Evaluation (~339 days after proposal close). Council expects a surveillance technology presentation Oct. 6, 2026, under Motion 202602632 (adopted Sept. 10) seeking current deployment, retention, data-sharing agreements, and an ordinance for limits, annual reporting, use policy, and council approval of related contracts. Cincinnati’s current plate readers come from Axon; Axon also owns Fusus, platform for Connect Cincinnati private-camera aggregation; Fusus site says it doesn’t use facial recognition though software can flag weapons/vehicles of interest. Covington across the river approved a $6M Axon deal this month but left out ALPRs per WVXU cite. Article stresses visibility gap for taxpayers, not alleged impropriety.
Why it matters
Municipal policing ALPR procurement and surveillance-governance transparency—core public-safety, not fire/EMS.
Evidence and measured results
Same-day local records journalism citing City Manager memo, DemandStar listing, council motion, and WVXU context on Axon/Fusus stack.
Limitations and uncertainty
Does not name bidders or prove wrongdoing; trial may have occurred without public record found; Axon bid status unknown; Oct 6 presentation prospective.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-27; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A $360k ALPR replace/expand procurement has eight unnamed bidders, unclear trial status, and an upcoming council surveillance briefing that may impose new approval rules.
- Stakeholders
- City Council
- City Manager
- CPD command / tech
- Purchasing
- Residents / transparency advocates
- Discovery questions
- Will finalists and scores be published before award?
- Did the 90-day top-three trial run, and what did it measure?
- Will ALPR award wait for the proposed council-approval ordinance?
- How is Axon ALPR evaluation separated from Fusus private-camera dependency?
- Value hypothesis
- Bounded value is transparent evaluation and sequenced governance before spending the $360k—not faster camera install.
- Potential engagement
- 4–6 week procurement transparency assist: public scorecard template, trial metrics design, Oct 6 briefing pack, ordinance sequencing plan.
- Unsupported claims
- That any named vendor has won
- Guaranteed violent-crime reductions from ALPR expansion
- That Fusus performs facial recognition despite published denial
Pre-sales engineering
Role takeaway
- Fit
- Municipal ALPR RFPs stuck Under Evaluation with incumbent bodycam/ALPR/private-camera platform adjacency.
- Architecture and integration
- RFP score matrix → optional field trial telemetry → public shortlist publish → retention/sharing config → council packet.
- Prerequisites
- Evaluation criteria published
- Trial success metrics
- Data-sharing inventory for Oct 6
- Separation of ALPR vs Fusus decision objects
- Constraints
- 339+ days since proposal close
- Bidder identities withheld to date
- Prospective ordinance may change approval path
- Security
- Require retention/sharing answers and MFA/audit commitments in award conditions before go-live.
- Proof of value
- Named finalists published
- Trial metrics reported
- Oct 6 packet includes ALPR sharing map
Delivery
Role takeaway
- Work
- Clarify trial status, prepare Oct 6 materials, sequence award vs ordinance, communicate visibility commitments.
- Dependencies
- Purchasing records release path
- CPD operational requirements
- Law department ordinance draft
- Ownership
- City Manager with CPD tech co-owner; Council owns ordinance timing.
- Skills and adoption
- Brief council on ALPR vs private-camera platform distinctions; train PIO on what can be disclosed pre-award.
- Governance checkpoints
- Oct 6 presentation
- Public evaluation summary
- Award-or-wait decision relative to ordinance
- Acceptance criteria
- Trial status documented
- Shortlist or award rationale public
- Sharing/retention answers in packet
- Risks
- Award before council approval rules
- Continued unnamed-bidder opacity
- Platform lock-in via Fusus adjacency
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
ALPR procurements sitting Under Evaluation for many months need public scorecards, named finalists, and defined trial measures before award—especially when the incumbent also owns the private-camera aggregation platform.
Governance
Who approves, reviews and stays accountable for outcomes?
Oct 6 surveillance presentation and proposed council-approval-of-contracts ordinance could arrive after or before ALPR award—sequencing is a governance risk called out by the article.
Security and privacy
What data, permissions and controls need testing?
Axon ALPR + Fusus private-camera aggregation concentrates vendor surface; FR denial sits beside object-flagging features that still expand video analytics.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Council and public need plain-language trial and sharing explanations; purchasing needs capacity to release evaluation summaries.
Procurement
What should contracts, pricing and exit terms secure?
Condition ALPR award on published shortlist/trial outcomes and alignment with forthcoming council contract-approval rules.
Operating model
Which teams own the service once it runs?
Treat surveillance package line items as politically coupled—ALPR, drones, private-camera aggregation need one governance calendar.
Publication history
- 2026-09-26Public Safety · Issue 204 resources
Stable resource ID: cincinnati-exchange-alpr-bids-20260926