5 posts tagged “Maximo AI Service”

A dated, evidence-tiered reference to the Maximo Assistant and the Maximo AI Service as of October 2026. It traces the path from the 9.0 AI broker through 9.1, the January and April 2026 Feature Channel drops, 9.2 GA's agentic Assistant and MCP server, and the AI Service 9.2.3 patch level. It also covers the security bulletins, a full capability matrix, the model bill of materials, what the Assistant still cannot do, the Assist-versus-Assistant naming correction, and a checklist for verifying each capability in your own instance.

MAS 9 native analytics has a real ceiling. This post names it, then makes the honest IBM-native case for watsonx.data — open Apache Iceberg, fit-for-purpose engines, and a bridge to watsonx.ai your MAS AI Service license already opened.

The Maximo Assistant is not a checkbox — it's a deployment project. The real path: the Maximo AI Service operator on OpenShift, the watsonx.ai connection, training recommendation models on your own data, and the feedback loop that keeps them improving. Mapped to IBM's ten team-exploration tasks and the realistic 68–128 hour pilot estimate.

When something is broken and the technician doesn't know why, this is where the Maximo Assistant earns its keep. How step-by-step troubleshooting guidance walks from symptom to likely cause, how AI failure-code identification recommends failure class, problem, cause, and remedy codes, how Visual Inspection folds in visual diagnosis, and how PM optimization recommends which preventive work to cut, tighten, or extend.

What the Maximo Assistant actually is, the IBM watsonx.ai foundation models that power it, and the Maximo AI Service that connects the two. A grounded introduction to generative AI in MAS 9 — including an honest map of what it does and, just as importantly, what it does not do.