Analyze the data: What is our landscape?

The business question What is our landscape? provides insights to the business capabilities and the applications that provide functional support to the business capabilities. The visualization represents a functional decomposition of your application landscape that provides insight to the organizations and the business capabilities they execute. It allows you to visualize application KPIs and color rules for rapid analysis to understand the current application landscape and plan your IT portfolio roadmap.

To open this business question, go to the left navigation panel, click to expand Business Questions, click to expand Roadmapping and click What is our landscape?

The visualization shows the top two levels of business capabilities in the business capability hierarchy and the current and planned application support. For each nested business capability, you can understand which applications currently support that business capability. Applications that provide support to a lower-level business capability are aggregated up to the second-level business capability.

Understand how different organizations provide applications that support business capabilities.Select an organization in the Business Owner filter field. Review the business capabilities and the applications that support them. Change the business owner to understand differences in organizational support in the landscape.

Understand the technical obsolescence of a business capability. Select Technical Obsolescence in the Color Rule filter to highlight the risks to the business capability based on technical obsolescence.

Recommendation: Identify which business capability are at risk due to applications that use a component that has reached the end of its planned lifecycle. To understand the issue, navigate to the object profile for application, go to Technology Portfolio and open the Component Lifecycles view. Review the components that have an end date before the application's end date and consider whether the components shall be updated or whether the unsupported application should be replaced by a different application.

Understand how the landscape changes over time for the most important business capabilities.Enter a date in the future in the Active Date filter field to understand which applications will be obsolete in the future and select Business Relevance in the color rule field to understand the business capabilities that are most critical for the business.

Recommendation: Analyze how your landscape changes over time and understand where risks will occur to critical business capabilities due to potential gaps in application support.

Identify potential replacement candidates for applications. Look for business capabilities that have a significant number of applications supporting them. Select Strategic Applications in the Color Rule filter field to understand the applications that are most critical for the business.

Recommendation: Identify which business capabilities are at risk due to applications that use a component that has reached the end of its planned lifecycle. To understand the issue, navigate to the object profile for application, go to Technology Portfolio and open the Component Lifecycles view. Review the components that have an end date before the application's end date and consider whether the components shall be updated or whether the unsupported application should be replaced by a different application.

Review or update the data source

This business question requires the availability of at-least 2 levels of business capabilities in your portfolio.

Click the Data Source button to view the business capabilities and applications relevant for this business question. You can do the following:

Understand the applications used for the report. Go to the Application Data Workbench to view the applications used for the report.

Understand where application support could be consolidated.

Click an application to navigate to its object profile, click Business Portfolio, and open the Similar Applications Supporting Business Capabilities view . The view shows the similarity between the business capabilities provided by the selected application and other applications so that you can understand what other applications provide support to the business capabilities that the selected application supports which of those business capabilities other applications support. Based on this information, you can consider which applications might be redundant and should be sundowned.

The Common Business Capabilities column lets you understand how many business capabilities the selected application has in common with other applications. The percentage of overlap is calculated and shown in the Overlap % column. You can sort the dataset based on the values in the Overlap % column. The other columns show the business capabilities that only the selected application supports and the business capabilities that other applications support.

Based on the overlap, should the selected application be sundowned? If so, then which business capabilities supported by this application need to be supported by other applications.

Based on the overlap, should other applications be sundowned that provide support to the same business capability as the selected application. If so, then which business capabilities supported by other applications need to be supported by the selected application.

Understand the business capabilities used for the report. Open the Business Capability Data Workbench to examine the business capabilities used for the report.

Understand strategic recommendations for applications.

The analysis looks at the business and technical scores of applications and places each application into one of four quadrants Tolerate, Invest, Migrate, or Eliminate. At the same time, the report colors the applications according to the value specified for the Recommendation attribute.

This allows you to assess whether the strategic recommendation of the application reflects the real world business and technical score. Understanding the application score will help in making decisions about whether it is best to keep an application ( Tolerate ), invest in the application ( Invest ), consider the application as a migration candidate ( Migrate ), or sundown the application ( Eliminate ).

The report shows applications as bubbles analyzed across 4 dimensions. Point to an application to show a tooltip with the following information: Application name, business score (BS), technical score (TS), Recommendation value, current year operational expenditure (OpEx).

The bubble size indicates the application cost based on the current year operational expenditure (OpEx).

The bubble color indicates the correspondence of the business and technical scores with the strategic recommendation specified for the application

The bubble is green if one of the following criteria applies:
technical and business scores are less than 2.5 and the application's Recommendation attribute = Eliminate.
technical score is >= 2.5 and the business score is <= 2.5 and Recommendation = Tolerate
technical score is <= 2.5 and the business score is >= 2.5 and Recommendation = Migrate
technical score is >= 2.5 and the business score is >= 2.5 and Recommendation = Invest.

The bubble is red if none of the above criteria applies.

The bubble is grey if the Recommendation attribute is not defined for the application.

The X-axis value is the weighted business score based on application indicators

BS - Business Relevance: 0 = Unknown / 1 = Business Operating / 2 = Business Enabling / 3 = not applicable / 4 = Business Evolving / 5 = Mission Critical.

BS - Numbers of Users: 0 = 0 / 1 = 1-10 / 2 = 11-100 / 3 = 101-1.000 / 4 = 1.001-10.000 / 5>10.000

BS - Ownership: 0 = Unknown / 1 = other role / 2 = not applicable / 3 = IT Owner / 4 = Business Owner / 5 = Business Owner and IT Owner.

BS - Provided Capabilities: (0 = 0 / 1 = 1 / 2 = 2-3 / 3 = 4-5 / 4 = 6-7 / 5>7)

BS - Using Organizations: (0 = 0 / 1 = 1 / 2 = 2-3 / 3 = 4-5 / 4 = 6-7 / 5>7)

The Y-axis is the weighted technical score based on application indicators

TS - Application Age (months): 0 > 120 / 1 = 73-120 / 2 = 49-72 / 3 = 25-48 / 4 = 12-24 / 5 < 24

TS - Architecture Type: 0 = unknown / 1 = Mainframe / 2 = Distributed / 3 = Client Server / 4 = Stand Alone / 5 = Cloud Based ext. Webpage.

TS - Vendor Support Lifespan (months): 0 <= 0 / 1 = 1-3 / 2 = 4-9 / 3 = 10-18 / 4 = 19-24 / 5 > 24

TS - Development Type: 0 = unknown / 1 = not applicable / 2 = Bespoke / 3 = COTS-Customized / 4 = not applicable / 5 = COTS-Configured

TS - Interfaces: 0 = 0 / 1 = 1 / 2 = 2-3 / 3 = 4-6 / 4 = 7-9 / 5 > 10