The SAP Leanix data model defines standard attributes for each Fact Sheet type to support Enterprise Architecture management. For the Application Fact Sheet, Business Criticality, Lifecycle, and Functional Fit are core, out-of-the-box attributes. These are fundamental for Application Portfolio Management (APM), enabling architects to assess an application's importance to the business, its current stage of life (e.g., active, end-of-life), and how well it meets user requirements. These attributes are crucial for making informed decisions about application investment, rationalization, and risk management.

A. Objective: "Objective" is not a standard attribute of an Application Fact Sheet. It is more commonly associated with a Project Fact Sheet, which details the goals and aims of a specific initiative.

B. Information: "Information" is too generic. In the SAP Leanix model, applications are linked to Data Object Fact Sheets, which represent the specific business information or data that the application creates, uses, or processes.

1. SAP Help Portal

SAP Leanix

Fact Sheet & Relation Types: The official documentation outlines the standard data model. The "Application" Fact Sheet section explicitly details attributes for assessment

including Business Criticality and Functional Fit. The Lifecycle is also described as a fundamental

built-in attribute for all Fact Sheets

with specific relevance to applications. (Refer to the "Application" subsection under "Fact Sheet Types").

2. SAP Leanix

"The Leanix Enterprise Architecture Data Model" (Poster): This official vendor resource visually represents the standard Fact Sheet types and their key fields. The "Application" Fact Sheet clearly depicts fields for Business Criticality

Functional Fit

and the Lifecycle phases.

3. SAP Leanix

"Application Portfolio Management" Documentation: This documentation explains how to use SAP Leanix for APM. It highlights the use of Functional Fit

Business Criticality

and Lifecycle information as the primary data points for creating reports and views (e.g.

Application Portfolio matrix) to drive rationalization decisions. (Refer to sections on "Conducting Application Assessments").

SAP LeanIX provides several features to foster collaboration among users. Collaborative live editing is available within the diagramming tool, allowing multiple users to work on architecture diagrams simultaneously in real-time. The Comments feature enables users to discuss specific Fact Sheets, ask questions, and provide feedback directly on the relevant architectural element, with the ability to @-mention colleagues. Furthermore, users can create To-Dos from comments or directly on a Fact Sheet to assign tasks, set deadlines, and track the completion of work, ensuring accountability and driving the evolution of the enterprise architecture. These three features are central to the collaborative workflow within the SAP LeanIX platform.

B. Zoom call integration: SAP LeanIX does not offer a native, built-in Zoom call integration as a standard collaboration feature. Communication is typically handled through integrations with platforms like Microsoft Teams or Slack.

E. Surveys: While Surveys involve multiple stakeholders, their primary purpose is structured data collection and governance to populate or update the inventory, rather than direct, real-time collaboration and discussion.

1. SAP LeanIX User Documentation

"Collaboration & Notification": This section details the functionality of Comments and To-Dos. It explains how users can "@mention" others in comments to trigger notifications and how comments can be converted into actionable To-Dos assigned to specific users with due dates. (Accessed via the official SAP Help Portal for LeanIX).

2. SAP LeanIX User Documentation

"Diagrams": The documentation for the diagramming feature explicitly mentions its collaborative capabilities

stating

"Multiple users can edit a diagram at the same time. You can see the cursors of other users who are currently in the diagram." This confirms the "Collaborative live editing" feature. (Accessed via the official SAP Help Portal for LeanIX).

3. SAP LeanIX Product Overview Documentation: Official product descriptions and feature lists consistently highlight commenting

task management (To-Dos)

and collaborative diagramming as key pillars of enabling teamwork within the enterprise architecture practice. The Survey feature is categorized under data governance and collection.

In SAP Signavio Process Intelligence, administrators have access to advanced settings to configure and manage features that can be provided to other users. These include Collections, which allow admins to group and share relevant analyses and processes with specific user groups. Admins can also create and manage Surveys to collect qualitative feedback from business users, integrating it with quantitative process data. Furthermore, Automations (also known as Actions) can be configured by admins to connect insights directly to execution systems, enabling users to trigger workflows or tasks in external applications based on their findings.

C. Diagrams: Diagrams, such as BPMN models, are primarily created and managed in SAP Signavio Process Manager and are then linked to or used within Process Intelligence, not configured as a shareable feature from its advanced settings.

E. Quality seals: Quality seals are a governance feature within SAP Signavio Process Manager used to manage the lifecycle and approval status of process models, not a configurable feature within SAP Signavio Process Intelligence.

1. Collections:

