Mobile Workload Pricing for z/OS (MWP) is one of the latest tools in the arsenal of software cost containment offerings for the z/OS platform.
Mobile Workload Pricing
MWP can be a very positive cost savings option for customers that have a significant portion of their workload originating from mobile devices.
Much has been written about Mobile Workload Pricing already. For those new to the subject, we suggest reading IBM’s MWP announcement letter and various other documents.
MWP Adds Another Layer of Complexity
The intentions behind MWP were good, but the downside of MWP is that it adds another layer to the already complex z/OS pricing mechanisms.
Traditional Software Pricing Metrics
Until now, the basic metrics that determined your software bill were the Rolling 4-Hour Average (R4HA), combined usage (highest combined peak usage for software that runs on multiple LPARs), Defined Capacity, and Group Capacity Limit. Most sites know how much each additional MSU will cost and they have budget targets that they must live within. Combining these two pieces of information, it is not difficult to identify an MSU cap.
MWP Eligible Workloads
With the introduction of MWP, a new factor comes into play:
- You have to pay the full price for some of your MSUs – those used by traditional work.
- You effectively pay a different price (a discounted one) for MSUs that are consumed by your mobile workloads.
This affects the relationship between consumed MSUs and your monthly software bill. Previously, you could say "if my peak R4HA is 100 MSUs, I have to pay for 100 MSU". Now the cost of that 100 MSUs is variable, depending on how many of those MSUs are MWP-eligible.