Several factors can contribute to the chargeback calculation of cost for vApps.

The cost of a vApp is based on the cost of memory and CPU that component machines consume, and the costs specified in the vApp blueprint and vApp component blueprints. Storage cost is not taken into account for component machines. If you assign a cost profile that includes a value for storage cost to a component machine, it is ignored. You can account for the cost of using storage in the daily cost specified in the blueprint for the component machine.

Table 1. Daily Cost Drivers

Cost Driver

Calculated Cost

Memory

Allocated memory (GB) multiplied by the daily memory cost per gigabyte specified in the cost profile associated with the virtual datacenter on which a component machine is provisioned

CPUs

Number of allocated CPUs multiplied by the daily CPU cost specified in the cost profile associated with the virtual datacenter on which a component machine is provisioned

Blueprint cost (vApp component)

The value for daily cost specified in the vApp component blueprint is added to the total cost of each component machine.

This value can represent a markup for using the machine in addition to the resources consumed by the machine.

Blueprint cost (vApp)

The value for daily cost specified in the vApp blueprint is added to the total cost of the vApp.

This value can represent a markup for using the vApp in addition to the costs of the component machines.

Lease cost is calculated as daily cost multiplied by the total number of days in the lease period, if applicable.

Cost-to-date is calculated as daily cost multiplied by the number of days a vApp is provisioned.