EA Meta-Model Reference
The EA catalog is aligned with SAP LeanIX Meta Model v4.0 with 6 factory extensions. Every catalog object gets a typed prefix (APP-001, CAP-003…) that determines its TOGAF layer, visual grouping, and Macroscope deliverable routing.
Object Types — 18 Prefixes
12 native LeanIX fact sheet types + 6 factory extensions. The prefix must match the Type column exactly.
| Prefix | Type | LeanIX Fact Sheet | TOGAF Layer | Use When |
|---|---|---|---|---|
| OBJ | Objective | Objective | Business | Strategic goal or KPI the architecture is meant to achieve |
| INI | Initiative | Initiative | Business | Program, project, or epic driving a transformation (hierarchy: program → project → epic) |
| CAP | Business Capability | BusinessCapability | Business | What the organization can do, independent of how (e.g. "Communication SMS") |
| BCX | Business Context | BusinessContext | Business | Market segment or external domain the system operates within |
| PRO | Business Process | BusinessProcess | Business | Process with an independent trigger (receive port, timer, file watcher) |
| PRS | Sub-Process | BusinessProcess | Business | Called by a parent PRO — no own trigger. Parent_ID = calling PRO |
| ORG | Organization | Organization | Business | Legal entity, business unit, or team. Subtypes: legalEntity, country, businessUnit, team |
| ROL | Role | (factory custom) | Business | Person role or job function that interacts with the system |
| DEP | Department | (maps to ORG) | Business | Department within the organization. Maps to ORG with businessUnit subtype |
| WFL | Workflow | (factory custom) | Business | Multi-step workflow or procedure with defined steps and actors |
| APP | Application | Application | Application | Deployable application, solution, or service. Groups related orchestrations |
| INT | Interface | Interface | Application | External-facing API endpoint, webhook, or adapter — the connection point between systems |
| SKL | Skill | (factory custom) | Application | Digital capability, AI skill, or automation component (production line assets) |
| DAT | Data Object | DataObject | Data | Database, schema, message type, or data store with business meaning |
| PLT | Platform | Platform | Technology | Top-level technical environment containing multiple apps and IT components |
| ITC | IT Component | ITComponent | Technology | Runtime, middleware engine, or infrastructure product that hosts applications |
| TEC | Technical Stack | TechnicalStack | Technology | Named technology stack or framework grouping multiple components |
| PRV | Provider | Provider | Technology | External organization that provides a service, API, or platform |
TOGAF Layers
Business
OBJ, INI, CAP, BCX, PRO, PRS, ORG, ROL, DEP, WFL
Application
APP, INT, SKL
Data
DAT
Technology
PLT, ITC, TEC, PRV
Object Hierarchy (L0 → L3)
Objects nest inside each other via Parent_ID.
The diagram generator reads this column for visual grouping.
CAP-001 (L0, no parent) ← top-level capability area
└── CAP-002 (L1, parent=CAP-001) ← sub-capability
└── PRO-001 (L2, parent=CAP-002) ← process
└── PRS-001 (L3, parent=PRO-001) ← sub-process
Rule: PRS always has Parent_ID pointing to a PRO (not an APP).
Parent orchestrations are PRO at L2; sub-orchestrations called by them are PRS at L3.
Relationship Types — 12 Standard
9 SAP LeanIX aligned + 3 factory extensions. Use only these types in the relations CSV.
| Type | Origin | Meaning | Visual Verb |
|---|---|---|---|
| contains | LeanIX | Parent-child containment | contains |
| supports | LeanIX | Provides functional support (upward) | supports |
| requires | LeanIX | Hard prerequisite | requires |
| uses | LeanIX | Consumes or interacts with | uses |
| realized-by | LeanIX | Capability realized by process | realized by |
| owned-by | LeanIX | Ownership relationship | owned by |
| provided-by | LeanIX | Supplied by vendor/provider | provided by |
| transfers | LeanIX | Data exchange via interface | transfers |
| successor-of | LeanIX | Replaces / evolves from | succeeds |
| data-flow | Factory | Data movement between components | data flow |
| depends-on | Factory | Soft dependency | depends on |
| triggers | Factory | Event-driven activation | triggers |
Macroscope Deliverable Routing
Every object must be tagged with its target Macroscope A-code in the Tags column.
A mapped deliverable with no content → explicit gap/constat, never silently dropped.
AS-IS (Architecture actuelle)
A200 CAP (BusinessCapability) + Value Streams Capacités d'affaires
A251 PRO / PRS (BusinessProcess) Processus
A250 APP (Application, business systems) Systèmes
A170 DAT — information domains (business view) Architecture de l'information
A239 ORG / ROL / DEP (roles & org) Ressources humaines
A269 Work environment (sites, postes, BYOD) Environnements de travail
A219 ITC — software components Architecture logicielle
A150 DAT — technical data architecture Architecture des données
A370 PLT / infra ITC / PRV Infrastructure technologique
Changement organisationnel
A100 INI + CO records Solutions d'entreprise
A280 CO Impact_* columns Impacts
A290 CO Cost_Project / OpEx_Delta / CapEx_Delta Coûts et bénéfices
A270 INI sequencing / Phase Stratégie de livraison
A275 CO Change_Type people/process Stratégie de changement organisationnel
Naming: Three Levels per Object
| Column | What it stores | Used in diagram mode | Example |
|---|---|---|---|
| Name | Universal product name — what vendors / procurement call it | physical | "Azure API Management" |
| Display_Name | Organizational alias — what people say in meetings | logical (default) | "Maestro" |
| Group | Architectural concept — independent of vendor and org alias | conceptual | "Intégration" |
Rule: Display_Name must never contain the product name in parentheses — that duplicates Name. If the org has no special alias, Display_Name can equal Name.