Best practices for IBM TRIRIGA application upgrade
With 150+ IBM TRIRIGA completed projects across the globe, ValuD has the largest and most experienced team focused exclusively on IBM TRIRIGA. ValuD offers a variety of delivery models to meet our clients’ needs to ensure customer success whether for a new implementation or an upgrade. In the first of a four part series, we share our best practices for TRIRIGA application upgrades.
What is an application upgrade
When an application’s new release is applied over an existing production environment, and data migration or re-implementation is not needed, it is called an application upgrade. While less complex, an application consultant and full regression testing of the new system is needed before taking it live.
ValuD TRIRIGA Upgrade Best Practices
1. Application versus Platform Upgrades
- If performing only platform upgrade: Ensure current application is compliant by the application sunset date to avoid support issues.
- If performing both application and platform upgrade: Perform the platform upgrade followed by the application upgrade to ease the issue resolution process.
- Ensure that current release can be upgraded to the targeted platform release since older platforms might require more than one jump.
2. Upgrade environments
ValuD recommends setting up two environments in addition to the current production environment during the upgrade process. The source environment would be a copy of the existing production environment and will be the one that gets upgraded to the target platform. Use the TRIRIGA standard data file in the third (Target) environment for a clean install of the targeted application and platform version. Ensure that the environments are procured well ahead of the upgrade process to avoid project delays.
3. Do not plan for modifications in conjunction with upgrade process
Performing modifications or removing customizations in conjunction with an upgrade process will increase costs and project timelines and impact your quality control process due to the absence of a testing baseline. Instead, move all modifications “as-is” to the new application release and then perform the customizations needed in the upgraded version. This will help save on costs, remove the need for design and documentation changes, and most importantly, will allow you to use your current system as the baseline for your testing process.
4. Standard preparation points for the upgrade process
- Read all the standard software release notes to identify potential issues that could affect your upgrade process
- Study all related internal documentation (Functional Specification Document, Technical Specification Document etc) to understand all the modifications implemented in the current system.
- Determine which TRIRIGA objects were modified and whether proper renaming standards were used.
- Move all modified queries “as-is” to the new release to avoid quality risks and project delays.
In the next post, we shall discuss the IBM TRIRIGA 10.5.3 upgrade preparation process specifically related to the FASB/IASB leasing standards. For more information on IBM TRIRIGA upgrade best practices, watch our webinar.