Maximo licensing models in 2026: AppPoints, perpetual, subscription and MAS

If you are shortlisting an IBM Maximo or Maximo Application Suite (MAS) programme, licensing is where optimistic business cases quietly come apart. MAS is not a simple version bump: it is a suite of applications (including Maximo Manage, which is what most people still mean by core Maximo) with a pooled entitlement model called AppPoints for current commercial offers, while many estates still sit on older perpetual or subscription terms written for a different product shape. The honest job for procurement and architecture is to separate what IBM’s contract and Licence Information actually require from what your integrator assumes you already bought.

This guide summarises how those models differ, what to evaluate with your legal and SAM teams, and where classic Maximo 7.6 still fits in the picture.

Why this matters

Licensing errors show up late. They surface when you turn on an industry solution, add a second non-production environment, expand IoT into Maximo Monitor, or discover that “read-only” interfaces still count as use under your agreement. IBM’s published licensing guidance for MAS states that your licence agreement and Licence Information are the authoritative source, and that the guidance document is supplementary. That single sentence should reset how you run diligence: spreadsheets from a sales deck are not the contract.

Commercially, the wrong model forces either scope cuts at go-live or a mid-term true-up that the programme board did not reserve budget for. Operationally, MAS runs on Red Hat OpenShift (on premises or with a cloud provider). That platform choice is related to, but not the same as, application entitlements: you need a coherent picture of both.

Technically, remember that MAS is a suite. Manage, Health, Monitor, Predict, Assist, and Visual Inspection are separate licensed applications within the suite, not interchangeable features inside a single SKU. Turning a module on can change user tiering, install counts, and indirect use, all of which feed back into AppPoints or predecessor metrics.

Governance matters as much as arithmetic. Programme directors should expect a standing agenda item that joins enterprise architecture, SAM, cyber security, and the IBM account team. Without that forum, projects optimistically “assume AppPoints will sort themselves out at hypercare”, which is rarely how IBM licence reviews read the estate.

What to actually evaluate

Work through the items below in order. Each line is a decision or evidence request, not a recommendation to buy more.

1. Establish which product generation you are discussing

Classic Maximo 7.6.x and earlier ran on traditional application servers. MAS requires OpenShift. If your estate is still on 7.6, your near-term choice is often renew and stabilise, move to MAS, or run a controlled overlap during migration. Those paths have different licence and support implications; IBM has been shifting investment from classic Maximo toward MAS, and classic 7.6 is in extended support territory with no hard end date promised in public summaries you should rely on for planning. Treat dates as a question for IBM, not an assumption in your business case.

2. For MAS, start from AppPoints as a pooled currency, then map users and installs

For current MAS offers, IBM describes AppPoints as credits that pay for combinations of users, access tiers, installs, and (for some capabilities) operational consumption. Customer-managed MAS and MAS as a Service both use AppPoints, but IBM explicitly documents that the AppPoints model differs between customer-managed MAS 9.0 and earlier and MAS as a Service. Your shortlist should therefore ask for two things in writing: which deployment pattern is in scope, and which IBM publication was used for the sizing worksheet.

3. Distinguish concurrent and authorised user logic

IBM’s MAS licensing guidance defines concurrent users (peak simultaneous humans using the program) and authorised users (named individuals, each needing a dedicated entitlement). Hybrid “access for concurrent and authorised users” is also described for some configurations. This matters because multiplexing and shared service accounts are common in asset-intensive estates; IBM’s definitions are strict about indirect access. Run your intended integration and batch patterns past the definitions, not past informal project nicknames.

4. Treat “Limited”, “Base”, and “Premium” as entitlement tiers, not marketing labels

The published MAS 9.1 licensing guidance ties AppPoints to application user tiers (Limited, Base, Premium) that unlock different combinations of Manage modules, industry solutions, add-ons, and suite applications. If your roadmap includes an industry solution or an add-on such as Scheduler at scale, your tier assumptions in year one may not hold in year three. Size for the roadmap module list, not only the go-live footprint.

5. Account for install-based charges where IBM documents them

Several components and connectors are described with per-install AppPoint costs in IBM’s licensing appendix and guidance. Examples called out in the official text include certain connectors, Visual Inspection installs, Spatial, Optimizer variants, and Real Estate and Facilities reserve models. If your architecture spreads environments across production, disaster recovery, and multiple test factories, install-type maths can dominate the conversation even when user counts look modest.

6. For SaaS, read the SaaS-specific AppPoints note end to end

IBM states that when you subscribe to MAS as a Service, you purchase AppPoints that are deducted when the suite is installed and when suite applications are deployed, and that costs vary by application and sometimes by operational tasks (for example Monitor KPI and I/O concepts, or Predict model and prediction concepts, as described in IBM’s SaaS AppPoints topic). SaaS also introduces minimum term language on IBM’s public pricing FAQ (for example, subscription term commitments described there). Your legal team should reconcile that FAQ with your order form.

7. Perpetual versus subscription in plain language

