4 CMDB Mistakes You Must Avoid at All Costs

A healthy CMDB (Configuration Management Database) is the foundation for your IT infrastructure and ITSM for your entire company. With this single source of truth, you can easily track IT assets and CIs (Configuration Items) with complete visibility and faster error detection and correction.

Unfortunately, certain mistakes are all too common when implementing a CMDB. These can hold you back from making the best use of the database, especially when you’re using the CMDB as the core for ServiceNow or other systems.

1. Forgetting About Integrations

Most organizations have third-party software in place for various purposes. When you forget to integrate them with your CMDB and your ServiceNow implementation, you’re crippling the database in terms of staying accurate and up-to-date. Such integrations are necessary to collect accurate and timely information for your CMDB, so you must plan how you will implement those integrations with relevant third-party software within your organization.

2. Overloading Your CMDB

This mistake is far too common—not everything should be recorded in your CMDB. When you overload it with all your data, it is going to be difficult to manage. A sluggish CMDB with too much data could even fail in the long-term. The goal is to record CIs that will be actively managed, not any and every detail you can think of. Keeping your CMDB lean and efficient will help you realize maximum efficiency and business value.

3. Making CIs Hard to Find

Not every user needs to see every CI in the CMDB, but no user should be left floundering and unable to find the CIs they require. Essentially, various categories of users require different CIs, and some users will probably have minimal technical know-how. The interface of your CMDB must be user-friendly and intuitive enough to cater to all categories of users. If some users struggle to find certain CIs, it will be difficult for them to use the CMDB for their tasks, and you’re also not making the best use of it.

3. Lacking Clear Ownership

A CMDB is not “set it and forget it”—someone needs to watch over it. Surprisingly, many organizations do not implement clear ownership and change management for the CMDB. Clear ownership ensures that someone (i.e., a configuration manager) is responsible for it, and keeping it up to date as changes take place in the organization. The configuration manager must ensure that the CMDB stays in sync with overall IT strategy so that it stays healthy and current. In addition, the configuration manager must ensure that only authorized changes are allowed. This type of effective change management keeps your CMDB ticking along with the pulse of the organization.

If you need assistance with your CMDB for ServiceNow, please contact us and we’d be glad to help. We’re an Elite ServiceNow partner and exclusively, 100% laser-focused on ServiceNow. ServiceNow’s automated discovery and mapping allows organizations to leverage maximum value from their CMDB. Let us bring our industry-leading laser precision and dedication to your organization.

Mike Roberts
Mike Roberts is VP of Marketing for Aptris. He joined in 2010 with 20 years of experience in sales, marketing and communications. He coordinates Aptris’ overall marketing and branding strategies.