IBM Planning Analytics licensing: per user, PVU, and Cloud Pak for Data.

Planning Analytics in the IBM analytics portfolio.

IBM Planning Analytics is the in memory multidimensional engine descended from the TM1 product line, originally developed by Applix, acquired by Cognos in 2007, and brought into IBM through the Cognos acquisition in 2008. Planning Analytics is the IBM analytics product most often deployed in finance, treasury, supply chain, and operational planning. It is rarely a small line item on a Fortune 500 IBM bill. Finance organisations use Planning Analytics for budget consolidation, forecasting, what if modelling, and management reporting. The licence count therefore tracks the working population of the finance and planning function, plus the integration points to source systems.

Planning Analytics licensing is more nuanced than most of the IBM portfolio because IBM has migrated the product through three metering models over the past fifteen years. Customers commonly hold a mixture of older Per Server, Authorized User, and modern Per User PVU models, often supplemented by Cloud Pak for Data entitlement that was added during a recent renewal. The buyer side discipline is to map the metric inventory precisely before any renewal conversation. For broader analytics context see the Cognos Licensing and SPSS Licensing articles. For the database side see Db2 Licensing.

As elsewhere on this site, we work as an independent firm. We are not an IBM Business Partner, reseller, or affiliate, and we hold no resell margin on any Planning Analytics licence.

Planning Analytics editions.

Planning Analytics is sold in two principal editions and one cloud variant.

Planning Analytics Local.

The on premise edition, deployed by the customer in the customer data centre. Licensed in Per User or PVU metrics depending on the customer history. The Per User model counts each named user with access to the Planning Analytics environment. The PVU model counts the processor capacity of the server hosting the Planning Analytics engine. Per User is the more recently sold metric for Planning Analytics Local; PVU continues for customers on long running contracts.

Planning Analytics with Watson.

A rebranded enhancement of Planning Analytics Local that adds AI assisted forecasting capabilities. Licensed on the same metric base as Planning Analytics Local. The capability set sits inside the same engine; the licence change is in entitlement, not architecture.

Planning Analytics as a Service.

The IBM Cloud hosted edition. Licensed per user with the cloud infrastructure included in the price. The buyer side discipline on Planning Analytics as a Service is to confirm that the cloud cost displaces the equivalent on premise cost and is not added on top of it. We have seen customers carry both the on premise PVU licence stream and the cloud per user licence stream simultaneously for a year or more during a poorly managed migration.

Planning Analytics on Cloud Pak for Data.

Planning Analytics is also available under Cloud Pak for Data Virtual Processor Core entitlement, with a conversion ratio that differs from Cognos and SPSS. The conversion offer typically arrives during a renewal as IBM proposes a consolidation across the analytics portfolio. See Cloud Pak Strategy.

Per User, PVU, and the metric question.

The metric question is the single most consequential decision in a Planning Analytics renewal. The Per User model is cheaper when the named user count is contained and stable; the PVU model is cheaper when the user count is large or growing fast. The break even point depends on the discount tier and the specific Per User and PVU price points, but as a rule of thumb the Per User model is preferable below roughly two hundred named users, and the PVU model is preferable above that threshold.

Customers on long running PVU contracts often hold more PVU entitlement than their current workload requires, because the PVU count was sized for a peak utilisation that no longer occurs. The harvest move at PVU contract renewal is to apply sub capacity through ILMT, confirm the actual peak utilisation, and drop excess PVU entitlement from the renewal. See Sub Capacity Explained and ILMT Guide.

Metric conversion is a contractual negotiation, not a one sided customer move. IBM will negotiate conversion at renewal if the customer brings a credible case. The buyer side preparation is to model the three year cost path under both metrics at current discount tiers and to present the model in the negotiation. See Renewal Strategy.

Source system integration and indirect access.

Planning Analytics rarely operates alone. It pulls source data from the general ledger, the ERP, the data warehouse, and the operational data stores. The licensing question that follows from this integration is indirect access: when a non Planning Analytics user accesses Planning Analytics data through a downstream application, does the access count against the Planning Analytics user metric, and does the source system data flowing into Planning Analytics create any reciprocal licence requirement against the source system.

For Planning Analytics the indirect access rule is generally narrow. A named user is one who is provisioned in the Planning Analytics environment, either directly or through a federated identity. A downstream BI consumer who reads a Planning Analytics derived report through Cognos or another front end is not a Planning Analytics named user. The buyer side discipline is to document this distinction explicitly in the entitlement inventory and refuse any IBM proposal that broadens the indirect access definition during a renewal or audit. See Cognos Licensing.

The reciprocal question, where Planning Analytics pulls data from an SAP or Oracle source, is a question for those vendors not for IBM. The buyer side discipline is to confirm that the source system contract permits the Planning Analytics data extraction.

Planning Analytics on Cloud Pak for Data.

The Cloud Pak for Data conversion offer arrives most often when the customer is renewing both Planning Analytics and one or two other analytics products. The IBM proposition is bundled simplification: a single Virtual Processor Core entitlement covers Planning Analytics, Cognos, SPSS, Watsonx.data, and the rest of the Cloud Pak for Data catalogue. The buyer side analysis is whether the bundle pays back.

Where the customer genuinely uses three or more Cloud Pak for Data products, the conversion typically pays back. Where the customer uses only Planning Analytics, the conversion usually does not pay back, because the VPC price per Planning Analytics workload exceeds the equivalent Per User or PVU cost. The buyer side discipline is to model both paths explicitly at three year total cost of ownership.

Where Cloud Pak for Data conversion does pay back, the buyer side negotiation moves are to lock the conversion ratio for the term, to retain ownership of the perpetual entitlement on the original metric so the customer can revert if needed, and to align the Cloud Pak for Data anniversary to the broader Passport Advantage anniversary. See ELA vs Passport Advantage and Multi Year Strategy.

Annual Planning Analytics harvest.

Planning Analytics harvest is an annual discipline. The active user count moves every year with finance organisation churn. The PVU peak moves with workload patterns. The S and S stream rewards the customer who right sizes both at each anniversary.

1. Pull the active user list from the Planning Analytics directory. Compare to the entitled user count under the Per User metric.
2. Pull the ILMT report for the past four quarters on any PVU licensed Planning Analytics environment. Identify the actual peak.
3. Reconcile entitlement to active users and to actual peak.
4. Identify excess Per User entitlement and excess PVU entitlement.
5. Decide which to drop at the next anniversary. Drop S and S on the excess.
6. Document the harvest decision in the entitlement inventory.

This routine is consistent with the harvest method we apply across the IBM portfolio. See IBM Shelfware Recovery for the general method and the harvesting expertise page for the engagement structure.

Planning Analytics at renewal.

Planning Analytics renewal sits inside the Passport Advantage anniversary. The buyer side moves at renewal are the harvest of excess entitlement, the metric conversion to the cheaper of Per User or PVU at the current user count, the resistance against any Cloud Pak for Data conversion that does not pay back, and the alignment of any Planning Analytics as a Service stream to the on premise retirement schedule.

On a multi year commitment, Planning Analytics sits with Cognos, SPSS, and the rest of the analytics portfolio. The buyer side discipline is to ensure the multi year commitment is sized to the harvest position rather than to a projection that has not been validated. The most common error in multi year Planning Analytics is to commit to a Per User count that anticipates a planning system rollout that never fully lands. See Multi Year Strategy.

Discount tier on Planning Analytics is generally consistent with the broader Cognos and analytics discount tier. The buyer side negotiation is therefore at the portfolio level rather than at the Planning Analytics level. See IBM Discount Structures.

Planning Analytics conclusion and next steps.

Planning Analytics is one of the higher value IBM analytics products inside Fortune 500 estates, with a metric model that rewards disciplined harvest. Hold the right metric, harvest the user count and PVU peak annually, refuse Cloud Pak for Data conversions that do not pay back, and align the renewal cycle to the broader Passport Advantage anniversary.

If you would like a buyer side advisor on your Planning Analytics estate, see the License Consulting service page or contact us through the contact page.