License metric type for non-discoverable software that doesn't need reconciliation just renewals

[Nancy Schilli]

I want to track the software entitlements for software that is not discoverable, e.g. pumps at a hospital. I don't need reconciliation, since the software can ONLY be installed on those devices. would be nice to know which version of software, but again not discoverable, and would need to be maintained manually.

what is the best approach in creating the software entitlement? Should I create a new license metric that has NO reconciliation & no discovery ? So it's easy to find all the products that are like this? 

I saw an earlier post where it was suggested to manually create the installations, so that reconciliation works (see link below). prefer not do to that, since again, there is no compliance issue. 

https://www.servicenow.com/community/itam-forum/custom-license-metrics-script/m-p/1307526

[Community Alums · Accepted solution]

Hi Nancy,

You can create a software model and entitlement like you normally would, however on the software model you can uncheck (no checkmark; it is checked by default when you create a software model) the "License Under Management" option. This will prevent this model (and associated entitlements) from appearing in your compliance reports, but still gives you the ability to track the information that you listed 🙂

All the best,

Stephanie

[Community Alums · Accepted solution]

Hi Nancy,

You can create a software model and entitlement like you normally would, however on the software model you can uncheck (no checkmark; it is checked by default when you create a software model) the "License Under Management" option. This will prevent this model (and associated entitlements) from appearing in your compliance reports, but still gives you the ability to track the information that you listed 🙂

All the best,

Stephanie

[dreinhardt · Accepted solution]

Hi @Nancy Schilli 

if the products are not known in the content library, they should be created as "Custom Products" and linked to the software model. After that, the entitlement can be assigned to the model in the usual way. (Add a custom software product (servicenow.com))

According to the assumption that all devices of the company are available in the CMDB as CI, also pumps - as these may have corresponding services for incidencts etc., I would add these devices to the "Device Allocation" tab at the software entitlement. This offers the possibility of tracking the life cycle of the software despite manual recording. If, for example, the maintenance for the software expires, it is displayed as underlicensed at the next reconcile.

Best, Dennis

[BradP-InnoSolv]

I know you said you don't want to reconcile, but adding this post in case you do. 

You can create a "custom license metric" and usee that metric when adding the entitlements.  Then add a record into the 'Resource Values' table for each SW model you want to track the quantity consumed.  I would suggest updating this data on a regular basis (monthly, quarterly) so you can see the trend over time against what you own to predict when to buy more or when to reduce your maintenance if all not used.

Example:

Prerequisite: Assumes product exists (or a custom product is created) and SW model is created (with "License under management" checked).

1. Create a new license metric called "Per Pump" in the samp_sw_license_metric_custom table

• Choose table source: "Resource Value"
• Add a short description (optional)
• Add the following in the script field: 

 getRightsForResourceValue();
 function getRightsForResourceValue(){
	var rightsForResourceValue = -1;
	var resourceValueRecord = new GlideRecord('samp_sw_resource_value');
	if(resourceValueRecord.get(entity)){rightsForResourceValue = resourceValueRecord.getValue('units_consumed');
	}
	return rightsForResourceValue;
}

2. Add a record into the samp_sw_resource_value table with the SW Model name and quantity of Pumps in use (this will reflect the consumption side of the reconciliation calculation)

3. Run reconciliation for the relevant publisher and check the license report.  It should show you the rights owned (in use entitlements) and rights consumed (from the resource value record).  

I appreciate greatly if you find this helpful and click the thumbs up below. 

[Ian Roper]

Loved this post, lots of good information.  This is the response I got from ServiceNow support, when I asked why my "Allocations available" numbers were not reflecting the consumption calculated from the "Resource value"... 

"For the Resource Value we will not be considering the allocations. If you would like to change the value based on the Units consumed on the Resource Value we need add a logic in the license metric script. But OOTB we will not be considering the allocation when the table source is set to Resource Value."