{"resourceId":"quincy-ma-deactivates-flock-moves-to-city-owned-axis-odineye-alpr-20261023","versions":[{"version":"external-4ad16f46af6db17c7700927528a6f505d0009924756cbdebe4c8762aded8cd2f","resource":{"id":"quincy-ma-deactivates-flock-moves-to-city-owned-axis-odineye-alpr-20261023","title":"Quincy, Mass., deactivates Flock plate readers and moves to a city-owned Axis Communications and OdinEye system, keeping 14-day data deletion","organization":"City of Quincy and Quincy Police Department (Massachusetts)","sector":"Policing / ALPR","geography":"Quincy, Massachusetts, U.S.","publishedAt":"Oct. 23, 2026, 12:59 PM (city news release)","publicationDate":"2026-10-23","eventDate":"2026-10-23","sourceName":"City of Quincy","sourceLabel":"Quincy Police to Change Plate Reader Technology","sourceUrl":"https://www.quincyma.gov/news_detail_T35_R339.php","evidenceClass":"standards-guidance","outcomeClass":"mixed","topics":["governance-procurement","data-security","infrastructure"],"finding":"Mayor Tom Koch and Police Chief Mark Kennedy announced on Oct. 23 that the police department has deactivated its Flock Safety ALPR system and will move to Axis Communications cameras integrated with OdinEye software, which the city says will let the department keep sole ownership of the data. Existing policies remain: searches only for active criminal cases, limited users and deletion of all data within 14 days. The mayor called it a good-faith balance between investigative value and residents’ concerns about Flock; both officials said the cameras capture plates and vehicles, not faces. WCVB’s report of the announcement carries a version of the mayor’s quote that also cites City Councilors’ concerns and says at least 18 Massachusetts municipalities have quit Flock.","sledRelevance":"Resolves a follow-up from earlier editions and shows the most common response to ALPR backlash: change vendor and ownership model rather than end plate reading.","evidence":"Opened the city news release (primary) and the WCVB report of the same announcement for context.","architectureImplications":"Shift from a vendor-hosted network to city-owned cameras and software; system integration and hosting details are not given.","governanceImplications":"Use limits (active cases, limited users, 14-day deletion) are department policy, not ordinance.","securityPrivacyImplications":"City claims sole data ownership under the new system; no audit results or sharing rules are published in the release.","caveats":"Government announcement, not an evaluation; no cost, timeline, effectiveness data or independent audit; residents’ groups’ response not reported in the release.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Quincy shows that the sale after a Flock exit is often a replacement, not an end to plate reading. The customer problem is keeping an investigative tool while answering ownership and sharing concerns. A bounded engagement could compare ownership, retention and sharing controls across replacement options. The release cannot support claims that city-owned systems resolve privacy objections, that the change saves money, or that the new system is more effective.","engineering":"Engineering framing: moving from a vendor network to agency-owned cameras changes the architecture: hosting, access control, audit logging and any sharing must now be built or configured locally. Pre-sales should check where OdinEye-type software runs, how 14-day deletion is enforced technically and whether search logs capture case numbers. Proof of value should verify automated deletion and log completeness, since the release states policies but no audit evidence.","delivery":"Delivery framing: the transition needs camera replacement, software deployment, policy carry-over and decommissioning of the old system, including confirming Flock data deletion. Dependencies are procurement, network and hosting capacity, and a written policy. The operational owner is the police department. Acceptance should include verified deletion at 14 days and a published audit. Risks are that residents view the change as cosmetic and that cost and timeline are not yet public."},"roleDetails":{"sales":{"customerProblem":"A police department wants to keep plate reading while answering resident concerns about a vendor-run network.","stakeholders":["Mayor and police chief","City Council","City IT","Residents’ groups"],"discoveryQuestions":["Who will host and administer the new system?","How is 14-day deletion enforced and verified?","Will any data be shared outside the city?"],"valueHypothesis":"A city-owned system with verified deletion and logged searches may address ownership concerns, if audits are published.","potentialEngagement":"Four-to-six week replacement options review comparing ownership, retention enforcement and sharing controls.","unsupportedClaims":["That city ownership resolves privacy objections","Cost savings","Improved investigative outcomes"]},"engineering":{"fit":"Cities replacing vendor-network ALPR with agency-owned systems.","architectureIntegration":"Agency-owned cameras feed locally administered software with role-based search and automated deletion.","prerequisites":["Hosting capacity","Access-control design","Written ALPR policy"],"constraints":["Release gives no technical details","Massachusetts legal context","Old-system data deletion must be confirmed"],"security":"Enforce deletion technically, log all searches with case numbers and restrict administrator access.","proofOfValue":["Proposed: verify automated 14-day deletion","Proposed: test that every search is logged with a case reference"]},"delivery":{"work":"Replace cameras, deploy software, carry over policy and decommission Flock.","dependencies":["Procurement","Network and hosting","Policy update"],"ownership":"Quincy Police Department","skillsAdoption":"Train users and auditors on the new system and policy.","governanceCheckpoints":["Confirmation of Flock data deletion","Go-live policy review","First audit report"],"acceptanceCriteria":["Proposed: no data retained beyond 14 days in sampled audit","Proposed: published audit within six months of go-live"],"risks":["Perceived as vendor swap only","Undisclosed cost","Transition gaps in coverage"]}},"retrievedAt":"2026-10-24T02:56:34Z","enrichedAt":"2026-10-24T03:03:04Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Not addressed.","procurementImplications":"Cost, contract terms and timing of the Axis/OdinEye transition are not disclosed.","operatingModelImplications":"Executive decision in response to a nonbinding council resolution; council role in the replacement is not described.","sourceVerification":{"openedUrl":"https://www.quincyma.gov/news_detail_T35_R339.php","referenceExcerpt":"limiting the personnel allowed to use the system, and wiping all data within 14 days will remain in place.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}