Reporting is the most important feature in modern EA software. We at LeanIX believe that a powerful and flexible way to show what you have or plan in your architecture is crucial in addressing your stakeholder’s concerns. Therefore we have added the most important reports in our report section everyone needs for his daily architecture work.
This page shows you:
- How to use LeanIX reporting
- Which standard reports are available
- How to use Filter & Views to create your individual report
- How to save reports
- How to use the Visualizer
- How to work with Custom Reports
Any LeanIX user will find the pre-defined reports in the reports menu.
The menu bar with available reports appears when clicking on the diagram symbol.
You may select any available report from there. Also, you can switch between the graphical view and table view for each report. The table view lists the contained objects as simple table without the heatmap information. The graphical view allows heat maps to identify objects fulfilling the (pre-)selected filter criteria.
LeanIX standard reports do not need to be computed in a query language to extract data from the data source. All reports can be selected from the report menu. LeanIX provide three different types of reports:
- Heat Maps
The Heat Map represents an at least two-dimensional relation between architectural objects. For example, it links applications with business capabilities, platforms with IT components or applications with information flows. More important, the user can select between various filter options to create a heat map with a particular focus. For example, he might be interested in all applications at the end of their life.
The Matrix reports are two dimensional matrix relating two different types of objects via a common denominator. For example, the Application Matrix, links business capabilities and user groups via the usage of and support by an application answering which user group uses which application for which purpose (functionality).
The Roadmap visualizes time-bound information. In particular, a visual, Gantt chart like representation of the lifecycle of applications, projects or IT components is available.
- Functional Fit / Technical Fit: The Application Portfolio is a matrix report that groups Applications according to their functional and their technical suitability. It can help you to identify Applications that need to be replaced or at least worked on.
- Functional Fit/ Business Criticality: The Application Portfolio is a matrix report that groups Applications according to their Functional Fit and their Business Criticality. It can help you to identify Applications that need to be replaced or at least worked on.
- Technical Fit / Business Criticality: The Application Portfolio is a matrix report that groups Applications according to their Technical Fit and their Business Criticality. It can help you to identify Applications that need to be replaced or at least worked on.
- Project Value / Project Risk: The Project Portfolio is a matrix report that groups Projects according to their value and their risk. It can help you to identify Projects that need to be stopped or at least being reviewed.
- Provider Criticality / Provider Quality: The Provider Portfolio is a matrix report that groups Providers according to their criticality and their quality. It can help you to identify Providers that need to be replaced or at least worked on.
Lifecycle & Age
- Active: The Active view indicates how many Applications you used (were active) and how many were phasing out at each point in time.
- Age Structure: The Age Structure gives you an overview of how "old" your current active Applications are. It shows how many of the current active Applications entered the status "active" each year.
This report gives you an overview of your IT landscape at a certain point of time or in a time frame. It shows you the IT support of your Business Capabilities.
- Lifecycle: In the Lifecycle view the color of the boxes indicates the current status of the application. leanIX differentiates five phases: plan, phase in, active, phase out and end of life.
- Business Criticality: 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.
- Functional Fit: 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.
- Technical Fit: In the Technical Fit view the color of the boxes indicates how appropriate an applications is from the technical perspective of view. leanIX differentiates between Inappropriate, Unreasonable, Adequate and Fully Appropriate.
- Project Status: The Project Status view shows the status of the, with each application, associated projects. If at least one of those associated project 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.
- Total Cost of IT Components: The Total Cost of IT Components view shows the IT component cost for the different applications. leanIX differentiates between 0 and >600k.
- 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: The Technology Risk view is based on the life cycle status of the used IT Components. If one application uses a component that has already the status "end of life" the application is marked "red". If none of the used components has the status "end of life", but one is in "phase out" it, the application appears "yellow". If all used components are still active the application is green and if there are no entries for the used components it stays white.
You do have the same views in the Interface Map and the Application Matrix. These are the out of the box views. In many views you can also filter for your individual tag groups.
The Application Roadmap generally gives an overview of the lifecycle time frame of all applications. You are able to see very quickly when did we start using an application and till when are we planning to use it.
- Successor: In the Successor view the preceded and the following Application are grouped together. The darker "+"-symbol indicates which application has a Successor and by clicking on it you make them visible.
- Children: In the Children view you can see the hierarchies of an application. The darker "+"-symbol indicates which application has a Child and by clicking on it you make them visible.
- Related Projects: In leanIX projects can be linked to applications. In the view Related Projects the darker "+"-symbol shows which application has related project , just click on it you will see which those are and what the project lifecycle looks like.
- Related IT Components: A lot of applications are using IT Components. The view Related IT Components shows which application is using which IT Components and what is the roadmap for those IT Components.
The Project Roadmap generally gives an overview of the time frame of all projects. It shows which projects are currently running, which are planned and which are already closed.
- Successor: Projects are often part of a larger program, which also means that they can have follow-up projects. Again the Successor view groups original project and follow-up project together.
- Children: In the Children view you can see the hierarchies of a project. The darker "+"-symbol indicates which project has a Child and by clicking on it you make them visible.
- Related Applications: This view shows which Applications are affected by a a project.
IT Component Roadmap
The IT Component Roadmap generally gives an overview of the lifecycle time frame of all IT Components. It works analog to the Application Roadmap.
- Successor: In the Successor view the preceded and the following IT Components are group together. The darker "+"-symbol indicates which application has a Successor and by clicking on it you make them visible.
- Children: In the Children view you can see the hierarchies of an IT Component. The darker "+"-symbol indicates which IT Component has a Child and by clicking on it you make them visible.
- Related Applications: The view Related Applications shows which Applications are using an IT Component.
- Business Capability Cost: This report gives you an overview of which Business Capabilities are supported by which applications and how much does this support costs you annually. It helps you to understand the cost allocation per business capability and to analyze where costs could be reduced.
- Provider Cost: In this report you can see the cost allocation per provider.
- Project Cost Tracking: This report shows you the costs of the different projects. It helps you to understand how your budget is consumed by the different projects and it gives you control over project budget and project cost.
As all LeanIX reports are interactive, you have three different options to create your individual report within a few seconds:
- Apply Filter
- Adjust View
- Apply further report-specific configuration
For all reports, the same filter functionality is available as in the Find Fact Sheets in the Inventory. You can use both the filter facets on the left hand side and the filter bar on top.
Additionally, we introduced our smart search also for Reports.
Since Pathfinder, we cleaned up the way to filter reports for multiple Fact Sheets. Every report has a dropdown on the top left that allows you to filter precisely by your criteria:
Application Matrix: Here you can filter by Application or by the configured axes (Business Capabilities, User Groups or Processes, see below). There is a small, but decisive difference in the way you apply filter:
- Filter for Applications - All Applications which support Business Capability HR: Doing so shows you all Applications which support HR. However if Application A1 supports also CRM, CRM is shown as well, as the Filter is applied by Application
- Filter for Business Capability - All Business Capability with parent HR: Here only the column HR with its children are shown, no other columns (e.g. CRM)
- Interface Circle Map: You can either filter by Interface (e.g. all Interfaces with a certain technology) or by Application (e.g. all Applications within a certain Business Capability).
A view requires defined Tags or other defined dependencies for the contained objects. For example the Applications in the Application Landscape report can obtain different color codings for the Tags “Product Catalog” or “SLA”. Further Tags constellations / settings are available once defined.
For example the total number of objects can be further filtered by clicking on the magnifier icon in the menu bar. If (!) data is defined, the number behind each filter indicated how many objects fulfill the criteria. If the filter is not available, it is indicated by (0). You may adjust the order of elements via X and use the drag’n’drop functionality to re-arrange the filter options according to your needs.
Filtering by Tags is also available for your own defined tags and tag groups. Please refer to the Inventory & Fact Sheet section for further information on tags. If you have defined your own tag you can use these tags to create your own, individual heatmap.
The cluster map can be further adjusted in the menu. You may change between the elements on the x-axis. In the Application Matrix, the selection of User Groups or Business Processes is alternatively available since both (and Business Capabilities) are linked to applications.
For those objects which are not linked, you may exclude them from your view by enabling the “Hide empty clusters” which is already set by default.
On the right hand side you can navigate through the report. You can change the order of appearance of objects (e.g. sorting, legend), the levels to be shown (you can select from the highest to the lowest available level) and you can zoom in and out. The zoom function only zoom in and out in the reports, while the browser integrated zoom zooms into the overall website. Alternatively you may also enlarge the browser window vertically. Tip: Once you print or export a report, the selected / filtered part / content / level of the report is printed or exported.
Since we know that the combination of the various options allows a nearly endless options to adjust the reports we provide a “Save-As” function to save all filter settings and to share the report with other LeanIX users. The Save Report option is available just below the user profile button.
LeanIX offers many ways to display reports outside the system.
The Advantage is that user can display and use reports flexibly in different ways.
- Open a Report
- click in the upper right (next to "save") at "[...]"
- There are 4 options
Just click on "Export" and then you can Download the file
If you choose to export a report as PDF, you will have the choices of selecting Format (Letter, A0-A4) and Orientation "Landscape or Portrait".
*Landscape: This is best used when...
- something "across" should be displayed
- Reports that already need a lot of space "across".
*Portrait: useful and best when...
- something "upright" should be displayed
- e.g. smaller reports
- e.g. you want to display small tables from a report.
-> a new tab opens, you can download it
- Click on "Export as embedded code"
- Click on "copy" to select the displayed code sniplet
You can embed this code as an iframe in a website or your companies wiki (e.g. sharepoint). Be aware that the embedded iframe always refers to the respective bookmark.
In case you are using Confluence and want to embed reports you can use our native integration to publish real-time reports.
For all relations to fact sheets, the following rule must be observed with regards to the Application Landscape: (Example User Group "A" Relation to Application "B")
Relations (e.g. user group "A") must be in the same period as the lifecycle of the fact sheet (application "B") so that they are displayed in the landscape. (Example View "User Groups: Functional fit)
If the relation Lifecycle falls out of the life cycle of the application, they are not displayed in the Matrix.