MAS 9.2 Is Here: What Maximo Teams Need to Know Before Upgrading

# MAS 9.2 Is Here: What Maximo Teams Need to Know Before Upgrading

IBM dropped Maximo Application Suite 9.2 on June 25, 2026, and it is not just another feature channel update. This is the annual major release that sets the platform direction for the next twelve months, and it lands at a moment when many organizations are still running MAS 8.x or early 9.0.x versions. If you have been putting off that upgrade planning session, now is the time to pay attention.

MAS 9.2 is not a radical architectural departure from 9.1. It runs on the same Red Hat OpenShift foundation, uses the same AppPoints licensing model, and preserves the same suite structure. But the changes under the hood, particularly around user management, email infrastructure, reporting, and the new Operational Dashboards, are significant enough that every administrator and platform architect should understand them before the first `oc apply` hits the cluster.

This article walks through what changed, what matters, and what your upgrade planning should account for. It is written for the people who actually do the work: the admins, the architects, and the technical leads who will be in the war room when the upgrade window opens.

The MAS 9.2 Release Landscape

MAS 9.2 shipped on June 25, 2026, alongside a full set of application updates. Here is what landed:

| Application | Version | Key Changes |
|---|---|---|
| MAS Core | 9.2.0 + June Feature Channel | New user management, SMTP OAuth, Operational Dashboards |
| Manage | 9.2.0 + June Feature Channel | Role-based app improvements, attachment support in mobile |
| Maximo Optimizer | 9.2.0 + June Feature Channel | Scheduling enhancements |
| MVI (Visual Inspection) | 9.2.0 + June Feature Channel | Local inference on mobile devices |
| AI Service | 9.2.0 + June Feature Channel | Agentic workflows, MCP Server |
| Monitor/IoT | 9.2.0 + June Feature Channel | Configurable dashboards, drag-and-drop cards |
| Predict | 9.2.0 + June Feature Channel | Condition Insight, health scoring improvements |
| Real Estate and Facilities | 9.2.0 + June Feature Channel | Lease abstraction with RAG |

For organizations still on MAS 8.x, IBM continues to ship patches. MAS Core 8.11.34 landed on April 30, 2026, and Manage 8.6.36 shipped on February 26, 2026. But the writing is on the wall: the innovation investment is going into 9.x, and 9.2 is where the platform is headed.

The Feature Channel Model

One of the most important operational changes in the MAS 9.x lifecycle is the Feature Channel delivery model. Instead of waiting for a single annual release to get new capabilities, IBM now ships monthly feature drops through the Feature Channel. MAS 9.2 itself was preceded by Feature Channel releases in January, February, March, and April 2026, each adding incremental capabilities that culminated in the June GA.

For upgrade planners, this means two things. First, you can evaluate new capabilities in a non-production environment months before they land in a GA release. Second, you need a process for tracking what is in each Feature Channel drop, because the cumulative delta between your current version and 9.2 may include capabilities you have never seen.

