IBM Maximo Application Suite replaced per product licensing with a shared pool of AppPoints. The pool flexes across apps and users, which sounds simple and prices in ways that surprise buyers at renewal.
IBM Maximo Application Suite licenses a shared pool of AppPoints that flexes across apps and users. This guide explains the model, the OpenShift cost, and the buyer side controls.
Maximo Application Suite licenses a single pool of AppPoints that any application in the suite can draw from. Instead of buying each product, you buy capacity and allocate it across apps and users as needed.
The flexibility is real. The published Maximo Application Suite lets a buyer shift entitlement between work management, monitoring, and prediction without separate purchases. The catch is that apps consume AppPoints at very different rates.
AppPoints are consumed by concurrent use within the Maximo Application Suite licensing rules. Sizing on total headcount rather than peak concurrency is the most common way buyers overbuy.
Maximo Application Suite runs on Red Hat OpenShift. That platform requirement adds infrastructure and licensing cost that the legacy Maximo business case usually did not include.
Red Hat OpenShift can be bought standalone or inside a Cloud Pak. Either way, budget the platform alongside the AppPoints, not after.
Legacy Maximo versus Application Suite sizing
| Dimension | Legacy Maximo | Application Suite |
|---|---|---|
| License unit | Per product, per user | Shared AppPoints pool |
| Flexibility | Fixed per product | Flexes across apps |
| Platform | Traditional stack | Red Hat OpenShift |
| Sizing risk | Shelfware per product | Oversized pool |
IBM offers conversion paths from legacy Maximo entitlements to AppPoints. Whether the trade is fair depends entirely on your app mix and how IBM values your existing licenses.
The ratio of legacy entitlement to AppPoints is not fixed in stone. Model it against your real usage before accepting the IBM proposed pool.
Confirm what you actually own in Passport Advantage before any conversion, so the trade starts from your full entitlement.
The standard advice is that AppPoints always save money because one flexible pool beats many fixed product licenses. We disagree. In the Maximo estates we have reviewed, the pool was routinely sized to named users and stacked with premium apps that drain AppPoints fast, so the flexible model cost more than a disciplined legacy footprint would have. The buyer side move is to measure concurrent usage by app, size the pool to that evidence, and treat premium apps as deliberate additions rather than defaults. Flexibility only saves money when it is sized to truth.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
AppPoints do not make Maximo cheaper. Measurement makes Maximo cheaper. The pool is only as efficient as the concurrency data behind it.
Three controls do most of the work.
Size the AppPoint pool to peak concurrent use by app, not to total headcount.
Treat Monitor, Health, and Predict as deliberate additions and track their AppPoint draw separately.
Include OpenShift and platform cost in the business case from the start.
AppPoints are a shared pool of license capacity that any application in Maximo Application Suite can draw from. Instead of buying each product, you buy capacity and allocate it across apps and users.
Different apps and user types consume at different rates. Base work management draws the least, while premium apps such as Monitor and Predict draw far more, and authoring users consume more than limited users.
Yes. The suite runs on Red Hat OpenShift, which adds infrastructure and platform cost that the legacy Maximo business case usually did not include.
Size it to peak concurrent use by application, not to total headcount. Sizing on headcount is the most common reason buyers overbuy AppPoints.
It depends on your app mix and the conversion ratio IBM offers. The ratio is negotiable, so model it against real usage before accepting the proposed pool.
Usually because the pool was sized to headcount, premium apps were enabled by default, and OpenShift cost was added. Each of those is controllable with measurement.
Premium apps such as Monitor, Health, and Predict, which can draw several times the AppPoints of the base work management app per use.
Right sizing the AppPoint pool against measured concurrency. Knowing exactly how many users hit each app at peak is what keeps the pool from being oversized.
AppPoints sizing, OpenShift cost, legacy Maximo conversion math, ILMT posture, and the buyer side moves across the IBM Maximo estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The Maximo suite sells flexibility. Flexibility is only a saving when it is sized to measured concurrency. Otherwise it is a bigger pool to pay for.
