Skip to main content

APR - application portfolio rationalisation

Introduction 

Application Portfolio Rationalization (APR) is a critical component of Enterprise Architecture (EA). It cannot be effectively executed without considering the broader EA framework. Whether or not an organization has a formally established EA function, APR must align with the enterprise vision and strategy. The APR journey begins by examining EA, particularly Business Architecture, and subsequently deriving IT and Technology Architecture.

Before initiating an APR exercise, it is essential to analyze business processes, the organization's operating model, and architecture maturity. A gap analysis should be conducted to identify misalignments between IT strategy and business strategy. This document focuses on the practical execution of APR once the decision to proceed has been made.

Objectives of APR 

APR involves the analysis and reorganization of applications within a portfolio to achieve the following:

  • Reduction in application count – Eliminating redundancy

  • Complexity reduction – Simplifying the IT landscape

  • Risk reduction – Mitigating operational and technological risks

  • IT-business alignment – Ensuring IT supports standard business processes

  • Cost reduction – Lowering maintenance and operational expenses

How APR Reduces Costs

  • Lower maintenance costs by removing redundant applications

  • Reduced infrastructure expenses due to consolidation

  • Improved IT management efficiency through decreased complexity

Steps in APR

  1. Assessment

  2. Analysis

  3. Planning

Assessment: Gathering Information

The first step in APR is gathering comprehensive data about all applications:

  • Application inventory: Owners, versions, technologies, platforms

  • Mapping applications to business processes

Analysis: Evaluating the Portfolio

Various aspects must be considered to assess an organization's application portfolio:

Business Analysis

  • The business value of an application is determined by its alignment with the company's strategic vision.

  • Applications critical to business operations and continuity hold high business value.

Technology Analysis

  • Technical quality assessment determines whether an application should be replaced, modernized, or maintained.

  • Two key aspects of technical value:

    • Software Quality (functional performance, code standards, production feedback)

    • Hardware Quality (scalability, compatibility, upgradability, maintenance challenges)

Software Quality Evaluation Methods:

  1. Testing – Functional and performance testing (e.g., response time, scalability)

  2. Static Code Analysis – Identifying potential issues affecting maintainability, security, and robustness

  3. Production Feedback – Collecting user experiences on system reliability and performance

Hardware Quality Considerations:

  • Scalability constraints

  • Upgrade limitations

  • Integration challenges with newer hardware

  • Support and maintenance difficulties

Risk Assessment

  • Applications with poor technical quality but high business value pose significant risks.

  • Risks should be identified, quantified, and mitigated through contingency planning.

  • Consider risk exposure, probability, and business impact.

Cost Analysis

The total cost of ownership (TCO) of an application includes:

  • Support costs

  • Maintenance expenses

  • Upgrade investments

  • Licensing fees

Planning: Rationalization Strategies

Based on the assessment and analysis, a rationalization plan is formulated:

  1. Low-value, old applications → Retire

  2. High-value, old applications → Modernize

  3. Redundant applications → Eliminate

Additionally, infrastructure and platform standardization should be part of the consolidation strategy.

Conclusion APR is a structured process aimed at optimizing an organization's application portfolio by eliminating redundancies, reducing costs, and aligning IT with business objectives. A systematic approach involving assessment, analysis, and planning ensures that applications contribute positively to the organization's strategic goals while maintaining efficiency and cost-effectiveness.

Comments

Post a Comment

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...
Post a Comment
Read more

Examples 7: ArchiMate flow relationship between elements in layers

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...
Post a Comment
Read more

SmartSimpleTextGenerator: A Smarter Way to Generate Text

  Introduction In the world of text generation, simple n-gram models can produce decent results, but they often lack context-awareness and coherence. To address these limitations, I have developed SmartSimpleTextGenerator , an improved version of my previous project, ImprovedSimpleTextGenerator . This new version enhances the text generation process by integrating Part-of-Speech (POS) tagging , n-gram models , and a back-off strategy , making the generated text more meaningful and contextually relevant. Key Features of SmartSimpleTextGenerator ✅ N-Gram Model with POS Tagging – Uses trigrams (default n=3) and applies POS tagging for better word prediction. ✅ Back-off Strategy – If a trigram sequence is unavailable, it falls back to bigrams and unigrams to ensure smooth text generation. ✅ Sentence Tokenization & Structure Preservation – Tokenizes input text properly while maintaining sentence integrity. ✅ Randomized Word Selection – Generates diverse outputs rather ...
Post a Comment
Read more