Fact sheet types and subtypes
Explore the reference model, current Atlas types and their available configuration.
On this page
A fact sheet type describes a kind of architecture information, such as an Application, Objective or Data Object. A fact sheet is an individual record of that type. A subtype refines a type; an API is a subtype of Interface in the reference model.
Open the type catalogue
Go to Settings → Fact Sheet Types, or choose Fact sheet types on the Metamodel overview. Search by a type or subtype name, then open a type to see its definition, reference subtypes, existing Atlas relations and available settings. Search results have a shareable URL.
The catalogue follows the SAP LeanIX v4 structure:
| Layer | Standard types |
|---|---|
| Strategy and transformation | Objective, Platform, Initiative |
| Business architecture | Organization, Business Capability, Business Context |
| Application and data architecture | Data Object, Application, Interface |
| Technical architecture | Provider, IT Component, Tech Category |
System, Data Product and Contract are listed separately as optional reference types. Atlas extensions, including Strategy Theme and Decision, remain available alongside them.
Read availability correctly
Available in Atlas means the type has an existing Atlas inventory. Separate types in Atlas means related records currently have their own inventories: Process, Value Stream and Customer Journey are shown under Business Context with links to those inventories. Planned in Atlas means the type has no usable inventory yet.
The reference model includes 27 subtypes. The Reference default column describes SAP's defaults, including dates for new workspaces. The Atlas availability column describes Atlas separately. A standard reference subtype can still be planned in Atlas. Viewing a reference type does not enable it, migrate records or create a new subtype.
IT Component is currently named Technology in the Atlas inventory. The catalogue keeps that mapping visible. An AI Agent reference subtype is not a claim that every AI System record is an application agent.
Configure fields and inspect relations
For Application, Business Capability and IT Component, Configure custom fields opens the existing field editor on the corresponding type. A workspace administrator can create and manage field definitions there. The existing editor also supports the Atlas Decision type. Existing permissions still apply.
The Relations in Atlas table shows current endpoints, direction and relation attributes. Business Context shows the relations of its separate types. This table describes relation definitions; it does not count workspace records or edit links.
For an individual relation, Active From and Active Until describe when the link applies. Its attribute chip shows the temporal state: a link without dates is current, and a link past Active Until is ended. Ended application-to-capability links do not contribute to current support or cost totals. The same dates and state are available in the MCP relation read.
Subtype, relation, responsibility, tag and access-rule definitions cannot yet be edited in the catalogue. Follow the availability shown on each type when deciding what to model today.
Inspect the same model through AI
A connected AI client can call get_metamodel with scope: "reference" to read the same catalogue. The default all response and atlas://metamodel include it as reference_profile. Existing entity_types remain separate: planned reference types are not accepted entity write types.
See Connect an AI client and Workspace access.