Top 4 Pitfalls to Avoid in CMDB Implementation

Top 5 Benefits of a Timesheet App
October 5, 2018
ServiceNow London Release – What’s in Store?
November 27, 2018

A successful CMDB can function as a powerful single source of truth for your entire organization. It serves as a basis for supporting your IT infrastructure and ITSM (IT Service Management). A CMDB enables improved control and tracking of IT assets as well as enhanced system reliability thanks to faster detection and correction of errors. The CMDB can also serve as the heart of a cloud platform such as ServiceNow when you wish to implement a single system across your entire organization simplifying work and inter-departmental processes

However, there is a high failure rate for CMDB implementations. This is largely due to certain common mistakes. Here are the top 4 pitfalls to avoid when implementing a CMDB.

  1. Treating Your CMDB as a Metadata Dump

Dumping data into the CMDB that has no real purpose makes management difficult and provides little value. Although the CDMB can manage a lot of data, you must consider what should be managed for maximum efficiency and business value. If you simply dump any and all data into your CMDB with poor relationship documentation, you are dooming your CMDB to sluggishness and ultimately failure. The key here is to only store the CIs (Configuration Items) that will be actively managed. This step will help you realize true value from your CMDB.

  1. No 3rd Party Integration

Think of 3rd party software as extra eyes, ears and bridges for your primary system, such as a ServiceNow implementation. Without 3rd party integrations your CMDB will fall out of date, as they are necessary to collect and provide comprehensive and up to date information. Take the time to plan and implement integrations with existing 3rd party software and this will go a long way to ensuring the accuracy and success of your CMDB in the long run.

  1. Lack of Effective Change Management

Implementing a CMDB is an ongoing process even after the CMDB has been set up. It’s not a one-shot deal where you leave it unattended after it is in place. Effective change management is crucial to ensure that your CMDB does not fall out of sync with the changing IT landscape of the organization. Such management must also ensure that only authorized changes occur to keep the CMDB up to date. Without these measures, your CMDB is likely to fall out of date and ultimately fail.

  1. Tough to Find CIs

Remember that there are many levels and categories of users in an organization and depending on their role, a user might have limited technical knowledge. In addition, many users only use the CMDB sparingly based on their job role, so the interface must be intuitive enough to serve them. If CIs (Configuration Items) in the CMDB are difficult to find, it is a tough task for these users to successfully use the CMDB in accordance with their job role.

Knowledge of these pitfalls can help you avoid unnecessary project delays and ensure project success, delivering value in a scheduled time-frame, so that the power of the CMDB can be harnessed for far-reaching benefits across the entire organization.

If you’d like a helping hand with your CMDB, please feel free to contact us. Our experts at abhra Inc. are experienced cloud solution providers and are ServiceNow implementation experts including CMDB implementation and healing existing CMDBs. ServiceNow provides automated discovery and mapping for the CMDB and can be a good choice for organizations looking to leverage benefits of the CMDB across various users, departments and processes.

Leave a Reply

Your email address will not be published. Required fields are marked *