Lake Stevens staff ask council to approve OpenGov asset‑management system; $131,000 budget amendment proposed

Laurie Erickson, a public‑works analyst, asked the Lake Stevens City Council on Saturday to approve a move from the city’s legacy asset‑management software to OpenGov’s enterprise asset management platform, saying the current system requires repeated manual work and does not update the city’s GIS as crews work in the field.

“I think we have really reached the brink of what we can do with the current system,” Erickson said during her presentation, summarizing a ten‑month review that tested several vendors and conducted hands‑on demonstrations with front‑line staff. She told council the OpenGov product would let crews update asset attributes in the field, show an asset’s complete maintenance history, and include risk and remaining‑life scoring to support capital planning and preventive maintenance.

Public‑works director Aaron Halverson framed the change as an efficiency and risk‑management step. “Before asking for more people, let’s optimize the people we have,” he said, describing features that would let supervisors see nearby work orders assigned to other crews and quickly redeploy staff.

Staff documented several problems with the current platform, ViewWorks, including slow network responses, inability to write data back to the city GIS, and limited mobile visibility (workers can see only their assigned work orders on the phone). Those limits force supervisors to recheck entries and often to call crews back to re‑upload photos or data, Erickson said.

OpenGov, the recommended replacement, showed higher user scores in the city’s evaluations and would centralize asset, work‑order and inventory data. Erickson and Halverson said the city could expect better preventive‑maintenance scheduling, reduced reactive repairs and modest inventory savings as a result. Staff used conservative estimates and calculated an operational‑efficiency benefit roughly equivalent to 1 FTE in additional productive time; recurring inventory savings were projected at about 2% of the department inventory budget.

The financial ask is a one‑time implementation professional‑services fee (data migration, workflow building and initial training) of roughly $85,000, plus higher subscription costs in year‑one and subsequent years compared with the city’s current vendor. Staff estimated the total near‑term amendment needed at about $131,000 to cover implementation and the first‑year subscription delta; annual subscription increases thereafter were described as modest.

Erickson emphasized the vendor’s quote is time‑sensitive: OpenGov held 2025 pricing for a short extension and staff said delaying the decision would likely raise subscription costs for 2026. The council did not take a vote at the retreat; staff asked for a consensus to bring a formal budget amendment to the regular council meeting on Feb. 17 and to proceed with a vendor contract if council authorizes the mayor to sign.

What’s next: staff will return Feb. 17 with the formal budget amendment and a funding plan that identifies offsetting operating savings or capital adjustments. If council approves, staff expects to begin implementation in March and complete migration by late summer.

Provenance: Staff presentation and Q&A at the council retreat (topic introduced SEG 9090, continued through SEG 9960).