IT & Network Asset Management
Last updated 13 Oct 2026
At a glance
IT Asset Management (ITAM) governs what the operator owns, leases or licenses: cost, contract, support, compliance and retirement. It is the third pillar beside ITSM and ITOM. In a telco the largest asset base is the network and CPE, and one box is an asset, a CI and a resource at once.
The picture
Choose a stage to see what it does to each record.
The asset register exists before the equipment is in service and after it is gone; the CI and the resource exist only while it is deployed. That difference is why the three drift.
How it works
What ITAM governs
- Hardware: IT servers and storage, and in a telco also network elements, spares and CPE, with cost, location, warranty, support contract and end-of-support date.
- Software: entitlements against usage for BSS/OSS platforms, databases and network function licences, so compliance can be proven in a vendor audit.
- Cloud and SaaS: spend against commitments, and subscriptions nobody uses.
- Lifecycle: request, procure, receive, deploy, maintain, retire, dispose.
ITAM is an ITIL 4 practice, with ISO/IEC 19770 as its standard family. It is not a TM Forum term and not an Assurance process: eTOM places asset governance in Enterprise Management (Financial & Asset Management) and the lifecycle of network resources in Resource Management.
Asset, CI and resource
One router is described three times. As an asset in the asset register: what it cost, its contract and warranty, its lifecycle state. As a configuration item in the CMDB: what depends on it, for change and incident impact. As a resource in resource inventory: its ports, capacity and addresses, and the services assigned to them.
The records have different lifespans. The asset is created at order or receipt and closed after disposal; the CI and the resource exist only while the equipment is deployed. A shared identifier, usually the serial number or an asset tag, links them, and reconciliation compares them. Without it they drift.
Where ITAM pays
- Licences: platforms licensed per subscriber, core or instance grow with the network; an audit that finds over-deployment ends in a true-up charge.
- Support contracts: decommissioned equipment whose asset was never closed keeps being supported; equipment past end-of-support still carrying services has no vendor escalation path.
- Retirement and refresh: ITAM knows the end-of-life dates, resource inventory knows the services on the kit. Retiring a platform is a service migration first.
- CPE recovery: operator-owned CPE in a customer’s home must be recovered on cease, which needs a link from the asset to the product instance.
Most ITAM failures surface elsewhere: an incident with no support path appears in ITSM, unlicensed usage is found by ITOM discovery, a write-off appears in ERP.
Who owns what
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Asset: cost, contract, warranty, lifecycle state | Asset register (ITAM tool or ERP) | — | CMDB, procurement | The book value lives in ERP fixed assets. |
| Fixed asset and depreciation | ERP | — | Asset register | Section 7.5 covers it |
| Configuration item and dependencies | CMDB | ITSM change forms | Asset register, resource inventory | — |
| Network resource, assignment and topology | Resource inventory | — | CMDB, asset register | TMF639 |
| Software entitlement | Asset register (software asset management) | — | Procurement, vendor contract | Compared against usage found by ITOM discovery |
| CPE held by a customer | Asset register or warehouse system | — | Product inventory, resource inventory | Recovery on cease depends on this link |
In practice
ITSM platform vendors sell ITAM on the same data model as the CMDB (ServiceNow and Ivanti, with Flexera common for software), so the asset-to-CI link is straightforward for the IT estate. Network equipment is more often split across network planning and resource inventory for what is deployed, a warehouse system for spares and CPE, and ERP for the financial record. Few operators have one asset register covering both.
ITAM is usually the least mature of the three pillars, because the cost of neglect arrives late and in someone else’s budget. A transformation that migrates services off a legacy platform without an asset record for it often cannot prove the platform is safe to switch off, and keeps paying its support.
The trade-off
What it solves
A governed asset register, linked to the CMDB and resource inventory, gives the operator control of cost, licence compliance, support coverage and retirement.
What it does not solve
- It does not tell operations what depends on a device; that is the CMDB and resource inventory.
- It does not replace ERP as the financial book of record.
- It does not back-fill records for equipment deployed before anyone tracked it; that needs discovery and a physical audit.
What it adds
- A third record of the same equipment, with its own owner and update path, that must be reconciled with the other two.
- Procurement, warehouse, field engineering and change management all have to update it at the right lifecycle step.
Architecture decision
Bring network equipment into the IT asset register, or keep it in network planning and ERP and reconcile?
One asset register for IT and network
Choose when The network estate is modest, the ITSM platform already holds the CMDB, and support and licence costs are a visible problem
Keep separate records and reconcile
Choose when A large network with established planning and inventory tools, where moving the record would disrupt engineering processes
Breaks if There is no shared identifier (serial or asset tag) across asset register, CMDB and resource inventory: the records then cannot be reconciled, whichever system holds them.
Takeaways
Key Takeaways
- ITAM governs cost, contract, compliance and lifecycle; it is the third pillar of service assurance beside ITSM and ITOM.
- It is an ITIL 4 practice, not a TM Forum term; eTOM places it in Enterprise Management.
- One piece of equipment is an asset, a CI and a resource; a shared identifier and reconciliation keep them aligned.
- In a telco the largest asset base is the network and CPE, often tracked outside the IT ITAM tool.
- ITAM failures usually surface somewhere else: in ITSM, in a vendor audit, or in ERP.
Check yourself
A router was removed from the network two years ago, but its support contract is still being renewed. Which record failed to change?Show answerHide
The asset register. The CI and the resource were removed with the equipment, but the asset was never moved to retired or disposed, so the support line stayed on the renewal.
Why can the CMDB not simply act as the asset register?Show answerHide
They answer different questions and live for different periods. The CMDB records dependencies for change and incident impact while the item is deployed; the asset register records cost, contract and lifecycle from order to disposal, including equipment that is in stock or already removed.