IBM Maximo Application Suite 9.2: The Practical Updates Worth Knowing

By MORE by Naviam AI Summary — based on the More by Naviam podcast episode with Steven Shull and Phil Runion.
‍

IBM ships a new version of Maximo Application Suite about once a year, usually somewhere around June, give or take. Every release lands as a mix of headline features, quieter enhancements, and behind-the-scenes plumbing that most people never see.
‍

With MAS 9.2, the updates that stand out aren't the flashy ones. They're the practical ones.

TL;DR

MAS 9.2 isn't defined by one big feature. It's a stack of practical changes that, together, make Maximo easier to administer, support, and use. The highlights:

• Email gets more reliable — SMTP queuing so messages aren't lost when the mail server is down, plus SMTP OAuth support and a configurable send-from address for scheduled reports
• User management moves into Maximo Manage — the separate Mongo-based suite-level user record goes away, which simplifies admin work and environment refreshes
• Fewer workarounds — communication templates replace YAML-based MAS Core comms, and behaviors like auto-populating an asset from a location become organization-level settings
• Operational Dashboards keep maturing — charts, work queues, embedded content like Power BI, and actions that let users do work, not just view it
• Maximo Mobile is easier to stand up — QR-code setup, better traffic routing, mobile dashboards, and visual inspection
• Better supportability — thread IDs and pod names in logging, and a new 200-row default table download limit to protect performance
• Upgrade advice: test it early in non-production, but don't rush the first release into production.
  ‍

On a recent episode of More by Naviam, Steven Shull and Phil Runion walked through the 9.2 features that matter most to the people actually living in Maximo every day — admins, support teams, cloud providers, planners, supervisors, technicians, and the power users who keep everything moving. Here's what stood out.

Why MAS 9.2 matters

The direction of this release comes down to one line: more of Maximo's control is moving back to where Maximo people already work.
‍

That's a bigger deal than it sounds. Most Maximo teams are comfortable in Maximo Manage. They know users and security groups, communication templates, automation scripts, object structures, system properties, escalations, cron tasks, reports, and integrations. They are far less comfortable editing YAML files in OpenShift or chasing user records across suite-level synchronization. So every time MAS 9.2 takes something that used to require platform-level work and turns it into a setting inside Manage, that's a win for the people doing the day-to-day administration.
‍

Steven and Phil also noticed how many of these changes look like they came straight out of real customer feedback through the IBM Ideas Portal. That's worth saying out loud: if your organization has a recurring Maximo pain point, submitting and voting on ideas seems to influence what shows up in future releases. Dark mode is a good example of the kind of request IBM is clearly hearing. It's not in 9.2, but the interest is loud. And for anyone who's had to log into Maximo at two in the morning, dark mode cannot come soon enough.

What admin changes reduce the old workarounds?

Administrative simplification is the strongest theme in 9.2, and user management is the cleanest example.
‍

In earlier versions of MAS, a user could exist in two places: Maximo Manage and a separate Mongo-based suite-level record. That split created real friction, especially during a production-to-non-production refresh. Anyone who's refreshed prod into dev, test, or training knows the checklist is long — users, passwords, authentication, integrations, endpoints, cron tasks, system properties, environment-specific settings. Adding a second user record outside of Manage just made it longer.
‍

In MAS 9.2, that Mongo-based user record goes away, and user management moves more fully into Maximo Manage. For long-time admins, that means working with the tools and processes they already know, which also makes bulk user updates more straightforward instead of forcing teams to reconcile multiple layers.
‍

The same idea shows up in communications. MAS 9.2 moves away from YAML-based MAS Core communications toward Maximo communication templates. That sounds technical, but the payoff is simple: admins already know communication templates. They know how to edit the message, manage recipients, use substitution variables, and switch a template on or off. YAML in OpenShift is a different world, and in a lot of organizations Maximo admins don't even have OpenShift access — that work sits with an infrastructure or platform team. Pulling these communications into Manage hands control back to the people who actually administer the system.
‍

There's also a smaller change that's easy to underrate. For years, Maximo has automatically populated an asset when a user enters a location that only has one asset tied to it. Some organizations love that behavior. Plenty of others have fought it with automation scripts and other workarounds. In MAS 9.2, it becomes an organization-level setting. That's exactly where a behavior like that belongs.

What's new with email and reporting in MAS 9.2?

Email is never the exciting part of a Maximo release, but it's one of the most important. Maximo leans on email for workflows, escalations, approvals, notifications, scheduled reports, and a long tail of business processes. When it works, nobody thinks about it. When it breaks, everybody notices.
‍