The practical approach: subscribe to the IBM Support page for MAS releases (Reference # 7277376 for MAS Core 9.2.0), set up a sandbox OpenShift cluster if you have not already, and start running Feature Channel updates there. The earlier you see what is coming, the fewer surprises you will have during the production cutover.

SMTP and OAuth: The Email Infrastructure Overhaul

For years, Maximo's email configuration has been a source of quiet frustration. SMTP settings were global. Authentication was basic. Scheduled reports always sent from the user who scheduled them, which meant every report scheduler needed a valid email address, and if that user left the organization, reports broke silently.

MAS 9.2 addresses all three of these pain points.

OAuth Support for SMTP

The biggest change: MAS 9.2 supports OAuth 2.0 authentication for outbound email. This matters because Microsoft 365 and Google Workspace have been deprecating basic authentication for years. Organizations that migrated to Exchange Online were forced into workarounds: relay servers, app-specific passwords, or third-party SMTP gateways. None of those were clean.

With OAuth support, you can now configure MAS to authenticate directly against Microsoft 365 or Google Workspace using modern authentication flows. The configuration lives in the MAS administration console under System Configuration, not buried in a properties file.

Here is what the configuration flow looks like conceptually:

code block

The key benefit is not just security. It is sustainability. When Microsoft or Google changes their authentication requirements, you update the OAuth configuration, not your entire email infrastructure.

Send-From Control on Scheduled Reports

MAS 9.2 introduces the ability to configure the "send from" address on scheduled reports at both the organization level and the PM level. Previously, reports always sent from the user who created the schedule. Now you can set a dedicated sender address like `maximo-reports@yourcompany.com` and have all scheduled reports use it.

This is a small change with outsized operational impact. It means:

- Report delivery no longer breaks when users leave the organization
- You can route all report traffic through a monitored mailbox
- DMARC and SPF compliance becomes simpler because you control the sender domain
- You can set different sender addresses per organization in multi-org deployments

SMTP Queuing

MAS 9.2 also introduces SMTP message queuing. In previous versions, if the SMTP server was unreachable when a notification fired, the message was lost. Now, MAS queues outbound email and retries on configurable intervals. This is particularly important for environments where notifications trigger critical workflows, such as PM-generated work orders or SLA breach alerts.

User Management: The End of the User Record as You Know It

This is the change that will generate the most internal discussion. In MAS 9.2, the version of the user record that existed in Maximo Manage goes away entirely.

Historically, Maximo maintained its own user records with attributes like person ID, default insert site, storeroom, labor record, and security group assignments. These records were synchronized with the MAS user directory, but they were distinct entities. In 9.2, user management is fully consolidated into the MAS identity layer.

What this means in practice:

- User attributes that were previously managed in the Users application in Manage are now managed in MAS administration
- Security group assignments move to MAS-level role-based access control
- Default insert sites, storerooms, and other user preferences are configured through organizational settings rather than individual user records
- The labor record linkage is handled through a new association model

The migration path is automated during upgrade, but you should audit your current user configuration before upgrading. Specifically:

1. Identify any automation scripts or integrations that read or write to the MAXUSER, PERSON, or LABOR tables directly
2. Review custom security configurations that depend on user-level attributes
3. Document all user-level default settings (insert site, storeroom, etc.) so you can reconfigure them post-upgrade
4. Test labor reporting workflows, since the user-to-labor linkage changes

Role-Based Application Improvements

Alongside the user management changes, MAS 9.2 improves role-based applications. Administrators can now configure which applications appear for which roles with finer granularity. This is not just about hiding applications; it is about tailoring the user experience so that a technician sees only what they need, a planner sees planning tools, and a reliability engineer sees Health and Predict dashboards.

The configuration is done at the organizational level, not globally, which means different business units can have different role-to-application mappings within the same MAS instance.

Operational Dashboards Replace Start Centers

Start Centers have been a staple of Maximo since the early 2000s. Every user had one. They showed work queues, KPIs, favorite applications, and inbox assignments. They were functional but rigid. Customizing a Start Center meant XML editing and portal configuration that most administrators avoided.

MAS 9.2 introduces Operational Dashboards as the replacement for Start Centers. These are not just a reskin. They are a fundamentally different approach to the landing page experience.

Key differences:

| Feature | Start Centers (Legacy) | Operational Dashboards (9.2) |
|---|---|---|
| Configuration | XML-based, template-driven | Drag-and-drop, card-based |
| Personalization | Limited to portlet arrangement | Personal views per user |
| Data sources | Work queues, KPIs, favorites | Any MAS data source, including Monitor and Health |
| Responsiveness | Desktop-optimized | Responsive across desktop and tablet |
| Sharing | Not shareable | Shareable views across teams |
| Real-time updates | Polling-based | Event-driven where supported |

The migration from Start Centers to Operational Dashboards is not automatic. IBM provides a migration utility, but the recommendation is to treat this as an opportunity to redesign the user experience rather than a lift-and-shift. Start Centers accumulated years of cruft in most organizations. Operational Dashboards give you a clean slate.

A practical migration approach:

1. Identify the top three to five Start Centers by user count
2. For each, list the portlets and data sources users actually use (not just what is configured)
3. Design equivalent Operational Dashboard cards for each data source
4. Build the dashboards in a test environment
5. Run a pilot with a subset of users before rolling out broadly

Upgrade Planning: The Practical Checklist

Upgrading to MAS 9.2 is not a weekend project. Here is a realistic checklist based on what the release changes:

Pre-Upgrade (4-6 weeks before)

- [ ] Audit current MAS version and all application patch levels
- [ ] Review the MAS 9.2 release notes for all installed applications (Core, Manage, Monitor, Predict, Optimizer, MVI, etc.)
- [ ] Inventory all custom automation scripts, especially any that touch user records, email, or Start Centers
- [ ] Document current SMTP configuration and identify the OAuth migration path
- [ ] Export Start Center configurations for reference (even if you plan to redesign)
- [ ] Identify all integrations that use MIF or OSLC and verify compatibility
- [ ] Check OpenShift cluster version compatibility (MAS 9.2 requires a supported OpenShift version)
- [ ] Review AppPoints consumption and ensure licensing covers the new capabilities you plan to enable

Pre-Upgrade (1-2 weeks before)

- [ ] Stand up a sandbox or dev environment running the latest 9.1.x patch level
- [ ] Apply the MAS 9.2 upgrade in the sandbox and run smoke tests
- [ ] Test OAuth SMTP configuration with your email provider
- [ ] Build and test Operational Dashboards for key user groups
- [ ] Run the user management migration and verify role assignments
- [ ] Test all critical integrations end-to-end
- [ ] Run a full regression test on mobile workflows (Maximo Mobile EAM)

Upgrade Window

- [ ] Communicate the maintenance window to all users
- [ ] Take a full backup of

...