Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Municipal Technology topic
No spam. Unsubscribe anytime.
Lake Stevens Council authorizes $333,570 OpenGov contract to replace legacy asset systems
Summary
The council authorized the mayor to sign a $333,570.02 contract with OpenGov to consolidate multiple asset‑management tools. Staff said the move could save about $130,000 annually in labor but requires a one‑time funding gap of roughly $103,000 split across parks, stormwater and streets budgets.
Lake Stevens City Council on a voice vote authorized the mayor to sign an agreement with OpenGov, a cloud platform the city plans to use to replace several current asset‑management systems.
Lori Erickson, the city’s public works analyst, told council the three‑year, nine‑month agreement quoted on 2025 pricing totals $333,570.02 and would first implement an asset‑management module before adding financial, inventory, fleet and facilities modules. "The ask coming into tonight's session was really for us to take a look at possible funding sources," Erickson said, adding the contract quote is valid only through the end of the month.
Council members and staff focused discussion on how to cover a roughly $102,000–$103,000 year‑one funding gap without tapping city reserves. Erickson proposed splitting the shortfall equally among the parks, stormwater and streets operating budgets—about $34,000 from each—so the council would not need a separate budget amendment.
Staff described the tradeoffs those reductions would create: parks would defer one larger or unforeseen capital project, stormwater would reduce aquatic vegetation maintenance area and the streets division would postpone about $34,000 of pavement preservation work (examples given were short lane‑width segments of repair). Erickson said the city expects a period of overlap with legacy systems for up to six months while OpenGov is implemented; Viewworks would remain active until wound down.
On efficiency, staff estimated OpenGov’s integrated tools and workflow visibility could free roughly $130,000 per year in labor—"soft cost" savings that Erickson said would translate into more time for crews to do field work rather than fight disjointed systems.
A council member moved to authorize the mayor to sign the agreement; after a second, the motion passed by voice vote. The transcript records the motion as: "I move to authorize the mayor to sign the agreement with OpenGov." The mayor will sign the contract following council authorization.
City staff said they will develop a communication plan for residents to prepare for the switch and that the IT director has procured a six‑month continuation of key legacy services to cover the implementation window.
The council did not record a roll‑call tally in the transcript; staff described the vote as a successful voice vote. The council also directed staff to proceed with implementation planning and public outreach.
Next steps: the mayor will sign the agreement and staff will begin implementation activities immediately, with initial rollout of service‑request and work‑order modules expected to finish in August and additional modules (inventory, fleet, facilities) no later than September.
