Users are allowed to select from a range of distinct Views when generating a report. Views are essentially attributes or relations, which are represented through a color-coded visualization. Each view provides a unique perspective on the data, enabling the user to gain better insights. Report views are selected from the View dropdown box on the report and can be based on the following:
- 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 in a relation between the base Fact Sheet Type and a related Fact Sheet, e.g., the Total annual cost attribute is stored in 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 - User-defined Tags. You can define tag colors in the Administration section.
In the Lifecycle view, the color indicates the current Lifecycle status of the Application, IT Component, or Project. LeanIX differentiates five phases: Plan, Phase in, Active, Phase out, and End of Life. This view can indicate how many Applications are active and how many are phased in and out at any 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!
The view Functional Fit refers to an attribute on the Fact Sheet Type Application. In the Functional Fit view, the color classifies how well the application supports a Business function. 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.
The view Technical Fit refers to an attribute on the Fact Sheet types IT Component and on the Fact Sheet type Application. In the Technical Fit view, the color of the boxes indicates how appropriate an application or IT component is from the technical perspective. For example, maybe an underlying technology of a specific application fits or doesn’t fit the company’s strategy. 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 that of an individual IT component.
The view Business Criticality refers to an attribute on the Fact Sheet Type Application. In the Business Criticality view, the color differentiates how critical an application is for your Business. LeanIX has the following classifications for Business Criticality: Administrative Service, Business Operational, Business Critical, and Mission Critical.
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 way:
- 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 are indirectly related to an Application. These are the IT components that can be related 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.
The field addressed/unaddressed risk can only be filled or changed with the TRM module.
- Risk accepted: Risk has been assessed and accepted
- Risk addressed: Risk has been addressed and the ITC will be updated, replaced, or removed
The Project Risk is an attribute on the Fact Sheet Type Project. It evaluates if a project faces low, moderate, high, or severe risk. Depending on the effects on the quality, timeline, and/or budget of the project dedicated management attention and support are needed.
The Project Status view shows the status of the project at 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.
Project: Business Value (Budget (OpEx + CapEx))
In the Project Portfolio Report, you have a view of your Capital expenditure and Operational expenditure. These 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.
Project: Business Value (NPV)
In the Project Portfolio Report, 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 in Net Present Value is classified into Marginal benefit, Little benefit, Large benefit, and Significant benefit.
The Provider Quality identifies how well a certain 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.
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 into where the company relies heavily on specific providers which do not provide the quality required and therefore should be replaced.
IT Components/Applications: Total annual cost
The Total Cost of IT Components view shows the IT component cost for the different applications. The cost information is maintained in a field at the relation between IT Component and Application. The color gradation deepens as the cost increases.
Tech Category/IT Components: Resource Classification
The Resource Classification is an attribute of the relation between the 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.
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.
For the Technology Risk Management (TRM) module, three new views are available in the Application Landscape Report. These views are based on the field Obsolescence Risk Status, for relations between Applications and IT Components.
Obsolescence: Mitigated Risk Percentage
The view Obsolescence: Mitigated Risk Percentage shows the percentage of relations to IT Components holding the values Risk Accepted and Risk Addressed. As a best practice, to manage risk comprehensively across your application portfolio, you would seek to reach 100% coverage of Risk Accepted or Risk Addressed.
Obsolescence: Missing Data Percentage
The view Obsolescence: Missing Data Percentage displays 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.
Obsolescence: Unaddressed Risk Percentage
This view visualizes 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.
In addition 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.
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.
Views within our system can employ either a 1:1 mapping to the displayed Fact Sheets or a form of aggregation. For instance, each Fact Sheet correlates directly with a specific lifecycle in the lifecycle view. On the other hand, we utilize Fields on relations or Fields on related Fact Sheets to map one Fact Sheet to multiple target Fact Sheets. To visualize this view and its associated color, it's necessary to define a specific form of aggregation.
The chosen aggregation approach hinges on the nature of the data and the customer's preference. For categorical views, we might want to display the "best" or "worst" value. When working with numerical fields, we could aggregate values to their sum or average. While default aggregation values can be changed within the data model according to the customer's needs, an additional dropdown provides comprehensive control over the chosen view aggregation.
This chosen view and aggregation setting can be saved to a bookmark. This feature ensures that only relevant options are displayed: sum/average options for numerical fields and min/max for categorical fields. This streamlined interface enhances usability, only seeing the applicable options for their selected view. If a view is changed, its default value configured in the data model is applied until the user decides to change the applied aggregation via the dropdown. If a view is saved with its default from the dropdown applied, saves to a bookmark, and changes the default within the data model, the new default is respected on reloading the report with the bookmark.
This way, our system offers flexibility and customization while maintaining a clear and intuitive interface.
In addition to the aggregation options, the dropdown menu offers an enhanced feature that extends the customization via the data model. This additional feature allows you to select a specific target Fact Sheet. This option bypasses the aggregation process altogether, providing a direct way to illuminate the value of the view for the chosen target Fact Sheet exclusively.
By selecting a related Fact Sheet, you can gain detailed insight into a particular data point without the distortion of aggregated data. This feature can be particularly beneficial when you want to isolate and scrutinize one aspect of their data, sidestepping the broader perspective typically provided by aggregation.
To select a related Fact Sheet, you can navigate through the dropdown menu, select the third option, and choose their desired Fact Sheet from the available options of the Fact Sheet Selector. The view then updates to reflect the view value of the chosen Fact Sheet. This selected view, similar to aggregation settings, can also be saved to a bookmark for future reference, and changes to the target Fact Sheet (such as adding/removing relations or changing its display name) are updated in the bookmark as well.
This feature represents another step in our commitment to offering flexible, user-oriented data management tools. By providing the ability to select a related Fact Sheet directly, we further empower you to control their data views and gain insights relevant to their unique needs.
Updated 2 months ago