SMB230 Optimizing your CMDB and
Change Management in Ivanti Service Desk
Bill Addenbrooke
Marcel Shaw
How do Change and CMDB work together
Change Management
The Request for Change (RFC) is formal request
for the implementation of a Change. The RFC is
precursor to the ‘Change Record’ and contains all
information required to approve a Change.
*http://wiki.en.it-processmaps.com/index.php/Checklist_Request_for_Change_RFC
What
drives
change?
Why do we need
change
mgmt?
Common Challenges around Change Mgmt
“Change is HARD.”
Determining Impact
Getting the right
stakeholders
Risk
IT Asset Management
The set of business practices empowering you
to manage your hardware and software
technology helping you gain the most from
your IT investments.
What drives Asset Management
Cost Risk Value
Translates IT data to:
Cost Risk Value
Common Challenges around Asset Mgmt
Getting the
complete list
of assets
Assets
Vendor
Purchases
Discovered
Network
Assets
How do we discover?
Reconciling Asset Data
Asset
CMDB
Change
Mgmt
Change Mgmt and Asset Mgmt compliment each other
Dependencies - Impact
Asset Ow ners - Stakeholder
Users - Risk
Benefits of a CMDB
How do I get started?
Leverage an integrated Asset and Service Mgmt solution
ITSM ITAM
As you begin each change, flag what Assets are CIs
Change
What’s
changing?
Create CI
Then begin to associate those Config Items to a Service
CI
Service
Let the Change Process Update Those Assets
Change started
CI
Update?
Add CI
to CMDB
No CI
How do bring it all together
Scenario 1 Demo
• Purchase Request for large order of Servers placed
• Servers upon arrival are immediately fed into AMDB
• Data moves from AMDB is made available to CMDB
• Change for new OS license count and users is fed into AMDB
Scenario 2 Demo
• New Change to add web server
• Available asset is selected to be added to infrastructure
• Asset is then updated as Deployed
• Server is linked as a supporting piece of infrastructure
DEMO
Thank you

SMB230: Optimizing your CMDB and Change Management in Ivanti Service Desk