Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the It Procurement topic
No spam. Unsubscribe anytime.
Chase County weighs $51,000 OpenGov deployment amid troubled PubWorks migration
Summary
Public‑works staff told commissioners that migration from PubWorks to GWorks/Hyperweb has underperformed; OpenGov offered a custom deployment priced at $51,000 and staff asked commissioners to allow more due diligence, references and possibly phased payment rather than an immediate switch.
Public‑works staff told the Chase County Commissioners on April 30 that the county’s migration from PubWorks to the GWorks/Hyperweb platform has produced disappointing results and customer‑service gaps, and presented OpenGov as an alternative with a substantial one‑time custom deployment fee.
The issue: staff said PubWorks was acquired and that the county’s data transfer to GWorks/Hyperweb has not produced a workable asset‑management system. Staff described the OpenGov quote as including a $51,000 custom deployment charge (professional services to extract and reorganize historical data) plus annual domain fees, and said OpenGov representatives offered to spread the deployment cost over multiple years to reduce upfront expense.
Why it matters: the county has accumulated a large historical asset database in PubWorks that staff do not want to lose; decisions on replacement software affect long‑term asset management, maintenance tracking and potential audit readiness for federal grant programs. Commissioners expressed interest in references, evidence other PubWorks users migrated successfully, and why OpenGov’s deployment fee is large.
Questions and next steps: commissioners asked staff to obtain contact references for counties that implemented OpenGov, to ask why implementation costs are high and whether OpenGov can reliably migrate PubWorks data, and to provide written proposals and contact details before the board decides. Staff agreed to collect OpenGov contact information, follow up on references (including counties that reportedly walked away from GWorks), and revisit the issue at the next meeting.
Budgetary context: staff estimated annual licensing and domain costs rising approximately 5% per year after initial deployment, and warned that data preservation of the county’s asset history is a priority. No procurement decision was made at the meeting; commissioners asked for more information and to discuss again at the next meeting.
