iCap report parameter descriptions

You can use the values generated in iCap reports from Cost Management to set input parameters for iCap policies.

The following table describes the parameters of the iCap report.

Report parameters	Description
Billing Year/Month	Usage month you selected for the report
Peak Interval	The date and time the Peak Interval occurred during the usage month for the managed objects you selected in the report
Low-Importance Level to Delay	Specified low-importance level to delay Workloads with the specified importance level will be delayed if the 4HRA MSU usage surpasses the Maximum MSUs Allowed. That is, if 4 is specified, workloads with an importance value of 4 and below are considered to be low importance. These workloads will be delayed if the MSU usage exceeds the Maximum MSUs Allowed. This parameter corresponds to the Low Importance parameter in iCap policies. For more information, see Policy-level-and-subpolicy-level-parameters.
% to Reduce from Peak MSUs	Specified percentage by which you want to decrease the peak MSU utilizations of the usage month.
Recommended % to Reduce from Peak MSUs	Actual percentage by which the MSU limit was reduced If there is a discrepancy between the % to Reduce from Peak MSUs and the Recommended % to Reduce from Peak MSUs values, this means that there was not enough low-importance work to decrease the peak MSU utilizations of the usage month for the selected percentage amount. For example, if you selected an adjustment of 10% and there was not enough low-importance work to reduce the Peak Interval by 10%, Cost Management calculates the actual percentage that was adjusted. The percentage of low-importance work is shown under Low-Importance Contribution %. The percentage value that you set for % to Reduce from Peak MSUs should not be higher than the value for Low-Importance Contribution %.
Low-Importance Contribution %	Percentage of low importance work that contributed to the Peak Interval
Maximum MSUs Allowed	Maximum allowed 4HRA of combined activity for the managed objects

The table at the bottom of the report contains a row of data for each managed object selected for the report. The following table describes the table columns in the iCap report.

Important

The column name includes the corresponding iCap policy parameter in parentheses. For example, Proportion of Peak MSUs, in .1% (Proportion) corresponds to the Proportion parameter.

Table column	Description
CPC Name - ID	Name of the CPC and the last five digits of the serial number of the CPC
Name (LPAR or Group Name)	Name of the managed object
Type (Type)	Whether the managed object is an LPAR or a group
Proportion of Peak MSUs, in .1% (Proportion)	Percentage that the managed object contributed to the peak 4HRA
Actual Maximum 4HRA (None)	Percentage of low-importance work that contributed to the peak 4HRA for the managed object
Low-Importance Contribution% (None)	Percentage of low importance work on the managed object that contributed to the peak 4HRA
Relative Cost Factor	The cost of a single additional MSU for a managed object. Consider the following points: If you add one MSU to a group, the MSU can be added to only one LPAR in the group. Therefore, the incremental cost of the MSU is counted only once, and included in the relative cost of the group. If you are managing LPAR members individually and you add one MSU, each of the LPARs can be incremented. Therefore, the incremental cost of the MSU is counted in the relative cost of each individual LPAR member. Consequently, the relative cost of a group will always be lower than the sum of relative cost for the LPAR members. Important If you are using more than one version of the same MLC product and you have a Single Version Charge agreement with IBM (in accordance with the IBM SVC rules), the cost of only the newer version of the product is included in the relative cost.

Using-iCap-reports-to-build-a-policy describes how you can use these values to build a policy.

iCap report parameter descriptions

On this page