Determining Your Upgrade Path

To determine your upgrade path:

  1. Use the Tested Configurations document to determine supported upgrade paths for major releases.
  2. Verify whether you can upgrade directly to the target release or whether you must first upgrade to a previous release before moving to the target release.
  3. Evaluate the complexity of your upgrade based on the number of modules implemented, number of integration points, number of interfaces, total number of business process scripts, and number of customizations to include.
  4. Determine the metrics and cost associated with each aspect of the upgrade.

Related Topics

Upgrade Best Practices

Treating Your Upgrade Activity as a Formal Company Project

Using an Appropriate Change Management Strategy

Building an Upgrade Team with Broad and Complementary Skills

Utilizing Peer and Oracle Resources

Deciding When to Change or Add Business Processes

Managing Issues

Preparing the Organization

Ensuring the Quality of Your Data

Taking Inventory for Your System

Preparing a Go-Live Checklist

Understanding and Mitigating Project Risks

Evaluating Your Architecture

Calculating New Hardware Sizing

Identifying Custom Code and Scripting

Adhering to Current Tested Configurations Requirements

Implementing the Current P6 EPPM Release and Patches

Minimizing Application Data to Upgrade

Testing a Copy of the Production Database

Leveraging Existing Test Scripts and Plans

Performing Index Management

Training End Users on the New Solution


Last Published Tuesday, December 12, 2023