Consumption Fact: Measures

FlexNet Manager Suite 2022 R1 (On-Premises)

The Consumption fact allows tracking the results of license consumption calculations over time. It supports the measures listed below. These general comments apply to all measures:

• For each measure, the figure shown is the maximum value found in all data snapshots included in your reporting period.
• All values are filtered by the access rights of the current operator (or report user). Access rights are managed through roles to which the operator is assigned, using enterprise groups of various kinds as filters. For example, if operator Sam is denied access to data from your North American location (and its children), then a report entry for license consumption in your Chicago office always shows zero when viewed by Sam, regardless of how many licenses are really consumed in Chicago.
• Since you may build a report using any combination of enterprise groups, the totals described for the following measures may be segmented across those groups, as expected. This sub-totalling and segmentation effect is omitted from the following descriptions for simplicity.

Allocated (max qty)

The number of installations (or users, depending on license type) that have specifically received allocations from the license in question. Allocations are essentially a manual linking of the installation/user with the license, to the exclusion of all other licenses, and may be made individually on the Consumption tab of the license properties. While they remain a 1:1 association, they can also be processed in bulk on the Apply Allocations and Exemptions page.

Related management view: See either the Consumption tab of the license properties, or the License Compliance > Apply Allocations and Exemptions page.

Database reference: The allocation count matches the number of entries in the SoftwareLicenseAllocation table that have both:

• A SoftwareLicenseID that links to the correct software license, and
• A value of 1, 2, or 3 for the SoftwareLicenseAllocationStatusID (this is a key to the text reasons given in the SoftwareLicenseAllocationStatus table, and these values mean that an allocation of some kind has been granted).

Data warehouse reference: AssignmentData table, AssignedCount column.

Consumed (max qty)

The consumption count for each license, as filtered by your chosen dimensions and identified in the last exported compliance calculation for each point in time. This is the final consumption calculation for each license, taking into account all beneficial aspects like items covered by other product use rights, device exemptions and the like.

Related management view: The Compliance tab of license properties displays the Consumed entitlements count. Also visible in many license listings, such as License Compliance > All Licenses.

Database reference: The total consumption for each license in the most recent compliance calculation is stored in the SoftwareLicense table, NumberInstalled column.

Data warehouse reference: ConsumptionData table, ConsumedCount column.

Covered by downgrade right (max qty)

The number of license entitlements consumed under a downgrade right (that is, the consumption occurred against a license for a later version or higher edition, but which included a downgrade right).

Related management view: This collective total is not available in management views.

Database reference: Downgrade count is the number of installations where the installed software title is a lower version or edition than the software title of the license. This involves linking from the InstalledSoftwareData table, through the SoftwareLicenseID to identify the license, and through the SoftwareTitleID to the SoftwareTitle table, where the SoftwareTitleVersionID and SoftwareTitleEditionID provide keys to the reference tables of versions and editions respectively.

Data warehouse reference: ConsumptionData table, DowngradeCount column.

Covered by rights on VMs and hosts (max qty)

The number of virtual machines that are linked to the selected license, but that are not consuming any entitlements because they are covered by special product use rights.

Related management view: For an individual license, look at the Consumption tab of license properties. Filter for Inventory device type of Virtual machine, and check the Consumed value (shows zero for any virtual device linked to this license but not consuming at the last license compliance calculation), and check for an Exemption reason such as Covered by virtual application access.

Database reference: The SoftwareLicensePointsConsumedData table stores the count of entitlements consumed (in LicensesConsumed) for each license (identified by the SoftwareLicenseID). This is the count of records for a given SoftwareLicenseID for which the LicensesConsumed value is 0 and the ComplianceComputerTypeID in the associated ComplianceComputer record is 3 (for virtual machine).

Data warehouse reference: ConsumptionData table, VMNonConsumedCount column.

Covered by second use right (max qty)

The number of license entitlements that were not consumed because the related consumption was covered by the second use right on the license.

Related management view: This collective total is not available in management views. For an individual license, open the license properties, and review the Consumption tab. A device contributing to this count shows 0 in the Consumed column, and an Exemption reason of Second use.

Database reference: This is always a calculated value, not stored in the operations databases; but is the count of records in the SoftwareLicenseSecondUseMapping table that have the SoftwareLicenseID column set to the ID of this license in the SoftwareLicense table.

Data warehouse reference: ConsumptionData table, SecondUseCount column.

Exempted (max qty)

The number of installations linked to the license that do not consume a license entitlement because they have an exemption. Exemptions may take either of two forms:

• An exemption for an individual inventory device linked to the license can be made on the Consumption tab of the license properties (these manual exemptions may also be made in bulk using the Apply Allocations and Exemptions page)
• An exemption may be made automatically during license consumption calculations when the inventory device has been assigned a role (such as Test) that matches an exemption reason declared in the Use rights & rules tab of the license properties.

Related management view: See either the Consumption tab of the license properties, or the License Compliance > Apply Allocations and Exemptions page.

Database reference: The exemption count matches the number of entries in the SoftwareLicenseAllocation table that have both:

• A SoftwareLicenseID that links to the correct software license, and
• A non-null value of SoftwareLicenseExemptionReasonID (this is a key to the text reasons given in the SoftwareLicenseExemptionReason table, and any valid value means that an exemption of some kind has been granted).

Data warehouse reference: ExemptCount column in the ConsumptionData table.

Installed (max qty)

The number of installed software records that are linked to the license in question. This is unlikely to be the total number of installations of the same application.

