Navigating the Maximo Transition: Choosing the Right Model

The leap from IBM Maximo version 7.6.x to Maximo Application Suite (MAS) for enterprise asset management is enormous, not only for customers but also for IBM and its business partners, but it must be faced because end of support (EOS) for 7.6.x is scheduled for September 2025. This upgrade is more complex than previous ones, introducing new technologies and involving decisions that require thoughtful planning. While a few organizations have proactively embraced the challenge as early adopters, many others have taken a more cautious approach to the transition to MAS.

For those considering an upgrade to MAS, it is essential to understand how it differs from previous versions, what choices must be made and — depending on those choices — what operational changes will result.

Key Changes in MAS

IBM launched MAS in June 2020, but there is still considerable confusion surrounding parts of the offering. Here's a look at the core changes impacting utility clients:

• Deployment options. Hosting responsibilities, infrastructure management and associated costs vary depending on the selection from four broad deployment options for MAS:
  • Customer-managed on-premises
  • Customer-managed hyperscaler
  • Software as a service (SaaS)
  • MAS Managed Services
• Architecture shift. MAS requires Red Hat OpenShift, a container-based Kubernetes platform that adds another layer of complexity to the upgrade process. For traditional Maximo administrators, this is a completely new concept. OpenShift knowledge is crucial for optimizing performance and minimizing disruptions.
• Functional enhancements. Integrated applications like Health, Monitor, Predict and Assist offer more intelligent asset management.
• Licensing model. MAS has transitioned to a flexible AppPoints-based licensing system. Determining the appropriate number of AppPoints for a specific customer is driven by multiple factors.

Defining Your Cloud Strategy

In the past, many Maximo customers preferred on-premises hosting; few ventured into the cloud. At a high level, MAS deployment options fall into one of two buckets: cloud or on-premises models. But MAS introduces nuanced variations — especially for cloud deployment — that require deeper evaluation. For example, not all cloud options fit the typical SaaS model. Some businesses might find that hybrid approaches better align with their needs.

Before making a decision, organizations should align deployment plans with corporate cloud policies. These typically cover security and compliance requirements, internal governance, regulatory mandates, data residency and sovereignty, and cost and budgeting strategies. These factors can significantly affect both the feasibility and long-term sustainability of a deployment. Evaluating them upfront will prevent roadblocks later in the upgrade process.

Choosing the Right Deployment Model

Determining who manages the environment is critical for achieving a successful upgrade. Key considerations include internal skill sets, IT workload and overall business priorities.

Red Hat OpenShift is a foundational requirement for MAS, and it enables flexibility and scalability but also introduces complexity. IT teams must evaluate their readiness to manage OpenShift or seek a third-party provider for support and management. The choice of a MAS deployment option ties into determining responsibility for managing OpenShift.

Organizations with strong IT capabilities might opt for self-managed deployments, while others could benefit from outsourcing to reliable third parties. When considering outsourcing, it’s important to clearly define responsibilities among all parties involved. Those responsibilities include:

• OpenShift platform management
• MAS administration and patching
• Integration with enterprise systems
• Database and application support
• Production migrations and upgrades

There is no single right answer for which deployment option is appropriate. The selection depends on multiple details unique to each customer. It is worth noting that customers retain responsibility for all the factors listed above if they select either the customer-managed on-premises or customer-managed hyperscaler deployment options.

Evaluating Outsourcing Options

For those organizations seeking external support, MAS works with a variety of outsourcing models, each offering a slightly different balance of control, cost and complexity:

• In the SaaS model, MAS is fully managed by IBM. Minimal administrative overhead is needed from the customer, which will have limited customization and database access. This model is ideal for hands-off deployments.
• For MAS Managed Services, hosting infrastructure (on-premises or hyperscaler) is provided by the customer, but IBM manages the initial setup, configurations and operations of MAS Administration, Red Hat OpenShift Cluster and the infrastructure. This model offers more flexibility than the SaaS approach, allowing customers to tailor infrastructure choices without taking on the complexity of managing the MAS and OpenShift environment themselves.
• Under hyperscaler cloud hosting, a Platform-as-a-Service (PaaS) model is offered by Amazon Web Services (AWS) and Microsoft Azure. The PaaS model includes full management of the Red Hat OpenShift Cluster by the hyperscaler. This simplifies OpenShift administration and provides a middle ground between control and convenience. With the PaaS model, responsibility for the MAS application deployment and management lies with customers. AWS PaaS is offered as ROSA (Red Hat OpenShift Service on AWS), while the Azure PaaS is offered as ARO (Azure Red Hat OpenShift).

Strategic Approach for Seamless Transition

Migrating to MAS is more than a mere upgrade from Maximo 7.6.x — it’s a strategic shift. Success requires clarity on the organization’s cloud strategy, OpenShift readiness, a defined outsourcing approach and careful provider selection.

By taking a structured, informed approach, organizations can undergo a smooth transition and unlock the full potential of MAS. Embracing this leading-edge asset management platform will ultimately drive better performance, scalability and long-term value for utilities.