What it is (plain English)
Tracking physical IT assets - laptops, phones, servers, monitors - through their whole life: ordered, received into a stockroom, assigned to a person, moved, and eventually retired and disposed. It answers "who has what, what did it cost, and when does it need replacing?"
Problems it solves
- No reliable answer to "who has which laptop?"
- Assets lost, hoarded, or paid for after they're gone (over-leasing, missed disposals).
- Refresh cycles missed because nobody tracks age and warranty.
- Audit and finance can't reconcile IT hardware.
What must exist first
Define hardware models, model categories, asset states, stockrooms, ownership, and lifecycle processes. CMDB Foundation should be prepared where hardware assets pair with operational CI records, but HAM can begin with asset-lifecycle scope before CMDB maturity is complete.
What the customer needs to provide
- Your current asset data, however messy (spreadsheets, old asset tool, procurement records).
- Stockroom locations and how receiving works today.
- Procurement process and who owns it.
- Lifecycle decisions: refresh policies, disposal process, lease vs. own.
- A named asset manager accountable for the data.
Where it can go next
Software Asset Management (SAM) complements HAM when software license compliance and optimization need context from shared devices, users, contracts, and procurement records; it does not depend on HAM. Asset data also feeds Incident Management and Change Management context; enterprise asset management (Enterprise Asset Management (EAM)) extends the model beyond IT. Pairing with Procurement Operations streamlines asset purchase requests end to end, and ESG Management can track the emissions and energy footprint of the hardware estate.