Consumption Fact: 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.
Measure | Notes |
---|---|
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 . page Database reference: The allocation count matches the
number of entries in the
SoftwareLicenseAllocation table that have
both:
Data warehouse reference:
|
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 . Database reference: The total consumption for each
license in the most recent compliance calculation is stored in the
Data warehouse reference:
|
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
Data warehouse reference:
|
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
Data warehouse reference:
|
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
Data warehouse reference:
|
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:
Related management view: See either the Consumption tab of the license properties, or the . page Database reference: The exemption count matches the
number of entries in the
SoftwareLicenseAllocation table that have
both:
Data warehouse reference:
|
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
Data warehouse reference:
|
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 Data warehouse reference:
|
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 Data warehouse reference:
|
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
Data warehouse reference:
|
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 . page Database reference: The
Data warehouse reference:
|
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 . Database reference: This figure is not saved in the operations databases. Data warehouse reference:
|
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
Data warehouse reference:
|
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 offer the Used count for the installations linked to each license. Database reference: This is the count of records in
the Data warehouse reference:
|
FlexNet Manager Suite (On-Premises)
2023 R1