Last time we talked about getting prepared to plan for your PeopleSoft 9.2 upgrade, collecting data and identifying people with the knowledge to complete the planning.
This time, we are looking at the planning for the upgrade project. This can be completed as the initial phase of your upgrade, or you can complete these tasks in advance so that you have a full understanding of what the upgrade project is going to take in terms of resources, timeline and budget. The latter is recommended if you are highly customized or if you need to go through a budgeting process to procure funds for the upgrade.
Here’s what you might want to consider:
- Reviewing customizations. There are two aspects to this. One is taking a look at the customizations and seeing if they have been replaced by new functionality. You’ll use the Cumulative Feature Overview tool for this again. The other aspect is looking at your customizations from a rationalization point of view. This is where you will review the ‘why’ of the customization and whether that reasoning still applies.
If you are like many organizations who use PeopleSoft, your last few upgrades have likely been technical in nature with a “lift and shift” to the new version moving customizations forward. V9.2 and the new selective adoption model increases the importance of taking a conscious step to evaluate the customizations you have and only moving those forward that are strategic or required for your business. This extra step as part of a 9.2 upgrade project will result in downstream cost savings and lower risk when using selective adoption. During the planning stage, you may be able to identify a number of customizations for potential removal along with the change impacts of the removal. Note: At this point, the customizations are only identified for removal, this will need to be reviewed and finalized during the upgrade project.
- Understand the new version. Take a look at what is changing against what you are using. Identify areas in your business that will be impacted by the change.
- Understanding technical infrastructure changes. You’ll use the technical architecture documentation you previously created to ensure that the versions, sizing, etc. will be supported for the new version. Make sure you are also looking at any integrations for impact. The technical architecture requirements can be found in My Oracle Support: PeopleSoft Update Manager (PUM) Home Page (Doc ID 1641843.2).
- Decide whether you want to use an upgrade lab to complete the technical portions of the upgrade. An upgrade lab can help by running the technical upgrade steps (upgrade pass 1) and also the test moves (we recommend at least 3 test moves) which tighten up the upgrade process and confirm that the upgrade steps can be completed within the implementation window. Upgrade labs have extensive experience with upgrades and often will have done your specific version to version upgrade path with a knowledge base of issues and resolutions based on what they’ve run into before. They also typically have proprietary tools to monitor and execute the upgrade steps.
- Understand and document the scope of the upgrade. All of the information that you have reviewed, analyzed and documented feeds into determining the scope of the upgrade. You should have fairly good detail of what customizations you expect to be removed and the impact of that removal on your organization. You will also understand other impacts based on the changes in the application. Consider what new functionality you may want to implement and include in scope that provide incremental improvements in functionality without adding a lot of time and risk to the project. And consider who needs to be involved in the upgrade project and when and what v9.2 specific expertise is needed to augment your team.
- Develop the project schedule. Once you have the scope defined, develop your project schedule and resourcing plan. It is important not to underestimate the testing effort here. This is one area where you will want to create reusable artifacts.
- Develop the project budget, making sure that you include any needed upgrades to your infrastructure and third party applications.
With these planning activities complete, you’re off and running!