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
• La prise en charge d'OAuth SMTP permet à Maximo de rester aligné avec la sécurité moderne du courrier électronique.
• Une adresse d'expéditeur configurable pour les rapports planifiés remplace une solution de contournement courante.
• La gestion des utilisateurs est davantage intégrée à Maximo Manage, et l'enregistrement utilisateur basé sur Mongo est supprimé.
• Les modèles de communication remplacent la configuration YAML plus difficile à gérer.
• Les tableaux de bord opérationnels continuent de s'améliorer en tant qu'alternative aux centres de démarrage, désormais avec des actions et du contenu intégré.
• Les applications basées sur les rôles continuent de gagner en capacités.
• Le mode Focus simplifie une navigation latérale gauche encombrée.
• Les paramètres au niveau de l'organisation remplacent plusieurs anciennes solutions de contournement basées sur des scripts d'automatisation.
• La configuration de Maximo Mobile est simplifiée grâce à la configuration par code QR, ainsi qu'un meilleur routage du trafic, des tableaux de bord mobiles et l'inspection visuelle.
• Les ID de thread et les noms de pod améliorent la journalisation et la maintenabilité.
• Une nouvelle limite de téléchargement de tableau par défaut de 200 lignes protège les performances et est ajustable.
• Il est recommandé de tester MAS 9.2 tôt, mais planifiez les mises à niveau de production avec soin.

‍

‍

Questions fréquemment posées sur MAS 9.2

Quand IBM Maximo Application Suite 9.2 est-il publié ?

‍IBM publie généralement une nouvelle version de Maximo Application Suite une fois par an, vers le milieu de l'année. MAS 9.2 suit ce modèle, poursuivant la cadence de publication annuelle d'IBM.

Quels sont les changements majeurs dans MAS 9.2 ?

‍Les changements les plus significatifs sont la mise en file d'attente des e-mails SMTP et la prise en charge OAuth, la gestion des utilisateurs entièrement intégrée à Maximo Manage (avec la suppression de l'enregistrement utilisateur au niveau de la suite basé sur Mongo), les modèles de communication remplaçant les communications MAS Core basées sur YAML, l'amélioration continue des tableaux de bord opérationnels, la configuration plus facile de Maximo Mobile via un code QR, et une meilleure journalisation grâce aux ID de thread et aux noms de pod.

MAS 9.2 supprime-t-il l'enregistrement utilisateur Mongo distinct ?

‍Oui. Dans MAS 9.2, l'enregistrement utilisateur au niveau de la suite basé sur Mongo disparaît, et la gestion des utilisateurs est davantage intégrée à Maximo Manage. Cela simplifie l'administration et facilite les actualisations d'environnement ainsi que les mises à jour d'utilisateurs en masse.

Quelles améliorations en matière de messagerie MAS 9.2 inclut-il ?

‍MAS 9.2 ajoute la mise en file d'attente des e-mails SMTP afin que les messages ne soient pas perdus lorsque le serveur de messagerie est indisponible, la prise en charge OAuth SMTP pour répondre aux exigences de sécurité modernes des e-mails, et une propriété système pour contrôler l'adresse "expéditeur" des rapports planifiés.

Quelle est la différence entre les tableaux de bord opérationnels et les centres de démarrage dans MAS 9.2 ?

‍Les centres de démarrage sont l'expérience d'accueil Maximo de longue date et fonctionnent toujours, mais ils peuvent devenir encombrés dans les grands environnements. Les tableaux de bord opérationnels sont l'option plus moderne et, dans la version 9.2, ils prennent en charge les graphiques, les files d'attente de travail, le contenu intégré comme Power BI, et des actions qui permettent aux utilisateurs d'effectuer des tâches directement plutôt que de simplement consulter des informations.

Pourquoi MAS 9.2 limite-t-il les téléchargements de tableaux à 200 lignes ?

‍Les exportations de listes-onglets volumineuses peuvent créer de sérieux problèmes de performance, et un téléchargement de liste-onglet n'est pas destiné à l'extraction de données en masse. La valeur par défaut de 200 lignes réduit ce risque. C'est ajustable, et pour des besoins en données plus importants, les organisations devraient utiliser des rapports, des intégrations, des structures d'objets, des API ou des requêtes de base de données.

Dois-je passer immédiatement à MAS 9.2 ?

‍Commencez à le tester tôt dans un environnement hors production, mais ne déployez pas la première version directement en production. Testez la configuration, validez les personnalisations, les intégrations, le mobile et les workflows, puis élaborez un plan de déploiement en production.

‍

‍

Réflexions finales

MAS 9.2 n'est pas le genre de version qui se définit par une seule grande fonctionnalité tape-à-l'œil, et c'est très bien. Ce qui la rend intéressante, c'est son aspect pratique. Elle redonne plus de contrôle à Maximo Manage. Elle élimine certaines anciennes solutions de contournement. Elle améliore la gestion des e-mails. Elle facilite la configuration mobile. Et elle offre aux administrateurs de meilleurs outils lorsqu'ils ont besoin de fournir un support et de résoudre des problèmes.
‍

C'est le genre de version que les équipes Maximo ont tendance à apprécier une fois qu'elles commencent à l'utiliser. Le conseil de Steven et Phil : testez-la d'abord en environnement de non-production.
‍

Vous envisagez MAS 9.2 ou planifiez votre prochaine mise à niveau Maximo ? Naviam peut vous aider à évaluer ce qui est important pour votre environnement, tester la nouvelle version et élaborer un plan de mise à niveau pratique qui réduit les risques tout en aidant votre équipe à tirer parti de toutes les fonctionnalités de MAS 9.2.