CMDB
Halo's CMDB is not just a register. It structures your IT estate in a five-layer hierarchy, maps every dependency, and feeds that context directly into incidents, changes, and automations — automatically.
CI STRUCTURE
Halo organises your IT estate in a structured hierarchy — from the business outcomes at the top to the infrastructure that supports them. Every layer is configurable, every relationship is tracked.
Creating a CI in the CMDB automatically creates a linked service catalogue item. Your SDM build directly populates the self-service portal — no duplication of effort, no second system to maintain.
Define your environments once (Production, UAT, Dev, Sandbox) and Halo auto-creates the corresponding instances under each application. No manual setup per app — the structure propagates automatically.
IMPACT ANALYSIS
Halo's dependency engine reads your CMDB and calculates impact automatically. Tag a CI on an incident and the impacted services, applications, and owners populate — no manual lookup required.
Every CI's upstream and downstream relationships displayed as an interactive diagram. Drill into any node. Peer-to-peer relationships between applications are modelled too — not just parent/child.
Tag a CI on an incident and Halo reads the dependency map to populate impacted services, business applications, and upstream relationships automatically. Change the CI and the impact fields recalculate instantly.
Every CI has a business owner and a technical owner. When an incident impacts a service, Halo notifies the right people automatically — pulled directly from the CMDB, not manually looked up.
Raising a change against a CI? The dependency map shows every downstream relationship — applications, instances, and infrastructure — so the CAB sees the full blast radius before approving.
DISCOVERY
Halo integrates with the discovery and monitoring tools you already use — so your CMDB reflects your real estate, not the spreadsheet from six months ago.
Automated hardware and software discovery. Device42 populates CI records, dependency maps, and change history in Halo — shown in the audit trail with "Device42" as the source.
Network-based asset discovery for Windows, Linux, and Mac devices. Lansweeper keeps hardware specs, OS versions, and software inventories current without manual data entry.
For organisations managing endpoints with Intune, Halo's native integration pulls device records directly — keeping the CMDB current as devices are enrolled, updated, or retired.
AUDIT TRAIL
Every field change on every CI is recorded — who changed it, when, and what it changed from. Whether the update came from a discovery tool or a manual edit, it shows in the change history. If a server spec changes and there's no linked change request, you'll know about it immediately.
WHAT'S INCLUDED
No CMDB add-on. No discovery module bolt-on. Every feature below is included in every Halo ITSM licence.
Set a target uptime for any technical service or application. Halo calculates downtime automatically from linked incidents — using configurable rules to determine what counts.
Track which CIs consume which software licences. Halo reports on licence usage across your estate — available, consumed, and overallocated — so you stay compliant and in control.
Attach recurring tickets to any CI — certificate renewals, backup checks, hardware reviews. Halo auto-creates and assigns them on schedule so nothing slips through without a chaser.
Link any CI to its supplier or maintenance vendor. When an incident is raised against that CI, Halo already knows the vendor — enabling escalation without manual lookup.
Mark critical CIs so any incident raised against them automatically escalates priority. The CMDB drives the SLA — not the agent's judgement in the moment.
Track every CI through its full lifecycle — Active, Maintenance, Decommissioning, Decommissioned. Status transitions are configurable and can trigger notifications or block certain ticket types.
FAQ
Allied ESM runs structured CMDB design workshops as part of every Halo implementation — defining the right hierarchy, configuring discovery, and ensuring your CMDB drives real automation from day one.