Tag Archives: application decommissioning
As part of their cost cutting program, organizations are consolidating data centers and the applications within them. Federal and state agencies in the public sector are among those where IT consolidation and moving applications to the cloud are top priorities as part of an overall goal to increase efficiencies and eliminate costs. In other industries, many consolidations are also under way due to mergers and acquisitions and other cost cutting initiatives. As you plan or undergo a consolidation project, you also need to plan for the retirement of legacy, redundant applications that are left behind.
Eliminating Up To 95% Of Legacy Costs As Part Of Your Journey To The Cloud, With Application Decommissioning And Archiving
We’re all familiar with those legacy applications that no longer add value, but still absorb significant costs. These redundant applications may be left due to mergers and acquisitions, IT consolidation, business modernization, application migration, or moving to a cloud-based or software as a service environment. If you are an EMC customer, many of you may be undertaking projects to consolidate your IT stack to increase efficiency, and moving gradually towards a private or hybrid cloud environment. As you are virtualizing, re-platforming, and migrating your hardware and software, what do you do with the old applications that are left behind? (more…)
Following a Merger and Acquisition (M&A), there is usually a focus on consolidating the two companies’ IT systems, leaving behind many redundant legacy applications. Until those legacy applications are shut down, you haven’t realized the cost savings of the consolidation. However, those old applications may contain data that’s no longer used for daily operations, but need to be retained for regulatory compliance. Keeping those applications up and running, just to retain the data within them introduces operational, business and legal risks. It is likely that the IT staff who have the expertise about those applications are no longer with the company, and without them it may be difficult to impossible to access the data in a meaningful way, in the time required, for an audit or eDiscovery request.
Last month I outlined the reasons why IT organizations should consider eliminating certain applications. The savings in terms of redirecting hardware, software maintenance licenses and full time equivalents (FTE) with specialized skill sets to other more critical projects can be significant. I also noted that all these benefits can be achieved so long as you can continue to retain and access the data easily and cost-effectively for compliance and reporting purposes.
A question that might linger in your mind is how much cost savings can you really achieve if you retire the data but still retain it in a database, with its associated maintenance cost? But what if you had the option to store your data at a fraction of its original size on common file systems, with full audit-ability, built-in retention management, while still maintaining on demand query access for your business users? The resulting savings could be so significant that application retirement might not only be an option, but an overwhelmingly compelling initiative that must be implemented.
Expanding on Judy Ko’s blog on Why Applications Don’t Matter, IT organizations should look at eliminating their applications. They should review their application portfolio and determine the business value of each application, especially those that are inherited from acquired companies. Many of these legacy applications are rarely accessed, either because the relevant data has been migrated to another application or the entire application has become obsolete, and the data is only useful for compliance audit purposes. In this case, they should think about retiring these applications and shutting down all the infrastructures associated with it.
Why keep around applications when you no longer use it, except on one-off occasions? According to Forrester, “Streamlining the existing application portfolio is a necessary step for organizations that have been in existence for a decade or more, especially if those organizations intend to evolve to SOA—why carry all that baggage forward to the next computing paradigm? Only some legacy applications will be reusable, and some aren’t fit for anything but retirement—but how can you tell which is which? Why waste money maintaining applications that aren’t worth keeping? Why not redirect that money to where it will benefit the organization?”1