3 ways to migrate and deploy IBM Maximo on AWS Cloud

A latest IDC report — The Business Value of IBM Maximo — that surveyed 9 firms with a median of 8,500 staff, discovered that after these firms 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 complete gear value avoidances yearly. 

IBM Maximo® Application Suite (MAS) is a single, built-in, cloud-based software platform for asset monitoring, administration, predictive upkeep and reliability planning. Maximo maintains high-value property with AI and analytics to optimize efficiency, lengthen asset lifecycles and scale back downtime and prices. To reap the perfect 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 crucial to mix information from totally different areas of a corporation, which in flip helps organizations uncover tendencies, 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. Consequently, the trail ahead for all Maximo EAM prospects is to maneuver to the newest cloud-based MAS. Due to this fact, Maximo migration and modernization has turn into much more necessary for shoppers.

To additional help Maximo migration to AWS, IBM has now made accessible 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 purposes — like Monitor, Well being and Visible Inspection — right into a cohesive single suite of purposes.

Read more: IBM announces IBM MAS Saas

Why MAS SaaS is exclusive

MAS SaaS, a subscription-based service supplied on the AWS, gives an operational surroundings deployed on AWS and operated and managed on a steady foundation by IBM Website 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 just like earlier upgrades on the subject of the info, however the underlying structure adjustments must be executed involving ROSA and different dependencies. The migration is just like how shoppers moved from on-premise to our earlier Maximo EAM SaaS Flex providing, however bearing in mind the variations with MAS. So as 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 totally different migration and modernization paths beforehand, laying out potential modernization packages earlier than making the funding utilizing our proprietary IBM Consulting Cloud Accelerator (ICCA) platform.

A world vitality firm’s strategy to Maximo migration

Allow us to have a look at an instance the place IBM labored intently with an vitality 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 
• Knowledge sharing challenges throughout a number of purposes as a consequence of lack of information cloth and integration layer
• Guide end-to-end deployment resulting in complicated setup, errors and safety

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

Resolution strategy

IBM adopted the next strategy to speed up the vitality firm’s Maximo migration to AWS:

• Upgraded current Maximo software from model 7.6.0.9 to model 7.6.1.2 utilizing Infra as a code (IaC)
• Deployed utilizing IaC offered 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 surroundings, additionally addressing latency points as a consequence of multi-AWS availability zone deployment
• Used AWS Database Migration Service (DMS) for information migration and schema conversion
• To reduce the database replication (DR) infra provision and preserve the DR value decrease, IaC was used to spin the DR surroundings based mostly on demand. DR capabilities used to maintain information updated inside availability zone and DR area
• Addressed information sharing throughout purposes utilizing IBM Cloud Pak for Data and uniform integration layer utilizing IBM Cloud Pak for Integration

Resolution parts

• Maximo Enterprise Utility Administration (EAM) relies on a 3-tier structure with the next parts:
  • HTTP/Net Tier and Utility Tier utilizing the IBM WebSphere and HIS deployed EC2 occasion beneath non-public subnet, to maintain software safe.
  • Database Tier is utilizing the AWS Oracle RDS with replication allow to handle the DR scenario, operating beneath non-public subnet.
• Digital Non-public Cloud (VPC) was configured based mostly 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
• Net software 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 accessible 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 permits firms to concentrate on deploying purposes and speed up innovation by off-loading the cluster lifecycle administration to RedHat and AWS, and has now supported configuration for IBM MAS. Because of this prospects don’t must create, handle and keep their very own RedHat OpenShift clusters for IBM MAS.

Maximo Migration and Working Mannequin

High 3 methods to speed up Maximo migration to AWS

So as to migrate to the cloud, there are three deployment fashions accessible 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