As we continue to prepare for the Campus Solutions 9.2 release, many of you have asked us about what to anticipate when planning for the effort and impact of the upgrade. While everyone's upgrade is different, the effort and the impact of the the technical upgrade from CS 9.0 to 9.2 should be significantly reduced, however the total upgrade effort will depend on your environment, upgrade goals and timing.
We have reduced the effort and impact of the technical upgrade from CS 9.0 to 9.2 by:
- Keeping tables and record structures generally unchanged.
- Thereby reducing the required data conversion by more than 90% compared to previous major upgrades (e.g. CS 8.9 to 9.0).
- Avoiding the introduction of net new functionality by rolling up new features previously delivered on CS 9.0.
- Forward fitting CS 9.0 bundles through July 2015 to CS 9.2.
- Following PeopleTools recommended technical adoption standards wherever possible.
While we've made every effort to reduce the technical impact, the total upgrade effort will depend on:
- Your current PeopleTools version
- Whether you have completed the CS - HCM separation
- The number of customizations you have; specifically on the pages that have been updated in CS 9.2 as a result of applying a new style sheet, accessibility, and other changes.
- Your level of familiarity and preparedness for the PeopleSoft Upgrade Manager (PUM; see our earlier blog entry regarding preparing for selective adoption in CS 9.2)
Your upgrade goals
- Many customers leverage the upgrade as an opportunity to adopt available functionality that has not yet been deployed. The CS Cumulative Feature Overview tool can be used to assess your options.
- Many customers leverage the upgrade as an opportunity to reduce and/or rationalize their customizations. The Oracle Upgrade Lab's CEMLI and PCAT tools are available to assist with this assessment and benchmark comparisons with other customers.
The timing of your upgrade
After the initial release of CS 9.2 we'll continue to apply maintenance to both the CS 9.0 and 9.2 codelines. As time passes, its's likely that additional complexity will be encountered to synchronize environments to be at comparable levels because you'll need to consider an adoption plan for an increasing number of features and capabilities. PUM technology simplifies this in that there will always be a single change package for you to use to "catch up". But, the impacts of deployment, training, roll-out, change management, testing etc. will factor into the overall size of the effort.