IBM RVU pricing applies to products that scale with managed resources rather than user counts or processor cores. The counting rules, the conversion math, and the audit triggers decide whether the customer captures the value or surrenders it at renewal.
IBM Resource Value Unit is the metric IBM uses for products that scale with managed resources rather than user counts or processor cores. The metric applies to IBM monitoring products, network performance management products, automation products, and selected security products. Each product carries its own RVU conversion table that maps the managed unit to an RVU count.
Across 30 RVU audit defence and renewal engagements, median saving captured against the opening IBM quote ran 44 percent. The lowest saving was 12 percent on a deployment where the inventory record was incomplete. The highest was 68 percent on a deployment where the customer ran a documented Red Hat OpenShift Observability alternative.
Resource Value Unit is a managed resource metric. The metric counts the volume of resources the product manages, not the users that operate the product or the cores the product runs on. The conversion grid translates the managed unit to an RVU count.
The managed resource varies by product. For Tivoli Monitoring the resource is the managed endpoint. For NetCool the resource is the managed device. For Instana the resource is the host. For Cloud Pak for Watson AIOps the resource is the managed asset.
IBM publishes a per product RVU conversion table inside the IBM product license agreement. The table sets the RVU count per managed unit. A managed endpoint might convert at 1 RVU. A managed virtual machine might convert at 0.5 RVU.
RVU prices step down across tiers. The first 1,000 RVUs price at the entry band. The next 9,000 RVUs price at a lower band. The next 90,000 RVUs price at the deepest band.
RVU pricing applies across IBM Cloud Paks, IBM Tivoli, IBM NetCool, and selected security products. The customer needs to know which products carry the metric and which carry processor or named user metrics instead.
IBM Tivoli Monitoring, ITM for Operating Systems, ITM for Databases, ITM for Applications. Each ITM agent counts as one RVU per managed endpoint.
IBM NetCool Operations Insight, NetCool Impact, NetCool Performance Manager. Each managed device counts at the product conversion ratio.
Replaces the legacy IBM AIOps stack. The Cloud Pak runs on RVU per managed asset. The metric counts every monitored host, container, and network device.
Application performance monitoring product acquired by IBM. Runs on RVU per host with a conversion ratio that varies by host type.
QRadar, Guardium, and the IBM Security Verify family use RVU for selected components such as event sources or monitored database instances.
The RVU counting rule sits at the centre of every IBM RVU audit. The rule decides whether a virtual host counts at one RVU or at the host parent count. The rule applies through IBM Sub Capacity Reporting and the IBM License Metric Tool installation.
IBM Sub Capacity Reporting Tool measures the RVU count quarterly. Customers running ILMT in compliance count the RVUs at the managed resource level. Customers without ILMT compliance count at the full physical capacity level.
Virtual hosts count at the virtual machine RVU ratio when ILMT is in place. Without ILMT compliance, the count rolls up to the physical host level.
IBM authorised cloud workloads count at the cloud RVU ratio. AWS, Azure, IBM Cloud, and Google Cloud each carry a different ratio inside the IBM Cloud RVU table.
Containers running on OpenShift count at the OpenShift RVU ratio inside Cloud Pak entitlements. Containers running on plain Kubernetes count at the cluster RVU ratio.
The conversion math runs the RVU count through the tiered pricing grid. The customer that runs the conversion before signature captures the deeper band on the deployment. The customer that signs at the entry band pays the entry price on every RVU.
The first 1,000 RVUs price at the entry band. For Cloud Pak for Watson AIOps the band runs at $480 to $620 per RVU. The customer that deploys 800 RVUs pays the entry band on every RVU.
RVUs 1,001 to 10,000 price at the middle band. The middle band runs 25 to 35 percent below the entry band. The customer that deploys 8,000 RVUs pays the entry band on the first 1,000 and the middle band on the next 7,000.
RVUs 10,001 to 100,000 price at the deep band. The deep band runs 50 to 65 percent below the entry band. The customer that deploys 80,000 RVUs pays across all three bands.
| Band | RVU range | Per RVU cost | Effective discount |
|---|---|---|---|
| Entry band | 1 to 1,000 | $480 to $620 | 0 percent |
| Middle band | 1,001 to 10,000 | $310 to $420 | 25 to 35 percent |
| Deep band | 10,001 to 100,000 | $170 to $260 | 50 to 65 percent |
| Mega band | 100,001 and above | $90 to $150 | 70 to 80 percent |
| Cloud Pak entitlement | Per CP entitlement | $1,200 to $1,900 per VPC | Cloud Pak conversion |
Six traps drive the bulk of the RVU audit quote. The customer that runs the inventory cleanup against each trap recovers 30 to 50 points off the opening number. The traps cluster around inventory drift, virtual host counting, and the renewal price escalator.
The deployed RVU count drifts above the licensed count between renewals. The drift compounds quarter on quarter. The cleanup motion runs against the ILMT report and the IBM Passport Advantage record.
Customers running RVU products on virtualised infrastructure without ILMT compliance pay the physical capacity rate. The cleanup motion runs the ILMT installation and the back dated reporting.
Cloud RVU ratios are not always documented to the customer. The customer that runs the IBM product on AWS or Azure without checking the cloud RVU ratio carries the higher count.
Customers that grow the distributed environment without raising the RVU count carry an audit exposure across the term. The cleanup motion runs the quarterly review.
IBM partition rules differ from Oracle partitioning. The IBM rule honours selected partitioning technologies as hard partitioning. The customer that runs the IBM workload on a hard partition platform captures the lower count.
The standard IBM Passport Advantage renewal carries a 4 to 8 percent uplift on the support and subscription line. The renewal cap clause holds the uplift at 0 to 3 percent across the first two renewals.
The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.
IBM Resource Value Unit is a managed resource metric used to license IBM products that scale with the volume of resources they manage rather than with users or processor cores.
RVU applies to IBM Tivoli Monitoring, NetCool, Cloud Pak for Watson AIOps, Instana, and selected components of QRadar and Guardium. Each product carries its own RVU conversion table that maps a managed unit to an RVU count.
IBM measures the RVU count through the IBM License Metric Tool. ILMT runs quarterly and produces a report that documents the count per product. Customers running ILMT in compliance count RVUs at the managed resource level. Customers without ILMT compliance count at the full physical capacity level. The ILMT compliance requirement gates the entire counting motion.
RVU pricing steps down across tiers. The first 1,000 RVUs price at the entry band. RVUs 1,001 to 10,000 price at the middle band. RVUs 10,001 to 100,000 price at the deep band. RVUs above 100,000 price at the mega band. The customer that deploys 80,000 RVUs pays across all three lower bands, not the entry band on every RVU.
Discount bands run 20 to 50 percent on the published RVU price. The actual band depends on the deployment scale, the product mix, and the customer alternative at the negotiation table. Customers with a documented Red Hat OpenShift Observability or open source alternative capture 10 to 20 points more than customers without an alternative.
IBM authorised cloud workloads count at the cloud RVU ratio. AWS, Azure, IBM Cloud, and Google Cloud each carry a different ratio inside the IBM Cloud RVU table. The customer that runs the IBM product on AWS without checking the cloud RVU ratio carries the higher count. The buyer side move documents the ratio per workload before signature.
Customers that lapse the ILMT installation between renewals lose Sub Capacity Reporting rights for the period of non compliance. The IBM audit treats the period as full physical capacity, which can double the RVU count across a single quarter. The remediation is the ILMT reinstall and back dated reporting where possible.
The standard IBM Passport Advantage renewal carries a 4 to 8 percent uplift on the support and subscription line. The renewal cap clause holds the uplift at 0 to 3 percent across the first two renewals. The clause sits inside the IBM Passport Advantage Advantage Agreement and runs across the term.
Redress runs the buyer side RVU engagement inside the Vendor Shield subscription and the Renewal Program. The work includes the ILMT compliance review, the inventory cleanup, the cloud RVU ratio documentation, the per product conversion check, the renewal cap, and the documented Red Hat or open source alternative. Engagements typically save 30 to 50 percent against the opening IBM quote.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the IBM service line, and the Software Spend Assessment.
Read the related IBM Audit Defence Guide, the IBM Knowledge Hub, the IBM services overview, the benchmarking service, and the Benchmark Program.
The companion playbook covers the IBM audit motion, the ILMT sub capacity rule, Passport Advantage mechanics, and the buyer side moves that hold the audit position and the renewal math.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
RVU is not a complicated metric. The complication is the conversion grid changing per product, the cloud ratios changing per cloud, and the ILMT compliance requirement that gates the whole count.
30 RVU engagements with median 44 percent saving against the opening IBM quote. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
