Maximo Health 9.1 and Predict 9.1: The Unified Asset Dashboard, the End of Health Standalone, and What Reliability Engineering Actually Looks Like in MAS 9

Maximo Health 9.1 and Predict 9.1: The Unified Asset Dashboard, the End of Health Standalone, and What Reliability Engineering Actually Looks Like in MAS 9The Maximo Application Suite 9.1 release is a significant one for the asset performance management side of the platform. Maximo Health stops being a standalone deployment and becomes Maximo Manage with Health. The Monitoring and Testing (MAT) service is retired, taking the notebooks that depended on it with it. Asset Investment Optimizer is replaced by Asset Investment Planning. And a new unified Asset and Location dashboard pulls data from Maximo Manage, Maximo Monitor, Maximo Health, and Maximo Predict into a single view that the reliability engineer can actually use to drive a decision.

Each of these changes is meaningful on its own. Together, they represent the most significant refactor of the Maximo APM stack since the original 8.x release. For reliability engineers, condition monitoring leads, and asset managers, the implication is that the platform is converging on a single, integrated way of working. The standalone Health deployment is no longer the right answer. The standalone Predict configuration, without Manage and Health underneath, is no longer the right answer. The right answer is the integrated Manage with Health and Predict stack, configured correctly, and used by a team that has been trained on the new model.

This article walks through each of the major changes, explains what they mean in practice, and gives you the configuration and operational patterns that turn the new platform into a working reliability program.

The End of Health Standalone and the MAT Retirement

The most operationally significant change is the retirement of Maximo Health as a standalone application. Before 9.1, organizations could deploy Health as a standalone application, with its own database, its own integration points, and its own administrative surface. In 9.1, that option is gone. New customers do not have the choice. Existing Maximo Health 9.0 users are required to manually upgrade to Maximo Manage with Health 9.1.

The migration path is documented and well supported, but it is a real project. The Health application data model is preserved, and the data is migrated into the Manage with Health deployment. The Health administrative surface is integrated into the Manage administration. The Health user-facing applications become part of the Manage user experience. For most organizations, the migration is straightforward but should not be done in a single weekend. The right cadence is a non-prod validation, a pre-prod rehearsal, and a production cutover with rollback capability.

The MAT service retirement is more contained. The Monitoring and Testing service, which provided a notebook environment for testing predictive models before deployment, is no longer available. Notebooks used for monitoring and testing services, and notebooks with names starting with ModelLifecycle_, are no longer available. The replacement pattern is to use the standard Predict notebook environment, which is engineered for production use, and to do the model testing in that environment with appropriate versioning and governance. The capability loss is small. The operational simplification is significant, because the MAT service was a separate deployment that added operational complexity without adding proportional value.

The Asset Investment Optimizer replacement is the third structural change. The 9.0 Asset Investment Optimizer is replaced by Asset Investment Planning in 9.1. The new application supports generating and comparing multiple scenarios for investment in assets, with rapid weighted analysis and multi-objective optimization to balance cost, risk, and performance. For capital planning teams, the new application is significantly more capable than the one it replaces. For teams that were using Asset Investment Optimizer, the migration should be planned as a separate workstream from the Health migration, because the underlying data model and configuration patterns are different.

The Unified Asset and Location Dashboard

The single most user-visible change in Health and Predict 9.1 is the unified Asset and Location dashboard. The dashboard pulls data from Maximo Manage, Maximo Monitor, Maximo Health, and Maximo Predict into a single view, organized by asset or by location. The reliability engineer opens an asset, and they see the health score, the criticality, the risk, the failure history, the maintenance cost, the meter history, the work history, the predictions, and the sensor data — all in one place.

The dashboard is organized into tabs. The Overview tab shows the health, criticality, and risk scores, with the underlying inputs and the calculation methodology. The Reliability tab shows the failure history and the total maintenance cost. The Alerts and Meters tab shows the active alerts and the meter history. The Predictions tab shows the failure probability, the days to failure, the anomalies, and the recommended actions. The Work History tab shows the chronological record of all work orders, with the ability to drill into any work order for full detail.

The practical impact is that the reliability engineer no longer needs to navigate between four different applications to get a complete picture of an asset. The data is in one place. The drill-down paths are consistent. The time to answer a question like "what is the failure probability for this pump, what is its current health, and what work has been done on it in the last 90 days" drops from several minutes to several seconds.

