IBM Maximo Application Suite Licensing Guide 2026

IBM Maximo Application Suite: What Changed and Why It Matters

IBM Maximo Application Suite (MAS) is IBM's enterprise asset management platform, consolidating the legacy Maximo product family — Maximo Asset Management, Maximo for Transportation, Maximo for Nuclear Power, Maximo IT — into a single subscription offering. IBM launched MAS in 2021 and has been systematically migrating clients off perpetual licences ever since. As of 30 September 2025, IBM ended standard support for Maximo Application Management 7.6, the previous perpetual version. Clients still on 7.6 face a stark choice: pay extended support premiums (typically 20–30% above standard annual maintenance) or migrate to MAS subscription.

The commercial model changed fundamentally. Legacy Maximo was licensed per user type — Authorised User, Limited Use User, Read-Only User — with separate perpetual licences for each module. MAS introduces AppPoints: a single metric that allocates across all MAS applications and user types. IBM positions this as flexibility; in practice, it is also a mechanism to reset the pricing conversation entirely, often resulting in enterprises paying 40–80% more annually than their previous maintenance costs.

Understanding AppPoints allocation before signing any MAS agreement is not negotiable. Enterprises that accept IBM's first proposal without independent validation consistently overpay. Redress has reviewed dozens of MAS migration proposals since 2022; IBM's initial offers are, without exception, above where negotiations settle.

The AppPoints Model: How IBM Allocates Capacity Across MAS

AppPoints are the currency of MAS licensing. Every MAS application consumes AppPoints according to IBM's allocation tables, which vary by application and user role. A concurrent user of Maximo Manage (the core EAM/CMMS module, equivalent to legacy Maximo Asset Management) consumes more AppPoints than a read-only user of Maximo Health. IBM publishes AppPoint weights in its Licence Information documents, but the tables are complex and IBM sales teams regularly propose AppPoint bundles that do not accurately reflect a client's actual usage profile.

The four primary MAS modules and their typical AppPoint consumption patterns are:

• Maximo Manage: The EAM core — work orders, assets, procurement, inventory. Full users consume 8–15 AppPoints each depending on role. A 200-user Manage deployment typically requires 1,500–2,500 AppPoints.
• Maximo Monitor: IoT and asset performance monitoring. Priced on a combination of device connections and user access; high device counts drive AppPoint consumption significantly above user-based equivalents.
• Maximo Health: Asset health scoring and failure prediction (formerly Maximo Health, Predict and Utilities). Read-access heavy deployments use Health at lower AppPoint cost than Manage, making it viable as an add-on for condition-based maintenance programmes.
• Maximo Visual Inspection: Computer vision for asset defect detection. Licensed on image inference volume and concurrent user count. High-volume manufacturing clients can face significant AppPoint consumption for Visual Inspection if inference rates are not capped in the contract.

AppPoints are non-expiring within a subscription term but cannot be carried between annual terms without renegotiation. IBM's renewal motion is to propose AppPoint increases at each annual renewal, citing usage growth. Clients who establish clear baseline AppPoint consumption in year one — with contractual language capping IBM's renewal uplift — have more control over long-term cost trajectory. Download our IBM Licensing Intelligence white papers for AppPoint allocation reference tables and negotiation templates.

Migrating from Maximo 7.6 Perpetual: What IBM Offers and What You Should Demand

IBM's standard migration offer converts legacy perpetual licences to MAS AppPoints using IBM's internal conversion tables. The conversion formula is not publicly documented in full, and IBM's account teams apply it inconsistently. Clients with broad legacy Maximo entitlements — particularly those holding module licences they no longer actively use — frequently receive migration proposals that under-convert their historical entitlement value into AppPoints, effectively requiring them to purchase additional AppPoints to cover the same user base.

IBM also offers MAS Subscription — Perpetual Conversion, a distinct path that lets clients convert perpetual licences into a MAS subscription at a specific conversion rate. This differs from a fresh MAS purchase and typically offers better pricing if the client's legacy entitlement portfolio is broad. IBM does not always present this option proactively; clients must ask.

Three migration principles Redress applies for every Maximo client:

