IBM & Red Hat on AWS

Modernize Enterprise Asset Management with IBM Maximo Application Suite as a Service on AWS

IBM Maximo Application Suite is an enterprise asset management (EAM) platform that uses AI, IoT and analytics to optimize equipment performance, extend asset lifecycles and reduce operational downtime and costs. On 12 April 2022, IBM announced end of support for all Maximo Enterprise Asset Management (EAM) 7.6.1.x and compatible versions of products, including industry solutions and add-ons, effective 30th September 2025. This post describes the steps involved to migrate existing IBM Maximo environment (on-premise, self-managed, managed) to IBM Maximo Application Suite 8 (MAS) Software-as-a-Service (SaaS) on AWS, with simplified and flexible consumption-based licensing structure that is scalable to suit customers’ needs.

Introduction to IBM MAS SaaS on AWS

IBM MAS SaaS on AWS represents the next phase of IBM’s initiative to support clients’ increasingly global operations. Built on 30+ years of market-leading technology, it offers best-practice industry solutions, supported by the scale and agility of AWS.

Let’s first understand deployment options available from IBM:

Features Maximo Application Suite Maximo Application Suite as a Service
Management model Client Managed SaaS – managed by IBM Site Reliability Engineering
Deployment Option Cloud/On-premises/Hybrid Cloud
Supported cloud platforms Red Hat Openshift – enabled platforms Not Applicable (SaaS offering)
Licensing Perpetual, Subscription, Monthly SaaS subscription based
Access to all Suite applications Shared AppPoints SaaS – based AppPoints
System provisioning, maintenance, and upgrades Client Managed (except Red Hat OpenShift Service on AWS – ROSA service) Automatic
Customizations Fully customizable UI and API driven

Table 1. IBM Maximo Application Suite deployment options.

MAS SaaS on AWS provides clients with an industry-leading asset management system from IBM supported by the scale, agility, and cost-efficiency of AWS. It offers a wide range of features and functionalities, empowering organizations to streamline their asset management processes. Some notable features include:

  • Consolidated subscription: With a single AppPoints-based subscription, there is no need to purchase and provision software and infrastructure.
  • All-inclusive management: By migrating to MAS SaaS on AWS, organizations can offload infrastructure management and maintenance tasks to AWS and IBM, reducing the burden on IT teams. This allows IT resources to focus on strategic initiatives and innovation. The SaaS subscription covers installation, configuration, platform upgrades, application operations, database management, infrastructure, and network management.
  • Convenient and cost-optimized procurement: MAS SaaS on AWS operates on a pay-as-you-go model, eliminating the need for upfront infrastructure investments. Organizations can leverage the cost benefits of cloud computing, paying only for the resources they consume. MAS SaaS can be directly purchased from the AWS Marketplace, potentially allowing customers to take advantage of AWS’ Enterprise Discount Program (EDP).
  • Enhanced productivity: By shifting operational and security tasks to IBM specialists, customers can focus on their core business activities, increasing productivity.
  • Modern and Enhanced Functionality: MAS introduces new features, enhanced user interfaces, advanced analytics capabilities, and mobile accessibility allowing users to access asset data and perform tasks from anywhere, anytime. This improves efficiency, enables seamless collaboration across teams, optimized asset management processes, and make data-driven decisions
  • Scalability and Flexibility: AWS provides a scalable infrastructure, allowing organizations to accommodate growth and handle fluctuating workloads efficiently. MAS SaaS can scale up or down based on business needs, ensuring optimal performance and cost-effectiveness.

High level architecture in Figure-1 below, explains how customers access IBM MAS, removing undifferentiated heavy lifting of managing underneath infrastructure.

High level architecture view of IBM Maximo Application Suite Software as a Service on AWS.

Figure 1. IBM Maximo Application Suite SaaS on AWS high level architecture view.

Refer to IBM documentation for more details on architecture.

Migration to IBM MAS SaaS on AWS

Migrating existing Maximo environment to MAS SaaS on AWS is a significant step towards modernizing asset management practices. This section describes various phases and steps involved for this migration (figure 2).

Different migration phases of IBM Maximo to AWS.

Figure 2. IBM Maximo Migration phases.

Planning

The migration journey begins with meticulous planning. Collaboration between the customer and IBM is vital to assess the complexity, define timelines, allocate resources, and identify potential challenges. Key considerations in the planning stage include:

  • Understanding the customer’s migration requirements and objectives
  • Assess existing environment by analyzing the Maximo environment and assessing compatibility with MAS SaaS on AWS:
    • Verifying that the source version of Maximo is v7.6.1.2 or above
    • Ensuring the source database is exported in IBM Db2 format, with the appropriate Db2 version depending on the migration timing. If source database is not Db2, you can leverage AWS Database Migration Service for migrating it to IBM Db2
    • Addressing and resolving all errors identified by running Maximo v7.6 Integrity Checker on the source database
    • Identifying all items to be migrated, including attachments and custom reports
    • Remediation of Java classes by converting them to Automation Scripts for a seamless transition
    • Converting fields using TEXT search to alternative values (WILDCARD, EXACT, or NONE), as TEXT search is not supported in MAS
    • Ensuring proper setup for Maximo Object Structure Tables, Data Dictionary Tables, MaxSequence, and other essential elements before sending the database to IBM MAS. Engage IBM or certified partners for additional help
  • Define migration strategy based on the assessment, and develop a migration strategy that aligns with organizational goals and priorities. Consider factors such as downtime tolerance, data migration approach, and the sequence of migration activities
  • Determining the level of expertise within the organization, and the need for external assistance from IBM Consulting, IBM Expert Lab Services, or an IBM certified system integrator (SI)