MAS 9.2 adds three changes here that solve problems teams have long had to work around in the field:

• SMTP email queuing when the mail server is unavailable. In older versions, if Maximo tried to send while the mail server was down or unreachable, that message could simply be lost. That's a problem for anyone, and especially for organizations on Microsoft 365, Google, SendGrid, Amazon SES, or other cloud email services. Naviam has historically stood up extra infrastructure to handle queuing, logging, and availability, so having more of that capability inside Maximo itself is a meaningful step
• SMTP OAuth support. As basic authentication keeps getting phased out or discouraged by the major providers, OAuth stops being optional. This keeps Maximo aligned with modern email security instead of fighting it
• A configurable "send from" address for scheduled reports. Previously, scheduled reports could go out as the user who scheduled them. That breaks down fast — the user might not have permission to send through the SMTP server, they might leave the company, or their address might trip spam filtering. Setting a shared system address through a system property is cleaner, and it's one more workaround replaced by a setting
  ‍

That last point is the pattern to watch across this whole release. The changes admins like best are usually the ones that turn a workaround into a checkbox.

How do Operational Dashboards and the UI improve?

Start Centers have been part of Maximo for a long time, plenty of organizations still rely on them, and they aren't disappearing overnight. But they get messy. A large environment can accumulate a pile of Start Center templates, result sets, KPIs, and portlets that becomes hard to manage and tune.
‍

Operational Dashboards are the more modern path forward, and in MAS 9.2 they keep getting better — charts, work queues, embedded content, and actions. The actions piece is the part worth noting first, because a dashboard shouldn't just show information, it should help users do something with it. A supervisor approving work orders, a service desk manager reviewing open tickets, a maintenance manager watching backlog, a planner looking at upcoming work — work queues support those jobs in a more action-oriented way than a traditional Start Center result set ever did.
‍

Phil also called out embedded content, like Power BI reports. That opens up some real possibilities when an organization wants Maximo users to see operational data and external analytics in one place instead of jumping between tools.
‍

Two more things worth noting:

• Role-based applications keep maturing. Some of the newer apps look ready for broader use, particularly around administration, users, and security. Others, like Work Order Tracking, deserve more planning for organizations with customizations, industry solutions, or complex work processes. The direction is clear, though — IBM keeps making these apps more capable
• Focus mode. When a user has access to dozens of applications, the left navigation gets crowded fast. Focus mode lets users narrow it down to the apps they actually use. It's a small thing, and it's the kind of small thing people will use every day

What changed in Maximo Mobile?

Maximo Mobile picks up several updates in 9.2, and the most practical one is QR-code-based setup.
‍

Anyone who's helped users configure the mobile app knows setup is one of the first places things go sideways. People don't know which URL to enter. They use the Manage URL instead of the mobile endpoint. They mistype it. They aren't sure which environment they're supposed to connect to. QR-code setup takes most of that guesswork off the table, which matters a lot for technicians and field users who just need to get into the app and start working.
‍

A few other mobile improvements stood out:

• Better mobile traffic routing, which Phil noted is especially valuable for medium and large deployments. As more technicians come onto Maximo Mobile, being able to route or separate that traffic more intentionally helps with scaling, performance, and troubleshooting
• Mobile dashboards. Field users don't want to bounce between a stack of disconnected apps. They want a clear starting point. A dashboard-style experience can surface assigned work orders, inspections, service requests, and other tasks in one place
• Visual inspection from the mobile app, which ties Maximo Mobile more closely to Maximo Visual Inspection. A technician can take a photo and use a model to help identify a crack, a defect, an abnormal condition, or some other issue. Not everyone will turn this on right away, but it's a good signal of where the broader suite is headed — mobile execution, inspections, AI, and asset management working together out in the field

What about logging, downloads, and supportability?

A handful of 9.2 changes are really about protecting performance and making troubleshooting less painful.
‍

The one users will notice first is the new default table download limit of 200 rows. Some people won't love that at first, and that's understandable. But large list-tab exports can cause serious performance problems, and a list-tab download was never meant to be a bulk data extraction tool. For larger data needs, the right tools are reports, integrations, object structures, APIs, or database queries — something more controlled. The limit is adjustable, but the intent is clear: keep users from accidentally creating a performance problem.
‍

On the support side, MAS 9.2 adds thread IDs and pod names to logging. Thread IDs make it easier to group related log entries, and pod names tell support teams where something actually happened in an OpenShift environment. These aren't glamorous features, but anyone who's spent a night digging through logs knows that a small improvement in traceability can save hours.

