---
title: Change Management integration with Software Asset Management
description: The Change Management integration with Software Asset Management \(SAM\) displays the projected licensing cost implication of a change.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/change-management/change-mgmt-integ-wth-SAM.html
release: australia
product: Change Management
classification: change-management
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Change management integrations, Reference, Change Management, IT Service Management]
---

# Change Management integration with Software Asset Management

The Change Management integration with Software Asset Management \(SAM\) displays the projected licensing cost implication of a change.

This integration tracks projected license cost changes when a change is proposed to one or more configuration item \(CI\) processor resources — CPU or CPU Core — running processor-licensed software.

This integration requires the Software Asset Management Professional \(com.snc.samp\) and Change Management - License Change Projections \(com.sn\_samp\_change\) plugins.

**Note:** You need to request the activation of the Change management – License Change Projections plugin \(com.sn\_samp\_change\) through the HI Service Portal.

When a change request is in the **New** state, users can propose a change to the CPU or CPU Cores of a CI using **Propose Change** or **Mass Update CI**. Those proposed changes are captured in an XML field that is then passed to Software Asset Management when the change request transitions into its first approval state. Once Software Asset Management performs the projected licensing cost change, those results are displayed in a new form section called License change projection.

The License change projection form section displays the license projection change summary for every CI in scope for the change. The left side of the section displays fields relaying the current spend, projected spend, the spend change, and the number of impacted installations. On the right is a bar graph providing a visual representation of that information.

For a more detailed breakdown of the license change projections, a related list can be added to the Change Request form called **CI Projection Summary**. This related list provides a CI-by-CI breakdown of the license change projection summary information and provides easy access to the Software Asset Management CI Project Summary record and additional data.

The projected cost impact covers software licensed by the processor \(CPU or CPU Core\) for the affected configuration items. Use the License change projection summary and the **CI Projection Summary** related list to estimate the spend change before the change is approved. Cost impacts for software licensed by other metrics are not included in this projection.

**Parent Topic:**[Change management integrations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/change-mgmt-integrations.md)

**Related topics**  


[Managing proposed changes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_ProposedChanges.md)

[Mass Update CI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/bulk-ci-change.md)