IBM Maximo Application Suite 8.2.0 system requirements

Detailed System Requirements

Abstract

The IBM® Maximo® Application Suite 8.2.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 Dependencies 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 additional 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 links to the corresponding Software Product Compatibility Reports in the Related information section.

Application-specific requirements

IBM Maximo Manage requirements

With Maximo Application Suite 8.2.0, Maximo Manage is deployed as an external application that is linked from the Maximo Application Suite user interface. For detailed system requirements, see Maximo Manage system requirements (Maximo Application Management 7.6.1.2). For installation instructions, see Installing Maximo Asset Management 7.6.1.2.

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 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 loadbalancer is not suitable and should not be used. Alternatives, such as, the NLB 2.0 load balancer in IBM Cloud, which is based on IPVS/Keepalived, can scale beyond 100K device connections.

Health and Predict content TBD

Visual Inspection

IBM Maximo Visual Inspection requires the following hardware:

Hardware

The following devices are supported:

POWER8 S822LC (8335-GTB) or POWER9 AC922 with at least one NVIDIA NVLink capable GPU
POWER9 IC922 with at least one NVIDIA T4 GPU
x86 system with at least one NVIDIA Pascal, Volta, or Turing-architecture GPU

Required specifications

Your device must meet these minimum requirements:

64 GB of memory
Ethernet network interface
75 GB of storage for installation, and at least 40 GB of storage for runtime. See Disk space requirements for details.
The Nvidia GPU must be configured in the Default compute mode. The Exclusive Process mode will cause trainings to fail. See nvidia-smi usage for details on compute modes.
There are multiple options for deploying the model for testing. Deploying a model to a Xilinx FPGA requires the Xilinx Alveo U200 Accelerator card.

Networking requirements

Your environment must meet the following networking requirements:

A default route must be specified on the host system.
- For instructions to do this on Ubuntu, refer to the IP addressing section in the Ubuntu Network Configuration. Search for the steps to configure and verify the default gateway.
- For instructions to do this on Red Hat Enterprise Linux (RHEL), refer to 2.2.4 Static Routes and the Default Gateway in the Red Hat Customer Portal.

For RHEL, docker0 must be in a trusted firewall zone. If it is not in a trusted firewall zone, modify the RHEL settings as follows:

  sudo nmcli device set docker0 managed yes  sudo nmcli connection modify docker0 connection.zone trusted  sudo systemctl stop NetworkManager.service  sudo firewall-cmd --permanent --zone=trusted --change-interface=docker0  sudo systemctl start NetworkManager.service  sudo nmcli connection modify docker0 connection.zone trusted  sudo systemctl restart docker.service

IPv4 port forwarding must be enabled.
If IPv4 port forwarding is not enabled, run the /sbin/sysctl -w net.ipv4.conf.all.forwarding=1 command. For more information about port forwarding with Docker, see UCP requires IPv4 IP Forwarding in the Docker success center.
IPv6 must be enabled.

Disk space requirements

IBM Maximo Visual Inspection has the following storage requirements for the initial product installation and for the data sets that will be managed by the product.

/var - The product installation requires at least 75 GB of space in the /var file system for the product Docker images. IBM Maximo Visual Inspection also generates log information in this file system. The installation process requires additional space because all Docker images are extracted to disk requiring about 40 GB of space, then the images are loaded by Docker. When the image is loaded, the extracted image is deleted but while images are being extracted and loaded, space is needed for both copies. All application Docker images are extracted and loaded in parallel.
Recommendation: If you want to minimize the root (/) file system, make sure that /var has its own volume.
/opt - IBM Maximo Visual Inspection data sets, models, and runtime data are stored in this file system. This file system must have at least five GB of free space, in addition to any data sets, models or other runtime data for IBM Maximo Visual Inspection to operate successfully. The storage needs will vary depending on the data sets and the contents. For example, video data can require large amounts of storage.
Recommendation: If you want to minimize the root (/) file system, make sure that /opt has its own volume. The /opt file system should have at least 40 GB of space, although this value might be more depending on your data sets.

Image support

The following image formats are supported:
- JPEG
- PNG
- DICOM
Images with COCO annotations are supported. For details, see Importing images with COCO annotations.
IBM Maximo Visual Inspection has limited support for Pascal VOC annotations. Annotations for multiple files residing in a common XML file are not supported. In other words, each annotation XML file can only contain annotations for a single image, identified by the filename attribute.
If you have a single XML annotation file containing annotations for multiple images in the data set to be imported, the annotations need to be split out into separate XML files before IBM Maximo Visual Inspection can import the annotations successfully.
The models used by IBM Maximo Visual Inspection have limitations on the size and resolution of images. If the original data is high resolution, then the user must consider:
- If the images do not need fine detail for classification or object detection, they should be down-sampled to 1-2 megapixels.
- If the images do require fine detail, they should to be divided into smaller images of 1-2 megapixels each.
- There is a 24 GB size limit per upload session. This limit applies to a single .zip file or a set of files. You can, however upload 24 GB of files, then upload more after the original upload completes.
- Large images will be scaled to the appropriate dimensions for the model as follows:
  - SSD: 512 x 512 pixels
    The original aspect ratio is maintained. If necessary, black bands are added to the image to make it fit.
  - Tiny YOLO v2: 416 x 416 pixels
    The longest edge is scaled to 416 pixels and, if necessary, black bands are added to the shorter side to make it 416 pixels.
  - YOLO v3: 608 x 608 pixels
  - Faster R-CNN: 1000 x 600 pixels
    The original aspect ratio is maintained. If necessary, black bands are added to the image to make it fit.
  - Detectron: 1333 x 800 pixels
  - GoogLeNet: 224 x 224 pixels
  - Action detection: 224 x 224 pixels

Supported video types

The following video formats are supported:

Can be played in the IBM Maximo Visual Inspection GUI:

Ogg Vorbis (.ogg)
VP8 or VP9 (.webm)
H.264 encoded videos with MP4 format (.mp4)

Supported by API only:

Matroska (.mkv)
Audio Video Interleave (.avi)
Moving Picture Experts Group (.mpg or .mpeg2)

Not supported:

Videos that are encoded with the H.265 codec.

Related Information

IBM Maximo Application Suite Software Product Compatibility Report

Application: IBM Maximo Manage Software Product Compatibility Report (Maximo Ap…

[{"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":"a8m0z000000cxN3AAI","label":"Maximo Health"},{"code":"a8m0z000000cx3cAAA","label":"Maximo Monitor"},{"code":"a8m0z000000cxN8AAI","label":"Maximo Predict"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.2.0"}]

Tips