The Maximo Ecosystem: What Each Component Does

01 · Basics — Understand the building blocks

The name Maximo can describe a maintenance application, a family of asset products or the whole Application Suite. Start by asking which business responsibility you mean. Recording work, watching equipment, assessing condition and choosing a replacement investment are different jobs, even when they concern the same asset.

Maximo Manage handles the operational asset and maintenance records: assets, locations, work orders, preventive maintenance, inventory, purchasing and related processes. MAS provides the suite environment in which applications are administered and accessed. OpenShift supplies the container platform for client-managed suite deployments. A platform service, a Manage extension and a suite application belong at different levels of an architecture.

Asset performance applications help teams interpret observations and decide where to focus. Monitor deals with operating signals; Health organizes condition and health assessment; Predict adds predictive analytics. Visual Inspection analyzes images. These capabilities need suitable data and deliberate connections to the maintenance process. An analytical result becomes useful when someone can review it and take an accountable action.

The ecosystem also includes industry solutions, add-ons, field applications and connectors. An industry solution adapts processes to a sector. An add-on extends a specific responsibility, such as maps or customer billing. A connector carries defined business information between systems. Their presence in the catalogue does not mean every component is installed in your environment.

Topics in this series

• Suite platform versus business applications
• Manage and field execution
• Monitoring, health and prediction
• Reliability and investment decisions
• Add-ons, industry solutions and connectors

02 · Map a business need to its components

Check each proposed handoff against the installed applications.

1. Write the outcome first: for example, reduce repeat failures of a duty pump while retaining a clear maintenance history.
2. Assign the operational record to Manage: identify the asset, location, responsible site and work process.
3. Identify how the observation arrives. A technician uses Mobile; a sensor needs an IoT data path and monitoring; a camera-based defect may use Visual Inspection.
4. Choose the decision capability only when needed. Use Health for condition assessment, Predict for a suitable predictive question, Reliability Strategies for maintenance policy, or Asset Investment Planning for long-term intervention choices.
5. Add contextual extensions deliberately: Spatial for geographical identity, Service Provider for customer obligations, HSE for the relevant risk process, or an industry solution for its sector-specific work.
6. Mark each required connection and its owner. Confirm what is actually deployed, who can access it, and which handoffs need integration or review. Avoid assuming a product tile creates an end-to-end process.

03 · Practical example

Fictional teaching example

A fictional pumping station repeatedly loses capacity. Manage holds the pump and repair history. A technician records findings through Mobile. Operating measurements feed the monitoring path, where an alert identifies a change worth investigating. Health helps the reliability engineer compare this pump with similar assets. Predict is relevant only if a suitable model and data can answer the failure question. The engineer reviews the evidence and raises approved work in Manage. Spatial supplies location context where needed; HSE supports the applicable risk controls. If recurring repairs make replacement worth considering, Asset Investment Planning compares interventions over the chosen horizon. This is a responsibility map: the connections and approvals still need to be designed and tested.

04 · Practice and verify

Draw a component map for the pump problem. Label every arrow with what moves across it: a measurement, alert, asset identifier, work request, approved work order or completion update. For each component, write its responsibility, input, output, owner and whether it is installed, required later or unnecessary for this use case.

Expected result

You can explain where the maintenance record lives, where observations originate, who interprets them, who authorizes work and where execution feedback returns. Your map distinguishes Health from HSE, a health assessment from a prediction, a work schedule from an investment plan, and an application from its hosting platform.

Common mistakes

• Selecting every available product before defining the outcome.
• Treating an alert, prediction or health score as an automatically approved work order.
• Assuming matching asset descriptions establish identity between systems.
• Confusing deployment availability, user access and a tested business handoff.

05 · Architecture decisions

Review the architecture at its boundaries: who owns the asset identifier, how timestamps and units are normalized, which system owns financial records, and how failed handoffs are retried and reconciled. Add the required integration, security and operational support responsibilities to the map. Begin with the components needed for the first business outcome; introduce further capabilities when their inputs, owners and acceptance criteria are clear.

IBM references

• IBM — Suite applications, industry solutions, add-ons and tools
• IBM — Maximo Application Suite architecture
• IBM — Maximo Health overview
• IBM — Maximo Predict
• IBM — Maximo Mobile overview
• IBM — Reliability Strategies
• IBM — Asset Investment Planning

Product explanations link to IBM sources. Scenarios and exercises are original Assetize guidance, not claims of executed lab procedures. Reviewed 2026-10-01.