The annual cost of a service is displayed on the Details pane of the Summary tab, as shown in the example in the following figure.
How does vCommander calculate the cost of a service on an annual basis? It takes the cost of the allocated or reserved resources for the service and then adds the storage costs, operating system costs, support costs and custom attribute costs. For more information about entering the costs that vCommander uses in its calculations, see Configuring Cost Models.
Because deployment decisions (for example, target host or cluster and storage location) can affect the total cost of a service when it's deployed, the cost of a service in the Service Catalog may not match that displayed for the source service in the tree. The cost displayed in the Details pane for a VM template includes only storage and custom attribute costs – it doesn’t include CPU, memory or operating system costs. The cost displayed for that same template when added to the Service Catalog, however, includes all resource costs. The Service Catalog cost provides you with a more realistic view of what the template would cost when deployed as a VM.
Also note that the Service Catalog costs displayed in vCommander are not necessarily (or even likely) what the Service Portal user will see. In the Service Portal, the displayed costs are based on the configured provisioning destination for that user. If multiple destinations are configured or no destination is configured, then vCommander displays the most reasonable cost estimate. If a Service Portal users chooses the destination on the request form, the displayed costs change accordingly.
To learn how costs are displayed for AWS stacks, see Managing AWS CloudFormation Templates and Stacks with vCommander. To learn how costs are displayed for ARM templates, see Managing ARM Templates and Resource Groups with vCommander. Note that the cost of a public Azure image is always displayed as $0.