7 part series
A grounded six-part series on the Maximo Assistant and AI Assist in MAS 9 — the watsonx.ai foundation, natural-language work guidance, SME collaboration and knowledge capture, guided troubleshooting, the AI Service deployment path, and the governance, data-privacy, and AppPoints decisions that gate it. Written for teams who want to know what generative AI in Maximo actually does, and what it does not.
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.
The feature people mean when they say 'AI in Maximo.' How the Maximo Assistant drafts a work order from a plain-English description, replaces filter queries with natural-language asset search, and recommends field values — priority, work type, failure codes, craft — each with a confidence score you can accept, modify, or reject.
Your best fixes live in your veterans' heads and in long-description fields nobody reads. Here's how the Maximo Assistant surfaces them — knowledge base search across manuals, SOPs, and repair narratives; similar-record detection that transfers knowledge from experienced staff to new staff; and remote technician assistance that connects the field to subject-matter experts.
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.
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.
Generative AI is a governance conversation before it is a technology one. The data-residency decision baked into SaaS-versus-on-premises watsonx.ai, the human-in-the-loop controls (confidence scores and accept/modify/reject) that keep the AI a recommender not a decider, the feedback loop as a governed data process, and the AppPoints licensing that gates who gets access — with a go-live governance checklist.
