FAQ

Empowering UF aims to build modern and unified businesses processes and administrative systems that will support the university for the next 20 years.

UF’s current administrative system, myUFL (PeopleSoft), was implemented 19 years ago. The trend across higher education is steadily moving towards cloud-based information solutions.

The One UF vision represents a desired future state in which all UF colleges, departments, and units use a common set of business processes in the same system. As such, all academic, administrative and DSO/affiliate units will participate in the modernization initiative. 

The initial software costs will be $3.6 million spread across three years. In the planned go-live year of 2027, the software will cost $5.2 million annually. UF’s software contract represents the lowest publicly known negotiated price.

UF is evaluating the costs related to utilizing an implementation partner, as well as opportunities for cost avoidance, as a part of this effort.

Please continue to visit this project website for updates. You may also complete our feedback form to submit any questions or comments.

Currently, UF has 53 third-party integrations to PeopleSoft. During the readiness assessment phase, an inventory of third-party applications was performed to determine the potential scope for the Empowering UF initiative. Decisions about keeping or retiring UF systems or other third-party applications will be made during project implementation.

No. Student information systems underwent a comprehensive modernization effort two years ago.  The current student systems are not changing but will need to integrate with the new UF cloud administrative system.

Homegrown, or “second-degree” systems will need to be evaluated to determine compatibility with Workday. Our goal is to meet as many business needs as we are able through Workday and thereby relieve departments of the need to maintain a separate system.

Yes, Workday’s recruitment functionality, including tracking, will be implemented and replace PageUp.

Yes, Workday Adaptive will be reviewed, adjusted and overlaid with the new budget model, taking advantage of Workday’s reporting capabilities.

This is still being discussed as one of our critical decisions.

During the Architect stage, which starts in Spring 2025, the project will conduct Design sessions to understand how Workday addresses specific business processes and design for the future. Thoughtfully identified members of the UF community will participate in Design sessions to keep input targeted and productive in order to help design Workday for UF’s needs. The Test stage of the project occurs later in the project timeline, beginning in Spring 2026, and will last for more than a year with many different types of testing. 

Informal training and change management will begin as early as the Post-Selection Readiness phase. The UF project team will begin to reimagine our business processes together to help eliminate pain points and to think about how we will work together in the future during design sessions in the Architect and Configure stages of the project. Unlike previous implementations, we will be asking for active participation throughout the configure and design phases, empowering members of the university community to become subject-matter experts and resources to their respective communities prior to go-live. Leading up to and upon go-live, traditional training and support will be available as well.

Yes, while the details of how much historical data will be available within Workday, we are planning to ensure historical data are still easily accessible based on the required need.

No, we will make a clean switch upon go-live of the new system. To help ensure the system is functioning optimally, we will conduct testing for more than a year, with any needed modifications made during and between each round of testing to smooth the transition.

A major piece of the planning phase will be capitalizing on the opportunity to reimagine UF’s chart of accounts and the way the university does its business. A lot of what we do today is based on practices that are nearly 20 years old and have not adapted to the university as it has grown.

Workday’s equivalent Chart of Accounts (COA) is called the Foundation Data Model (FDM). The FDM is a critical component of the Workday ERP solution and represents a shift in how UF will think about the COA in the future.  The project will begin planning for this core element of the new cloud‐based Workday ERP solution early on in the Readiness stage of the project to enable a successful a COA design.