CI Inventory
Maintain typed classes and canonical configuration records.
CI InventoryMaintain typed classes and canonical configuration records.
Dependency MapsTraverse recorded relationships and location ancestry.
Service PortfoliosOrganize services with governed portfolio taxonomy.
CSDM Services and OfferingsBind service and offering CIs through validated references.
IdentityRelationships
Connect typed CIs, dependencies, service portfolios, services and offerings to hardware, software and customer operations.
What Connects Here
Explore in detailDependency Maps
Traverse recorded relationships and location ancestry.
Service Portfolios
Organize services with governed portfolio taxonomy.
CSDM Services and Offerings
Bind service and offering CIs through validated references.
Identity → Relationships → Service
Explore the details below, then bring your workflow, source data and questions to a guided conversation.
Built into the platform
The capabilities behind
the experience.
CI inventory
Maintain typed classes and canonical configuration records.
Dependency maps
Traverse recorded relationships and location ancestry.
Service portfolios
Organize services with governed portfolio taxonomy.
CSDM services and offerings
Bind service and offering CIs through validated references.
Data certification
Review normalization and certification workflows.
IT and OT classification
Distinguish IT, OT, shared and unclassified equipment.
Actual product view
Inside CMDB & CSDM.
See the running demo environment. Features and records are subject to your role, configuration and integrations.
Connected by design
Context travels
with the work.
Service records, configuration items, people, locations and evidence share the same operational foundation. Move from investigation to the related asset, service or customer workflow with clear ownership.
Explore the platform architectureImplementation context
Views and actions follow configured roles, permissions, enabled modules and connected source data. Screens show a demonstration environment.
Who this is for
Configuration managers, service architects, CMDB stewards and asset data owners
A configuration inventory becomes hard to trust when hardware, software and service teams maintain competing identities. Service impact also remains ambiguous when portfolio, offering and dependency references are not governed consistently. An evaluation of CMDB & CSDM should make those boundaries inspectable before the team relies on the operating view.
Illustrative walkthrough
Connect a service offering to its supporting estate
A fictional enterprise models its employee access service and its supporting application and hardware. The data steward wants canonical CIs, a clear service offering and recorded dependencies that operational teams can inspect during an incident.
01Establish canonical configuration
Identify the correct typed classes and shared configuration records before creating another representation of the same hardware, software or service entity. Maintain typed classes and canonical configuration records.
02Build the service relationship
Bind the offering to its validated service reference and portfolio taxonomy, then inspect saved dependencies and relevant location ancestry. Organize services with governed portfolio taxonomy. Ask the demonstrator to identify the responsible role and the source evidence for this step.
03Review data quality and classification
Check normalization and certification workflows, and distinguish IT, OT, shared and unclassified equipment according to the recorded functional role. Review normalization and certification workflows. Ask the demonstrator to identify the responsible role and the source evidence for this step.
Choose one service offering and follow its parent service, canonical configuration identity and recorded infrastructure relationships; ask the steward to identify incomplete or uncertified data explicitly. Use demonstration records and preserve the applicable reporting scope.
Explore the platform
See Qintorava in action.
Open a workspace for a closer look.
Prepare the evaluation
Bring the right inputs.
What to prepare
- Canonical CI identity and class
- Service and offering references
- Dependency and certification records
Candidate measures to agree
- CIs with canonical identity
- Offerings with valid service references
- Configuration records reviewed for certification
These are evaluation criteria, not promised outcomes. Agree the baseline, scope, source coverage and acceptance method with the responsible owners before drawing conclusions.
Questions for this topic
Get the details.
How is CSDM different from a flat inventory?
The available model connects portfolios, services and offerings with validated references, allowing configuration records to carry service context rather than appearing only as isolated equipment rows.
Does the map show every possible dependency?
No. Traversal reflects relationships that have been recorded and are visible to the current role; missing relationships should be addressed through data stewardship and discovery review.
Can IT and OT share the same foundation?
The shared inventory distinguishes IT, OT, shared infrastructure and unclassified equipment by functional role while retaining typed configuration identities and governed relationships.
Your next operating chapter
See what connects
when everything connects.
Bring one workflow, one service challenge or one part of your estate. We’ll show you where Qintorava fits.