The one line difference
The three acronyms get used interchangeably in procurement documents, which causes real problems later when the delivered system does not do what somebody assumed. The cleanest way to separate them is by the question each one answers.
- FAM answers: what do we own and what is it worth. The audience is finance and audit.
- ITAM answers: what technology do we have, who holds it and what covers it. The audience is IT operations, procurement and information security.
- ITSM answers: what work is being done on it and are we meeting our commitments. The audience is the service desk and the business it supports.
What FAM is for
Fixed asset management is a financial control discipline that happens to involve physical objects. Its output is a register that ties to the general ledger and survives a statutory audit.
It covers every capitalised physical asset, not only technology: plant and machinery, buildings, vehicles, furniture, laboratory instruments. It computes depreciation, in India under Schedule II of the Companies Act 2013 with a parallel written down value working for the Income Tax Act 1961. It records custody, movement, impairment and disposal through approval workflows. It supports physical verification with evidence, so that the register can be reconciled against reality rather than assumed to match it.
The failure mode when FAM is missing is quiet and expensive: a register that carries assets which no longer exist, depreciation computed on a base that is wrong, and an insurance or audit exposure that surfaces at the worst moment. See what is fixed asset management software for a fuller treatment.
What ITAM is for
IT asset management is an operational and commercial control discipline. Its output is a defensible position on the technology estate.
It covers hardware from procurement to certified disposal, with custody recorded rather than assumed. It covers software licence entitlement measured against actual installation, which is where both under licensing and over licensing surface. And it maintains a configuration management database that records how systems depend on each other, which is what makes impact analysis possible.
A common misunderstanding is that a discovery tool is ITAM. It is not. Discovery reports what is currently reachable on the network. ITAM holds the commercial and custodial truth: what was bought, what it cost, who holds it, what licence covers it, when the warranty ends and how it was disposed of. Discovery data is an input to ITAM, not a replacement for it.
The failure mode when ITAM is missing is a licence exposure discovered during a publisher audit, renewals paid for software nobody uses, and devices that leave the organisation with the employee who held them.
What ITSM is for
IT service management is a work management discipline. Its output is measured service performance and a history that can be used to reduce future work.
It runs incidents, service requests and changes through structured workflows. It measures performance against service level agreements, with escalation before breach rather than a report afterwards. And when it is linked to assets, it accumulates the operational history that turns firefighting into elimination: which device fails repeatedly, which category of request consumes the most effort, which change preceded the outage.
The failure mode when ITSM is missing, or is running as a shared mailbox, is that priority is decided by who asked loudest, service reports are reconstructed by hand, and nobody can say whether the commitments in the contract were met.
Side by side comparison
| Dimension | FAM | ITAM | ITSM |
|---|---|---|---|
| Primary question | What do we own and what is it worth | What technology do we have and who holds it | What work is being done and are we meeting commitments |
| Scope | All capitalised physical assets | Hardware, software licences, configuration items | Incidents, requests, changes, service levels |
| Owner | Finance and internal audit | IT operations, procurement, information security | Service desk and business service owners |
| Key output | Audit ready register and depreciation working | Licence position and custody trail | SLA performance and problem trends |
| Compliance driver | Companies Act 2013, Income Tax Act 1961, statutory audit | Publisher licence audits, information security review | Contractual service levels, internal service charters |
| Typical trigger to buy | An audit observation on the asset register | An anticipated licence audit or a device recovery failure | An SLA dispute or unmanageable ticket volume |
| Field work involved | Physical verification with evidence | Device audit and reconciliation | Generally none |
Where they overlap and why it matters
The overlap is the whole point, and it is where most organisations lose money without noticing.
Take a single laptop. To FAM it is a capitalised asset with a three year useful life, a custodian and a disposal obligation. To ITAM it is a device with a warranty end date, an operating system version, an assigned user and a licence covering the software on it. To ITSM it is the configuration item attached to four tickets in the last eight months.
If those are three separate systems, three separate records exist, and they will disagree within a year. The laptop that ITSM shows failing repeatedly is the one FAM still shows as in service and ITAM still shows assigned to an employee who left. Every reconciliation between them is manual, and every manual reconciliation is eventually skipped.
On a shared platform the three disciplines read the same record. The ticket carries the device, its warranty status and its failure history. The replacement decision is made with the repair spend visible next to the written down value. The disposal updates the register and the configuration item at the same moment.
What to ask a vendor about each
Evaluations go wrong when the same generic questions are asked of all three. Each discipline has its own tell, the question whose answer separates a product that has been deployed at scale from one that demonstrates well.
For fixed asset management
Ask to see the depreciation working rather than the depreciation number, because that is what an auditor will test. Ask what happens when a physical verification finds an asset that is not in the register, since the exception path is where products differ most. Ask whether the mobile application works with no connectivity, and then test it somewhere without any.
For IT asset management
Ask how entitlement is stored and how it is compared against installation, then ask what the reconciliation report looks like when the two disagree. Ask what happens at employee exit, because a register that cannot show a device was recovered is a register that will not survive an information security review. Ask where discovery data comes from and how it is matched to purchase records, since a device that appears in two places under two identities is the most common cause of a wrong estate count.
For IT service management
Ask how a service level agreement clock behaves across working hours, weekly offs and public holidays, and whether calendars can differ by location, because in India they almost always do. Ask what triggers an escalation and who it reaches. Ask to see a ticket that carries the asset, its warranty status and its previous failures on the same screen, since that single view is the whole argument for linking service management to an asset register.
In every case, ask for a reference deployment in a comparable sector and speak to them directly. A vendor that has done this before will offer one without being pressed.
Which one to implement first
Implement the one that is currently causing pain, and let the platform absorb the others later.
- Start with FAM if you have an outstanding audit observation on the asset register, an insurance or valuation exercise coming, or a depreciation computation running in spreadsheets.
- Start with ITAM if a publisher licence audit is anticipated, if devices are not being recovered at employee exit, or if nobody can produce a current list of the estate.
- Start with ITSM if service commitments are contractual and currently unmeasured, or if ticket volume is unmanageable and reporting is assembled by hand.
The sequencing decision matters less when the three share a spine, because adding the second module is a configuration exercise rather than an integration project between two vendors. That is the reasoning behind the MeltX platform: FAM, ITAM and ITSM on one asset record, with the Governance Suite reading from the same place.