Everything you need to know about moving from

Maximo EAM to Maximo Application Suite

Kim Woodbury, Maximo Senior Product Manager, IBM

Steve Hauptman, Maximo Architect and Ecosystem Lead, IBM

April 2024
Agenda

• Comparisons between EAM and Manage

– Concepts
– Maximo Application Suite Manage topology and deployment
• Modernization with OpenShift
• Understanding Maximo Application Suite (MAS)
• Installation/upgrade considerations and process
• Upgrade Resources
– Helpful links for upgrade
• Useful Resources
– Links for reference
• Moving to Openshift
• Moving into MAS Managing the Suite (user mgmt, languages, configuration files)
• Upgrading EAM to Manage
Maximo Application
Suite
Manage Monitor Health
Intelligent Asset Management Monitor and Detect Anomalies 360 View of Assets

Best-of-class capabilities to
provide complete view of
your assets addressing the
needs of key personas in
your organization. Predict Visual Inspection IT
Predictive Failures AI-Powered Insights ITSM and ITAM combined

- Technicians
- Technician Supervisor
- Asset Maintenance Manager
- Plant Manager
- Fleet Manager Mobile Assist Reliability Strategies
- Operations Manager Technician Work Execution Prescriptive Assistance Dedicated Reliability Centered
- Reliability Engineer Maintenance
- Quality Manager Industry Solutions| Accelerate time to value
- Planners / Schedulers
- Dispatchers Maximo Accelerators Catalog | Complement, extend or enhance MAS
- Purchasing Managers IBM Cloud Pak for Data | Watson Studio | Watson ML | Watson Discovery | Watson Assistant | App Connect | Cognos Analytics

Infrastructure Independent
Common Operating Environment
IBM Cloud AWS Azure Google Cloud Private Edge Systems

4
Maximo EAM to Maximo Application Suite (MAS)

Maximo EAM 7.x Maximo Application Suite

8.x, (9.x coming soon)

Same Integration options (excepting RMI)

Same DB support (DB2, Oracle, Sqlserver)
Same Customization options

5
 PPA, Fix Central
Maximo 7.6.x
Maximo EAM iFixes
Customer actions:
Maximo EAM Industry Solutions Download, install
Maximo EAM add-ons
Customization
Build ear file
Maximo EAM Base
Update database
Maximo EAM Configs Deploy

Cron cluster WAS

UI Cluster Integration cluster BIRT Reporting Maximo EAM
Deployment Other external
Database
Manager systems
Maximo Admin WAS Node WAS Node WAS Node WAS Node
Workstation Server + OS Server + OS Server + OS Server + OS Server + OS Server + OS
(Customization and Build
machine)
• Customer actions:
Manage Operator Manage Base Manage Add-on Manage Industry Customization
• Install operator MAS Manage
images image image Solutions image archive • Customization and make it available
• Define the spec
Image Registry Customer’s repository • Operator
PPA • Build
MAS install script • Deploy
Entitlement key • Watch and maintain the system according to
spec change

Operators Admin/command
UI bundle
Integration
Cron bundle
Reporting
Maximo EAM
processor bundle bundle
Database Other external
systems
OpenShift Container Platform
Master node Server + OS
Master node Worker node Worker node Worker node Worker node

Infrastructure
IBM & Expanded Partner Ecosystem, virtualization, baremetal

6
Changes: Containerization, Built-in Liberty, OpenShift

Maximo Maximo
Maximo Maximo
Application Application • Containerization
Application Application
Liberty Liberty • Light weight
Websphere JVM Websphere JVM Container Container • Fast
Websphere Network Deployment Container Runtime • Portable
• Consistent
Operating System Operating System

Infrastructure Machines Infrastructure Machines

• OpenShift
OpenShift Control plane Maximo pod Maximo pod Maximo pod Maximo pod • Container orchestration/scheduling
• Load management
• Routing
OpenShift • Config management
• Security
Master Worker Node Worker Node
• Monitoring
Node Master
Node Master
Node

7
 Applications in One Suite

Maximo Application Suite:

Install once, select what application you need
and enable
Manage Application:
Deploy once, select what add-on you need
and enable

