Product · Maximo
IBM Maximo licensing and audit defense.
Maximo is licensed by named user, and named user counts drift upward faster than anything else in an IBM estate. When the audit lands, the gap between accounts provisioned and entitlements held becomes the finding. We map the real count and defend it. Independent and buyer side only.
Authorized User metricOver-deployment is the trap
How Maximo is licensed.
Maximo Asset Management is licensed primarily on user metrics. The Authorized User metric counts every individual given access to the program, whether or not they log in during a period. Limited and self service user tiers carry lower entitlements but tighter definitions, and Application Point packaging meters the specific Maximo applications and industry add-ons a deployment uses.
The defining feature is that an Authorized User is counted by provisioning, not by activity. A leaver who was never deprovisioned still counts. A service account, an integration login and a test user all count unless they are excluded under the program terms. Maximo counts the door, not who walks through it.
Some Maximo deployments also pull in infrastructure that carries its own metric: the bundled or separately licensed database, application server and integration components. Each of those can be in scope under the correct metric, which is why a Maximo audit rarely stays confined to Maximo alone.
Common audit traps.
01
Stale user accounts
Leavers, duplicates and dormant logins never deprovisioned still count as Authorized Users in the audit pull.
02
Tier misclassification
Limited or self service users carrying full Authorized User definitions, inflating the entitlement gap.
03
Application Point sprawl
Add-on applications and industry solutions activated beyond the Application Point entitlement.
04
Bundled infrastructure
The database and middleware under Maximo pulled into scope under their own PVU or VPC metric.
05
Non production counted
Test and development users folded into the production count when they should be scoped separately.
06
Integration accounts
Service and integration logins counted as named users without the exclusion argument made.
How we defend it.
The buyer side method, applied to the Maximo user count.
01
Contain
Scope the user extract before it reaches IBM. We decide what proves your real count, not IBM.
02
Reconcile
Map active named users to entitlements, strip leavers and duplicates, classify each tier correctly.
03
Challenge
Dispute every account IBM counted that should be excluded, with the deprovisioning and tier evidence.
04
Settle
Reduce the over-deployment claim and write a clean user governance baseline into the settlement.
Result on the record.
Enterprise · Cognos + Maximo
$2.8M
over-deployment cut
User reconciliation
Actual user counts mapped to entitlements, excess license claim removed at renewal.
Method
Reconcile
the named count
Active users only
The defense lives in proving who actually holds access, not what the directory still lists.
Coverage
500+
engagements delivered
Buyer side only
Every Maximo defense is run from the client side of the table, never with IBM.
Defend the Maximo count now.
Named user drift is the easiest finding IBM raises and the easiest to challenge with the right evidence. We mobilize within 48 hours. Independent and buyer side, every time.
Get audit help now →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
IBM Audit
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019