IBM Support

Maximo Anywhere 7.6.x Sizing Guidelines

Technical Blog Post


Abstract

Maximo Anywhere 7.6.x Sizing Guidelines

Body

Are you interested in Maximo Anywhere 7.6.x, but don't know where to start to size your Maximo environment to include it? Here are some guidelines to help.

First, we recommend that you start with the IBM MobileFirst Platform V7.1 Scalability and Hardware Sizing document and the Hardware Calculator available from IBM MobileFirst, especially if you plan to use IBM MobileFirst for purposes in addition to Maximo Anywhere.

Then, you can use the following information to assist you with specific details for Maximo Anywhere.

MobileFirst Server:

  • The Maximo Anywhere platform deploys the adapter on the MobileFirst server which acts as an http proxy server and can manage up to 300 users per JVM.
  • Each JVM requires 2 dedicated CPU cores and 4-6 GB allocated for the JVM heap space (plus an additional 30% available RAM for JVM overhead).

Maximo OSLC Server:

  • The Maximo OSLC Server can manage up to 100 users per JVM under normal user load. Refer to to the exceptions below for specific guidance on certain end user activities.
  • Each JVM requires 2 dedicated CPU cores and 4-6 GB allocated for the JVM heap space (plus an additional 30% available RAM for JVM overhead).

Database Server:

  • Maximo Database
    • A minimum extra 30% CPU and memory resources should be added to the DB server to handle Maximo Anywhere load. Refer to the exceptions below for specific guidance on certain end user activities.
  • WorkLight Database
    • Worklight database requires 2 dedicated CPU cores and 4 GB Memory.

Best Practices, Usage Notes, and Exceptions:

  • For more information on tuning, refer to the Maximo Best Practices for System Performance 7.6.x white paper.
  • For application storage and reports, consider separate JVMs and refer to the IBM MobileFirst Platform V7.1 Scalability and Hardware Sizing document to assist in scalability and sizing.
  • The "Download lookup data" feature is used to download a large amount of data to mobile devices.
    • This is typically not a daily activity for the user, but can happen periodically based on how often this data needs to be refreshed.
    • This activity may consume significant system resources on the Maximo OSLC Server reducing the number of managed users to as low as 50 users per JVM. As a best practice, introduce users in batches to avoid a large number of end users accessing this feature concurrently.
    • For internal testing, the lookup data consisted of 50000 Assets, 5000 Locations, 5000 Items, 400000 Failure Lists, 500 Tools, and 250 Persons. All remaining lookup data consisted of  100 record each. Maximo Anywhere may be able to support higher numbers of lookup data with appropriate system resources.
  • The "Download current work list" feature is used to download the list of current work orders to the mobile device.
    • This activity may consume significant system resources on the Maximo Database Server. As a best practice, monitor the database resources to be sure sufficient memory is allocated to handle business requirements during peak usage periods.
    • For internal testing, the Work Order List consisted of 300 Work Orders with 600 attachments, Maximo Anywhere may be able to support larger number of Work Order Lists with appropriate system resources.
  • CPU core recommendations here are based on an Intel Xeon x 5300 series core @ 3000 MHz

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11130163