operating model · version 2026.1

Generic Cloud Infrastructure Operating Model

A vendor-neutral demand-to-operations view with governance, assurance, economics and provider boundaries.

Generic Cloud Infrastructure Operating Model. A vendor-neutral demand-to-operations view with governance, assurance, economics and provider boundaries.
PNG preview2400 × 951 px24 KBVersion 2026.1 · reviewed 2026-09-08
Explore semantic layers
Generic Cloud Infrastructure Operating Model previewqualifyrouterequirementsdirectionaccepttriggereconomicsexecuteperformanceProduct & application teams: Demand and business outcomesProduct & application teamsDemand and business outcomesCloud Governance / CCoE: Governance routingCloud Governance / CCoEGovernance routingCloud Service Management: Service lifecycleCloud Service ManagementService lifecycleCloud Architecture: Technical directionCloud ArchitectureTechnical directionPlatform Engineering: Reusable productsPlatform EngineeringReusable productsCloud Operations: Run and improveCloud OperationsRun and improveSecurity & Assurance: Risk and control authoritySecurity & AssuranceRisk and control authorityFinOps: Economics and actionFinOpsEconomics and actionMSP / technology providers: Delegated executionMSP / technology providersDelegated execution
Accessible diagram transcript

Objects

  • Product & application teams: Demand and business outcomes (Consumers)
  • Cloud Governance / CCoE: Governance routing (Governance)
  • Cloud Service Management: Service lifecycle (Service ownership)
  • Cloud Architecture: Technical direction (Authorities)
  • Platform Engineering: Reusable products (Engineering)
  • Cloud Operations: Run and improve (Operations)
  • Security & Assurance: Risk and control authority (Authorities)
  • FinOps: Economics and action (Governance)
  • MSP / technology providers: Delegated execution (Providers)

Directed relationships

  • consumergovernance: qualify (handoff)
  • governanceservice: route (handoff)
  • servicearchitecture: requirements (handoff)
  • architectureengineering: direction (handoff)
  • engineeringoperations: accept (handoff)
  • governancesecurity: trigger (authority)
  • governancefinops: economics (authority)
  • provideroperations: execute (handoff)
  • operationsservice: performance (feedback)
01

When to use it

Use as the opening architecture for a Cloud TOM workshop or executive design discussion.

02

What to challenge

  • Separate accountable authority from delivery execution.
  • Make every important handoff directional and reviewable.
  • Treat this reference pattern as a starting point, not a prescription.
03

Adapt it responsibly

  1. Rename functions to match the organization vocabulary.
  2. Remove elements that are genuinely out of scope.
  3. Validate decision rights and handoffs with accountable stakeholders.
04

Model contents

9 objects and 9 directed relationships. Every object keeps a stable semantic ID.

One model, multiple representations

The browser view and editable file are generated from the same canonical graph, so labels, roles and relationship direction stay aligned.

Clear visual grammar

Shape, color and connector style distinguish actors, governance, authorities, services, engineering, operations and providers.

Make this model your own.

Rename objects, adjust the scope and download an editable version. Your changes stay in this browser; no account is required.

Customize this diagram