ServiceNow Software Asset Management Professional for Energy and Utilities

Software asset management in an energy or utility business means keeping one record of which licensed software runs on which systems, how many entitlements the company holds, and when each renewal falls due. This page helps a software asset manager decide which systems to reconcile first and how to handle licences on operational technology.

Software Licensing in Energy and Utilities

Energy and utilities companies operate infrastructure that must remain available 24/7. System uptime is not a convenience; it is a requirement for delivering power, gas, or water. Software licensing complexity can threaten uptime. A software licence expiration or compliance violation can trigger vendor lockout, loss of support, or audit findings. Software Asset Management Professional helps track which software is deployed where, which licences are active, and when renewals are due.

Utilities also face cost pressures. Unused software licences represent waste. A SAM Professional implementation creates visibility into what software is running, how many licences are in use, and where there is opportunity to consolidate or reduce spending.

Inventory Scope for Utilities Operations

Energy and utilities organisations run diverse systems: control systems (SCADA, industrial control systems), enterprise resource planning for operations, customer information systems, financial systems, and supporting infrastructure (email, collaboration, security). SAM Professional must track all of these accurately.

Focus on systems critical to operations first. If your SCADA environment runs on Windows servers, ensuring you have valid software licences is non-negotiable—loss of support means loss of vendor assistance during an outage. Similarly, your customer information system and billing systems are mission-critical; licensing compliance here is a business continuity priority.

License Compliance and Audit Readiness

Software vendors audit compliance—they verify that your organisation has paid for the number of licences in use. Non-compliance findings can result in audit fees, demands to purchase additional licences retroactively, or legal action. Utilities, operating in a regulated environment, face additional risk: regulators may view software licence non-compliance as a governance failure.

SAM Professional provides evidence of compliance. For each significant software product, you can quickly generate a report showing: how many users or systems are using the software, how many licences you own, and compliance status (compliant or non-compliant). This report is essential when a vendor audit occurs. Store the report in SAM Professional along with supporting evidence—purchase orders, licence keys, deployment inventory—so you can produce evidence quickly.

Handling Industrial Control Systems and Operational Technology

Industrial control systems (SCADA, programmable logic controllers, distributed control systems) often run specialised software with unique licensing models. Some vendors charge per-site, others per-year of operation, and some per-device. SAM Professional should accommodate these variations. Track the licence type, the consumption metric (seats, devices, or sites), the current usage, and renewal dates.

Operational technology (OT) often follows different update and patch cycles than enterprise IT. A SCADA system may run on software that is no longer receiving security patches, but patching is risky because it could interrupt operations. SAM Professional should help you track which systems are running end-of-support software and escalate the risk to operations leadership so informed decisions can be made about maintenance windows or system upgrades.

Vendor Management and License Optimization

SAM Professional integrates with vendor records. When you negotiate a software agreement with a vendor, record the terms in SAM Professional: the license type, the quantity, the per-unit cost, the renewal date, and the support coverage. This data helps you plan budgets and identify opportunities to optimise spending.

Over time, SAM Professional analytics reveal patterns. You might discover that you have multiple applications providing similar functions—text editors, collaboration tools, or data analysis platforms—where consolidation could reduce spending. You might find licenses that were purchased but never deployed, which could be returned or reallocated. Annual SAM Professional reviews with finance and operations leadership can inform decisions about software investments and retirements.

Change Management and License Impact

When systems are upgraded, decommissioned, or moved to new infrastructure, licence requirements may change. Integrate SAM Professional with change management: before approving a major system change, verify whether licence requirements will be affected. For example, migrating from on-premises software to a cloud service may eliminate perpetual licence costs but introduce per-user or per-consumption costs. Capture this analysis in the change record so decision-makers understand the financial impact.

Reconciling installed software against entitlements, step by step

A software audit is a reconciliation exercise. The vendor asks how many copies are running, and you answer by matching what is installed against what you are entitled to hold. The answer is only as good as the weakest evidence in the chain, so the reconciliation should state which evidence supports each figure.

1. Standardize product names before counting, so a title recorded three ways is not double counted.
2. Match each installation to a license entitlement, noting the metric the vendor uses: named user, device, site or processor.
3. Record the shortfall or surplus per product, and attach the evidence used for each figure.
4. Resolve shortfalls by checking whether an entitlement exists under a parent agreement before buying anything new.
5. Keep the reconciliation as a dated record, so the position at audit time can be shown without rebuilding it.

Name normalization and the duplicate-product problem

In many utility estates, errors come from naming more often than from arithmetic. A control room application may appear as a product name, a vendor suite, an internal code name and a version string, and each variant looks like a separate product to a tool that does not know better. Build a product dictionary that maps each variant to one canonical product, and review it whenever a new source is added. Do not merge two products that the vendor licenses separately, even if they share a vendor and a name stem.

Handling license models that cannot be counted from a scan

Some operational technology licenses are measured per site, per controller or by metered throughput, and none of those is visible to a desktop scan. For these, use a named attestation with a clear owner, a stated method and a date. Record the counting method beside the figure, and repeat the attestation when the site or controller count changes. The discovery approach for energy and utilities describes how network scanning is combined with manual input for field assets.

Renewal and true-up timing

Renewals are where cost and risk meet. A renewal that arrives without a reconciliation forces a choice between paying for unknown quantities and taking a support gap. Start the reconciliation early enough that the figures are settled before the renewal conversation begins.

• Build a renewal calendar that lists the notice date, not only the end date, because some terms need notice before the renewal window opens.
• Reconcile each product in the calendar at least once before its notice date, and note any product with incomplete evidence.
• Separate support-only renewals from license renewals, since they carry different risk if lapsed.
• Flag products that run on software no longer receiving vendor support, so the renewal decision includes the operational risk.

Deciding whether to buy, redeploy or retire

The change record is the easiest place to prevent a surprise. A migration that trades a perpetual license for a per-consumption charge can look cheaper in the project plan and more expensive in the first full year, unless the metric is written into the approval.

Questions about audits and ownership

What should we do when a vendor refuses to provide a usage report?

Ask for the report in writing and record the request date. If the vendor still refuses, use the contract to check the audit and usage-reporting clauses, and keep your own reconciliation as the working position. Do not present an estimate as a vendor-verified figure.

Is a scan result enough evidence in an audit?

It is good evidence of presence on the scan date and weak evidence of use. Combine it with an entitlement record and a usage source where the vendor counts use, and explain the gap in writing for any product where a scan is the only source.

Who should own the entitlement record?

The software asset manager should own the record, with each application owner confirming their products each cycle. Splitting ownership this way helps avoid a record that nobody checks until the audit letter arrives.

Next step for your license position

The software license optimization guidance covers how entitlement and usage records feed spend decisions, and the software asset lifecycle controls guide explains the controls behind them.