Skip to main content

Getting Started

What is a CMDB​

A CMDB (Configuration Management Database) is a system for storing and accessing asset information within an organization.
The concept originates from the IT domain and is a fundamental component of the ITIL (Information Technology Infrastructure Library) best practices.
In this manual, the concept is extended and applied to any context where it is necessary to know, manage, and control assets (Configuration Items or CIs).

The CMDB serves as the official central repository, providing a consistent view of all items that must be managed. It is a dynamic system that represents the current state and knowledge of the asset inventory and the relationships among its elements.

What’s CMDBuild​

CMDBuild is a robust, customizable, and extensible CMDB solution.
Its extensibility is based on an open and dynamic environment that system administrators can design, configure, and extend over time in terms of:

  • object types
  • attributes
  • relationships (domains)
  • workflows
  • reports
  • dashboards
  • interoperability with external systems

Because no two organizations manage their assets in the same way, flexibility is the key feature of CMDBuild. The system is built to be fully customizable (see CMDBuild features: main mechanisms, CMDBuild features: native features and CMDBuild features: user interfaces) so that the application can be adapted to specific needs. Technical configurability is achieved through extensive use of metadata.

The CMDBuild core interprets metadata to generate the web interface for operators, enabling them to update the CMDB, run workflows, execute reports, view dashboards, and more.

Despite its name, CMDBuild is not only a modeling environment for CMDB applications, nor is it limited to managing a database of Configuration Items.

CMDBuild mechanisms allow you to manage the entire lifecycle of Configuration Items by using workflows, business rules, documents, reports, georeferencing, and integrations with other systems.
With CMDBuild, you can design complete Asset Management applications across different operational contexts.

A configurable system offers several advantages:

  • adaptation to organizational structures and work procedures
  • possibility to introduce the system gradually, reducing organizational impact
  • quick response to organizational or technological changes
  • increased user autonomy
  • a single product codebase used across different vertical solutions

Use Guidelines​

Using the Management Module assumes that the system administrator has defined an initial data model through the Administration Module.
It is not necessary for the initial model to include every property managed within the organization. It is recommended to adopt a strategy of progressive development, extending classes and relationships over time.

We suggest starting with a small but complete set of objects and relations, then expanding the system as requirements and organizational knowledge evolve.

Operators are expected to use the Management Module according to the rules defined in the Administration Module.
We recommend using CMDBuild by:

  • respecting procedures and permissions
  • properly recording data on cards, since incomplete data reduces usefulness
  • entering new information as soon as it becomes available and keeping existing data up to date