Solution · IT asset management
Know what you own, where it is, and what it is costing you.
Every IT team owns more than it thinks: laptops in drawers, software licences nobody uses, a server everyone forgot under a desk. Until the list is written down, every purchase is a guess and every outage starts with the question of what is actually there.
One record of every asset, its owner, and what it depends on.
Purchases and renewals decided from the list, not from memory.
Ageing hardware replaced before it fails, not after.
The problem
Why asset lists go stale
Asset management fails quietly. Nothing breaks the day the record goes stale — it breaks months later, when the record is needed and nobody trusts it.
The list lives in three places
A spreadsheet, a finance system and one person’s memory, each telling a different story. When an audit or an outage asks for the truth, the team spends a day reconciling instead of answering.
Nobody knows what depends on what
A server fails and nobody can say which services run on it or who is affected. The asset is known; the relationship between assets is not, and that is the part that matters in an outage.
Licences paid for, never used
Subscriptions renew on a card nobody checks, for software nobody opened in a year. Without a record tied to actual use, the budget leaks a little every month and nobody notices.
Replaced after it fails
Hardware is kept until it breaks because nobody tracked its age or its failure history. The replacement then happens in a hurry, at the worst time, and costs more than a planned swap would have.
The process
Five steps, and the itserva page for each
Five steps, from the first list to a record you can trust.
- 01
Record what you own
List the assets that matter and what each one is: hardware, software, services, and who owns them. Start with the services that matter most; depth beats breadth, and a short accurate list beats a long guessed one.
- 02
Link assets to services
Record what depends on what, so a failing server answers the next question immediately: which services and people are affected. A list without relationships is a stocktake, not a map.
- 03
Keep software patched
Use the asset list to drive patching: every system on the list gets patched, and anything unpatched is visible instead of forgotten. Patching is where the list earns its keep every month.
- 04
Replace before it fails
Watch how often ageing hardware fails. When the time between failures keeps shrinking, the asset is telling you its replacement date — listen before it chooses one for you.
- 05
Retire and record
When an asset leaves, record the retirement the same day: what it was, where it went, and what data it held. A record that keeps the dead assets in it is not a record at all.
What’s included
Tools, templates and guides for it asset management
Comparison
Best Patch Management Software
Patch management tools compared on coverage, automation and price.
Measure it
The four numbers worth tracking
Four numbers show whether the asset record is complete, current and useful. If the first one is low, the other three cannot be trusted.
Register coverage
The share of assets that are actually recorded, with an owner. Coverage below full means decisions are being made about assets nobody can see.
Unpatched assets
Systems on the register that missed the last patch cycle. Every unpatched asset is a known risk with a known fix, and the count should fall every month.
Failure rate by age
How often assets fail as they get older. A rising rate in one age band is the signal to budget replacements — before the failures choose their own schedule.
Cost of asset downtime
What it costs when an asset fails: lost work, recovery time, and the emergency replacement. The number makes the case for the planned swap.
Frequently asked questions
What is the difference between an asset register and a CMDB?
An asset register lists what you own and what it is worth. A CMDB goes further: it records how assets relate to each other and to the services they support. A small team often needs the register first and the CMDB second.
How often should the asset record be updated?
When something changes: a purchase, a move, a retirement. A record updated in a monthly batch is already out of date; the update belongs with the change itself, while the detail is fresh.
Do we need CMDB software to start?
No. A simple list with owners and dependencies is a better start than a tool nobody maintains. Buy software when the list outgrows the spreadsheet, not before.
Who should own the asset record?
One named person, even in a team of one. A record owned by everyone is owned by nobody, and it is the first thing that goes stale when the work gets busy.
Start the list with the assets that matter most.
Read the CMDB guide, list the assets behind your most important service, and give each one an owner. A free workspace saves your comparisons and calculations while the list grows.