Skip to content

The Configuration Management Database (CMDB) in the OTOBO ticket system

The Configuration Management Database (CMDB) in the OTOBO ticket system

Section titled “The Configuration Management Database (CMDB) in the OTOBO ticket system”

The Configuration Management Database (CMDB) is a central component of the OTOBO ticket system and forms the foundation of modern IT Service Management (ITSM). It serves to record, manage, and link IT and non-IT assets, thereby enabling a transparent representation of the IT infrastructure and its dependencies.


A CMDB is a central database in which all information about a company’s IT landscape is stored. This information includes:

  • Configuration Items (CIs): Physical and virtual resources such as servers, laptops, software, network components, or even contracts and locations.
  • Relationships: The representation of dependencies and connections between individual CIs, which allows potential risks and the impact of changes to be identified quickly.

Through this central repository, the CMDB acts as a “Single Source of Truth” upon which all IT processes can be built.


Areas of application and benefits of a CMDB

Section titled “Areas of application and benefits of a CMDB”

The CMDB is used in numerous IT management processes:

  1. Asset Management:

    • Management of the entire lifecycle: From procurement to decommissioning, every piece of hardware and software is documented.
    • Transparency: All IT resources can be retrieved at any time.
  2. Incident Management:

    • Rapid problem detection: In the event of malfunctions, affected CIs can be quickly identified and isolated.
    • Efficient troubleshooting: Relevant information is immediately available to support teams.
  3. Change Management:

    • Risk minimization: Changes to the IT infrastructure can be planned in detail by visualizing dependencies.
    • Optimized planning: Through the transparent representation of CIs and their relationships, changes can be implemented safely and in a controlled manner.
  4. Compliance and Audits:

    • Audit-proof documentation: All configurations and changes are logged without gaps.
    • Audit preparation: A central database facilitates compliance with regulatory requirements.

The OTOBO ticket system seamlessly integrates the CMDB into the ITSM process and offers numerous functions that simplify everyday work:

  • Holistic view of assets:

    • All CIs and their relationships are clearly displayed.
    • Local data silos are dissolved so that all teams work with the same up-to-date information.
  • Real-time transparency:

    • Automated processes (e.g., Auto-Discovery) keep the database up to date.
    • Changes to the IT infrastructure are immediately reflected in the CMDB.
  • Efficient IT processes:

    • Incident and Change Management processes benefit from the rapid availability of relevant data.
    • Troubleshooting is accelerated, which ultimately increases service quality.
  • Compliance and audit capability:

    • Audit-proof recording of all configurations supports internal audits and compliance requirements.
  • Optimized customer service:

    • Contracts, Service Level Agreements (SLAs), and assets are managed centrally – leading to higher service quality and customer satisfaction.

OTOBO provides predefined categories and classes for recording Configuration Items. Standard categories include:

  • Location
  • Infrastructure, Network
  • Software
  • Workplace
  • Contract

These templates are based on best practices and can be adapted to specific company requirements.

The integrated YAML editor allows CI definitions to be designed flexibly. Dynamic fields, multi-column masks, and individually definable field sequences make customization intuitive and efficient.

The OTOBO CMDB supports the import and synchronization of data from various sources:

  • Auto-Discovery systems
  • Inventory tools
  • Directory services
  • Product databases

Synchronization takes place via REST or SOAP APIs, ensuring that data remains up to date.

Thanks to a hierarchical tree structure, the relationships between CIs are clearly visualized. This representation makes it easier to identify dependencies and take preventive measures to avoid disruptions.


Integration of Service Level Agreements (SLAs)

Section titled “Integration of Service Level Agreements (SLAs)”

In the OTOBO ticket system, Service Level Agreements can be managed directly in the agent interface. The integrated widgets offer:

  • Overview of existing SLAs: Display of all assigned services and their SLA times.
  • Detailed views: Widgets for displaying SLA information, relevant times, and deadlines.
  • Reports and statistics: Analysis of ticket numbers, average resolution times, and success rates, which support continuous improvement of service quality.

To exploit the full potential of the CMDB, the following measures should be implemented:

  1. Ensure data quality:

    • Regular validation and cleaning of data.
    • Use of automated collection processes to minimize manual input.
  2. Process integration:

    • Link the CMDB with central ITSM processes such as Incident, Change, and Problem Management.
    • Use the CMDB as a basis for informed decisions.
  3. Define clear responsibilities:

    • Determine roles such as the CMDB Manager or Change Coordinator to ensure data maintenance.
  4. Regular audits:

    • Conduct regular audits to ensure the currency and relevance of the data.

The CMDB in the OTOBO ticket system is an indispensable tool for companies that want to manage their IT infrastructure efficiently and optimize ITSM processes. Through the central storage of all configuration elements and their relationships, transparency and efficiency are increased – leading to better service quality and higher customer satisfaction.

Use the comprehensive functions of the OTOBO CMDB to sustainably improve your IT processes and identify risks at an early stage.


Sources and further information: