Upgrades
Why Upgrade ?
A simple question with some complex answers.
There are a number of reasons or inputs to upgrading:
- Retain a supported version of QAD Enterprise Applications (MFG/PRO)
- The business has changed and we need to review processes
- Our data structures are wrong and we need to start again
- The business needs to be reviewed and processes changed to become more efficient
- The business wants to review bespoke work and get back to standard
- The business would like to take advantage of the latest .Net functionality
- There is a need to reskill and an upgrade project provides focus
- The business wants to use new modules that are only available in later versions
- Take can take the opportunity to update the operating system and hardware
- It’s less expensive than a new ERP system and we don’t have the time or resources to implement brand new.
It’s been said that “technical” only upgrades are a “waste of time and money” as they only fulfill one or maybe two of the inputs above. One of the key financial justifications for an upgrade should include a detailed review of processes and practices with the inevitable effect on roles and responsibilities to incorporate changes to the business and remove ineffective processes.
To look to get to the root cause of the sort of activity that is; “the “sticky plaster that covered a gap in the bigger plaster that covered the bandage that was a stop gap measure” for a problem that last happened 15 years ago, and is now enshrined in every day practice.
A well-defined and planned upgrade can fulfill all the criteria above and bring big business benefits without costing the business the costs of reimplementation.
The wins are there to be had and Redstone can help project manage the upgrade through workshops, QAD Enterprise Applications (MFG/PRO) consultancy and “as is” and “to be” process mapping to get the most from your investment.
