?? Important Update for IBM Maximo Users ??

?? Important Update for IBM Maximo Users ??

As we approach the end of support for IBM Maximo Asset Management 7.6.x, it's crucial for Maximo 7.6.1.x customers to plan their upgrade to the IBM Maximo Application Suite (MAS). Here are the key dates to keep in mind:

  • End of IBM Base Support for Maximo 7.6.x: September 30, 2025
  • End of IBM Extended Support for Maximo 7.6.x: September 30, 2026

Many customers are still unclear about how MAS differs from traditional Maximo 7.6.x. Below are some fundamental differences:

Architecture and Deployment Model

Maximo EAM (7.6) uses a monolithic architecture, meaning the application operates as a single unified unit with a single user interface, business logic, data access layer, and database. In contrast, MAS employs a microservices architecture, which consists of smaller, independent units. These services are lightweight and loosely coupled, leveraging OpenShift for deployment.

Database Model and Support

The database support remains unchanged, with options including DB2, Oracle, and SQL Server.

Application Server

Maximo EAM (7.6) supports WebSphere ND & Liberty and WebLogic, whereas MAS is compatible only with WebSphere Liberty.

UI/UX

Both versions offer the Classic and Work Centers interfaces. However, MAS also includes new skins and improved navigation.

Security and User Management

Maximo EAM (7.6) uses security controls via WebSphere/WebLogic and Maximo EAM (LDAP/VMM sync, native, or SAML). MAS provides enhanced security with MAS Authentication.

Integration and Message Queue

Maximo EAM (7.6) utilizes RMI, JMS, and REST for integration and message queuing. MAS, on the other hand, uses REST and Kafka, and supports JMS for external integration only.

Mobile

Maximo EAM (7.6) includes mobile capabilities specific to EAM. MAS enhances the mobile experience with a new interface.

Serviceability

Maximo EAM (7.6) relies on standard system error logs stored on the filesystem and can be monitored with Tivoli add-ons or third-party tools. MAS offers improved logging options with Elasticsearch, Fluentd, and Kibana, and includes monitoring with Prometheus and Grafana.

Operations

Maximo EAM (7.6) uses an Installation Manager for setup. MAS uses OpenShift Operators for installation, environment configuration, customization, and upgrades.

MAS Functional Areas

MAS supports a wide range of functional areas to ensure a seamless transition:

  • Attached Documents: Fully supported.
  • Reporting: BIRT reporting is supported.
  • Industry Solutions/Add-ons: All industry solutions and add-ons are supported.
  • Anywhere: Updated mobile apps are available for download.
  • Maximo Mobile: Combines all connected and disconnected functions into one application, with initial versions offering Assists, followed by Technician and Inspection.
  • Scheduler, Calibration, Linear: Fully supported.
  • Migration Manager: Fully supported.
  • Multi Language: Fully supported with all 25 languages.
  • SAP/Oracle Integration: Fully supported.
  • Third-party Add-ons: Existing third-party changes will be migrated only if they can be fully extracted into the customization archive.

High-Level Upgrade Approach for Maximo 7.6 to MAS

To upgrade from Maximo 7.6 to MAS, customers should follow these steps:

Maximo 7.6.x to MAS Upgrade

  1. Prepare the Database:
  2. Install and Configure MAS:
  3. Customization:
  4. Deploy and Configure Manage:
  5. Activate:

Staying ahead of these changes will ensure a smooth transition to IBM Maximo Application Suite and continued efficiency and support for your asset management needs.

Prepare now to leverage the advanced capabilities of MAS.

Libby Ingrassia

GBM

GBM Qatar

#ibmchampion

#IBM #Maximo #AIMigration #TechUpdate #EnterpriseSoftware #DigitalTransformation #OpenShift

?

要查看或添加评论,请登录

Rakesh Kumar的更多文章

社区洞察

其他会员也浏览了