Related management view: For an individual license, look at the Applications tab of the license properties, and add the Installed column from the column chooser. There is no management view that shows this value for many licenses at a time. (Keep in mind that this is not the Installed count on an applications listing such as Installed Applications, because that figure is not filtered by license.)

Database reference: The InstalledSoftwareData table records installations and links to licenses through the SoftwareLicenseID property.

Data warehouse reference: InstalledCount column in the ConsumptionData table.

Last purchase date

The most recent purchase date of all the purchases linked to the selected license.

Related management view: For an individual license, you can check the result on the Purchases tab of the license properties, adding the Purchase date to the table from the column chooser, and sorting on the dates to see the latest one.

Database reference: Not saved as a distinct value in the operations databases. The EntitlementTransaction table links individual purchases (through the PurchaseOrderDetailID) to licenses (through the SoftwareLicenseID). Each purchase then links to the PurchaseOrder table through its PurchaseOrderID, and this table records the PurchaseOrderDate for all the purchases that form part of the same purchase order.

Data warehouse reference: LastPurchaseDate column in the PurchaseData table.

Licensed cores (max)

The number of processor cores that are covered by a license, totaled for all inventory devices linked to this license at the appropriate license consumption calculation.

Related management view: In the properties for an individual license, check the Consumption tab and add the Cores column from the column chooser. This shows the number of cores licensed for each device attached to this license. (Remember that the core count for individual devices may be missing from inventory, depending on the inventory tool used; and that you can manually correct the value in the Hardware tab of the inventory device properties.) No management view of multiple licenses shows the total cores licensed.

Database reference: Individual core counts per device are saved in the SoftwareLicenseCoresConsumedData table, with the total per license summed for all records that have the appropriate SoftwareLicenseID.

Data warehouse reference: LicensedCores column in the ConsumptionData table.

Linked VMs (max qty)

The number of devices linked to this license that are virtual machines. This includes virtual machines which are not consuming entitlements because they are covered by other product use rights, exemptions, and the like.

Related management view: This collective total is not available in management views.

Database reference: Installations recorded in the InstalledSoftwareData are linked through the ComplianceComputerID column to the ComplianceComputer. Of these linked records in ComplianceComputer, the number with ComplianceComputerTypeID=3 gives the count of VMs (this is a foreign key to the ComplianceComputerType table, where 3 = Virtual Machine).

Data warehouse reference: VirtualEnvironmentCount column in the ConsumptionData table.

Purchased (max qty)

The total number of license entitlements owned by the enterprise (or enterprise group) for the given license, being the sum of the Licensed from PO and Extra entitlements values stored in the properties of the license. This is the number of entitlements you are entitled to consume for this license. (Where individual purchases have been associated with particular enterprise groups, these facts are reflected in the subtotals for relevant groups.)

Related management view: See the Compliance tab of the individual license properties, or review a license listing such as the License Compliance > All Licenses page.

Database reference: The EntitlementTransaction table links individual purchases (through the PurchaseOrderDetailID) to licenses (through the SoftwareLicenseID). The PurchasedCount in the data warehouse is the sum of the LicenseQuantity fields for all records in the PurchaseOrderDetail table that are thus linked to the relevant license (filtered for appropriate enterprise groups, where the purchases have values for LocationID, BusinessUnitID, CostCenterID, or CategoryID). Any Extra entitlements (which are saved in the NumberPurchased field of the SoftwareLicense table) are added to the subtotal for the enterprise group identified in the license (if any), or rolled into the total for the enterprise, as appropriate.

Data warehouse reference: PurchasedCount column in the PurchaseData table.

Shortfall/Availability (max)

The calculated difference between Total entitlements and Consumed entitlements (visible in the Compliance tab of the license properties). Positive values show entitlements still available, and negative values show that consumption exceeds purchases (a purchasing shortfall).

Related management view: For each license, see the Shortfall/Availability figure in the Compliance tab of the license properties. Also available in license listings such as License Compliance > All Licenses.

Database reference: This figure is not saved in the operations databases.

Data warehouse reference: CompliancePosition column. Not stored, but calculated on demand as PurchaseData.PurchaseCount less ConsumptionData.ConsumedCount.

Total purchase price (max)

The total of all recorded costs for all the purchases linked to the particular license. (This may be unrelated to the costs of licenses consumed.)

Related management view: The total price for each individual purchase is visible in the All Purchases page (and in the Financial tab of the properties of each purchase, where details can be recorded). There is no management view that shows the rolled-up total of all the purchases linked to a specific license.

Database reference: The EntitlementTransaction table links individual purchases (through the PurchaseOrderDetailID) to licenses (through the SoftwareLicenseID). The Total purchase price is the sum of the TotalPrice fields for all records in the PurchaseOrderDetail table that are thus linked to the relevant license.

Data warehouse reference: PurchasedCost column in the PurchaseData table.

Used (max qty)

Out of the installation records linked to the particular license, this is the subset for which there are usage records that meet the current criteria for software usage (by default, an application must have been used at least once in the last 3 months, with the settings adjustable on the Usage tab of the application properties).

Related management view: You can inspect which devices/users are known to have used the licensed software on the Consumption tab of the license properties. As well, license views such as License Compliance > All Licenses offer the Used count for the installations linked to each license.

Database reference: This is the count of records in the InstalledSoftwareUsageData table that have the SoftwareLicenseID matching the current license.

Data warehouse reference: UsedCount column in the ConsumptionData table.