IT asset management software that closes the gap between records and reality

MeltX ITAM is the IT asset management module built by MeltX Software Solutions in Pune, India.

  • Hardware lifecycle from procurement to secure disposal
  • Software licence entitlement measured against real installations
app.meltxsoftware.com/itam/licences

Licence position

1 over-deployed
Discovered
1,284
Unmanaged
37
Renewals 30d
4
  • Microsoft 365 E3388/420
  • AutoCAD LT71/60
  • Adobe Creative Cloud22/45
  • A CMDB that maps dependencies, not just a device list
  • Automated reconciliation across physical, financial and configuration records

THE PROBLEM

IT knows what it bought. It rarely knows what it still has

Procurement holds the purchase orders. The service desk holds the tickets. Finance holds the capitalised value. A discovery tool holds a device list. None of them reconciles to the others. When a licence audit arrives, or a laptop leaves with an employee, the cost of that disagreement becomes visible.

  • Licence exposure discovered during an audit

    Entitlement is tracked in a purchase folder while installations grow independently, so the shortfall appears only when a publisher asks.

  • Shelfware nobody cancels

    Renewals continue for software that has not been launched in months, because no one holds usage next to entitlement.

  • Ghost devices on the network

    Assets that were replaced, returned or written off still appear in monitoring tools, and assets in use appear nowhere.

  • No dependency map when something breaks

    An outage becomes an investigation because nobody can say which services ran on the failed host.

CAPABILITIES

What IT Asset Management actually does

Four capability pillars, each grounded in the mechanism behind it rather than in adjectives.

01

Hardware asset management

Every device tracked from procurement to certified disposal, with custody proven.

  • Record laptops, desktops, servers, network gear, printers and peripherals with make, model, serial number and warranty.
  • Assign devices to employees, departments and locations, with issue and return acknowledged rather than assumed.
  • Track warranty and annual maintenance contract cover, and alert before it lapses on a business critical device.
  • Close the loop at end of life with a documented disposal trail, including certified e-waste handling through MeltX services.
unmanagedunmanaged
02

Software asset management

Licence entitlement measured against actual installation, so both over licensing and under licensing surface early.

  • Hold entitlement records with the purchase document, licence metric and renewal date against each publisher and product.
  • Compare entitlement with installed instances to expose under licensing before an audit does, and over licensing before a renewal does.
  • Track subscription renewals and true up dates on a calendar the finance team can see, not in a mailbox.
  • Keep the evidence pack an audit requires: proof of purchase, deployment counts and reconciliation working.
Microsoft 365 E3within entitlementAutoCAD LTover-deployedCreative Cloudwithin entitlementTally Primewithin entitlement
03

Configuration management database

A CMDB that records relationships between assets, services and users, and feeds service management directly.

  • Model configuration items and the relationships between them, including which services depend on which hosts.
  • Use the dependency map for impact analysis before a change and for root cause work after an incident.
  • Share one record with MeltX ITSM, so a ticket, an asset and a configuration item are the same object rather than three copies.
  • Maintain history on every configuration item, so a change can be reviewed against what the item looked like before it.
AcquireDeployMaintainVerifyRetire
04

Automated reconciliation

Physical, financial and configuration records brought into agreement continuously rather than annually.

  • Reconcile the IT register against the fixed asset register so capitalised value and device reality agree.
  • Match scanned and verified devices against the recorded estate and raise every difference as an exception.
  • Flag devices that have not been seen, acknowledged or verified within a defined window.
  • Give finance and IT the same reconciliation report instead of two extracts that never match.

IN DETAIL

The parts that decide whether it works in practice

Enterprise software succeeds or fails on the details nobody demonstrates. These are the ones that matter after go live.

One estate, two lenses

Finance sees capitalised value, depreciation and disposal. IT sees allocation, warranty and configuration. Both read the same underlying record, so the numbers never diverge.

Employee issue and return

Devices are issued against an acknowledgement and recovered at exit, with the trail retained.

Renewal and true up calendar

Subscription and maintenance dates surfaced in advance, with the commercial owner named.

Stock and spares pool

Unallocated devices are held as stock rather than disappearing between an exit and the next joiner.

Certified disposal trail

End of life devices leave through a documented e-waste route, with the certificate retained against the asset.

Role based access control

