ServiceNow IT Asset Management: Guides and Services

What IT Asset Management Covers on the Now Platform

ServiceNow IT Asset Management brings together hardware, software, and virtual assets under one platform. It spans discovery, tracking, compliance, and optimization workflows. Asset Management sits at the core of IT operations because every infrastructure decision flows from knowing what you actually own, where it is, its condition, and what it costs to run.

The module connects deeply with CMDB data, connects to discovery tools to populate hardware inventories automatically, integrates with procurement to track purchases through their lifecycle, and feeds reporting to show utilization and risk. When done well, it provides the single source of truth for what exists in your infrastructure.

How the Modules in This Group Relate

Asset Management forms the data foundation for decisions across several related areas. Hardware Asset Management focuses specifically on physical IT equipment—servers, workstations, networking gear. Software Asset Management tracks software licenses, their compliance status, and cost allocation. Financial Management uses asset data to depreciate capital items and track operational spending. Service Mapping and CMDB depend on accurate asset records to build a credible model of your services and their dependencies.

The relationship flows in both directions. Discovery feeds asset records into the system. CMDB enriches those records with relationships and context. Financial teams consume asset data to reconcile spend. Compliance workflows check asset age, support status, and license validity.

A Map of the Module Sections

This section contains guides organized by what you need to do. Start with the “what is” guides if you are new to a capability. Move to best practices if you are configuring a module for the first time. For migrations from legacy tools, use the migration considerations guides. If you need to plan a project or understand design decisions, workshop questions and RACI guides walk you through the thinking. Troubleshooting guides help when something is not behaving as expected.

Each guide assumes you know ServiceNow basics and that you have the right module installed. Most guides apply to the current release; where release-specific constraints exist, they are noted. If a guide talks about a feature you do not see in your instance, check your licensing or contact Oblytech for configuration help.

Where to Start

If you are evaluating Asset Management, begin with the “what is” guides to understand scope and positioning. They explain the problem the module solves and how it fits with your other platforms. If you already have Asset Management and are improving it, read the best practices guides for your specific area—hardware, software, or virtual assets. These guides give you a reason for each practice and show what good looks like.

If you are migrating from a legacy asset tracking system, the migration considerations guide walks you through inventory, data mapping, cutover, and validation. Read the RACI and roles guides if ownership or escalation paths are unclear in your organization. Finally, if you encounter something behaving unexpectedly, the troubleshooting guide will help you narrow down the cause.

Integration Across Your IT Landscape

Asset Management is not isolated. It is one piece of a larger ITSM ecosystem. Your asset data flows upstream to financial systems for cost allocation and depreciation calculations. It flows downstream into Service Mapping to show infrastructure dependencies. It connects to Inventory Management to determine what to order. It feeds compliance workflows that check whether devices meet security standards and support policies.

Effective asset management requires thinking about the end-to-end flow. When a new laptop is purchased, that event should automatically create an asset record, assign it a location, and prepare it for a user. When that laptop is eventually retired, the system should capture the retirement date and cost for depreciation purposes. The asset record is not just an inventory item; it is a piece of data that serves multiple business processes.

Sequencing the Asset Modules Against Your Data Readiness

Asset programs often go wrong in the order they are started rather than in the tools they choose. A license review cannot be trusted while the hardware inventory is half-complete, and a cloud cost report cannot be allocated while nobody owns the resource tags. The practical question for a sponsor is therefore not “which module do we buy” but “which question can we answer correctly with the data we have today”. Start there, and let the answer decide which sub-area to open first.

A Starting Sequence That Holds Up Under Review

Work through the sequence in order. Each step needs an owner and a review date before the following step begins. The steps look administrative, but skipping them is what produces an inventory nobody trusts a year later.

1. Name one owner for the asset record and one owner for each asset state. Write the states down, with the rule that moves an asset from one state to another.
2. Decide which discovery sources feed the inventory, and which of them are allowed to overwrite a manually entered value.
3. Load a single asset category from start to finish, including purchase data, assignment and disposal, and reconcile it against finance records for the same period.
4. Only after that category reconciles, add the second category and repeat the check.
5. Connect the license or cloud module to the reconciled inventory, and start with the reports that the sponsor asked for.

