3 ways to migrate and deploy IBM Maximo on AWS Cloud

A current IDC report — The Business Value of IBM Maximo — that surveyed 9 corporations with a median of 8,500 staff, discovered that after these corporations adopted IBM Maximo, it resulted in: a enterprise profit of roughly USD 14.6 million, on common, per yr per group; 43% much less unplanned downtime per yr; and USD 8.6 million in whole tools value avoidances yearly. 

IBM Maximo® Application Suite (MAS) is a single, built-in, cloud-based utility platform for asset monitoring, administration, predictive upkeep and reliability planning. Maximo maintains high-value belongings with AI and analytics to optimize efficiency, lengthen asset lifecycles and cut back downtime and prices. To reap the very best advantages with most efficiency, it’s important to host the identical on a scalable infrastructure, thereby the present development is emigrate Maximo to cloud. On this journey, we’re seeing an elevated curiosity in migrating and deploying MAS on AWS Cloud.

The rising want for Maximo migration to AWS Cloud

Migrating to cloud helps organizations to drive the operational resiliency and reliability, on the identical time retaining software program updated with minimal improve effort and infrastructure constraint. As a result of elevated demand of data-driven asset administration, it’s essential to mix knowledge from completely different areas of a company, which in flip helps organizations uncover developments, make predictions and take higher knowledgeable asset administration selections.

Consistent with this development, final April IBM introduced end of support for all Maximo 7.6 and add-ons by September 2025. Because of this, the trail ahead for all Maximo EAM prospects is to maneuver to the newest cloud-based MAS. Subsequently, Maximo migration and modernization has change into much more necessary for shoppers.

To additional help Maximo migration to AWS, IBM has now made out there newer containerized variations of Maximo Utility Suite as a Service (MAS SaaS) on AWS Market with Deliver Your Personal License (BYOL) on AWS. MAS SaaS on AWS represents one more necessary step in Maximo’s journey to combine its standalone functions — like Monitor, Well being and Visible Inspection — right into a cohesive single suite of functions.

Read more: IBM announces IBM MAS Saas

Why MAS SaaS is exclusive

MAS SaaS, a subscription-based service provided on the AWS, supplies an operational setting deployed on AWS and operated and managed on a steady foundation by IBM Web site Reliability Engineering (SRE) specialists utilizing greatest practices. This collaboration equips prospects with an industry-leading asset administration system from IBM, supported by the dimensions, agility and cost-efficiency of AWS.

Shifting to MAS 8 is each an improve and migration when utilizing MAS SaaS. The improve is much like earlier upgrades with reference to the info, however the underlying structure adjustments have to be accomplished involving ROSA and different dependencies. The migration is much like how shoppers moved from on-premise to our earlier Maximo EAM SaaS Flex providing, however considering the variations with MAS. With the intention to migrate to MAS SaaS, perpetual on-premises prospects would cease paying Service & Assist (S&S) and buy a SaaS subscription; on premises Subscription License prospects would start a brand new SaaS subscription; and current MAS Flex and MAS Managed Service prospects would start a brand new MAS SaaS subscription.

To jumpstart the migration journey, companies can design completely different migration and modernization paths beforehand, laying out potential modernization applications earlier than making the funding utilizing our proprietary IBM Consulting Cloud Accelerator (ICCA) platform.

A world power firm’s method to Maximo migration

Allow us to have a look at an instance the place IBM labored carefully with an power firm that was dealing with the next challenges:

• Longer instances to acquire infrastructure required to help newest model of Maximo
• WebSphere being the core to Maximo had excessive availability and high-performance points 
• Information sharing challenges throughout a number of functions attributable to lack of information cloth and integration layer
• Guide end-to-end deployment resulting in complicated setup, errors and safety

The shopper selected the most recent model — Maximo Utility Suite 8 (MAS8) — because it addresses {industry} challenges reminiscent of threat of failure, rising upkeep value and sustainability and compliance rules. AWS Cloud was the popular selection for the shopper to reap the benefits of larger deployment flexibility, scalability, excessive availability and safe structure.  

Answer method

IBM adopted the next method to speed up the power firm’s Maximo migration to AWS:

• Upgraded current Maximo utility from model 7.6.0.9 to model 7.6.1.2 utilizing Infra as a code (IaC)
• Deployed utilizing IaC supplied the flexibleness of spin-up the occasion required for auto scaling. This automation helps to cut back the lead time to spin and run the brand new setting, additionally addressing latency points attributable to multi-AWS availability zone deployment
• Used AWS Database Migration Service (DMS) for knowledge migration and schema conversion
• To attenuate the database replication (DR) infra provision and maintain the DR value decrease, IaC was used to spin the DR setting primarily based on demand. DR capabilities used to maintain knowledge updated inside availability zone and DR area
• Addressed knowledge sharing throughout functions utilizing IBM Cloud Pak for Data and uniform integration layer utilizing IBM Cloud Pak for Integration

Answer parts

• Maximo Enterprise Utility Administration (EAM) relies on a 3-tier structure with the next parts:
  • HTTP/Internet Tier and Utility Tier utilizing the IBM WebSphere and HIS deployed EC2 occasion beneath personal subnet, to maintain utility safe.
  • Database Tier is utilizing the AWS Oracle RDS with replication allow to handle the DR scenario, operating beneath personal subnet.
• Digital Non-public Cloud (VPC) was configured primarily based on AWS greatest practices with private and non-private subnets
• Utility servers and deployment supervisor have been setup for autoscaling utilizing the Auto Scaling Group  
• Maximo web-based UI decision for exterior entry utilizing the AWS Route 53 service
• Internet utility firewall (WAF) was used as a primary line of protection in opposition to internet exploits
• IaC scripts on Terraform and CFT have been built-in to provision autoscaling structure

Reference Structure on AWS  

How Maximo on RedHat OpenShift Service on AWS (ROSA) helps shoppers

MAS 8.0 has now been containerized and out there to run particularly on RedHat OpenShift. To ease this transition for purchasers unfamiliar with operating containers in manufacturing, AWS has partnered with IBM and RedHat to develop an IBM MAS on ROSA reference structure. ROSA is a fully-managed, turnkey application platform that enables corporations to give attention to deploying functions and speed up innovation by off-loading the cluster lifecycle administration to RedHat and AWS, and has now supported configuration for IBM MAS. Which means prospects don’t need to create, handle and preserve their very own RedHat OpenShift clusters for IBM MAS.

Maximo Migration and Working Mannequin

Prime 3 methods to speed up Maximo migration to AWS

With the intention to migrate to the cloud, there are three deployment fashions out there to shoppers for operating IBM MAS on AWS Cloud:

1. MAS SaaS on AWS powered by ROSA
2. MAS devoted on AWS powered by ROSA
3. Buyer-hosted ROSA