Application Rationalization

Application rationalization is an analytical process used to achieve cost savings and avoidance, simplify the end-user experience and improve customer service. As an organization's application portfolio grows to meet evolving business needs, it can be easy to overlook redundancies in capabilities across business lines, the costs of infrastructure and the required support and licensing associated with legacy solutions. Application rationalization is a first step toward identifying opportunities to simplify the IT environment, reduce costs and bridge the gap between business and IT.

Application rationalization begins with base lining an organization’s application portfolio. A clear “as-is” snapshot is necessary to establish where an organization is and then develop a plan for where it wants to be.

Once a baseline inventory has been established, meetings are held with business and IT points of contact. The intent of these “deep dive” meetings is to understand each application from a technical, IT perspective as well as a functional, business perspective. The information collected in these meetings is synthesized into recommendations that inform each application’s 4 year roadmap. The GSA uses the acronym TIME for the purpose of describing each application’s strategic direction.

T - Tolerate
I - Invest
M- Migrate
E - Eliminate

Application 4 year TIME roadmaps can be viewed on the GSA Enterprise Architecture Analytics and Reporting (GEAR) website at TIME reports for specific applications can be found by clicking the “Applications” tab to the left on the GEAR home page. Choose “Application TIME reports” from the resulting drop down and use the search box at the top right to find specific applications and their associated TIME reports.

Definitions of each letter in the TIME acronym, and other supporting documentation, can be found by clicking the “About/FAQ” link at the top right of the GEAR home page and then clicking the “Application Rationalization” tab on the “EA Integration Portal Overview” page.

Last Reviewed 2016-08-04