• Audit legacy entitlements first. Before IBM's conversion tables are applied, independently verify what perpetual licences you actually hold. IBM's records are frequently incorrect — either missing entitlements or including licences that were legitimately retired. Correcting the baseline before conversion prevents paying for AppPoints you are entitled to receive as part of the migration.
• Demand a minimum AppPoint guarantee. IBM's migration offer should include a minimum AppPoint allocation that covers your current active user base at today's consumption rates, with no additional charge. If IBM's proposal requires purchasing additional AppPoints to match your existing user count, challenge the conversion formula.
• Negotiate the uplift cap at migration, not renewal. IBM's renewal uplift on MAS subscriptions averages 8–12% per year at list. Locking in a maximum uplift cap (typically 3–5% for multi-year agreements) at the point of migration is substantially easier than renegotiating at renewal when IBM holds the leverage of active support dependency.

See our IBM ILMT Guide for how ILMT compliance requirements interact with MAS licensing — particularly if Maximo is deployed in virtualised environments where sub-capacity PVU rules still apply to the underlying IBM middleware (WebSphere, Db2) that MAS runs on. Our IBM Db2 Licensing Guide is specifically relevant if your Maximo 7.6 deployment used Db2 as the underlying database, which carries its own licence metric implications into MAS.

Subscription vs Perpetual: The Total Cost of Ownership Comparison

Clients resisting the move to MAS subscription frequently cite the preference for perpetual ownership. For Maximo, the perpetual option effectively ceased as a new purchase option with IBM's 2021 MAS launch, and support for existing perpetual 7.6 licences ended in September 2025. The commercial question has shifted: it is no longer perpetual vs subscription, but rather how to structure the MAS subscription to minimise lifetime cost.

A 5-year total cost of ownership comparison for a typical 300-user Maximo deployment (using Manage as the primary module) illustrates the stakes. Under legacy 7.6 perpetual, a client might have been paying £180,000–£250,000 annually in maintenance. IBM's first MAS subscription proposal for equivalent coverage typically comes in at £280,000–£420,000 annually, a 60–80% increase at list pricing. After Redress negotiation — applying conversion credits, competitive benchmarks (ServiceMax, Infor EAM, IFS are credible alternatives IBM's team takes seriously), and multi-year commitment discounts — the settled price for the same deployment typically falls to £200,000–£300,000 annually, a 10–20% premium over legacy maintenance rather than 60–80%.

The negotiation window is widest at the point of migration. Once a client is live on MAS, switching costs are significant: data migration, workflow reconfiguration, and user retraining. IBM knows this and factors it into renewal pricing. Engaging Redress before the migration commitment is the single highest-return action available to enterprise Maximo clients in 2025–2026.

Negotiating MAS: Leverage Points That Work in 2026

MAS negotiations respond well to several specific tactics that Redress applies consistently across IBM asset management engagements:

• Present alternative EAM vendors. ServiceMax (Salesforce-based), Infor EAM, IFS, and SAP PM are credible enterprise alternatives IBM's account teams respond to. A documented evaluation of alternatives — even a preliminary RFP — unlocks additional discount authority of 10–20% above IBM's standard offer.
• Scope AppPoints conservatively. IBM proposes AppPoint bundles sized for peak usage plus growth. Negotiate to actual baseline usage with a contractual right to purchase additional AppPoints at renewal pricing if you exceed the cap. This prevents paying for capacity you may never use.
• Use the support end-of-life deadline as leverage, not as IBM's leverage over you. IBM's sales team will cite September 2025 EoS as pressure to migrate quickly. Position it differently: IBM is equally incentivised to convert you before a competitor does. Extended support has a cost — IBM wants MAS revenue, not extended support revenue. Use that dynamic to negotiate concessions.
• Request multi-year pricing with annual flexibility. IBM offers better AppPoint pricing on 3-year MAS commitments versus annual. Negotiate a 3-year deal with an annual true-down right (ability to reduce AppPoints if usage falls) rather than a traditional true-up-only structure.
• Bundle the underlying infrastructure licences. If your MAS deployment uses IBM Db2 and IBM WebSphere, negotiating all three (MAS, Db2, WebSphere) as a single commercial package consistently yields better blended pricing than purchasing separately. See our IBM Sub-Capacity PVU guide for how PVU-based pricing on underlying infrastructure interacts with the MAS subscription.

Redress structures IBM Maximo engagements as fixed-fee advisory — we validate your entitlements, model the AppPoint requirement, benchmark the proposal, and negotiate. The engagement typically completes before your migration deadline, and savings consistently exceed advisory fees by 5–10×.