IBM Maximo Licensing Guide: Application Suite and Manage.

What Maximo is now.

IBM Maximo was, for two decades, a classic perpetual licence product with an Authorized User metric and an Asset metric. In 2021 IBM rebuilt the product as the Maximo Application Suite (MAS), a containerised application portfolio delivered on a Cloud Pak for Data foundation, licensed by AppPoint. The transition is one of the largest single product re licensing events in the IBM portfolio in the last decade.

The buyer side reality is that most Fortune 500 customers now hold a mix of classic Maximo entitlement and Maximo Application Suite entitlement, with a transition pathway in progress or pending. The licensing complexity sits in three places. The metric conversion from Authorized User to AppPoint. The Cloud Pak foundation underneath the application portfolio. And the deployment choice across IBM Cloud, customer self managed OpenShift, and other cloud providers.

Written from the buyer side by independent advisors. We are not an IBM Business Partner. For our position on independence, see why independence matters. For an introduction to the Cloud Pak conversion mechanics that underlie the MAS model, see Cloud Pak strategy.

The Application Suite model.

The Maximo Application Suite is a portfolio of applications grouped under a single brand. The applications include Maximo Manage (the core asset management workhorse), Maximo Health, Maximo Monitor, Maximo Predict, Maximo Visual Inspection, and Maximo Mobile. Each application has a published AppPoint consumption rate per user type. The customer holds a pool of AppPoints and consumes from the pool against the application usage.

The AppPoint pool is the central commercial construct. AppPoints are sold in tiers, with discount thresholds at typical Passport Advantage breakpoints. The pool is replenished by purchase or by S and S, and consumed by deployed users against the applications. The mathematics of the pool sizing is one of the most consequential buyer side decisions in the Maximo estate.

AppPoint and Authorized User.

The historical Maximo Authorized User metric is preserved as a legacy entitlement for customers with prior purchases. New growth is on AppPoint. The conversion mechanics from legacy Authorized User to AppPoint are documented but the conversion is rarely advantageous to the customer at the published rate.

The AppPoint rate by user type.

Three user types anchor the AppPoint consumption. A Maximo Manage Authorized User typically consumes ten AppPoints. A Maximo Manage Limited User typically consumes five AppPoints. A Maximo Mobile or Casual User typically consumes one AppPoint. The exact rate by application and user type is published in the IBM AppPoint table and changes by release. The buyer side discipline is to validate the current rate at every renewal.

The Authorized User to AppPoint conversion.

The conversion from classic Authorized User to AppPoint is rarely at parity. The buyer side discipline is to model the conversion as a discount negotiation rather than a metric translation. The conversion rate is the negotiation variable. See IBM discount structures for the broader benchmark frame.

Classic to MAS migration.

The classic Maximo product is on extended support. IBM has set successive end of support dates and pushed several. The current operational guidance is that classic Maximo is supported through the published end of support date and customers should plan the MAS migration on a multi year horizon, not a near term one.

The migration commercial pathway is the negotiation surface. IBM typically offers a trade up that converts classic entitlement to AppPoint at a published rate, with a multi year commitment in exchange for the conversion. The conversion is structurally similar to a Cloud Pak conversion and the buyer side discipline is similar. Model the forward economics, not the trade up math. See ELA vs Passport Advantage for the multi year structure considerations.

Deployment options.

The MAS Cloud Pak can be deployed in three configurations. IBM hosted (the Maximo Application Suite as a Service variant), customer self managed on OpenShift, and certified third party cloud provider environments. Each carries different operational and commercial implications.

IBM hosted.

The IBM hosted variant removes the operational burden of running OpenShift but caps the architectural flexibility. The commercial discount tier on the hosted variant is typically lower than the self managed variant. The trade off is the operational simplification.

Customer self managed on OpenShift.

The self managed variant requires a Red Hat OpenShift entitlement, which the Cloud Pak typically includes for the bounded MAS workloads. The architectural flexibility is the highest, the discount tier is typically the most favorable, and the operational burden is the highest. See Red Hat licensing expertise.

Other cloud provider environments.

The MAS Cloud Pak runs on certified hyperscaler OpenShift environments, including Red Hat OpenShift on AWS (ROSA) and Azure Red Hat OpenShift (ARO). The licence portability is the value. The buyer side discipline is to validate the certification status of the target environment at every release.

The four optimisation levers.

Four buyer side levers anchor the Maximo optimisation discipline.

Lever one. User type rationalisation.

The largest single lever is the rationalisation of users from Authorized User to Limited User to Mobile User. Each step down reduces the AppPoint consumption by half or more. Most Fortune 500 estates carry twenty to thirty percent of users at a higher tier than their actual functional need.

Lever two. Application portfolio rationalisation.

The MAS portfolio includes applications that may not be deployed. AppPoints consumed by deployed applications are the operational reality. AppPoints reserved against undeployed applications are a buyer side cost without operational return. The portfolio review identifies the rationalisation.

Lever three. Pool sizing.

The AppPoint pool is sized at purchase. Over sizing produces shelfware. Under sizing produces over consumption charges. The pool sizing discipline is to model the steady state consumption with a fifteen to twenty percent buffer and avoid both extremes.

Lever four. Deployment architecture.

The deployment architecture choice (hosted versus self managed versus hyperscaler) carries a five to fifteen percent discount tier differential at the AppPoint level. The architecture choice is therefore a buyer side commercial decision, not only an operational decision.

Maximo and audit.

The Maximo audit posture is shifting as the estate transitions from classic to MAS. The classic audit was an Authorized User and Asset audit, with named user counts and asset inventory the primary evidence. The MAS audit is an AppPoint consumption audit, with the consumption telemetry from the Cloud Pak Licence Service the primary evidence.

The Cloud Pak Licence Service produces consumption telemetry that is automatically available to IBM compliance. This shifts the audit dynamic. There is less room for buyer side data discipline disputes because the telemetry is the source of truth. The buyer side discipline shifts to the entitlement reconciliation and the methodology dispute. See audit defense guide and the self assessment guide.

Where to go next.

For the broader Cloud Pak strategy that underlies MAS, see IBM Cloud Pak strategy. For the container licensing rules that govern the MAS deployment, see IBM container licensing. For Red Hat licensing on the OpenShift base, see Red Hat licensing expertise. For the Cloud Pak expertise page, see Cloud Paks expertise. For the broader cost discipline that frames the Maximo conversation, see IBM Cost Optimization Guide. For the audit defense guide, see audit defense guide.

For a scoped advisory conversation about your Maximo estate, AppPoint sizing, or MAS migration commercial structure, the contact page is the entry point. A senior advisor responds within 24 hours.