Maximo Manage 9.2: What Changed and What It Means for Administrators

August 19, 2026

IBM Maximo Application Suite 9.2 reached General Availability on June 25, 2026, and for administrators who live in Maximo Manage day to day, this release brings a collection of changes that are both practical and consequential. While the headline features of 9.2 focus on AI capabilities like Condition Insight and the MCP Server, the Manage application itself received a substantial set of updates that affect how administrators configure the system, how users interact with it, and how the platform handles data and integrations.

This article walks through the Manage-specific changes in MAS 9.2, covering the new Alerts and Ticketing framework, the enhanced Inspection Forms capabilities, the Dashboards functionality, improvements to email processing and system logic, the security and user management updates, and the database and platform currency changes that administrators need to plan for. These are not incremental cosmetic updates. Several of them change how existing workflows operate and require administrator attention during and after the upgrade process.

Whether you are already on MAS 9.x and planning a feature channel update to 9.2, or you are preparing a migration from 8.x, understanding what changed in Manage will help you prioritize your post-upgrade configuration work and prepare your users for new functionality.

The New Alerts and Ticketing Framework

MAS 9.2 introduces a new Alerts function in Maximo Manage, and with it comes a new underlying record and application called a Ticket. This is not to be confused with the existing Service Request or Incident ticket types in Maximo. The Alerts framework is a new construct designed to surface conditions that require attention based on thresholds, rules, or AI-driven triggers.

When a condition or threshold is exceeded, an Alert can be generated automatically. The Alert record captures the context of the condition, including the asset or location involved, the metric or event that triggered it, and the relevant historical data. From there, action can be taken by a user or by an AI agent through the MCP Server.

The integration between Alerts and the AI capabilities of MAS 9.2 is where this becomes significant for administrators. Condition Insight, the flagship AI capability in 9.2, can generate Alerts based on its analysis of asset data. When Condition Insight identifies a pattern that suggests a developing issue, it can create an Alert that surfaces that insight to reliability engineers or maintenance planners. The Alert includes the AI-generated explanation of the condition, the recommended corrective action, and the relevant failure mode from the asset's FMEA.

For administrators, this means there is a new application to configure, new security groups to manage, and new notification templates to set up. The Alerts application needs to be added to security groups for the users who should see and act on alerts. Notification templates need to be created if you want alerts to trigger emails or other notifications. And the conditions that generate alerts need to be defined, whether they come from Condition Insight, from Monitor, or from manual threshold rules.

The Ticket framework also introduces new automation script opportunities. Administrators can write automation scripts that trigger on Alert creation, enabling custom workflows for alert routing, escalation, and auto-resolution. This is particularly useful for organizations that want to integrate alerts with their existing enterprise notification systems or IT service management platforms.

Administrators should also be aware of the relationship between Alerts and the existing Work Order system. One of the key capabilities of the Alert framework is the ability to generate a Work Order directly from an Alert. When an Alert is generated by Condition Insight, the system can recommend the most appropriate job plan based on the identified failure mode, and users can create a Work Order with the Summary and Description fields pre-populated with the recommended actions and insights. This creates a closed loop from detection to action that previously required manual interpretation and data entry.

Enhanced Inspection Forms

Inspection Forms receive a significant update in MAS 9.2, and the changes address some of the most common pain points that inspectors and administrators have raised since the feature was introduced. Several of these changes are based directly on client feedback, which means they solve real-world problems rather than theoretical ones.

The first change is organizational scoping. Inspection Forms can now be created for specific Organizations, specific Sites, or both. Previously, forms were more broadly scoped, which created challenges for organizations with multiple sites that had different inspection requirements. If left blank, the form remains available to any Org or Site defined in the MAS Manage instance, preserving backward compatibility. This gives administrators fine-grained control over which forms appear for which inspectors, reducing clutter and ensuring that inspectors only see forms relevant to their location.

The second change is attachments. Inspection Forms can now have attachments associated with them, and these attachments are made available to the inspector when they start the form. This is particularly valuable for providing reference materials such as safety procedures, equipment manuals, or visual guides. Administrators can attach PDF documents, images, or other reference materials to the form, and inspectors can access them without leaving the inspection workflow.

