...
- The feature's name, version, and type (see Feature identifiers, below).
- Information about the feature, such as statistics totals and the last update time.
- A current count of licenses used, borrowed and reserved, and (if not unlimited) the total licenses available.
NEED DATA TO PRODUCE AN UPDATED SCREENSHOT IF WE WANT ONE WITH A MORE CURRENT DATE
Notes:
- Expired features are indicated by a warning icon
in the chart details on the right of the page, as shown above for Used features. The color-coding of the text used for "Last Update Time" indicates the minutes elapsed since the last update time:
Minutes elapsed since last update time Color indicator 0 - 10 Green
10 - 20 Orange 20 or more Red - If there are unlimited licenses for the feature, the license usage gauge will not show the total number of licenses or utilization percentages, since they are not applicable, as illustrated below.
...
Throughout License Statistics, features shown in lists include a separate entry for each version of that feature, and are named feature_version. Versioning provides a finer granularity to report results, which is useful when you have multiple versions of particular features that you want to track individually. For example, under IBM LUM, the Catia MD2 application cost varies depending on version, so Feature Versioning can help when considering budget for one version versus another version.
...
For example, say you have a feature called F1, for which you have a floating installation of version 1.0 and both a node-locked and floating installation of version 2.0. This would appear in Feature lists as follows:
F1 _1(v1.0 (, Floating)
F1 _2(v2.0 (, Floating)
F1 _2(v2.0 (, Nodelocked)
In grids such as License Server Current Usage, feature identifiers are displayed in three separate columns: Name, Version, and Type. If a given feature has more than one type, it will be listed in usage grids once for each type.
...