Upgrade Desk · Checklist

Maximo 7.6.1.x → MAS 9.2

The work, phase by phase, with the IBM page or published record behind each item. Items marked for your system depend on what you run. 31 items from IBM and the record, 25 specific to your system. Exports to Excel, PDF and Markdown with your ticks.

Back to the move · Upgrade Desk

Before the move

Your baseline

What you run decides what the move must carry. Inventory before you price.

• Work IBM's own upgrade checklist for Maximo Manage: version compatibility and upgrade paths, Java version changes and customisation recompilation, OpenShift cluster requirements, database backup and integrity validation, customisation and integration testing. — Upgrading Maximo Manage checklist (IBM)
• For your system: Inventory every automation script by launch-point type, and record which ones call custom Java classes or external endpoints.
• For your system: Inventory custom Java (MBO extensions, field classes, custom applications, report scriptlets) with the source-control location of each.
• For your system: Inventory object structures, publish channels, enterprise services, external systems and every endpoint address they use.
• For your system: Export every customised presentation (Application Designer) and every customised BIRT report design so the regression list has a baseline.
• For your system: Record the exact fix level you run today (product version, fix pack, interim fixes) — the whole plan prices against this.

Supported route

IBM names the source levels you can move from. Get to one of them, then confirm one hop or staged for your case.

• Get to a supported source level first: IBM requires Maximo Asset Management 7.6.0.10, 7.6.1.2 or 7.6.1.3 installed before the move to Maximo Manage. On the IBM Control Desk route to Maximo IT it is Control Desk 7.6.1.5 with Maximo Asset Management 7.6.1.3. Any other level is a fix pack of upgrade work before the upgrade starts. — IBM names three Maximo Asset Management levels you can upgrade to Maximo Manage from: 7.6.0.10, 7.6.1.2 or 7.6.1.3 (IBM)
• For your system: Confirm, for your exact source level, whether the move is one hop or must stage through an intermediate release.
• When upgrading from Maximo Asset Management 7.6.1.3 or earlier to Maximo Manage in MAS 9.1, the cron, mea, report and ui server bundles for Manage are installed. — When upgrading from Maximo Asset Management 7.6.1.3 or earlier to Maximo Manage in Maximo Application Suite 9.1, the cron, mea, report, and ui server bundles for Maximo Manage are installed (IBM)
• If you run IBM Control Desk: ensure version 7.6.1.5 is installed before upgrading to Maximo IT. — Ensure that you have IBM Control Desk version 7.6.1.5 installed before upgrading to Maximo IT (IBM)

Platform prerequisites

OpenShift, database and operator minimums surface as upgrade failures if found late.

• For your system: Minimum OpenShift Container Platform version, operator catalog and storage classes for the target release, against IBM's current compatibility matrix.
• For your system: Minimum database version for the target release, and whether your database vendor and edition are supported for every application you deploy.
• If you intend to move to Db2 12 with MAS 9.2: the upgrade is opt-in, requires a valid Db2 Warehouse license file, needs a complete backup first, and is irreversible. — A complete backup of the Db2 database is required before the upgrade from Db2 11 to 12 (IBM); The upgrade from Db2 11 to 12 is irreversible (IBM)
• CouchDB is replaced with MongoDB; Maximo Optimizer requires MongoDB installed and configured before deployment. — CouchDB is replaced with MongoDB (IBM); Maximo Optimizer requires MongoDB to be installed and configured before deployment (IBM)
• Manual deployment and installation-script deployment of applications are discontinued from MAS 8.10; plan on operator-driven deployment. — The manual deployment for applications and that use installation script for Maximo Application Suite are discontinued from Maximo Application Suite 8.10 (IBM)

Database and configuration

Pending configuration, custom triggers and integrity errors are the classic upgrade blockers.