SAP Help Portal

SAP Signavio Process Intelligence

"Manage collections". This section details how administrators and modelers can create

edit

and share collections to provide curated content to viewers.

2. Surveys:

SAP Help Portal

SAP Signavio Process Intelligence

"Manage surveys". This documentation explains the administrative role in creating survey forms and managing survey campaigns to distribute to stakeholders for data collection.

3. Automations (Actions):

SAP Help Portal

SAP Signavio Process Intelligence

"Manage actions". This source describes how administrators configure actions that connect to external systems. Once configured

these actions are available for users to trigger from within their analyses.

A platform, in a modern technology context like SAP BTP, is fundamentally an architecture that enables interactions and the development of complementary products or services. The core element that facilitates this interaction and extensibility is the interface (most commonly, an Application Programming Interface or API). Interfaces act as the contractual points of connection, allowing applications, services, and third-party developers to access the platform's core functionalities and data in a controlled and standardized manner. The platform's value is derived from its ability to be extended and integrated with, which is only possible through well-defined interfaces.

A. Provider: A provider is the entity that owns and operates the platform (e.g., SAP is the provider of SAP BTP), not a technical element of the platform's architecture.

B. Application: An application is a consumer of the platform's services; it is built on or runs on the platform, rather than being a fundamental component of the platform itself.

D. Organization: An organization is a logical construct representing a customer or tenant that uses the platform. It is a user entity, not a core architectural element of the platform.

---

1. SAP Help Portal

SAP Business Technology Platform (BTP) Documentation: The documentation for core BTP services like the SAP Integration Suite and its API Management capability describes how APIs (interfaces) are the central mechanism for connecting and extending applications. It states

"With API Management

you can securely publish your APIs to application developers

partners

and other consumers for them to discover and use." This positions the interface as the primary element for platform interaction.

Source: SAP Help Portal

"What Is API Management?" section within the SAP Integration Suite documentation.

2. Tiwana

A. (2014). Platform Ecosystems: Aligning Architecture

Governance

and Strategy. Waltham

MA: Morgan Kaufmann. This peer-reviewed academic book is a foundational text on platform architecture. Tiwana defines a platform's architecture as consisting of a core and a periphery. The interaction between them is mediated by "boundary resources

" which are explicitly defined as the platform's interfaces (e.g.

APIs and SDKs).

Reference: Chapter 3

"Platform Architecture

" pp. 41-44.

3. SAP White Paper (2022). SAP's Approach to the Clean Core for SAP S/4HANA and SAP S/4HANA Cloud. This official document outlines SAP's strategy for extensibility

which is central to its platform concept. It emphasizes that extensions should be built on SAP BTP and connect to the S/4HANA core exclusively through stable

public APIs (interfaces)

reinforcing the interface as the essential architectural element for platform-based development.

Reference: Section 3

"The Clean Core Principles

" Principle 2: "Extend the solution with SAP BTP using released SAP APIs."

The SAP LeanIX 'Organization' fact sheet is a core element of the business architecture layer used to model the structural and hierarchical composition of an enterprise. Its primary purpose is to represent any organizational unit. This includes formal, legally recognized structures such as a 'Legal entity' and functional or operational divisions like a 'Business unit', department, or team. This modeling allows for the mapping of business capabilities, processes, and applications to the specific parts of the organization that own or use them, providing clarity on responsibilities and impact.

B. IT component: An IT Component is a distinct fact sheet type in the technology layer of the SAP LeanIX meta-model, representing software, hardware, or services, not an organizational structure.

C. Income: Income is a financial metric or attribute. While it could be a property associated with an Organization fact sheet, it does not represent the organizational unit itself.

1. SAP Help Portal - SAP LeanIX Documentation: The official documentation on the SAP LeanIX meta-model defines the 'Organization' fact sheet as part of the Business Layer. It explicitly states its use for modeling organizational units like business units

departments

and teams. This concept extends to any formal business structure

including legal entities.

Reference: SAP Help Portal

"SAP LeanIX Meta Model

" Section: "Fact Sheet Types > Business Layer > Organization." (Accessed via the official SAP LeanIX product documentation).

2. SAP LeanIX White Paper on Enterprise Architecture Meta-Models: These documents consistently describe the 'Organization' entity (often referred to as 'User Group' in older contexts but standardized as 'Organization') as the element for representing the business structure.

Reference: "The LeanIX Poster for Enterprise Architects

" which visually depicts the 'Organization' fact sheet in the business layer

distinct from the 'IT Component' in the technology layer.