IBM Maximo Application Suite consolidated five Maximo products into one Red Hat OpenShift container suite priced on the AppPoints metric. The buyer side that maps consumption per application captures the band IBM would otherwise keep.
IBM Maximo Application Suite is the consolidated enterprise asset management platform IBM launched in 2020 and matured through 2025. MAS combines five previously discrete Maximo products into one container suite on Red Hat OpenShift, priced on the AppPoints metric.
The AppPoints metric looks transparent. In practice the per application conversion rates differ widely and the OpenShift infrastructure carries separately. The buyer side that maps consumption per application and infrastructure together captures the band IBM would otherwise keep.
MAS bundles five discrete applications under one consumption metric. Each application addresses a distinct enterprise asset management need. Customers commit to the full suite or to a subset depending on the asset estate and the maturity of the asset management programme.
The core work and asset management application. Successor to classic Maximo 7.6. Handles work orders, asset records, preventive maintenance schedules, service requests, and inventory management. The foundation of any MAS deployment.
The IoT monitoring application. Ingests sensor data from connected assets, applies anomaly detection, and surfaces events. Suitable for asset estates with deployed IoT instrumentation. Drives the data layer for MAS Predict.
The AI driven predictive maintenance application. Consumes data from MAS Monitor and Manage to predict asset failures and recommend preventive interventions. The largest AppPoints consumer per asset in most deployments.
The computer vision application. Trains image recognition models for asset inspection, defect detection, and visual quality control. Used in manufacturing, transportation, and utilities scenarios where visual inspection drives maintenance decisions.
The asset health and reliability scoring application. Computes asset health index, reliability metrics, and risk scores across the estate. The reporting and decision layer above Manage, Monitor, and Predict.
| Application | Primary use | AppPoints consumption | Typical adopter |
|---|---|---|---|
| MAS Manage | Work and asset management | Per user, per asset | All MAS customers |
| MAS Monitor | IoT sensor monitoring | Per device, per data point | IoT enabled asset estates |
| MAS Predict | Predictive maintenance AI | Per model, per inference | Maintenance excellence programs |
| MAS Visual Inspection | Computer vision inspection | Per camera, per inference | Manufacturing, transport, utilities |
| MAS Health | Asset health scoring | Per asset, per score | Reliability engineering teams |
AppPoints (AP) is IBM's unified consumption metric for MAS. The customer commits an AppPoints pool against the planned application portfolio. Each application consumes AppPoints at a defined rate per user, per asset, per processor, or per inference depending on the application.
The customer estimates the AppPoints required across the application portfolio. The estimate drives the commit pool size. IBM offers volume discount bands at the 5,000, 10,000, 25,000, and 50,000 AppPoints commit tiers.
Manage consumes AppPoints per concurrent user and per managed asset. Monitor consumes per connected device. Predict consumes per AI inference call. The conversion rates differ widely and require a sustained measurement programme to validate.
Customers running all five applications can find the AppPoints pool consumed disproportionately by one application. A heavy MAS Predict deployment can absorb the pool that was meant to support Manage. The buyer side runs application level visibility against the pool.
Pool overage prices at standard per AppPoint rates without the multi year discount band. A sustained overage event drives the renewal up. The buyer side runs quarterly pool reviews and adjusts the commit at renewal.
MAS runs as containers on Red Hat OpenShift. The OpenShift infrastructure carries separately from the MAS AppPoints commit. The OpenShift cost can match or exceed the MAS cost depending on the deployment scale.
OpenShift Container Platform on customer infrastructure (on premises). Red Hat OpenShift Service on AWS, Azure, or IBM Cloud (managed). Customer chooses based on data residency, existing infrastructure, and hyperscaler strategy.
MAS workloads require a multi node OpenShift cluster sized for the application portfolio. Manage, Monitor, and Predict have different resource profiles. The cluster baseline drives the OpenShift subscription cost.
OpenShift requires platform engineering capability. Customers without in house Kubernetes operations should consider Red Hat OpenShift Service variants where Red Hat operates the platform. Trade off is operational burden against platform fee.
IBM offers bundles that include OpenShift entitlement with MAS commits. The bundle simplifies procurement and can deliver per AppPoint efficiency at scale. The buyer side tests the bundle against unbundled OpenShift subscription pricing.
Most MAS customers migrate from classic Maximo 7.6 or earlier. The migration is a multi quarter programme covering data migration, customization rewriting, and OpenShift infrastructure provisioning. IBM offers migration tooling and partner support.
Asset records, work order history, preventive maintenance schedules, inventory, and master data. The migration toolset handles the standard data model. Custom data extensions require manual mapping.
Classic Maximo customizations using Java MBOs do not port directly to MAS. The MAS extension model uses different patterns. Customers rewrite or retire classic customizations as part of the migration.
Customer provisions the OpenShift cluster either on premises or on hyperscaler. Cluster sizing depends on MAS application portfolio. The infrastructure provisioning often paces the migration timeline.
Typical migration projects run six to twelve months from kickoff to production cutover. Larger estates with heavy customization can run eighteen months. The buyer side prefers a phased cutover by site or business unit.
Five buyer side moves drive the typical 30 percent recovery on an MAS commit. The buyer side that runs all five captures the band. Skipping any one move concedes recovery to IBM list pricing across the asset management estate.
Document asset count, user count, IoT deployment, and the application portfolio in scope. The inventory drives the AppPoints commit pool sizing. Without the inventory the commit is a guess.
Apply the per application conversion rates to the inventory. Quantify expected AppPoints consumption for Manage, Monitor, Predict, Visual Inspection, and Health separately. The map is the basis for the negotiation.
On premises OCP, managed ROSA on AWS, managed ARO on Azure, or IBM Cloud Red Hat OpenShift. Each carries different cost and operational profiles. The decision drives the infrastructure spend across the MAS term.
Phase the classic Maximo migration to spread the AppPoints ramp across the term. A big bang migration commits to peak AppPoints from day one. A staged migration matches commit to actual consumption growth.
Three year MAS commits attract per AppPoint discount bands. The lock protects against the next IBM AppPoints rate event and against renewal inflation. The buyer side locks the price for the full term.
The checklist takes the asset management and procurement functions from a MAS interest conversation to a structured commit. The earlier the work starts, the wider the option set on the day IBM puts the proposal on the table.
Maximo Application Suite (MAS) is the consolidated enterprise asset management platform built on Red Hat OpenShift. MAS combines Maximo Manage, Monitor, Predict, Visual Inspection, and Health into one container suite priced on AppPoints.
AppPoints (AP) are IBM's unified consumption metric for MAS. The customer commits an AppPoints pool. Each application consumes AppPoints at a defined rate per user, per asset, or per processor depending on the application.
Yes. MAS runs as containers on Red Hat OpenShift. Customers can run OpenShift on premises, on hyperscaler infrastructure, or as Red Hat OpenShift Service. The OpenShift cost is separate from the MAS AppPoints commit.
MAS Manage (work and asset management), MAS Monitor (IoT monitoring), MAS Predict (AI driven predictive maintenance), MAS Visual Inspection (computer vision), and MAS Health (asset health and reliability scoring).
Classic Maximo licensed per Processor Value Unit or named user. MAS unifies everything into AppPoints with per application conversion rates. The metric simplifies billing but obscures the per application economics until the rates are mapped.
Yes. IBM offers migration paths from Maximo 7.6 and earlier to MAS 8 plus. Migration involves data migration, customization rewriting, and OpenShift infrastructure provisioning. Most migrations take six to twelve months.
Enterprise asset estates commit between 5,000 and 50,000 AppPoints per year depending on user count, asset count, and application mix. Multi year commits attract deeper per AppPoint discounts.
Redress runs MAS licensing decisions inside the broader IBM ELA motion. The work covers AppPoints modelling, application scope, OpenShift infrastructure decisions, and classic Maximo migration economics.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, and the Software Spend Assessment.
Read the related IBM audit defense guide, the IBM watsonx licensing guide, the IBM services, the IBM knowledge hub, the benchmarking service, and the Benchmark Program.
IBM audit response, ILMT compliance, sub capacity rules, and the buyer side moves that close audit positions.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Maximo Application Suite consolidated five product lines into one container catalog. The AppPoints metric looks transparent until the per application conversion rates compound across Manage, Monitor, Predict, Visual Inspection, and Health.
We run IBM Maximo Application Suite decisions across Manage, Monitor, Predict, Visual Inspection, and Health. Typical 30 percent recovery on the consolidated MAS commit through AppPoints and OpenShift math.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
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.
