ServiceNow Software Asset Management Professional: Guides and Services

What Software Asset Management Professional Covers

Software Asset Management Professional (SAM Pro) on the Now Platform provides comprehensive software license tracking and optimization. SAM Pro differs from basic asset management by focusing specifically on software: tracking license count and type, monitoring usage, detecting unlicensed software, ensuring compliance with vendor audits, and optimizing spending through license consolidation and retirement. Large organizations often have thousands of software products, millions of license costs, and complex licensing models that vary by vendor. SAM Pro brings order and control to that complexity.

Core Capabilities and Features

Software Asset Management Professional tracks software installations across your environment through agents, inventory scans, or integration with device management systems. It records license entitlements: what you purchased, how many licenses, the terms (perpetual, subscription, named-user, concurrent), and cost. It compares actual usage against entitlements to show where you have excess licenses, where you are under-licensed, and where software is unlicensed. It forecasts renewal dates and costs so you can plan budget. It generates reports for internal tracking and for responding to vendor license audits. Integration with procurement ensures that purchased licenses are recorded and matched to installed software. Integration with financial systems allows cost allocation, chargebacks, and ROI calculation.

License Compliance and Audit Management

Software vendors conduct audits to verify that customers are properly licensed. An audit begins with a demand for an inventory: what versions of the software are installed, how many instances, how many users. Audits are expensive to respond to and risky if compliance is uncertain. SAM Pro maintains an accurate software inventory so audit response is straightforward and defensible. It can generate the reports vendors demand quickly. If audit reveals under-licensing, you understand the gap and can negotiate remediation without surprise or denial. Risk of major compliance violations and fines decreases dramatically.

Cost Optimization and Spend Analysis

Many organizations spend far more on software than necessary. Common problems include: licenses purchased but never used, multiple products doing the same thing, unused seats being renewed, older versions running when cheaper newer versions exist, and expensive named-user licenses when cheaper concurrent-user licenses would work. SAM Pro surfaces these issues. Analysis might show that retiring an unused product saves millions, that consolidating multiple tools into one platform reduces cost, or that renegotiating licensing with a vendor based on demonstrated usage saves cost. Cost optimization work often pays back the cost of a SAM initiative in the first year alone.

Vendor License Management and Optimization

Software license models are complex and often unfavorable to customers if you do not pay attention. Common models include: perpetual licenses (buy once, unlimited use, updates are optional), subscription licenses (annual or monthly fees), named-user licenses (based on how many people can access), concurrent-user licenses (based on how many use simultaneously), and metered/consumption-based licenses (pay for actual usage). Switching from an expensive model to a cheaper one for the same software can be a major cost reduction. SAM Pro can calculate the cost of different licensing models and model the economics of switching. Some negotiations with vendors are possible: if your usage is lower than your license level, you might downgrade; if usage is higher, you might negotiate better bulk rates.

Integration with Procurement and Financial Systems

SAM Pro works best when integrated with your procurement and financial systems. When a purchase order for software is approved, the license details should flow into SAM Pro automatically. Renewal costs should be flagged ahead of renewal dates so budget is planned. Retirements should be coordinated with expense accounting so old licenses are not forgotten. Integration ensures SAM data is current and reliable.

How Oblytech Supports Software Asset Management Professional

Oblytech helps organizations implement and optimize SAM Pro on the Now Platform. We begin with discovery: understanding your current software inventory, known licensing, and problem areas. We configure SAM Pro to track software across your environment through agents or integration with existing inventory systems. We help you respond to vendor audits and remediate compliance gaps. We work with you to identify cost optimization opportunities and model the financial impact of changes. We establish processes so SAM Pro remains current as software is deployed and retired. Many organizations engage us for ongoing managed support to maintain and evolve SAM Pro as their software environment changes.

Decide which of the three software views you need first

Software asset work draws on three different pictures of the same estate, and they rarely agree at the start. The first is what the organization has bought: the entitlement, its term and its cost. The second is what is installed: the product and version found on each device or in each cloud tenant. The third is what people actually run: usage over a period. A program that tries to reconcile all three at once often stalls. A better sequence is to establish the purchased picture first, because it is the basis of every compliance and renewal decision, then add installations, and only then usage, which is the most expensive to collect accurately.

Where each view should come from

Each view has a natural source, and a platform does not change that. Purchase data normally lives with procurement or finance. Installation data comes from discovery or an agent. Usage needs telemetry, and the quality of that telemetry depends on what the software reports. The table below sets out the questions that matter at the planning stage and the element of the platform that holds the answer once it is loaded.

A procedure for the first purchased-view reconciliation

1. Choose the products with the largest annual spend, and gather their agreements, order forms and renewal notices into one folder.
2. Record the license model for each product exactly as the agreement states it, rather than as the team remembers it.
3. Enter the purchased quantity and the term for each product, with the date the agreement was signed.
4. Match each product to a software product model in the platform, and note any product that has no match so it can be created or mapped by hand.
5. Compare the purchased quantity with the installed count from discovery, and label each gap as an explained difference or an open question.
6. Have the procurement owner check the figures against their own records before any of them is used for a renewal decision.

Choose the software scope by risk, not by alphabet

It is tempting to start with the full catalog in alphabetical order. A risk-based scope often produces faster value. Put first the products with the highest spend, the products whose vendors audit most often, and the products where a single missed renewal would interrupt a business service. Products that are cheap, widely licensed under a flat agreement and rarely audited can wait. This ordering also tests the process on the hardest cases early, which is useful because the difficult license models are where the reconciliation rules are most likely to need adjusting.

Frequently asked questions on software scope

Should free or open-source software be in scope?

Include it where a vendor agreement, a support contract or a usage restriction applies, and where the software is part of a paid bundle. Free software with no restrictions can be recorded for completeness, but it should not dilute the effort on products where money or compliance is at stake.

How do we handle software that runs in a virtual desktop environment?

Ask the vendor how its agreement counts virtualized use before loading any installation records, because the counting rule is often different from a physical device. Record the rule in the product’s entitlement notes so that the next reviewer does not have to rediscover it.

Who should approve a change to the purchased view?

The procurement or finance owner who holds the agreement should approve it, and the software owner should confirm the usage picture. Changes made only by the technical team tend to drift from the signed contract over time.

Do we need the usage view before the first renewal?

Not always. A renewal can be negotiated from the purchased view and a sample of installations. Usage data is valuable, but waiting for it to be complete can push a renewal past its notice date, and that cost is easy to avoid.

Next step

Pulling the agreements for the top few products is often enough to fix the sequence. Ongoing support for licensing work is described in the software licensing and optimization service, and the software license optimization hub covers the wider optimization picture.