See what you run, and everything that depends on it.

The CMDB describes the items in your information system and how they are linked, in a repository you structure yourself. Before you intervene, you know what will be affected; afterwards, you know what changed.

Request a demonstration Download the sheet

Types and fields defined without development
Dependency graph at the depth you choose
Every version available

01Before you intervene

The graph shows what an item hosts and what depends on it.

Choose the depth and the relationship types: the graph unfolds everything that relies on a service, a server or an application. Change management uses it to calculate the affected items.

02Over time

Every change leaves a version.

Who changed what, and when: the history keeps every version of an item, available at any time. Read, write and delete rights are set by group and by item type.

03Built around you

A repository that follows your organisation, not the other way round.

Server, application, licence, network device or any other type: you create types, their fields and their inheritance without development, then export the configuration to import it into another environment.

One repository for every module.

Assets, supplier contracts and devices discovered on the network are repository items, with no double entry. The Service Desk, change management and monitoring all rely on the same description.

Duplicates stay out.

Devices discovered on the network are matched by serial number, MAC address or name before they enter the repository.

I’m blown away!
A customer who has used Ecaldima since its early days, after the demonstration of the new version

Related modules

Service Desk On every ticket, the CI context panel brings together the items concerned, their dependencies, other open tickets and changes in progress, without leaving the record.
Assets Assets are items in the repository, with no double entry: they are immediately available to tickets, changes and bookings.
Contracts Supplier contracts are repository records, linked to the assets and licences they cover; their expiry dates are tracked at 30, 60 and 90 days.
Network inventory Discovered devices go into the repository with no separate database, matched by serial number, MAC address or name to avoid duplicates.
Event management: monitoring alerts Each alert is linked to the item concerned as soon as it arrives, and the item’s record shows its alerts from the last seven days.

Functional scope Every detail of the module

Customisable typesServer, application, licence, network device or any other type, with text, number, date, choice list, file or reference fields.
InheritanceA type can inherit from another to share fields without re-entering them.
RelationshipsExplicit links between items (“hosts”, “depends on”) and a dependency graph.
HistoryAll modifications are traced, with access to previous versions.
Rights by typeRead, write and delete rights set by group and by item type.
Enriched usersYour organisation’s users can be viewed as items in the repository and completed with fields of their own.
Export and importConfiguration and items exported to a file, validated, then imported into another environment.
AttachmentsUseful documents can be attached to each item.

Integrations

Directory of your organisation’s users
Network discovery and inventory, with write-back to the repository
File storage for attachments

Prerequisites

The item types to track, to be defined with you
The groups that read and edit each type

The essentials of this page in PDF, to keep or pass on.

Download the sheet

Want to see this module on your own processes?

We will build the demonstration around your operational reality.

Request a demonstration