LeanIX Basics
Out-of-the-Box & extensible EA data model
* At every Fact Sheet
Strategy & O P • Tagging
Transformation Objective Project
• Hierarchies
• Documents
• Relations
Business U B P • Audit Trail
Architecture User Group Business Process • Subscriptions
Capability
• Metrics (Time-series)
• Survey-Results
Application & Data D A I Extensible via Configuration
Architecture Data Object Application Interface • Attributes
• Relations
• New Fact Sheet Types
• Authorization
Technical P I T
Architecture Provider IT Tech
Component Category
4
* Becomes part of the OOTB data model and available via self-service in Q1/2022. Available on demand via www.leanix.net/support until then.
Fact Sheet type descriptions
• An Application is something that is visible to • Interfaces are connections between Applications.
A the end user. I
• They transfer Data Objects and are implemented
Application • It is the core Fact Sheet type of LeanIX. Interface via IT Components.
• Business Capabilities are serving as a placeholder
• A Data Object reflects information about important
B to reflect the primary dimension of the needs of the D business items (e.g., account, employee).
business.
Business Data Object • Can be linked to Applications and Interfaces, and
Capability • These can be capabilities, process groups,
stores additional information on data sensitivity.
functional building blocks or anything else.
• An IT Component can be a service, software or
U • A User Group represents the consumer or provider I hardware. Anything that you need to offer an
of Applications.
User Group IT Application.
• Can be a single person, a country, an organization, Component
• Has a lifecycle for risk and succession management,
a subsidiary or a certain location.
contains cost per Application and has a Provider.
More information in the LeanIX User Documentation: https://docs.leanix.net/docs/what-is-a-factsheet 5
Fact Sheet type descriptions
• Processes show how you perform certain activities
• The Provider is connected to Projects and IT in your organization.
P Components to get an overview of provided services P
and total cost of services. • Close integrations are provided to incorporate the
Provider Process
full functionality of a modern process modeling tool.
• Tech Categories are used to group IT Components
P • With a project Fact Sheet you can manage or build
T into different categories of technology (e.g.,
budgets, reflect a project status, and show the
database, web server).
Tech Category Project impact of a project on your Application Portfolio and
• It is used to make IT Components comparable and their affected User Groups
visualize the technologies and services used.
• Objectives allow high-level definitions and progress
O
tracking of transformation initiatives and can be
Objective linked to Business Capabilities.
More information in the LeanIX User Documentation: https://docs.leanix.net/docs/what-is-a-factsheet 6
Establish an Application definition that fits your
environment based on best practices
Attributes Recommendations
A
• Processes or analyzes business data • Business first: The application
Application
list needs to be understandable by
• Relies on IT components (software, everyone
hardware or service) to function • Be realistic: If an XLS or a
Sharepoint application is
• Supports business tasks, processes, or supporting your business, it‘s
aspects of your operating model likely an application
• Provides specific business capabilities to • Keep it simple: Use hierarchies
your organization only when really needed. Don‘t be
shy to leave out modules or other
details at least for the start
• Make clever use of tags:
Aspects like hosting or PII can
start as tag groups and evolve
later
7
Understanding how to approach IT Components
Attributes Recommendations
I
• Manages technological risks caused by • Use-Case first: It‘s easy to get lost in
IT Component
obsolete supported SW/HW the details – only maintain ITCs in
LeanIX that add value
• Runs, maintains or changes an • LeanIX is not a CMDB: As rule of
application (per definition on previous thumb, it is recommended to work with
slide) abstraction / product models, not
instances
• Utilizes the technology category to
manage standards • Be careful with relations: IT
Components can be interlinked via a
• Maps annual IT run costs to their “parent / child” and “requires / required
respective application by”, but often there is an easier way
• Build-up blueprints: Use typical
settings / examples to establish a
standardized view throughout your
organization
8
An illustrative comparison of Applications and IT Components
according to our best practices
Example Categories
System Software /
Application1 Application Platform / Tool2 Hardware4
Technology Service3
Factsheet Type
A
Application
I
IT Component
• Generally, there are clear best practices when modeling Applications and IT Components
• However, in certain cases, e.g. Robotic Process Automation, can be modeled as either an Application
or an IT Component and should be modeled based on a holistic, use case-based assessment
• For more information on modeling or regarding specific questions, please reach out to your CSM
Examples:
1. Enterprise suites, ERP Systems…
2. Robotic Process Automation, Test Automation…
3. Operating Systems, Databases, Virtual Machines…
4. Laptops, Desktop Computers, Servers, Mobile Devices… 9
Possible Subscription Roles and Types
Company Dedicated Subscription Authorization Fact Sheet Type
Description
Position Subscription Roles Type Role to be subscribed
The Enterprise Architect has complete overview in LeanIX. The
Enterprise
• Enterprise Architect EA is empowered to align the IT strategy with company Accountable Admin All
Architect
mission.
The Application Owner is the one responsible for the
• Application Owner
Application Application, usually he is from the department that uses the
• Service Owner Accountable Member Application
Owner Application most. The Application Owner is held accountable
• Product Owner
for budget and E2E process.
• Application The Application Architect is responsible for running the
Application Architect application in alignment with the requirements of the
Responsible Member Application
Architect • Application Application Owner. In addition to development and
Manager maintenance, this also includes support and advice.
The Domain Architect is responsible for the entire architecture
stack of a defined domain (e.g. one Business Capability). He
has a holistic view on the activities and all architecture
Domain • Domain Architect
information in the domain, is involved in planning activities and Responsible Member Business Capability
Architect • Business Architect
approves essential architecture decisions for the domain in
question. The Domain Architect is dependent on the knowledge
/ input of the Application & Technology Architects.
11
Possible Subscription Roles and Types
Company Dedicated Subscription Authorization Fact Sheet Type
Description
Position Subscription Roles Type Role to be subscribed
The Data Architect defines and maintains the data model that is
used for EA purposes. Since the level of detail often depends
Data on the use case, the Data Architect works closely together with
• Data Architect Responsible Member Data Object
Architect his most important stakeholders (e.g. the data protection
officer) to define a model. He also knows which data is
processed in which system and defines their operations.
The Technology Architect ensures that the IT components for
each Application are defined, categorized, maintained and
Technology • Technology ITC & Tech
planned. His job is to ensure the current state of the art, which Responsible Member
Architect Architect Category
is consistent with the technology target architecture, the
provider service and the applicable regulations.
The Domain Architect ensures that the IT-Components for
every Application are defined, categorized, maintained and
Domain ITC & Tech
• IT Business Analyst planned. His/her mission is to ensure state-of-the art Responsible Member
Architect Category
Technology that is in line with the Technology Target
Architecture, within provider service, and valid regulations.
The main tasks of the Integration Architect are to maintain an
Integration • Integration efficient technical environment for all customer services,
Responsible Member Interfaces
Architect Architect document all architectural plans, as well as provide support for
all functions and the installation of system components.
12
Possible Subscription Roles and Types
Company Dedicated Subscription Authorization Fact Sheet Type
Description
Position Subscription Roles Type Role to be subscribed
• Security Officer The Security Officer combines the roles of the Data Protection
• Data Protection Officer and the Information Security Officer. He is responsible
Security
Officer for compliance with regulations and laws, identifies and Observer Viewer All
Officer
• Information Security eliminates potential security risks and is available to the
Officer company as an advisor on security issues.
All managers who need insight into the LeanIX landscape for
Manager - Observer Viewer All
reporting, transparency and decision making reasons.
Business
- The business user can be any employee in the company. Observer Viewer All
User
13