8
Benefits of Modernization through OpenShift
Aligning with Modern IT Practices
• Containerization: Streamlining application deployment
• Cloud Architecture : Embracing the flexibility of the cloud
• Resource Efficiency: Optimizing utilization
• Automation: Operator framework enhances automation, boosting efficiency and scalability in the
deployment, management, and scaling of containerized applications
• Security: Robust security measures
– Role Based Access Control(RBAC) for fine grained access control beyond just Admin y/n
– Network policies for secure communication
• Monitoring
– Monitoring and Logging for enhanced visibility and compliance
• Stability: Ensuring reliability and robustness
– Health checks, readiness, and liveness probes
– Node failures trigger workload redistribution, ensuring continued application operation
* Roadmap to support zLinux and Power
Modernizing Asset Management with MAS
• Simple interface to Manage OCP artifacts directly in MAS Workspace Configuration
– Language selection
– Industry Solution
– # of JVMS
• Centralized user management
• Log management: 'Must Gather' logs utility for capturing installation and upgrade application logs and
is based on OpenShift utility.
• Modern Asset Management (EAM)
– New UI: New modern look and feel.
– Mobile disconnected with shared infrastructure (MAF)
– Reduce downtime during Manage upgrade - (no need to take down system for some dbscript
updates) provides ~60% improvement in db update time
– Tools APIs for seamless server control such as start/stop server, integrity checker, access integrity
checker logs
– Configure logs to be directed to S3 storage is available
Changes Summary
To Maximo End User:
• Same UI experience (classic, Work Centers,
Maximo Application Framework) - different skin
Deployment
System functional
Changes due to • same apps
Changes due to • same functionality
architecture MAS
containerization • same performance
• Different Login

Installation Properties
User To Maximo Admin:
management • Same supported databases
• Different Middleware
• New way to install
• New way to run
Server Certificate
Configuration • New way to manage users
bundles management
• New way of system configuration
• New way to upgrade

Upgrade
Integration To Maximo Developers:
processes • Same supported customization
• Same customization structure
• Different dev/test process
Customization
process To Maximo buyer:
• New Flexibility
• New licensing
11
Deployment Options vary for Production and Development

• Apppoints
Standard SNO (single Openshift Local Docker required for
(fka code ready Container (no
Deployment node openshift) containers) MAS, no OCP)
ALL options

Staging and/or
Production Not production Not production
Production
Supported supported supported
environment

Certified for Certified for

Fully Supported Manage only
Manage only Manage only

Could support
multiple MAS Best for <70
instances Users/Small
(Dev1/Dev 2/Test)

12
 Migration from EAM to MAS

Planning
• Sizing (MAS + Prereq + Manage)
• Bundles and bundle level properties
• Industry solutions and languages installed
• Extracting customization archive
• Integration, Kafka or JMS
• LDAP/SAML integration with MAS
• Doclinks
• Identify any APAR or hotfixes not in the latest version EAM to MAS (Recording and PDF)
• Run integrity checker
https://community.ibm.com/community/user/asset-
Testing and upgrade facilities/viewdocument/maximo-eam-to-maximo-
• Have the ManageWorkspace CR (directly or through UI) application-su?CommunityKey=3d7261ae-48f7-481d-
• PVs b675-a40eb407e0fd&tab=librarydocuments
• Customization archive
• Components, language, etc
• Additional server settings, jvm options, encryption secret
• Point to a 761x database
• Activate
• Images generated
• Maxinst pod instantiated
• Some validation will run
• Database updated to latest version
• Existing Maximo users synced to MAS
• Server running
Coming in MAS 9.0 – Targeted GA June 25, 2024
• Database currencies
– Sqlserver to support doublebyte/singlebyte languages in single database
– Support RDS Models
• User Authentication improvements
– Improved parity with EAM
• Ability to white label
– CSS and MAS header configuration ability
Introducing MAS 9.0
Targeted GA June 2024

What does it mean?

Traditionally, a change to the version number of software indicates an impactful technical or functional
difference from the prior release. For MAS this is not the case.

MAS 9.0 will provide:

• Standardization of MAS product versioning which simplifies and aligns across the MAS portfolio
• All MAS products (including Maximo Manage, Monitor, Health and Predict) will utilize the same version
number within each release. (e.g., MAS 9.0 will contain Maximo Manage 9.0 and Maximo Health 9.0)

• Introduction of a new 3+1+3 Lifecycle Policy

15
New lifecycle for MAS: 3+1+3 with 12-month release cadence
**Please review MAS SaaS policies for their release cadence
June 2023 October 2024 March 2026 July 2027 December 2028 April 2030 August 2031 January 2033 May 2034

