Community

What's Actually Happening in the Maximo Community Right Now: Forum Signals, RCM Workshops, and the Practitioner Access Map

The Maximo community in 2026 is in an unusual moment. The platform is in the middle of a structural shift — from classic Maximo to MAS, from per-module licensing to AppPoints, from a scriptable extension model to an AI-augmented one — and the community is where that shift is most visible. People are asking the questions they couldn't ask a year ago, and the answers are converging on a clear picture.

This article reads the signal from the last few months of the IBM Community Maximo forums, the SWMUG (Southwest Maximo User Group) March 2026 product update, the RCM workshop that surfaced the Manage-Monitor-Health-Predict unification, and the practitioner-access paths (certifications, labs, user groups) that actually work.

What people are actually asking in the forums

The Maximo forum on IBM TechXchange is the most active asset-management community in the industry. The threads that are getting the most engagement in mid-2026 cluster around a few topics:

"How do I plan a 7.6 to MAS 9 migration?"

This is the dominant question, and it has been since late 2025. The high-quality answers converge on a pattern that is now standard across the community:

Treat it as a platform transformation, not a version upgrade. The 7.6 → MAS 9 move is not a Maximo upgrade. It is a move from WebSphere on Windows/Linux to OpenShift, from a per-module license model to AppPoints, and from direct SQL access to API-mediated access.
Run an MVP first. Clone the database, run the upgrade activation in non-prod, document every error, fix the data, fix the customizations, fix the integration, and only then repeat the proven process in production.
Plan AppPoints carefully. A 1:1 mapping from 7.6 licensed users to MAS 9 Premium authorized is the most common budget mistake. The right mapping is closer to 60–70% Premium, 25–30% Base, with the rest on Self-Service or Limited.
Database activation is the critical path. Don't start it with dirty data, unresolved Integrity Checker errors, unsupported database versions, pending configuration changes, or active custom triggers.

A 2026 community post by Avinash Kumar on the IBM Community blog lays out the most-cited 7.6 → MAS 9 upgrade checklist. The post has been cross-posted to LinkedIn, the SWMUG site, and partner blogs; it has effectively become the field reference for the upgrade.

"What is the difference between MIF, OSLC, the REST API, and Kafka?"

The second most-asked question, especially from teams taking on the MAS upgrade. The community's answer in 2026 is consistent:

MIF / JMS: legacy, still supported, but increasingly the wrong answer for new work.
MIF / Kafka: the right answer for high-volume outbound event streams.
JSON REST API: the right answer for modern inbound and outbound integrations.
OSLC: still useful for ALM/lifecycle integrations, otherwise subsumed by the REST API.
App Connect: the iPaaS layer for SaaS connectors and visual flow design.

The community reads the IBM performance wiki at ibm-mas.github.io as the authoritative source for the MIF/Kafka scaling data, and references it directly in forum answers.

"How does the AppPoints math actually work?"

A close third. The most useful community resource on this is the partner-published breakdown of concurrent vs. authorized entitlements, the user tier table (Self-Service, Limited, Base, Premium, Admin), and the "what's included" vs. "what costs extra" matrix. The honest community answer: AppPoints can save 15–30% over 7.6 licensing, but only if you do the entitlement work up front.

"What is the RCM story?"

The RCM question has gone from "is Maximo doing RCM?" to "how do I make the FMEA library live in the system?" The community answer is now concrete: use the sfmea template in the AI Service, populate the Reliability Strategies library, and link the FMEA entries to the condition tasks and the predicted failure modes. The 2026 RCM workshop at IBM (reported in a community blog by Stefan Hoffmanns) made the Manage-Monitor-Health-Predict unification visible to practitioners in a way the previous product roadmap hadn't.

The SWMUG March 2026 product update

The Southwest Maximo User Group (SWMUG) published a detailed IBM Maximo Application Suite product update in March 2026. The deck is publicly available on the SWMUG site and is the most-cited single document in the community right now. The headline takeaways:

The AI Assistant is the focus. Database retrieval, analytical insights, and interactive results in Manage 9.1 are the "now" capabilities. Voice interaction, computer vision, and a persistent digital teammate are the "MAS 9.2" capabilities.
The future is agentic. MAS 9.2 is positioned around three shifts: a persistent, context-aware assistant; extensible agentic workflows; and a long tail of use cases across the asset lifecycle.
The loop is unified. Manage, Monitor, Health, Predict, and Reliability Strategies are increasingly presented as connected operational capabilities, not separate products.

