[MUSIC PLAYING] On top of making sure that your desktop, server, and web applications are ready for migration as part of a one-off project, there are also other ongoing factors which can cause application compatibility problems for organizations.
These are things like acquisitions. Though organizations undergo constant change, if there's an acquisition, merging applications for a new company can be time-consuming, expensive, and disruptive to the business.
New technology. A good example of this is virtualization. It is essential to know which applications will work on your chosen virtualization technology before you start, but this will not just be a point of time assessment. If you're adopting visualization technologies. You need to check all of your apps for compatibility going forward. Any new application will need to be assessed and converted into a virtual format on an ongoing basis.
New and updated applications. Any new application entering the environment will need to be tested against your application [INAUDIBLE], especially your core line of business applications, to make sure there won't be any conflict before you deploy them into the environment. Also, before you apply application updates, both for external and internal applications, you need to make sure that these updates won't cause any incompatibility.
Regular OS updates and patches. Patch Tuesday is another. We've all heard of patches which cause problems. It is important to test the patches against your applications to make sure they won't have any adverse effect before you roll them out.
Standardization and automation. So last, but not least, getting applications into the correct corporate standard. All applications must make sure that your company specific [? centers ?] are incorporated before they are deployed. While we hope that user acceptance testing will find any issues, automation can help to speed up that process and ensure you get new applications to your users quickly.
So as you can see from what I've already said, change happens constantly. Application readiness should not be thought of as a one-off problem, like a migration, but instead, as part of best practices for ongoing management. ChangeBASE should be incorporated as part of your application life cycle management process, to make sure that all of your applications are ready all of the time.