| This page refers to License Statistics v6.18 and newer, which now reports usage for both main features and packages when using Feature Collections for Autodesk license manager. If you are using an earlier version, please refer to the documentation for earlier versions. |
This feature is available with Licensing Model 2019 only. Collections are currently supported only for Autodesk and Dassault license managers. |
Feature Collections let you track feature usage in cases where:
By default, features do not belong to a Collection. You can enable Collections by toggling this option on in the Gathering settings when creating/editing the license server.
For Autodesk, you can enable Collections only when initially creating the license server; thereafter, this setting cannot be changed. However, Collections can be enabled/disabled for Dassault license manager at any time. |
When you enable Collections for a license server, features for that license server will be individually reported, based on their Collection name. The Collection name can be viewed in reports that include information for Features; however, note that this column is hidden by default.
The Collection name is also shown in parentheses following the version and type in feature selectors, labels, and notifications; for example:
For Autodesk, enabling Feature Collections lets you gather more meaningful statistics for features that are combined into packages and sold as a single product by the vendor. In packages such as this, you may have the same feature that has been purchased with multiple different packages, and the price of the feature may differ for each package. In such cases, you can use Collections to separate the feature usage reporting based on which package the feature is in, rather than reporting all feature usage together.
For Autodesk license servers, the Collections setting cannot be changed after creating the license server or enabled for an existing license server, because this would invalidate previously gathered data for that license server. |
For example, say you have one package (Package A) that contains features F1 and F2, and another package (Package B) that contains features F1 and F3.
Without Collections enabled, usage is simply reported by feature, without accounting for which package the features are part of; for example:
However, with Collections enabled, reports will include usage data for each individual package/feature combination in addition to the total usage data for each feature; for example:
For Dassault, enabling Feature Collections lets you track usage by "authorization items." Dassault license server output can be configured by an administrator to define authorization items that control feature usage. Authorization items can be set to any value by which an administrator wishes to specify which "groups" can access the feature (for example, user groups, departments, countries, etc.) and how many of the feature's total licenses each of those groups may consume.
When Collections is enabled, License Statistics will monitor and report on the feature as usual, and if authorization item information is available, License Statistics will also report usage for each defined group separately to indicate how many licenses of the total usage each of the groups accounts for.
The Collections will contain information about user licenses, total available licenses, and user-host sessions that are available on all reports, in the same manner as any other feature. However, the statistics will not contain denials, as the information is available only for the entire feature.
For Dassault license servers, Collections can be enabled/disabled at any time; however, when Collections is disabled, the data for those Collections will not be collected. |
For example, say you have a feature (F1) with a total of 100 licenses. An authorization item may be defined to limit license usage according to country; for example:
On License Statistics reports, the feature usage will be separated according to each authorization item's usage; for example: