SAF and IT management crosswalk

The matrix shows nearest concepts but does not define an automatic transformation. Each cell uses a correspondence type and a confidence code:

• D — direct, P — partial, C — composite, NA — not applicable;
• H — high confidence, M — medium, L — low.

For example, C/H means that a SAF object is consistently expressed through a combination of several concepts. Full scale definitions are in the common overview, while boundaries for CIs, assets, and records are on the relationships page.

ITSM, RITM, and ITIL

SAF object	ITSM	RITM	ITIL Version 5
Actor	Customer, user, provider, owner, and support role — P/H: roles of one Actor.	Consumer, participant, and management role — P/M.	Stakeholder, service consumer, customer, user, or sponsor — P/H.
Channel	Portal, service desk, point of contact, or access channel — P/M.	Consumer interaction plus an operational point of contact — C/L.	Service interaction or touchpoint — P/M; no separate formal type is publicly defined.
Service	Service — D/H; ITSM adds relationships and delivery terms.	Product or service in the management scope — D/M for Service; Product is broader.	Service — D/H; offering and product are separate management contexts.
Process	Process or part of a management practice — P/H.	Process and operational activity — D/M.	Value stream, lifecycle activity, and management practice — C/H.
Capability	Organizational or service-management capability or practice — P/M.	Capabilities, competencies, resources, and management area — C/M.	Management practice and four dimensions — C/M.
Information Object	Ticket, configuration record, knowledge, or documented information — P/M.	Managed object, document, and factual control data — P/L.	Information, resource, or record in the lifecycle — P/M; no common class equals SAF.
System	Service system, application service, or application CI — C/M.	System in the IT architecture area and managed object — P/M.	Digital product and information-and-technology resources — C/M.
Component	Application or technical component as a CI — P/H.	Architectural element plus CI or asset — C/M.	Product resource and configuration-practice objects — P/L.
Interface	Technical access point, contract, and CI — C/L.	IT architecture interface — P/L: public semantics are insufficient.	No universal formal element is publicly defined — NA/M.
Integration	Dependency, information exchange, and workflow — C/M.	Architectural integration and information flow — C/L.	Work and information flow between lifecycle activities — C/L.
Deployment	Environment or instance CI plus deployment activity or record — C/H.	Actual configuration, architecture, and production of a change — C/M.	Configuration item plus deployment or release work — C/M; work is not a SAF object.
Compute Resource	Infrastructure CI and/or asset — P/H.	Resource, IT asset, or configuration item — P/M.	Information-and-technology resource — P/M.
Network Segment	Infrastructure or network CI and dependency — P/H.	Network resource in the architecture or asset area — P/L.	Part of the information-and-technology dimension — C/L.

ISO/IEC 20000, FitSM, and COBIT

SAF object	ISO/IEC 20000-1	FitSM 3.0	COBIT 2019
Actor	Organization, service provider, customer, and interested party — P/H.	Customer, user, service owner, and process role — P/H.	Stakeholder, governing body, management, and organizational structure — C/H.
Channel	No separate object semantics — NA/H.	Communication or contact mechanism — P/M.	A channel may be part of a process or information, but is not a Core Model object — NA/M.
Service	Service within the SMS scope — D/H.	Service and service portfolio — D/H for Service.	Services as a governance-system component and subject of service objectives — P/H.
Process	SMS processes — P/H: the management context is narrower than a SAF business Process.	Service-management process — P/H.	Process associated with each governance or management objective — P/H.
Capability	Organizational capability to manage and deliver services — C/M.	Process capability and overall SMS capability — P/H.	Objective together with the seven governance-system components — C/H.
Information Object	Documented information and records — P/H.	Documents, records, reports, and configuration information — P/H.	Information flows and items — P/H.
System	Supporting technology without a prescribed decomposition — NA/H.	Service-supporting system or CI — P/M.	Applications within the services, infrastructure and applications component — P/H.
Component	No formal architectural type — NA/H.	Application or technical CI — P/H.	Application or infrastructure element as part of a governance component — P/M.
Interface	No formal architectural type — NA/H.	Technical CI or documented interface — P/L.	May be considered within applications and processes, but has no separate type — NA/H.
Integration	Managed as process or supplier interaction, not a type — NA/M.	Dependency and information flow between CIs or processes — C/M.	Information flow and interaction between governance components — C/M.
Deployment	Transition or change evidence and supporting technology — C/M.	CI in an environment plus release or deployment activity — C/H.	BAI/DSS work and actual configuration — C/M.
Compute Resource	SMS resource without architectural specialization — P/M.	Infrastructure CI and asset — P/H.	Infrastructure in the services, infrastructure and applications component — P/H.
Network Segment	No specialized type — NA/H.	Network CI and its dependencies — P/H.	Infrastructure element without a network metamodel — P/L.

