Valuemation: Software für IT Change + Configuration Management (CMDB)

The software for your IT change and configuration management (CMDB)

Make your IT infrastructure transparent

The Configuration Management Database (CMDB) provides you with a comprehensive overview of your IT infrastructure:

  • Central entry of IT components (configuration items / CIs) and their relationships and dependencies with/on each other
  • Entry of physical components (e.g. servers, databases) and logical components (services)
  • Audit-compliant documentation of all changes using the change process
  • Automatic comparison with physical inventory data to identify unapproved changes

    Identify dependencies and risks

    The ITIL®-compliant Configuration Management Database (CMDB) is an important foundation for low-risk, secure IT operation:

    • Graphical presentation of CI dependencies – from the customer, service, to infrastructure components
    • Display of error statuses from monitoring
    • Ascertainment of the effects and risks of changes (impact analyses)
    • Identification of the causes of problems (root cause analyses)

    Identify deviations between the target and actual inventories in the CMDB

    Separation between the target and actual inventories ensures a high quality of data:

    • Automated maintenance of the target inventories by means of ITIL® processes
    • Automated capture of the actual inventories by means of inventory/discovery tools
    • Automated target/actual reconciliation to identify changes that have not been approved or have not been carried out

    Merge configuration data from different sources

    Integration of external data sources enables a federated CMDB:

    • Any desired data sources are linked and integrated by means of interfaces.
    • Configuration data remains in the source systems and is not duplicated.
    • A cross-system, consistent data model is not necessary.


    Avoid frequent stumbling blocks in rolling out your configuration management database (CMDB)

    Best practices: Benefit from the experience gathered from many CMDB projects.

    1. CMDB management and planning

    In the planning phase, the strategy, objectives, scope, processes, KPIs, roles and interfaces to the stakeholders in configuration management (e.g. in change, incident and problem management, etc.) are defined.

    Frequent stumbling blocks are:

    • Unclear content, no common vision: A CMDB tool is often purchased first of all and then everything else is only defined in the course of the project.
    • Too large a scope with unrealistic deadlines: Everything is to be tackled with one big, sweeping blow.
    • Wrong priorities: Sensible priorities cannot be defined without adequate goal orientation.
    • Unclear role assignment and process interfaces: Defining responsibilities is essential in configuration management.

    2. Identification of the CMDB configuration

    In the identification phase, the configuration model is defined so that the CMDB can incorporate all necessary information on the CIs (the IT infrastructure and service components).

    Frequent stumbling blocks are:

    • Different understanding of terms: Are services, applications and software synonymous terms? Definitely not!
    • Too much detail: It is often the case that every nuance, no matter how insignificant, is maintained in the CMDB, especially for attributes.
    • CI maintenance for attributes not completely clarified: Is a technical attribute, such as the CPU, maintained automatically or manually?

    3. Controlling of the CMDB

    The aim in the control phase is to ensure that changes to the CMDB are carried out only as part of other ITSM processes, such as change management, and that no unauthorized changes are made.

    Frequent stumbling blocks are:

    • The CMDB data is maintained only in configuration management by a dedicated “maintenance team”: No, better not! Think in a process-oriented way.
    • Poor data quality: If the quality of the data is too low, the CMDB lacks reliability and trust in it is lost.
    • Verification and control mechanisms introduced too late or not at all: Plan verification and control mechanisms before filling the CMDB for the first time.

    4. CMDB status proof and reporting

    In the reporting phase, proof of the status of all recorded CIs is furnished and their status is continuously monitored over their entire lifecycle, i.e. from planning to removal from service.

    The issue of reporting is often underestimated here. Many requirements are placed on configuration management in the course of the project, especially from adjacent ITIL® disciplines. You may need to plan reporting across CMDBs (including the interfaces to be supplied).

    5. CMDB verification and auditing

    In the verification phase, regular checks and audits are established and conducted. That ensures compliance with the processes in configuration management and that the data in the CMDB is up-to-date, complete and correct.

    Frequent stumbling blocks are:

    • Irregular auditing: Organizations often shy away from the cost and effort involved in audits and so they are conducted too seldom.
    • Audit result “Old labels on physical devices”: The label has not been updated after a device has been renamed. The only remaining criterion to identify it clearly is the serial number.

    Practical guide: configuration management database (CMDB)

    However, there are still a number of other things to consider so that your CMDB project succeeds. In this extensive practical guide, you can read about what you should heed in detail.

    Read the practical guide now

    Reduce risks from changes to the infrastructure

    The ITIL®-compatible change management processes reduce the risks involved in changes to your IT infrastructure:

    • Standardized processes for applying for, planning, approving and implementing changes
    • Flexible adaptation of processes for standard, normal and emergency changes
    • Initiation of change processes from the troubleshooting process (request for change / RfC) or using the service catalog (service request)

    Roll out software releases reliably

    With release management, you can reliably integrate new software releases into your productive environment:

    • Planning of releases and all task packages for the rollout
    • Deployment of releases by means of change processes
    • Complete documentation of all release versions as well as related changes

    More information

    Expert information

    Specialist articles and white papers on the subject of IT Service Management

    Download now

    Market study

    The top 20 software vendors for IT and enterprise service management

    Download now

    Product information

    Functions and benefits of the Valuemation modules for change management & CMDB

    Download now

    Any questions?

    We’ll be pleased to provide you with more information or put you in touch with a product expert.

    I want to learn more

    Your contact

    Michael Münch
    Executive Product Manager

    +49 7141 4867-610

    Would you like to test?

    Try out the service management software Valuemation for yourself – free of charge and without obligation.

    I’d like to test it

    Vendor Selection Matrix Technology Cost and Resource Optimization: The Top 10 Global Vendors 2020

    Use this market study from Research in Action to identify relevant vendors and their solutions.

    Get your complimentary copy!