// Reference
Class guide
Every class, relationship and hint the modeler knows, written in our own words from ServiceNow's public material: the CSDM white paper, and the product documentation for the Kubernetes classes. Each entry links to its source so you can check it.
Classes
Grouped by the lane they sit in on the canvas, top to bottom. Lanes are a drawing aid, not CSDM domains: the white paper organizes CSDM 5 into seven domains (p. 14). Classes marked CMDB come from ServiceNow's product documentation rather than the white paper. Classes marked Extended (strategy, value streams, SDLC, product models and AI) appear in the palette when you turn on View › Extended classes.
Business
Business Capability
cmdb_ci_business_capability
What the business does, independent of how. Arranged in a hierarchy of at most six levels.
Business Process
cmdb_ci_business_process
How work is done. Related to the Business Applications that enable it.
Strategic PriorityExtended
sn_gf_strategy
A key, cross-functional focus area that drives long-term goals, likely spanning several business units.
GoalExtended
sn_gf_goal
A broad, qualitative outcome the organization wants, often for a business unit and in service of a Strategic Priority.
TargetExtended
sn_gf_goal_target
A quantifiable measure of a Goal: a milestone tracked over time.
Product IdeaExtended
sn_align_core_product_idea
A product, feature, enhancement or change proposal that can be curated and promoted into demand, a project, an epic or a story.
Planning ItemExtended
sn_align_core_planning_item
Work that is aligned to goals, planned and executed: a demand, project, epic or custom work item.
Value StreamExtended
cmn_value_stream
How work really happens across the organization to deliver value, a product or service, to a customer.
Value Stream StageExtended
cmn_value_stream_stage
A distinct grouping of activities within a Value Stream.
Design
Business Application
cmdb_ci_business_app
The logical software the business knows by name, independent of where or how many times it runs.
Information Object
cmdb_ci_information_object
A kind of data a Business Application uses, recorded to scope governance and compliance.
SDLC ComponentExtended
cmdb_ci_sdlc_component
An individually developed part of a Business Application, such as a microservice or an infrastructure configuration. A deployed application-type component is an Application Service.
Product ModelExtended
cmdb_model
The product record (goods or services) a CI refers to through its model: owner, status, life cycle and end of life. Not a CI.
Service
Business Service
cmdb_ci_service_business
The service as the customer sees it, not what IT calls it. Single level, not a hierarchy.
Business Service Offering
service_offering
A consumable option of a Business Service. Application Services are exposed through offerings.
Technology Management Service
cmdb_ci_service_technical
A provider-focused service that manages technology layered under business and Application Services.
Technology Management Service Offering
service_offering
A stratification of a Technology Management Service by geography, environment, support group, approval group and similar options.
Application Service
cmdb_ci_service_discovered
A deployed, running instance of an application, e.g. per environment or region: the application type of Service Instance. Its table follows how it is populated: manual or Service Mapping (cmdb_ci_service_discovered), tags, calculated, or a dynamic CI group (cmdb_ci_query_based_service).
Service Instance
cmdb_ci_service_auto
The base class for every deployed instance of a service; CSDM 5 relabeled the old Application Service base table. Pick a specific type where you can: it is for reporting across all of them.
Data Service Instance
cmdb_ci_data_service_instance
A deployed or provisioned instance of data services: database servers and services, storage, AI and machine-learning services such as pipelines and models, and data products.
Connection Service Instance
cmdb_ci_connection_service_instance
A logical or physical network connection, such as a VLAN, LAN or WLAN, kept as a CI so it takes part in dependency and impact analysis.
Network Service Instance
cmdb_ci_network_service_instance
A deployed or provisioned instance of network services built on network functions. With connections, it forms the service delivery network.
Operational Process Service Instance
cmdb_ci_operational_process_service_instance
An instance of an operational process, such as manufacturing, utility or warehouse operations, carried out by connected devices and equipment.
Facility Service Instance
cmdb_ci_facility_service_instance
A service tied to running a facility, such as heating and cooling, lighting, power, water, building access or elevators.
Functional
API
cmdb_ci_api
An interface a service exposes or depends on.
Application
cmdb_ci_appl
Installed software running on a host: a web server, application server, database instance, middleware.
AI ApplicationExtended
cmdb_ci_appl_ai_application
AI software running on a host, container platform or cluster: machine-learning models, analytics or AI-enabled applications. An extension of Application.
AI FunctionExtended
cmdb_ci_function_ai
An AI SaaS function on a public cloud platform, offering on-demand machine learning, data processing or AI tasks.
Kubernetes NamespaceCMDB
cmdb_ci_kubernetes_namespace
A named partition of a cluster, often one per team, application or environment.
Source: Kubernetes discovery using patterns (ServiceNow docs, Yokohama)
Kubernetes WorkloadCMDB
cmdb_ci_kubernetes_workload
A deployment, daemon set or stateful set: the containers a cluster keeps running for an application.
Source: Kubernetes extension classes (ServiceNow docs, Yokohama)
Kubernetes ServiceCMDB
cmdb_ci_kubernetes_service
A stable network endpoint in front of a workload's pods. Not a CSDM service: it is a runtime object.
Source: Kubernetes discovery using patterns (ServiceNow docs, Yokohama)
Kubernetes PodCMDB
cmdb_ci_kubernetes_pod
The smallest unit a cluster schedules: one or more containers running together on a server.
Source: Kubernetes discovery using patterns (ServiceNow docs, Yokohama)
Infrastructure
Host
A physical or virtual computer an application runs on.
Network
Network infrastructure a service depends on.
Kubernetes ClusterCMDB
cmdb_ci_kubernetes_cluster
A Kubernetes Cluster: the control plane and nodes that run containerized workloads.
Source: Kubernetes discovery using patterns (ServiceNow docs, Yokohama)
Kubernetes NodeCMDB
cmdb_ci_kubernetes_node
A worker machine in a cluster, hosted on a server.
Source: Kubernetes discovery using patterns (ServiceNow docs, Yokohama)
Relationships
Reported type labels appear in ServiceNow material we cite. Conventional labels are standard CMDB types commonly used for the pairing; the pairing is sourced, the label is a suggestion.
| From | To | Type | Evidence | Source |
|---|---|---|---|---|
| Business Application | Application Service | Uses::Used byLegacy: Consumes::Consumed byCSDM 4 used Consumes::Consumed by; the CSDM 5 relationship figure (p. 48) shows Uses::Used by. A Business Application relates to Application Services only, not to other Service Instance types. | reported | CSDM CI relationships (ServiceNow docs) |
| Business Capability | Business Application | Provided by::ProvidesOlder files, other direction: Provides::Provided byDrawn from the capability, as the white paper's figure does. Older Blueprint files drew it from the application (Provides::Provided by). | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Application | Information Object | Uses::Used byLegacy: reference:information_objectA CMDB relationship in the CSDM 5 figure. Older Blueprint files used a reference field. | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Process | Business Capability | Operationalizes::Operationalized by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Process | Business Application | Depends on::Used byThe single Business Process reference field on a Business Application is legacy in CSDM 5; use a relationship. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 33 |
| Business Service | Business Service Offering | reference:parentThe figure shows a reference ("Published as") from the service to its offerings; the field name is ours. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Capability | Business Service | Provided by::ProvidesOlder files, other direction: Provides::Provided byDrawn from the capability, as the white paper's figure does. Older Blueprint files drew it from the service (Provides::Provided by). | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service | Technology Management Service Offering | reference:parentThe figure shows a reference ("Published as") from the service to its offerings; the field name is ours. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Application Service | Contains::Contained byLegacy: Depends on::Used byCSDM 5 shows a Technology Management Service Offering containing the service instances it covers. Older Blueprint files used Depends on::Used by. | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Application | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Host | Depends on::Used byA drawing shortcut. In the CMDB, an application runs on the infrastructure, and Service Mapping discovers the service's infrastructure through its applications. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 38 |
| Application Service | Network | Depends on::Used byA drawing shortcut. In the CMDB, an application runs on the infrastructure, and Service Mapping discovers the service's infrastructure through its applications. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 38 |
| API | Application Service | Receives data from::Sends data toOlder files, other direction: Depends on::Used byDrawn from the API, as the white paper's figure does. Older Blueprint files drew it from the service (Depends on::Used by). | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| API | Application | Provided by::Provides | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| API | Business Service Offering | Receives data from::Sends data to | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application | Host | Runs on::RunsThe figure relates applications to infrastructure CIs in general. | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Capability | Business Capability | reference:parent | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 32 |
| Business Service Offering | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Data Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Connection Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Connection Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Network Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Operational Process Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Business Service Offering | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Technology Management Service Offering | Facility Service Instance | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Application Service | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Data Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Network Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Operational Process Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Facility Service Instance | Depends on::Used by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Service Instance | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Data Service Instance | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Network Service Instance | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Operational Process Service Instance | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Facility Service Instance | Connection Service Instance | Connected by::Connects | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Connection Service Instance | Network Service Instance | Provided by::Provides | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Value Stream | Business Capability | Many-to-many map | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 15 |
| Value Stream Stage | Business Capability | Many-to-many map | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 15 |
| Value Stream | Business Process | Many-to-many map | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 15 |
| Value Stream Stage | Business Process | Many-to-many map | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 15 |
| Value Stream Stage | Value Stream | reference:value_streamEach stage belongs to one value stream; the field name is ours. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 15 |
| Product Idea | Planning Item | Promoted to | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Planning Item | Goal | Aligned to | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Planning Item | Target | Aligned to | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Target | Goal | Measures | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Goal | Strategic Priority | In service of | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Product Idea | Product Model | Related to | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Planning Item | Product Model | Related to | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 30 |
| Business Application | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 33 |
| Application Service | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 46 |
| Business Service Offering | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 46 |
| Technology Management Service Offering | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 46 |
| Application | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 46 |
| Host | Product Model | reference:model_id | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 46 |
| Business Application | SDLC Component | Contains::Contained by | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| SDLC Component | Application Service | Contains::Contained byA deployed instance of an application-type SDLC Component is an Application Service (p. 35). | reported | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 48 |
| Application Service | AI Application | Depends on::Used byPairing inferred: AI Application extends Application, so it takes Application's relationships. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 41 |
| AI Application | Host | Runs on::RunsPairing inferred: AI Application extends Application, which runs on infrastructure (Figure 16). | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 41 |
| Application Service | AI Function | Depends on::Used byPairing inferred: a service instance that uses a SaaS AI function depends on it. The white paper does not name this pair. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 41 |
| Data Service Instance | AI Function | Depends on::Used byPairing inferred: a service instance that uses a SaaS AI function depends on it. The white paper does not name this pair. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 41 |
| Kubernetes Cluster | Kubernetes Namespace | Contains::Contained by | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Kubernetes Cluster | Kubernetes Node | Cluster of::Cluster | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Kubernetes Cluster | Kubernetes Pod | Contains::Contained by | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Kubernetes Cluster | Kubernetes Service | Contains::Contained by | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Kubernetes Workload | Kubernetes Cluster | Hosted on::Hosts | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Kubernetes Service | Kubernetes Workload | Provides::Provided by | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Host | Kubernetes Node | Hosts::Hosted onThe documentation names a Linux server as the host. | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Host | Kubernetes Pod | Contains::Contained byThe documentation names a Linux server as the host. | reported | Kubernetes discovery using patterns (ServiceNow docs, Yokohama) |
| Application Service | Kubernetes Workload | Depends on::Used byPairing inferred: a workload and its cluster are components configured to offer the service, like applications and hosts. The Kubernetes documentation does not name this pair. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 38 |
| Application Service | Kubernetes Cluster | Depends on::Used byPairing inferred: a workload and its cluster are components configured to offer the service, like applications and hosts. The Kubernetes documentation does not name this pair. | conventional | CSDM 5 white paper (Scott Lemm, Rob Koeten), p. 38 |
Hints
Hints advise; they never block you from drawing.
infoBusiness Application has no Business Capability
Relate each Business Application to the capabilities it serves, for visualization and reporting.
infoBusiness Application has no Application Service
Where the application is deployed, model each running instance as an Application Service related to it.
warningBusiness Application linked straight to infrastructure
Infrastructure belongs under the Application Service that runs on it. Relate the Business Application to an Application Service, and the service to its applications and hosts.
infoService instance is not exposed through an offering
Expose each service instance through the related Business Service Offering or Technology Management Service Offering. The white paper says this of Application Services; its relationship figure relates offerings to every service instance type.
infoService Instance has no specific type
Choose the type that fits: Application Service, or a Data, Connection, Network, Operational Process or Facility Service Instance. The base class is for reporting across all of them.
warningCapability hierarchy deeper than six levels
Keep Business Capability hierarchies to six levels or fewer.
warningCircular capability hierarchy
A capability cannot be its own ancestor. Remove one parent link to break the loop.
warningRelationship not used in CSDM
These two element types are not related this way in CSDM. Remove the relationship, or route it through the element CSDM puts between them.
infoOffering has no parent service
An offering is a stratification of one service. Relate each Business Service Offering to its Business Service, and each Technology Management Service Offering to its Technology Management Service.
infoLegacy relationship type
This relationship uses an older type or direction: a CSDM 4 type (such as Consumes::Consumed by), or how an earlier Blueprint file drew it. Delete it and redraw it to get the CSDM 5 type.
ArchiMate® 3.2 mapping
Switch the editor's lens to CSDM + ArchiMate 3.2 to see these names on the canvas. The mapping is our interpretation; each element links to the chapter of the public specification that defines it, and every relationship is an allowed ArchiMate relationship. ArchiMate® is a registered trademark of The Open Group.
| CSDM class | ArchiMate element | Layer | Note |
|---|---|---|---|
| Business Capability | Capability | Strategy | |
| Business Process | Business Process | Business | |
| Business Application | Application Component | Application | The logical application, independent of where or how often it is deployed. |
| Information Object | Business Object | Business | At the application level, a Data Object realizes it. |
| Business Service | Business Service | Business | |
| Business Service Offering | Product | Business | An offering packages a service with commitments such as hours and support levels, which ArchiMate expresses as a product (with a contract). |
| Technology Management Service | Technology Service | Technology | |
| Technology Management Service Offering | Technology Service | Technology | An offering of the parent service; model its commitments as a contract if you need them. |
| Application Service | Application Component | Application | Name trap: a CSDM Application Service is a deployed instance, not an ArchiMate Application Service (exposed behavior). It reads as an Application Component that realizes the logical Business Application. |
| Service Instance | Grouping | Other | The base class spans many kinds of instance, so it reads as a grouping of what delivers the service. Pick a specific type for a precise element. |
| Data Service Instance | Node | Technology | The platform that provides the data services; model the data itself as Data Objects or Artifacts if you need it. |
| Connection Service Instance | Path | Technology | A link between nodes through which they exchange data. |
| Network Service Instance | Communication Network | Technology | |
| Operational Process Service Instance | Equipment | Physical | The connected devices and machinery that carry out the process; model the process itself as a Technology Process if you need it. |
| Facility Service Instance | Facility | Physical | The facility whose services it represents, such as a plant, office or control center. |
| API | Application Interface | Application | |
| Application | System Software | Technology | Installed software such as a web server, database engine or container runtime. |
| Host | Node | Technology | Use Device when you mean physical hardware. |
| Network | Communication Network | Technology | |
| Strategic Priority | Driver | Motivation | A key focus area that motivates the organization's goals. |
| Goal | Goal | Motivation | |
| Target | Outcome | Motivation | ArchiMate outcomes are measurable end results, like CSDM targets. |
| Product Idea | Requirement | Motivation | A proposed product, feature or change: a statement of need. |
| Planning Item | Work Package | Implementation & Migration | |
| Value Stream | Value Stream | Strategy | |
| Value Stream Stage | Value Stream | Strategy | A stage is itself a value stream that its parent is composed of. |
| SDLC Component | Artifact | Technology | The developed code that realizes the application. |
| Product Model | Product | Business | The catalog definition of a product; elements are instances of it. |
| AI Application | System Software | Technology | |
| AI Function | Technology Service | Technology | A cloud AI service consumed on demand. |
| Kubernetes Cluster | Node | Technology | A cluster is a node that aggregates other nodes. |
| Kubernetes Node | Node | Technology | |
| Kubernetes Namespace | Grouping | Other | A namespace partitions a cluster; ArchiMate groups things with a grouping. |
| Kubernetes Workload | System Software | Technology | A containerized workload; model its container image as an Artifact if you need it. |
| Kubernetes Service | Technology Interface | Technology | A stable endpoint to reach a workload, which is what an ArchiMate interface is, not an ArchiMate Technology Service. |
| Kubernetes Pod | Node | Technology | An execution environment for its containers. |
| CSDM relationship | ArchiMate relationship | Reads as |
|---|---|---|
| Business Application → Application Service | Realization (reversed) | the deployed instance realizes the application |
| Business Capability → Business Application | Realization (reversed) | the application realizes the capability |
| Business Application → Information Object | Access | the application accesses the object |
| Business Process → Business Capability | Realization | the process realizes the capability |
| Business Process → Business Application | Serving (reversed) | the application serves the process |
| Business Service → Business Service Offering | Aggregation (reversed) | the product aggregates the service |
| Business Capability → Business Service | Realization (reversed) | the service realizes the capability |
| Technology Management Service → Technology Management Service Offering | Aggregation | the service aggregates its offering |
| Business Service Offering → Application Service | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Application Service | Serving | the technology service serves the instance |
| Application Service → Application | Serving (reversed) | the system software serves the instance |
| Application Service → Host | Serving (reversed) | the node serves the instance |
| Application Service → Network | Serving (reversed) | the network serves the instance |
| API → Application Service | Composition (reversed) | the instance is composed of its interface |
| API → Application | Realization (reversed) | the system software realizes the interface |
| API → Business Service Offering | Serving | the interface serves the product |
| Application Service → Application Service | Serving (reversed) | the dependency serves the dependent instance |
| Application → Host | Aggregation (reversed) | the node aggregates the system software |
| Business Capability → Business Capability | Aggregation (reversed) | the parent capability aggregates the child |
| Business Service Offering → Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Service Instance | Serving | the technology service serves the instance |
| Business Service Offering → Data Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Data Service Instance | Serving | the technology service serves the instance |
| Business Service Offering → Connection Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Connection Service Instance | Serving | the technology service serves the instance |
| Business Service Offering → Network Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Network Service Instance | Serving | the technology service serves the instance |
| Business Service Offering → Operational Process Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Operational Process Service Instance | Serving | the technology service serves the instance |
| Business Service Offering → Facility Service Instance | Serving (reversed) | the instance serves the product |
| Technology Management Service Offering → Facility Service Instance | Serving | the technology service serves the instance |
| Application Service → Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Application Service → Data Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Application Service → Network Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Application Service → Operational Process Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Application Service → Facility Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Application Service | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Data Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Network Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Operational Process Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Data Service Instance → Facility Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Application Service | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Data Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Network Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Operational Process Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Network Service Instance → Facility Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Application Service | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Data Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Network Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Operational Process Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Operational Process Service Instance → Facility Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Application Service | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Data Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Network Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Operational Process Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Facility Service Instance → Facility Service Instance | Serving (reversed) | the dependency serves the dependent instance |
| Service Instance → Connection Service Instance | Association | the path connects the instance |
| Application Service → Connection Service Instance | Association | the path connects the instance |
| Data Service Instance → Connection Service Instance | Association | the path connects the instance |
| Network Service Instance → Connection Service Instance | Association | the path connects the instance |
| Operational Process Service Instance → Connection Service Instance | Association | the path connects the instance |
| Facility Service Instance → Connection Service Instance | Association | the path connects the instance |
| Connection Service Instance → Network Service Instance | Realization (reversed) | the network realizes the path |
| Value Stream → Business Capability | Serving (reversed) | the capability serves the value stream |
| Value Stream Stage → Business Capability | Serving (reversed) | the capability serves the stage |
| Value Stream → Business Process | Realization (reversed) | the process realizes the value stream |
| Value Stream Stage → Business Process | Realization (reversed) | the process realizes the stage |
| Value Stream Stage → Value Stream | Composition (reversed) | the value stream is composed of its stages |
| Product Idea → Planning Item | Realization (reversed) | the work realizes the idea |
| Planning Item → Goal | Realization | the work realizes the goal |
| Planning Item → Target | Realization | the work realizes the outcome |
| Target → Goal | Realization | the outcome realizes the goal |
| Goal → Strategic Priority | Influence (reversed) | the driver influences the goal |
| Product Idea → Product Model | Association | the idea concerns the product |
| Planning Item → Product Model | Association | the work concerns the product |
| Business Application → Product Model | Association | the application is an instance of the product |
| Application Service → Product Model | Association | the instance is an instance of the product |
| Business Service Offering → Product Model | Association | the offering is an instance of the product |
| Technology Management Service Offering → Product Model | Association | the offering is an instance of the product |
| Application → Product Model | Association | the software is an instance of the product |
| Host → Product Model | Association | the node is an instance of the product |
| Business Application → SDLC Component | Realization (reversed) | the component's code realizes the application |
| SDLC Component → Application Service | Realization | the component's code realizes the deployed instance |
| Application Service → AI Application | Serving (reversed) | the AI software serves the instance |
| AI Application → Host | Aggregation (reversed) | the node aggregates the AI software |
| Application Service → AI Function | Serving (reversed) | the AI service serves the instance |
| Data Service Instance → AI Function | Serving (reversed) | the AI service serves the data platform |
| Kubernetes Cluster → Kubernetes Namespace | Aggregation | the cluster aggregates the namespace |
| Kubernetes Cluster → Kubernetes Node | Aggregation | the cluster aggregates its nodes |
| Kubernetes Cluster → Kubernetes Pod | Aggregation | the cluster aggregates the pod |
| Kubernetes Cluster → Kubernetes Service | Composition | the cluster is composed of the interface |
| Kubernetes Workload → Kubernetes Cluster | Assignment (reversed) | the cluster is assigned to run the workload |
| Kubernetes Service → Kubernetes Workload | Composition (reversed) | the workload is reached through the interface |
| Host → Kubernetes Node | Assignment | the host is assigned to run the Kubernetes Node |
| Host → Kubernetes Pod | Aggregation | the host aggregates the pod |
| Application Service → Kubernetes Workload | Serving (reversed) | the workload serves the instance |
| Application Service → Kubernetes Cluster | Serving (reversed) | the cluster serves the instance |