Linked.Archi LeanIX Meta Model v4 Ontology

Cross-reference for Linked.Archi LeanIX Meta Model v4 Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi LeanIX Meta Model v4 Ontology.

Classes

Application
Business Application
Business Capability
Business Context
Categorization
Data Object
Data Usage
Deployment
Driving
Fact Sheet
Impact
Initiative
Interface
Interface Ownership
IT Component
Microservice
Objective
Organization
Organization Unit
Organizational Usage
Platform
Process
Product
Provider
Provision
Requiring
Supporting
System (optional)
Tech Category
Value Stream

Application^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Application

Applications are the software systems or programs that process or analyze business data to support business tasks, processes, or aspects of your organization's business model. They are the central entities in SAP LeanIX because they link business and IT.

Example

"SAP S/4HANA Finance" or "Salesforce Sales Cloud" represented as Application fact sheets.

has super-classes: Fact Sheet ^c
has sub-classes: Business Application ^c, Deployment ^c, Microservice ^c

Business Application^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessApplication

Application subtype representing business‑facing applications used directly by end users in business processes.

Example

A "CRM Core" system used by sales representatives to manage opportunities.

has super-classes: Application ^c

Business Capability^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessCapability

Business capabilities (also called domains) model what your applications do to support your business goals.

Example

Business capabilities like "Customer Management", "Order Processing" that model what applications do to support business goals.

has super-classes: Fact Sheet ^c

Business Context^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessContext

Business contexts capture the specific activities your organization performs to achieve its business goals.

Example

Activities like "Customer Onboarding", "Order Fulfillment" that your organization performs to achieve business goals.

has super-classes: Fact Sheet ^c
has sub-classes: Process ^c, Product ^c, Value Stream ^c

Categorization^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Categorization

A categorization relationship from an IT component to a tech category.

has super-classes: qualified relationship ^c
is in range of: qualified categorized by ^op

Data Object^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#DataObject

Data objects provide an overview of general data processed and exchanged by specific applications.

Example

General data like "Customer Profile", "Invoice Data" processed and exchanged by applications.

has super-classes: Fact Sheet ^c

Data Usage^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#DataUsage

A usage relationship from an application to a data object.

has super-classes: qualified relationship ^c
is in range of: qualified uses data ^op

Deployment^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Deployment

Application subtype representing a concrete deployed instance or environment of an application, such as production or test.

Example

"CRM Core – Production (EU)" and "CRM Core – Test" modeled as Deployments of the same logical application.

has super-classes: Application ^c

Driving^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Driving

A driving relationship from an objective to an initiative.

has super-classes: qualified relationship ^c
is in range of: qualified drives ^op

Fact Sheet^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#FactSheet

Abstract supertype for all LeanIX fact sheet instances in Meta Model v4.

Example

Any Application, Business Capability or Platform fact sheet is also an instance of :FactSheet.

has super-classes: element ^c
has sub-classes: Application ^c, Business Capability ^c, Business Context ^c, Data Object ^c, IT Component ^c, Initiative ^c, Interface ^c, Objective ^c, Organization ^c, Platform ^c, Provider ^c, System (optional) ^c, Tech Category ^c

Impact^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Impact

An impact relationship from an initiative to an application.

has super-classes: qualified relationship ^c
is in range of: qualified impacts ^op

Initiative^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Initiative

Initiatives capture the planned projects or programs within your organization that impact its enterprise architecture and are aimed at achieving specific goals or objectives.

Example

"ERP Consolidation Program 2026–2028" that rationalizes the finance application landscape.

has super-classes: Fact Sheet ^c

Interface^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Interface

Interfaces are the connections between applications that illustrate how data exchange occurs.

Example

An "Order export API" interface between an e‑commerce front end and the ERP system.

has super-classes: Fact Sheet ^c

Interface Ownership^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#InterfaceOwnership

An ownership relationship from an application to an interface.

has super-classes: qualified relationship ^c
is in range of: qualified has interface ^op

IT Component^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#ITComponent

IT components represent the technology or services that your applications depend on. They can provide information on both development and operations. They are used to model operating costs as well as technological risks.

Example

"PostgreSQL 15", "Kubernetes cluster", "Azure Functions" or "Red Hat Enterprise Linux" modeled as IT Components.

has super-classes: Fact Sheet ^c

Microservice^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Microservice

Application subtype representing a fine‑grained, independently deployable service that contributes to a larger application or platform.

Example

Microservices such as "Pricing Service", "Customer Profile Service" or "Notification Service" used by multiple channels.

has super-classes: Application ^c

Objective^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Objective

