Re-implementation vs. upgrade: Which process should you choose?

With execution cycles and time frames very similar for both re-implementation and upgrade projects, which is best for you? Look at both approaches to help you decide.

When we move from one major release to another of IFS Applications, we think about many things such as the functional improvements, the value your business will gain from the latest release, and of course, the costs to reach that point. What is also important to think about is the process to achieve that and from the work we have undertaken, we are seeing that the two approaches are much closer than you might think.

Re-implementation

The re-implementation approach focuses on moving through a sequence of structured steps, much like an initial implementation, however, the knowledge of the solution is detailed and comprehensive, allowing the focus to be on process improvement and helping to solve prevalent business challenges; hence the time and effort involved is significantly less than any new product implementation cycle.

The key to the re-implementation is the ‘prepare’ phase in our approach. This is where the project team focus on:

• Application Orientation and Knowledge Building (latest release)
• Data Transition Planning and Scripting – building migration scripts
• Solution Operation Validation – testing the end-to-end solution execution on the latest release
• Transition Pre-Test – executing a complete cycle of the migration process

Having proved the solution and written the transition scripts, the project moves to two formal test cycles, AST and user acceptance testing (UAT), to validate that the solution and data all operate as expected, before deployment to the live environment.

Baker Tilly works with their re-implementation clients to define an appropriate timeline to move though the project in a simple and structured way, deliver a successful re-implementation with has been oriented wholly to the business needs.

Upgrade

The upgrade process for IFS follows a very similar roadmap. The first phase of work is focused around:

• Application Orientation and Knowledge Building (latest release)
• Upgrade Scripting – compiling migration scripts
• Solution Operation Validation – testing existing processes on the latest release
• Transition Pre-Test – executing a complete cycle of the upgrade process.

Baker Tilly works with many customers to provide consulting and technical services which particularly focus on application orientation, solution validation and technical customisation.

Having proved the solution and tested the upgrade scripts, the project moves to two formal test cycles (Iterations) to validate that all business processes operate (and all data is as expected), before deployment to the live environment.

Which should you choose?

With execution cycles and time frames very similar for both re-implementation and upgrade projects, which is best for you?

Fundamentally, both approaches unlock the key business benefits of enhanced functional capabilities and current supported technology. From a process perspective, the re-implementation approach provides the additional opportunity to address significant business process changes and cleanse operating data, whilst also providing an uncomplicated method of transitioning from ageing releases. Upgrade methods can be very efficient and reliable where the level of change is small.

Whichever approach is right for you, Baker Tilly will work with you to make your journey to the next release a success. Our full-service professional team offers consulting, technical and project management services, certified as part of our strategic alliance with IFS. We seek to deliver a high-quality service in a simple and straightforward way which is focused on your needs.

To learn how Baker Tilly can accelerate your projects with IFS, contact our team today.