CA Service Management

  • 1.  CA CMDB vs SDM CMDB and some additional questions

    Posted Apr 05, 2013 11:04 AM
    Hi,

    I work at GEHC, and we are evaluating some options for one of the projects we are working on. I had a couple of questions:

    1. What additional capabilities does CA CMDB provide over SDM CMDB? Are they replacable?
    2. Could someone explain what they use either or both of these systems - at a high level?

    Thanks
    Preetham


  • 2.  RE: CA CMDB vs SDM CMDB and some additional questions
    Best Answer

    Posted Apr 05, 2013 11:25 AM
    Preetham, I hope all is well at GEHC.

    1. The CA CMDB and the SD CMDB are EXACTLY the same technology. When CA started creating CMDB capabilities, we sold it as a separate technology. So those with Service Desk could add the CA CMDB to the product. With CA Service Desk Manager, it is included. But, they have all the same capabilities.

    2. A CMDB is used to link supporting Configuration Items (CIs) to the business services they are supporting. Such as: Servers, Routers, Switches, Applications, Databases, etc. The relationship between these components help with understanding the potential impact of a pending change, as well as in an outage (Incident) situation, what the Root Cause could be. For more information on the CMDB look in the Documentation at the CMDB tech reference guide.


    Start Smart Philosophy:

    Select 1 Business Service to map the supporting CIs

    Determine the top 30-60 CIs that you know about that support this Business Service

    Classify each of these CIs into the proper Service Desk Manager Class/Family

    Determine by CI family which attributes are CRITICAL to track (no more than 6-10 per family)

    Determine by CI family which relationship are CRITICAL to track (no more than 6-10 per family)

    Determine by attribute and relationship if there are discovery technologies that can be considered a trusted source (MDR – Management Data Repository) of information for the attribute or relationship (only one trusted source per attribute or relationship)

    Setup the MDR for each attribute and or relationship

    Pull the information into the repository for that single business service for only those supporting CIs above into the Transaction Work Area

    Validate that the CIs, attributes and relationships look as anticipated; if not, fix the information at the MDR/trusted source; if it is move it into the live CMDB
    • Find the next Business Service and begin again (this will be faster since you have already mapped out many critical CI attributes and relationships, as well as the supporting MDR to provide the information by family

    Hope this helps.

    Randal Locke
    The ITIL "Texas Ranger"
    VP - Customer Lifecycle Solutions
    CA Technologies

    [color=#f00101]ADMIN:[color] Kyle_R. 2013-4-12. Flagging Randal's reply as the solution.