
This month at VMware Discover Europe in Barcelona, we hosted an Govt Briefing session for VCPP companions. It included a number of breakout classes, and I used to be invited to current the one titled “Exploiting your VCPP Bundles to the fullest with incremental income streams”. In essence, my breakout session coated construct further, monetizable providers utilizing the VCPP Flex-Core Bundle and Add-Ons.

Through the session, one of many attendees requested an attention-grabbing query, that comes up in lots of conversations with companions: “How do I arrive at an inexpensive pricing mannequin for per-GB-VRAM options and merchandise in VCPP?”. That is what I’m going to reply on this weblog publish.
Understanding VCPP Pricing
While you look into the Product Utilization Information, positioned in Associate Join, you will see that almost all of merchandise and options are metered and priced based mostly on the quantity of VRAM consumed by the VM that leverages a given set of options. For instance, NSX-T DC Skilled provides x Factors to the Flex Core Bundle cost, whereas the NSX-T DC Superior Version provides y Factors to it. The extra options and merchandise a given VM makes use of, the costlier it turns into for the supplier – in direct relation to the GB of digital RAM reserved or allotted to that specific VM.
This mannequin supplies a properly aligned foundation for calculating the complete value of any given workload and is absolutely Pay-as-you-go and scalable for the supplier. On the gross sales and pricing facet, nevertheless, the per-GB-VRAM metric could cause a problem. It’s pretty unusual within the cloud market to cost for options, like community capabilities in NSX or monitoring capabilities in vRealize, based mostly on the quantity of VRAM a VM has. Prospects can be reluctant to pay a distinct value for his or her distributed firewall or OS monitoring between two VMs, solely as a result of they’ve completely different sizes of reminiscence. There’s merely no relatable technical connection between the function and the completely different value factors.

Aligning on a per VM cost
The plain reply to the above query is subsequently: Cost per function set that any given VM makes use of, regardless of the quantity of VRAM the VM has. This often raises some eyebrows with the viewers. Why? As a result of this proposal disconnects the price driver (VRAM) from the income driver (No. of VMs). And that may make calculations difficult and enhance threat on the specified margins.
Nevertheless, with the suitable knowledge and a few easy monetary engineering, VMware Cloud Suppliers can mitigate this threat and make sure the margins they need. Each whereas promoting options and merchandise on a compelling, per-VM foundation.
It’s all concerning the Math
Right here is the way it’s achieved: We to begin with want a stable understanding of the typical VRAM dimension and distribution of VMs {that a} single buyer or the sum of all prospects are working on the cloud platform that we wish to calculate pricing for. Whether or not the evaluation is completed for one buyer solely or throughout all prospects is determined by whether or not the supplier has a devoted pricelist per buyer or a single pricing mannequin throughout all prospects. Total, the bigger the set of VMs we take a look at, the higher to reduce threat.
As a simple instance, lets assume the checklist of VMs seems as follows:
VM | vRAM (GB) |
VM-1 | 4 |
VM-2 | 4 |
VM-3 | 2 |
VM-4 | 8 |
VM-5 | 24 |
Because the value driver for the supplier within the VCPP mannequin is GB of VRAM in relation to the factors per GB VMware costs per set of options, we have to perceive the incremental variety of factors. You’ll be able to seek advice from the Product Utilization Information to calculate the variety of factors based mostly on the options and merchandise your prospects want. Let’s assume the supplier needs to cost and promote a set of options that provides 5 factors per GB of VRAM to the Flex-Core value. This offers us the next:
VM | vRAM (GB) | Added Factors |
VM-1 | 4 | 20 |
VM-2 | 4 | 20 |
VM-3 | 2 | 10 |
VM-4 | 8 | 40 |
VM-5 | 24 | 120 |
And based mostly on the VCPP factors value, the supplier can now calculate the incremental value for any given VM dimension. We assume the checklist value of 1 USD per VCPP level right here. Thus far really easy. Now comes the necessary half. We wish to discover a value in the direction of the client that fulfils the next necessities:
- Be relevant throughout any given GB VRAM dimension of a VM
- Cut back Danger
- Protect Margin
- Be aggressive
To realize this steadiness, we first have to calculate the typical value added for the function set. On this case, it’s 42 USD:
VM | vRAM (GB) | Added Factors | Added Prices |
VM-1 | 4 | 20 | 20 USD |
VM-2 | 4 | 20 | 20 USD |
VM-3 | 2 | 10 | 10 USD |
VM-4 | 8 | 40 | 40 USD |
VM-5 | 24 | 120 | 120 USD |
Common Value: | 42 USD |
With this info, the supplier can add a markup as proportion of the entire common prices for the add-on function set to find out an incremental value per VM. That value is unbiased of the VMs VRAM dimension, which is the primary necessities we had.
Absolutely the margin is, nevertheless, completely different for VMs of various sizes, and will even be destructive on a per VM foundation. On this instance, VM-5 would generate a destructive margin based mostly on these assumptions. To scale back threat and protect wishes optimistic margin, the supplier can now calculate based mostly on completely different markups for the function set and decide the optimum, absolute margin that additional ensures competitiveness. On this instance we used 25 p.c markup:
VM | vRAM (GB) | Added Factors | Added Prices | Worth | Margin |
VM-1 | 4 | 20 | 20 USD | 52,5 USD | 32,5 USD |
VM-2 | 4 | 20 | 20 USD | 52,5 USD | 32,5 USD |
VM-3 | 2 | 10 | 10 USD | 52,5 USD | 42,5 USD |
VM-4 | 8 | 40 | 40 USD | 52,5 USD | 12,5 USD |
VM-5 | 24 | 120 | 120 USD | 52,5 USD | -67,5 USD |
Common Value: | 42 USD | Whole Margin: | 52,5 USD |
It’s necessary to watch that, whereas some absolute margins for bigger VMs, like VM-5 on this instance, are destructive, the entire total margin all the time stays optimistic as a consequence of restoration from smaller situations. On this case, a set of options or capabilities delivered by merchandise which are charged at an extra 5 VCPP Factors, can be bought at 52,50 USD per VM. This equals a complete of 262,50 USD of incremental income with a complete of 52,50 USD or 20 p.c total margin.
If extra granularity and extra risk-mitigation is required, companions can section the projected sizes of VMs and apply completely different costs based mostly on the weighted common for per-VM options in these segments. This segmentation may sometimes be achieved based mostly completely on VRAM dimension, which leads us again into the unique route of a hyperlink between technically disconnected options to promote and the completely different value factors. Due to this fact, is should be used with warning, i.e. solely in few segments.
An identical method is to mannequin VM lessons and value these VM lessons and their add-ons in line with their use-case. That is steadily seen in hyperscale pricing fashions and might be achieved in VCD utilizing Compute Insurance policies, too. With this, VMware Cloud Suppliers can construct, for instance, memory-intensive VM lessons and t-shirt sizes, that include a distinct per-VM add-on value in comparison with general-purpose VM lessons.

