Maximo Application Suite and AppPoints.

What AppPoints actually are.

Maximo Application Suite, the successor to the older standalone Maximo deployments, is licensed through AppPoints rather than per named user per product. AppPoints are a pooled entitlement: you buy a quantity, and each application and each user type within the suite consumes a defined number of points. A user reaching only a single application draws fewer points than one with broad access across asset management, monitoring, scheduling and other suite capabilities. The model is designed to flex as usage shifts, but the pool is finite, and the audit question is whether consumption stayed inside what you bought.

Where the pool gets overdrawn.

The common finding is consumption drift. Because AppPoints are shared, granting one team access to an additional suite application quietly increases the draw, and nobody tracks the running total against the entitlement. Concurrent versus authorized consumption rules, base versus premium user types, and add on applications each change the point cost. When the suite is rolled out broadly without a consumption model, the deployed draw can exceed the purchased pool well before anyone notices, and the audit measures the peak, not the average.

• AppPoints are pooled, so every new application access raises the draw
• User type, base or premium, changes the points each person consumes
• Add on suite applications carry their own point cost on top
• The audit measures peak consumption against the purchased pool

How the suite is defended.

The defense rebuilds the consumption model from the actual deployment: which applications each user truly accesses, at which user type, and what that draws from the pool. The frequent overstatement is treating every provisioned user as a premium, broad access consumer when most use one application at a base rate. Correcting the user type mix and removing access that was provisioned but never used brings the calculated draw back toward the entitlement, and that recalculated number is what we put in front of IBM.

What this means under audit.

A Maximo Application Suite finding is an AppPoints arithmetic dispute: how many points the real deployment consumes versus how many IBM's opening read assumes. Under Contain, Reconcile, Challenge, Settle, the Reconcile step rebuilds the consumption from access records and user types, and the Challenge step disputes the inflated point draw on the evidence. Getting the consumption model right is what turns an over the pool claim into a defensible position.