Methodology of counting usage

Edit online

Product usage is reported for stand-alone products and solution bundles. In case of the latter, the licensing terms might provide specific conditions of how usage of bundled products contributes to the overall usage of the solution. If licensing terms define a ratio between the bundled product and the solution bundle, the ratio is automatically applied, and the result is rounded up to ensure compliance. The information is provided in the form of the audit snapshot.

For example, a solution bundle consists of three bundled products.
  • The first product uses 2 metric units and has the ratio of 1:5.
  • The second product uses 3 metric units and has the ratio of 1:4.
  • The third product uses 2 metric units and has the ratio of 1:5.
For each product, the usage is rounded up to ensure compliance. As a result, each of the products contributes 1 metric unit to the usage of the solution bundle. The solution bundle uses 3 metric units. The usage is calculated the following way:
⌈2/5⌉ + ⌈3/4⌉ + ⌈2/5⌉ ~ 1 + 1 + 1 = 3

Context metrics

A product can use context metrics. These metrics are included by the product but are not listed in the licensing terms and do not contribute to product usage. They provide more visibility into how the product is used.

For example, the product is licensed based on the number of API calls and this metric is listed in the licensing terms. Additionally, the product provides information about the following metrics:
  • Number of users
  • Number of days when the product is installed

This information gives you an overview of how many API calls were made per user and what was the timeframe. Such an approach allows you to maintain full visibility of the environment even when some metrics are available for information purposes only and do not contribute to the overall license consumption.