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.
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.
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.
Core reconciles, de-duplicates and normalises asset data from multiple sources, so every record in Halo is clean and unique.
uControl Discovery discovers your IT, IoT and cloud estate and feeds Core — supplying new discovery or enhancing what you already have.
End-user devices and peripherals are captured by Insight Discovery, or the uControl ITAM agent for remote workers — all synced to Halo.
Map any CI, attribute or relationship — standard or custom — and filter exactly what syncs. The mapping is yours, not a fixed template.
Model applications and services in Core with uMap and publish them to Halo — one workflow even for multi-instance apps, maintained for life.
Sync the relationships Halo uses for Blast Radius impact and approvals, and configure change, drift or publish to raise a service ticket automatically.
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.
You control what moves between Core and Halo, and how it's represented — so the CMDB reflects your model, not a vendor default.
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.
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.
Book a demo and we'll map it to your estate — your sources, your model, your rules.
Book a demo