• Before you start: review current database settings, disable custom triggers, commit any pending configuration changes, and back up the database and other important system files. — Reviewing database settings and backups (IBM); Commit any pending database configuration changes before upgrading Maximo Manage (IBM)
• Run the Integrity Checker before the upgrade to identify and fix data-dictionary and database integrity issues. — Running Integrity Checker before upgrade (IBM); Run the Integrity Checker utility regularly and before the upgrade to identify and fix database integrity issues (IBM)
• Known trap: Integrity Checker in repair mode can produce an exception due to auto-commit. — Integrity checker in repair mode produces exception due to auto-commit (IBM)
• Known trap on the classic → Manage migration: after the EAM upgrade to Manage, the Integrity Checker can report errors — schedule a post-migration run. — After EAM upgrade to Manage, integrity checker reports errors (IBM)
• For your system: A verified, restorable backup of the database and attachments exists and has been restored once to a scratch environment.

Customisations

Custom Java, automation scripts and screen changes are where a move actually breaks.

• Maximo Manage 9.1 runs on Java 17. IBM recommends recompiling Java customisations with Java 17, and states that migrating Manage from Java 8 to 17 requires diagnostics and testing. — Maximo Manage 9.1 supports Java 17 (IBM); Recompiling Java customizations with Java 17 is recommended (IBM); IBM Maximo Manage requires diagnostics and testing when migrating from Java 8 to Java 17 (IBM)
• Maximo Health 9.1 and Maximo Predict 9.1 move from JDK 16 to JDK 17. — Maximo Health 9.1 and Maximo Predict 9.1 upgrade from JDK 16 to JDK 17 (IBM)
• Migrate customisations by using customisation archives; understand how authentication, security and SMTP are implemented before you upgrade. — Preparing to upgrade (IBM)
• For your system: Every automation script that touches a deprecated property, a removed API or a changed behaviour on the move page has a test on the target release.
• For your system: Customised presentations render correctly under the target release's skin; check the UI versions page for what changed on screen without any change to the XML.
• Known trap: after a Maximo upgrade a new report development environment reflects the updated BIRT version and newer MXReport classes; some reports failed to show all expected data until re-tested. — Known Issues (IBM)

Integrations and authentication

Endpoints, auth model and queue contents are their own workstream.

• RMI is not supported in Maximo Manage; REST API is used instead for interactions from custom extensions or external applications. Re-point every RMI-dependent integration. — RMI is not supported in Maximo Manage (IBM); REST API is used instead of RMI for interactions with the product from custom extensions or external applications in Maximo Manage (IBM)
• User and group management APIs deprecated in MAS 9.1 are removed in 9.2; the User synchronization status page and MASUSERSYNC are gone. Port provisioning integrations to the 9.1 user management APIs and the relational user store. — The User synchronization status page is no longer available in Maximo Application Suite 9.2 (IBM)
• User Data Services (UDS) is deprecated and replaced with IBM Data Reporter Operator (DRO) starting in MAS 9.0, 8.11.7 and 8.10.10; from 9.0 you must migrate. — The User Data Services (UDS) is deprecated and replaced with IBM Data Reporter Operator (DRO) starting in Maximo Application Suite 9.0, 8.11.7, and 8.10.10 (IBM); Starting in Maximo Application Suite 9.0, if you are using IBM User Data Services, you must migrate to Data Reporter Operator (IBM)
• For your system: Inbound and outbound JMS queues are drained (or their contents preserved) before cutover, and the cron tasks that consume them are stopped in the right order.
• For your system: Every headless integration has a working credential on the target (API key or the identity provider flow you will use) and none depends on basic auth against a removed endpoint.
• For your system: Every external system endpoint address and certificate is updated for the target environment's routes.

Industry solutions and add-ons

Each add-on ships its own compatibility line; the suite upgrade does not carry them for free.

• Verify the compatibility of the industry solutions and add-ons you deploy. — Verify the compatibility of the industry solutions and add-ons (IBM)
• For your system: The required level of every industry solution and add-on at the target release, from each product's own compatibility line.
• Maximo Inventory Optimization is no longer available as an externally configured application from MAS 9.0; it is accessed by its dedicated URL. — Maximo Inventory Optimization is no longer available to be added as an externally configured application in 9.0 (IBM); IBM Maximo Inventory Optimization (IBM)
• Kepler GPUs are no longer supported in Maximo Visual Inspection 9.0. — Kepler GPUs are no longer supported in Maximo Visual Inspection 9.0 (IBM)

Licensing and AppPoints

Consumption modelling belongs before the contract, not after go-live.

• MAS is licensed in AppPoints; usage divides into reserved and concurrent, and the Suite License Service stores and manages the license. — Maximo Application Suite 9.1 uses AppPoints as a unit of measure by which the Program can be licensed (IBM); AppPoints usage is divided into reserved and concurrent usage (IBM); The Suite License Service (SLS) stores and manages the Maximo Application Suite license (IBM)
• Maximo Visual Inspection requires a separate license, with 45 AppPoints allocated per installation. — Maximo Visual Inspection requires a separate license, with 45 AppPoints allocated per installation (IBM)
• For your system: AppPoint consumption modelled at the target with the applications and user types you will actually enable, and signed off before the contract.
• Dual Support for MAS with Maximo Asset Management ends 30 April 2027: EAM 7.6.1.x is no longer supported after that date for Subscription Upgrade customers, and for Perpetual Trade-Up customers EAM usage rights expire. — EAM 7.6.1.x will no longer be supported after April 30, 2027 for Subscription Upgrade customers (IBM); After April 30, 2027, EAM usage rights expire and continued use would be out of compliance for Perpetual Trade-Up customers (IBM)

During the move

Mobile

Legacy mobile clients and the Maximo Mobile apps are a separate cutover.

• For your system: The move from legacy mobile clients to the Maximo Mobile apps is planned as its own workstream: device enrolment, offline data scope and app configuration per role.
• Known trap: file attachments to work orders stopped working on iPad and iPhone after a 7.6.1.2 interim fix. — No longer able to add file attachments to work orders when using an iPad or iPhone after 7612 IFIX (IBM)
• Known trap: in the Maximo Mobile Technician app, a user who switches locale to Swedish cannot enter meter readings on an assigned work order. — In the Maximo Mobile Technician app, when a User changes the locale language to Swedish, they cannot enter Meter Readings in an assigned Work Order (IBM)

Cutover rehearsal

A rehearsed window with a rollback story, or no window at all.

• For your system: A full rehearsal has run end to end on a production-sized copy, with the window measured and the rollback executed at least once.
• For your system: Configuration freeze, integration pause and communication plan are agreed with every upstream and downstream system owner.
• For your system: Go / no-go criteria are written down, with the smoke tests that decide them.

After the move

Post-upgrade validation

Every behaviour change on the move page is a regression test.

• For your system: Every behaviour change listed on the move page has been exercised on the target, and the result recorded.
• Redeploy all models after upgrading Maximo Visual Inspection. — Redeploy all models after upgrading Maximo Visual Inspection (IBM)
• Run the Integrity Checker again after the migration; errors after the EAM → Manage upgrade are a known report. — After EAM upgrade to Manage, integrity checker reports errors (IBM)
• For your system: Every customised BIRT report runs on the target and returns the same rows as the baseline export.
• For your system: Cron tasks, escalations and integration queues are running, and no message is stuck in an error queue.
• Retire the classic 7.6.1.x environment before 30 April 2027; for Perpetual Trade-Up customers continued use after that date would be out of compliance. — After April 30, 2027, EAM usage rights expire and continued use would be out of compliance for Perpetual Trade-Up customers (IBM)

Security catch-up

Confirm each security fix gained is active in the target build.

• MAS security bulletins can be searched by product, severity or publish date; review them for the target build. — Maximo Application Suite has security bulletins that can be searched by product, severity, or publish date (IBM)
• For your system: Each security change listed on the move page's security catch-up is confirmed present in the exact build you deployed.

Deprecation exit

For each deprecated item still in use: replacement adopted, or removal date noted.

• For your system: For each entry in the deprecation register that you used: the replacement is adopted, or the removal version is noted in the risk log.
• The SNMP business process agent is no longer included. — The SNMP business process agent is no longer included (IBM)