AppPoints arithmetic. MAS bundle economics. Asset class entitlement. Industry solution overlap. The buyer side framework for the largest IBM commercial conversation outside of the mainframe and middleware estate.
IBM Maximo Application Suite is the consolidated successor to the legacy Maximo product family. The transition from per application named user licensing to the AppPoints based MAS metric is the largest IBM commercial conversation in most asset intensive enterprises. The AppPoints arithmetic is opaque to most buyers and well understood by the publisher's enterprise sales team. The buyer side framework is the corrective.
This playbook walks through the framework. The objective is not to deploy MAS. The objective is to land in 2030 with a defensible, supportable, commercially efficient Maximo and IBM industry solution estate. MAS is the publisher's preferred destination. Several alternative paths remain commercially viable for portions of the estate. Read also our IBM services and the IBM Knowledge Hub.
IBM Maximo Application Suite consolidates the legacy Maximo product family, the IBM industry solutions, and the related health, safety, and AI capabilities into a single licensed bundle. The bundle includes:
The licensing metric is AppPoints, with each application carrying an AppPoint weighting per user type.
The commercial advantage of MAS over the legacy per application licensing model is the reallocation flexibility. AppPoints can be moved across applications within MAS without additional licensing, provided the contract is drafted appropriately. The contract clauses governing reallocation are the most important commercial conversation in any MAS deal. Without the right reallocation clauses, MAS is just a bundle. With the right reallocation clauses, MAS is a flexible entitlement pool.
AppPoints are the consumption metric for MAS. Each application has an AppPoint weighting per user type, with limited user, base user, and premium user as the principal categories. The total AppPoint requirement is the sum of all weighted user counts across the deployed applications. The arithmetic is straightforward in principle and opaque in practice.
The negotiation room sits in three places.
We have run more than thirty MAS conversion engagements since 2022. The pattern is consistent. Most clients can move the AppPoint requirement by twenty to thirty percent through user classification alone, and a further fifteen to twenty five percent through application scope and reallocation clause negotiation. The Maximo white paper walks through the framework with worked examples.
The AppPoint weightings vary materially by application. Maximo Manage carries the highest weighting per base user, reflecting its position as the core asset management application. Maximo Health and Maximo Predict carry lower weightings but are typically deployed against larger user populations. Maximo Visual Inspection and Maximo Assist carry application specific weightings that reflect their role in the broader MAS portfolio.
The right framework for the application weighting analysis is to model the AppPoint requirement against the planned deployment shape over the full contract term, not just at deal close. Application adoption typically increases over the term, and the AppPoint requirement scales with that adoption. The contract should size the AppPoint pool against the third year deployment, not the first year deployment. Sizing against the first year creates a true up risk that the publisher will treat as a re negotiation opportunity.
IBM industry solutions overlay onto Maximo for utilities, transportation, oil and gas, and aviation. The industry solution licensing was historically separate from the core Maximo entitlement. Under MAS, the industry solutions are folded into the AppPoints metric, with industry specific weightings layered onto the base application weightings.
The folding of industry solutions into MAS is generally favorable for the buyer if the deal is structured appropriately. The legacy industry solution licensing was complex and expensive on an absolute basis. The MAS overlay structure simplifies the entitlement and creates room for cross application reallocation that was not available under the legacy model. The negotiation room sits in the contract drafting around the industry overlay, not in the headline pricing.
Most enterprises are converting from a legacy Maximo entitlement to MAS, rather than starting fresh. The conversion arithmetic is the center of the commercial conversation. The publisher's conversion logic translates legacy named user counts into AppPoint counts at a defined ratio. The published ratio is rarely the negotiated ratio.
The buyer side conversion framework runs in three steps.
The PVU to VPC transition playbook covers a parallel conversion framework on the IBM middleware side.
IBM uses ILMT and contract entitlement comparison as the primary Maximo audit mechanism. The audit script reviews ILMT data against the contractual AppPoint entitlement and flags variances. The audit team is well trained, and the audit settlement framework is well rehearsed.
The audit defense framework runs in three workstreams.
The full framework lives in our IBM audit defense guide and under Vendor Shield always on cover.
MAS is available as both a SaaS subscription and an on premise deployment. The SaaS pricing is structured against AppPoints in the same way as the on premise pricing, with a defined infrastructure overlay. The choice between SaaS and on premise is rarely an arithmetic decision. It is an operational and strategic decision.
SaaS works well for enterprises that want to offload Maximo infrastructure operations and that have a relatively standardized deployment shape. On premise works well for enterprises with extensive customisations, complex integrations, or specific data residency requirements. Most large enterprises run a mix, with the core asset management workload on premise and the analytics and AI overlay in SaaS. Our IBM services page covers the full advisory framework.
The right time to engage on a Maximo or MAS conversation is twelve to eighteen months before the largest in scope renewal or conversion event. Earlier is better. The work is most valuable when there is enough time to use the recommendations to shape the renewal strategy, rather than to react to a renewal that is already in flight. We will tell you on the first call whether the timing fits your situation. Read also our IBM licensing assessment service.
AppPoints are the consumption metric for IBM Maximo Application Suite. Each MAS application has an AppPoint weighting per user type. The total AppPoint requirement is the sum of all weighted user counts across the deployed applications. AppPoints can be reallocated across applications within MAS without additional licensing if the contract is drafted appropriately.
MAS is rarely cheaper than legacy Maximo on a like for like basis at first deployment. The economic case for MAS depends on consolidation across multiple Maximo applications, IBM industry solution overlap, and the value of the bundled health, safety, and AI capabilities. The right comparison is multi year total cost across the application portfolio, not single application list pricing.
IBM uses ILMT and contract entitlement comparison as the primary Maximo audit mechanism. The audit script reviews ILMT data against the contractual AppPoint entitlement and flags variances. Independent license position review before the audit is the most effective defense.
AppPoints can be reallocated across applications within MAS if the contract is drafted appropriately. The reallocation flexibility is one of the principal commercial advantages of MAS over the legacy per application licensing model. The contract clauses governing reallocation should be negotiated explicitly at the deal table.
The full IBM audit defense framework, from ILMT data review through settlement framing. AppPoint reallocation clauses, user classification definitions, and the negotiation positions we have used on more than fifty live IBM audits.
Eighty pages. PDF. No reseller fingerprints. The framework we use on every IBM audit response.
IBM produced an AppPoints conversion number we could not afford. Redress ran the user classification first, the application weighting second, and the reallocation clause third. The number moved twenty two million dollars over five years, and the contract is now flexible.
Confidential consultation. No follow up sales call unless you ask for one.
AppPoints precedents, audit movements, MAS pricing benchmarks, and middleware transition case work.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
