MAS 9.2 Is Here: What Maximo Teams Need to Know About the Latest Upgrade

IBM Maximo Application Suite 9.2 became generally available on June 25, 2026, marking the second major release since MAS 9.0 launched in June 2024. If 9.0 was the foundation and 9.1 was the expansion, 9.2 is the maturation. The release does not reinvent the platform. Instead, it refines AI capabilities, stabilizes mobile and admin workflows, updates the underlying infrastructure stack, and introduces a continuous delivery model through the Feature Channel that changes how teams consume updates.

For organizations still on Maximo 7.6.1.x, the clock has already run out. Standard support ended September 30, 2025. For those on MAS 8.10 or 8.11, standard support ended April 30, 2026. MAS 9.2 is not an optional upgrade. It is the current baseline, and the Feature Channel model means the platform will keep evolving incrementally rather than through annual big-bang releases. This article walks through the key changes, what they mean for your environment, and how to plan the transition.

We will cover the Feature Channel delivery model, AI upgrades including the shift from Granite to GPT-OSS-120B, platform infrastructure changes, Manage usability improvements, mobile and field service enhancements, and what the upgrade path looks like for organizations coming from 9.1 or earlier. Whether you are actively planning an upgrade or evaluating whether to wait, this guide gives you the technical detail to make that decision. We will also look at known issues that IBM has documented through the Feature Channel releases, so you can plan around them rather than discovering them during your upgrade window.

The Feature Channel Delivery Model

MAS 9.2 introduces a fundamentally different approach to how IBM ships updates. Instead of waiting for a major release once a year, the Feature Channel delivers monthly capability drops that organizations can evaluate in non-production environments before they land in a production release. This means the gap between "IBM announces a feature" and "you can use it" shrinks dramatically.

