Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Asset Management topic

No spam. Unsubscribe anytime.

Cambria board approves OpenGov asset-management contract after public scrutiny

Cambria Community Services District Board of Directors · February 17, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The Cambria Community Services District board authorized a five-year agreement with OpenGov for asset-management software, citing potential savings and improved maintenance tracking; some public commenters urged broader vendor comparison and raised procurement concerns before the 3–1 approval.

The Cambria Community Services District board voted to authorize General Manager McElhaney to enter an agreement with OpenGov for an enterprise asset-management and preventive‑maintenance system, a move staff said would centralize equipment records and help avoid costly reactive repairs.

OpenGov account executive Andrew Wooters and regional manager Brandon Cook told the board the platform would track assets, schedule preventative maintenance, and provide scenario planning to prioritize capital investments. “When we think about moving from reactive to proactive work, it’s a huge initiative,” Cook said during the presentation. Staff said the software could also support FEMA reimbursement claims by documenting asset condition before and after storms.

The board and staff framed the contract as an investment intended to reduce emergency repairs, save staff time and improve long‑term budgeting. General Manager McElhaney said the district has experienced repeated infrastructure failures and lacks a single system of record: “This is an area where our institutional knowledge has been the primary mechanism, and that leaves gaps when people leave,” he said.

Public commenters and at least one director urged more competitive vetting. Tina Dickerson read reporting about a San Francisco procurement controversy involving OpenGov and asked whether the district had compared alternatives. “This needs to be more thought out,” she said, urging further homework before authorizing the district to proceed.

OpenGov and staff responded that district staff had evaluated multiple vendors and that the company’s offering for small jurisdictions—an unlimited user model and combined asset/financial tools—matched the district’s needs. OpenGov said the contract includes termination for non‑appropriation and that annual price increases are customary; Cook told the board to expect roughly a 5% year‑over‑year increase after the initial term.

Director Thomas moved to authorize the agreement and Director Gray seconded. The roll call recorded three ayes and one no from Board President Farmer; Vice President Dean was not present for the vote. The board recorded the contract as approved and directed the general manager to finalize the agreement.

Next steps include contract execution and an implementation timeline, during which staff and the vendor will plan training, configuration and on‑site support. Staff said they will present details about exit clauses and long‑term costs as they finalize terms.