IT asset management: the lifecycle, not the spreadsheet

IT asset management is the practice of tracking hardware and software from acquisition through deployment, maintenance and retirement. It exists to answer three questions that organisations are surprisingly bad at: what do we have, where is it, and are we paying for things nobody uses.

Most programmes concentrate on the first half of the lifecycle, because procurement generates records naturally. What is thinly managed is everything after deployment — the laptop with a departed employee, the licence renewed annually for a team that migrated two years ago, the server decommissioned physically but never removed from the inventory, the disposal that sent drives out of the building without documented destruction.

The IT asset management lifecycle stages worth instrumenting

• Acquisition: purchase order, supplier, cost, warranty term and expiry.
• Assignment: who holds it, from when, in what location — the record that makes recovery possible.
• Maintenance: warranty status, support contract, and the end-of-support date, which drives replacement planning far better than age does.
• Software entitlements: what was bought, what is installed, and the gap in either direction.
• Recovery: the offboarding step that gets equipment back, which is where most loss occurs.
• Disposal: certified data destruction, environmental compliance, and the record of both.

Unknown assets are a security problem before they are a cost problem

An accurate asset inventory is a prerequisite for almost every security control: patching, endpoint protection, access review, vulnerability scanning. A device nobody knows about receives none of them, and the gap is invisible by definition. That is why asset management appears near the top of every security control framework, and it is a better argument for funding the programme than licence savings are — though the savings are usually real too.

Reconcile the inventory against something independent at least annually — a discovery scan, the directory of active devices, the supplier’s licence position. An inventory reconciled only against itself always agrees with itself.

Software is where the money hides

Unused licences renew silently, and over-deployment surfaces only during a vendor audit. Both are addressed the same way: comparing entitlements against actual installation and usage, on a schedule, before renewal dates rather than after. Build the renewal calendar first — it is a small piece of work that immediately produces decisions, and it makes the case for the rest of the programme.

Keeping the register

Ettex Sheets holds the asset register with assignment, warranty and end-of-support dates so replacements and renewals are visible ahead of time, Ettex Records keeps the purchase documents, disposal certificates and licence entitlements per asset, and the dependency view of the same estate is the configuration record described alongside it. The finance-side view is covered in fixed asset register.

Plainly: this is a spreadsheet and records approach, not an asset management platform with discovery agents. Past a few hundred devices those tools earn their cost; what this covers is the lifecycle discipline that a tool will otherwise inherit incomplete.