Skip to main content

Change Management Requirements

Change Management depends on accurate CMDB data and clear ownership. This guide summarizes the typical prerequisites for Cloudaware Change Management.

Platform Prerequisites​

  • CMDB inventory present: connect your cloud providers and/or on‑prem sources so that relevant CIs exist in CMDB (see Integrations).
  • Ownership and context: use Cloudaware Virtual Applications tiers and relationships, so approvals and notifications can be routed by impact.
  • History tracking enabled where needed: decide which CI classes and fields require “before/after” history and enable tracking accordingly (see History & Audit).

Process Prerequisites​

  • Defined change types: standard, normal, emergency, and release/project changes.
  • Approval policy: which changes must be approved, by whom, and within what windows (see Approvals).
  • Evidence expectations: what must be attached for audits (implementation logs, validation results, rollback confirmation).

Integrations​

  • ITSM: ServiceNow or another ITSM to manage change requests and CAB records (see ServiceNow).
  • Notifications: Slack/Teams/email for approval requests and change alerts (see Notifications).
  • Webhooks/API: to connect CI/CD pipelines and custom tooling (see Webhooks).

Agents and Telemetry (Optional)​

Permissions and Roles​

At minimum, define who can:

  • Configure approval processes and automation (typically admins/platform owners).
  • Submit for approval and schedule changes (change managers/operators).
  • Approve changes (CAB members, service owners, security).