Blog

Farewell Single Version Charging (SVC)

2 Posted by - February 28, 2017 - Blog

Farewell Single Version Charging (SVC)

For more years than I care to remember customers asked me “Why do we have Single Version Charging (SVC)?”, “Can I extend my SVC period?”, “Is there another way of me installing the latest version of CICS against a prior version, without paying for both?”, “Your pricing sucks!” – and variations on those statements. Well on February 14th 2017, IBM delivered a Valentine’s day present to address these questions.

In their announcement letter 217-093, Multi-Version Measurement (MVM) replaces Single Version Charging for eligible z/OS and z/VSE software programs. The announcement outlines the replacement of SVC with MVM, which also replaces the Migration Pricing Option (MPO) and the IPLA Migration Grace Period – further details are available from the announcement letter.

Simplistically this eliminates the possibility of being charged separately for multiple versions. It is a complete replacement for all three of the existing pricing offerings, SVC, MPO and the IPLA Migration Grace Period.

MVM dramatically simplifies pricing by replacing three completely different pricing policies with one single, more flexible, standard policy. MVM imposes no time limits upon customers who run multiple eligible versions of software in much the same way customers were not charged for latest releases within a version in the previous pricing method.

MVM provides Clients with more control over their upgrade cycles, allowing them to prioritize and stage software upgrades as their business requirements demand. This also allows more flexibility to react to unforeseen issues by altering their upgrade projects plans without needing to notify IBM or apply for technical waivers.

With continuous delivery development cycles, providing customers the opportunities to update their run-times with latest technologies is now seamless. Clients can deploy new capabilities delivered in new software versions for specific projects that require them without also being required to upgrade everything else.

In cases where upgrades to certain older and less critical workloads is a more problematic upgrade, Clients can now choose to leave those on an older version, while upgrading everything else without initiating SVC.

 

 

 

Comments