Service Management Tools, Automation and Data
This domain tests how tools, automation and data support service management without replacing judgement. Expect ITSM platform capabilities, workflow, CMDB, catalogue, knowledge, integrations and APIs, automation and orchestration, AIOps, observability and data quality.
Core rules and concepts
- An ITSM tool supports workflows, records, reporting and integration. A tool does not fix a broken process; it automates whatever process exists.
- The CMDB, service catalogue and knowledge base are data products. They need ownership, quality rules and review cycles.
- Automation executes repeatable steps. Orchestration coordinates multiple automated tasks across systems.
- AIOps and analytics depend on clean, complete and timely data. Poor data produces confident but wrong recommendations.
- Automation needs identity checks, audit logs, exception handling and a manual fallback.
Worked example
A team wants to automate password resets. They measure volume and failure modes, verify identity checks, design self-service with MFA, log every action, define escalation when verification fails, pilot with a small group, and measure reset success and security events. The reasoning is to automate a stable, understood process with controls, not to automate chaos.
Traps
Buying a tool to solve a process problem; automating a broken workflow; treating the CMDB as a one-time project; integrating systems without data ownership; deploying AI or chatbots without fallback and monitoring.