Avoid CMDB Pitfalls and Achieve Cost‑Effective Configuration Management

Configuration Management Misconceptions

Undoubtedly, configuration management (CMDB) is a core component for improving the orderliness of operation systems, tracking the full lifecycle of many elements.

However, many CMDB projects fail. Below are two typical pitfalls.

Pitfall 1: Blindly Pursuing a “Big‑and‑All” Scope

Newcomers often try to pack everything—from project management to consumable procurement—into the CMDB, leading to stalled or abandoned implementations.

Pitfall 2: Expecting Full Automation

Some advocate a completely automated CMDB covering data collection, harmonization, processing, consumption, and retirement. In practice, full automation drives costs up and yields low ROI; a small amount of manual work (under 10‑20% of effort) is acceptable.

Success Factors for Configuration Management

The author believes success hinges on four points: defining scope, clarifying development path, appropriate model design, and continuous optimization.

1. Define the Scope

Understanding the current state guides scope; too small is boring, too large becomes unmanageable. Asset management is a stable starting point that delivers quick value.

2. Clarify the Development Path

IT must support business long‑term, so top‑level design should consider future business needs and phased implementation.

3. Appropriate Model Design

Design the CMDB with granularity that meets current delivery needs and allows automation to handle at least 80% of CI maintenance.

Information collection Attribute normalization Credibility verification Information audit Change traceability

Some information inevitably requires manual handling, but if it stays below 10‑20% of total work, CMDB quality remains acceptable.

4. Continuous Optimization

Apply PDCA cycles for phased improvement; risk management is crucial, especially as cloud, containers, and micro‑services reshape the environment.

Case 1: Bank IT System Project

The project built an integrated management platform, starting with stakeholder identification and ITIL knowledge transfer. A conservative initial scope—basic infrastructure monitoring and cloud platform—was chosen, followed by user education and model design involving end users.

The effort involved roughly three people for three months and exceeded cost‑benefit expectations.

Case 2: Internet Company CMDB Project

In a fast‑moving internet firm, the CMDB scope focused on supporting automation, enabling multi‑system coordination, scheduling, and traceability. A notable design was performance normalization, converting resource attributes into formulaic values accessible via API for downstream scheduling.

Both cases illustrate that, despite different contexts, the direction remains the same: CMDB as the core of operations management.

Conclusion

Short‑term effectiveness keeps configuration management alive; long‑term cost control ensures it lives a long, healthy life.