As a last possibility, Suppliers can embody the extra options within the base VM value for a category, for instance a high-security VM class, that features further networking, safety and monitoring capabilities within the per-VM base value with out Add-Ons.
Further Issues and Planning
With the above instance, we have been in a position to present calculate a per-VM value from a per-GB-VRAM value driver. The logic offered therein doesn’t change whether or not the calculation is completed for five, 50 or 5,000 VMs. But there are a few further concerns for real-world eventualities.
To begin with, incremental cost inside VCPP is capped at a specific amount of chargeable GB of VRAM. Each VM that’s bigger than that cap, should be handled as if it has the capped most of GB VRAM within the calculation. If that’s not achieved, the supplier is susceptible to being much less aggressive and overpricing.
The larger concern that comes up in conversations about this method, is the static nature of the mannequin. We checked out a snapshot of VMs and their VRAM sizes at a given cut-off date. This method contradicts the scalable and versatile nature of utilizing Cloud sources, the place VMs get spun up, scaled or deleted as calls for change. To counter this impact and its probably destructive influence on margin, companions ought to calculate based mostly on completely different eventualities and assumptions concerning the growth of the setting. Because the setting grows or the calculation is completed throughout a bigger set of VMs, outliers in both route could have much less influence on the margin.
Moreover this fundamental monetary engineering, companions can implement contractual security nets that enable them to regulate pricing in accordance with the typical dimension of workloads or different adjustments to the setting, which is widespread apply in cloud environments.
In some instances, it will possibly make sense to have sure options included in an elevated base VM value with out breaking them out into separate, per-VM SKUs. That is for instance the case when a function is often utilized by each VM within the setting, like IDS in NSX-T DC Superior. The identical mannequin could also be utilized for options and functionalities that aren’t detected on a per VM-basis by Utilization Meter. Examples embody IPv6 dynamic routing, EVPN and VRF, that are detected per Tier-0 Router. Or L2VPN, which is detected on a per-Section foundation. On this case, companions may nonetheless implement a extra granular charging mannequin, however want to concentrate to the inherit threat of disconnecting the price driver from the income driver. For that reason and to create a predictable pricing mannequin for patrons, an elevated base cost for all VMs will be the more sensible choice in comparison with granular per-VM pricing.
Companions ought to seek the advice of the Usage Meter Detection guide, available in Partner Connect, to grasp the precise metering mechanism and derive the suitable charging mannequin.
Further Help
For those who’d prefer to get began with calculating the enterprise alternative behind these further worth added providers, VMware supplies Cloud Provider opportunity calculators for Flex-Core and value-added services.
And as all the time, please don’t hesitate to achieve out to your account groups and as for assist with constructing your small business case and monetization technique.