Kenosha finance committee hears update on ‘Kentegrity’ ERP rollout; timeline through January 2027

Clarence Clark, project manager for Data Climb, told the Kenosha Finance Committee on May 19, 2025, that the city's enterprise resource planning program (branded Kentegrity) is progressing on schedule with a target to complete deployment of all modules by January 2027.

The update to the Committee outlined program scope (finance, human capital/payroll, permits and licenses, revenue management, enterprise asset management, courts and utilities billing), the phased implementation approach, expected benefits and key risks. Clark said the program is intended to centralize departmental data, streamline workflows and increase transparency between departmental operations and the city's financial records.

Clark said the project has completed initiation and planning and that work is now underway on current-state/future-state assessments and early data conversions. "The program has been branded by the mayor and by our city administrator as Kentegrity," Clark said, characterizing the program's health as "very good" and saying the work is on track.

Why it matters: the ERP replaces a decades-old, homegrown system and is intended to reduce manual work, give staff and managers real-time access to financial and operational data, enable online permitting and payments, and reduce long-term maintenance needs by moving to a cloud-based Tyler solution.

Clark walked the committee through the implementation methodology and the deployment timeline. Financial modules and permitting/licensing and human capital management are the initial launch areas; utilities billing and enterprise asset management follow in later phases. Managers emphasized that financials form the program's backbone and must be configured accurately before downstream modules go live.

Committee members asked about deployment details. Clark said the city will run parallel processes in key areas (for example payroll and utilities billing) during cutover to reconcile results between the legacy system and the new Tyler environment. He said the implementation team will use user-acceptance testing and training cycles before each go-live.

City staff addressed cybersecurity and data protections. Staff said the Tyler cloud architecture will use an isolated tenant environment, multi-factor single sign-on integration with the city's Google accounts, and encryption of data both at rest and in transit. Clark added that Tyler maintains a cybersecurity team and that the city will retain its own cyber-insurance coverage.

Clark also highlighted an internal resource constraint: "We literally have two people to do data conversions for everything that you saw on that timeline," he said, noting the importance of protecting staff bandwidth and avoiding burnout while sustaining the schedule.

Committee members asked about training and parallel operations. Clark confirmed that go-lives will include user training, user-acceptance testing and cutover processes for each phase. He recommended staggered deployments and a department-level change-agent network to help communicate changes and gather feedback.

What's next: Clark said the project will continue current- and future-state workshops, complete data conversions already underway, and begin configuration work for the next set of modules. The team will monitor change-management indicators from department change agents and report progress to the committee in coming months.

Ending: Committee members had no additional questions after the presentation and thanked Clark for the update; the project returns to the committee for routine status reports and any approvals tied to future contract amendments or scope changes.