BITAS 2026

LeanIX: AI-Powered EA ToolsDemo

Hammam Nashiruddin EA Consultant · hammam@atdsolution.com

ATDSol. LeanIX · EA Demo
~42 min
SAP LeanIX · EA Tools Demo · BITAS 2026

From architecture data
to AI-assisted decisions.

EA supplies the enterprise context AI needs. SAP LeanIX connects and governs that context so people and AI agents can answer enterprise-specific questions with evidence.

LeanIX landscape pan-out — whole organization as one connected graph
Capture 01 — Landscape The whole organization as one connected graph, strategy → capability → application → technology.
LeanIX business capability map
Capture 02 — Capability map The high-level view for business navigation.
01
The EA Shift

Bringing all domains together

05 min

Customers usually run separate, disconnected tools per domain. EA connects business capabilities, applications, technology, ownership, and initiatives. This shared context makes AI more relevant to the enterprise, while AI can help architects build and use that context faster.

The three core layers + Strategic Context + Solution Layer
  • BusinessBusiness Capabilities, Organization, Business Context
  • ApplicationApplications, Interfaces, Data Objects
  • TechnologyIT Components, Providers, Tech Categories
  • Strategy & TransformationObjectives, Initiatives, Platforms: the steering layer on top
SAP LeanIX EA landscape — all domains connected in one repository
Capture — EA landscape All domains in one connected view.

AI-EA Synergies

EA gives AI context. AI helps EA move faster.

EA → AI: Enterprise context
EA connects business priorities, capabilities, applications, data, technology, and ownership. This context helps teams identify valuable AI use cases, understand dependencies and constraints, and ground AI responses in the organization's architecture.
AI → EA: Faster architecture work
AI can help extract and structure architecture information, suggest relationships for review, and answer questions using repository data. Architects can spend less time assembling information and more time assessing change impacts, evaluating options, and advising decision-makers.

Shared foundation: Current, connected repository data and human validation.

Two equal partner robots labeled AI and EA holding hands, with white bodies and ATDSol red accents
Concept illustration: AI and EA as partners.
02
Tool & EA Framework

Overview LeanIX

07 min

A connected EA repository brings data from sources such as ServiceNow, BMC, and custom databases into a shared model. Fact sheets provide a practical structure for architecture data and complement methods such as TOGAF and modeling languages such as ArchiMate.

The SAP EA Approach & Fact Sheet types

12 default fact-sheet types connect three conceptual architecture layers, with Strategy & Transformation spanning them. The prescriptive starting point is configurable when the organization needs it.

LeanIX meta model — fact-sheet types across the 4 layers
Capture 03 — Metamodel The relationships needed to trace capability → application → technology → owner → initiative.
Out-of-the-box views
  • Business Capability Maphow capabilities are supported by applications
  • TIME / Application RationalizationTolerate · Invest · Migrate · Eliminate
  • Application Landscapethe portfolio at a glance
  • Risk Reporttechnology risk & dependency view
LeanIX TIME matrix — application rationalization
Capture 04 — TIME matrix Application rationalization: which to keep, invest, migrate, or retire.
03
Repository · Governance · Data Freshness

Governance & data that stays fresh

10 min

Our answer is useful only when the underlying data is complete, owned, and current. Mandatory attributes support completeness, Quality Seal assigns approval responsibility, history records changes, and surveys help owners refresh the data.

LeanIX Quality Seal approval state
Capture 06 — Quality Seal Changes can trigger review by the responsible or accountable owner before the fact sheet is approved.
LeanIX fact-sheet history — interactive audit trail
Capture 07 — History See who changed the fact sheet, when it changed, and what was updated.
LeanIX survey questionnaire to the application owner
Capture 08 — Survey A short questionnaire to the application owner drives the periodic refresh.
What I show in LeanIX ›
  • Open a fact sheet and read its default attributes.
  • Show the mandatory attributes required before approval.
  • Open the Quality Seal and show who reviews and approves the fact sheet.
  • Open fact-sheet history to show who changed what and when.
  • Create and run a survey, and show the owner’s response flow.
04
Architecture views

Different views of the same architecture

08 min

Choose the view that fits the question: inspect a record, trace dependencies and potential change impacts, explain relationships in a diagram, browse an application catalog, or analyze the portfolio.

Fact Sheets

Inspect one architecture record in detail, then check how its data has changed.

LeanIX application Fact Sheet with Sourcing expanded, showing technical fit and linked hardware and software components
Fact Sheet detail Inspect an application's technical fit and linked IT components in the expanded Sourcing section.
LeanIX BPOS Fact Sheet change history with events, old and new values, users, and timestamps
Fact Sheet change history Trace changes to the record: what changed, who changed it, and when. This is separate from saved diagram versions.

Object Explorer

Start with a selected object and follow its relationships across architecture domains to assess potential change impacts. Trace connections between objectives, initiatives, applications, and technology, then expand related organizations, data, or interfaces. The analysis depends on the relationships recorded in the repository.