The asset hierarchy and location hierarchy views are particularly useful for root cause analysis. The hierarchical view shows the child assets and their scores, which makes it possible to identify which child asset is driving the parent's condition. This is a real win for complex asset structures where a single component failure can drive a parent asset's health score down. The reliability engineer can see the hierarchy, see the contributing child scores, and identify the root cause without navigating to a separate application.

The meter comparison view is a productivity gain for engineers who are used to exporting meter data to a separate tool for analysis. The Asset and Location dashboard supports selecting up to six meters and comparing their historical data in either a tabular or graphical view for a selected date range. The data can also be downloaded in CSV format for offline analysis. For teams that have been doing this analysis in Excel, the native capability removes a manual step and improves the consistency of the analysis.

Reliability Strategies, RPN Categories, and Action Types

The Reliability Strategies application in Health 9.1 has been extended with new settings that make it more flexible. RPN (Risk Priority Number) categories can now be added and configured, and action types can be added and configured. For teams that have been running reliability strategies with a fixed RPN methodology, the ability to define custom RPN categories is significant. The RPN calculation can now reflect the organization's specific risk model, rather than the out-of-the-box defaults.

The action types customization is similarly useful. The action types define the recommended actions that surface from a reliability strategy, such as "inspect," "replace," "reengineer," or "no action." Custom action types let the organization match the strategy output to its specific maintenance and engineering practices. For example, a team that has a "condition-based replacement" program can define an action type for that program and have it surface from the strategy when appropriate.

The new API methods for condition score notebook templates are worth understanding as well. The library API methods allow you to retrieve a list of assets connected to a specific location or asset. This is useful for understanding how surrounding assets may be impacting a specific asset's overall condition, which is a common reliability engineering question. The API is documented and stable, and it is the integration point for any custom reliability tooling.

The AI Virtual Assistant and the Operational Dashboard

The AI virtual assistant that was introduced with Maximo Assistant in 9.1 is also available in Maximo Health. The assistant can be configured to retrieve and answer questions about data in Maximo Manage and Maximo Health. The configuration is done through the AI configuration application, and the assistant leverages the same watsonx.ai-backed service that powers the Maximo Manage assistant.

For reliability engineers, the assistant is useful for two kinds of questions. The first is the "what is the current state of this asset" question, which the assistant can answer by querying the relevant data and presenting it in natural language. The second is the "show me the assets that are most at risk" question, which the assistant can answer by applying the appropriate filters and presenting the results. The assistant is not a replacement for the dashboard, but it is a useful complement, particularly for engineers who are on the move and need quick answers without navigating through the application.

The Operational Dashboard in Maximo Application Suite now includes the Health work queues. The work queues are the operational units of the Health application, and they are the place where assets that need attention are surfaced. The work queues can be configured to track assets with missing installation dates, assets with high failure probability, assets that will fail before the next scheduled preventive maintenance, and many other conditions. Surfacing the work queues in the Operational Dashboard makes them visible to the operations team, not just the reliability team, which is important for organizations that want to integrate reliability engineering with day-to-day operations.

The access permissions for work queues are now configurable. Administrators can set permissions for creating, viewing, editing, or deleting work queues. For organizations that have separated reliability engineering from operations, or that have multiple reliability teams with different responsibilities, the access control is a real improvement. The right people see the right work queues, and the wrong people do not see the work queues that are not relevant to their work.

Asset Investment Planning: From Optimizer to Multi-Objective Optimization

The Asset Investment Planning (AIP) application that replaces Asset Investment Optimizer in 9.1 is a significant capability addition. The application supports generating and comparing multiple scenarios for investment in assets, based on business priorities, with rapid weighted analysis and multi-objective optimization to balance cost, risk, and performance.

The scenario generation is data-driven, with customizable value frameworks. The organization defines the objectives (for example, minimize five-year cost, minimize risk of failure, maximize production availability), the weights (for example, 40% cost, 30% risk, 30% availability), and the constraints (for example, capital budget of $5M per year, no more than 10% of assets deferred in any year). The application generates the investment scenario that best meets the weighted objectives, and it presents the trade-offs in a way that the capital planning team can understand and act on.