Should you upgrade to MAS 9.2 right away?

Steven's advice on the episode was simple: start testing early, but don't rush the first release straight into production.
‍

There's a lot to like in 9.2, and most organizations should begin evaluating it now. But Maximo upgrades need real testing, especially when an environment includes custom applications, automation scripts, integrations, mobile users, industry solutions, large data volumes, or complex workflows. The smart approach is to install MAS 9.2 in a non-production environment, test the configuration, explore the new features, and find the issues before building a production rollout plan.
‍

That's not being overly cautious. That's just good Maximo practice.

Key takeaways

• SMTP email queuing helps prevent lost messages when the mail server is unavailable
• SMTP OAuth 支持使 Maximo 与现代电子邮件安全保持一致
• 可配置的计划报告发件人地址取代了常见的变通方法
• 用户管理更全面地整合到 Maximo Manage 中，基于 Mongo 的用户记录将被移除
• 通信模板取代了更难管理的 YAML 配置
• 运营仪表板作为启动中心的替代方案持续成熟，现在支持操作和嵌入式内容
• 基于角色的应用程序功能持续增强
• 专注模式简化了拥挤的左侧导航栏
• 组织级设置取代了多个旧的自动化脚本变通方法
• Maximo Mobile 设置通过二维码配置变得更简单，此外还改进了流量路由、移动仪表板和可视化检查
• 线程 ID 和 Pod 名称改进了日志记录和可支持性
• 新的 200 行默认表格下载限制保护了性能，并且可调整
• MAS 9.2 值得尽早测试，但请谨慎规划生产环境升级

‍

‍

关于 MAS 9.2 的常见问题

IBM Maximo Application Suite 9.2 何时发布？

‍IBM 通常每年年中发布一次 Maximo Application Suite 的新版本。MAS 9.2 遵循这一模式，延续了 IBM 的年度发布节奏。

MAS 9.2 中最大的变化是什么？

‍最具影响力的变化包括SMTP邮件队列和OAuth支持、用户管理完全迁移至Maximo Manage（移除了基于Mongo的套件级用户记录）、通信模板取代了基于YAML的MAS Core通信、操作仪表板的持续改进、通过二维码简化Maximo Mobile设置，以及通过线程ID和Pod名称实现更好的日志记录。

MAS 9.2是否移除了独立的Mongo用户记录？

‍是的。在MAS 9.2中，基于Mongo的套件级用户记录被移除，用户管理更全面地整合到Maximo Manage中。这简化了管理，并使环境刷新和批量用户更新变得更容易。

MAS 9.2包含了哪些邮件改进？

‍MAS 9.2增加了SMTP邮件队列功能，确保邮件服务器不可用时消息不会丢失；支持SMTP OAuth，以满足现代邮件安全要求；以及一个系统属性，用于控制计划报告的“发件人”地址。

MAS 9.2中的操作仪表板和启动中心有什么区别？

‍启动中心是Maximo长期以来的主页体验，目前仍可使用，但在大型环境中可能会变得杂乱。操作仪表板是更现代的选择，在9.2版本中，它支持图表、工作队列、Power BI等嵌入式内容，以及允许用户直接执行操作而非仅查看信息的各种功能。

为什么MAS 9.2将表格下载限制为200行？

‍大型列表标签导出可能会导致严重的性能问题，而且列表标签下载并非用于批量数据提取。200行的默认限制降低了这种风险。此限制可调整，对于更大的数据需求，组织应使用报告、集成、对象结构、API或数据库查询。

我应该立即升级到MAS 9.2吗？

‍尽早开始在非生产环境中进行测试，但不要将第一个版本直接投入生产环境。测试配置，验证定制、集成、移动功能和工作流程，然后制定生产部署计划。

‍

‍

结语

MAS 9.2并非以某个单一的、引人注目的重大功能为亮点，但这并无不妥。其引人之处在于它的实用性。它将更多控制权重新交给了Maximo Manage。它清除了过去的一些权宜之计。它改进了邮件处理。它简化了移动设置。并且为管理员在需要支持和故障排除时提供了更好的工具。
‍

Maximo团队一旦开始使用，就会喜欢上这种发布版本。Steven和Phil的建议是：先在非生产环境中进行测试。
‍

正在考虑MAS 9.2，还是在规划下一次Maximo升级？ Naviam可以帮助您 评估对您的环境至关重要的因素，测试新版本，并制定一个实用的升级计划，从而降低风险，同时帮助您的团队充分利用MAS 9.2的所有功能。