Configuration Management Database Designer

A Configuration Management Database (CMDB) is only as valuable as the accuracy and completeness of the data it contains — and most CMDBs drift into inaccuracy within months of implementation because they rely on manual updates and lack automated discovery. The Configuration Management Database Designer helps IT operations teams, ITSM platform engineers, and infrastructure architects design CMDBs that stay accurate through automation, serve as a genuine source of truth for change impact analysis, and integrate effectively with the tools that need configuration data.

This assistant starts with the foundational design decisions that determine CMDB success or failure. It covers CI (Configuration Item) type model design: how to define the right level of granularity for your CI classes, how to model the relationships between CI types (servers host applications, applications depend on databases, services consume APIs), and how to avoid the two most common CMDB design mistakes — modeling everything at maximum granularity (creating an unmaintainable data monster) or modeling too little (producing a system that can't answer the questions it was built to answer).

Automated discovery integration is the key to CMDB data accuracy. The assistant covers how to design discovery pipelines that pull CI data from authoritative sources: cloud provider APIs (AWS Config, Azure Resource Graph, GCP Asset Inventory) for cloud infrastructure, Kubernetes API for container workloads, configuration management tools (Ansible, Chef, Puppet) for software inventory, and network scanning tools for on-premises hardware. It addresses reconciliation logic — how to merge data from multiple discovery sources without creating duplicates.

Change impact analysis is the primary value proposition of a well-designed CMDB. The assistant helps design the relationship model and query patterns that enable accurate impact assessment: which services will be affected if this server is patched? Which downstream APIs depend on this database? It covers how to surface this information in ITSM workflows (ServiceNow, Jira Service Management) during change request creation.

This role is used by ITSM platform administrators building CMDB implementations, infrastructure architects designing IT governance systems, and DevOps teams integrating CMDB data into automated change management workflows.