Configuration Management Database
Configuration Management Database ( CMDB) denotes a term used in computer science. After the IT Infrastructure Library (ITIL ) is in the CMDB is a database, which is used to access and manage configuration items. As a Configuration Item (CI ) are referred to in IT management all the resources of IT. The term Configuration is somewhat misleading. This is understood in this context, the existence and interactions of the managed objects.
A CMDB serves more than just the pure inventory. The aim is to all modules of the Service Support and Service Delivery Related to Configuration Items ( CIs) to support. These organizational and commercial information of a CI may include, for example, the user of the CI whose departments - but also acquisition and time values as well as obtaining information and information on the product life cycle of a CI.
Problem and the basic concept
Many companies use different databases side by side for problem, change, asset, as well as process data. Often there are ( inconveniently ) relevant information scattered to a CI and / or difficult to access different databases.
This is where the concept of CMDB. The aim is to clear all information from the above-mentioned To consolidate databases at one point and so to make the access to these data simpler and more transparent. Not necessarily have to be physically incorporated into a database system data. Instead, may be advantageous here to use a federated database management system.
Building a CMDB
Building a CMDB, depending on the specific requirements, be very tedious and time-consuming. Therefore, the use of a flexible CMDB, which enables the detection of individual CIs and their relationships and dependencies, and can be extended if necessary, individually and in stages is recommended. This allows on the one hand quick, visible results ( called " quick wins " to create goodwill in the management for the further implementation ) and on the other side all the freedom to describe your requirements.
So complex and labor-intensive are the building as well as the maintenance of a CMDB so indispensable both their existence as well as the timeliness and reliability of the processes and applications based on it. (Without a CMDB example, there is no efficient and effective problem management and change management).
Basic requirements for the software that are critical to building a CMDB, are according to leading analysts:
- Reconciliation ( Ist-/Soll-Abgleiche )
- Mapping and visualization as well as