If you are new to the Maximo community and want one document to read, this is it.

The RCM workshop: a community moment

In May 2026, Stefan Hoffmanns published a community blog post titled "Why RCM Is Becoming the Missing Link Between EAM and APM in the Maximo Application Suite." The post is a practitioner's read of an IBM workshop, and it captures a shift that has been building for two years.

The shift in one sentence: Maximo Application Suite is evolving from a work-execution platform into a connected asset lifecycle platform where reliability engineering, condition monitoring, health scoring, and AI-driven insights work together as one continuous process.

The community reaction to the post is telling. The comments are not arguing the shift. They are asking about implementation: how to bootstrap an FMEA library, how to wire Monitor data into Health, how to make the loop run without a reliability engineer babysitting it. The conversation has moved from "is this real?" to "how do I do it?"

That is the most important community signal in mid-2026. The narrative is settled. The work is the work.

Practitioner access: certifications, labs, user groups

For someone joining the Maximo community in 2026, the practitioner access map is:

Certifications

IBM's certification path for Maximo has been refreshed for MAS. The current path includes:

IBM Maximo Manage Application Consultant — the foundational certification. Covers the suite-level architecture, the Manage application, the role-based UI, automation scripts, integrations, and the most common industry solutions.
IBM Maximo Manage System Administrator — for the platform-side practitioners. Covers installation, upgrade, configuration, security, performance.
Specialty certifications in Monitor, Health, Predict, and the AI Service. These are newer and the curriculum is still maturing.

The honest read: the certifications are valuable for credibility and for the structured curriculum, but they are not a substitute for hands-on work. The community's most-respected practitioners are the ones who have done multiple real upgrades, not the ones with the most badges.

Labs

IBM's GitHub-hosted labs at ibm.github.io/maximo-labs are the most useful free resource for hands-on learning. The labs cover:

The Health and Predict-Utilities pattern (with a public pump dataset and a public substation transformer dataset).
MAS installation and configuration.
Monitor and IoT connector patterns.
The AI Service templates.

The labs are not always current with the latest release, but the core patterns are stable. If you have 8 hours and a sandbox environment, the Health and Predict-Utilities lab is the single best hands-on introduction to the reliability-engineering side of Maximo.

User groups

The user group ecosystem in 2026 includes:

SWMUG (Southwest Maximo User Group) — the most active in the US. Quarterly meetings, a strong product update cadence, and a deep practitioner community.
MUG (Maximo User Group) chapters in major metros.
Industry-specific groups for utilities (Utilimetrics, APPA), transportation, and manufacturing.
The IBM Community Maximo forums — the most accessible entry point for someone new.

The user groups are where the real practitioner signal lives. A question you post in a user group is read by 5–10 senior practitioners who have done the work. The answers you get are the answers you would have paid a consultant $5,000 to produce.

The community signal in one sentence

The Maximo community in mid-2026 is past the "is MAS the right direction?" debate and into the "how do I get there from here?" implementation. The people who are participating are not the people who are still evaluating — they are the people who are building, who are upgrading, who are writing the playbooks for the next wave. The community signal is: the future is real, the work is hard, and the people doing the work are the people worth talking to.

Where to plug in this week

If you are reading this and want to engage, the highest-leverage moves are:

Join the IBM Community Maximo forums. Read the recent threads. Post a question. The community is open and the response time is hours, not days.
Read the SWMUG March 2026 product update. It is the single best 30-minute orientation to the current state of MAS.
Run one of the IBM labs. The Health and Predict-Utilities lab is the most useful for getting hands-on with the reliability-engineering side.
Find your local user group. SWMUG if you are in the US Southwest. MUG-NE, MUG-Midwest, MUG-Europe, or one of the regional groups otherwise. Show up. Ask questions.
Sign up for the MAS 9.2 beta. IBM is taking design partner customers for the agentic layer. If you are building something ambitious, the beta is the place to be.

The Maximo community is one of the most practitioner-rich communities in enterprise software. The work is real, the people are generous with their time, and the conversation in 2026 is the most substantive it has ever been. Plug in.