Use Case- How CMDB will help the change management:

In change management, it is vital to know what CIs are affected by a given change.
Using the BSM map, its often useful to see this in a related list directly on your
change form as well. The Impacted Services related list in the change form,
populates this data. This UI action gathers all of the information about the CIs in
change request and adds the impacted services to the list.

The relationship model for change management plays an important role in impact
analysis of the change to the CI and determines who would be impacted, what the
risk was and hence, who would be the right person to get approvals from.

For Eg:

In the below screenshot, related items with open changes associated with a CI are
identified with a Clip icon (highlighted in orange).

Hovering the mouse over it bring up popup (highlighted in orange) that display the
CI information and the associated Change Record Number. Based on the roles and
privileges the user has, he or she can open the change record and view the
complete detailed information including the schedule, assignment groups and
description pertaining to the change number. The user will also be able to see the
affected CIs (if any) associated to the change.
 i. Change Management Pain Points that can be
reduced with a CMDB
Pain Point Possible Cause How will a CMDB Help?
Changes fail: They
are backed out or Dependencies were not
require re-work to identified before
resolve issues with deployment.
installation.
During the change
impact assessment,
dependencies have to
be identified manually.
Change turnaround The Change Manager
time is too long. and CAB must consult
with SMEs to gain an
accurate understanding
of potential impact and
risk.
A change causes a
service impacting
incident.
Users and support
staff are disrupted
by changes.
Change team was not
able to identify all the
impacted users or
support staff.
When a change request
is received, the
change team can
query the CMDB to
identify all
configuration items
that will be impacted
by the change.
Change assessors and
approvers can access
information about the
impacted
configuration items,
and their relationships
to other systems and
applications, in a
central location.
This saves time by
eliminating the need
to manually
investigate the
dependencies of every
request and helps the
change team identify
more dependencies
before they cause
issues during
implementation.
The change team can
use the CMDB to find
out which users and
systems will be
impacted by the
change, ensuring that
all affected parties are
informed of the
change in advance.