Vendor-neutral adoption patterns for technical customer conversations after the initial AIOps pitch. AI identifies opportunities; automation delivers outcomes.
What these pages are for.
AIOps Use Cases explain when Event-Driven Ansible, AI enrichment, and Automation orchestrator earn their place for a given operational pattern. They are not partner Solution Guides. Partner technologies may appear as examples; start with the foundational AIOps Solution Guide for the reference architecture, then open partner integrations from each use case’s Related Guides section.
| Maturity | Focus | Use cases |
|---|---|---|
| Crawl | Build visibility and enrich insights | Incident and Ticket Enrichment, Cost and Resource Optimization |
| Walk | Orchestrate and automate with intelligence | Intelligent Capacity Orchestration, Curated Automation Remediation |
| Run | Autonomous operations and continuous enforcement | System-Level Drift and Policy Enforcement, Self-healing infrastructure |
The two Run links above are separate conversation topics (prevent drift vs close the break-fix loop), not a mandatory sequence.
Self-healing (use case 6) models curated Run execution from an approved library; the optional multi-LLM workshop appendix on that page is for lab and policy-governed exceptions only.
Workflows can begin from a human request, an observability event, an ITSM ticket, or a scheduled review. The use case describes the pattern; the entry point depends on the customer environment.

Solution Guides answer “how does AAP plus a partner solve X?” Use cases answer “which pattern are we selling, and when does each platform layer matter?”
Return to the Solution Guides catalog for partner integrations, or filter by partner on the homepage.