Maximo

Maximo Manage in MAS 9.2: Administration, Integration, and Developer Updates

# Maximo Manage in MAS 9.2: Administration, Integration, and Developer Updates

Maximo Manage remains the operational heart of IBM Maximo Application Suite. It hosts the asset registry, work order lifecycle, preventive maintenance engine, inventory and purchasing workflows, service requests, contracts, job plans, and the workflow engine that ties them together. In MAS 9.2, Manage receives both platform-level upgrades and application-level enhancements that affect how administrators configure the system, how developers build integrations, and how end users interact with data.

The most visible changes in Manage 9.2 fall into four areas: user management, communication and reporting, integration extensibility, and the Redwood-based user experience. Less visible but equally important are the patches that fix long-standing defects in preventive maintenance, invoices, inventory, receiving, and the scheduler. The Manage Operator patch 9.0.27, released on 25 June 2026, updates Manage to version 9.0.325 and includes fixes for duplicate reservations, mobile OSLC async failures, prorated service allocation, inventory condition code updates, and scheduler constraint population.

This article explores what Manage administrators and developers need to understand about MAS 9.2. It covers the user model changes, the SMTP OAuth and scheduled-report enhancements, the integration framework improvements, the Redwood experience, the developer tools and AI integration points, the defect fixes that matter for production stability, and how to approach testing and migration.

User Management and the End of the Versioned User Record

One of the most consequential changes in MAS 9.2 is the removal of the versioned user record. In earlier releases, the user record in Manage was versioned, which created friction for bulk updates, synchronization with external identity providers, and automated provisioning workflows. Administrators often had to work around the versioned record when updating user attributes, roles, or person-group assignments through automation scripts or external tools.

In 9.2, the versioned user record is gone. User records can be updated through standard Manage database operations like other business objects. This has several practical effects. Bulk updates become simpler because there is no need to manage record versions. Integration flows that push user data from an HR system or identity provider can write directly without worrying about stale versions. Support teams can make corrections faster.

The change also aligns with the cross-suite user management capability introduced at the MAS platform level. User identity can be managed more consistently across Manage, Monitor, Health, Predict, and other suite applications. The coupling to MongoDB that complicated earlier releases is reduced, which simplifies architecture and troubleshooting.

For developers, the change may require updates to existing automation scripts. Any script that explicitly handled the versioned user record, or that relied on the previous behavior, should be reviewed. The good news is that most scripts become simpler. The risk is that scripts that were written for the old model may fail silently if they assume the version field still exists.

Administrators should also revisit their user provisioning runbooks. With bulk updates now straightforward, organizations that previously used complex workarounds may be able to retire them. This is a good opportunity to standardize how users are created, deactivated, and assigned to sites, security groups, and labor records.

A typical post-upgrade user management workflow might look like this:

| Step | Action | Owner |

|---|---|---|

| 1 | HR system publishes user changes to MAS | Identity team |

| 2 | Automation script or integration updates Manage user record | Maximo admin |

| 3 | Security groups and person-group assignments are applied | Maximo admin |

| 4 | Cross-suite sync propagates identity to Monitor, Health, Predict | Platform team |

| 5 | User logs in through SAML and lands in role-based application | End user |

OAuth2 SMTP and Scheduled Report Sender Control

Email has been a persistent pain point in Maximo environments. In MAS 9.2, two related improvements make outbound communication more flexible and more secure. The first is OAuth2 authentication for SMTP. The second is the ability to control the send-from address on scheduled reports.

OAuth2 SMTP matters because many enterprise mail providers, including Microsoft 365, are deprecating basic authentication. A Manage environment that relied on username and password SMTP authentication could suddenly stop sending notifications when the mail provider enforces modern authentication. MAS 9.2 addresses this by allowing administrators to configure an OAuth client in the Endpoints application and then reference that client through a system property. The configuration is similar to other OAuth-based integrations in Manage, which lowers the learning curve.

The high-level OAuth2 SMTP setup in Manage looks like this:

1. Register an OAuth client in your corporate identity provider, such as Azure AD.

2. In the Manage Endpoints application, create an OAuth2 endpoint with the client ID, client secret, token endpoint, and scopes.

3. Set the suite-level system property that names the OAuth client to use for SMTP.

4. Configure the communication template or system property to send mail through the OAuth-enabled endpoint.

5. Test with a workflow notification or escalation to confirm token refresh and delivery.

The scheduled report enhancement resolves a different but equally common issue. Historically, scheduled reports were sent from the user who scheduled them. In many organizations, that user was an administrator, which meant recipients saw reports coming from individuals rather than a service account. Workarounds using automation scripts or custom report scheduling were common. In 9.2, administrators can configure the send-from address directly, making the origin of scheduled reports consistent and professional.

Both features require planning. OAuth2 SMTP needs an OAuth client registered in the corporate identity platform, the correct scopes, and a credential rotation process. The scheduled report sender needs coordination with the mail team to ensure the chosen address is allowed to relay and that recipients recognize it. These are small changes, but they touch identity, mail, and compliance domains, so they benefit from a documented change-control process.

Integration Framework: JSON Mapping and Automation Scripts

The Maximo Integration Framework (MIF) continues to be the primary mechanism for moving data into and out of Manage. In MAS 9.2, the framework remains powerful, but some gaps still require developer creativity. One example is JSON Mapping, which IBM supports for Publish Channels and Enterprise Services but not for Invocation Channels.