LeanIX object relationship tree tracing an objective through AI Transformation 2025 and Chatbot Backend to LiveChat ChatBot SaaS Hosting, with additional relationship branches
Cross-domain impact analysis Follow the highlighted path from an objective to an initiative, application, and IT component. Expand connected branches to identify dependencies and investigate what a change could affect.

Diagrams

Explain how architecture elements connect, and compare saved versions of the drawing.

LeanIX diagram editor with architecture elements linked to Fact Sheets
Create and edit a diagram Arrange architecture elements and their connections using shapes linked to repository Fact Sheets.
LeanIX diagram with the Version History panel open
Diagram versions Select an earlier saved version, compare changes, and return to the latest diagram.

Portal

Give users a catalog they can browse without starting from a diagram or a detailed architecture record.

  • Search and filter the application catalog.
  • Read application descriptions and availability or approval status.
  • Use the visible request entry point when an application is needed.
LeanIX Application Portal with search, team filters, application cards, and approval statuses
Application Portal A self-service entry point for finding applications and viewing catalog information.

Dashboards & Reports

Start from a dashboard organized for a role or use case, then open a report to examine a specific architecture question.

LeanIX My Dashboard with links to persona-based and use-case dashboards
Dashboard The workspace landing dashboard brings together guidance and links to role-based and use-case views.
LeanIX All Reports catalog with report preview cards, search, type and owner filters, and use-case navigation
Reports catalog Browse available reports, search by title or description, and filter by report type or owner before opening a view.
Report example: Technology Lifecycle ›
LeanIX Technology Lifecycle report with IT components grouped by application on a lifecycle timeline
Technology Lifecycle report Compare IT component lifecycles across applications and identify upcoming phase-outs or end-of-life dates.
What I show in LeanIX ›
  • Open an Application Fact Sheet and inspect its attributes and relationships.
  • Open its change history to show who changed what and when.
  • Use Object Explorer to trace a selected object's dependencies across domains and assess potential change impacts.
  • Create or edit a diagram, then compare its saved versions.
  • Search the Application Portal and inspect a catalog entry.
  • Open the dashboard, then a report with its filters and legend.
05
AI Capability & Integration

Give AI enterprise context

10 min

Generic AI does not know your capabilities, applications, dependencies, owners, or initiatives. SAP LeanIX supplies that governed enterprise context to its native AI capabilities and, through MCP, to an external AI harness.

Three jobs for AI

Discover and structure

Inventory Builder analyzes diagrams, images, and files, then proposes fact sheets and relations for an architect to review.

AI Inventory Builder proposals awaiting review
Inventory Builder Review the proposed fact sheets and relationships before adding them to the repository.

Ask and understand

Use natural language to find architecture facts, relationships, and missing information.

LeanIX native AI query
Ask in LeanIX Query the architecture in natural language, then inspect the records behind the answer.
Prompt workbench
Run it in LeanIX first, then reuse it in the MCP harness.

Connect and extend

MCP gives an external AI client access to the LeanIX tools allowed for the authenticated user or technical role.

View AI-generated impact brief

Saved MCP result: Salesforce Experience Cloud dependencies, relationship paths, and mapping gaps. Opens in a new tab; no live LeanIX connection is required.

External AI harness connected to SAP LeanIX through MCP
LeanIX through MCP Reuse the architecture context in an external AI client, within the authenticated role's permissions.
Presenter notes: LeanIX → MCP proof sequence ›
  1. Ask in LeanIXRun the decision-trace prompt in Joule or the LeanIX AI assistant.
  2. Open the evidenceInspect the returned capability, application, IT component, owner, and remediation records.
  3. Ask through the MCP harnessPaste the same prompt into your external AI chat connected to the SAP LeanIX MCP server.
  4. Compare and explain the boundaryBoth paths use governed repository context. MCP exposes only the tools available to the authenticated role, and missing data must remain visible.

Supporting integration paths

LeanIX can combine native connectors, APIs, and spreadsheet exchange to bring source data into the architecture repository.

Use the native connector to exchange selected data with ServiceNow and connect operational records to the architecture model.

LeanIX ServiceNow integration config
Capture 16 — ServiceNow A configured source for operational architecture data.
06
Closing & Resources

Context before automation

02 min

Without architecture context, AI gives generic answers. With connected and governed EA data, it can help answer enterprise-specific questions and expose the evidence behind them.

Key takeaways
  • EA provides decision contextIt connects strategy, capabilities, applications, technology, ownership, and change.
  • LeanIX makes the context reusableThe repository keeps relationships visible, governed, and available across reports, diagrams, and integrations.
  • AI accelerates accessAI can discover and query architecture data, while architects validate evidence and remain accountable for decisions.
Resources
QR code for the BITAS demo materials at bitas.hammamnash.site

Revisit the demo materials

Scan the QR code to open this presentation, explore the screenshots, and reuse the example prompts after the session.

Or open this address on your device:

bitas.hammamnash.site