Procurement, IT operations, finance and audit each see the fields their role requires and nothing more.

Bulk onboarding

Load an existing estate through a validated template with duplicate detection before commit.

Exception dashboards

Unverified devices, expiring cover and licence gaps presented as work, not as a report to read.

Licence compliance and audit defence

A software publisher audit is won or lost on evidence. MeltX ITAM keeps entitlement, deployment and reconciliation in one place, so the answer to an audit letter is a report rather than a fire drill.

Security and compliance position
  • Entitlement evidence

    Purchase documents, licence metrics and renewal terms are held against each product, so proof of purchase is never reconstructed from email.

  • Deployment position

    Installed instances are compared against entitlement, giving a defensible position before a publisher asks for one.

  • Asset custody trail

    Issue, transfer and return records show who held a device and when, which matters for both audit and information security.

  • Secure disposal record

    End of life hardware carries a documented disposal trail, supporting both financial write off and data protection obligations.

LIFECYCLE

One record, six stages, no re-keying

Each stage writes to the same record. Nothing is retyped into a second system, which is where most asset data goes wrong.

  1. 1

    Procure

    Purchase orders, invoices and warranty terms are captured as the device enters the estate.

  2. 2

    Onboard

    The device is tagged, added to the register and linked to its configuration item.

  3. 3

    Allocate

    It is issued to an employee, department or location against an acknowledged handover.

  4. 4

    Operate

    Tickets, changes, patches and licence usage accumulate against the same record.

  5. 5

    Reconcile

    Verified devices, financial records and configuration data are matched, and differences are raised.

  6. 6

    Dispose

    The device leaves through approval and certified e-waste handling, with the certificate retained.

Built for the people who answer for the numbers

One register, read four different ways. Each of these roles asks it a different question, and gets the answer without asking anyone for an extract.

  1. Chief information officers and IT heads

    One defensible view of the estate: what exists, who holds it, what it costs and what it is exposed to.

  2. IT asset and procurement managers

    Renewals, warranties and stock managed on a calendar instead of on memory.

  3. Finance and internal audit

    IT hardware value reconciled to the fixed asset register, with the working available on demand.

  4. Information security teams

    Custody records and disposal evidence that support access reviews and data protection obligations.

WHERE IT'S DEPLOYED

Built for estates that span offices, plants and field sites

MeltX ITAM is deployed where devices move between locations and custody changes often, including manufacturing, education and public sector environments across the MeltX and partner clientele.

  • CEAT

    Manufacturing

    MeltX FAM was configured to the entity, plant and cost centre hierarchy already used by finance. Assets were tagged with barcode and QR labels under the existing numbering policy, and field teams verified them on the MeltX Android application with geo tagged photographs.

    Verification evidence
    Geo tagged, per asset
    How the deployment ran
  • Borivali Education Society

    Education

    MeltX FAM and ITAM were configured to the institution department structure, with tagging across laboratories, classrooms and administrative offices, and custody recorded against named department heads.

    Custody
    Department wise
    Grant traceability
    Retained per asset
    How the deployment ran

SECTORS

Where ITAM is running

The sectors whose deployments include IT Asset Management. Each page sets out what the register has to answer for in that sector.

What buyers ask about ITAM

The questions buyers actually ask during evaluation, answered without marketing language.

What is IT asset management software?

IT asset management software tracks technology assets across their working life. It records hardware from procurement to disposal, holds software licence entitlement against actual deployment, maintains configuration relationships between systems, and reconciles those records so IT, finance and audit work from one set of facts.

What is the difference between ITAM and a discovery tool?

A discovery tool 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 and when it must be renewed or disposed of. Discovery data is an input to ITAM, not a replacement.

How does MeltX ITAM help with software licence compliance?

MeltX ITAM stores entitlement records with their purchase evidence and licence metric, then compares them against installed instances. Under licensing surfaces before a publisher audit, and over licensing surfaces before a renewal, so the commercial decision is made with the numbers in front of you.

Does MeltX ITAM include a CMDB?

Yes. MeltX ITAM maintains a configuration management database that records configuration items and the relationships between them. Because MeltX ITSM reads the same records, impact analysis before a change and root cause analysis after an incident use live data rather than a stale diagram.

See it against your own register

Configured around your asset classes before the call. Thirty minutes.

  • No obligation
  • Run on your register
  • Answered within a business day