Shelby Klingerman, Content Curator |

At RECONNECT 18, customer panelists came together to discuss their journey with implementing the Fluid User Interface. Panelists included Nancy Eavenson from Cru, Rahul Nori from the State of Minnesota and Ashutosh Rana from Capella University. Each panelist had a unique Fluid implementation story, but they all three ultimately had success. Here’s a small breakdown of the journey of each panelist.

Cru

Footprint

The organization started with PeopleSoft for HCM and Financials in 1994. In 2016 they turned on Fluid with PeopleSoft 9.2 and PeopleTools 8.55. They went live with only a few key Homepages and Tiles including the most essential Pages, Navigation Collections and WorkCenters.

Implementation and Rollout

Cru had two programmers working on Fluid and three team members from HRIS working on Homepages, Dashboards, WorkCenters and Navigation Collections. The process took around eight months and they are still gradually adding to it.

They took on a staged release approach to rolling out Fluid, while others have chosen a “big bang” approach. They started with Navigation features first and did not immediately deliver or turn on all Fluid features at once. They also provided training videos to help ease the transition.

State of Minnesota

Footprint

The state of Minnesota utilizes Payroll, Human Resources, Benefits, Recruiting Solutions and Learning Management within PeopleSoft. HCM is currently on 9.2 PUM 27 with PeopleTools 8.54.20 and disabled Fluid. ELM is on 9.2 PUM 17 with PeopleTools 8.54. FMS is on 9.1 with PeopleTools 8.54 but is moving to 9.2 with 8.56 soon. HUB and EPM are both on 9.1.

Implementation and Rollout

The team for this implementation was larger than the other panelists’ teams. They had six developers on the HCM team, eleven developers on the FMS team and eight contractors. The primary objective of moving to Fluid was to get the State of Minnesota on a path aligned with Oracle’s product roadmap and to catch up with PUM and PeopleTools upgrades with ease. They started the process in the summer of 2017 with a go-live date set for February 2019; it has been a longer-term project.

They decided to use the “big bang” method for the FMS rollout. They are trying to train users in advance based on test systems so that the users are ready when production is up and running.

Capella University

Footprint

Capella University has Campus Solutions, ELM, CRM, Human Resources, Finance and Interaction Hub. They are all on 9.2 with PeopleTools 8.56. All applications are utilizing Fluid except for CRM.

Implementation and Rollout

The implementation team for this project was smaller than the other panelists’ and had only two developers. The rollout followed the “big bang” approach, coming out all at once. Users were initially asked if they wanted to have both Fluid and Classic experiences, but Capella decided it was best to have everyone get used to Fluid all at once.

As you can see, implementing Fluid looks different for everyone! To learn more about the benefits gained, lessons learned and where each panelist is on their Fluid experience now, check out the full presentation in this video:

Several PeopleSoft customers have implemented Fluid. Learn about their successes, challenges, lessons learned and recommendations for others in these Quest Customer Stories!