Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Asset Management topic
No spam. Unsubscribe anytime.
Board approves OpenGov asset‑management agreement after public and board questions
Summary
The Cambria Community Services District board authorized the general manager to enter a five‑year agreement with OpenGov for an asset‑management and maintenance system after staff and OpenGov answered questions on costs, exit rights and expected savings.
The Cambria Community Services District board on Feb. 12 voted to authorize the general manager to sign an agreement with OpenGov for an enterprise asset‑management and computerized maintenance system.
The board’s approval followed a presentation from OpenGov account executive Andrew Wooters and regional manager Brandon Cook, who described the product as a single system of record for assets, work orders, preventative maintenance, resource tracking and scenario‑based capital planning. "We follow an unlimited user model," Wooters said, describing the software licensing and implementation approach.
General Manager McElhaney and utilities staff argued the system would help the district move from reactive to proactive maintenance and capture labor and materials costs now spread across multiple records. McElhaney told the board the district had lost potential FEMA reimbursements in the past because it lacked contemporaneous asset documentation; OpenGov representatives said their platform would help preserve evidence for future claims.
Board members and public speakers pressed staff and OpenGov on contract length, cancellation terms and long‑term cost. Director Thomas moved the agreement; Director Gray seconded. During the roll call, Director Thomas and Director Scott recorded votes in favor; President Farmer voted no. Staff and OpenGov said the contract allows termination for non‑appropriation and that year‑over‑year increases follow a standard schedule.
Several residents urged caution and recommended competitive procurement and further vetting of vendors before large technology purchases. "This needs to be more thought out," public commenter Tina Dickerson told the board, citing news about procurement controversies elsewhere.
The board approved the contract and directed staff to finalize implementation steps, including training and staging timelines. Staff said they will allot implementation responsibilities across department managers—fire, utilities and facilities—and that the vendor will provide on‑site training to support staff uptake.
Next steps: staff will return with a schedule for configuration, training and a proposed implementation timeline for the software roll‑out.
