A CMDB tells you what your services run on and what breaks when something changes. SMC Consulting's ITIL v4 certified consultants build the CMDB in HaloITSM: a data model sized to your services, configuration items fed automatically by Lansweeper or Intune, and the relationships your incident and change teams use every day.
A configuration management database (CMDB) is the record of the configuration items (CIs) that deliver your IT services, and of how they depend on each other. In ITIL 4 it supports the service configuration management practice: knowing which servers, applications, network devices and cloud resources a service needs, so incidents are diagnosed faster and changes are assessed against real dependencies.
A CI is not the same as an asset. An asset is something you own and pay for, tracked for cost, contracts and lifecycle; a CI is anything you need to manage to deliver a service, tracked for its relationships. A laptop is usually an asset first; a database server behind your ERP is a CI first. Many records are both, which is why the CMDB and IT asset management in HaloITSM share the same data.
The CMDB is one of the ITIL practices described in our practical guide to ITSM. HaloITSM is the tool we recommend most often for it: see why HaloITSM is our pick.
Source: the ITIL 4 Service Configuration Management practice, ITIL 4 by PeopleCert.
CI relationships connect servers, applications, services and users, and the map shows what sits behind each service.
Incidents and changes draw on the same relationships, so the affected services are visible on the ticket, not in a separate tool.
HaloITSM is priced per agent with every module included: the CMDB and asset management are never behind an upsell.
Change, problem and incident management sit on the same CMDB, which is why HaloITSM is the tool we recommend most often for ITIL depth.
A live demo with two or three of your services mapped, or a free HaloITSM trial: 30 days, 15 of them guided by SMC Consulting.
Start with a minimum data model and grow it: a CMDB that tries to hold everything on day one goes stale. NIS2 makes this minimum model a compliance topic too; our post on the minimum CMDB data model for NIS2 lists the fields that matter.
The services your users see, and the technical services behind them, each with an owner and a criticality.
Business applications and their components, linked to the services they deliver and the teams that support them.
Physical and virtual servers, databases and middleware, with the applications that run on them.
Switches, firewalls, load balancers and links that a service depends on, so a network change shows its real impact.
Subscriptions, virtual machines and managed services in Azure, AWS or Google Cloud, kept apart from on-premise CIs.
Runs on, depends on, connects to, used by: a short list of relationship types everyone reads the same way.
HaloITSM has no discovery agent of its own; it integrates with Lansweeper's Data API, and webhooks push asset changes to Halo as soon as devices change.
Managed laptops, phones and tablets imported from Intune, with their users, so end-user devices stay current without manual entry.
For cloud and container estates, discovery tools map resources and dependencies; we connect them so cloud CIs follow the same rules as the rest.
The same five steps in Belgium, Luxembourg and France. Our step-by-step guide shows the method in detail: build a CMDB in 30 days.
Not sure where your CMDB stands today? Book my free ITSM audit: 30 minutes with a senior consultant. Still choosing a tool? Our comparison of the 10 best ITSM tools sets HaloITSM against the alternatives.
Which services the CMDB must cover first, and which decisions it must support: incident diagnosis, change impact, audits.
CI classes, mandatory attributes and relationship types, kept to what the first scope needs.
Lansweeper, Intune, cloud discovery and your existing lists connected, with one authoritative source per CI class.
Duplicates merged, stale records flagged, and the services mapped to their CIs with the people who run them.
CI owners named, quality rules automated and reviewed every month, and the CMDB linked to incident and change workflows.
Who need the impact of a change before the CAB, not after the incident.
Who must show which assets support which services, and who owns them.
Whose CMDB was left half-built at go-live and is no longer trusted.
A configuration management database records the configuration items that deliver your IT services (applications, servers, network devices, cloud resources) and the relationships between them. In ITIL 4 it supports service configuration management, so incidents and changes are handled with the real dependencies in view.
Discovery tools and imports create and update the CIs; reconciliation rules decide which source wins for each attribute; relationships link CIs to the services they support. Agents then see the affected services on an incident, and change managers see the impact of a change before approving it.
The asset register tracks what you own: cost, contracts, warranty, lifecycle. The CMDB tracks what your services depend on and how. In HaloITSM both use the same records, so a device can be an asset and a CI at once. See IT asset management in HaloITSM.
Yes. HaloITSM integrates with Lansweeper's Data API, and Lansweeper webhooks push device changes to HaloITSM as they happen. We set the mapping and the reconciliation rules; see the HaloITSM and Lansweeper integration and Lansweeper asset discovery.
It depends on the number of services, sources and the quality of your current data. Our guide describes a first, limited scope in 30 days (build a CMDB in 30 days); the CMDB then grows service by service. The schedule is fixed with you once the first scope is agreed.
Yes. HaloITSM has one price per agent with every module included, CMDB and asset management among them; see HaloITSM pricing. Our advice is independent. If you choose HaloITSM, we can also supply the licences as its certified partner, and we tell you so up front.
Book a live demo on your own services. You can also start a free trial: 30 days, 15 of them guided by SMC Consulting.
Learn how the ServiceNow MCP server connects AI agents to governed ITSM workflows, Action Fabric and secure enterprise automation, plus readiness steps for 2026.
Read more →
Learn how a HaloITSM Lansweeper integration connects discovery data to HaloITSM, enabling cleaner CMDB records, faster triage, and better change decisions.
Read more →
A practical ServiceNow migration cutover plan helps reduce risk, protect service continuity, validate integrations and support confident ITSM modernisation.
Read more →
