Osceola leaders outline timeline, risks and data‑governance needs for ERP modernization

Osceola County School District staff and consultants gave the board an update on the district’s enterprise resource planning (ERP) modernization work during a workshop, outlining the vendor selection timeline, implementation phases and data‑governance recommendations.

The update, presented by a Plante Moran consultant, said the district has documented more than 30 current business processes and developed more than 900 functional requirements that were incorporated into an RFP published in January. Proposals are due February 28; the district’s cross‑functional evaluation committee will review submissions, shortlist vendors, host demonstrations in April and May, and target a final recommendation to the board around June 24, with contract negotiations aimed for completion by September.

The consultant described the difference between the current legacy ERP and modern cloud‑hosted systems, saying, “An ERP system is essentially the software platform that drives business processes for an organization,” and explained that modern systems are typically cloud‑hosted, accessed via web browsers, and designed to integrate with third‑party tools. He told the board a phased rollout is recommended for an organization of Osceola’s size rather than a single “big‑bang” cutover.

Why it matters: the district’s ERP underpins finance, human resources, payroll, budgeting and work orders. Upgrading the system affects how staff enter and access authoritative data and can change who maintains critical records; the presenters emphasized that a successful transition will require strict data governance and a plan to limit and phase out ‘‘shadow systems’’ such as local spreadsheets that currently act as unofficial sources of truth.

Key findings and recommendations from the gap analysis included a need for: strong data governance structures and a dedicated data‑governance committee; application governance; an identified implementation team and backfill plans for staff who will work on implementation; change‑management and training plans in advance of rollout; and cleanup of the chart of accounts and payroll code structures prior to go‑live.

The consultants described three broad options for handling historical data in the legacy system: (1) convert all historical data to the new ERP (noted as effort‑intensive and costly); (2) retain the legacy system in a limited, view‑only mode for a period (access restricted to a few staff for audit and compliance purposes); or (3) export legacy data to a data warehouse for reporting and compliance. The vendor proposals will include recommended approaches and associated costs.

The update also covered evaluation process rules. The consultant stressed a no‑contact rule for evaluation committee members and board members to prevent undue influence: committee deliberations and scoring will occur in public meetings to preserve fairness, and reference checks and peer‑district site visits are planned as part of due diligence.

On implementation sequencing, the consultant said the general ledger/chart of accounts is typically implemented first because it provides the financial backbone other modules use; subsequent modules (for example, HR/payroll) can follow by phased priority. The district and vendors will further refine the phasing approach during evaluation and demos.

Plante Moran presented an optional follow‑on service: the firm offered implementation project management services to support the district during software rollout if the board chooses to contract that work. No board motion or vote was taken during the workshop; the presentation was an informational update and debate about next steps.

Next steps: proposals due February 28; initial proposal scoring by the evaluation committee is scheduled for April 1 to create a shortlist; vendor demonstrations will occur in April–May; final evaluation is tentatively targeted for June 10 with a board recommendation to follow June 24; contract negotiations are targeted for completion by September. The district also plans to continue work now on chart‑of‑accounts cleanup and other readiness activities.