For years, Maximo users have had newer interfaces available, but many of us kept returning to the classic applications. With Maximo Application Suite 9.2, it may be time to revisit that decision.
‍

IBM has been moving Maximo toward modern, role-based user experiences for more than a decade. Maximo 7.6 introduced Work Centers in December 2014, offering focused tasks, responsive design, and a cleaner experience than the classic applications. On paper, that was a meaningful shift.
‍

In practice, many Maximo users did what we often do. We kept working where we were already productive. The classic applications were familiar, configurable, and embedded in business processes. For me, the Integration Work Center was useful for generating API keys, but most role-based applications did not offer enough value to justify rebuilding processes, updating training material, or moving users away from screens they already knew.
‍

Then came Maximo Application Suite. MAS brought a new platform direction, a refreshed visual design, and a stronger focus on role-based applications. Classic applications such as Work Order Tracking remained available with an updated look, but the larger investment was clearly moving toward focused user experiences. IBM’s broader platform direction, including modern design patterns and component-based web technologies, made it clear this was not a temporary experiment.
‍

Still, I use the classic applications every day. Some of that is habit. Some of it is practicality. The real question is value. Is the benefit of moving users to newer applications worth the work required to move fields, processes, security, documentation, and training?

What Changes with MAS 9.2?

MAS 9.2 may be where that value equation starts to change. The User application is a good example. Administrators were already pushed toward the newer User application in MAS, and MAS 9.1 expanded that direction with additional User and Security Group capabilities. With MAS 9.2, the User application is approaching the functionality many administrators expect from the classic application, while also receiving enhancements that are not always backported. For organizations managing AppPoint calculations and user access, it is time to stop treating the classic User application as the default.
‍

Operational Dashboards are another strong example. I have not seen a concrete reason to believe Start Centers are disappearing any time soon, but IBM is giving users reasons to move. Operational Dashboards provide a modern landing page with KPIs, workflow assignments, quick actions, work queues, security-based access, and configurable dashboard tabs. That looks less like a Start Center replacement and more like a better daily workspace for many users.
‍

Throughout the rest of the role based applications the bigger shift is not just visual. IBM continues to add new functionality to newer Maximo experiences, including AI-enabled field value recommendations, problem code recommendations for work orders, similar record identification, and AI recommendations in Reliability Strategies. These new capabilities, in general, are only delivered in the newer applications, Maximo teams must decide whether to customize the classic applications to catch up or move users to where the product investment is happening.
‍

That is the real decision point. When a new feature appears, do we backport it into the classic application, or move users into the newer role-based applications? Backporting can feel easier in the short term, especially for teams with established customizations. Over time, though, keeping classic applications aligned with newer product capabilities may cost more than a planned transition.

Which Users Should Move First?

Administrators will likely live in both worlds for a while. Some administrative functions, such as Users and Security Groups, are clearly moving forward in newer applications. Others, such as Organizations, are less likely to be rebuilt as role-based experiences anytime soon. Finance and purchasing teams may also continue relying on classic applications such as Purchase Requisitions and Purchase Orders, even if Operational Dashboards improve how they monitor their work.
‍

Technicians and maintenance-focused users are strong candidates for a transition. Many newer Maximo experiences already target their work, especially where Maximo Mobile, work execution, inspections, and AI-supported recommendations come together. If technicians already use newer mobile applications in the field, a more consistent web experience can reduce friction and make future enhancements easier to adopt.

A Practical Path Forward

I do not think every organization should rush to replace every classic application. That is not realistic, and for many processes it is not the best use of time. But MAS 9.2 is a good point to review where newer applications now provide enough value to justify the move.
‍

Start with targeted use cases instead of trying to move everything at once. Administrators can begin shifting toward the newer User and Security Group applications where the functionality supports daily work. Organizations can also evaluate Operational Dashboards for selected Start Center use cases, especially where dashboards better surface KPIs, assignments, work queues, and quick actions.
‍

Technician and supervisor workflows are another logical starting point, particularly where they align with Maximo Mobile, role-based work execution, inspections, or AI-supported recommendations. Teams should also avoid rebuilding every classic customization by default. Some customizations still serve a clear purpose; others may not be worth carrying forward. Use new MAS 9.2 features as a trigger to reassess where users should work and where newer applications justify the change.

Final Thoughts

The classic applications are not headed to Davy Jones’ locker, and they still have an important place in many Maximo environments. But MAS 9.2 adds enough capability in the newer interfaces that it may be time to stop viewing them as optional side applications. For the right users and processes, they are becoming the better long-term investment.

If your organization is planning a MAS 9.2 upgrade, now is a good time to review which users should stay in classic applications, which users should move, and which customizations are worth carrying forward. The answer will vary by team, but the conversation is becoming harder to avoid.

‍