Tracking changes to CIs by using Compare activity


If you use BMC Helix ITSM: Asset Management with BMC Helix CMDB, you could instead track changes with the Compare Dataset reconciliation activity.

As a configuration manager, use the compare activity in a reconciliation job to compare CIs between two datasets to track the changes made to the CIs. The compare activity produces a detailed report about the differences in CIs in the two datasets. You can compare only those dataset instances that have been identified during the identification activity and that have the same reconciliation ID.

Scenario

Chris, a configuration manager at Apex Global, is responsible for the accuracy and integrity of the CIs in the production dataset. To effectively track changes made to CIs during daily operations, he monitors the sandbox dataset, BMC.ASSET.SANDBOX, within the organization’s asset management system. This configuration ensures that any user edits to a CI are initially saved to the Sandbox dataset, providing a controlled environment for review.

To monitor and validate these changes, Chris configures a reconciliation job that uses the Compare Activity feature to compare the Sandbox dataset with the production dataset, BMC.ASSET. This comparison allows Chris to:

  1. Validate that the changes align with organizational policies and standards.
  2. Approve or reject modifications before they are incorporated into the production dataset.
  3. Identify and address any unauthorized changes to maintain data integrity.

By leveraging the Compare Activity feature, Chris ensures the production dataset remains consistent, accurate, and compliant with organizational requirements. This approach supports Apex Global in maintaining a robust and reliable configuration management process, critical for the organization’s operational efficiency.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*