In the basic edition of leanIX there are ten different Fact Sheets, namely Application,Data Object, Project, IT Component, Provider, Technoloy Stack, User Group, Business Capabilty, Process and Interface. This article offers the definitions we use for the standard setup of a workspace. If they do not match the definitions of your company, just customize 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 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 “realtime” 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 to make them 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.
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 about 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 model how your applications help you to support your business goals. In contrast to capabilities, they focus on activities. A process in leanIX is a container as leanIX is no dedicated process modelling tool. Close integrations, e.g. to Signavio, are provided.
Interfaces are connections between Applications. They transfer data objects and are implemented via IT components.