Configure Tier Tealeaf in CA SAM

Document ID : KB000120699
Last Modified Date : 26/11/2018
Show Technical Document Details
Introduction:
  • Does CA SAM have a metric engine for RVU based on MMI or its conversion?
  • Do you have any example of application of this metric? How are the levels calculated in the tables?
Background:

Resource Value Unit (RVU)

Resource Value Unit (RVU) is a unit of measure by which the Program can be licensed. RVU Proofs of Entitlement are based on the number of units of a specific resource used or managed by the Program. Licensee must obtain sufficient entitlements for the number of RVUs required for Licensee's environment as defined by the specific software terms. RVU entitlements are specific to the Program and the type of resource and may not be exchanged, interchanged, or aggregated with RVU entitlements of another program or resource.

Note: Some programs may require licenses for the Resources available to AND the resources being managed by the Program. In that case, the following applies: In addition to the entitlements required for the Resources used by the Program directly, Licensee must obtain entitlements for this Program sufficient to cover the Resources managed by the Program.

Note: Some programs may be licensed on a managed basis ONLY. In that case, the following applies: Instead of the entitlements required for the Resources used by the Program directly, Licensee must obtain entitlements for this Program sufficient to cover the Resources managed by the Program.

To understand these benefits of Resource Value Unit licensing and to determine how many Resource Value Units to obtain, please refer to the program specific Resource Value Unit table. You may also contact IBM or your IBM Sales representative.

Instructions:
There is no special metric engine. In most cases customers rely on the external calculation of IBM's own tools. If you want to calculate within CA SAM on your own, you need to know how the product is licensed. We know e.g. RVU products that are calculated based on number of cores of a device put through a tiering table. For this the approach is rather simple. You need a small job updating the installation quantity to the number of cores. Afterwards the product should use the "Generic tiers" metric engine for the conversion. It needs connected tier ranges for each of the "discount levels". Master catalog expects the externally pre-calculated numbers, though. So you need to adjust the catalog for self-calculation.