Interpreting License Counts
FlexNet Manager for Engineering Applications displays the number of deployed licenses for each license group: concurrent, detachable, or activatable, with and without the overdraft count.
Overdraft Licenses
Overdraft licenses are granted by a software publisher and allow for enterprises to use more licenses than purchased. Usually, these overdraft licenses are valid only for a short period of time before additional licenses must be purchased.
In {Hyperlink}Figure {Default ¹ Font}, the feature netf2avend9 has a total license count of 4 and an overdraft license count of 3. This means that one license of the four available has been purchased by the enterprise, while the publisher has authorized the use of three overdraft licenses.
Note:FlexNet Manager for Engineering Applications supports triggering an alert every time an activatable overdraft license is used.
Total
Total license counts for a feature or product are computed based on the license source (license file or fulfillment record in trusted storage).
For licenses in license files, the total is the sum of licenses purchased plus overdraft licenses.
Total = Count + Overdraft
| • | Count—The count field of the license line. |
| • | Overdraft—The value set for overdraft in the license line. |
For licenses in fulfillment records, the count in the license line is multiplied by the number of licenses to arrive at the total. For example, the total concurrent count for product A is:
Total = (Count x Concurrent) + (Overdraft x ConcurrentOverdraft)
| • | Count—The count field of the license line. |
| • | Concurrent—The number of concurrent licenses purchased. |
| • | ConcurrentOverdraft—The number of concurrent overdraft licenses purchased. |
To further understand counts as they appear in different pages of your Licenses tab, consider the following example of the license assets of Company A.
|
License Source |
Product |
Product Count |
Feature |
Feature Count |
License Type |
|
Fulfillment Record 1 |
P1 |
6 |
f1 |
1 |
Activatable |
|
f2 |
1 |
||||
|
Fulfillment Record 2 |
P1 |
10 |
f1 |
1 |
Detachable |
|
f2 |
1 |
||||
|
Fulfillment Record 3 |
P2 |
1 |
f1 |
4 |
Concurrent |
|
License Certificate 1 |
- |
- |
f1 |
7 |
Concurrent |
|
- |
- |
f2 |
7 |
Concurrent |
There are several points to note:
| • | In the column License Source, Company A has both trusted storage, as well as license file–based licenses. A fulfillment record is stored in trusted storage, while license certificates make up license files. |
| • | In the column License Type, trusted storage has licenses of the activatable, detachable, and concurrent types. License certificates only have concurrent licenses. This is always true of license file–based licenses, not just for Company A. |
| • | Features are the basic unit of licensing for both license file- and trusted storage-based licenses. However, in license certificates, features are not grouped into products. (See the Product column in the table above.) For example, both Fulfillment Record 1 and License Certificate 1 contain licenses for features f1 and f2. However, f1 and f2 are grouped to form the product P1 in Fulfillment Record 1. |
| • | Fulfillment Record 1 contains 6 activatable licenses (see Product Count) for product P1. |
| • | Fulfillment Record 2 contains 10 detachable licenses (see Product Count)) for product P1. |
| • | Fulfillment Record 3 contains 1 concurrent license (see Product Count)) for product P2. |
| • | License Certificate 1 contains 7 concurrent licenses each (see Feature Count) for features f1 and f2. These features do not combine to form a product. |
| • | Each product P1 contains one each of features f1 and f2. |
| • | Each product P2 contains 4 of feature f1. |
This is how the information appears in the Licenses tab for Company A:
| • | There are a total of 21 concurrent licenses for feature f1: |
10 (Fulfillment Record 2) + 4 (Fulfillment Record 3) + 7 (License Certificate 1) = 21
Note that the 6 licenses in Fulfillment Record 1 do not contribute to this total. This is because these are licenses that cannot be checked out of and in to a license server machine; they can only be activated on end-user machines.
| • | Feature f1 cannot be activated or detached independently; along with feature f2, it combines to form Product P1, for which Company A has activatable and detachable licenses. (See Fulfillment Record 1 and Fulfillment Record 2) |
| • | Checking out a concurrent license for feature f1 does not require checking out a license for feature f2. |