Architecture

Maximo Ecosystem Architecture Atlas

Evidence-grounded Maximo architecture from suite landscape to implementation detail — products, capabilities, relationships, version changes, sources, and explicit unknowns.

Three altitudes

The MAS suite explorer opens on the whole landscape, then descends: suite territory at 50,000 feet, then product and capability at 25,000, then the implementation detail a build actually needs at 5,000. Every brick and wire is drawn from the source-backed catalogue and carries the evidence state the validator enforces — including, where it applies, "not established". Components can be removed from the picture to model a system that does not run everything, and the result exports.

Quick reference — get your bearings in seconds

Ahead of the full interactive Atlas sits a short index of the diagrams practitioners ask for most:

• MAS platform — where Manage sits on OpenShift, MAS core, and the shared services around it.
• Maximo object & data model — MBOs, object structures, and the relationships the whole product is built on.
• Upgrading to MAS — the 7.6.1 → MAS 8.x → 9.x path and the landmines on the way.
• Work order lifecycle — WAPPR → APPR → INPRG → COMP → CLOSE and the status rules between.
• PM to work order — how preventive maintenance generates work from job plans, frequencies and meters.
• How approvals route — workflow versus escalation versus limits: who approves what, and when.

What the atlas will not do

It will not draw a relationship the published evidence does not support. Where the record is silent the atlas shows the gap rather than inferring a connection, which is the same rule the evidence method applies everywhere else on the site.