Objectives capture the goals that your organization aims to achieve. These drive initiatives to improve business capabilities and transform the IT landscape.

Example

"Reduce IT run cost by 20% by 2027" modeled as an Objective.

has super-classes: Fact Sheet ^c

Organization^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Organization

Organizations represent your organization's hierarchical business architecture, detailing departments and teams.

Example

Departments like "Finance", "Sales EMEA" or teams like "IT Operations" that represent hierarchical business architecture.

has super-classes: Fact Sheet ^c
has sub-classes: Organization Unit ^c

Organization Unit^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#OrganizationUnit

Subtype of Organization used for internal structures such as departments, teams or cost centers.

Example

"Accounting Shared Services" team within the Finance organization modeled as an OrganizationUnit.

has super-classes: Organization ^c

Organizational Usage^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#OrganizationalUsage

A usage relationship from an organization to an application.

has super-classes: qualified relationship ^c
is in range of: qualified used by org ^op

Platform^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Platform

Platforms are groupings of business capabilities, applications, and technologies that provide common functionalities.

Example

Platforms like "Customer Data Platform" that group capabilities, applications and technologies providing common functionalities.

has super-classes: Fact Sheet ^c

Process^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Process

Repeatable sequence of activities or tasks that realizes one or more value stream stages and capabilities.

Example

Processes such as "Create Customer Invoice", "Approve Purchase Order" or "Handle Returns".

has super-classes: Business Context ^c

Product^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Product

Market‑facing or internal product or service bundle that is offered to customers or users.

Example

"Gold Credit Card", "Premium Current Account" or "Field Service Mobile App" modeled as Products.

has super-classes: Business Context ^c

Provider^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Provider

Providers are the companies or entities that supply IT solutions, services, or technologies to support your organization in achieving its objectives and operational efficiency.

Example

External providers such as "SAP", "Salesforce", "Microsoft Azure", or an internal "Shared Services IT" provider.

has super-classes: Fact Sheet ^c

Provision^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Provision

A provision relationship from an IT component to a provider.

has super-classes: qualified relationship ^c
is in range of: qualified provided by ^op

Requiring^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Requiring

A dependency relationship from an application to an IT component.

has super-classes: qualified relationship ^c
is in range of: qualified requires ^op

Supporting^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Supporting

A supporting relationship from an application to a business capability.

has super-classes: qualified relationship ^c
is in range of: qualified supports ^op

System (optional)^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#System

Systems represent the technical environment underlying applications, such as a server or virtual machine with its operating system, database, runtime configurations, and more.

Example

"SAP ERP Central System (ECC PROD)" modeled as a System composed of several applications and technologies.

has super-classes: Fact Sheet ^c

Tech Category^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#TechCategory

Tech categories are used to group IT components into different categories of technology.

Example

Technology categories like "Database", "Middleware", "Cloud Platform" used to group IT components.

has super-classes: Fact Sheet ^c

Value Stream^c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#ValueStream

End‑to‑end sequence of stages that collectively create value for an internal or external customer.

Example

Value streams such as "Lead to Cash", "Idea to Market" or "Acquire to Retire".

has super-classes: Business Context ^c

Object Properties

Categorized By
Drives
Has Interface
Impacts
Provided By
qualified categorized by
qualified drives
qualified has interface
qualified impacts
qualified provided by
qualified requires
qualified supports
qualified used by org
qualified uses data
Requires
Supports
Used by Organization
Uses Data

Categorized By^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#categorizedBy

IT component is categorized by a tech category.

Drives^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#drives

Objective drives an initiative.

Has Interface^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#hasInterface

Application has an interface.

Impacts^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#impacts

Initiative impacts an application.

Provided By^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#providedBy

IT component is provided by a provider.

qualified categorized by^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedCategorizedBy

has range: Categorization ^c

qualified drives^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedDrives

has range: Driving ^c

qualified has interface^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedHasInterface

has range: Interface Ownership ^c

qualified impacts^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedImpacts

has range: Impact ^c

qualified provided by^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedProvidedBy

has range: Provision ^c

qualified requires^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedRequires

has range: Requiring ^c

qualified supports^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedSupports

has range: Supporting ^c

qualified used by org^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedUsedByOrg

has range: Organizational Usage ^c

qualified uses data^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedUsesData

has range: Data Usage ^c

Requires^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#requires

Application requires an IT component.

Supports^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#supports

Application supports a business capability.

Used by Organization^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#usedByOrg

Application is used by an organization.

Uses Data^op back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#usesData

Application uses or processes a data object.

Legend back to ToC

^c: Classes
^op: Object Properties

Linked.Archi LeanIX Meta Model v4 Ontology

Release: 2025-01-01