Managing Configuration Items › Configuration Audit and Control Facility (CACF) › Planning and Implementing Change Verification

Previous Topic: Determine the Action for a Rogue Change

Next Topic: Set Up the Environment

Planning and Implementing Change Verification

The Configuration Manager wants to implement change verification so that the CMDB contains correct data. The Change Manager wants to help ensure that changes execute correctly, and is concerned with rogue changes and understand the number of rogue changes that occur and from which data sources. Both managers agree implementing change verification provides significant value to the organization. The Change Manager wants to help ensure that any changes to the Change Management process do not harm the production environment.

The Configuration Manager and the Change Manager agree to a conservative-phased implementation, so that a Configuration Administrator implements policies for specific locations and specific CIs in those locations. This scenario describes example phases about completing the verification policy implementation to a broader audience for your organization.

The following diagram shows how a Configuration Administrator completes the example phases to implement change verification:

Diagram that shows how to plan and implement change verification.

  1. Set Up the Environment.
  2. Gather Information About Changes to a Managed Attribute.
  3. Determine the Scope of Rogue Changes to the Attribute.
  4. Prevent Rogue Changes to the Attribute.
  5. Require Change Specifications when Updating the Attribute.