The Feature Channel is available to customer-managed installations and allows teams to preview new capabilities ahead of general availability. IBM has been releasing Feature Channel updates approximately monthly. For example, the April Feature Channel shipped on April 30, 2026, and the June Feature Channel shipped alongside the 9.2.0 GA on June 25, 2026. Each drop includes documentation references (such as IBM Reference #7277376 for MAS Core 9.2.0) that administrators can use to trace exactly what changed. The Feature Channel covers all major applications: MAS Core, Manage, AI Service, Monitor/IoT, Predict, Maximo Visual Inspection, and Real Estate and Facilities.

For upgrade planners, this model has significant implications. First, you no longer need to wait for a major release to evaluate new features. You can point a non-production environment at the Feature Channel and test incrementally. Second, the GA release is essentially a snapshot of the Feature Channel at a point in time, stabilized and fully documented. Third, your upgrade strategy should shift from "upgrade once a year" to "continuously evaluate and adopt."

The practical approach is to maintain at least two environments: one on the current GA release for production, and one tracking the Feature Channel for evaluation. This requires discipline around environment management, but it reduces the risk of surprises during a major upgrade. Organizations that adopted this pattern during the 9.1 Feature Channel period reported smoother transitions to 9.2 because they had already tested the features in advance.

One important note: the Feature Channel is not a replacement for fix packs. Security updates and bug fixes continue to ship through the regular Operator Catalog updates. The Feature Channel is specifically for new capabilities. If you are on MAS 9.1, you continue to receive monthly fix packs (9.1.14 in March 2026, 9.1.16 in April, 9.1.18 in May, 9.1.19 in June) alongside the 9.2 track. This dual-track approach means organizations on 9.1 are not left behind while 9.2 matures. You can stay on 9.1, receive security patches, and evaluate 9.2 features through the Feature Channel before committing to the upgrade.

AI Upgrades: From Granite to GPT-OSS-120B

The most significant technical shift in MAS 9.2 is the AI model upgrade. In the January 2026 Feature Channel release, IBM confirmed that the openai/gpt-oss-120b model is replacing ibm/granite-3-2-8b-instruct for PCC (Prediction, Classification, and Clustering), MCC, and FMEA workflows. The Granite model was deprecated in February 2026. This is a notable shift for organizations that had tuned their AI workflows around the Granite model's behavior.

This change affects several AI-powered features across the suite:

• FMEA Content Builder: The generative AI tool that automates Failure Modes and Effects Analysis content creation now runs on the larger GPT-OSS-120B model, which produces more nuanced failure mode descriptions and mitigation recommendations. For reliability engineers using the Reliability Strategies add-on, this means the AI-generated FMEA content is more detailed and contextually accurate.
• Similarity Tracker: The work order comparison engine that identifies recurring issues benefits from the larger model's improved pattern recognition. This helps maintenance teams identify recurring problems faster, reducing mean time to resolution.
• Maximo Assistant: The conversational AI that allows natural-language queries against work orders, assets, and service requests sees improved response quality and accuracy. IBM reported that this approach helped save approximately 10,000 hours annually across roughly 200,000 work orders in 2025.

The Maximo AI Service acts as the bridge between Maximo and watsonx. IBM trains the models to understand Maximo's data model, asset management concepts, and condition-based maintenance principles. The models are hosted within the Maximo ecosystem, and organizations are entitled to watsonx through the AI Service license. This is not a bring-your-own-model setup. The AI is trained specifically on Maximo concepts.

MAS 9.2 also introduces Maximo Condition Insight, an agentic AI capability that evaluates work orders, metrics, time-series data, meter readings, FMEA data, and alerts to produce explainable summaries of asset condition. Unlike standalone AI tools, Condition Insight integrates directly into maintenance workflows. It can recommend whether to proceed with or defer upcoming work based on current asset state. This is not a chatbot. It is an AI agent that participates in the condition-based maintenance workflow. Powered by IBM watsonx, Condition Insight communicates its findings in plain language, making AI practical for maintenance teams that do not have data science expertise.

Looking forward, IBM has announced four AI agents that, when combined, will create a fully automated condition-based maintenance workflow: a monitoring agent that watches asset state continuously, an analysis agent that interprets patterns in the data, a recommendation agent that suggests actions, and an execution agent that generates work orders. These agents are being introduced incrementally through the Feature Channel. The MCP Server capability in 9.2 also allows organizations to bring their own agents and integrate them directly with Maximo Manage APIs, enabling AI to participate in existing operational processes without manual coordination between disconnected tools.

Platform Infrastructure and Compatibility

MAS 9.2 updates the underlying technology stack to stay current with enterprise infrastructure standards. The key platform changes include:

• OpenShift 4.19 support: MAS 9.2 is certified for Red Hat OpenShift Container Platform 4.19, giving organizations access to the latest Kubernetes features, security patches, and scalability improvements. For organizations on older OpenShift versions, this may require an OpenShift upgrade before or alongside the MAS upgrade.
• MongoDB 8.0 support: The database layer now supports MongoDB 8.0, which brings performance improvements in query processing and memory management. If you are running MongoDB 6.0 or 7.0, plan the database upgrade as a prerequisites step.
• Operator Catalog updates: The IBM Maximo Operator Catalog (v9-260326 for the March 2026 build, v9-260129 for the January build) includes updates across all applications. The catalog now supports IBM Power (ppc64le) architecture for industry solutions and add-ons, including Maximo Asset Configuration Manager, Maximo Reliability Strategies, Maximo IT, and Maximo Vegetation Management. This is particularly relevant for utilities and infrastructure organizations running on Power infrastructure.
• OAuth2 authentication: Full OAuth support for SMTP email handling and integration endpoints. This was backported to 9.0 and 9.1 as well, but 9.2 makes it the default pattern. The endpoints application in Maximo Manage now supports OAuth client configuration, and a system property controls which OAuth client to use. At the suite level, OAuth can also be configured for suite-wide integrations.
• Java 17: MAS 9.2 continues on the Java 17 foundation introduced in 9.0. For organizations coming from 7.6.1.x, this is a significant jump. The removal of Nashorn (the JavaScript engine) and changes to the API surface require automation script review. Any scripts using Nashorn-compatible JavaScript syntax will need to be rewritten or replaced.

The SMTP email handling improvements deserve specific attention. MAS 9.2 introduces email queuing within the Maximo instance, which complements the existing delivery service. Previously, email failures could silently drop messages. The new queuing mechanism ensures emails are retried and logged, addressing a long-standing pain point for integration teams. Additionally, the send-from address on scheduled reports can now be configured independently, rather than always sending as the user who scheduled the report.

For airgap environments, the Operator Catalog supports disconnected installation with preloaded databases. However, known issues exist with Maximo Real Estate and Facilities in airgap scenarios, where installation can be slow. If you are running MREF, plan extra time for the upgrade. A known issue in the March 2026 release also affects MREF upgrade scenarios from 9.1.x to 9.2 Feature Channel, with users encountering failures during upgrade scenarios.

Maximo Manage Usability Improvements

MAS 9.2 brings a series of incremental but meaningful improvements to Maximo Manage. These are not headline features, but they address common pain points that administrators and users deal with daily. Collectively, they reduce administrative overhead and improve the day-to-day user experience.

User management consolidation: In 9.2, the Manage-level user record is eliminated entirely. User management is consolidated at the suite level. This means bulk updates to user records can be performed through the Manage database using standard tools, and the synchronization issues between suite-level and Manage-level user records are resolved. For organizations with hundreds or thousands of users, this eliminates a significant administrative burden. The user management changes that began in 9.1, where many user management functions moved to Manage, are completed in 9.2.

Operational Dashboards: The Operational Dashboards introduced in 9.1 continue to expand in 9.2. New capabilities include the ability to add attachments to dashboard widgets, embed iframes for external content, and use the single work queue as a replacement for result sets. Users can now configure their left-hand navigation, giving them control over their own workspace layout. This is a meaningful shift from the rigid Start Center model, allowing personalized workflows without administrator intervention.

Work order and PM improvements: Work order description generation can now be controlled at the organization level and at the PM level, rather than only at the global level. This means different organizations or PMs can have different description formats. If a PM should generate work orders with the description on the last day versus the first day, that is now configurable per PM. This level of granularity has been requested by the community for years.

Asset-location behavior: A long-requested feature is the ability to prevent an asset from auto-populating when a location is specified on a work order. If a location has one and only one asset, Maximo historically auto-populated the asset field going back to at least version 5. In 9.2, this behavior can be controlled, giving organizations flexibility in how they handle single-asset locations.

Logging improvements: Pod names are now tracked in log entries. When ingesting logs into Elasticsearch or similar systems, you can identify which pod generated each entry. This is a small change with significant operational impact for troubleshooting distributed MAS installations. The default query limit has also changed from unlimited to 200 out of the box, which prevents accidental full-table scans in large environments.

Mobile and Field Service in 9.2

MAS 9.2 continues to build out Maximo Mobile as a more complete field solution. While mobile features are covered in depth in our Mobile and Field Service coverage, the platform-level implications are worth noting here. The 9.2 release includes QR code scanning for materials and assets directly from the mobile app, improved task execution and failure reporting, support for crew management and location-based work, and expanded inspection capabilities including AI-powered visual inspection with local inference on the device.

The Mobile Admin section in MAS Administration now allows centralized management of mobile settings, data synchronization, preloaded database content, and query limits. Administrators can identify which users are actively logged into Maximo Mobile, providing better oversight and support capacity. Push notification support has been extended with background data synchronization, ensuring field teams receive updates without interrupting their work.

For platform administrators, the mobile deployment story in 9.2 is significantly more stable than in 9.1. Several bugs that affected MAF app configuration publishing and deployment have been resolved. The superuser profile editing failures that blocked some admin workflows have been fixed. These are the kind of fixes that do not make roadmap presentations but matter enormously to the teams running the platform.

Planning Your Upgrade Path

The upgrade path to MAS 9.2 depends on your current version. Here is what each scenario looks like:

From MAS 9.1: This is the most straightforward path. Apply the 9.2.0 update through the Operator Catalog. Review the Feature Channel notes to understand which features are now GA. Test your automation scripts for compatibility with the new AI model. If you are using Maximo Health as a standalone application, note that it is now an add-on within Maximo Manage. You must add Maximo Health as an add-on in Manage 9.0 or 9.1 before upgrading to 9.2. Also note that Maximo Assist has been renamed to Maximo Collaborate. The name change reflects automatically in the UI after upgrade.

From MAS 9.0: Similar to 9.1, but you may need to address more cumulative changes. Review the 9.1 release notes for features that were added between 9.0 and 9.2. The TRIRIGA integration (now Maximo Real Estate and Facilities) was introduced in 9.1. If you have TRIRIGA, plan for the rename and integration changes. The Maximo Asset Investment Planning add-on, introduced in 9.1, is also available in 9.2.

From MAS 8.10 or 8.11: Standard support ended April 30, 2026. You need to upgrade to MAS 9.0 first, then to 9.2. This is a major jump. The Java 17 migration, container architecture changes, and AppPoints licensing model all require careful planning. IBM recommends engaging with their upgrade services or a certified partner. The 8.x to 9.x transition involves significant data model changes, automation framework updates, and infrastructure redesign.

From Maximo 7.6.1.x: Support ended September 30, 2025. You are running on an unsupported platform with no security patches. The migration to MAS 9.2 is not an upgrade. It is a reimplementation. Plan for data migration, automation script rewrites, integration reconfiguration, and user retraining. IBM's migration tools and services can help, but this is a multi-month project. The technical leap includes Java 17, removal of Nashorn, API changes, container-based deployment, and the shift from traditional licensing to AppPoints.

For all upgrade paths, the AppPoints licensing model applies. AppPoints provide flexibility in how licenses are consumed across the suite. Dual licensing (traditional plus AppPoints) is available until 2027, after which full support for legacy licensing retires. If you have not already transitioned to AppPoints, plan for that as part of your upgrade.

Known Issues and Watch Items

Through the Feature Channel releases leading up to 9.2 GA, IBM documented several known issues that upgrade planners should be aware of. The January 2026 release (9.1.8) had an issue affecting HSE and Oil and Gas solutions. Customers with HSE installed were advised to avoid upgrading to the January release, and installation of HSE or Oil and Gas on Manage 9.0.x or 9.1.x was deferred until the February 2026 patch. The February 2026 release had an issue affecting Maximo Real Estate and Facilities, where customers with MREF installed were advised to avoid the 9.1.8 release. The March 2026 release documented failures during MREF upgrade scenarios from 9.1.x to 9.2 Feature Channel, along with slow installation in airgap environments.

Additionally, customers using Maximo Assist v8.7 or v8.8 were flagged to not update and instead contact IBM Support for guidance regarding the removal of IBM Watson Discovery and the upgrade path to Maximo Collaborate v9.0. These issues underscore the importance of reading the release notes for your specific application stack before initiating an upgrade. The Feature Channel model helps here because you can test in non-production first, but only if you actually do the testing.

Practical Implications

For Maximo administrators and IT teams, MAS 9.2 changes three things about how you operate. First, the Feature Channel means you should shift from annual upgrade planning to continuous evaluation. Stand up a non-production environment on the Feature Channel and test monthly drops. This reduces risk and shortens the path to adoption. Second, the AI model change from Granite to GPT-OSS-120B means any custom AI workflows or prompts may produce different results. Test your existing AI-powered automations against the new model before deploying to production. Third, the user management consolidation eliminates a long-standing administrative headache. Plan to migrate your Manage-level user records to suite-level management as part of the upgrade.

For organizations on 7.6.1.x or 8.x, the message is clear: you are on unsupported software. MAS 9.2 is a mature, stable platform with significant AI, mobile, and integration capabilities. The longer you wait, the more technical debt you accumulate. Start planning now. Engage with IBM or a certified partner, scope the migration, and budget for the project. The AppPoints model gives you flexibility to start with what you need and scale as you grow. The Feature Channel means you will not face another massive upgrade gap, because updates arrive continuously.

Bottom Line

MAS 9.2 is not a dramatic departure. It is a solid, incremental release that matures the platform. The Feature Channel delivery model, AI model upgrade, infrastructure updates, and Manage usability fixes together represent a meaningful step forward. The known issues documented through the Feature Channel releases are being addressed proactively, and the continuous delivery model means fixes arrive monthly rather than requiring a full upgrade cycle. Organizations already on 9.1 should plan to upgrade within the next quarter. Organizations on earlier versions should treat this as the trigger to start their migration project. The platform is stable, the AI is practical, and the continuous delivery model means it will keep getting better without requiring major upgrade projects each year.