The business question What should we be focusing on? explores the business capabilities, their business relevance, and the number of applications associated with the business capabilities in the as-is and to-be landscapes. Analytics help you understand whether to invest, migrate, or divest in applications based on the business relevance of the business capabilities they support.

The visualization shows business capabilities (level 1) with subordinate business capabilites (level 2) nested inside. The subordinate business capabilities are colored based on the Business Relevance indicator and the total number of as-is vs. to-be applications providing the business capability.

As-is application: Current date is between application start date and end date To-be application: Application start date is in the future, or if its Recommendation attribute is Invest or Tolerate or Migrate for strategic applications. Applications with a Retired object state are ignored and not counted as as-is or to-be applications.

Look for business capilities that are not business relevant but where additional to-be applications are planned:

• Red warning sign: There are more to-be applications than as-is applications supporting a business capability that is not business relevant.
• Yellow warning sign: There are more to-be applications than as-is applications supporting a business capability that is business relevant.

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

• Navigate to any business capability or application to view basic data as well as various reports about it.
• Open the Business Capabilities or Applications views by clicking the view caption to manage and edit the data.

The business question Who is responsible for our assets? enables your company to understand the users and organizations that have a functional role for the objects in the IT portfolio. In Alfabet FastLane, responsibilities are documented via the concept of "roles". This information is critical to close the gaps in your data and identify the relevant users to correct data quality issues.

You can view responsibilities for all relevant assets in your repository to find gaps in responsibilities and initiate mitigations You should review the information for each object class to understand how many assets have an “owner” specified and who is responsible for a specific application or component. By diligently reviewing and maintaining the responsibilities for the assets in your company, you can establish a single source of truth for all responsibilities to quickly find the right contacts when making decisions about which assets to keep and which to retire. The business question Who is responsible for our assets? allow to track and take action if the information about responsibilities is incomplete so that you can move closer to a desirable data governance completeness score.

The following preconfigured roles types are available although your company may add additional role types: Application Manager  Architect  Business Owner  IT Owner  Stakeholder  Similarly, role types available for a responsible organization are: Business Owner  IT Owner  Operations  Stakeholder

• Understand who is responsible for a specific asset:

  Enter the name of the object in the Object Name field.

• Specify the object class you want to analyze:

  For example, select Application in the Object Class filter. You can select one or more classes to show in the data table.

• Search for specific roles to understand which assets they are responsible for:

  For example, select Business Owner in the Responsibility filter. You can also select the not defined checkbox to find assets with incomplete governance information.

• Understand how many active assets a person is responsible for:

  For example, select a user in the Person / Organization Name field and set the Object State field to Active.