MaximoInsider

MAS Platform & Upgrades

What Maximo teams should watch in MAS 9.1

A practical read on upgrade sequencing, OpenShift readiness, Java impacts, mobile adoption, and where AI belongs in the roadmap.

Kevin Arhagba8 minMay 4, 2026MAS 9.1 / Manage 9.1 tested

TL;DR

MAS 9.1 planning should start with platform readiness, not feature demos. Confirm OpenShift capacity, identity, integration observability, and rollback ownership before scheduling application work. Then sequence Manage, Mobile, and AI pilots by operational risk instead of by product excitement.

What changed for Maximo teams in MAS 9.1?

MaximoInsider is preparing this analysis in Sanity. The current launch draft keeps the article route, metadata, citation tools, and newsletter capture live while editorial content is finalized.

How should teams sequence the upgrade?

MaximoInsider is preparing this analysis in Sanity. The current launch draft keeps the article route, metadata, citation tools, and newsletter capture live while editorial content is finalized.

What should administrators check first?

MaximoInsider is preparing this analysis in Sanity. The current launch draft keeps the article route, metadata, citation tools, and newsletter capture live while editorial content is finalized.

Where do mobile and AI pilots fit?

MaximoInsider is preparing this analysis in Sanity. The current launch draft keeps the article route, metadata, citation tools, and newsletter capture live while editorial content is finalized.

What changed since the last version?

MaximoInsider is preparing this analysis in Sanity. The current launch draft keeps the article route, metadata, citation tools, and newsletter capture live while editorial content is finalized.

bash
mas upgrade readiness --check platform identity integrations mobile

Readiness Checklist

  • - Confirm OpenShift sizing, storage classes, and ingress ownership.
  • - Map identity, SSO, and role changes before user acceptance testing.
  • - Inventory integrations by business criticality and retry behavior.
  • - Create a release rehearsal with rollback criteria and named owners.
  • - Pilot Mobile with one high-value technician role before broad rollout.