Closed loop change and configuration management

This page provides some details about closed loop change and configuration management use cases.

Process overview

Integrating configuration management tools, such as BMC BladeLogic Server Automation, with the service desk for closed loop change and configuration management.

Key use cases

  • Operator-initiated change
    • Open a change and wait for approval before executing the BMC BladeLogic Server Automation job
  • Closed loop compliance
    • Open an incident for each non-compliant component
    • Open a change for a non-compliant component and relate it to an incident
    • Upon change approval, build and execute a remediation job on the schedule set in the change ticket
    • Validate remediation and close out related incidents and changes
  • Incident enrichment
    • Add recent configuration change information to incidents associated with monitored components

Closed loop change and configuration management


Business values

  • Cost
    • BMC BladeLogic Server Automation team no longer has to manually create and update service desk tickets
    • BMC BladeLogic Server Automation team no longer has to manually create remediation jobs
    • Less downtime to critical business services as change process is followed, reducing chances of unplanned changes or misconfigurations
  • Risk
    • Change/approval process is always followed before configuration changes can be made
    • Removes the “human factor” of making a mistake when making a change
    • Enables organizations to run significantly more compliance checks and to ensure environment is always compliant and secure
  • Governance
    • Changes are enforced and documented
    • ITIL processes are followed