Design, Architecture, and Lessons Learned from Building a CMDB for Car Home

What is a CMDB? A Configuration Management Database (CMDB) is a platform that centrally manages IT data, device status, and assets for an enterprise, linking configuration information with service support and delivery processes to provide a data foundation for ITIL workflows.

Design Purpose The CMDB was created to address three main problems: the rapid growth of diverse equipment increasing audit costs, data silos caused by various automation tools, and disordered, duplicated manual operations that hinder efficiency.

Design Direction, Core Idea, and Functions The system aims for high accuracy, high availability, and high automation. Core thinking centers on process control to manage changes through repeatable, automated workflows, ensuring data integrity and impact assessment.

Key Functional Modules

Integration: Consolidate multiple data sources into a unified view and reports.

Self‑reconciliation: Eliminate duplicate or inconsistent records across sources.

Sync cascade: Propagate updates to downstream subsystems.

Permission hierarchy: Granular CRUD rights based on roles and conditions.

Visualization: Provide intuitive dashboards to understand data changes.

Platform Showcase

1. Asset Management Platform

Images illustrate the asset data pages, showing 35 fields used for queries, statistics, and audit records.

2. Process Control Platform

The workflow covers data initialization, state‑machine‑driven changes, reporting, and audit via ticket queries, ensuring accurate data throughout the device lifecycle.

3. Other Functional Platforms

IP Pool Management consolidates IP resources, defines three usage states, and includes a validation program for the entire network.

Data center view visualizes asset lists with rack availability, position queries, and highlighted machines based on search criteria.

Summary and Lessons Learned

After two years of development, the team shares common pitfalls (lack of dedicated project owner, overly ambitious scope, misaligned goals between operations and development, missing core process focus, insufficient feedback loops, and compromises) and best‑practice recommendations (leadership commitment, thorough data verification, treating CMDB as a process‑driven system, standardization, and high‑availability focus).

Key Takeaways

Secure leadership support for time, personnel, and resources.

Validate and clean historical data comprehensively.

Design a holistic configuration‑management process before building the CMDB.

Standardize and platform‑ize all related workflows.

Ensure the system is findable and usable to sustain long‑term value.