The need and risks associated with decommissioning systems
Our thirst for IT solutions has grown exponentially in the last two decades, with the continuous acquisition of applications an inherent part of business life. However, organisations don’t have the same thirst for decommissioning legacy applications and are suffering severe software bloat to such a degree that their applications portfolios are becoming an expensive drain on their business. Decommissioning success is not always guaranteed.
Cloud computing has added another layer of complexity, and as we continue to move to cloud-based applications to run our businesses we’re likely to leave our on-premise based applications to fester on the network. There they take up storage and leave the business open to risk as they reach their end of support period and security patches are turned off. The IT department is faced with providing the business with new applications that can deliver more functionality, mobility, and analytics whilst retaining an ever-growing amount of applications that have been shelved but continue to be a drain on the business.
Whilst the risks and the costs are clear, most enterprises feel daunted by the prospect of decommissioning. Successfully running a decommissioning project is often seen as complex and expensive, and despite cost savings offered by the process, lack of expertise means many of these projects are avoided or started and then fail.
With the compelling need to move data centres from on-premise to the cloud, the opportunity offered by leaner, modern applications that improve cost efficiencies is clear. Therefore, many organisations are having to face down their fears and begin the process. Here we offer the key steps we feel are invaluable when undertaking a decommissioning project: