Our MAS Single plan is a single server deployment designed for price-sensitive organizations with up to 50 concurrent users, who don’t yet need to use additional suite modules besides standard Maximo (aka Manage in MAS), and don’t require redundant servers in multiple availability zones. (See below for SQL to estimate your concurrent user count).

Our MAS Cluster plan is a cluster deployment with worker nodes and control plane nodes distributed across multiple availability zones. Like our MAS Single plan, it is right-sized for MAS in order to provide unbeatable value at a lower price point than you will find anywhere. The MAS Cluster plans starts with as few as 2 worker nodes and can be expanded to any number to support your concurrent user requirements. Additional special purpose nodes can be added as well, such as GPU processors for MAS modules that utilize AI.

See Our MAS hosting plans for a comparision of our MAS hosting services.

Estimating the MAS Capacity You Need

To estimate your Maximo concurrent users, find your current high-water mark with the following SQL query. This will return the top 10 concurrent user counts and the day each occurred in the prior year. You may choose to disregard any outliers.

You may also want to decrease your high-water mark if you have set Maximo’s time-out period to be longer than the standard 30 minutes, as this means the high-water number returned by the query may be inflated in terms of actual load on the server.

SQL Server:

select top 10 cast(attemptdate as Date) as countdate, max(currentcount) as concurrentcount from logintracking where attemptdate > getdate()-365 group by cast(attemptdate as Date)
order by max(currentcount) desc;

Oracle:

select * from
(select trunc(attemptdate) as countdate, max(currentcount) as concurrentcount from logintracking where attemptdate > sysdate-365 group by trunc(attemptdate)
order by max(currentcount) desc)
Where rownum <=10;