Skip to main content

CMDB Management Overview

Use the CMDB module to track every hardware, software, and service component in your IT environment, understand how they connect, and see what breaks when something changes.

The Configuration Management Database (CMDB) stores and manages data about all configuration items (CIs) in your IT environment, including hardware, software, systems, networks, and services, and the relationships between them.

Key Functions​

  • Asset Inventory: Maintains a comprehensive inventory of all CIs, such as servers, applications, databases, and networking devices.
  • Relationship Mapping: Tracks and visualises relationships between CIs, showing dependencies, upstream/downstream connections, and potential impact areas.
  • Change Impact Analysis: Supports change management by assessing the impact of changes before implementation, enabling informed decisions and reducing risk.
  • Incident and Problem Management: Enables your team to quickly pinpoint affected assets and identify root causes by analysing the connections between CIs.
  • Compliance and Auditing: Maintains accurate records of IT configurations and changes for regulatory compliance, security audits, and performance assessments.
  • Lifecycle Tracking: Monitors the entire lifecycle of assets from procurement to decommissioning, keeping IT operations and planning up to date.

Benefits​

  • Improved Visibility: Gain complete visibility into your IT infrastructure.
  • Enhanced Decision-Making: Understanding relationships between CIs helps you make better decisions during incident response, problem resolution, and change implementation.
  • Efficient Risk Management: Assess the risk of changes by understanding how components depend on one another.
  • Faster Troubleshooting: A centralised database reduces downtime by accelerating root cause identification and resolution.

Getting Started with CMDB​

Follow these steps to set up the CMDB module and create your first CI.

  1. Confirm you have a CMDB license, the CMDB Specialist Technician role, and the Manage CMDB permission (required for sync rules).

  2. Set the Discovery Preference Rule to CI.

  3. Set up a Discovery Pattern. Default patterns are available out of the box. Create custom patterns if your environment needs them.

  4. Create a CI using one of these methods:

    For a full walkthrough of all four methods, see Creating a CI.

  5. Confirm the CI appears on the CI List page.

  6. Open the CI and complete its details on the CI details page.

  7. Map the CI status to your asset statuses.

  8. Associate CIs with Assets, Requests, Problems, Changes, Releases, Knowledge, and Projects as needed.

  9. Create Workflows to automate CI management tasks.

  10. Build a CI dashboard and generate reports to monitor your CMDB health.

CMDB Best Practices​

Adhering to these best practices will help you build and maintain an accurate, reliable, and scalable CMDB that drives value across your IT operations.

Strategy & Planning​

  • Establish a clear CMDB vision by defining objectives, scope, and success criteria aligned with IT strategy.
  • Improve scalability by starting with critical services and expanding gradually as data maturity grows.

Data Quality & Accuracy​

  • Promote standardization through logical CI hierarchies and consistent naming conventions.
  • Accelerate CMDB accuracy with automated discovery and rule-based CI classification.
  • Ensure bidirectional synchronization between assets and configuration items for data consistency.
  • Improve import accuracy by validating bulk CI uploads and applying integrity checks.
  • Track lifecycle changes through well-defined CI status mapping and audit visibility.

Relationship & Impact Analysis​

  • Strengthen service understanding by mapping relationships between infrastructure and business applications.
  • Improve operational insight by discovering and validating inter-CI dependencies automatically.
  • Enhance reliability by continuously reviewing and optimizing relationship accuracy through visual graphs.
  • Enable impact analysis by linking CIs to critical business services and dependencies.
  • Reduce downtime risk by using relationship graph maps to analyze incident and change impact.

Customization & Flexibility​

  • Increase flexibility by customizing CI types, forms, and statuses based on organizational needs.