Maximo audit: user over deployment patterns.

Why Maximo is a user count audit.

Maximo asset management is licensed largely on people, whether through the older Authorized and Concurrent User metrics on standalone Maximo or through AppPoints in Maximo Application Suite. That makes the audit a counting exercise, and counting users is where deployments drift furthest from entitlements. Field technicians, contractors, integrations and reporting tools all touch Maximo, and each can become a chargeable user if the count is built from a raw export rather than a reconciliation. The patterns below are the ones IBM's audit teams find again and again.

The patterns that repeat.

The first is indirect access: users reaching Maximo through a mobile work order app, a portal, or an integration are real users even though they never log into the core interface, and they are routinely uncounted by the buyer but counted by IBM. The second is dormant and departed accounts left active in the user table, inflating the headcount with people who no longer exist. The third is user type mismatch, where occasional or read only users were provisioned at a full authorized user level they never needed.

• Indirect access through mobile, portals and integrations counts as users
• Dormant and departed accounts inflate the table until they are removed
• Concurrent versus authorized metrics are mixed up in the opening count
• Occasional users provisioned as full users when a lower type fit

How each pattern is defended.

Indirect access is mapped and counted honestly, because conceding it late is worse than scoping it early; the goal is to count each person once, not twice through two channels. Dormant accounts are removed against directory and HR records. User type is corrected so occasional users sit at the right level. In the locked enterprise case, this kind of Cognos and Maximo user reconciliation cut $2.8M of over deployment by mapping actual usage to entitlements and removing the excess claim at renewal.

What this means under audit.

A Maximo finding is the gap between IBM's raw user table and a reconciled count of real, correctly typed, distinct users. Under Contain, Reconcile, Challenge, Settle, the Reconcile step rebuilds that count from access and directory records, and the Challenge step disputes every inflated line. The over deployment IBM opens with is almost always larger than the deployment you can prove, and proving it is what moves the number.