FlexNet Manager Suite 2022 R2 (On-Premises)
The number of license entitlements consumed by each computer or end-user (depending on license type). The typical quantity is one, but may have other values for any of these reasons:
  • Zero after an individual allocation that is not (or not yet) confirmed by imported inventory, when allocations are not automatically being counted as installations.
  • Zero for device-based licenses, even though the Installed column displays a check, when the device is covered by a right of second use. Typically this device will be a laptop (or notebook) computer. To check, from the column chooser add (and then sort by) the User name column to bring together such paired installations, since the two computers must have the same end-user.
  • Zero for IBM VPC or IBM PVU licenses in any 'child' rows, since the consumption is always shown only for the 'root' row, after all contributions have been rolled up and (if necessary) capped to the total cores available on the host.
    Tip: What is shown in the 'root' row for an IBM VPC license depends on the setting for Bundle consumption rules (in the Use rights & rules tab, under the License consumption rules group):
    • If Consume for each product on a device is selected, the 'root' row of each group is the licensed IBM product
    • If Consume once for each device is selected, the 'root' row of each group is typically the VM host, or possibly a stand-alone server.
  • Zero for IBM PVU licenses where an inventory device has a Device status of Archived — this device has no current consumption, because it is in transition awaiting deletion. It is currently held because of its impact on retrospective calculations of sub-capacity points consumption. (This possibility only exists when FlexNet Manager Suite is responsible for sub-capacity PVU calculations, for which see IBM High-Frequency Scanning.)
  • Zero for IBM PVU licenses where the inventory source does not return a count of Cores for a device.
    Tip: The value of Consumed may be zero, even when the value of Calculated consumption is non-zero. This is because, when the count of cores is missing, the processor count is used instead to give an indicative figure in Calculated consumption. However, since the auditable consumption figure must use the core count, Consumed remains at zero in this corner case. Remember that you can correct a missing core count by drilling through to the inventory device properties and applying an override on the Hardware tab.
  • Greater than one for device-based licenses where a right of multiple use has been specified for this license, and the computer has enough installations to consume multiple license entitlements.
  • Greater that one for user-based licenses where the end-user operates more than one computer on which the software is installed.
  • Much greater than one for points-based licenses, where the number of points per device may be affected by the make of computer, the type of processor, the number of assigned core, or other factors. Calculation rules vary slightly:
    • For Processor Points licenses, this is calculated by identifying the number and types of processors on the computer and applying the relevant points rule.

    • For Core Points licenses on physical machines and orphaned virtual machines, this is calculated by identifying the number of cores and types of processors on the computer and applying the relevant points rule.
      Tip: An orphaned virtual machine is a virtual machine without a host.
    • For Core Points licenses on virtual machines, this is calculated by identifying the VM Host's processor specifications, applying the relevant points rules, and then multiplying that figure by the number of cores on the virtual machine.
    • Oracle Processor licenses do not display this column: see instead Consumed Points.
    Note: In case of a multi-product license, the consumption is not displayed separately for each product. To view the license consumption by each product of a multi-product license, open the Device License Details or User License Details report and group the output by application.
For more about the relationships between various consumption fields (with special emphasis on IBM PVU licenses), see Relationships Between Consumption Fields.
Tip: For an SAP Named User license, an end-user has a non-zero quantity in this field when she has been allocated an entitlement to use SAP under this license. This allocated license need not be the optimal license for this end-user, based on usage levels (compare with the Used result).

Not editable. This value is the result of the latest compliance calculation (the time and date of which is displayed at the top right of every web page).

Not available for CAL Legacy, Core Points, Oracle Application User, Oracle Legacy, Oracle Named User Plus, and Oracle Processor licenses.

FlexNet Manager Suite (On-Premises)

2022 R2