IT4IT, SRE, and DevOps

SAF object	IT4IT 3.0.1	SRE	DevOps
Actor	Stakeholder, product owner, or team role — P/M.	User, service owner, SRE/on-call team — P/H.	Cross-functional team, product/service owner, and stakeholder — P/M.
Channel	A digital-product interaction channel is not a primary type — NA/M.	Critical user journey or entry point — C/M.	Customer-feedback channel or product touchpoint — P/L.
Service	Product or service model within a digital product — C/M.	Observable service boundary — P/H.	Product or service owned by a team — P/M.
Process	Value stream and management functions — C/H.	Reliability work, incident response, and operational process — C/M.	Delivery value stream and automated workflow — C/M.
Capability	Reference-architecture Capability — D/H.	Reliability-engineering capability — P/M.	Technical, process, and cultural capabilities — P/M.
Information Object	Management Data Object — P/H.	Telemetry, configuration, incident, and postmortem data — C/M.	Code, artifact, configuration, telemetry, and feedback — C/M.
System	Digital product and set of Functional Components — C/M.	Production system or service — P/H.	Product or service system and independently deployable architecture — P/M.
Component	Functional Component — P/H, but this is a management-architecture component.	Service or component dependency — P/M.	Loosely coupled component or service — P/H.
Interface	Functional Component interaction and data contracts — C/M.	Observable endpoint or dependency boundary — P/M.	API or contract through which parts are delivered independently — P/M.
Integration	Data Object flow between Functional Components — C/H.	Dependency, traffic flow, and telemetry path — C/M.	Pipeline, event or data flow, and system dependency — C/M.
Deployment	Lifecycle or release data and operational product instance — C/M.	Production instance and rollout — C/H.	Pipeline outcome plus deployment record — C/H; activity is not a SAF object.
Compute Resource	Technology environment in management data — P/L.	Resource or capacity unit of a production system — P/H.	Infrastructure as code and runtime resource — P/H.
Network Segment	Separate semantics are unnecessary in the management reference architecture — NA/M.	Network dependency, traffic path, and failure domain — C/M.	Network configuration and infrastructure dependency — P/M.

Canonical relationship groups

Group	SAF	IT management projection	Important boundary
Value and services	An Actor receives a Service through a Channel; a Process realizes a Service.	A service offering defines a terms variant; customer, user, and provider roles and an SLA/SLO specialize the relationship.	An offering, SLA, or technical service does not replace the SAF business Service.
Processes and capabilities	A Process requires a Capability; a System supports a Capability.	A practice, value stream, governance objective, and team capability organize work.	A practice or value stream is usually composite and does not equal one Process.
Applications and interfaces	A System consists of Components; a Component provides an Interface.	A CI, product boundary, Functional Component, loosely coupled architecture, and ownership provide the operational projection.	CI is a control role; an IT4IT Functional Component belongs to the management architecture.
Information exchange	A Process operates on an object; an Integration transfers an object.	A ticket, configuration data, telemetry, pipeline artifact, and management Data Object move between tools.	Record instances and telemetry do not become an architectural catalog.
Placement and infrastructure	A Deployment realizes a Component and is placed on a resource in a Network Segment.	A CMDB, IaC, cloud API, pipeline, and observability describe actual configuration.	A deployment activity or record is not a SAF Deployment.
Ownership and governance	An Actor owns an object; the governed level stores source and verification.	Service, product, and process owners, governing body, on-call, policy, audit, and assurance refine accountability.	One owner is insufficient for RACI, governance, and operational escalation.

Crosswalk usage rules

1. First identify the user question and authoritative repository.
2. Preserve source identifiers and create a separate mapping_id.
3. For partial and composite correspondence, document the transformation rule.
4. Do not create a fictitious SAF object for every ticket, SLO, CI, or pipeline run.
5. Check the validity period and direction of the reference.
6. Treat low confidence as a reason for manual review, not automatic import.
7. Do not use the table as evidence of conformity with an external standard.