MAS 8.9

MAS 8.10 (LTS)

MAS 8.11 (LTS)

MAS 9.0
Feature Channel
Feature
(Previews of 9.1.0)
MAS 9.1
Feature Channel
Feature
(Previews of 9.2.0)

Feature Channel
Feature
(Previews of 9.3.0)
MAS 9.3

• Follow 3+1+3 lifecycle

• Release every 12 months (9.x)
• Monthly maintenance updates for 36months (Base Support)
• Initial Extended Support for another 12 months *Usage + Existing & Sev1 Critical Defect Fixes
• Ongoing Extended Support for another 36months *Usage + Existing Fixes
* Terms and Conditions of Extended Support
• Feature Channel to explore new features in non-production
• Builds in the feature channel have short term availability and would never be ‘fixed’

Note: EAM customers on 7.6.0.10/7.6.1.2/7.6.1.3 will be able to directly upgrade to 9.x

All MAS sub-components (i.e., Manage , IS/Add-ons, Health, etc.) will now align to the release version – for example 9.0
16
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal
without notice at IBM’s sole discretion.
Maximo EAM Lifecycle Updates
DESCRIPTION DATE
Announce End of Market Announcement Letter published April 12, 2022
(EOM & EOS) IBM Announcement Letter #922-024
EOM and New Support Parts are available for purchase April 19, 2024
End of Marketing (EOM)
Update Support Plans and Lifecycle page Sept 30, 2025
End of Support (EOS)

Must be on v7.6.1.3
R 7.6.1 for latest ifixes

End of
Life
GA EOM/EOS EOM Sustained Support
Extended Support
July 2018 Announced April 2024 Sept 2025 Option
Option
April 2022 Sept 2030
Sept 2026

*IBM Extended Support: Enables clients continued access to IBM Support for "how to" questions, usage issues, known defects
published in IBM Fix Central, and new critical sev1 defects (no proactive security fixes) after IBM standard support ends for 7.6.1.x.

*IBM Sustained Support: Enables clients to continue to get support for "how to" questions, usage issues, and known defects
published in IBM Fix Central after IBM standard/extended support ends for 7.6.1.x. IBM Sustained Support does not include support
for new defects or new security fixes.
*New Support Terms and Conditions

New IBM Support Offerings and EAM EOS Support page 17

Upgrade Resources

• Overview of what’s New : Overview documentation link

• Upgrade Planning: Checklist, prerequisites and capacity planning: Planning documentation link
• Prepare: Prepare documentation link
– Database settings and backup
– Authentication and security
– Adapters (SAP, Oracle)
– Customizations
– Third party Jars
– Integrity Checker
• Install MAS and Manage: Install documentation link
• Maximo Manage database: Database configuration link
• Deployment: Deployment documentation link
• Activation Manage: Activation Manage app link
Upgrade Resources (Contd.)

• Post Deployment: https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=manage-

migrating
– Integrity Checker after upgrade
– Report migration
– Integrating with external systems(JMS)
– Server bundle properties
– Cron task for migrated users
– Certificates
• Verification: Manage Verification documentation link
Useful Resources

• Product Overview
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=product-overview
• Configuring MAS
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=configuring
• Administration
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=administering
• Monitoring
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=monitoring
• Automation: Ansible Scripts
– https://ibm-mas.github.io/ansible-devops/
• Single Node OpenShift installation (production supported for small installations)
– https://ibm-mas-manage.github.io/sno/
– Being incorporated into standard install documentation
• Troubleshooting
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=troubleshooting
Useful Resources

• Developer choices
– https://www.ibm.com/docs/en/maximo-manage/continuous-delivery?topic=administering-setting-up-local-
maximo-manage-development-environment (No MAS/no OCP)
– OpenShift Local (not production supported) mini-version of OCP running MAS/Manage
https://github.com/evilADevil/mas-local
– Install (multiple) shared MAS in the same OpenShift cluster
• References
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=reference
• Glossary
– https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=glossary
• EAM to MAS (Recording and PDF)
– https://community.ibm.com/community/user/asset-facilities/viewdocument/maximo-eam-to-maximo-application-
su?CommunityKey=3d7261ae-48f7-481d-b675-a40eb407e0fd&tab=librarydocuments
Thank you!