How NGOSS Can Transform Your CMDB Design for Efficient Operations

In daily operations, managing vast infrastructure and software services raises questions about management principles, granularity, unified modeling, cost reduction, and lifecycle handling. The ITIL CMDB is a core concept that underpins many operational activities.

Drawing from experience building a telecom resource management system, the author highlights that telecom environments already implement a powerful CMDB through the NGOSS framework.

What Is NGOSS?

NGOSS (Next Generation Operations System and Software) provides a comprehensive framework covering business processes, information models, technical architecture, and operational management. It consists of four sub‑systems: business view, system view, implementation view, and deployment view, each guided by standards such as eTOM (business view), SID (system view), and TAF (architecture).

Business View and eTOM

The business view divides telecom activities into domain models, further refined into detailed business frameworks and activity views, as illustrated by the eTOM model.

Mapping System View to Activity View

NGOSS maps system‑level models to activity‑level processes, showing how technical components support business functions.

Applying NGOSS to CMDB Construction

To build a CMDB, first identify operational activities (e.g., server provisioning, IP allocation, process lifecycle). These activities define the configuration items (CIs) to be managed. Two key questions arise: what is the scope of objects (physical vs. logical) and what granularity of data is needed?

Physical objects include tangible assets like servers, switches, and racks, while logical objects cover IP resources, operating systems, and relationships. Granularity should balance cost‑benefit; fine‑grained data is justified when automation tools are available, otherwise a coarser approach reduces overhead.

Modeling tools can create extensible schemas, reserving extra fields in database tables for future CI attributes.

Automation and Cost Reduction

Automatic discovery mechanisms collect configuration data (processes, hardware specs, IP info) to minimize manual effort. Exceptions are reported for human review, dramatically lowering labor costs.

Lifecycle Management

As the CMDB grows, accurate state tracking becomes essential. Each CI should have a lifecycle diagram, change‑control ownership, and logged state transitions, preferably integrated into a change‑management system.

Conclusion

By following NGOSS methodology—extracting business scenarios, defining manageable objects, modeling them, implementing automation, and applying lifecycle controls—organizations can build robust CMDBs that enhance operational efficiency and reduce management overhead.