What Usually Goes Wrong in the First Year

Duplicate assets come first. A laptop that is discovered by the endpoint tool, entered by procurement and assigned by the service desk becomes three records unless one of them is declared the source of truth for each attribute. Decide that per attribute, not per system. The second failure is a retired asset that still counts. Disposal often happens in a different team from the one that owns the record, so the retirement step needs a trigger that does not depend on memory. The asset lifecycle management guidance is a useful reference for those disposal triggers.

The third failure is the one that surprises sponsors most: a report that is technically correct and still wrong for the decision it supports. A license position built from installed software will look non-compliant if the entitlements were entered from a different unit of measure, such as per user rather than per device. Put the unit of measure beside every number in the report, and have the business owner sign off the first version before it goes to leadership.

How to Tell the Program Is Maturing

Early progress is measured by reconciliation, not by volume. Track the share of assets that match between the inventory and the finance register for each category, the number of assets with no owner, and the number of records in a state that the rules no longer allow. A program that is maturing shows those gaps shrinking month after month, even while the number of records grows. If the gaps stay flat while the record count climbs, new data is arriving faster than it can be governed.

When a Full ITAM Program Is the Wrong Scope

Not every organization needs all four sub-areas. A small estate with a limited number of devices, one cloud account and a single finance owner may do better with a disciplined register and a yearly review. Adding modules in that setting creates cost, configuration and training effort without answering a question anyone is asking. Likewise, do not start a license optimization effort while the business has no agreed list of contracts, since the work can stall at the first unmatched invoice. The CMDB is the natural home for the configuration relationships that asset records depend on, and it should be scoped at the same time rather than afterwards.

Decisions to Settle Before Funding a Module

Before any module is funded, the sponsor should be able to answer five questions in a single page: which asset categories are in scope, who owns each state, which source wins for each attribute, which report is the first one required, and what the program does when a record cannot be reconciled. Teams that cannot answer these questions on one page often discover, six months later, that they bought a capability they cannot yet use. For the control points these answers feed into, see the software asset lifecycle controls guidance.

Next Step

Choose the first question you need answered, then test that choice before sign-off. The right first sub-area depends on the data you hold today, and that is easier to judge in a short working session than in a long document.

How to Track IT Asset Cost in ServiceNow From Purchase to Disposal

Tracking IT asset cost in ServiceNow means attaching a purchase cost, a cost centre, a depreciation rule and a named owner to every asset record, then reporting from those fields. Cost totals are only as reliable as the purchase record each asset starts from.

Work through the cost chain in this order. First, agree the cost basis for each asset category, for example purchase price for hardware and contract value for subscriptions. Second, load purchase cost from procurement or the finance register using the same asset identifier the asset record uses, so the two sides can be matched rather than guessed. Third, set the cost centre at assignment and update it on every transfer. A cost that stays with the old department is the most common reason a budget review gets challenged.

Depreciation is the step teams misread most often. In most implementations the finance team sets the method and the useful life, and the asset team supplies only the acquisition date. If both teams set those values, two versions of the same asset’s value start to circulate.

Disposal closes the cost. A retired device that keeps its cost keeps inflating the estate, so the disposal step should record the disposal date and any residual value on the record that started the cost. The usual failure is a retirement captured in a service desk ticket.

Recurring charges such as subscriptions and cloud consumption need their own rules because they arrive as invoices rather than a single purchase. Cloud spend is covered in the cloud cost visibility guide, and licence spend in the software license optimization guide.

A cost figure is trustworthy when someone can pick one asset and trace its number back to the invoice, the cost centre and the depreciation rule without asking a specific person. Where a figure cannot be traced, fix the rule that produced it before correcting the figure, or the same gap returns at the next load. Stages between purchase and disposal sit in the IT asset lifecycle management guides.