Amin Chakri, an IBM Maximo technical expert, documented a practical workaround for this constraint. The approach uses a short automation script to invoke the Maximo JSON mapper engine programmatically. The script instantiates the ExternalJSONMapper class, applies the configured mapping to the Object Structure data, converts the result to bytes, and returns it as the outbound payload. The benefit is that existing JSON Mapping configurations can be reused without manual JSON construction in scripts and without custom Java development. It also keeps transformation logic separated from integration logic.

A simplified representation of the pattern is:

// Inside an automation script invoked by an Invocation Channel
from psdi.iface.router import ExternalJSONMapper
mapper = ExternalJSONMapper()
mappedBytes = mapper.map(osName, ifaceName, action, messageData)
# mappedBytes becomes the outbound payload for the invocation channel

This pattern illustrates a broader truth about MAS 9.2 Manage development: automation scripts remain the swiss army knife. Whether the task is mapping JSON, enforcing business rules, or extending the UI with custom actions, the automation script engine is the fastest path. MAS 9.2 ships with examples such as the "take ownership" action that demonstrates how custom actions can call automation scripts.

Developers should also be aware of the MAS 9.2 MCP Server, which allows external agents to integrate directly with Manage APIs. This opens the door to agentic workflows where AI systems can read and act on Manage data through governed interfaces. The security model remains granular, with role-aware access and Maximo permissions inherited by any integrated agent.

For integration developers, the takeaway is to review each channel and script for 9.2 compatibility. Channels that use JSON transformations, OAuth endpoints, or custom actions should be regression-tested. Scripts that touch user records, API keys, or integration event handlers should be validated against the new stack.

Redwood UI, Attachments, and Field Experience

The Redwood user experience continues to expand in Manage 9.2. New applications are added with Redwood interfaces, and existing applications receive incremental improvements. One notable addition is the ability to add attachments in contexts where the classic UI either lacked the feature or required non-trivial configuration. In 9.2, attachments are available out of the box in more places, reducing the need for custom solutions.

The Redwood Document Records page now supports previewing committed attachments while editing document records. This small change improves data entry accuracy because users can confirm the correct document is attached before saving. For records management and compliance workflows, this is a meaningful quality improvement.

Another Redwood improvement is user-configurable left-hand navigation. Users can arrange their navigation to match their role, which reduces the time spent hunting for applications. For administrators, this means spending more time designing sensible default navigation for roles and less time fielding requests for custom Start Centers.

Operational Dashboards also continue to mature. MAS 9.2 adds the ability for dashboards to pull from non-Manage applications within the suite. A maintenance supervisor can now see work order backlog, asset health scores, and monitor alerts in a single dashboard without needing separate integrations. The dashboard framework supports iframes, role-based access, and focus mode for distraction-free work.

Focus mode is a small but meaningful addition. In environments where technicians work in noisy plants or outdoors, reducing screen clutter can improve accuracy and speed. Administrators should consider which roles benefit most from focus mode and configure default layouts accordingly.

Developer Tooling and the MCP Server

MAS 9.2 introduces the MCP Server, which allows external agents to call Manage APIs through a governed interface. MCP stands for Model Context Protocol, and the intent is to let AI agents participate in operational processes without manual coordination between disconnected tools. For Manage developers, this is a new integration pattern to consider.

The practical use cases are still emerging, but the immediate value is clear. An agent could query open work orders for a set of assets, summarize overdue inspections, or check inventory levels for a planned job. Because the agent uses Maximo security and permissions, it cannot see or do anything that the underlying user role cannot. This respects the governance model that enterprises already trust.

Developers should experiment with the MCP Server in a lab environment before exposing it to production workloads. Key questions to answer include: which agents are allowed to connect, which APIs they need, how their sessions are audited, and what rate limits or quotas apply. The MCP Server is a capability, not a default configuration. It should be enabled deliberately.

Beyond MCP, MAS 9.2 continues to support the automation script engine, Java-based extensions, REST APIs, and the Maximo Integration Framework. The recommended approach for new development is to prefer configuration and automation scripts over custom Java, and to prefer REST APIs over direct database access. This reduces upgrade friction and makes the system easier to support.

Defect Fixes That Stabilize Production

The Manage Operator patch 9.0.27 release notes show the kind of production issues that keep administrators up at night. Several fixes stand out.

Defect DT458077 addresses a preventive maintenance problem where a work order failed to change status to APPR with the error "BMXAA4590E - Could not change Work Order status to APPR," yet the system still created reservations, including duplicate reservations for both new and used condition codes. This fix prevents inventory inconsistencies that could ripple through purchasing and scheduling.

Defect DT458514 fixes mobile OSLC async job fetching, where some requests never completed and eventually returned a 400 error after repeated 202 responses. Mobile users depend on async jobs for background data sync, so this fix improves field reliability.

Invoice fixes DT461631 and DT462561 correct prorated cost allocation for services, ensuring that line cost updates recalculate the total services to allocate correctly. For organizations with complex service contracts, these fixes protect financial accuracy.

Inventory and receiving fixes DT464379 and DT464675 address balance updates after condition code changes and GL account validation on receipts. These are foundational to trustworthy inventory records.

Finally, DT466872 in Scheduler and Crew addresses a failure where GS-LP failed to populate constraints and the Gantt view with error BMXAT0137E due to SQL validation rejecting an internal SKDCONSTRAINT update. Scheduler users will recognize how disruptive this class of issue can be for weekly planning cycles.

The table below summarizes these fixes and the business risk they address.

|---|---|---|---|

| DT462561 | Inv

...