Inventory / CMDB Features

The Inventory / CMDB Feature Set provides a unified, governed view of all infrastructure and configuration items across the enterprise.

It consolidates data from multiple discovery, monitoring, and inventory sources — ensuring a single, accurate, and continuously updated source of truth for assets, relationships, and lifecycle states.

Built on StableNet® discovery and extended through TOTUUS schema and governance engine, this Feature Set delivers deep visibility, flexible data modelling, and seamless integration with ITSM, security, and observability platforms.

The feature set forms the central intelligence layer of the TOTUUS platform.

It ensures that every device, service, and configuration item is accurately discovered, governed, enriched, and synchronised — providing the reliable foundation upon which Lifecycle, Observability, and Compliance features depend.

See CMDB Managed Solutions for additional details.

Intelligent discovery feature that automatically identifies devices, maps network connectivity, and collects comprehensive hardware and software details to maintain an accurate view of the infrastructure.

Uses multi-protocol (SNMP, SSH, API) and multi-vendor methods, with topology correlation and relationship mapping integrated into the CMDB model.

Enables bulk ingestion of asset or configuration data from spreadsheets or legacy systems.

Provides field mapping, validation, and conflict-handling mechanisms to ensure imported data aligns with the TOTUUS schema and classification model.

Ideal for onboarding new customers or seeding datasets prior to discovery integration.

Integrates directly with network and system management platforms such as StableNet®, Meraki, Mist, or other third-party discovery tools.

Performs API-based data retrieval to synchronise inventory, status, and configuration attributes into the CMDB.

Supports periodic or on-demand execution to maintain dataset accuracy.

Automates recurring data synchronisation between TOTUUS and connected systems.

Scheduling can be configured per integration, allowing datasets to refresh at defined intervals (e.g., daily discovery updates, weekly contract sync).

Ensures the CMDB remains current without manual intervention.

Merges and enriches data for each configuration item (CI) using inputs from multiple systems — for example, discovery data from StableNet®, inventory spreadsheets, and ITSM asset records.

Maintains source precedence rules and merges attributes intelligently to form a complete, unified record.

Supports data provenance tracking to identify the origin of each attribute.

Applies automated rules to detect and resolve data conflicts between sources.

Supports configurable precedence logic (e.g., “prefer StableNet® values for hardware attributes, prefer ITSM for ownership”).

Ensures that every CI record is internally consistent and governed under defined validation criteria.

Integrates IP address allocation, subnet management, and relationship tracking within the CMDB.

Provides visibility of IP usage across devices, domains, and tenants.

Supports import or synchronisation from existing IPAM tools where available.

See IP Address Managment for more details.

Interfaces with third-party compliance or configuration assessment tools to capture security posture and compliance state for each device.
Stores assessment outcomes as attributes or status flags within the CMDB.
Enables reporting on configuration drift, non-compliance, and remediation progress.

Manages the transition of devices from discovery to active network management.

Supports pre-commissioning validation, ensuring discovered devices meet readiness criteria before being integrated into NMS or ITSM workflows.

Links commissioning events to lifecycle states and ownership attributes in the CMDB.

Allows administrators to design tailored CMDB views per classification.

Layouts are JSON-defined, enabling dynamic presentation of attributes, relationships, and related data.

Supports simplified or advanced views to suit operational, engineering, or governance needs.

Enables the creation of user-defined attributes for any configuration item class.

Supports flexible data types (string, numeric, Boolean, list) and validation rules.

Allows domain- or customer-specific metadata to be captured without changing the core schema.

Provides the ability to define new relationship types between configuration items — beyond standard dependencies.

Supports hierarchical, peer, and functional associations.

Enables richer modelling of service dependencies, site relationships, or customer constructs.

Automates the export of CMDB data to external systems such as ServiceNow, Freshservice, or other ITSM platforms.

Supports scheduled and event-driven synchronisation, ensuring external systems receive the latest validated configuration data.

Enables closed-loop workflows where discovery, CMDB, and service management operate in sync.