User Guide › Design › Resources › Resources › Resources Life-cycle Management - Version Control And Change Sets

Resources Life-cycle Management - Version Control And Change Sets

Service providers continuously upgrade their physical infrastructure by adding, removing or changing the equipment used to service their customers. These changes are reflected by changing the resource attributes and documenting the changes per resource or as part of a wider change, in a change set.

The Service Delivery CMDB supports version control in individual resources for small infrastructure changes and groups of changes in a change set. Whenever a resource attribute is changed, the user must commit the change for this resource. The change may be committed by resource or groups of resources. In addition, the commit date (the date on which this change has become effective) can be changed between resources. Committing a resource means committing the changes made. Changes to a resource are not in effect until they are committed. This allows setting up resources in advance and committing them at a future date.

Organizations that implement ITIL conventions typically apply infrastructure changes following the release process and group many changes in one transaction. The Service Delivery CMDBs change set capability allows the user to group together a set of infrastructure changes and commit all changes on the same date.

The Service Delivery CMDB supports roll-back, roll-forward and complete transaction tracking over changes, specific resources or change sets.

Keeping a time-based track of changes at the resource level is crucial to retroactive or future change information. Even when CA Business Service Insight is informed only after the fact of the change, the system takes these changes into consideration by performing an automatic recalculation.

Moreover, the user can upload changes that occur in the future, in order to simulate and predict the business impact analysis of this change.

Note: Uncommitted resource values cannot be checked in Business Logic Scope. To check them, they must be committed. For more information on Business Logic Scope, see Testing Business Logic Formulas.