For companies that want to operate efficiently, it is essential to bring together all business-relevant information from distributed data sources in a central location. In the best case, this location is a Configuration Management Database, or CMDB for short. Here we tell you what a CMDB is, what benefits it brings, how it must be structured, and how it is maintained to provide optimal benefits.
A CMDB is a data pool that stores all information about the configuration of elements within an organization. The IT organization determines exactly what should flow into the CMDB database. This may include the following elements …
Once fed into the Configuration Management Database, configuration data is related and interdependent. That is, they can be assigned to classes and attributes. Any change to an element or the relationship to other elements is automatically recorded and documented. But how does that work exactly?
A CMDB contains a set of data or elements. These elements are called Configuration Items (CIs). As defined in ITIL 4, CIs are “all components that need to be managed in order to provide an IT service”.
For example, an asset, such as a laptop, can be a Configuration Item, but it does not have to be. The decisive factor is whether the asset is configurable and has relevant dependencies to other elements. When planning and defining dependencies in a CMDB, the following should be considered to make the system work:
Here is an example to make what has just been said easier to understand: For each device (for example, a laptop), all its properties, such as …
… are recorded. But that’s a lot of information needed per device. If you multiply this by the number of devices in the company (all laptops), the amount of data stored, or the effort required to store it, becomes infinitely large, not to mention unmanageable.
If, on the other hand, the new documentation is created in a CMDB and the affected CIs (again, the laptop example) are given a logical relation to this documentation, the data updates automatically. This saves time and resources, because in the optimum case, the new software version is identified during the automatic capture of the CIs (via a discovery engine) and the new documentation is set in relation via automation rules .
Relations are also used to recognize dependencies. If, for example, an external service provider fails, it can be selected in the CMDB and a list of all sites or devices related to this service provider can be displayed. Therefore, when planning a CMDB, consider the following:
The CMDB can therefore exchange data, determine dependencies and configure properties with various systems as part of IT service management (ITSM) – in short, a CMDB has many features.
However, a CMDB is not an isolated system, but also forms a basis that can be accessed by all systems used in the company. Here are a few examples of how a configuration management database works together with various systems:
A monitoring solution receives information about the systems to be monitored from a CMDB. At the same time, it reports back on the status of the respective assets, which in turn is stored in the CMDB.
A discovery engine or software periodically scans the network for connected devices. The information in the corresponding configuration items (CIs) in the CMDB is then updated with the data obtained.
A mapping function that ensures unambiguous assignment of data and status information. This makes it possible to connect any sources quickly and flexibly.
The service desk benefits from a CMDB in a special way. If, for example, monitoring reports a fault in a system, a corresponding ticket can be opened automatically. This not only contains information about the type of fault. The CMDB simultaneously provides all available information on the affected system.
Conversely, a service desk employee can access the CMDB data in the event of a fault report. This gives him a complete overview of the faulty systems in a short time.
In problem management, a CMDB can help with root cause analysis and lead teams to the heart of a problem faster. It can also support proactive problem management and help teams identify assets that need upgrades to lower service costs and reduce unplanned outages.
In change management, a CMDB can improve risk assessment by anticipating which users, systems and other CIs may be affected.
Technology managers need CMDB data to plan generally at the enterprise architecture and portfolio management level as well as in detail at the capacity and asset management level.
IT Finance must be able to access application or service code records to allocate billings and properly manage company finances.
Auto-Discovery fully automates the populating of the CMDB solution. The integrated monitoring continuously records status information and changes. All objects, their properties and status are thus always up-to-date and centrally available.
By building a CMDB, companies obtain a valid database of high-quality information that not only minimizes the time it takes to obtain information, but also forms the basis for improving process and service quality.
The goal of a CMDB, then, is to provide organizations with the exact information needed to make better business decisions and execute ITSM processes efficiently.
The possible uses and application examples for a CMDB in the company are diverse and all company areas can benefit from it. Because it offers:
The CMDB thus contains information from all areas of your company, saves it in the CIs, establishes connections between them, and makes information available to employees and managers across departments and centrally.
By centralizing all configuration information, all staff and management can better understand critical CIs and their relationships to each other. A CMDB can thus be of great benefit as a consequence in important ITSM processes :
The following graphic illustrates well how ITSM processes, database configuration management, the discovery engine and process automation are interrelated.
We list the benefits your company will gain from implementing a powerful CMDB in the following section.
A CMDB saves time and avoids idle time by eliminating the need for your team to cycle through dozens of tools to determine the information they need. No matter whether you are looking for information on a server from monitoring, an invoice from financial accounting or the last correspondence with the technical department in order to be able to rectify a fault: All information and documents are available in the CMDB.
An always up-to-date CMDB…
However, the greatest added value is the reliability of information. Since there is no longer any local documentation and all changes are documented in the CMDB, highly up-to-date information is always available to employees in all departments.
The tedious and error-prone comparison between different documentation data to determine the current version is thus history thanks to a well-maintained CMDB. In regulated industries, it can additionally support compliance, help teams manage controls, and provide a clear audit trail.
However, in order to reap these benefits, it is important to take certain steps within the company and leave nothing to chance when implementing a CMDB. Find out now what requirements a successful CMDB implementation entails.
The decisive factor in determining whether a CMDB can be used efficiently is its structural design. This means that it must be designed according to current company-specific requirements. Currently, this means that the requirements and needs in a company can change. A CMDB must be able to follow such changes and map them correctly, preferably in real time.
To benefit from the advantages just mentioned, you need to plan well and overcome various challenges. Here we name the three most important:
A CMDB can quickly become one of the largest data stores in your organization. This is because it often additionally contains a copy of data from other source systems in order to be used effectively and to map the complete company. Then, as companies grow and develop, the data set can become quite large and then you need to be able to act.
A CMDB is only as good as the timeliness of its data. So if your IT environment changes, the data stored in your CMDB must also change as a result, and features such as auto-discovery help you do just that. This means new assets, removal of retired assets, changes to existing assets and the relationship between them must always be up to date. In addition, outdated or obsolete information should be updated or cleaned up as automatically as possible.
The value of a configuration management database lies not only in its data, but above all in its correct use. So to use a CMDB effectively, you need …
… to make efficient use of all configuration data. But it is not only certain challenges that a CMDB poses to you, you should also plan well for the introduction in the company itself. Because properly implemented, a CMDB facilitates the work of your IT teams at all levels and significantly optimizes the quality of your digital services.
Industry statistics, such as those from Gartner Research, show that only 25% of organizations are seeing meaningful value from their CMDB investments. Because of this low success rate, the technology has a rather dubious reputation. However, this poor reputation does not come from the performance of the CMDB itself, but rather from the incorrect use and poor implementation of the system.
In each company, it must be determined whether the introduction of new technologies and processes will be successful. In a recent Harvard Business Review study, 93% of executives said the biggest challenge in data-driven digital transformation is employee knowledge of these processes.
To help you overcome these challenges, here are 5 tips to help you successfully implement CMDB management.
CMDBs are often described as a central source of information. This sometimes leads to companies trying to squeeze all their data into one database without thinking about whether the data is even relevant.
As with any data pool, a CMDB should contain only focused, useful data that also supports internal business processes. So make sure that your CMDB has a clearly defined benefit and offers the possibility to update data, to map all changes and that there are also clear responsibilities for this.
When we refer to a CMDB as a central location for viewing asset data, it does not mean that all asset data must reside exclusively in the CMDB. For example, it makes more sense to store financial data in an IT Financial Management (ITFM) tool and software license information in a Software Asset Management (SAM) tool.
The data can then be imported into your CMDB and mirrored, even if this is not the primary storage location.
The most common problems with using a CMDB are that …
A suitable solution to these challenges is event-driven detection, which complements traditional bottom-up detection. Bottom-up discovery assigns assets from infrastructure to customer-facing CIs.
Event-driven detection occurs when, for example, an event occurs within a system or a problem occurs that results in communication between systems. Based on this event, the system then assigns the associated CIs and their connections.
CMDBs are used not only to model older infrastructures and software, but also to catalog new infrastructures and their associated workflows.
Choosing the right tool is hugely important for a CMDB to add value to business processes. Some CMDB tools are nothing more than data structures that are slow to respond to changes. So, to work successfully with a CMDB, you need a powerful configuration management database tool.
REALTECH’s SmartCMDB software does just that by creating a database for automating your IT processes. It provides access to all information as well as assets of your organization. Thus, it supports you during audits or the analysis and monitoring of your critical infrastructures. And we help you with the implementation in the company through our support team. We also help you solve the challenges and issues you and your employees face.
Perfect! Just book your free demo here or write to us.
In addition to the high requirements for the introduction of a CMDB – from a practical and company-related perspective – the maintenance of a CMDB is a challenge that should not be underestimated. After all, the data is only as good for the processes and users as it is up-to-date and correct.
When employees are given outdated or incorrect data to perform their tasks, their work is often rendered moot and useless. This leads to frustration and distrust among users and can result in CMDB bypass or unacceptance of the CMDB solution. This is exactly why a CMDB must be well maintained. This is ensured as follows:
Optimally, this can already be documented in the CMDB and, if necessary, also displayed to the user as information. Because with the dynamics of today’s business world, an intelligent, standardizing discovery engine is indispensable. It must be able to reliably identify various technical objects, read out their status and configuration, and make them easily accessible to the user on a normalized basis (with uniform designations and notations).
In addition to the intelligent discovery function, the CMDB must have sufficient interfaces and methods to be able to cleanly match data from third-party systems at any time. In short, a uniform image of the heterogeneous reality should always be generated in the CMDB.
Only if configuration items (CIs) and their relations are up-to-date and the metamodel adapts to constantly changing conditions can the CMDB exploit its true potential and become a valuable, reliable tool.
Implementing a CMDB involves a lot of work, but this effort is rewarded. Because the benefits of a functioning CMDB are enormous. By creating a binding information point, you create added value – not only for the IT department, but for all departments incl. Management. In short, you not only make processes within the company more efficient, you optimize your entire company by means of a CMDB.
CMDB is the abbreviation for Configuration Management Database, i.e. a central database that contains all relevant information about the hardware and software components of the IT infrastructure used by IT services.
The purpose of a CMDB is to identify, store, monitor, determine, catalog, and report on service assets and CIs to designated locations. This leads to saving time, ways and resources by storing all relevant information needed to achieve business goals in one place.
A CMDB contains so-called configuration items (CIs). CIs are all components that have to be managed in order to provide an IT service. For example, an asset, such as a laptop, can be a Configuration Item, but it does not have to be. The decisive factor is whether the asset is configurable and has relevant dependencies to other elements – then it belongs in a CMDB.