The third change is calculated responses. A response can now have a value calculated from meters or other asset and location related fields using Maximo Formulas. This eliminates the need for inspectors to manually perform calculations, reducing errors and saving time. For example, a form could automatically calculate the difference between a current meter reading and the previous reading, or compute a ratio based on two meter values, and populate the response field automatically. Administrators configure the formula when building the form, and the system handles the calculation at inspection time.

The fourth change is QR and barcode scanning. Inspectors can now scan QR codes or barcodes and have the values appear directly in a response field. This is a significant improvement for asset verification workflows where inspectors need to confirm they are inspecting the correct asset. Instead of manually entering asset numbers or searching through lists, inspectors scan the code on the asset and the system populates the field. This reduces transcription errors and speeds up the inspection process.

The fifth change is geolocation. Inspection forms can now capture geolocation data if the MAS Manage system is attached to a map server. When the inspector starts the form, the system can capture their GPS coordinates and associate them with the inspection record. This is valuable for organizations that need to verify inspection locations, particularly for distributed assets like pipelines, transmission lines, or remote facilities.

For administrators, these changes mean that existing Inspection Forms may need to be reviewed and updated to take advantage of the new capabilities. Forms that were previously shared across all sites may benefit from being scoped to specific sites. Forms that required manual calculations should be updated with formula-based responses. And forms that could benefit from barcode scanning or geolocation should be updated to include those field types.

Dashboards and Mobile Dashboards

Dashboards are a new function in MAS Manage, and with the release of MAS 9.2, there is now a Mobile Dashboard as well. The Dashboards capability gives administrators and users the ability to create configurable, role-based views of key metrics and operational data without requiring custom application development or external reporting tools.

The APM Dashboard is the most prominent example. An Assets and Locations dashboard is installed by default for all Manage users in 9.2, and it includes pre-configured health scores, performance KPIs, and analysis tools ready to use on day one. This dashboard helps users determine the health of their assets and the risk of failure to their business without requiring custom configuration. For administrators, this means that users immediately have access to meaningful operational data after the upgrade, without a lengthy configuration effort.

The dashboard system is configurable by role or use case. Different teams can view asset performance in ways that are relevant to them. Reliability engineers can see health scores and failure probabilities. Maintenance managers can see backlog, overtime, and cost metrics. Operations can see availability and downtime data. This role-based approach means a single dashboard framework serves multiple constituencies without requiring separate reports for each.

The Mobile Dashboard extends this capability to the field. Technicians and inspectors can access dashboards from their mobile devices, giving them visibility into asset health, work order status, and operational metrics while on site. This is particularly valuable for field service teams that need context about the assets they are working on but do not have access to a desktop computer.

For administrators, the dashboard configuration work involves understanding the available data sources, defining the metrics that matter to each role, and configuring the dashboard layouts. The pre-configured APM dashboard provides a starting point, but most organizations will want to customize dashboards for their specific KPIs and organizational structure. Security group configuration is also important, as dashboard visibility is controlled through the existing security framework.

Email Processing, Time Zones, and System Logic

MAS 9.2 includes several updates to email processing and queuing that improve reliability and configurability. For administrators who have struggled with email delivery issues in previous versions, these changes are welcome.

One significant update is the support for OAuth2 SMTP authentication for outgoing emails. This is increasingly important as organizations move away from basic authentication for email systems. Microsoft 365, in particular, has been deprecating basic authentication for SMTP, and organizations using M365 for email relay have needed a solution. With OAuth2 support, administrators can configure MAS Manage to authenticate with modern email providers without storing plaintext passwords or using legacy authentication protocols.

Email processing and queuing improvements also address throughput and reliability. The email queue system has been refined to handle higher volumes more gracefully, with better error handling and retry logic. Administrators who have monitored the email queue in previous versions know that stuck messages and queue backups have been a recurring issue. The 9.2 updates improve the queue management capabilities and provide better visibility into email processing status.

Time zone handling has been improved across the system. This may seem like a minor change, but for organizations operating across multiple time zones, it addresses a long-standing source of confusion. Previous versions had inconsistencies in how time zones were applied to different types of date and time fields, leading to scheduling errors and reporting discrepancies. The 9.2 updates standardize time zone logic, making it more predictable and consistent.

