Halo ITSM

CMDB

The Intelligence Behind
Every ITSM Decision

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

Five layers. Every relationship mapped.

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.

Business Service
e.g. IT Service Management, Finance
Layer 1
Technical Service
e.g. ERP Platform, CRM System
Layer 2
Business Application
e.g. SAP, Halo ITSM, Salesforce
Layer 3
App Instance
e.g. SAP Production, SAP UAT, SAP Dev
Layer 4
Infrastructure
e.g. Linux servers, databases, network devices
Layer 5

Auto-linked service catalogue

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.

Environment management

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

Know what's affected before you raise a P1.

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.

Visual dependency maps

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.

Auto-calculated impact

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.

Owner notifications from the CMDB

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.

Change risk from CI relationships

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.

Live dependency map
IT Service Management
Business Service
ERP Platform
Technical Service
SAP S/4 HANA
Business App
Prod
UAT
Dev
Finance App
Business App
peer dependency
Auto-populated on incident
Impacted services IT Service Management
Impacted apps SAP S/4 HANA, Finance App
Business owner James Fletcher
Technical owner SAP Support Team

DISCOVERY

A CMDB only works if the data stays accurate.

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.

Device42

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.

Lansweeper

Network-based asset discovery for Windows, Linux, and Mac devices. Lansweeper keeps hardware specs, OS versions, and software inventories current without manual data entry.

Microsoft Intune

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 change logged. Every time.

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.

Manual edits attributed to the agent who made them
Discovery-driven changes attributed to the tool (e.g. Device42)
Full before/after values retained for every field
Change history — Linux Server 04
RAM updated: 4 GB → 8 GB
Today 09:14 · via Device42
Status: Active → Maintenance
Yesterday 16:30 · James Fletcher
OS Version updated
12 May · via Lansweeper
Linked to CHG0042 — Patch Cycle
11 May · Sarah Okonkwo

WHAT'S INCLUDED

Every CMDB capability. One licence.

No CMDB add-on. No discovery module bolt-on. Every feature below is included in every Halo ITSM licence.

Service availability tracking

Set a target uptime for any technical service or application. Halo calculates downtime automatically from linked incidents — using configurable rules to determine what counts.

Software licence management

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.

Scheduled maintenance tickets

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.

Supplier & vendor links

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.

SLA overrides per CI

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.

CI status lifecycle

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

Common questions

What's the difference between a CI and an asset in Halo?
In Halo, assets and CIs use the same underlying data structure — the distinction is in how you classify and use them. Assets tend to refer to physical items you own and track (laptops, servers, network devices). CIs include those assets but extend to software, services, business applications, and logical items in your service hierarchy. Halo's CMDB supports both in a single system — the five-layer model gives you the ITIL-compliant structure, while asset tracking handles the physical and lifecycle detail.
Does Halo populate the CMDB automatically or do I have to do it manually?
Both options are supported. For initial population and ongoing accuracy, Halo integrates with discovery tools including Device42, Lansweeper, and Microsoft Intune — these push CI data and field updates automatically. For the service hierarchy (Business Services, Technical Services, Applications), most organisations build this manually during implementation and maintain it through structured change processes. Halo also supports bulk import via spreadsheet and API for any CI type.
How does the CMDB connect to change management?
When a change request is raised against a CI, Halo displays the full dependency map so the CAB can see every downstream relationship before approving. Business and technical owners from the CMDB can be automatically pulled into the approval workflow. After the change is completed, any CI updates are linked back to the change record — giving you full traceability: change request → CI updated → who approved it.
What discovery tools does Halo integrate with?
Halo has native integrations with Device42, Lansweeper, Microsoft Intune, and SCCM. For organisations that need more comprehensive discovery — including cloud infrastructure, service dependency mapping, and continuous CMDB accuracy — Allied ESM recommends pairing Halo with Virima, which is natively integrated and purpose-built for this use case.
Can I track service availability in the CMDB?
Yes. Against any Technical Service or Business Application in the CMDB, you can set a target availability percentage and configure rules for what counts as downtime (e.g. P1 incidents only). Halo calculates actual availability automatically from linked incidents — using the ticket creation and close timestamps. You can also flag individual tickets as downtime manually, giving you flexibility alongside the rule-based calculation.

Build a CMDB that actually works.

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.