Source Configuration
Define discovery sources, patterns and scope.
Source ConfigurationDefine discovery sources, patterns and scope.
Identification and ReconciliationBring inventory into canonical CI identities.
NormalizationUse governed classes, references and configuration context.
CertificationKeep data review connected to records.
ScopeDiscover
Connect discovery, identification, reconciliation, normalization and certification to canonical configuration records.
What Connects Here
Explore in detailIdentification and Reconciliation
Bring inventory into canonical CI identities.
Normalization
Use governed classes, references and configuration context.
Certification
Keep data review connected to records.
Scope → Discover → Reconcile
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.
Discovery sources
Maintain provider and infrastructure discovery configuration.
Patterns
Define discovery behavior for supported sources.
Executive workspace
Review inventory, capital exposure and lifecycle exceptions.
Model catalog and stockrooms
Manage hardware models and stored inventory.
Actual product view
Inside Trusted CMDB Data.
See the running demo environment. Features and records are subject to your role, configuration and integrations.
Connected capabilities
Explore the workspaces
that make it possible.
01 / infrastructure
CMDB & CSDM
Connect typed CIs, dependencies, service portfolios, services and offerings to hardware, software and customer operations.
Explore 02 / infrastructureDiscovery & Reconciliation
Configure discovery sources, patterns, ranges and schedules, then reconcile confirmed inventory into the shared CMDB.
Explore 03 / assetsHardware Asset Management
Connect procurement, custody, inventory, stockrooms, warranty, leases, maintenance, disposal and employee recovery to the same hardware CIs.
ExploreImplementation 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
CMDB managers,Discovery administrators,Service model owners
A configuration inventory becomes less useful when duplicate identities, conflicting sources and unclear relationships remain unresolved. Teams need a practical way to connect source lineage, identification, reconciliation and certification so operational decisions can distinguish trusted context from records that still require review.
Illustrative walkthrough
Illustrative workflow: reconcile conflicting configuration inputs
An illustrative service owner finds that discovery inputs describe the same equipment differently. The CMDB team examines source lineage and identification rules, reviews the canonical record and service relationships, then uses the certification process to make remaining data-quality responsibilities visible.
01Understand the contributing sources
Identify the discovery sources, patterns and relevant schedules contributing to the record. Examine resource lineage and the available identifying information before deciding whether inputs represent one item or different items. Keep source uncertainty visible instead of simply choosing the most convenient description for the inventory.
02Reconcile the canonical context
Review identification and reconciliation against the canonical configuration record. Inspect related assets, services, offerings and dependencies where those relationships are available. Resolve conflicting context with the responsible owner so subsequent service work has a clear reference rather than relying on duplicate or ambiguous records.
03Certify and revisit the information
Use data certification and accountable ownership to identify what has been reviewed and what remains incomplete. Evaluate the next discovery update against the agreed rules. Treat quality as ongoing operational work rather than a one-time declaration that every configuration record is permanently accurate.
Inspect source lineage, canonical identity, recorded relationships and certification context. These support a defensible data-quality discussion; they do not make an incomplete discovery estate complete or eliminate the need for owners to review conflicting or outdated information.
Explore the platform
See Qintorava in action.
Open a workspace for a closer look.
Prepare the evaluation
Bring the right inputs.
What to prepare
- Representative conflicting discovery records
- Identification and reconciliation requirements
- Service model owners and certification responsibilities
Candidate measures to agree
- Configuration records with traceable source lineage
- Conflicting identities resolved through agreed rules
- Relationships reviewed by accountable service 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.
Is discovery the same as a trusted CMDB?
Discovery supplies observations from configured sources. A trusted operating model also needs identification, reconciliation, relationship ownership and review. Evaluate these together with representative records so the organization understands how observations become canonical context and what uncertainty remains after the update.
Does an asset record replace a configuration item?
Asset and configuration records answer related but different questions. Custody, lifecycle and financial responsibility do not automatically establish service dependencies or canonical configuration identity. Inspect the connection between the records while preserving the ownership and purpose of each operational discipline.
Can certification guarantee that every relationship stays correct?
Certification records a review within the configured process and available evidence. Relationships can still change as the environment changes or new sources arrive. Agree ownership, discovery coverage and follow-up responsibilities so certification supports continuing quality rather than an unsupported promise of permanent accuracy.
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.