IBM Maximo Application Suite licensing in 2026. How the AppPoints pool is counted.

Maximo Application Suite is licensed from one shared pool of AppPoints. Your bill follows the peak number of users logged in, the tier their security groups reach and the cluster you run it on, so measure all three before IBM sizes the pool.

How does IBM Maximo Application Suite licensing work?

You buy a pool of AppPoints, and every user and some installed components take a set number of points from it. IBM defines an AppPoint as a common unit of value for licensing the suite, and your pool has to cover everything you have switched on at once.

One entitlement to Maximo Application Suite covers Manage, Monitor, Health, Predict, Mobile and the other suite applications, so capacity can shift from work management to monitoring or prediction without a separate purchase. What decides the bill is how quickly each user type and application drains the pool.

Administrators sit outside this table. An administrator is licensed as an authorized user at 10 points for Base level or 15 for Premium, so the points stay reserved whether or not they sign in.

Which tier does each user land in?

A user is charged at the highest tier their security groups reach, whatever they actually do. A technician working in three Manage modules is a Limited user at 5 concurrent points. Open Health to the same person and the charge becomes 10. Open Predict and it becomes 15.

Should you license authorized or concurrent users?

IBM's Maximo Application Suite licensing rules allow both, and most customers need a mix. A concurrent user draws points at login and returns them at logout. An authorized user holds points permanently, cannot share them, and can only be reassigned by permanently transferring the entitlement to another person.

The break even point is simple division. A Base authorized user costs 3 points against 10 for a concurrent seat, so authorized wins for any Base group where more than 30 percent of people are logged in at the busiest hour. The Limited threshold is 40 percent (2 against 5), and Premium is one third (5 against 15).

Which components draw install based AppPoints?

Some items consume points per install whether or not anyone logs in. IBM's current guidance lists these among them:

• ERP connectors. The Maximo Connector for SAP, Oracle or Workday applications takes 80 points each.
• Spatial and Civil Infrastructure. 20 and 50 points per install.
• Optimizer. 220 points, or 60 for Optimizer Limited.
• Visual Inspection. 45 points per install, on top of the Premium user points of the people who work in it.

Why do premium applications drain the pool so quickly?

A Premium seat costs three times a Limited seat, and the tier rises for everyone in a security group the moment one Premium application is added to it. Predict, Visual Inspection and the industry solutions all require Premium, and Health requires at least Base.

Monitor is often lumped in with the premium group, but IBM prices Monitor user access at the Limited rate. IBM's guidance lists no device or install charge for Monitor, so its extra cost shows up in the cluster that stores and processes device data.

A worked example: one pool, three ways to buy it

Say you run 400 Maximo users in three groups, and you have measured the peak number logged in during your busiest month. The table prices each group both ways at IBM's published rates.

The cheapest answer mixes the two. Planners peak at 75 percent of headcount, well above their threshold, so they go authorized at 180 points. Technicians at 30 percent and engineers at 25 percent stay under theirs and remain concurrent at 450 and 150. The mixed pool is 780 points, about 26 percent below the all concurrent figure.

Adding group peaks together overstates slightly when groups peak at different hours, since the suite counts one combined peak. Now suppose someone adds Health to the technicians' security group. They move from Limited to Base, their 90 peak seats cost 900 points instead of 450, and the pool you need rises from 780 to 1,230 without a single new user.

What does the OpenShift requirement cost?

The OpenShift license comes with the suite, but the servers, storage and people that run the clusters do not. Maximo Application Suite runs only on Red Hat OpenShift, and IBM states that the suite ships with the supporting software it needs, such as OpenShift, Cloud Pak for Data, Db2 and WebSphere Liberty.

The included entitlement is restricted to Maximo and its supporting programs, and IBM grants it at a fixed ratio of OpenShift cores to the AppPoints you buy. Ask IBM to confirm how many cores your pool entitles and price any shortfall.

Which platform costs belong in the business case?

Budget these alongside the AppPoints from the first draft of the business case, since IBM's quote will not include them.

• Cluster capacity. Control plane and worker nodes, sized for Manage plus every other application you deploy, on premises or on AWS, Azure or Google Cloud.
• Storage. Persistent storage for the database, attachments and, if you run Monitor, device data.
• Skills. OpenShift administration, patching and suite upgrades, from your own team or a partner.
• Extra entitlement. Red Hat OpenShift subscriptions for any other workload on the same clusters, bought standalone from Red Hat or inside a Cloud Pak.

When does SaaS take the OpenShift question away?

If IBM hosts the suite, the platform cost is inside the subscription. IBM's public price list starts Maximo Essentials for maintenance at under $40,000 a year for 150 AppPoints, one environment and up to 25 users, and the Standard SaaS plan at 300 AppPoints. Subscriptions carry a minimum 12 month non cancellable term.

A single site maintenance team will often find SaaS cheaper once cluster hardware and skills are counted. A large utility with its own OpenShift team and data residency rules usually prices client managed first, and should still compare both.

How does converting from legacy Maximo work?