The multi-objective optimization is the differentiator. Most capital planning tools support single-objective optimization (minimize cost) or constrained optimization (minimize cost subject to a maximum risk). AIP supports multi-objective optimization, which means that the tool can find solutions that are not on the single-objective frontier. For example, a solution that costs 2% more but reduces risk by 15% is a better outcome than the cheapest solution, and AIP can find and present that solution.

For organizations that have been using Asset Investment Optimizer, the migration to AIP is a real opportunity to upgrade the capital planning process. The new tool is more capable, but it requires more configuration. The value frameworks need to be defined. The optimization parameters need to be tuned. The scenario comparison workflow needs to be designed. This is a project, not a configuration change, and it should be planned as such.

The Condition-Based Maintenance Pattern That Works

The integration between Manage, Monitor, and Health in 9.1 enables a condition-based maintenance (CBM) pattern that was difficult to achieve in earlier releases. The pattern works like this: Monitor ingests time series data from sensors, devices, and control systems; the data flows into Health as meter readings; the meter readings drive the health score; the health score drives the work queue; the work queue drives the work order; the work order drives the maintenance activity. The full chain is integrated, and the maintenance activity is automatically triggered by the asset condition.

The pattern requires three things to work correctly. The first is the meter configuration in Manage, which defines what is being measured, how often it is measured, and what the expected ranges are. The second is the asset configuration in Monitor, which defines the data sources, the data transformation, and the publishing to Health. The third is the health score configuration in Health, which defines the calculation methodology, the inputs, and the thresholds.

When the three are configured correctly, the CBM pattern is a real improvement over time-based preventive maintenance. The maintenance is done when the asset needs it, not when the calendar says to do it. The result is fewer unnecessary maintenance activities, fewer unexpected failures, and a lower total cost of ownership. When the three are not configured correctly, the CBM pattern produces noise, false positives, and missed signals, and the maintenance team loses trust in the system.

The configuration effort is real. A reasonable estimate for a typical CBM deployment is 8 to 12 weeks of configuration work, plus 4 to 6 weeks of validation and tuning, plus 4 to 6 weeks of operations stabilization. The teams that budget the time and the resources for the configuration get the benefit. The teams that try to deploy CBM in a weekend and expect it to work are disappointed.

Practical Implications

The Health and Predict 9.1 changes are a real opportunity for organizations that have been running Maximo APM in a fragmented way. The unified dashboard, the integrated work queues, the multi-objective optimization, and the CBM pattern are all improvements that deliver measurable value. But the changes also require real work. The Health standalone migration is a project. The AIP migration is a project. The CBM configuration is a project. The training and change management for the reliability team is a project.

For organizations that are still on Health 9.0 standalone, the implication is that the migration to Manage with Health 9.1 cannot be deferred indefinitely. The Health standalone deployment is no longer the supported path, and the longer the organization stays on it, the more it is carrying operational and security debt. Plan the migration. Validate in non-prod. Cut over with rollback capability. Then take advantage of the new capabilities.

For organizations that are evaluating Maximo APM for the first time, the implication is that the integrated Manage with Health and Predict stack is the right starting point. Do not deploy Health standalone. Do not deploy Predict without Health. The integrated stack is more capable, more operationally simple, and more aligned with the way reliability engineering actually works in 2026.

For reliability engineers, the implication is that the day-to-day work changes. The dashboard replaces the application switching. The work queues replace the ad hoc queries. The AIP replaces the spreadsheet scenario analysis. The skill set is shifting from "navigate the application" to "interpret the dashboard and act on the work queue." Training is required, and the training should be planned as part of the deployment.

Bottom Line

Maximo Health 9.1 and Predict 9.1 are a meaningful step forward for the Maximo APM stack. The unified Asset and Location dashboard, the integrated work queues, the AIP replacement for AIO, the MAT retirement, and the new reliability strategy configuration are all changes that make the platform more capable and more operationally simple. The Health standalone retirement is the forcing function that organizations need to consolidate on the integrated stack. The CBM pattern is the operational outcome that the integrated stack enables. The investment is real, but the return is also real, and the organizations that make the investment are the ones that will be running a modern reliability program in 2026 and beyond. The teams that defer the migration are the ones that will be running a 9.0 Health standalone deployment in 2027, with a sunset date and a migration project they should have started a year ago.