How one can create per-VM Value Fashions for per-GB-VRAM Options


This month at VMware Discover Europe in Barcelona, we hosted an Govt Briefing session for VCPP companions. It included a number of breakout periods, 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 the right way to construct further, monetizable providers utilizing the VCPP Flex-Core Bundle and Add-Ons.

Determine 1: Flex Core Bundles and Add-Ons in VCPP

In the course of 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 affordable pricing mannequin for per-GB-VRAM options and merchandise in VCPP?”. That is what I’m going to reply on this weblog submit.

Understanding VCPP Pricing

Whenever you look into the Product Utilization Information, positioned in Companion Join, you will discover 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 dearer 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 total value of any given workload and is totally Pay-as-you-go and scalable for the supplier. On the gross sales and pricing facet, nonetheless, the per-GB-VRAM metric may 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 could be reluctant to pay a special worth 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 may be merely no relatable technical connection between the characteristic and the completely different worth factors.

Determine 2: Add-On Examples in VCPP

Aligning on a per VM cost

The plain reply to the above query is subsequently: Cost per characteristic set that any given VM makes use of, no matter the quantity of VRAM the VM has. This often raises some eyebrows with the viewers. Why? As a result of this proposal disconnects the associated fee driver (VRAM) from the income driver (No. of VMs). And that may make calculations difficult and improve danger on the specified margins.

Nonetheless, with the suitable information and a few easy monetary engineering, VMware Cloud Suppliers can mitigate this danger and make sure the margins they need. Each whereas promoting options and merchandise on a compelling, per-VM foundation.

It’s all in regards to the Math

Right here is the way it’s completed: We to start with want a stable understanding of the common 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 finished 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. General, the bigger the set of VMs we have a look at, the higher to attenuate danger.

As a straightforward instance, lets assume the record of VMs seems as follows:

Desk 1: Instance Checklist of VMs

For the reason that value driver for the supplier within the VCPP mannequin is GB of VRAM in relation to the factors per GB VMware prices per set of options, we have to perceive the incremental variety of factors. You possibly can confer with 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 desires to cost and promote a set of options that provides 5 factors per GB of VRAM to the Flex-Core worth. This provides us the next:

VMvRAM (GB)Added Factors
Desk 2: Instance added Factors per VM

And based mostly on the VCPP factors worth, the supplier can now calculate the incremental value for any given VM dimension. We assume the record worth of 1 USD per VCPP level right here. To date really easy. Now comes the vital half. We wish to discover a worth in the direction of the shopper that fulfils the next necessities:

  • Be relevant throughout any given GB VRAM dimension of a VM
  • Cut back Danger
  • Protect Margin
  • Be aggressive

To attain this steadiness, we first must calculate the common value added for the characteristic set. On this case, it’s 42 USD:

VMvRAM (GB)Added FactorsAdded Prices
VM-142020 USD
VM-242020 USD
VM-321010 USD
VM-484040 USD
VM-524120120 USD
  Common Price:42 USD
Desk 3: Common Prices for the instance VMs

With this data, the supplier can add a markup as proportion of the full common prices for the add-on characteristic set to find out an incremental worth per VM. That worth is unbiased of the VMs VRAM dimension, which is the primary necessities we had.

Absolutely the margin is, nonetheless, completely different for VMs of various sizes, and will even be unfavorable on a per VM foundation. On this instance, VM-5 would generate a unfavorable margin based mostly on these assumptions. To scale back danger and protect wishes constructive margin, the supplier can now calculate based mostly on completely different markups for the characteristic set and decide the optimum, absolute margin that additional ensures competitiveness. On this instance we used 25 % markup:

VMvRAM (GB)Added FactorsAdded PricesValueMargin
VM-142020 USD52,5 USD32,5 USD
VM-242020 USD52,5 USD32,5 USD
VM-321010 USD52,5 USD42,5 USD
VM-484040 USD52,5 USD12,5 USD
VM-524120120 USD52,5 USD-67,5 USD
  Common Price:42 USDComplete Margin:52,5 USD
Desk 4: Per VM and complete Margin throughout all VMs

It’s vital to look at that, whereas some absolute margins for bigger VMs, like VM-5 on this instance, are unfavorable, the full total margin at all times stays constructive as a result of restoration from smaller situations. On this case, a set of options or capabilities delivered by merchandise which can be charged at a further 5 VCPP Factors, could 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 % total margin.

If extra granularity and extra risk-mitigation is required, companions can phase 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 might usually be completed based mostly completely on VRAM dimension, which leads us again into the unique path of a hyperlink between technically disconnected options to promote and the completely different worth factors. Due to this fact, is should be used with warning, i.e. solely in few segments.

An analogous method is to mannequin VM courses and worth these VM courses and their add-ons in line with their use-case. That is continuously seen in hyperscale pricing fashions and will be completed in VCD utilizing Compute Insurance policies, too. With this, VMware Cloud Suppliers can construct, for instance, memory-intensive VM courses and t-shirt sizes, that include a special per-VM add-on worth in comparison with general-purpose VM courses.

Determine 3: Instance of VM courses with completely different per-VM costs for Add-Ons

As a ultimate possibility, Suppliers can embody the extra options within the base VM worth for a category, for instance a high-security VM class, that features further networking, safety and monitoring capabilities within the per-VM base worth with out Add-Ons.

Extra Issues and Planning

With the above instance, we have been capable of present the right way to calculate a per-VM worth from a per-GB-VRAM value driver. The logic introduced therein doesn’t change whether or not the calculation is finished for five, 50 or 5,000 VMs. But there are a few further concerns for real-world situations.

Initially, 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 completed, the supplier is vulnerable to being much less aggressive and overpricing.

The larger challenge 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 time limit. This method contradicts the scalable and versatile nature of utilizing Cloud assets, the place VMs get spun up, scaled or deleted as calls for change. To counter this impact and its probably unfavorable influence on margin, companions ought to calculate based mostly on completely different situations and assumptions in regards to the growth of the surroundings. Because the surroundings grows or the calculation is finished throughout a bigger set of VMs, outliers in both path may have much less influence on the margin.

Moreover this fundamental monetary engineering, companions can implement contractual security nets that permit them to regulate pricing in accordance with the common dimension of workloads or different modifications to the surroundings, which is frequent observe in cloud environments.

In some circumstances, it might probably make sense to have sure options included in an elevated base VM worth with out breaking them out into separate, per-VM SKUs. That is for instance the case when a characteristic is often utilized by each VM within the surroundings, 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-Phase foundation. On this case, companions might nonetheless implement a extra granular charging mannequin, however want to concentrate to the inherit danger of disconnecting the associated fee driver from the income driver. Because of this and to create a predictable pricing mannequin for patrons, an elevated base cost for all VMs will be the better option in comparison with granular per-VM pricing.

Companions ought to seek the advice of the Utilization Meter Detection information, out there in Companion Join, to know the precise metering mechanism and derive the suitable charging mannequin.

Extra Help

If you happen to’d prefer to get began with calculating the enterprise alternative behind these further worth added providers, VMware supplies Cloud Supplier alternative calculators for Flex-Core and value-added providers.

And as at all times, please don’t hesitate to succeed in out to your account groups and as for assist with constructing your enterprise case and monetization technique.


Please enter your comment!
Please enter your name here