An Oracle blog about Campus Solutions

  • September 29, 2017

Tips and Lessons from successful Campus Solutions 9.2 upgrades

Lawrence Borgione
Campus Solutions Product Strategy Manager

We are asked all the time about the upgrade experiences of our customers to Campus Solutions 9.2.  Questions include: which institutions have upgraded, how long did the upgrade take, how was it managed, and what are the “take aways”.  I have asked some of our customers who have upgraded a number of these questions.  I would like to pass along some of the lessons learned, tips, and experiences that they have shared with me.

The University of Wisconsin Greenbay went live on CS 9.2 initially in about 8 months.  Mike Bubolz, the CS 9.2 Upgrade Manager shared three lessons:

  • Create a separate testing area (get people out of their offices).
  • Make sure to have end-user support for testing and the upgrade window.
  • Learn PUM; maintenance will be very different going forward.

Lidia Anderson from Central Washington University emphasized the importance of managing potential disruptions associated with the upgrade.  They kept the university community informed with continual announcements, sponsored mini presentations for staff around campus, and presented a project overview to every College and to their satellite location.  In addition, they produced training videos for various user groups (e.g. students, staff), posted them on the project web page and supplied links on the MyCWU landing page.  A similar tactic has been used by the University of Southern Queensland.  One of the first institutions to upgrade to CS 9.2, USQ has posted a really cool video announcing their implementation of the Fluid UI to their students.   Kristin Humphreys, Manager (Student Systems) | Student Administrative and Academic Support, told us there’s a lot of excited users and you can see why by taking a look at: https://youtu.be/uR2OL76-RnQ.

In July, 2017, the Kentucky Community and Technical College System (16 colleges statewide) successfully upgraded to Campus Solutions 9.2.  Paul Czarapata, KCTCS CIO shared that change management of project team members on the fluid user interface took longer than anticipated.  To address this he suggests: 

  •        Conduct a “Bootcamp” for project team members on the Fluid user interface in the beginning phase or prior to the upgrade.
  •        Ensure development teams are given ample time to learn the “ins and outs” of Fluid.
  •        If possible, go the route of using an upgrade lab and full time project manager.
  •        Conduct more testing, get feedback from a wider audience of users very early in the project.

Throughout Summer and Fall of 2017  we are seeing an ever increasing number of institutions not only completing the upgrade , but also implementing Fluid, Elasticsearch, and a number of other features that make Campus Solutions 9.2 a valuable and worthwhile investment.  Watch this space for updates as we follow and report on further progress. 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.