Updates to integration points and invocation channels provide more flexibility for external systems communicating with Manage. These changes affect how automation scripts, integration frameworks, and external APIs invoke Manage processes, and administrators responsible for integration architecture should review the updated documentation to understand the new capabilities and any changes to existing integration behavior.

Security, User Management, and Platform Currency

The security model in MAS 9.2 has been tightened, with improvements to the permission framework and user management interface. These changes are part of IBM's broader effort to align MAS with modern security practices and regulatory requirements.

The tightened security permission model affects how administrators configure access to applications, features, and data. Some permissions that were previously broad or implicit have been refined to require explicit assignment. This means that after upgrading to 9.2, administrators should review existing security groups to ensure that users retain the access they need. A post-upgrade security audit is recommended to identify any permission gaps.

User Management and Security UI improvements make it easier for administrators to manage user accounts, security groups, and access controls. The updated interface provides better visibility into user permissions and makes common administrative tasks more efficient. The License Consumption Dashboard has also been improved, giving administrators better insight into how AppPoints are being consumed across the system and which users and applications are driving consumption.

The Improved Data Import functionality streamlines the process of bringing data into Manage. For administrators who regularly perform data migrations, bulk updates, or integrations that use the data import framework, the 9.2 improvements reduce configuration effort and improve error handling.

On the platform currency front, MAS 9.2 brings several significant updates. DB2 12.1 is now supported, as is Oracle 26ai (once on-prem availability is confirmed). BIRT has been upgraded to version 4.21, and Cognos to 12.1. MongoDB 8.0 is supported, and CP4D 5.2 is supported. The platform has also upgraded to Java 25, with Java 21 for MREF. These currency updates matter because they affect supportability, performance, and compatibility with other enterprise systems.

Administrators should plan for the database and platform currency updates as part of their upgrade planning. If you are running DB2 11.5 or Oracle 19c, you will need to plan a database upgrade in addition to the MAS upgrade. The BIRT and Cognos upgrades may affect existing reports, and report validation should be part of your UAT cycle. The Java upgrade is handled by the MAS installation process, but any custom Java code running in the Maximo JVM should be tested against Java 25 compatibility.

E-sig for LDAP enhancement improves the electronic signature integration with LDAP directories, and support for unsupported languages has been added for organizations operating in locales that were not previously covered. Graphite Bidi support and the Focus Menu are UI enhancements that improve usability for specific user populations.

Practical Implications

For administrators planning a move to MAS 9.2, the Manage changes require careful sequencing. Start with the security audit, as permission changes can affect user access immediately after upgrade. Next, configure the new Alerts application and integrate it with your notification and workflow processes. Then update existing Inspection Forms to take advantage of the new scoping, attachment, calculation, and scanning capabilities. Finally, configure dashboards for your key roles and use cases.

If you are coming from MAS 8.x, the database and platform currency changes may require additional upgrade steps. Database upgrades, BIRT report validation, and custom Java code testing should be factored into your timeline. If you are already on 9.0 or 9.1, the feature channel update to 9.2 is simpler, but the security model changes and new applications still require post-update configuration work.

The SAP connector update to use CPI is particularly relevant for organizations using the SAP integration. The CPI-based connector replaces the previous connector technology, and the migration requires planning and testing. Similarly, the Oracle Fusion connector is new in 9.2 and provides integration capabilities for organizations using Oracle Fusion ERP.

Bottom Line

MAS 9.2 is a substantial release for Maximo Manage administrators. The Alerts and Ticketing framework, enhanced Inspection Forms, Dashboards, email processing improvements, security model updates, and platform currency changes collectively represent the most significant Manage update since the initial 9.0 release. Administrators should approach the upgrade with a post-upgrade configuration plan that prioritizes security validation, Alerts setup, Inspection Form updates, and dashboard configuration. The platform currency changes require attention to database, reporting tool, and Java compatibility. For organizations that have been waiting for a reason to move to 9.x, the Manage improvements in 9.2 provide practical, operational value that justifies the upgrade effort beyond the AI headline features.