Report Views

Report views enable you to color Fact Sheets shown in the report to help you gain insights. Report views are selected from the View dropdown box on the report and can be based on:

  • Fields on Fact Sheets - attributes on the base Fact Sheet Type of the Report. In some cases this attribute may be derived or calculated, e.g. Aggregated Obsolescence Risk.
  • Fields on Relations - attributes that you find on a relation between the base Fact Sheet Type and a target Fact Sheet, e.g. the Total annual cost attribute is stored on the relation between an Application and an IT Component.
  • Fields on Related Fact Sheets - attributes from Fact Sheets not shown in the report but related to the Fact Sheets displayed, e.g. the functional fit of an Application in an IT Component Landscape report.
  • Tags - define tag colours in the Administration section
19251925

📘

Views on the reports and their use cases

For a complete overview of the use cases that can be resolved with the views below, please refer to this excel file.

Default Report Views

1. Lifecycle

In the Lifecycle view, the color of the e.g. Applications indicates the current status of the application. LeanIX differentiates five phases: Plan, Phase in, Active, Phase out and End of Life. This view can indicate how many Applications were active and how many were phasing in and out at each point in time. You need to be especially aware of the ones marked as the end of life – there might be a severe technology risk!

2. Functional Fit

The view “Functional Fit” refers to an attribute on the Fact Sheet Type Application. In the Functional Fit view, the color of the boxes indicates how well the Business support is. LeanIX differentiates between Unreasonable, Insufficient, Appropriate, and Perfect.
It can help you to identify Applications that need to be replaced or at least worked on since they do not functionally fit their purpose.

3. Technical Fit

The view “Technical Fit” refers to an attribute on the Fact Sheet type IT Component and to an attribute on the Fact Sheet type Application. In the Technical Fit view, the color of the boxes indicates how appropriate an application or technology is from the technical perspective. This means the underlying technology of specific applications might not fit the company’s strategy for example. LeanIX differentiates between Inappropriate, Unreasonable, Adequate, and Fully Appropriate.
Please be aware of what technical fit you are looking at – the technical fit of an Application or the one of an individual IT Component.

4. Business Criticality

The view “Business Criticality” refers to an attribute on the Fact Sheet Type Application. In the Business Criticality view, the color of the boxes indicates how critical/important an application is for your Business. LeanIX differentiates between Administrative Service, Business Operational, Business Critical, and Mission Critical.

5. Obsolescence: Aggregated Risk

The view "Aggregated Obsolescence Risk" allows you to understand the underlying IT components' lifecycle status that supports your applications. With this view, you can understand if your applications are at risk due to any obsolescence of the technical components that are directly or indirectly related to the application.

The calculation for the Aggregated Obsolescence Risk view takes into consideration all the IT components related to an application in the following cases:

  • IT Components directly linked to the Application (relApplicationToITComponent) with an active relation (inactive relations are not considered, view the field active from/until in the relation between IT Components and Applications)
  • IT Components indirectly related to an Application. This means IT components that can be reached via a set of active relations from IT components to other IT components, as hierarchical relations (relToChild) or requires relations (relToRequires). (Excluding the relations of the type requires/required by, between IT Component and Applications)
  • Indirectly connected to the application via another application, with an active hierarchical relation (relToChild).

The order determines the weighting for the applied status Applications.

13831383 15111511

On the relation between Application and IT Component (editable on Application and ITC Fact Sheet) the "Obsolescence risk status" can be classified as accepted or as addressed. Additionally, an “Obsolescence Risk Comment” can be made for documentation.

📘

Information

The field addressed/unaddressed risk can only be filled or changed with the TRM module.

Values

  • Risk accepted: Risk has been assessed and accepted
  • Risk addressed: Risk has been addressed and the ITC will be updated, replaced or removed
16711671

6. Project Risk

The Project Risk is an attribute on the Fact Sheet Type Project. Here it is evaluated if a Project faces low, moderate, high, or severe risk. Depending on the effects on quality, timeline, and/or budget of the Project dedicated management attention and support are needed.

7. Project Status

The Project Status view shows the status of the project of the chosen point in time. If at least one of the projects associated with an application has the status "red" the color of the application is also red. If none of the projects has the status "red", but at least one has the status "yellow" the application appears as yellow. If all projects have the status green, the application is also green. If there are no associated projects the application stays white.

8. Project: Business Value (Budget (OpEx + CapEx))

Capital expenditure and operational expenditure are costs that can be maintained as an attribute on the Fact Sheet Type Project. It can further be broken down at the relation between Projects and Provider to indicate where the money was spent. In the Business Value view, the color of the boxes indicates the overall sum of the Budget.

9. Project: Business Value (NPV)

The Project Business Value indicates the financial improvements that can be achieved by the Project. It also refers to an attribute on the Fact Sheet Type Project. The benefit is maintained as a Net Present Value.

10. Provider Quality

The Provider Quality identifies how well this Provider provides services to your company. LeanIX differentiates between Unreasonable, Insufficient, Appropriate, and Perfect. It can help you to identify Providers that need to be replaced or at least worked on.

11. Provider Criticality

The Provider Criticality identifies the appropriate criticality of the Provider. LeanIX differentiates between Commodity, Operational, Tactical, and Strategic. In combination with the Provider Quality, the view can give you insights where the company relies heavily on specific Providers which do not provide the according to quality and therefore should be replaced.

12. IT Components/Applications: Total annual cost

The Total Cost of IT Components view shows the IT component cost for the different applications. The cost is maintained in a field at the relation between IT Component and Application. LeanIX differentiates between 0 and >600k.

13. Tech Category/IT Components: Resource Classification

The Resource Classification is an attribute at the relation between IT Component and Tech Category. It indicates whether the technology is an approved standard in the company or not. LeanIX differentiates between Unapproved, Retiring, Conditional, Approved, and Investigating.

14. Data Object/ Application: Data Classification

The Data Classification view shows the sensitivity level of the data that is used, manipulated, or utilized by an application. LeanIX differentiates between Public unclassified, Sensitive, Restricted, and Confidential.

Technology Risk Management Report Views

For the Technology Risk Management (TRM) module, three new views are available in the Application Landscape Report. These views are based on the recently introduced field, 'Obsolescence Risk Status', for relations between Applications and IT Components.

15. Obsolescence: Mitigated Risk Percentage

Showing the percentage of relations to IT Components holding the values 'Risk Accepted' and 'Risk Addressed'. As an example, to comprehensively manage risk comprehensively across your application portfolio, you would seek to reach 100% coverage of ‘Risk Accepted’ or ‘Risk Addressed’.

787787

16. Obsolescence: Missing Data Percentage

Displaying the percentage of relations to IT Components without lifecycle information. The color-coding from green to red in this view is inverted compared to the previous view because the goal is to have a low percentage of missing data.

787787

17. Obsolescence: Unaddressed Risk Percentage

Visualizing the percentage of relations to IT Components with lifecycle information in 'Phase out' or 'End of life'. The corresponding Applications are shown on the Application Landscape report in the 'Obsolescence: Aggregated Risk' view with the status 'Unaddressed End of Life' or 'Unaddressed Phase Out'.

787787

Individualized Views

Next to the standard views that LeanIX provides you are able to create your own Attributes and Tag groups that can be applied as views in reports.

👍

Best Practice:

Through searching and filtering you can also tailor the view of reports to your needs. Check out our fundamental filtering functionality for reports as well as additional advanced filter options in LeanIX.


Did this page help you?