Hardware, software, licences and cloud subscriptions in one register – linked to contracts, costs and services.
Phase 1
Before anything is bought: standards, requirements, budget and the right licensing model.
Phase 2
The contract sets out what you’re allowed to do. I review licence terms, usage rights, warranties and the supplier’s SLA.
Phase 3
Every asset gets a record, an owner and a location, and is linked to a service, a contract and a cost centre.
Phase 4
Changes, moves and regular inventories keep the register accurate, while licence usage and upcoming renewals stay on the radar.
Phase 5
A clean exit: data wiping, disposal, returning licences to the pool and closing the record.
Physical and virtual devices tracked from purchase to certified disposal.
Licence compliance and audit readiness, on-premise and in the cloud.
Visibility of subscriptions bought outside the usual procurement route.
Several data sources combined into one, with automated cleansing and matching.
A configuration database you can trust as the single source of truth about what your services are made of.
The rules, roles and responsibilities that keep the register accurate long after go-live.
Anything with financial, contractual or licence value. You track its price, supplier, contract, warranty, depreciation and assigned user. It falls under IT Asset Management.
Anything needed to deliver an IT service. You track its technical state, version, dependencies and the impact if it fails. It falls under Service Configuration Management and lives in the CMDB.
A physical server is itself both an asset and a configuration item. As an asset, it is tracked financially and contractually: purchase, warranty, depreciation, disposal. As a configuration item, it is tracked technically: its configuration and its relationships to the operating system, database and services running on it.
I set up your register in the platform you already use, or help you choose the right one. For example:
One version of the truth about what you own – for IT, procurement and finance, and for the day the auditors arrive.
SACM (Service Asset and Configuration Management) is an ITIL v3 term that combined asset and configuration management into one process. ITIL 4 splits them into two separate but closely linked practices: IT Asset Management focuses on the financial, contractual and licence side of assets across their lifecycle, Service Configuration Management on technical items, their relationships and their links to services. ITIL (Version 5), released in 2026, keeps the same split.
The foundation is the ISO/IEC 19770 family. Part 1 defines requirements for an IT asset management system, part 2 software identification tags (SWID), part 3 the entitlement schema and part 4 resource utilisation measurement.
ISO/IEC 27001 requires an inventory of information and other associated assets (control A.5.9) and configuration management (control A.8.9). ISO/IEC 20000-1 sets requirements for both asset management and configuration management within the service management system. Without reliable records, compliance is very hard to demonstrate.
The NIS2 Directive lists asset management among the mandatory cybersecurity risk-management measures, and the DORA Regulation requires financial entities to identify and record their ICT assets and their dependencies. Accurate asset and configuration records are therefore a precondition for compliance, not just good practice.
