Usage Summary Report

A Usage Summary report provides textual output that summarizes the usage statistics for each feature. The top section of the report provides information about the report parameters—including when the report was run, the vendors and license server hosts included in the report—and a list of the features with and without activity.

Feature activity includes all feature events, including checkouts, denials, unsupported requests, and queued requests. If you chose to sort the report data by feature, you can click a feature name in the “Features with activity” section to view the specific activity for that feature.

Note:In rare cases, the vendor daemon reports unsupported events in the report log as ultimate denials, instead of unsupported events. These events appear in the report log as ultimate denials, but unlike standard ultimate denial events, these events do not have any license feature associated with them. FlexNet Manager for Engineering Applications reports these events as unsupported events, rather than denials.

The bottom section of the report, with default settings, contains one line per feature and multiple columns per line, depending on the breakdown categories you selected. These columns are described in the following table.

Usage Summary Feature Activity Information

Column Name	Description
Max Avail	Maximum license count available for the specified time period. When the availability for a feature is unlimited, the Max Avail is displayed as Uncounted.
Hrs Avail	Available license count multiplied by the time available. When the availability for a feature is unlimited, the Hrs Avail is displayed as n/a.
Requests	Total number of license requests: Used + Denied + Unsupp (unsupported) Note:RIF-formatted output does not include this column.
Used	Number of license requests fulfilled.
Duplicates	Number of licenses requests where duplicate grouping was used to prevent the need to use a new license
Queued	Number of license requests queued.
Denied	Number of license requests denied. If the client application was built using FlexNet Licensing 9.0 or later, only true (ultimate) denial events by Vendor Daemon will be in the report. All that are not ultimate denial events are ignored.
Unsupp	Number of license requests not fulfilled because the feature is unsupported. These are also referred to as exception events.
%Denied	Percent of license requests that were denials. For more information, see “License Denials.”
Max	Maximum number of licenses used simultaneously, including overdraft licenses.
Hours	Number of available license hours used.
Total Used	Total number of license hours used.Unlike Hours, this include license hours where the usage was reduced due to duplicate-grouping, and as such may be greater than Hrs Avail.
%Used	Percent of available license hours used. The formula is: % Used = Used hours / Available hours * 100

Note:For more information on how duplicate grouping can affect license usage, review “Duplicate Grouping” in the concepts guide.

 

Denials in Usage Summary Report:

If there are denials in your reports where the maximum available number of licenses was never used, some of the possible reasons are listed below, including an example for each:

•

The number of available licenses changed during the report period.

For example, you may have started your report when you had ten licenses of Feature A. A few months later, while you were writing to the same report log, you add ten more Feature A licenses. Your report would now show a maximum number of available licenses as being 20, and maximum number of used licenses as being 18, but also shows eight denials. These denials probably occurred when you only had ten available licenses.

•

A vendor enabled the “use all features” switch.

For example, if this switch is enabled and you try to check out a license for a feature that has multiple feature lines (some of which are already checked out), denials will be logged for each feature line that is already in use until the license server finds an available license.

•

Some licenses are reserved for particular users.

For example, if someone outside of the reservation group tries to check out a reserved license, the request will be denied because even though all licenses for a feature are not checked out, they are not available to all users. License reservations are set in a vendor daemon’s options file.

•

Some users are excluded from the group of users who can check out a license.

For example, a particular user may be denied from checking out a license even though not all of the available licenses are checked out. A particular user can be excluded through a vendor daemon’s options file.

•

The total number of licenses for a feature are divided among multiple license servers.

For example, when all licenses for a feature allocated to a particular license server are checked out, additional requests from that server will be denied even though licenses are available for the same feature from another server.

To create a Usage Summary report configuration:

1.

From the Reporting tab, under Classic Reporting, click Report Configurations.

2.

For the Usage Summary report configuration, click Edit to launch the Create Report Configuration Wizard.

3.

In the Create Report Configuration: Naming page, provide a name and description for your report configuration, specify a date range, and select the vendor daemons and license server hosts from which you want report log data.

4.

In the Create Report Configuration: Feature Selection page, select the features whose report logs you want to use to provide data, and specify how you want the features identified in the report.

5.

In the Create Report Configuration: Filter Properties page, create filters to focus the data that is displayed in the report.

6.

In the Create Report Configuration: Summary Options page, specify breakdown categories for report data and select the time periods to include in the report.

7.

In the Create Report Configuration: Output Options page, select the report output format, specify sort order, and provide additional output-related information.

8.

Click Finish or Finish & Run.

See Also

Running Classic Reports

Classic Reporting