This tool estimates how many MAS AppPoints your user population will consume, by role, tier, and access type.
Size AppPoints from the work people actually do, not from headcount. Model authorized versus concurrent access, the tier floor that Predict and add-ons force, install reservations, and the saving from offset, pooled concurrent populations. It is a planning estimate, not an IBM quote. Your contract controls.
AppPoint consumption is driven by each user's license tier and access type. An authorized user permanently reserves AppPoints from the pool at a fixed weight per tier. A concurrent user checks AppPoints out for the length of a session and returns them when it ends. Limited, Base, and Premium each carry a different weight, and capabilities like connectors and Optimizer reserve a fixed number of AppPoints when installed in production.
Authorized AppPoints are reserved for a named user whether they log in or not, at a lower weight per tier. Concurrent AppPoints are shared and checked out only while a session is active, at a higher weight. Concurrent saves AppPoints only when the peak number of simultaneous users is low enough to beat that higher weight.
No. The per-tier user weights match, but MAS as a Service bills hourly and retrospectively rather than by simultaneous peak, so the concurrent and break-even math here does not port to SaaS. This tool covers customer-managed MAS only. Re-verify any SaaS or government number against your current Service Description before relying on it.
No. This is a planning estimate built on published AppPoint weights with a visible last-verified date. It is not a quote, a licensing opinion, or a compliance determination. Your license agreement and transaction documents are controlling. Verify current weights, your deployed MAS version, and your contract terms with IBM or your reseller before purchasing.