Detailed System Requirements
Abstract
The IBM® Maximo® Application Suite 8.7.0 system requirements consist of environment requirements and software dependencies, capacity planning information, and software product compatibility reports.
Content
For detailed Maximo® Application Suite installation instructions, see the IBM Maximo Application Suite download document and the installation documentation.
Environment requirements and software dependencies
Maximo® Application Suite runs on Red Hat OpenShift. For more information about general requirements such as domain registration, certificates, and required software installation and configuration details, see the Requirements topic in the Maximo Application Suite documentation.
Capacity planning
Use the Maximo® Application Suite sizing calculator to estimate the required sizing for your planned deployment.
Important: The information in this document represents the minimum resources that you need to successfully install Maximo® Application Suite. You might need more resources to support your specific workload. If needed, work with your IBM® Sales representative to generate more accurate calculations based on your expected workload.
To use the calculator:
- Download and open the linked spreadsheet in Excel.
- Select or enter values for the yellow fields only to match your planned application deployment.
- The calculator provides estimated total system requirements in VPCs and Memory (GB) for your configuration in the Resulting Complete Environments Requirements section of the Output table.
Software Product Compatibility Reports
For more information about prerequisite and supported software such as browser versions for Maximo® Application Suite and supported applications and tools, see the following links to the corresponding Software Product Compatibility Reports.
- IBM Maximo Application Suite Software Product Compatibility Report
- IBM Maximo Application Suite - Manage Application Compatibility Report
Application-specific requirements
IBM Maximo Manage
Refer to the Maximo® Application Suite sizing calculator above for capacity planning for the IBM Maximo Manage application.
IBM Maximo Monitor and IoT
Workload sizes:
The following table lists typical workload sizes.
| Developer | Small | Medium | |
|---|---|---|---|
| IoPoints* | 200 | 5,000 | 50,000 |
| Max number of simultaneously connected devices | 200 | 5,000 | 50,000 |
| Max data rate (totaled over all connected devices) | 0.4 kB/s | 10 kB/s | 100 kB/s |
| Max msg rate (totaled over all connected devices) | 4 msg/s | 100 msg/s | 1,000 msg/s |
| Max Db2® insert rate | 4 inserts/s | 100 inserts/s | 1,000 inserts/s |
*An IoPoint is a data value that is written to the Maximo® Monitor database by a distinct device with a frequency of no more than one write per minute.
When you are calculating with IoPoints, you need to consider three dimensions:
- Number of devices
- Number of data points sent in each message
- Number of messages per second
For example, a total of 1,000 IoPoints might be allocated in the following ways:
- 1,000 devices that each send 1 message per minute, where each message contains 1 datapoint.
- 1 device that sends 1,000 messages per minute, where each message contains 1 datapoint.
- 500 devices that each send 2 messages per minute, where each message contains 1 datapoint.
- 1 device that sends 1 message per minute, where each message contains 1,000 data points.
In the preceding table, the data rate and message rate rows show the rates for data that flows from devices to the IoT tool and to the Maximo® Monitor application.
Persistent storage requirements
The IoT Tool requires a PVC to store the MQTT broker state. You set the storage class and size of the PVC when you deploy the IoT tool.
Requirements
To view a list of available storage classes in your cluster, run the following OpenShift console command: oc get storageclasses
Choose the appropriate storage class and size for your workload size.
The storage class can be used to dynamically provision a persistent volume with access mode RWO (ReadWriteOnce).
No specific filesystem permissions are required.
Supported and tested storage
The following storage providers have been tested with the IoT Tool:
-
Openshift Container Storage
-
IBM Cloud block storage class:
ibmc-block-gold
The following table lists typical storage requirements.
| Maximo® Application Suite core | RLKS: 5 Gb |
| Maximo Monitor | None |
| IoT - Developer | Message Gateway: 64 Gb |
| IoT - Small | Message Gateway: 64 Gb |
| IoT - Medium | Message Gateway: 128 Gb |
| MongoDB | 20 Gb |
| Kafka | ZooKeeper: 20 Gb Kafka: 50 Gb |
| Cloud Pak for Data (Db2) | Cloud Pak for Data: 20 Gb Db2 Warehouse: (100 Gb * 2) + Db2 user storage based on retention policy |
Db2® user data storage
User storage requirements for Db2® are primarily determined by two factors:
- Incoming event data rate
- Retention policy
A typical allocation might be 1 Mb storage per day per 300 bytes/minute (3 IoPoints).
The following table is based on the workload sizes estimates.
| Data rate | IoPoints | Db2® Storage Requirements | |
|---|---|---|---|
| Developer | 400 bytes/sec | 200 | 80 Mb storage per day |
| Small | 10,000 bytes/sec | 5,000 | 2 Gb storage per day |
| Medium | 100,000 bytes/sec | 50,000 | 20 Gb storage per day |
For example, if you wanted to store 1 month's worth (30 days) of data and also match the benchmark figures, the user storage requirements are as follows:
- Developer: 2.4 Gb (30 * 0.08 Gb)
- Small: 60 Gb (30 * 2 Gb)
- Medium: 0.6 Tb (30 * 20 Gb)
Messaging Load Balancer
For messaging workloads with more than 100K device connections, the OCP Ingress load balancer is not an option. Alternatives, such as, the NLB 2.0 load balancer in IBM Cloud®, which is based on IPVS/Keepalived, can scale beyond 100K device connections.
IBM Maximo Health
Workload sizes:
The following table lists typical workload sizes.
| Small | Medium | |
|---|---|---|
| Assets | 3,000 | 20,000 |
| Users | 1 | 5 |
IBM Maximo Predict
Workload sizes:
The following table lists typical workload sizes.
| Small | Medium | |
|---|---|---|
| Assets (subset of assets in Health | 600 | 6,000 |
| Asset groups* | 5 | 10 |
| Users | 1 | 5 |
| Number of sensors per asset | 10 | 30 |
| Sensor readings | 328,000 | 3,288,000 |
| Failure history for active assets | 10,500 | 75,000 |
* In each asset group, for a small workload, were 60 active and 60 decommissioned assets. For medium workload, there were 300 active and 300 decommissioned assets in each group.
** Sensor readings are at a daily level for each active asset over a period of 3 years.
Additionally, Maximo Predict includes a notebook that includes 6 models under 4 templates:
| Number of models | |
|---|---|
| Degradation curve | 1 |
| Time to failure | 2 (1 for each failure mode) |
| Failure prediction | 2 (1 for each failure mode) |
| Anomaly detection | 1 |
Persistent storage requirements
The following table lists typical storage requirements.
| Maximo Health | IBM Db2 Warehouse (dedicated instance): 120 GB |
| Maximo Predict* | 20 GB |
* Because Maximo Health is deployed as part of deploying Maximo Predict, storage requirements for Maximo Health are also applicable to a Maximo Predict deployment.
IBM Maximo Visual Inspection
Recommended hardware configuration and I/O performance
Worker nodes
Maximo Visual Inspection requires the following configuration for each worker node:
- At least one 64-bit x86-compatible processor.
- 60GB of memory.
GPUs
Maximo Visual Inspection needs GPUs to perform deep learning model training and requires the following GPU configuration:
- NVIDIA Pascal, Volta, or Turing GPU architectures (all optimization options) and at least 16GB of GPU memory per GPU
or
- NVIDIA Ampere architecture (Yolo V3 models supported in this release) and at least 16GB of GPU memory per GPU.
Storage
Maximo Visual Inspection uses a persistent volume claim (PVC) to manage storage and requires the following storage configuration and I/O performance:
- A PVC storage class that supports ReadWriteMany access mode.
- NFS based, file-storage based, or IBM Cloud File Storage implementations that offer ReadWriteMany access modes are supported.
- Storage provider implementations that offer ReadWriteOnce access mode, such as most block storage implementations, are NOT supported.
- A PVC storage size of at least 40GB for data sets and models.
- Increased numbers for data sets and models lead to increased storage requirements.
- Most storage providers allow storage allocations to be increased.
- If you cannot increase your allocation, use the following rule to determine a rough estimate of your storage utilization:
(100 KB per image) x (number of images) x (number of data sets) +
1GB x (number of models) +
10GB
Note: images and video clips vary greatly in resolution and compression ratios. This rule might not be appropriate for your workload.
- At least 10,000 input/output operations per second (IOPS) of random read/write performance for data set uploads and downloads.
- Less storage bandwidth means that certain actions are visibly slower.
- As more storage IOPS are allocated, application performance scales up to approximately 50,000 random read/write IOPS.
- Configuration of IOPS and storage quotas varies from provider to provider. See how to manage IBM Cloud File Storage IOPS or refer to your storage provider's documentation.
IBM Maximo Safety and Assist
IBM Maximo Safety workload sizes
The following table lists typical workload sizes.
| Tiny | Small | Medium | Large | |
|---|---|---|---|---|
| Workers Monitored* | 50 | 250 | 2,500 | 10,000 |
* If worker or asset location tracking is used, the number of workers (or assets) that can be monitored by the solution sizes is reduced to half as many.
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m0z000000cwZDAAY","label":"Maximo Application Suite"},{"code":"a8m3p000000hAePAAU","label":"Maximo Application Suite->MAS Applications->Health"},{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite->MAS Applications->Manage"},{"code":"a8m3p000000hAeKAAU","label":"Maximo Application Suite->MAS Applications->Monitor"},{"code":"a8m3p000000hAeVAAU","label":"Maximo Application Suite->MAS Applications->Predict"},{"code":"a8m3p000000hAeUAAU","label":"Maximo Application Suite->MAS Applications->Visual Inspection"},{"code":"a8m3p000000GoD8AAK","label":"Maximo Assist"},{"code":"a8m3p000000GoDCAA0","label":"Maximo Safety"},{"code":"a8m0z000000cwZDAAY","label":"Maximo Application Suite"},{"code":"a8m3p000000hAePAAU","label":"Maximo Application Suite->MAS Applications->Health"},{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite->MAS Applications->Manage"},{"code":"a8m3p000000hAeKAAU","label":"Maximo Application Suite->MAS Applications->Monitor"},{"code":"a8m3p000000hAeVAAU","label":"Maximo Application Suite->MAS Applications->Predict"},{"code":"a8m3p000000hAeUAAU","label":"Maximo Application Suite->MAS Applications->Visual Inspection"},{"code":"a8m3p000000GoD8AAK","label":"Maximo Assist"},{"code":"a8m3p000000GoDCAA0","label":"Maximo Safety"},{"code":"a8m0z000000cwZDAAY","label":"Maximo Application Suite"},{"code":"a8m3p000000hAePAAU","label":"Maximo Application Suite->MAS Applications->Health"},{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite->MAS Applications->Manage"},{"code":"a8m3p000000hAeKAAU","label":"Maximo Application Suite->MAS Applications->Monitor"},{"code":"a8m3p000000hAeVAAU","label":"Maximo Application Suite->MAS Applications->Predict"},{"code":"a8m3p000000hAeUAAU","label":"Maximo Application Suite->MAS Applications->Visual Inspection"},{"code":"a8m3p000000GoD8AAK","label":"Maximo Assist"},{"code":"a8m3p000000GoDCAA0","label":"Maximo Safety"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0"}]
Was this topic helpful?
Document Information
Modified date:
13 May 2022
UID
ibm16488613