uControl
Integration
uControl logo

Overview

uControl Core sits between your discovery and your service desk. It brings CMDB data together from any source, reconciles it into clean, unique records, models your applications and services, and keeps Halo in sync, two-way and mapped exactly how you need.

Why it matters

Most Halo teams don't lack data. They have too many sources that disagree. Duplicates, gaps and stale records undermine Halo's Blast Radius impact analysis and approval workflows, because those are only as good as the relationships behind them. uControl fixes the data and keeps it fixed.

What you get

One clean record from many sources: Core reconciles, de-duplicates, merges and normalises data from uControl Discovery, your existing tools (via direct integrations, JDBC, REST API or CSV) and Halo itself.

Discovery across IT, IoT and cloud: uControl Discovery provides new coverage or enhances what you already have. End-user devices and peripherals are captured by Insight Discovery, or by the uControl ITAM agent for remote workers.

Mapping you control: Map any CI, attribute or relationship, standard or custom. Create custom relationship types, and filter what syncs by type, category, lifecycle, owner, site or attribute. There's no fixed schema and no bespoke development.

Model and publish services: Design application and service models in Core with uMap and publish them to Halo. Model a multi-instance application once and apply it to every instance, maintained across its lifecycle.

Fully two-way: If Halo is your golden source, Core pulls its data, models on top of it and publishes back.

Change-aware ITSM: Sync the relationships Halo uses for Blast Radius and approvals, with relationship types and direction matched to your Halo configuration. Configure a change, drift event or application publish to raise a service ticket in Halo automatically.

Scheduled syncs: Scope and schedule syncs around your change windows and governance.

Who it's for

Service management, change and CMDB owners who need Halo's impact analysis, approvals and service context to run on data they can trust, and Halo administrators who want a configurable CMDB integration without custom development.

Security

Agentless, read-only discovery. AES-256-GCM encrypted credential vault. SSO via SAML, OIDC or LDAP. Role-based access control with an audit log. Deploy on-premises, in the cloud or hybrid.

Getting started

Connect Core to HaloITSM and your other sources, then configure your mappings, relationships and sync schedule. Start with a single service or site, then expand. Book a demo at ucontrol.tekwurx.com and we'll map it to your estate.

About TekWurx

Since 2013, TekWurx has helped organisations get value from their IT service and operations management tools, specialising in discovery, CMDB data quality and service modelling.

Features & Benefits

  • One clean record from many sources: reconcile, de-duplicate, merge and normalise data from uControl Discovery, your existing tools and Halo itself.
  • Connect any source: use direct integrations, or bring in data via JDBC, REST API or CSV.
  • Discovery across IT, IoT and cloud: uControl Discovery provides new coverage or enhances what you already have.
  • End-user devices and peripherals, even remote: these are captured by Insight Discovery or the uControl ITAM agent and synced to Halo.
  • Mapping you control: map any CI, attribute or relationship, standard or custom, with no fixed schema and no bespoke development.
  • Custom relationship types: create relationship types that match your service model.
  • Filtered syncs: choose what syncs by type, category, lifecycle, owner, site or attribute.
  • Scheduled syncs: scope and schedule syncs around your change windows and governance.
  • Application and service modelling: design models in Core with uMap and publish them to Halo, with no manual CMDB build.
  • Multi-instance applications: model once and apply the model to every instance in one workflow.
  • Lifecycle maintenance: models stay current as the estate changes, and updates re-publish to Halo.
  • Fully two-way: if Halo is your golden source, Core pulls its data, models on top of it and publishes back.
  • Blast Radius ready: sync the application and service relationships Halo uses for impact analysis and approvals.
  • Configurable relationship direction: match relationship types and direction to your Halo impact and approval setup.
  • Automatic tickets: configure a change, drift event or application publish to raise a service ticket in Halo.

No items found.
No items found.
No items found.