<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=7178634&amp;fmt=gif">
uControl Book a demo
Integration · uControl Core

Halo + uControl Core

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

  • Reconcile asset data from many sources into clean, unique records
  • Model applications & services in Core and publish them to Halo — two-way
  • Fully customisable mapping, with change or drift able to raise a service ticket in Halo
What you get

Your CMDB, mapped your way.

Core doesn't impose a fixed schema. Bring data together from any source, map every CI, attribute and relationship how you need, and keep Halo in step — so it reflects your organisation, with no bespoke development.

One record from many sources

Core reconciles, de-duplicates and normalises asset data from multiple sources, so every record in Halo is clean and unique.

Discover IT, IoT & cloud

uControl Discovery discovers your IT, IoT and cloud estate and feeds Core — supplying new discovery or enhancing what you already have.

EUC & peripherals, even remote

End-user devices and peripherals are captured by Insight Discovery, or the uControl ITAM agent for remote workers — all synced to Halo.

Mapping you control

Map any CI, attribute or relationship — standard or custom — and filter exactly what syncs. The mapping is yours, not a fixed template.

Model & publish services

Model applications and services in Core with uMap and publish them to Halo — one workflow even for multi-instance apps, maintained for life.

Change-aware ITSM

Sync the relationships Halo uses for Blast Radius impact and approvals, and configure change, drift or publish to raise a service ticket automatically.

Ingest & reconcile

Many sources in. One clean record out.

Core brings asset data together from across your tools and reconciles it — de-duplicating, merging and normalising records so what reaches Halo is clean, unique and trustworthy.

  • Reconcile, de-duplicate and merge records from many sources into one clean record
  • Normalise fields so every asset in Halo is consistent and unique
  • Feed Core with uControl Discovery across IT, IoT and cloud — new discovery or enhancing existing data
  • Capture EUC and peripherals via Insight Discovery, or the uControl ITAM agent for remote workers
  • Connect other systems through direct integrations, or via JDBC, REST API or CSV
Map

Configure every part of the sync.

You control what moves between Core and Halo, and how it's represented — so the CMDB reflects your model, not a vendor default.

  • Select and filter CIs by type, category, lifecycle, owner, site or attribute
  • Map standard and custom attributes field-by-field
  • Create custom relationship types to match your service model
  • Scope and schedule syncs to fit change windows and governance
Model

Model once, publish to Halo — and back.

Model your applications and services in Core with uMap and publish them into Halo. If Halo is already your source of truth, Core can pull that data, model on top of it, and publish back — no extra sources needed. One workflow handles even multi-instance applications, maintained across their whole lifecycle.

  • Design application & service models in Core (uMap) — no manual CMDB build in Halo
  • Pull from Halo, model, and publish back when Halo is your golden source — fully two-way
  • One process publishes multi-instance applications — model once, apply to every instance
  • Maintain models through their lifecycle; changes re-publish to keep Halo current
Operate

Relationships and tickets that keep pace with change.

Halo uses CMDB relationships for its Blast Radius impact analysis and approval workflows. Core syncs those relationships — and because Halo's impact and approval setup is configurable, Core makes relationship types and direction fully customisable to match. When something changes, Core can open the right ticket automatically.

  • Sync the application & service relationships Halo uses for Blast Radius impact
  • Customise relationship types and direction to match Halo's impact and approval configuration
  • Configure a change, drift event or application publish to raise a service ticket in Halo
  • Keep models, relationships and tickets current as the estate evolves

Connect Halo to uControl Core.

Book a demo and we'll map it to your estate — your sources, your model, your rules.

Book a demo