# How do you automatically generate a LeanIX-compliant enterprise baseline?

> Canonical: https://decisionpen.com/blog/automatically-generate-leanix-compliant-enterprise-baseline  
> Published: 2026-10-25 · DecisionPen · Living EA series (D6c)  
> Related docs: /docs/incremental-modelling, /docs/architecture-decision-workspace, /docs/decisionpen-vs-traditional-ea, /docs/beyond-traditional-ea

## Summary

A LeanIX-compliant enterprise baseline is a curated starting landscape aligned to that metamodel (Applications, IT Components, Capabilities, related types), populated from CMDB extracts and documents with AI proposals and human curation — not months of blank factsheet entry or an unsupervised dump into production.

## What “LeanIX-compliant” means

Metamodel alignment: recognised factsheet types and relationships; applications vs tech vs capabilities; How/Why evidence; human curation before production truth.

**Operating definition:** AI proposes metamodel-aligned entities/links from inventory + documents → humans curate → living Context of Record.

## Why LeanIX programmes stall

Discovery Tax (manual factsheets) empties workspaces. Inventory connectors help deployment truth; documents still hold intent and dependencies (knowledge discovery).

## Practical generation method

1. Bound scope (domain / value stream / carve-out).
2. Seed from CMDB or inventory spreadsheet.
3. Ingest HLDs, decks, wikis, notes for the same scope.
4. AI proposes LeanIX-aligned types and relationships with evidence.
5. Architects curate (accept, merge, reject, mark unknowns).
6. Use Ask/artefacts; widen scope; complement LeanIX or switch by operating model.

See also: start EA from documents in 30 days.

## What automation should not promise

- Silent production load without review.
- Full replacement of LeanIX SaaS/SAP discovery inboxes.
- Complete How/Why from CMDB rows alone.

## How DecisionPen generates a LeanIX-aligned baseline

Architecture Decision Workspace with LeanIX metamodel support: import inventory and/or documents → propose → curate → Enterprise Ask and artefacts. Complement or primary workspace depending on operating model. Trial: https://decisionpen.com/trial

## When is DecisionPen the wrong tool?

LeanIX connector admin only; network scanning; freeform Visio/BPMN as the primary job.

## FAQ

**What is a LeanIX-compliant enterprise baseline?**  
Curated landscape shaped to LeanIX-style factsheet types and relationships, ready for portfolio work.

**Can you auto-generate LeanIX factsheets from documents?**  
Propose yes; publish to production only after curation.

**Replacement or on-ramp?**  
Either — complement existing LeanIX or switch when one workspace should own modelling + Ask.

**Fastest inputs?**  
Bounded scope + inventory spreadsheet + HLD/wiki pack.

**How does DecisionPen do it?**  
LeanIX-aligned propose/curate with evidence; Ask on the living map; complement or inform LeanIX rollouts.

**When is DecisionPen wrong?**  
Connector-only, scanner-only, or freeform drawing as the main need.

## Related posts

- https://decisionpen.com/blog/what-is-the-context-tax-in-enterprise-it  
- https://decisionpen.com/blog/decisionpen-vs-leanix-complement-or-switch  
- https://decisionpen.com/blog/how-ai-accelerates-automated-enterprise-discovery  
- https://decisionpen.com/blog/what-is-automated-enterprise-architecture-discovery  
- https://decisionpen.com/blog/how-to-enrich-ea-factsheets-with-unstructured-documents  
- https://decisionpen.com/blog/how-to-start-ea-from-documents-in-30-days  
- https://decisionpen.com/blog/what-is-the-discovery-tax-in-it-transformations