13 October

Adopt a CMDB today! A step by step guide to CMDB Implementation

Do you break out into a sweat just thinking about Configuration Management and CMDB? I know the effort can seem overwhelming, but don’t fear. We know how daunting a task it may seem but with some guiding principles – a good project management framework and some helpful tools developed by people who have “been there – done that”, we can assure you that there is some light at the end of the tunnel.

The identification and management of configuration items (CIs), assets and critical business services along with their relationships to each other are essential to establish and maintain a successful service management program, but where to start can absolutely be intimidating.  By taking a maturity model approach, organizations can quickly establish a foundational CMDB to gain immediate value while strategically building additional value in the more mature areas of change management, configuration management and service level management.

Your actual challenge isn’t to create a CMDB, but to maintain one with quality and accurate information to support the many aspects of service management and ultimately assist IT in ensuring they remain relevant to the enterprise.

The Step by Step Guide

Depending on the level of awareness and Configuration Management process maturity, we can provide you with a refresher covering what a CMDB is (and isn’t!), the difference between Services, Configuration Management, Asset Management and Inventory Management. We can also recommend addional training if that’s an immediate requirement.

The next thing we will review with you is the CMDB Implementation Methodology and walk you through the critical path and things to consider along the way. Some of the key highlights will include building a business case, and determining your scope! You will have to consider a top-down services approach or a bottom – up discovery approach. Not to fear, there is guidance on both approaches to determining your scope.

Value Based Outcomes

A key piece to remember to help you get started on the right foot is identifying your “why”. What are your value based outcomes? Here are a few to consider that may be the answer to your “why”:

  • Achieve higher levels of customer satisfaction
  • Improve Service Levels
  • Enable accurate incident routing
  • Facilitate and expedite Root Cause Analysis
  • Reduction risks to Production Environments
  • Minimize incidents and outages
  • Simplify Impact Analysis with visibility to dependencies
  • Improve your change success rates
  • Improve estimation of resources and capacity for new application and service releases
  • Reduce maintenance contract costs and license fees
  • Increased accuracy of service costing
  • Improve service level tracking
  • Simplify customer charge models
  • Lower asset TCO