Measuring CMDB Value
A telecommunications company has invested heavily in CMDB and CSDM over the past two years. They have populated 150,000 CIs and implemented CSDM for business services and application services. However, the executive team is questioning the value of the investment because they haven't seen tangible benefits. The CMDB team reports metrics like 'number of CIs' and 'percentage of CIs with complete attributes', but these don't resonate with executives. The company wants to demonstrate the value of CMDB in terms of business outcomes, such as reduced incident resolution time and improved change success rate.
1. What is wrong with the current metrics, and what should be measured instead? Provide examples of business-relevant CMDB metrics.
Read the worked answer
The current metrics are output-based (number of CIs) and do not link to business value. Instead, measure outcome-based metrics that show how CMDB improves IT services. Examples: (1) Reduction in mean time to resolve (MTTR) incidents due to accurate impact analysis. (2) Increase in change success rate because dependencies are known. (3) Cost savings from decommissioning unused CIs. (4) Percentage of business services with complete and accurate mapping. These metrics should be baselined before CMDB improvements and tracked over time.
2. How can the CMDB team use CSDM to directly support the calculation of these business metrics? Describe the data relationships needed.
Read the worked answer
CSDM provides the structure to link business services to application services and infrastructure. For MTTR, the CMDB can show which business services are affected by an incident, allowing prioritization. For change success, CSDM relationships help identify impacted CIs and services, enabling better risk assessment. The team should ensure that business services are mapped to application services (CSDM layer 1-2) and that incidents and changes are linked to CIs. Then, analytics can correlate CMDB data with incident and change records to compute the metrics.