These are the parameters that govern how a default upgrade planning is composed:
- Upgrades and Phases start on a Monday
- Upgrades and Phases end on a Friday
- A Classical upgrade lasts
per version, which translates to 14 weeks for the 2-version upgrade that is proposed by default.
Note: If you need a duration that is less than 4 weeks in total, please select an Expedicted upgrade type instead.
- An Expedited upgrade is usually seen during the implementation phase, all environments are upgraded almost simultaneously without formal phases (Analysis, BUild, etc.).
- When creating a classical upgrade schedule, the maximum duration of the training phase is 4 weeks (you can always modify that manually).
- Vacations and holidays are only displayed, they do not have an influence on the proposed planning. Add a comment here if you have suggestions on what would be useful.
-
Environment upgrades are proposed in this way:
- REL at the start of the project
- POC at the start of the build phase
- TST at the start of the testing phase
- MST, ACEs and PLY at the start of the training phase
- SUP 4 days before the PRD upgrade
- PRD at the end of the project
-
SU Deliveries are proposed in this way:
- Initial SU Delivery at the start of the project
- All Fix SUs Delivery 2 weeks after the end of the Testing phase
- Pre-Upgrade Critical SU 2 weeks before the PRD upgrade
-
Post-Upgrade SU Delivery 2 weeks after the PRD upgrade
- (yeah, one could argue that the PRD upgrade date is thus not the real end of the upgrade project...)