Maximo is one of the high-risk IBM products that draws audits, and the move to mobile has added a population that licensing practice often fails to track. A technician using a Maximo Mobile or Anywhere app in the field is using the software, and that use consumes entitlement just as a desktop session does. Because mobile rollouts are frequently run by operations teams rather than the people who manage the license position, the field workforce can grow well past what was counted. When Maximo appears in an audit, the mobile users are a common source of the gap.
How mobile use is licensed.
Maximo is typically licensed by user type, and the application based mobile offerings carry their own user definitions and entitlements. Maximo Mobile and the Anywhere family of apps give field workers task focused access, and each authorized mobile user counts. The detail that catches teams out is that a mobile app user is not free because they never log into the full Maximo desktop client. They hold access to the application, and access is what the metric measures. A large field workforce equipped with a mobile app is a large licensable population, whether or not anyone added them to the traditional user count.
Where Maximo mobile exposure hides.
- Field users never counted. Technicians provisioned with a mobile app whose access was never reflected in the license position.
- User type mismatch. Mobile users assigned a richer user type than their task focused role requires, or a lighter one than their access actually grants.
- Seasonal and contractor surges. Temporary field staff given app access during peak periods and never deprovisioned.
- Indirect access through integrations. External systems and devices reaching Maximo data through the mobile or Anywhere layer, still counting as use.
Counting the mobile workforce.
The defensible Maximo position counts every person and process with access, on any device. That means reconciling the desktop user community and the mobile and Anywhere app users together, mapping each to the correct user type, and accounting for seasonal, contractor and integration based access. The mobile population is usually the part nobody has a clean list of, so building that list is the first defensive step. Once the full access picture exists, the position can be compared to entitlement and a mobile related finding can be confirmed or challenged on evidence rather than guesswork.
Maximo mobile findings come from a field workforce that was provisioned but never licensed, or licensed at the wrong user type. The buyer side response is to count every user with access on any device, map each to the correct type, and reconcile the whole population to entitlement, so the mobile gap is confined and the rest of the claim is held to evidence.
The buyer side defense.
We contain the data request, then build the complete Maximo access picture: desktop users, Maximo Mobile and Anywhere app users, contractors, seasonal staff and integration based access. Each is mapped to the correct user type and reconciled against entitlement before IBM finishes its count. Genuine gaps in the mobile workforce are confined to the specific users and period, over assigned user types are corrected downward, and the reconciled position is written into the settlement with a forward plan that keeps mobile provisioning matched to the license position.