<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_NEW_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-01-20T13:15:11.000Z

The LeanIX meta model

<div id="content"><p tabindex="0">The next video introduces you to the LeanIX meta model, the heart of LeanIX. Understanding LeanIX's meta model is essential for comprehending how LeanIX operates and how to best store data within it.</p><div class="kalturaVideoLessonWrapper"><div aria-label="Meta model overview" class="kalturaVideoLessonContainer" data-testid="video" id="1_1pcq9l3x"></div></div></div>

Meta model overview

Learning to Use the LeanIX Tool for Successful Enterprise Architecture

Learn about the heart of Linux and its predefined meta model, which provides a fast time to value for your organization's enterprise architecture work. Discover the structure, fact sheets, and insights that Linux offers.<br><br># This description was auto-generated #

7. LeanIX EAM Meta Model.mp4

The heart of Linux is the predefined meta model, which provides a fast time to value to start and maintain your organization's enterprise architecture work with Linux. In general, a meta model is a foundational framework to describe and define various components, relationships and principles that make up the architecture of an organization. Our Linux meta model is based on best practices and knowledge from our work with more than a thousand customers. and gives a clear guidance on documenting all elements of your organization's enterprise architecture. Following our modeling guidelines allows your organization to capture the architecture according to the highest standards and get all the insights you need using our Linux reports and diagrams. We recommend our customers to stay with the default or close to the default meta model that is lean and non-complex. Let's look into the basic structure of the meta model. You can see four layers representing different aspects of the enterprise architecture from a more business-driven view down to a technical view. Strategy and transformation, business architecture, application and data architecture, and the technical architecture. For each layer, there's a defined set of fact sheets that have their specific attributes to capture relevant information. We will dive deeper into the Meta model in the Level 2 Practitioner course, but there are some key aspects you should know for a successful start. The Linux Meta model is application-centric. Applications are a key component, and they have relations to all the layers in the Meta model. Having well-documented applications is of high relevance for all reports and insights you want to create in Linux. To get your first insights through reports, we recommend Linux customers to start their journey, at least with modeling and maintaining three fact sheet types. Application, business capability, and organization. Relations between the fact sheet types determine how you will be able to connect your information and use it in your reports. Some of the relations between fact sheets are indirect. For example, in order for the provider to be linked to the business capability, it would first have to be linked with an IT component, and then to an application, and then finally to the business capability itself. As an admin, you should know that this meta model is already implemented out of the box when you start working in your Linux workspace. You can go ahead and import data based on the predefined meta model. As a business user, for example, an application owner, you should understand what an application is exactly and which information you need to fill the application fact sheet with. You should also understand how to link applications to the other important fact sheet types and leverage Linux to get insights about your application and its dependency on others. We will cover this in a later session. While the metamodel is configurable, it's crucial to understand the implications of any change. Each modification could affect your modeling practices and reporting, potentially impacting future use cases. If you consider extending the metamodel, feel free to discuss and validate the desired configuration with your customer success manager. We will discover the metamodel and the rest of the fact sheets in another course, where we will explore more advanced topics such as modeling guidelines and the metamodel configuration.