The vApp cost appears at various stages of the request and provisioning life cycle and is updated according to the current information in the request or on the provisioned item.

Daily cost and lease cost appear at all stages of the lifecycle. After the vApp is provisioned, the cost-to-date also appears.

Table 1. Cost Displayed During the Request and Provisioning Life Cycle

Life Cycle Stage

Value Displayed for Cost

Viewing the catalog item details before a request

Projected costs based on the cost profile, the values for machine resources specified in the component blueprints, lease duration specified in the vApp blueprint, and the daily costs specified in the component blueprints and vApp blueprint.

The values of some of the cost drivers can be unknown before a machine is requested:

  • The component blueprints can specify a range for machine resources. The requester can specify any value in the blueprint range.

  • More than one reservation can be available for provisioning the vApp. If these reservations have different virtual datacenters, different cost profiles can apply.

  • More than one datastore can be available for provisioning the vApp, either on the same reservation or on different reservations, that have different storage cost profiles.

  • If more than one reservation or datastore is available, the daily cost apperas as a range with the lower bound being the minimum resource use multiplied by the lowest resource cost for memory, CPU, and storage, and the upper bound being the maximum resource use multiplied by the highest cost.

If the vApp blueprint specifies a range for the lease duration or the daily cost is a range, the lease cost appears as a range with the lower bound being the minimum lease duration multiplied by the minimum cost, and the upper bound being the maximum lease duration multiplied by the maximum cost.

Completing the request form

Projected costs based on the cost profile, the values for machine resources and lease duration specified in the request form and the blueprint cost.

The daily cost can be a range if more than one reservation is available for provisioning the component machines and these reservations have different virtual datacenters that vary in cost. Alternatively, more than one datastore can be available for provisioning the component machines, either on the same reservation or on different reservations, that vary in cost.

By default the request form shows the request for the vApp, but the requester can select a specific vApp component to edit the properties of the component. The values for daily and lease cost are updated as the user edits the relevant values in the request form.

Viewing details of a submitted request or approving a request

Projected costs based on the requested machine resources, lease duration, and blueprint cost.

The daily cost can be a range if more than one reservation is available for provisioning the component machines and these reservations have different virtual datacenters that vary in cost. Alternatively, more than one datastore can be available for provisioning the component machines, either on the same reservation or on different reservations, that vary in cost.

Depending on the approval policy, an approver can edit values for machine resources or lease duration that affect the cost, but the cost information is not updated in the request.

Viewing the details of a provisioned machine

Actual daily cost, lease cost, and cost-to-date based on the resource use of the provisioned component machines, lease duration, blueprint costs, and number of days since the vApp was provisioned. You can view the cost details for both the vApp as a whole and its component machines.