Canonical CIs
Maintain a shared configuration identity across operations, hardware and software records.
Canonical CIsMaintain a shared configuration identity across operations, hardware and software records.
CSDM ServicesRelate business, technology and application-service CIs to a governed service model.
Offering HierarchyBind offerings to their parent services and portfolio taxonomy.
Dependency TraversalFollow saved service and infrastructure relationships, with visible health coverage.
IdentityRelationships
Connect configuration, service portfolios, service offerings, dependencies and IT/OT classification to operational work.
What Connects Here
Explore in detailCSDM Services
Relate business, technology and application-service CIs to a governed service model.
Offering Hierarchy
Bind offerings to their parent services and portfolio taxonomy.
Dependency Traversal
Follow saved service and infrastructure relationships, with visible health coverage.
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.
Canonical CIs
Maintain a shared configuration identity across operations, hardware and software records.
CSDM services
Relate business, technology and application-service CIs to a governed service model.
Offering hierarchy
Bind offerings to their parent services and portfolio taxonomy.
Dependency traversal
Follow saved service and infrastructure relationships, with visible health coverage.
Data certification
Review normalization and certification of the data used in operational work.
IT/OT classification
Distinguish IT, OT, shared infrastructure and unclassified equipment by functional role.
Actual product view
Inside CMDB & Service Model.
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
Features depend on enabled modules, configured roles, source data and supported integrations. Agree your implementation scope and acceptance criteria during discovery.
Who this is for
Enterprise data architects, configuration stewards, service model owners and integration designers
Cross-module context depends on more than drawing a relationship diagram. The platform needs canonical identities, typed service references and governed taxonomy so hardware, software and operational workflows can describe the same enterprise consistently. An evaluation of CMDB & Service Model should make those boundaries inspectable before the team relies on the operating view.
Illustrative walkthrough
Design a service model that operating teams can reuse
A fictional architecture team defines a business service, technology service and related offering. It wants to inspect the saved dependency direction, certify the supporting data and understand how the shared model serves service, asset and facility work.
01Define canonical identities
Review the configuration classes and the shared identity used across hardware, software and operational records before introducing new relationships into the enterprise model. Maintain a shared configuration identity across operations, hardware and software records.
02Connect service and offering hierarchy
Relate the service types, governed portfolio taxonomy and validated offering references, then follow saved dependencies that make the intended operating context explicit. Bind offerings to their parent services and portfolio taxonomy.
03Qualify model completeness
Inspect normalization, certification and IT or OT classification, identifying missing relationship or health coverage rather than interpreting the diagram as a complete discovered estate. Review normalization and certification of the data used in operational work.
Ask the architecture team to trace an offering to its parent service and supporting CIs, showing both validated references and a known data-quality gap that requires stewardship. 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 classes and identity rules
- Portfolio and offering taxonomy
- Relationship and certification records
Candidate measures to agree
- Service references passing validation
- Operational records reusing canonical CIs
- Known model quality gaps assigned to owners
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.
Does a graph view replace data stewardship?
No. A connected model still depends on recorded relationships, canonical identities, normalization and certification work that responsible data owners must review and maintain.
Can service offerings have a governed parent?
Yes. The available model binds offerings to their parent services and portfolio taxonomy through validated references, giving operational work a consistent service hierarchy.
How should an incomplete relationship be presented?
Identify the missing or unverified relationship explicitly and establish its source and owner; a visible map should not be treated as proof of complete topology or monitoring coverage.
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.