IBM Maximo Application Suite Licensing: AppPoints, Migration, and Cost Optimisation

What IBM Maximo Application Suite Is — and Why the Licensing Changed

IBM Maximo Application Suite (MAS) is IBM's converged enterprise asset management platform, combining Maximo EAM (Enterprise Asset Management), Maximo Asset Performance Management (APM), and Maximo Asset Investment Planning (AIP) under a single subscription licence. MAS was built on Red Hat OpenShift, positioning it as a cloud-native or on-premises containerised platform consistent with IBM's broader hybrid cloud strategy.

The move to MAS represents IBM's deliberate sunset of the legacy Maximo 7.6 perpetual licence model. Maximo 7.6.1.x standard support ended in September 2025. Organisations that have not transitioned to MAS AppPoints licensing either need IBM Sustained Support (extended support at additional cost) or face operating on unsupported software. The commercial pressure this creates is intentional — IBM's revenue model for Maximo has shifted from one-time perpetual revenue to recurring subscription revenue, and the end-of-support timeline is the primary commercial lever to drive that transition.

The AppPoints Licensing Model Explained

MAS licensing is built around AppPoints — a pooled credit system that replaces the per-user, per-application model of Maximo 7.6. Organisations purchase a pool of AppPoints rather than named user licences for each Maximo application. AppPoints can be allocated across any MAS application — Manage (core EAM), Monitor (IoT and remote monitoring), Predict (AI-driven predictive maintenance), Visual Inspection, and others — providing flexibility to shift allocation as business priorities change.

How AppPoints Are Consumed

Each application and user type consumes AppPoints at a defined rate. Heavy users of Maximo Manage (the core EAM application) typically consume more AppPoints per user than limited or read-only users. The AppPoint rates for different user types and applications are defined in IBM's MAS licensing documentation and can change between subscription renewals. The pooled model means that a large AppPoint purchase can support a mix of heavy users, limited users, and application add-ons without requiring separate licence counts for each — but it also means that AppPoint pool sizing is critical: an undersized pool creates a compliance gap, while an oversized pool creates unnecessary cost.

Subscription Duration and Pricing

MAS subscriptions are available for terms of 12 to 60 months. Longer terms typically attract better per-AppPoint pricing, but the lock-in increases proportionally. IBM's standard commercial approach is to offer a multi-year commitment at an attractive per-AppPoint rate — the trade-off is reduced flexibility to adjust the licence pool or renegotiate terms if business requirements change. IBM Essentials, IBM's entry-level SaaS offering for smaller deployments, starts below $40,000 per year for fixed configurations, but enterprise deployments with large AppPoint pools are significantly more expensive and require direct commercial negotiation.

Migrating from Maximo 7.6 Perpetual Licences

The mechanics of migration from Maximo 7.6 perpetual licences to MAS AppPoints are important to understand before any commercial negotiation, because they determine how much of your existing investment IBM will credit toward the new subscription.

Trade-Up Provisions

IBM offered existing Maximo 7.6 customers the ability to trade up their existing user-based perpetual licence entitlements to MAS AppPoints through their annual Passport Advantage renewal. The trade-up converts named user licences (Base, Limited, Express, and other 7.6 user types) to a corresponding AppPoint allocation, providing "Dual Entitlement" — the right to run both the legacy 7.6 platform and MAS during the transition period.

The trade-up provision requires active IBM Passport Advantage Software Subscription and Support (S&S). Organisations that allowed their Maximo 7.6 S&S to lapse are not entitled to the trade-up credit — they must purchase MAS AppPoints as a net-new acquisition, with no credit for their legacy perpetual investment. This is a common and expensive mistake. Before any MAS licensing discussion, verify that your Maximo 7.6 S&S coverage has been maintained without gaps.

ILMT and Sub-Capacity for MAS

IBM Maximo Application Suite, when deployed on-premises or in a customer-managed cloud environment, falls within IBM's software licensing compliance framework. For distributed deployments — which MAS on OpenShift typically represents — ILMT (IBM License Metric Tool) remains a mandatory compliance requirement for sub-capacity licensing. Organisations running MAS on virtualised or cloud infrastructure without ILMT correctly configured face full-capacity assertion risk in the event of an IBM licence review. IBM License Service is the container-specific tooling required for OpenShift-deployed MAS. Both ILMT and IBM License Service should be deployed and generating reports before any MAS licence review with IBM.

The Commercial Risks of Delaying MAS Migration

With Maximo 7.6.1.x standard support having ended in September 2025, organisations still running on legacy Maximo face four escalating risks.

IBM Sustained Support Costs

IBM offers Sustained Support for Maximo 7.6.1.x beyond the standard support end date, but at a material cost premium. Sustained Support is typically priced at a significant uplift above the standard S&S rate — organisations should expect to pay 20 to 30 percent more for Sustained Support than for in-support software maintenance. This premium, combined with the absence of new feature development on the 7.6 platform, makes Sustained Support a transitional measure rather than a long-term strategy.

Negotiating Leverage Declines Over Time

IBM's commercial position on MAS AppPoint pricing is strongest when the customer is operating without current support — IBM knows that migration is not optional and prices accordingly. Organisations that begin MAS migration discussions before their 7.6 support expires retain more commercial leverage: they have the option of extending S&S, delaying migration, or competing IBM against alternative EAM platforms. Once support has expired, the negotiating dynamic shifts materially in IBM's favour.

PVU Licensing Exposure for Legacy Maximo Infrastructure

Organisations running Maximo 7.6 on IBM middleware infrastructure — WebSphere Application Server, Db2 — may hold those components under PVU licensing. As the transition to MAS occurs, middleware licensing transitions toward VPC under IBM Cloud Pak structures. The PVU-to-VPC transition creates compliance gaps if not managed carefully: organisations may find themselves paying PVU fees on legacy infrastructure and VPC fees on new MAS infrastructure simultaneously without appropriate entitlement for both. An infrastructure audit before migration is essential to identify and resolve any PVU/VPC overlap.

Five Strategies to Optimise Your MAS Licensing Position

1. Size AppPoints Accurately Before Committing: IBM's default MAS proposals tend to include AppPoint pools sized generously — ensuring you are not under-licenced but potentially over-licenced. Independently model your required AppPoint consumption based on actual user profiles, application usage, and planned MAS application adoption. Commit only to the AppPoints you can demonstrate a need for in the contract term.

2. Negotiate Trade-Up Credits: If you have maintained Maximo 7.6 S&S continuously, you are entitled to trade-up credits for your existing perpetual licences. Ensure IBM's commercial proposal explicitly accounts for all trade-up credits available — IBM's initial proposals do not always apply the full entitlement without negotiation.

3. Use Competing EAM Platforms as Leverage: IBM is aware that Maximo competes with SAP PM, Oracle EAM, Infor EAM, and specialist asset management platforms. A credible competitive evaluation — even a preliminary RFI process with one or two alternative vendors — changes the commercial conversation materially. IBM account teams have latitude to improve AppPoint pricing when a customer demonstrates genuine alternatives under consideration.

4. Time Your Migration to IBM's Q4: IBM's fiscal year ends 31 December. Commercial flexibility is greatest in October, November, and December. Initiating MAS migration commercial discussions in September gives you access to IBM's Q4 close pressure as a negotiation lever.

5. Verify ILMT and IBM License Service Before Any IBM Review: Ensure ILMT is deployed for any IBM software components running in virtual machine environments and IBM License Service is deployed for OpenShift-hosted MAS components. Compliance gaps discovered by IBM during a licence review create audit liability that shifts the commercial dynamic unfavourably.