Application-specific requirements for Maximo Health and Maximo Predict
Review the Maximo Health and Maximo Predict typical workload sizes and persistent storage
requirements.
Workload sizes
The following table lists typical workload sizes for Maximo Health.
| Small | Medium | |
|---|---|---|
| Assets | 3,000 | 20,000 |
| Users | 1 | 5 |
The following table lists typical workload sizes for Maximo Predict:
| 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 six models under four
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.
| Product | Description |
|---|---|
| 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.