Outside marketing, “perpetual” usually means you acquired a perpetual entitlement under IBM’s International Program License Agreement style terms, with ongoing support and subscription priced separately through Passport Advantage style programmes. “Subscription” for MAS commonly means term-based rights to current versions and IBM support for the paid term. The economic comparison is cash timing, true-up mechanics, certification burden, and exit cost, not which label sounds cheaper in year one.

8. OpenShift cores for customer-managed MAS

IBM’s MAS licensing guidance states that deployments on OpenShift must have sufficient entitlement for the MAS cores used. Platform sizing workshops should produce a core count that your IBM or partner quote can map to licence language, not only to infrastructure cost.

9. Evidence pack your partner should be able to produce

Ask for a reconciled workbook that lists: named applications in scope, user types and counts by tier, production and non-production instances, planned industry solutions and add-ons, integration interfaces with a note on indirect access risk, growth assumptions by year, and the IBM publication date used for ratios. Then ask your software asset management owner to sign alignment with the Licence Information document for your specific part numbers.

10. Generative AI and token-style consumption

IBM’s published MAS 9.1 licensing material describes a Maximo AI Service measured with content tokens that convert to AppPoints at a published ratio. If your roadmap includes assistant-style features, treat token growth like you treat storage growth: model a low, central, and high case, and stress-test what happens if adoption spikes after a successful pilot. This is not a reason to avoid the capability; it is a reason to put it in the same workbook as Manage users.

11. Service-provider and multi-tenant patterns

If you deliver asset management as a commercial service to third parties, IBM’s licensing guidance includes additional terms and specific product rules (for example, references to Maximo Service Provider and waiver processes described in IBM’s text). Outsourcers and joint ventures sometimes discover this late because the internal template assumed a single-company estate. Flag revenue-generating managed service models early in shortlisting so legal review runs in parallel with technical design.

12. Contract mechanics beyond the unit price

Subscription paperwork usually bundles true-up cadence, currency, indexation, renewal notice windows, and support severity. Perpetual estates add support renewal co-termination risk across Passport Advantage line items. Procurement should read IBM’s public pricing page alongside the order form: IBM states that MAS is offered as client-managed software or SaaS, explains AppPoints at a high level, and notes that indicative prices vary by country and exclude taxes. Use that page to sanity-check scope, not to replace a signed quote.

Common mistakes

Sizing only full-time maintenance users. Limited and self-service patterns exist for a reason. If you size everyone as Premium concurrent because it was easier in the workshop, you will overbuy or, worse, underbuy and block go-live when tier checks fail.

Treating non-production as “free”. IBM publishes specific guidance on non-production instances for MAS. Clone counts, refresh frequency, and whether test teams perform realistic integration tests all affect whether those environments need explicit entitlement.

Ignoring indirect access. Enterprise integrations (ERP, SCADA historians, mobile middleware) can cause user actions to touch Maximo through a small number of technical accounts. IBM’s licensing guidance includes sections on indirect access scenarios. That language exists because auditors read it.

Confusing MAS suite activation with “turning on a feature flag”. Health, Monitor, Predict, Assist, and Visual Inspection are separate applications within the suite with their own entitlement patterns. A successful Manage go-live does not automatically mean you have the right to turn on Predict for a pilot without revisiting the pool.

Negotiating implementation SOWs before licence shape is fixed. Statement-of-work assumptions about environments, user types, and module counts should trace to the same workbook as the IBM quote. Divergence between SOW and PoE is a primary source of change-order friction.

Letting the hypervisor team size OpenShift while the application team sizes MAS. The reference data for this site is explicit: MAS runs on OpenShift. If platform and application procurement run on separate tracks, you can end up with a cluster that is technically excellent but misaligned with MAS core entitlements, or the reverse. One integrated sizing narrative avoids that gap.

How MaxIron approaches this

MaxIron is an IBM Gold Partner delivering MAS implementation, upgrade, managed hosting, and SLA-backed support across the UK, Ireland, USA, and Europe. On licensing, we treat IBM’s Licence Information and your transaction documents as the source of truth, use IBM’s published MAS licensing guidance and SaaS-specific notes where they apply, and align technical architecture (environments, integrations, module roadmap) to that evidence before we commit delivery dates. We can work with bring-your-own-licence estates or transact where that fits the programme, and we publish a dedicated overview of AppPoints and BYOL positioning at maxiron.com/maximo-apppoints-licensing so buyers can compare those paths without a sales call.

We do not replace IBM’s auditors or your internal SAM function. We do make sure workshop decisions (which modules, which environments, which user types) are traceable to the same Licence Information clauses your CFO will rely on at renewal. Where programmes are still anchored on Maximo 7.6, we keep the migration conversation honest about suite structure and OpenShift, consistent with IBM’s own documentation on what MAS is and how it deploys.

Next steps

If you want an independent pass across your entitlement story before a major renewal or MAS migration, use maxiron.com/contact and ask for a licensing and architecture review tied to your PoE and roadmap. For delivery context, see maxiron.com/ibm-maximo-implementation for greenfield and complex programmes, maxiron.com/maximo-to-mas-upgrade for migration from classic Maximo, and maxiron.com/maxiron-cloud for managed OpenShift hosting models that sit alongside your licence choices.