Fact Sheets are the central element in LeanIX. They are used to document and save information regarding architectural objects like e.g. Applications, Business Capabilities or IT-Components. With a Fact Sheet, you keep all relevant information on a "one-pager" and maintain the dependencies within your IT landscape.
Head: Offers you the opportunity to subscribe to the current fact sheet and add a new open comments or documents. It also shows you all available reports and the change history of the current fact sheet. Besides the Fact Sheet Name and Type, the header contains Tags and Data Quality Information.
Body: Contains all the relevant information for a Fact Sheet (e.g. lifecycle, criticality, dependencies). It is structured in sections so you can easily find, add or update the information you are looking for.
Sidebar: Includes basic actions like edit, print, delete and clone the Fact Sheet. It also tracks the last Fact Sheets you visited, which enables you to navigate faster back and forth between different Fact Sheets.
As not all attributes and values might be obvious to you, at first sight, there are little help texts provided. The help texts are also provided for more detailed information, e.g. values in drop-down menus.
Every architectural object (Application, Business Capability, Project,…) is stored in a individual template according to its Fact Sheet Type. For example the Fact Sheet Type "Data Object" has a Data Management section, while a Fact Sheet Type "Project" has a Project Environment and Project Setup section.
You can access the Fact Sheets Types on the upper left Side of the Inventory.
According to LeanIX standard Data Model (see the end of this section) there are ten types of Fact Sheets. The following overview provides the definitions we use for the standard setup of a workspace. If they do not match the definitions of your organization, it is possible to configure the workspace to your needs.
The Application is the major element in LeanIX which is interconnected to many different Fact Sheets. In some companies, they call it Solution, IT System or even Service. An Application should be something which is visible to the end user. For the information flow between Applications, there are interfaces connecting them.
A Data Object reflects information about important business items. This could be data of the kind account, employee or organization. A Data Object Fact Sheet can be linked to Applications and Interfaces and stores additional information about data sensitivity. A good use of the Data Object is when you want to manage data sensitivity or manage consistency of business information. Where do we use data of a special sensitivity level?
With the Project Fact Sheet, you can manage to build budgets, project status and show the impact of a project to your Application Portfolio and their affected User Groups. In addition orders of each provider can be managed to get a good overview of the real budget status. Cost center and controlling reports very often show only after the fact events, so it is not too bad to keep a “real-time” eye on where you spend your money.
An IT Component can be a service, a software or hardware, anything you need to offer an Application. An IT Component has a lifecycle for risk and succession management, contains cost per Application for cost management and has a Provider. You should consider your internal services as an IT Component. With this approach, you can make the cost of your IT management effort visible.
The Provider is connected to Projects and IT Components to get an overview of provided services and total cost of services.
The Technology Stack is used to group IT Components into different categories of Technology. This could be e.g. a Database, an Operating System or a Web Server. The Tech Stack is used to make IT-Components comparable and visualize the used technologies and services. This is very helpful to identify redundant or out-of-lifecycle IT-Components. Another use case is to see what kind of know-how about certain technologies or programming languages is necessary to maintain your IT portfolio.
Since a Technology Stack can be seen as a rather stable structure, it will look pretty similar for different companies. If you want to start classifying your IT-Components using a Tech Stack you should have a look at our Best Practice Technology Stacks.
A User Group represents the consumer of Applications. A User Group can be a single person, a country, an organization, a subsidiary, a certain location. Every consumer can be created as a User Group. You can even edit several different types of User Groups into LeanIX to view as many dimensions as needed. We do geocode the User Group.
Business Capabilities are serving as a placeholder to reflect the primary dimension of the needs of the business. This can be capabilities, process groups, functional building blocks or anything else. We know that each of the mentioned dimensions is of interest for a company. Our experience is that it is already a challenge to concentrate on one primary dimension.
Processes show how you perform certain activities in your organization. A process in LeanIX is a rather stable container as LeanIX is no dedicated process modeling tool. Close integrations, e.g. to Signavio, are provided to incorporate the full functionality of a modern process modeling tool.
Interfaces are connections between Applications. They transfer data objects and are implemented via IT components.
The following logical data model illustrates the main relations between the Fact Sheets.