This tool decides whether a Maximo role should be Authorized, Concurrent, or Mixed, and whether shifts actually lower peak demand.
Concurrent is not automatically cheaper. It carries a higher AppPoint weight per user, so it only wins when peak simultaneous usage stays low. Simple mode draws the break-even line live as you move the peak. Shift mode derives a real peak from your shift populations, then runs the same math. It is a satellite of the AppPoints Estimator.
No. A concurrent user carries a higher AppPoint weight than an authorized user of the same tier. Concurrent only saves when the peak number of simultaneous users is low enough to overcome that higher weight. Above the break-even peak, authorizing every user uses fewer AppPoints.
It is the peak concurrent users at which concurrent and authorized cost the same. It equals total users times the authorized weight, divided by the concurrent weight. As a share of total users it is the authorized weight over the concurrent weight: about 40 percent for Limited, 30 percent for Base, and 33 percent for Premium.
Only if the shifts do not overlap and peak active usage stays low. Base across three full shifts can cost more than authorized because its concurrent weight is more than three times its authorized weight. Premium across three shifts only breaks even before overlap, and any handoff overlap or persistent session erases the advantage.
No. This break-even logic is the customer-managed model. MAS as a Service bills concurrent usage per active clock hour, not by simultaneous peak, so the threshold works differently. Do not apply these results to a SaaS subscription without reworking the model.