IBM Maximo/MAS release timeline.

For users

Cleaner suite navigation and stronger role-based entry points.

For admins

OpenShift-first lifecycle operations, identity hardening, and entitlement review checkpoints.

For developers

Java 17 compatibility work, API governance, and extension review become central upgrade tasks.

For users

More modern work-center patterns and improved dashboard expectations.

For admins

Configuration governance, migration package testing, and performance baselines move earlier in the plan.

For developers

Automation scripts and integrations need compatibility testing against updated runtimes.

For users

Technicians get more role-specific flows for inspections and work execution.

For admins

Offline data scopes and sync policy design become adoption-critical.

For developers

Mobile configuration extensions should be tested by role and network state.

For users

Suite experience consolidates more Maximo capabilities under MAS.

For admins

Platform readiness, AppPoints planning, and OpenShift capacity become upgrade gates.

For developers

Custom code needs runtime, security, and API review before migration.

For users

Asset condition signals become easier to surface for operations teams.

For admins

Device ingestion and alert thresholds need clearer ownership.

For developers

Event pipelines and downstream work creation should be observable.

For users

Reliability teams get clearer asset health scoring and intervention cues.

For admins

Asset hierarchies and data quality directly affect health model usefulness.

For developers

Analytics integrations need stable identifiers and governed data contracts.

For users

Predictive maintenance use cases shift from pilots to production decision support.

For admins

Model monitoring and business process ownership are required for sustained value.

For developers

Prediction outputs should connect to work creation and review workflows.

For users

Manage teams see incremental usability and operational improvements.

For admins

Upgrade testing should focus on automation, reporting, and security groups.

For developers

Integration object structures and scripts remain the main regression surface.