Note Review: LeanIX Catalog Schema (2026-03-22)

Note Review: LeanIX Catalog Schema (2026-03-22)

Source: note-leanix-catalog-schema.md Reviewed: 2026-03-22 Method: Interactive review via /toolkit:note-review

Context

The factory needs unified CSV schemas for two catalogs — Object/Solution Catalog and Changement Organisationnel (CO) — aligned with SAP LeanIX Meta Model 4 and Macroscope methodology. Three mismatched schemas currently exist in the repo. The schemas must be dual-use: factory self-portrait AND client deployments. The factory itself will be the first catalog instance.

Key Observations

  1. Three competing CSV schemas exist (leanix-catalog-extract skill, framework templates, BizTalk integration inventory) — need one unified schema aligned with SAP LeanIX Meta Model 4
  2. Multi-level catalog structure needed (L0→L3) for capability mapping, process hierarchy, and organizational hierarchy
  3. CO (Changement Organisationnel) is a separate catalog layer linked to roadmap items — projects come later, if at all
  4. Factory self-portrait is the first instance — every role, workflow, skill, production line becomes a catalog object
  5. Request flow: Marcel orchestrates → work gets done → published via toolkit:leanix-catalog-extract + toolkit:diagram-generate

Decisions

D1 — Schema Language · Critical

Stakes: Current schemas mix French and English columns. Need consistency.

Options considered:

  • A: English only
  • B: French only
  • C: Bilingual headers

Decision: English only. Translate for customers if needed. Aligns with factory language convention (CLAUDE.md says English).

D2 — Hierarchy Depth · Critical

Stakes: How deep the capability/process hierarchy goes.

Options considered:

  • A: 3 levels (L0/L1/L2)
  • B: 4 levels (L0-L3)
  • C: Flexible depth

Decision: 4 levels (L0→L3). L0 Capability Areas → L1 Capabilities → L2 High-Level Processes → L3 Detailed sub-processes/activities.

D3 — Object Type Prefixes · Important

Stakes: Current prefixes (PLT, APP, ITC, DAT, TEC, PRO, ROL, ORG) may not cover factory objects.

Options considered:

  • A: Add all four (CAP, DEP, WFL, SKL)
  • B: Add CAP + WFL only
  • C: Keep current + CAP only

Decision: Add all four — CAP (Capability), DEP (Department), WFL (Workflow), SKL (Skill). Full coverage for factory self-portrait + client use.

Full prefix list: PLT, APP, ITC, DAT, TEC, PRO, ROL, ORG, CAP, DEP, WFL, SKL

D4 — Relationship Types · Important

Stakes: Current custom types don't align with SAP LeanIX standard vocabulary.

Options considered:

  • A: Adopt LeanIX vocabulary (unified 12-type list)
  • B: LeanIX core only
  • C: Park for later

Decision: Adopt LeanIX vocabulary. Unified list (12 types):

  • From LeanIX: contains, supports, requires, uses, realized-by, owned-by, provided-by, transfers, successor-of
  • Factory additions: data-flow, depends-on, triggers

Questions Clarified

Q1 — CO Change Tracking · Critical

How do CO records link to work that drives the change?

Answer: CO records link to a Roadmap_Item (required) — the strategic motivation for the change. A Project field is optional — added later when a project is created to implement the change. "Parent" is NOT the right term — parent means containment hierarchy (object catalog), roadmap linkage is a different relationship ("driven by" / "planned in").

Q2 — Request Flow · Important

How does catalog work flow through the factory?

Answer: Request goes to Marcel → work gets done (Francois for frameworks, others for their domains) → published via toolkit:leanix-catalog-extract + toolkit:diagram-generate. Factory self-portrait is the first instance — CEO can see what each talent is working on.

Actions

# Action Owner Priority
A1 Build unified Object Catalog CSV schema (English, 4 levels, 12 prefixes) Francois Critical
A2 Build CO Catalog CSV schema (Roadmap_Item + optional Project) Francois Critical
A3 Update toolkit:leanix-catalog-extract to match new unified schema Ivan High
A4 Update relationship types in toolkit to match LeanIX vocabulary (12 types) Ivan High
A5 Build factory self-portrait as first catalog instance Elena + Francois High
A6 Align framework template CSVs with unified schema (fix mismatches) Francois Medium

Suggested Next Step

The input/ folder has enough context to build the unified CSV schemas. Francois should produce:

  1. object-catalog-schema.csv — unified Object Catalog with all 12 prefixes, 4 levels, LeanIX-aligned columns
  2. co-catalog-schema.csv — CO Catalog with Roadmap_Item + optional Project fields
  3. relationship-types.md — reference doc listing all 12 relationship types with definitions and examples

Then update the toolkit:leanix-catalog-extract skill to match.