AppPoints Licensing Explained

What are AppPoints?

AppPoints are the licensing currency used across Maximo Application Suite. In practical terms, they help determine which users can access which MAS capabilities and how that access consumes entitlement. The exact commercial details should be confirmed with IBM or your licensing partner, but the planning principle is stable: role design and application access affect cost.

Summary: AppPoints planning belongs in architecture and adoption workshops, not only in procurement meetings.

Why do AppPoints matter during MAS planning?

MAS makes it easier to think beyond Manage. A user might need Manage, Mobile, Health, Monitor, Predict, or other capabilities. That flexibility is useful, but it can create budget surprises if access is granted broadly without persona modeling. A casual requester, technician, planner, supervisor, reliability engineer, and administrator should not automatically receive the same entitlement.

How should teams model roles?

Start with personas and tasks. List what each role actually does in the suite, how often they do it, and whether access is production, pilot, read-only, administrative, or occasional. Then map those needs to licensing assumptions and validate them with IBM guidance.

| Persona | Likely access question | Planning risk | | --- | --- | --- | | Technician | Mobile work execution | Underestimating rollout volume | | Planner | Manage and scheduling | Overlapping capabilities | | Reliability engineer | Health, Monitor, Predict | Pilot becoming production | | Executive | Dashboards and reports | Over-entitlement | | Admin | Broad configuration | Too many privileged users |

What mistakes should be avoided?

Do not use security groups as a substitute for licensing analysis. Do not grant suite-wide access just because it is convenient for testing. Do not forget contractors, seasonal workers, shared devices, or read-only stakeholders. Do not let a successful pilot expand without revisiting entitlement.

What is the best governance habit?

Create a quarterly entitlement review that compares active users, roles, applications, adoption metrics, and upcoming projects. Include finance and procurement so budget decisions follow actual usage. Include security so access remains least-privilege. Include business owners so license changes match operational value.