Eventually, every user will reach a point when it makes sense to upgrade. The decision, then, needs to be made whether to attempt the upgrade in-house or with an Agile specialist, like myself. Regardless of the direction you go, I want you to have a successful upgrade. So, we’ll walk you through every necessary step. Follow them closely, and you’ll be up and running in no time.
Why Upgrade?
Odds are that your supply network is global. This is important to note when discussing upgrades, because along with globalization comes the need for the centralized manipulation and processing of data. This translates into faster product development from ideation to retirement in a way that optimizes the user’s business advantages across the enterprise and to all supply chain participants. A PLM system upgrade is essential for a competitive edge in a global industry.
An upgrade will:
- Optimize performance and add sustainability and stability to the entire system.
- Ensure you are leveraging the ever-changing hardware and software platforms and using any new features and capabilities.
- Increase ROI. An upgrade will fill in the gaps between what has to be accomplished and what the current system version is able to provide.
- Incorporate the latest compliance regulations into the system, which can quickly reduce productivity costs if left unchecked.
Darren Thatcher states an Agile Upgrade as
By identifying the benefits of what a later version offers and weighing it up against the issues – or risks – of keeping an historical version, and factoring in the price (to always take an economic view) then the answer is in there somewhere.
Whatever your reasons for upgrading, I’m confident the return will fast become evident once you’ve gone live.
Now, let’s cover the upgrading steps.
How to Upgrade Oracle Agile PLM
1. Dual Systems Environment
Building a VM or utilizing additional hardware is highly recommended. In order to eliminate the hassle and cost of restoring data when the upgrade run does not happen perfectly, two simultaneously running environments (current and upgrade target), save cost and time.
2. Backups, Backups, and More Backups
This is more than just a nice-to-have. Backing up data is your safety net if the upgrade failed. It’s your insurance policy. Regrettably, this step gets overlooked more frequently than others. I can’t say it enough, “make backups!” This includes databases, applications, storage, etc. You need to create incremental backups continuously until the completion of the upgrade process. The average-sized PLM installation will require several upgrade passes before going live. We prioritize thorough preparation to ensure the final run is as smooth as possible and all issues are resolved Consequently, despite the upgrade occurring in a separate environment, maintaining a backup of the entire system remains essential. Don’t omit to make backups!
3. Technical Requirements and Software Compatibility
Evaluate the overall system infrastructure and architecture in order to ensure the software is compatible. This is a great time to consider thinking about expanding the implementation to take advantage of all PLM module functionality has to offer. Ask yourself, “how can we better align best practices, process improvements, time/cost savings, etc., with built-in product functionality?” This includes integrating all product suites and modules along with other applications seamlessly within the enterprise. Identifying the right hardware and software requirements will avoid a lot of bumps during the upgrade and implementation.
4. Installation and Migration
After confirming the software and hardware requirements, you can now proceed to install the new system. The company executes this according to a scheduled timeline, tailored to the scale of the business and system.. The larger the database, the more time it takes and the greater the number of passes required.
It is always best to use the installation and migration tools provided by Oracle to get the best results. We have rigorously tried and tested these tools, validating them for each new update version. Consequently, misunderstanding or failing to validate them beforehand can lead to significant, hidden costs. Without proper caution, the risk of data corruption escalates
5. Testing and Training
Upgrade versions vary in what they offer and likewise what they require from the user. Some will be in need of extensive retooling and training, while others will not. Cross-functionality, data integration, and other applications that operate with the new software have to be carefully evaluated.
After multiple installations and migration passes, the company can be sure of a stable system going forward. Rolling back versions is not an option. Therefore, it is critical to test the new system so as not to run into surprises down the road.
Coming from an old version of Agile software, it’s important to undergo thorough training in the new features and functions. Make sure every user and systems administrator takes part in the training as well. This will ensure a seamless transition from the older version to the newer. Furthermore, the true advantage emerges as improvements in processes and features become evident
6. Post-Upgrade Support
Finally, in order to ensure the seamless adoption of new features and functions, it is recommended that every newly upgraded system receive post-go-live support. What this will do is provide end-users with a further understanding of the system. Users will learn how to troubleshoot, perform maintenance, and ensure the system runs smoothly 24/7. Application support conveniently handles monitoring system uptime and ensures users enjoy all the benefits of their upgrade. No one can foresee when future problems might arise. Application support guarantees immediate resolution if your system ever goes down, for any reason.
Empower your IT administrators with this checklist to help simplify the upgrade process
If you run into any questions that I can help you with, please submit a comment below. Best of luck!
Disclaimer: The views and opinions expressed do not necessarily reflect the views and opinions of Domain Systems. The author takes full responsibility for the views expressed here.