Maximo Insights That Never Get Old

How to read MAXOBJECT counts as an add-on's real database footprint, why HSE ships inside Oil & Gas under one shared PLUSG prefix, why Aviation conflicts with almost everything, and the exact MAS 9 compatibility matrix that tells you which extensions can coexist.

Venkat AchantaJul 15, 2026Part 4 of 6

A developer's deep dive into the four-file MBO pattern behind every Maximo object, how MAXOBJECT.CLASSNAME links to the MBO Set, and how a PLUS extension layers on.

Venkat AchantaJul 15, 2026Part 1 of 6

MAS 9.1 moved the JVM under every Maximo customization from Java 11 to Java 17. MAS 9.2 (June 2026) adds Java 25 at the platform and AI-Service level while Java 17 stays the baseline for Manage and your custom code. Here is what changes for existing extensions, why 9.2 is a mixed Java-17/Java-25 environment, how to test and remediate, and why the extension model endured while everything around it modernized.

Venkat AchantaJul 15, 2026Part 6 of 6

How Maximo add-ons are activated in the MAS Manage component model, and how custom Java is now delivered as a Customization Archive baked into a container image on OpenShift instead of dropped into WebSphere — the old-world/MAS-world post for developers and upgrade teams.

Venkat AchantaJul 15, 2026Part 5 of 6

The reference every Maximo developer bookmarks: the complete PLUS prefix directory (PLUSA through PLUSV, TLOAM, custom), which prefixes are included capabilities versus paid add-ons versus legacy, the five-layer extension hierarchy, and exactly how Maximo stitches multiple add-ons into one MBO inheritance chain — with the WorkOrder and Asset chains resolved step by step.

Venkat AchantaJul 15, 2026Part 2 of 6

A developer's deep dive into product.xml — the extension control file behind every Maximo add-on. Learn the anatomy of mboset, mbo, class, field, and bean declarations, why alphabetical prefix order matters, what bytecode injection does at build time, and how the resolved top-of-chain class lands in MAXOBJECT.CLASSNAME so you can predict super() behavior.

Venkat AchantaJul 15, 2026Part 3 of 6

A developer's deep dive into how IBM Maximo add-ons and industry solutions extend the core through Java — PLUS prefixes, MBO inheritance chains, product.xml, bytecode injection, the compatibility matrix, the MAS 9 Customization Archive, and the Java 17 shift.

Venkat AchantaJul 15, 2026

Approving a work order looks different in MAS 9. Here's the honest picture — the Workflow Designer is unchanged and your 7.6 workflows carry forward, the new Approvals Role-Based Application replaces the Work Supervisor approval flow (with one gap), watsonx-powered Work Order Intelligence recommends a failure code with a confidence score at approval, and electronic signatures can be enforced on specific status changes for regulated work.

Venkat AchantaJul 15, 2026Part 2 of 6

Part 3 showed you how to consume the operational dashboard. This is the other half: how to build your own work order KPIs in MAS 9. The KPI Manager application, custom queries against any Maximo object, refresh intervals, green/yellow/red thresholds, trend calculations, matching a KPI to the right card type, and the MAS 9.1 ability for KPI services to return JSON from an external API.

Venkat AchantaJul 15, 2026Part 4 of 6

The work order integration surface moved in MAS 9. Here's the JSON API for work orders — /api/os/mxwodetail with lean=1 — with real query and create examples, Kafka events for near-real-time WO changes, and the honest posture on MIF: it still works, but new integrations belong on REST and Kafka.

Venkat AchantaJul 15, 2026Part 6 of 6

IBM's Operational Dashboard is the strategic replacement for Start Centers as the maintenance manager's command center. Here's what ships out of the box in MAS 9 Manage — the WO KPIs, the pre-built Maintenance Manager dashboard, the card types worth knowing — and the honest 9.1 limitation that keeps many teams running Start Centers side by side.

Venkat AchantaJul 15, 2026Part 3 of 6

BIRT is not formally deprecated in MAS 9 and your existing work order reports still run. The upgrade mistake is treating the report catalog as a rebuild backlog. Here's how to rationalize WO reporting into KPI Manager cards, keep the reports that must stay reports, and know exactly when Cognos Analytics earns the job.

Venkat AchantaJul 15, 2026Part 5 of 6