IBM Maximo AppPoints: Size the Pool, Not the Headcount
Maximo Application Suite prices on a shared AppPoints pool, and the same person costs 5, 10, or 15 points depending on the tier you assign. The pool you buy sets the bill until renewal.
Prepared by Redress Compliance · June 2026 · Representative Maximo estate (benchmark scenario, not a quote)
Executive Summary
Maximo Application Suite (MAS) replaced the old per user Maximo licenses with AppPoints, a single pool of points that user entitlements and add ons draw from. The point cost is set by the user tier, not the headcount. A Limited user draws 5 points, a Base user 10, and a Premium user 15, while a Self Service requester draws 0.
Two mechanics decide whether the pool is right sized or bloated. The first is Authorized versus Concurrent. An Authorized user reserves points permanently, even when never logged in. A Concurrent user checks points out only during an active session and returns them at logout, so you size to peak concurrency rather than the named list.
The second is the tier gate. The application sets the minimum tier, not the role. Switch on one Premium gated application such as Maximo Predict, and every user of it is pulled to 15 points, three times a Limited user, regardless of how lightly they use it.
This paper covers how users are measured, how the pool works and how to size it, how MAS differs from classic Maximo at the contract level, the audit findings that cost the most, and a worked renewal model. In the benchmark estate, concurrent default plus tier correction cut the pool from 5,800 to 3,350 AppPoints, a 42 percent reduction.
How are Maximo users measured under AppPoints?
Maximo users are measured by the points their tier draws from the pool, and by whether that draw is Authorized or Concurrent. The headline point price is the small part. The allocation method is where the money moves.
IBM sets four user types in the suite, documented on the Maximo Application Suite licensing pages. Each draws a fixed number of AppPoints when it consumes an application.
| User tier | AppPoints | Typical applications and roles |
|---|---|---|
| Premium | 15 | Predict, Visual Inspection, full Industry Solutions, and power roles needing every Manage module. |
| Base | 10 | Manage core EAM, Health, Safety, and IT for planners, supervisors and managers. |
| Limited | 5 | Monitor, Mobile, and a small number of Manage modules for technicians and light users. |
| Self Service | 0 | Service requesters who raise and track tickets only, with no AppPoint draw. |
What is the difference between Authorized and Concurrent?
Authorized reserves points permanently; Concurrent shares them across a session ceiling. An Authorized user holds the points whether logged in or not. A Concurrent user checks points out at login and returns them at logout, per IBM's AppPoints usage documentation.
The first non obvious mechanic follows from that. Concurrent licensing is sized to peak simultaneous sessions, not to the named headcount. A shift based technician estate of 500 people may only ever have 150 logged in at once, so concurrent buys the pool for 150, not 500.
Where is the concurrent ceiling a risk?
The second mechanic is the session ceiling. If more users try to log in at once than the pool supports, MAS denies the session. Size concurrent to the genuine peak with headroom, or a busy Monday morning becomes a help desk queue.
How does the AppPoints pool actually work?
The pool is one shared entitlement that every user tier and every add on draws from. You buy a number of AppPoints, and consumption against that number is what IBM measures. The point cost climbs steeply with the tier.
AppPoint values per IBM Maximo Application Suite licensing documentation. Source line below.
How does the tier gate inflate the pool?
The third non obvious mechanic is that the application gates the tier, not the job title. Limited tier reaches Monitor, Mobile and a handful of Manage modules. Base reaches Manage, Health, Safety and IT. Premium is required for Predict, Visual Inspection and full Industry Solutions.
Switch on one Premium gated application for a group of light users, and each one jumps from 5 or 10 points to 15. A pilot of Predict for 40 technicians can add 600 points to the pool before a single work order changes.
Which add ons draw from the same pool?
Industry Solutions and certain add ons consume AppPoints from the same shared pool, so enabling them quietly raises consumption. Confirm the point draw of every application before you switch it on, not after the usage report shows the overage.
How does Maximo Application Suite differ from classic Maximo at the contract level?
Classic Maximo licensed named Authorized and Concurrent users per product. MAS collapses that into one AppPoints pool spanning Manage, Monitor, Health, Predict, Visual Inspection and Assist. The contract unit changed from users to points, and the conversion is where migrations over provision.
| Dimension | Classic Maximo | Maximo Application Suite |
|---|---|---|
| License unit | Named Authorized or Concurrent users per product. | Shared AppPoints pool across all suite applications. |
| User cost | Flat per user by product. | 5, 10 or 15 points by tier, plus the tier gate. |
| Flexibility | Locked to the product purchased. | Points re flow as you reassign tiers and applications. |
| Migration risk | Known headcount. | Conversion ratio can over size the pool at cutover. |
The fourth mechanic is the migration conversion. Classic user entitlements convert to AppPoints at a defined ratio, and the safe looking move is to convert the full named list. That carries idle accounts, leavers and over tiered users straight into the new pool, locking the bloat in for the term.
Verify the suite structure and the application set on the IBM Maximo product page and confirm the entitlement terms in the IBM license information documents before you sign the conversion.
Which Maximo audit findings cost the most?
Maximo overages come from how access was assigned, not from the point price. MAS tracks AppPoint consumption against the entitled pool, so the audit question is simple: did peak consumption exceed what you bought. Four patterns drive most of the gap.
| Finding | Buyer risk | Buyer move |
|---|---|---|
| Tier mismatch | Light users on Premium or Base for one gated app. | Match the tier to the lowest application each user truly needs. |
| All Authorized | Points reserved 24/7 for shift and seasonal staff. | Move intermittent users to Concurrent, sized to peak. |
| Contractor accounts | Temporary and shared logins left at full tier. | Time box contractor access and reclaim points at offboarding. |
| Non production | Dev, test and sandbox drawing from the production pool. | Classify environments and license non production correctly. |
Mobile access is the quiet one. Field technicians on the Maximo mobile apps are often provisioned at Base when Limited covers their work, so a 500 strong crew can carry an extra 2,500 points for an entitlement they never use. Shared and generic logins compound it, because the audit counts the highest tier ever assigned to the account.
Across the Maximo reviews we ran in 2024 to 2025, the AppPoints pool typically sat a quarter to two fifths above measured application and concurrency use before correction.
Requesters who only raise and track tickets belong on Self Service at zero points. Many estates license them as Limited or Base out of habit, paying for nothing.
How do you size the pool and model a Maximo renewal?
You size the pool to measured application use and peak concurrency, then model the renewal from that floor. Measure first, convert second, negotiate third. The order matters, because the pool you commit is the cost until the next renewal.
Where the common advice on Maximo licensing is wrong
The standard reseller advice is to buy a generous AppPoints pool up front and license everyone Authorized so no team is ever blocked. We disagree. In the Maximo reviews Morten Andersen ran in 2024 to 2025, that posture sat 25 to 40 percent above real use, while tier gates and Authorized reservation stacked cost on top. The buyer side move is to default to Concurrent, size the pool to peak concurrency, and match every user to the lowest tier their applications require before you commit.
The worked estate below shows the gap. A representative manufacturer runs 1,000 named Maximo users. Licensing every user Authorized at their provisioned tier needs 5,800 AppPoints. Correcting tiers and defaulting shift users to Concurrent at peak brings it to 3,350.
| User tier | Named users | All Authorized AppPoints | Right sized AppPoints |
|---|---|---|---|
| Premium | 60 | 900 | 600 |
| Base | 240 | 2,400 | 2,000 |
| Limited | 500 | 2,500 | 750 |
| Self Service | 200 | 0 | 0 |
| Total | 1,000 | 5,800 | 3,350 |
Benchmark scenario, not a quote. Right sized column reflects tier correction on Premium and Base plus concurrent peak sizing on Limited. Source line below.
Benchmark scenario, not a quote. 5,800 and 3,350 AppPoints from the table above.
At an illustrative 450 USD per AppPoint per year, that pool difference is real money. The cost line tracks the points exactly.
| Line | All Authorized | Right sized |
|---|---|---|
| AppPoints | 5,800 | 3,350 |
| Annual cost at 450 USD per point | $2,610,000 | $1,507,500 |
| Annual saving | $1,102,500, a 42 percent reduction | |
Benchmark scenario, not a quote. 450 USD per AppPoint is illustrative, used to convert the point gap to cost.
What is the 90 day renewal model?
Run the renewal as a measured sprint, not a reorder. Three phases turn usage data into the entitlement you actually buy.
Measure use
Pull AppPoint consumption by user and application, map which applications each team opens, and flag every Premium gated draw.
Reclassify
Move intermittent users to Concurrent, drop over tiered users, send requesters to Self Service, and remove leavers and idle accounts.
Size and negotiate
Set the pool to peak concurrency with headroom, model the renewal from that floor, and benchmark the point rate before you sign.
The cheapest Maximo entitlement is the AppPoints pool sized to the tiers your teams actually need and the sessions they actually run.
Our recommendation
Treat the AppPoints pool as a measured entitlement and size it from data, not from the named list. Two moves protect the most money for the least effort.
- Default to Concurrent and correct the tier. Reserve Authorized for steady daily users, put shift and seasonal staff on Concurrent at peak, and match each user to the lowest application tier they need.
- Model the renewal before you convert. Measure consumption first, then convert, so idle accounts and over tiered users do not migrate into the new pool and lock in for the term.
We are glad to tie a meaningful part of the fee to delivered value.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. The worked estate is a representative benchmark scenario, not a quote, sized for illustration at 450 USD per AppPoint per year.
