uControl Core · Control

Automated service mapping and CMDB accuracy.

uControl Core reconciles data from across your hybrid and cloud estate into one trusted model, then keeps your CMDB accurate as your environment changes. Visibility, accuracy and control, without manual audits.

Book a demo

No-code service modelling with uMap
Continuous drift detection keeps the CMDB aligned
Blind-spot detection exposes what others miss

What uControl Core does

One trusted model of your estate.

Turn fragmented, multi-source IT data into a reconciled, continuously validated view your teams can act on.

Automated service mapping

A no-code approach (uMap) that detects relationships across hardware, software and network, turning a complex web of dependencies into intuitive service maps.

CMDB synchronisation

Controlled synchronisation keeps uControl and your CMDB aligned, syncing enriched CIs, application and service relationships plus business context back into the CMDB.

Import & reconciliation

Connect ITSM, monitoring, discovery, cloud and custom sources, then normalise and intelligently reconcile records into one unified model merging or flagging conflicts.

Drift detection & alerts

uAlert continuously validates modelled components, detects configuration drift and new relationship candidates, and alerts owners when changes impact accuracy.

Blind-spot detection

Surfaces hidden or undocumented assets, dependencies and relationships — assets in discovery but missing from the CMDB, stale records, duplicates and missing ownership.

Analytics & dashboards

Turn reconciled asset and service data into interactive dashboards that drill from executive summary to asset-level detail, with charts, KPIs and threshold signals.

Scheduled reporting

Automated, timely report delivery for consistent visibility, including direct delivery to SharePoint document libraries.

Full traceability

Track full lineage from source record to reconciled asset, with audit-ready change history and source-to-asset traceability.

Business context enrichment

Layer owner, criticality, lifecycle state, cost centre and compliance tags onto reconciled assets, so service models carry business context, not just topology.

Data quality scoring

Rank data quality by source, track alignment against gold-standard sources, and surface deviations so confidence improves over time.

No-code class mapping

Configure class mappings, attributes, relationships and lifecycle handling per CMDB instance entirely through the UI, no coding required.

Multi-vendor integrations

Built for complex, multi-vendor estates, connecting BMC Discovery, ServiceNow, BMC Helix, Lansweeper, EasyVista and Atlassian JSM Assets, plus Teams and SharePoint.

uMap: automated service modelling

Turn raw discovery into service maps you can trust.

uMap automatically inventories, detects dependencies, and assembles single- and multi-tier application and service models, then maintains and monitors them as the estate changes.

No-code: detects relationships across hardware, software and network
Single- and multi-tier models with upstream/downstream impact paths
Publishes models to upstream systems including BMC Discovery
Monitors modelled applications and tracks drift over time

Import, reconcile, sync

One pipeline from many sources to a single trusted record.

Core consolidates ITSM, monitoring, discovery, cloud and custom sources, normalises them to a common model, and reconciles records into one asset, merging or flagging conflicts with full lineage.

API, scheduled and event-driven imports
Identification rules prevent duplicates and resolve conflicts
Reconciled, enriched CIs and relationships sync back to the CMDB
Full source-to-asset traceability and change history

Drift detection & owner validation

Keep the CMDB honest without manual audits.

Core validates that modelled components are still present, flags stale or decommissioned assets, and surfaces newly discovered relationships, with owner sign-off before anything is written back.

Tag and drift rules identify candidate CIs for a service
Owners confirm changes before the CMDB is updated
Automated relationship adjustments keep uMap and the CMDB aligned
Blackout windows and controlled publishing respect change policy

Questions

Frequently asked.

What data sources can Core import from?

ITSM, monitoring, discovery, cloud and custom sources, via API, scheduled or event-driven imports, across both structured and semi-structured datasets, consolidated into one repository.

How does Core avoid duplicate CIs?

It normalises incoming data to a common model and applies identification rules, multiple prioritised rules per configuration type per source, to merge or flag conflicting records into a single trusted asset.

Which CMDBs and tools does Core integrate with?

The connector set includes BMC Discovery, ServiceNow, BMC Helix CMDB, Lansweeper, EasyVista and Atlassian JSM Assets, plus Microsoft Teams for alerts and SharePoint for report delivery.

Can I control when data is written back to the CMDB?

Yes, per connection you can set blackout windows and choose instant or manual sync, and configure class, relationship and lifecycle handling per instance, all through the UI without coding.

What is a “blind spot”?

A gap where tools disagree, assets in discovery but missing from the CMDB, records with no recent discovery evidence, duplicates, or missing ownership, lifecycle or criticality, surfaced for reconciliation.

Does building dashboards or reports need scripting?

No, dashboards follow a build-view, create-report, assemble-dashboard flow with charts, KPIs, tables and heatmaps. No scripting or complex development required.

Why we built it

The hard part of a CMDB isn't building it once, it's keeping it true as the estate changes every day. We engineered Core around continuous validation and owner sign-off, so the model stays accurate and every write-back is deliberate and auditable, never a black box.

O Oliver Wood Head of Development, TekWurx