Every organization manages different assets: servers, software licenses and IT services, buildings and plants, vehicles, medical equipment. With CMDBuild you don't have to fit into a predefined data model: the CMDB adapts to you.
From the Administration Module you decide which items to manage, what information to record and how they relate to each other. Everything is configured, with no software development.
What you can model
Types of items
Servers, contracts, buildings, vehicles: you create whatever types of items you need. For large volumes of data, such as IoT sensor readings, there are simplified, optimized types.
In CMDBuild: classes
Hierarchies
"Computer" branches out into "PC", "Notebook" and "Server": shared information is defined just once, and each type adds its own.
In CMDBuild: superclasses and subclasses
Information
Text, numbers with units of measure, dates, IP addresses, files, value lists, references to other cards and fields calculated with formulas.
In CMDBuild: attributes
Relationships
"The server hosts the application", "the plant is located in the room": links between items, which can carry their own information, such as a contact person's role.
In CMDBuild: domains
Value lists
Statuses, categories, priorities: lists defined once and reused across all cards, optionally with icons so values can be recognized at a glance.
In CMDBuild: lookups
Views
Lists that filter the data of one type or combine several, for example "servers with warranty expiring", defined visually or with SQL queries.
In CMDBuild: filter, join and SQL views
Relationships are the heart of a CMDB: see how they work in CMDBuild.
Tailor-made forms
For each type of item you also decide how operators enter and view the data:
For more specific needs you can add widgets, context menus and form triggers: see Advanced customization.
Everything else is ready to go
As soon as you create a new type of item, CMDBuild provides with no further configuration:
Why it pays off
The benefits of configurability
Step by step
Start with the most pressing needs and expand the CMDB in later phases, reducing project risk.
Independence
New types of items are added from the Administration Module, with no costly software changes.
The right level of detail
The model is tuned to the organization's needs and to the resources available to keep it up to date.
From test to production
Changes to the model can be compared and moved between environments in a controlled way (Data Model Synchronization plugin).
Learn more in the online documentation
