2.5

A price matrix is associated with a pricing model and can contain multiple cost entries for different vCPU
count and memory bundles. You can also define a criterion to specify the hierarchies for which the price matrix
is applicable. You can define multiple pricing matrices with different hierarchy selection criteria for each
pricing model defined in vCenter Chargeback Manager. Each hierarchy selection criteria for a selected pricing
model must be unique. Also, each entry in the pricing matrix must be unique.
vCenter Chargeback Manager applies the fixed cost defined in the pricing matrix on the virtual machines in a
hierarchy by running the VM Instance job that periodically checks for new and updated hierarchies, and
hierarchy selection criteria and the corresponding pricing matrix. Based on the hierarchy and entity selection
criteria, the application uses the corresponding pricing matrix to apply the fixed cost on the virtual machines
in the hierarchies that match the specified criterion as follows:
1 vCenter Chargeback Manager checks for the hierarchy selection criteria and the corresponding pricing
matrices defined in it.
2 vCenter Chargeback Manager uses the pricing matrix corresponding to the first matching criterion for
each hierarchy.
3 vCenter Chargeback Manager first searches for a row in the pricing matrix that has the same vCPU count
as in the virtual machine.
4 If such a row is not found, then vCenter Chargeback Manager selects the row with the next higher value
of vCPU count than in the virtual machine.
5 For the selected vCPU count, vCenter Chargeback Manager checks for a memory value equal to or higher
than the memory in the virtual machine.
6 If a row with the vCPU count or memory value equal to or higher than the vCPU count or memory in the
virtual machine is not found, then vCenter Chargeback Manager uses the default cost configured in the
matrix.
NOTE For hierarchies imported from vCloud Director, the vCPU count and memory allocation values
synchronized from the vCloud Director database is considered for applying the fixed cost. For hierarchies
created in vCenter Chargeback Manager, the vCPU count and memory utilization values synchronized from
the vCenter Server database is used for applying the fixed cost.
If a virtual machine configuration is changed, then the corresponding change in the fixed cost is applicable
from the time the configuration change is effected. If the fixed cost in the pricing matrix is changed, then the
change is effected from the next run of the job.
By default the VM Instance job runs every 5 minutes. You can configure the time interval for the job run from
the General page of the Settings tab. To know about how to configure the VM Instance job interval, see
“Configure VM Instance Job Interval,” on page 15.
If any row in the matrix is deleted, then the corresponding fixed cost is also deleted and is not considered
during reporting. Similarly, if a cost matrix is deleted, then the costs defined in the matrix is lost and is not
considered when a report is generated on the virtual machine, the parent entity, or hierarchy.
You must have a Super User role to create and manage virtual machine instance pricing matrix. Also, the
defined fixed cost is reported only if the report is generated by a Super User.
Create a Pricing Matrix for Virtual Machines
A pricing matrix defines multiple costs based on vCPU count and memory bundles and is associated with a
pricing model and a hierarchy selection criterion.
Procedure
1 In the Configure Cost tab, click Edit VM Instance Cost.
Chapter 5 Managing and Configuring vCenter Chargeback Manager Cost Elements
VMware, Inc. 99