IBM offers conversion paths from legacy Maximo entitlements to AppPoints, and whether the trade is fair depends on your application mix and on how IBM values the licenses you already own. For most 7.6 customers the timing is no longer optional.

Regular support for Maximo Asset Management 7.6.1.x ended on September 30, 2025. IBM sells up to one year of Extended Support and up to five years of Sustained Support, but only to customers current on Subscription and Support, on 7.6.1.3 or later, with an upgrade roadmap. Expect the conversion quote to reflect that deadline.

Reconcile entitlements first

Confirm what you own in Passport Advantage before any conversion, so the trade starts from your full entitlement. Look for perpetual licenses under old part numbers and separately bought industry solutions, since each can carry value into the conversion. Our Passport Advantage guide covers where those records hide.

The conversion ratio is negotiable

The ratio of legacy entitlement to AppPoints is not fixed in stone. Model it against measured concurrency by application before you accept the pool IBM proposes, and ask to see the calculation line by line: each legacy product, its user type, the AppPoints credited and the price per point.

Why we do not accept that AppPoints always save money

The usual advice is that one flexible pool must beat many fixed product licenses. We disagree. In the Maximo environments we have reviewed, pools sized to named users and loaded with premium access cost more than a disciplined legacy footprint would have.

Measure concurrent use by application first, size the pool to that evidence, and grant premium access to named groups by decision. With that done, the suite can come in below the legacy footprint, and without it the flexible pool mostly buys unused headroom.

What have we seen in recent Maximo negotiations?

Across roughly 15 to 25 IBM Maximo engagements Morten Andersen advised on in 2024 and 2025, the AppPoints model was widely misunderstood at purchase. Buyers sized the pool to named users rather than concurrency and absorbed OpenShift platform cost they had not budgeted. Three patterns came up again and again.

• Oversized pools. AppPoint pools were 15 to 35 percent larger than measured use required, with a median of 28 percent, because sizing started from headcount.
• Unbudgeted platform cost. OpenShift and platform cost added 10 to 20 percent that was not in the original Maximo business case, with a median of 15 percent.
• Fast premium draw. Premium applications consumed AppPoints two to four times faster than the base work management app, typically around 3x.

A flexible pool saves money only when someone has measured who logs in, to which application, at the busiest hour of the month.

How do you measure your own AppPoint position?

Start from login data and security groups, since those two sources decide both the peak and the tier. You can do most of this before you speak to IBM.

1. Turn on login tracking in legacy Maximo. Without it you have no record of when people sign in and out, so peak concurrency is a guess.
2. Run AppPoints in parallel on 7.6.1.2 or later. The AppPoint Licensing Setup application and the CalculateAppPoints cron task record daily peaks from users' security profiles, which shows your AppPoint demand before you migrate.
3. Read the AppPoints usage page in suite administration. Once on the suite, it shows AppPoint consumption against your entitlement over time, which is the evidence for any resizing.
4. Map security groups to tiers. List every group that opens Health, Predict, Visual Inspection or an industry solution, and count the people in it.
5. List install based components. Connectors, Spatial, Optimizer and Visual Inspection installs each take points before anyone logs in.

Which peak should you size to?

Size to a busy period, such as month end or a planned outage, rather than an average week, which understates the pool and causes denied logins at the worst moment. The single highest minute of the year overstates it. A sustained daily peak across your busiest month is the fairest basis.

Check non production too. IBM's guidance says development and test instances with a corresponding production install do not consume AppPoints, so any quote that charges for them needs correcting. Our note on IBM non production licensing covers the wording to ask for.

Which controls cut Maximo Application Suite cost?

Three controls do most of the work, and the contract terms below keep the savings for the full term.

• Measure concurrency. Size the pool to peak concurrent use by application, and put heavy daily users on authorized licenses where the break even test favors it.
• Gate premium apps. Grant Health, Predict and Visual Inspection to named groups, track their AppPoint draw separately, and review security groups every quarter.
• Budget the platform. Include OpenShift and platform cost from the start, and choose SaaS or client managed on the full cost of each.

What will IBM's account team say, and how should you answer?

Suggested reading

• IBM Practice. How we scope IBM work.
• IBM Hub. The wider IBM licensing library.
• Maximo and industry solution licensing. How the industry add ons are priced and bundled.
• IBM Cognos licensing. How IBM analytics metrics compare and where cost grows.
• Software spend health check. Benchmark the IBM position against peers.

What to do next

1. This month. Measure concurrent Maximo usage by application and by user type, using login tracking or the AppPoints usage view.
2. Before any quote. Reconcile legacy entitlements in Passport Advantage, including perpetual licenses and industry solutions.
3. Before accepting the pool. Model the AppPoint conversion ratio against measured concurrency, product by product.
4. In the sizing model. Separate premium app consumption from base work management, and test each group for authorized against concurrent licensing.
5. In the business case. Budget Red Hat OpenShift cluster, storage and skills cost, and compare it with the SaaS price.
6. At signature. Right size the AppPoint pool to evidence, and add the price hold, uplift cap and reduction terms.
7. Before the next renewal or conversion. Engage independent IBM advisory to check IBM's numbers against your own.

Frequently asked questions