IBM Maximo Playbook

IBM Maximo Licensing: Authorized Users, AppPoints, and Suite Mechanics

How IBM Maximo licensing actually works in 2026. Authorized User counts, AppPoint conversions, Maximo Application Suite mechanics, and the audit traps that catch enterprises every cycle.

Portrait of Morten Andersen
Written byMorten AndersenCo Founder · ex IBM, ex Oracle
Read Time20 Minutes
Last UpdatedMay 2026

Now that you have the framework

Apply it to your IBM situation.

25 minute call with our IBM practice lead. We will walk through your specific renewal, audit, or contract and tell you what we would do next. No follow up sales pressure unless you ask for one.

HomeIBM HubWhite PapersIBM Maximo Licensing: Authorized Users, AppPoints, and Suite Mechanics
The Short Version

If you read nothing else

Bottom Line

Maximo Application Suite consolidates classic Maximo modules into AppPoints, but the math is opaque. Most buyers over commit on AppPoints because the conversion ratios favor IBM. The playbook is to inventory user counts, pre model the AppPoint pool, and negotiate the conversion before signing the suite.

Key Takeaways

Five conclusions

AppPoints are not seats. AppPoints are a pooled currency. Every module consumes a different ratio. Without modeling, you over commit.
Authorized User is strict. An Authorized User is named and counted, not concurrent. Contractors and shared logins both count.
Suite migration is one way. Once you migrate to MAS, you cannot revert. Negotiate the AppPoint floor before migration.
Audit findings inflate. IBM audits Maximo by inspecting user tables. Mobile access, contractor logins, and shared accounts inflate findings.
Renewal is the leverage. AppPoint renewal is the negotiation moment. Right size every 12 months. Refuse multi year over commits.
Recommendations by Role

What to do this quarter

Chief Information Officer
  1. Inventory all Maximo users, including mobile and contractor access
  2. Pre model the AppPoint pool against actual module use
  3. Refuse multi year AppPoint commits without ramp clauses
Procurement
  1. Negotiate the AppPoint conversion ratio before MAS migration
  2. Cap annual price uplift in the suite contract
  3. Document the floor in the order form, not the master agreement
Maximo Owner
  1. Run a quarterly user audit on every active module
  2. Disable inactive accounts before the renewal
  3. Document mobile and EAM Mobile users explicitly
The Framework

Eight ideas

1. Authorized User Mechanics

An Authorized User is a named individual with access to Maximo. Concurrent licensing does not apply. Contractors, vendors, and shared accounts all count if they have access. Audit posture is strict.

2. AppPoint Currency

AppPoint is a pooled currency consumed by modules at module specific rates. Asset Management consumes one rate, Field Service another. Build the consumption model before committing.

3. Suite Migration

Migration to Maximo Application Suite is one way. Classic Maximo licenses convert to AppPoints at a published ratio. The ratio favors IBM if you have many modules. Model carefully.

4. Module Consumption Rates

Each Maximo module consumes AppPoints at a different rate. Asset Management, Health, Predict, and Manage all have separate rates. Confirm the rate table at signature.

5. Mobile and EAM Mobile

Mobile access is licensed separately or as part of the suite. Confirm what is included. Mobile users are a frequent audit finding.

6. Audit Posture

IBM audits Maximo by extracting user tables and reconciling to entitlements. Contractors, ex employees, and shared accounts inflate findings. Run an internal audit before the external one.

7. Renewal Leverage

AppPoint renewals are the negotiation. Right size the pool, push for ramp pricing, and refuse multi year commits without floors. The 12 month review is the lever.

8. Multi Vendor Strategy

Maximo competes with SAP EAM, Infor EAM, and others. Keep alternatives live in the procurement pipeline. The threat of replacement is real and material.

Reference

Acronyms

MASMaximo Application Suite
EAMEnterprise Asset Management
AUAuthorized User
APAppPoint
PVUProcessor Value Unit
ILMTIBM License Metric Tool
Methodology & Sources

This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.

Portrait of Morten Andersen
About the Author

Morten Andersen

Co Founder, Redress Compliance
Connect on LinkedIn →
Vendor relationship up for review?
Request a Renewal Review
Related

Continue

Skyscraper
Ready?

Your next renewal is an opportunity.

Vendor management, contract negotiation, audit defense, renewal strategy. One firm. Eleven practices.

Buyer Side Newsletter

Once a month. Vendor moves, audit patterns, renewal alerts. For IT and procurement leaders.