User classification alone shifted the AppPoint requirement by 20 to 30 percent, before any discount was discussed
MAS is marketed as a flexible bundle and priced through a conversion ratio. The ratio is where the deal is decided, and the published one is rarely the negotiated one.
Prepared by Redress Compliance · August 16, 2026 · IBM advisory. More than 30 Maximo Application Suite conversions, 2022 to 2025.
Executive summary
Classification moved the AppPoint requirement 20 to 30 percent on its own. Limited, base, and premium user classes carry different weights, and mapping people to the lowest class that works is the single largest lever in the conversion.
Scope and reallocation cut a further 15 to 25 percent. AppPoints can be reallocated across MAS applications only if the contract allows it, so the reallocation clause is a commercial term rather than a product feature.
Conversion offers opened 15 to 30 percent above a defensible like for like baseline. The published legacy to AppPoint conversion ratio is rarely the negotiated ratio, and treating it as fixed concedes the largest number in the deal.
Size the pool against third year deployment, not year one. A pool sized to initial rollout trues up as the suite spreads, and the true up prices at a worse ratio than the conversion did.
How AppPoints actually price
MAS replaces legacy per application Maximo licensing with a single AppPoints pool. The pool is drawn against by users, and users are not equal.
| Element | How it works | Where the lever sits |
|---|---|---|
| User classification | Limited, base, and premium classes draw different AppPoints | Largest single lever, worth 20 to 30 percent |
| Application scope | Which MAS applications are in the entitlement | Scope discipline, worth 15 to 25 percent with reallocation |
| Reallocation | Moving AppPoints between applications | Permitted only if the contract says so |
| Conversion ratio | Legacy entitlement translated into AppPoints | Published ratio is rarely the negotiated one |
| Audit basis | ILMT data against contracted AppPoint entitlement | Instrumentation, as everywhere else on IBM |
Reallocation is the clause that decides whether the pool is actually flexible. MAS is marketed as a flexible bundle, and the flexibility is contractual rather than technical. AppPoints move between applications only where the agreement permits it, so a pool that looks fungible in the product can be fixed in the paper. Establish the reallocation right explicitly, because without it the pool has to be sized correctly per application on day one and cannot be rebalanced as adoption shifts.
The ratio decides the deal, and it arrives looking like a constant
Across more than thirty Maximo Application Suite conversions, the AppPoints conversion ratio rather than the headline discount decided the outcome. That is worth stating first because the ratio does not present as negotiable. It arrives as a published figure translating legacy entitlement into AppPoints, carrying the appearance of a technical constant rather than a commercial position. Conversion offers landed 15 to 30 percent above a defensible like for like baseline in the engagements run, and the gap sat almost entirely in that ratio.
Underneath it, classification is the lever with the widest reach. Limited, base, and premium user classes draw different AppPoints, and the default mapping is generous to IBM because it is produced from role titles rather than from what people actually do in the system. Reclassifying against real usage moved the requirement 20 to 30 percent on its own, before any discount conversation. That is a larger number than most negotiated discounts on this product, obtained by measuring rather than by arguing, and it is available to any buyer willing to look at the usage data before agreeing the count.
Scope and reallocation then compound it by a further 15 to 25 percent, and they are linked. Narrowing application scope reduces the pool, but only if you can also reallocate as adoption changes, because a narrow pool without reallocation rights becomes a true up trigger the moment usage shifts between applications. That is why the reallocation clause is a commercial term rather than a product feature, and why negotiating scope without it produces a saving that reverses at the first true up.
Two timing disciplines close the position. Size the pool against third year deployment rather than year one, because MAS spreads through an asset intensive estate over time and a pool sized to initial rollout trues up at a worse ratio than the conversion achieved. And engage 12 to 18 months before the renewal or conversion event, since classification analysis and scope modelling both require usage data that takes months to assemble and cannot be produced inside a negotiation window. The wider IBM posture sits in the vendor management playbook, and the library in the IBM practice.
- Your agreements decoded into plain English before the auditor interprets them for you
- Entitlements mapped against measured usage, classification by classification
- A defensible position paper generated in minutes, not weeks
The levers, in order of size
- Reclassify users against real system usage, not role titles, since limited, base, and premium draw different AppPoints and classification alone moved the requirement 20 to 30 percent.
- Negotiate the conversion ratio, because the published legacy to AppPoint figure is rarely the negotiated one and it carries the largest single number in the deal.
- Narrow application scope and secure reallocation together, since scope without reallocation converts a saving into a true up trigger.
- Size the pool against third year deployment, because MAS spreads over time and a year one pool trues up at a worse ratio than the conversion.
- Confirm the ILMT position, since IBM audits Maximo using ILMT data against contracted AppPoint entitlement, exactly as it does elsewhere.
- Start 12 to 18 months out, because the usage data behind classification and scope cannot be assembled inside a negotiation window.
What the MAS conversions showed, 2022 to 2025
Across more than 30 Maximo Application Suite conversions, the conversion ratio rather than the headline discount decided the outcome:
How far user classification alone shifted the AppPoint requirement, before any discount was discussed.
Further reduction from application scope discipline negotiated together with the reallocation clause.
Conversion offers landed 15 to 30 percent above a defensible like for like baseline. IBM markets MAS as a flexible bundle, and the flexibility is contractual: AppPoints reallocate across applications only where the agreement permits it.
IBM audits Maximo using ILMT data against the contracted AppPoint entitlement, which puts the same instrumentation discipline behind this product as behind the rest of the estate.
Your first five moves
- Pull system usage per user and reclassify against what people actually do rather than against role titles.
- Build a defensible like for like baseline before the conversion offer arrives, since offers open 15 to 30 percent above one.
- Treat the conversion ratio as negotiable, because it presents as a constant and carries the largest number in the deal.
- Negotiate scope and reallocation as a pair, never scope alone.
- Size the pool to third year deployment and start 12 to 18 months out. The IBM practice runs the classification with you.
Frequently asked questions
What is the AppPoints metric?
The single pool metric replacing legacy per application Maximo licensing in Maximo Application Suite. Users draw against the pool at different weights depending on whether they are classified as limited, base, or premium.
What is the largest lever?
User classification, worth 20 to 30 percent of the AppPoint requirement on its own. The default mapping is produced from role titles rather than from system usage, which is generous to IBM and correctable with data you already hold.
Is the conversion ratio fixed?
No, though it presents that way. The published legacy to AppPoint ratio is rarely the negotiated one, and it carries the largest single number in the deal. Conversion offers landed 15 to 30 percent above a defensible like for like baseline.
Can AppPoints be moved between applications?
Only if the contract allows it. MAS is marketed as a flexible bundle and the flexibility is contractual rather than technical, so the reallocation right has to be negotiated explicitly rather than assumed from the product.
Why negotiate scope and reallocation together?
Because a narrowed pool without reallocation rights becomes a true up trigger the moment usage shifts between applications. Scope discipline alone produces a saving that reverses at the first true up.
How should the pool be sized?
Against third year deployment rather than year one. MAS spreads through an asset intensive estate over time, and a pool sized to initial rollout trues up at a worse ratio than the conversion itself achieved.
How does IBM audit Maximo?
Using ILMT data against the contracted AppPoint entitlement, which puts the same instrumentation discipline behind MAS as behind PVU licensed products elsewhere in the estate.
When should we start?
12 to 18 months before the renewal or conversion event. Classification analysis and scope modelling both depend on usage data that takes months to assemble and cannot be produced inside a negotiation window.
Do the levers stack?
Yes. Classification moved the requirement 20 to 30 percent and scope with reallocation cut a further 15 to 25, and both operate on the quantity before any discount is applied to it.
Is the headline discount worth chasing?
Less than the ratio and the classification. The conversion ratio decided the outcome across the engagements run, which means a strong discount applied to an inflated AppPoint requirement still produces a poor result.
