Want to learn more about Capacity-Based Licensing for IBM?
As technology advances, software licensing can become a complex and confusing process.
One aspect that can be particularly challenging is understanding the different units of measure by which a program can be licensed.
This article aims to demystify the capacity-based licensing models used by IBM and clarify the different units of measure.
Eight Methods of IBM Capacity-Based Licensing
Install License
An Install is a unit of measure that refers to an installed copy of a software program on a physical or virtual disk that can be executed on a computer. For each Install of the Program, the licensee must obtain an entitlement to use the Program.
Managed Virtual Server License
A Managed Virtual Server is a unit of measure that refers to the licensing of a program based on the physical hardware resources of a server.
A server is a physical computer that executes requested procedures, commands, or applications for one or more users or client devices.
Virtual servers can be created by partitioning the resources of a physical server or by using an unpartitioned physical server. Each separable physical device, such as a blade or rack-mounted device, is considered a separate server.
Licensees must obtain Managed Virtual Server entitlements for each virtual server the program manages.
Processor Value Unit (PVU) License
The Processor Value Unit (PVU) is a measure that determines a program’s licensing based on the processor technology and the number of processors made available to the program.
IBM defines a processor, for PVU-based licensing, as each processor core on a chip.
A dual-core processor chip, for example, has two processor cores. The licensee can deploy the program using either Full Capacity licensing or Virtualization Capacity (Sub-Capacity) licensing.
Full Capacity licensing requires PVU entitlements to cover all activated processor cores in the physical hardware environment managed by the program.
Virtualization Capacity licensing requires PVU entitlements sufficient to cover all activated processor cores made available to or managed by the program, as defined by the Virtualization Capacity License Counting Rules.
PVUs in Containers License
A container is a lightweight, standalone executable package with everything needed to run the software, including code, libraries, and system tools.
The licensing of a program running in a container is based on the number of processors made available to the program, using the same PVU-based licensing model as for non-containerized deployments.
Terabyte License
A Terabyte is a unit of measure that determines a program’s licensing based on the amount of storage capacity available. One Terabyte is equivalent to 2 to the 40th power bytes.
The licensee must obtain an entitlement for each Terabyte of storage available to the program.
Virtual Processor Core (VPC) License
The Virtual Processor Core (VPC) is a unit of measure that determines a program’s licensing based on the number of virtual processor cores available to the program.
A Physical Server is a physical computer that executes requested procedures, commands, or applications for one or more users or client devices.
Virtual servers can be created by partitioning the resources of a physical server or by using an unpartitioned physical server. Each separable physical device, such as a blade or rack-mounted device, is considered a separate Physical Server.
A Processor Core is a functional unit within a computing device that interprets and executes instructions.
A Virtual Processor Core is a Processor Core in an unpartitioned Physical Server or a virtual core assigned to a Virtual Server.
Licensees must obtain entitlements for each Virtual Processor Core made available to the program.
VPCs in Containers License
The licensing of a program running in a container is based on the number of Virtual Processor Cores made available to the program, using the same VPC-based licensing model as for non-containerized deployments.
Virtual Server License
A Virtual Server is a unit of measure that determines a program’s licensing based on the number of virtual servers available to the program.
A server is a physical computer that executes requested procedures, commands, or applications for one or more users or client devices.
Virtual servers can be created by partitioning the resources of a physical server or by using an unpartitioned physical server. Each separable physical device, such as a blade or rack-mounted device, is considered a separate server.
The licensee must obtain Virtual Server entitlements for each virtual server made available to the program, regardless of the number of processor cores in the virtual server or the number of copies of the program on the virtual server.
It’s worth noting that some programs may require licenses for the program and what is being managed. The licensee must obtain additional entitlements to cover the managed resources in these cases.
For example, in addition to the entitlements required for the program directly, the licensee must obtain PVU or Terabyte entitlements to cover the resources managed or processed by the program.
In summary, capacity-based licensing can be a complex topic, but ensuring that a software program complies with licensing agreements is essential.
FAQ About Capacity-Based Licensing
What is Capacity-Based Licensing?
Capacity-Based Licensing is a licensing model that determines the cost of a software license based on the capacity of the underlying infrastructure that the software runs on.
Why is Capacity-Based Licensing important?
Capacity-Based Licensing can be cost-effective for organizations with fluctuating demands or those looking to optimize costs. However, it can also be complex and requires careful management to ensure compliance.
Looking for expert guidance on Capacity-Based Licensing?
Redress Compliance is here to help!
Contact us today to learn more and ensure compliance while optimizing costs.
