Bringing our ServiceNow licensing into SAM Pro — entitlements, contract & usage?

[klausschmid]

We're rolling out SAM Pro and want to manage our  own ServiceNow subscription (ITSM/ITAM/ITOM/CBS/SAM/.., etc.) inside SAM Pro the same way we manage Microsoft, Adobe and other publishers — i.e. visible as software entitlements linked to a contract, with usage tracked for reconciliation.

I understand based on other community entries there's no out-of-the-box connector for ServiceNow's own licensing. My questions:

1. What's the recommended way to **import the entitlements** for ServiceNow products (Import Entitlements wizard / spreadsheet / PPN)? Are ServiceNow PPNs available in the content library so software models are auto-created?
2. How do people bring the **usage / measures from the platform Subscription Management module** into SAM Pro so reconciliation has a "used" figure? Is the Resource Value table (Software Asset > Administration > Resource Value) the right approach, and has anyone automated this with a flow/script?
3. Any best practice for **custom license metrics** to model ServiceNow's subscription bundles correctly?

We're on the latest Zurich release. Thanks in advance!

[pr8172510]

Hi @klausschmid,

1. Entitlements

   • Use the Import Entitlements wizard or spreadsheet to import your ServiceNow entitlements.

   • Verify whether the required Software Models exist in the Content Library. If a matching model is not available, create the software model manually before importing entitlements.

2. Usage

   • There is no documented OOTB mechanism to synchronize usage from Subscription Management into SAM Pro.

   • If reconciliation against ServiceNow subscription usage is required, a custom integration (Flow Designer, IntegrationHub, or script) is typically needed to populate the required usage data.

3. License metrics

   • If your ServiceNow subscriptions do not match the OOTB license metrics, model them using custom license metrics that reflect your contractual licensing model.

   • Keep the implementation upgrade-safe by avoiding modifications to OOTB content.

[klausschmid]

does anyone know if there's the plan (Roadmap) to bring that OOTB? 

[fknell]

Hi @klausschmid,

You have the Subscription Management store application, which gets the job done. Why do you want to build redundant functionality?

Hope this helps!

[klausschmid]

hi @fknell 

if we'd use the supplier portals (e.g. from MSFT, SAP, ...) / integrated License overviews, then we don't need SAM Module. For a Software Asset Manager, having it within SAM PRO is necessary because otherwise its always a part missing, like contract, entitlements vs. usage, savings, etc.  and you can never report / monitor 100%. 

Additionally, we separate between "License Manager" and "Software Manager" where the License Manager has the overview on all licenses (within SAM) and the Software Manager who manages his/her software in detail, knows about it more detailed, and has maybe additional measures / Portals outside SAM.