Refer to this IBM documentation for more details on planning phase.

Initial setup

The initial setup phase involves preparing the target MAS SaaS on AWS environment, and identifying all components that require migration. After customer provisions the MAS SaaS offering, IBM will create and setup the MAS target environment for the migration.

Identication of components to be migrated

  1. Database:
    • Identify the EAM 7.6.x database
    • If source database is not IBM Db2, then database must be migrated to IBM Db2 before migration. You can leverage AWS Database Migration Service for migrating it to IBM Db2
    • Data integrity testing plan for migrated database
  2.  Codebase:
    • Identify the EAM 7.6.x application codebase
    • Prepare the codebase for compatibility with MAS SaaS, and remediate the changes identified in the planning phase. Refer to this article for more details, or engage IBM or your preferred SI partner for help
  3. Attachments and Data:
    • Identify any attachments (PDF, MS Office files, scanned documents), or external data sources used by the EAM system
    • Plan for migrating attachments and data to the new MAS environment

Finalize documentation and initial setup

  1. Integration Documentation:
    • Document all existing integrations with the EAM system
    • Identify any APIs, web services, or third-party systems that interact with EAM
  2. VPN Setup (if applicable):
  3. MAS SaaS on AWS Configuration:
    • IBM SRE configures MAS SaaS on AWS based on your organization’s requirements, including user management, role assignments, and settings
    • IBM SRE setup a dedicated testing environment within MAS SaaS on AWS your your initial testing and validation

Note: Both the IBM and Client (and/or SI partner) are responsible for ensuring the successful execution of these migration steps. Clear communication and collaboration between the two parties are essential for a smooth migration process.

Migration

Primarily, Maximo migration involves two major steps:

Application configuration and customization

  1. Review SaaS-specific Requirements:
    • Identify the SaaS-specific requirements and constraints imposed by the MAS SaaS on AWS cloud
    • Technical requirements must be validated with the IBM documentation here
  2. Adjust Configuration Settings:
    • Modify configuration settings in EAM and Maximo to align with the MAS SaaS on AWS environment by following the guidelines here
    • Update parameters such as database connection strings, email servers, and authentication methods
  3. Customization Review:
    • Examine custom code, scripts, or extensions in EAM and MAS SaaS
    • Engage IBM or your preferred SI partner to ensure that customizations are compatible with the SaaS environment and make necessary adjustments
  4. Documentation Update:
    • Maintain thorough documentation of all configuration changes and customizations made for future reference

Data migration for IBM Db2 database

  1. Database is migrated from on-premise to MAS SaaS on AWS using an export done using Db2 utilities like db2move/db2look
  2. The IBM SRE team would prefer a database backup image provided is from the same database version (check for compatible Db2 version at the time of migration planning) as running in MAS SaaS. For all migration stages (initial build, testing, cutover), new database export/import is executed
  3. Customers are responsible for exporting the data and loading into staging area provided by IBM
  4. IBM SRE team then imports data into MAS SaaS on AWS
  5. If the source database is being converted from another platform (for example Oracle or Microsoft SQL Server), it is customer’s responsibility to convert and perform validation of the converted Db2 database before providing it to the IBM SRE team for import into the target MAS SaaS on AWS environment. Customers can leverage AWS Database Migration Service for migrating it to IBM Db2 as first step, and then stage the backup copy in IBM SRE provided staging area.

For more details, refer to this documentation or contact IBM.

Testing

Two-stage testing is recommended for a smooth migration:

  • Test 1: In this stage:
    • all steps required to migrate from the existing implementation to the MAS SaaS on AWS are executed
    • This includes exporting data from the source system, transferring it to MAS, loading it into the new database instance, configuring the environment, and validating integrations
    • Customer’s testing team thoroughly tests all business flows to ensure those perform as expected, and any issues identified are addressed promptly
  • Test 2: This is a comprehensive dress rehearsal (mock go-live) for the final migration to the MAS SaaS on AWS production environment:
    • All steps are documented, and timings are recorded to ensure a smooth go-live process
    • This test should be conducted close to the final cut-over date, typically within a few weeks of the actual migration
    • If required, multiple dress rehearsals are executed to fine tune the cutover plan.

For more details, refer to this IBM documentation or contact IBM.

Cutover and Go Live

The Cutover and Go Live phase marks the execution of final migration steps and announcing going live on the MAS SaaS on AWS. This phase involves:

  • Establish a rollback plan in case unforeseen issues arise during or after the migration.
  • Define procedures for reverting to the previous EAM system to minimize downtime and mitigate potential risks
  • Exporting data from the source system and transferring it to MAS SaaS on AWS
  • Addressing any remaining technical changes in MAS using maxadmin, or at the OS level. Client will have to raise a support ticket to get issues (if any) fixed at OS level with IBM SRE team
  • Deploying attachments required for the MAS environment
  • IBM SRE will import the previously exported database into the MAS environment.
  • Apply any outstanding changes, including integrations, needed before the go-live
  • Thoroughly testing all changes and configurations to ensure a successful migration. Invite global users, if needed and feasible, to test
  • Announce the go-live with the MAS SaaS on AWS from existing Maximo environment

Summary

By migrating to IBM MAS SaaS on AWS, clients will continue to have IBM product support. It unlocks the opportunities to modernize, easily integrate with other AWS hosted IBM products, and leverage native AWS cloud services for driving business value. Embrace the journey to MAS SaaS on AWS and unlock the full potential of the Maximo Application Suite.

References and rurther reading

Here are some valuable resources that can assist you when planning the migration from on-premise Maximo environment to MAS SaaS on AWS: