The most important facts in brief:
- Structured ITIL-compliant IT documentation: An ITIL CMDB serves as a central database for all IT assets (configuration items, CIs) and documents their dependencies. This creates a transparent and standardised information basis for IT service management.
- ITIL CMDB as a central database: It structures and documents IT assets and dependencies for efficient IT documentation. Without it, data gaps and inefficient IT processes arise.
- Challenges during implementation: Multiple data sources make consolidation difficult. Cross-vendor solutions are rare, as many tools only cover sub-areas such as hardware and software inventory.
- Efficient data selection and automation: Only relevant data that can be captured automatically should be included. Too many details make it difficult to use and increase the maintenance effort.
Is an ITIL CMDB necessary for IT documentation?
This question is often asked in documentation projects. To answer it, we first need to clarify what an ITIL CMDB is and how it is structured. ITIL (IT Infrastructure Library) is an established process framework for IT service management (ITSM). The introduction of a Configuration Management Database (CMDB) or a Configuration Management System (CMS) is recommended as part of ITIL.
Structure and requirements of an ITIL CMDB
An ITIL CMDB is made up of configuration items (CIs) that can be linked to each other as required. For example, a network card (CI 1) can be recorded as part of a workstation (CI 2). A standardised ITIL CMDB should also contain baselines that document different configuration statuses and make them comparable.
A CMS combines several existing CMDBs into a standardised system. In practice, however, there is a challenge: many companies have multiple sources of information for their CMDB, which makes standardised data management difficult. In addition, manufacturers often offer proprietary methods for obtaining information, but a manufacturer-independent, complete ITIL CMDB is difficult to implement. Many software solutions mainly capture hardware and software inventories, while essential configuration data and application server settings are often missing.
Selection and maintenance of data
The complexity of the data is often underestimated. At the start of an IT documentation project, there is often a desire to transfer as much information as possible to the ITIL CMDB. However, it is important to bear this in mind:
- A high level of detail increases the maintenance effort and can cause more confusion than benefit.
- Automated data collection is essential, as manual maintenance is often neglected.
- The structure of the CMDB must be tailored to the subsequent deployment scenarios.
ITIL CMDB as the basis for IT documentation
A well-structured ITIL CMDB is an essential basis for IT documentation and, in particular, for system documentation. The process documentation often refers to the CMDB or regulates its maintenance and updating. It is also important to define processes in order to efficiently transfer changes in the CMDB to existing IT documentation and ensure updates.
For more on this topic: Professional IT documentation with Docusnap
