vRealize Automation Cloud Assembly pricing cards help cloud administrators define and assign the pricing policy for the monetary impact of your individual deployments to help you manage resources.

Before you can create or assign pricing cards, you must configure and enable pricing in vRealize Operations to work with vRealize Automation . When configuring vRealize Operations with vRealize Automation , ensure that both applications are set to the same timezone. To configure the timezone in vRealize Operations, enable SSH and log in to each vRealize Operations node, edit the $ALIVE_Base/user/conf/analytics/advanced.properties file, and add timeZoneUseInMeteringCalculation = <time zone>.

Pricing cards define the rates for a pricing policy. The pricing policy can then be assigned to specific projects to define a total price. After creating a vRealize Operations endpoint, a predefined Default Rate Card is available with a cost equal to price configuration on the Infrastructure > Pricing Cards tab. You can create pricing cards that apply to projects only or cloud zones. By default, all new pricing cards are applied to projects.
Note: If you change the All pricing cards are applied to setting, all existing pricing card assignments are deleted. Also, if the vRealize Operations endpoint is deleted from Cloud Assembly, all pricing cards and assignments are also deleted.

The price of a deployment over time appears on the deployment card as the month-to-date price, which resets to zero at the beginning of each month. The component cost breakdowns are available in the deployment details. Providing this information at the deployment level informs the cloud administrator, but it also helps the members understand the impact their work might have on budgets and long-term development.

How is price calculated

The initial price that you see at the deployment level for your compute and storage resources are based on industry standard benchmark rates, and then calculated over time. The rate is applied to hosts and the service calculates the CPU and memory rates. The server recalculates the price every 24-hours.

New policies, assignments, and upfront pricing are priced during the next occurring vROPs data collection cycle. By default, the data collection cycle is run every 5 minutes. It can take up to 24-hours for new policies or changes to be updated in projects and deployments.

You can also manually refresh the price server at any time on the vROPs Endpoint page, Infrastructure > Integrations > vROPs Endpoint > . In the vCenter servers section, click Sync. When manually refreshing the price server using the Sync option, the price is recalculated for all projects in the organization. Depending on how many projects your organization has this process might be intensive and take time.

For a list of supported resources, see List of costed component types in vRealize Automation Cloud Assembly.