IBM Maximo Application Suite Migration FAQ

What is Maximo Application Suite?

Maximo Application Suite (MAS) is an enterprise asset management platform that builds upon and enhances classic Maximo, particularly in the areas of performance improvement and predictive maintenance.

MAS offers substantive improvements over classic Maximo thanks to major changes in the application’s infrastructure. Based on Red Hat’s OpenShift containerized deployment architecture, it is possible to run multiple instances of Maximo at once.

As a result, users can now deploy multiple Maximo applications with a single license. Using a points-based subscription model, users freely use different modules in MAS as necessary to support their asset management goals.

Why is IBM making this change?

IBM’s transition toward MAS revolves around helping EAM users to better accomplish their goals with less friction and uncertainty.

One of the top priorities was to simplify licensing. The new points-based subscription model offered through MAS allows users to incorporate as many modules as they want with a single license, and only when they need them.

The shift provides Maximo users with more control around how they manage their enterprise assets. The ability to leverage the full functionality offered by MAS (when necessary) gives users the flexibility they need to respond to economic headwinds and global instability.

Finally, unifying Maximo features and modules into a single platform helps users eliminate data silos in their organization and makes it easier to see how information from each module contributes to the big picture.

Is there a deadline for the transition to MAS?

Maximo EAM will be sunset on September 30, 2025. Following this deadline, IBM will no longer be providing support for Maximo 7.6.1 (or previous versions) in the form of fixes, patches, and telephone support. Until that date, additional support may be delivered to solve critical defects or security vulnerabilities that may arise between now and the deadline.

What are my options for implementing MAS?

Maximo users have multiple options for implementing MAS, and the path forward will be largely dictated by what infrastructure is already in place.

For users that desire to continue running their Maximo operations largely in-house, the ability to build and maintain the Red Hat software architecture underpinning MAS will be necessary both to implement the platform and for long-term success.

For users already operating their EAM in the cloud, MAS is currently deployable on these and other supported cloud services:

Additionally, MAS can be deployed and maintained as a service by a strategic technology partner. Depending on the needs of the organization, this approach could mean setting up Red Hat and cloud infrastructure, acquiring Maximo licenses, ongoing maintenance, or any combination of these services.

What does the transition to MAS to look like?

It’s best to start this process after understanding what the transition to MAS from Maximo Classic will look like from beginning to end. The transition can be summarized by these four major goal posts:

1. Evaluate the existing system – Before an organization rebuilds their deployment of Maximo, it makes sense to determine if that deployment is delivering its full value. The transition may be an ideal opportunity to move on from a configuration that isn’t working.

2. Establish the new environment – Whether MAS is being run on in-house servers or on the cloud, the next step in the transition is to configure the Red Hat OpenShift environment that will support the Application Suite.

3. “Lift and shift” from Classic to MAS – During this step, an organization’s existing features and functionality in Classic are ported into or recreated in the Application Suite.

4. Test and roll out – Finally, user testing and feedback will determine the success of the transition and whether additional configurations or modules are necessary before the project is complete.
How soon should the organization transition to MAS?

Several factors will determine how soon an organization should begin their transition from Maximo Classic to MAS. The more complex the transition, the longer the process will take, and the sooner an organization will need to begin to meet the deadline.

Data quality and governance play a large role in determining how complex the transition will be. Likewise, the presence of industry specific modules and user customizations can add extra steps to the process.

In cases where an organization is already prepared for a transition and just needs to execute the final stages of the transition, the process can take as little as 90 days. If an organization is starting the process from the beginning, their timeline could look closer to 9 months.

How can organizations get the most out of the transition to MAS?

The transition to MAS is a unique opportunity for Maximo users to significantly increase the value they receive from their enterprise asset management tool.

The new subscription model gives users more leeway to explore how Maximo’s modules can improve their operations. And by partnering with an EAM expert like JLLT, there’s no trial and error to determine which modules will have the biggest immediate impact.

Connect with us today to find out how easy we can make the transition to MAS for your team.