Maximo Assistant on MAS 9: A Practical Six-Part Guide to the watsonx-Powered Assistant
Who this is for: Maximo administrators, maintenance leaders, and technical teams deciding whether — and how — to turn on the generative AI in MAS 9. If you want to know what the Maximo Assistant actually does, what it does not do, and what it costs to run, this series is for you. If you are building the full asset-intelligence pipeline, the other MAS add-on series (Health, Predict, Monitor, Visual Inspection) cover their own ground; this series is the deep treatment of the AI layer that sits across all of them.
Read time: ~14 minutes for this index | Full series: ~2 hours
Why This Series Exists
Generative AI is the single most over-promised and under-explained capability in MAS 9. Every vendor deck has a chatbot on it. Every upgrade conversation eventually reaches the question: "So does Maximo do AI now?"
The honest answer is: yes, and it is more specific — and more bounded — than the marketing suggests. The Maximo Assistant is real. It is powered by IBM watsonx.ai foundation models. It can draft a work order from a plain-English description, translate a natural-language question into a Maximo query, recommend a failure code with a confidence score, and surface similar historical records so a new technician benefits from a veteran's past fix. That is genuinely useful, and it represents the biggest change in how people interact with Maximo since the web UI replaced the fat client.
But it is an assistant, not an oracle. It drafts; you approve. It recommends; you accept, modify, or reject. It learns from your data, which means it is only as good as the two-plus years of work-order history you feed it. And it does not come for free — it needs watsonx.ai, the Maximo AI Service on OpenShift, trained models, a feedback loop, and AppPoints to license it.
Most teams meet this capability through a demo and a licensing line item, then discover the gap between "the demo drafted a work order" and "our technicians trust it in production." This series closes that gap. Six parts, each grounded in documented MAS 9.0 and 9.1 behavior, each concrete about what watsonx does and does not do.
Where This Series Fits
If you have read the broader MAS add-ons material, you already met the Assistant briefly — MAS-FEATURES Part 14 touches the AI Assist capability as one add-on among many, and the Work Order Operations series mentions Work Order Intelligence recommending failure codes at approval. Those are the one-paragraph introductions.
This series is the deep treatment. Where MAS-FEATURES gives you the headline, this series gives you the foundation model beneath it, the deployment project behind it, and the governance decisions around it. Here is the division of labor so you never read the same thing twice:
| If you want… | Read… |
|---|---|
| A one-page overview of AI Assist as an add-on | MAS-FEATURES — Part 14 |
| How failure-code recommendation appears at WO approval | MAS WORK ORDER OPS — Part 2 (Approvals) |
| ML failure prediction (a different capability) | MAS PREDICT series |
| The Assistant end to end — foundation, features, deployment, governance | This series |
A note on naming: IBM uses "Maximo AI Assist" for the recommendation and assistance features and "Maximo Assistant" for the conversational interface. They are the same capability family running on the same watsonx.ai foundation through the same Maximo AI Service. This series treats them as one, because you deploy and govern them as one.
What the Assistant Actually Does — At a Glance
Before you pick a reading path, it helps to see the whole capability surface on one page. Everything in the six parts is an expansion of one of these rows. None of it is invented — this is the documented set of things the Assistant does in MAS 9, and the boundaries around each are where trust is won or lost.
| Capability | What it does concretely | Where it lives in the series |
|---|---|---|
| Conversational assistant | Ask questions and issue requests in plain language inside MAS | Part 1 |
| Natural-language work order creation | Draft a work order from a plain-English problem description | Part 2 |
| AI-powered asset search | Replace filter queries with plain-English asset searches | Part 2 |
| Field value recommendations | Suggest priority, work type, failure codes, craft, and more — each with a confidence score | Part 2 |
| Similar-record detection | Surface similar historical work orders and service requests | Part 3 |
| Knowledge base search | Pull answers from manuals, SOPs, and repair narratives | Part 3 |
| Remote technician assistance | Step-by-step field guidance and expert connection | Part 3 |
| Guided troubleshooting | Walk a tech from symptom to check to likely cause | Part 4 |
| Failure-code identification | Recommend failure class, problem, cause, and remedy codes | Part 4 |
| PM optimization | Recommend which PMs to cut, tighten, or extend | Part 4 |
Read that list twice, because it is also a list of things the Assistant does not do. It does not run your integrations, restructure your data model, forecast failures (that is Maximo Predict, a different application), or take any action without a human confirming it. Every row above ends with a person deciding. That single fact — recommender, not decider — is the spine of the whole series.
What You Need to Run It
The second thing worth knowing before you start is that none of these capabilities is a switch you flip in Manage. They are served by the Maximo AI Service, a workload you deploy on OpenShift and connect to watsonx.ai, running models trained on your data. Part 5 walks the full deployment; here is the prerequisite checklist so the scope is honest from page one:
| Prerequisite | Why it is required | Covered in |
|---|---|---|
| A watsonx.ai instance (SaaS or on-premises) | Supplies the foundation models behind natural language and generation | Parts 1, 5, 6 |
| The Maximo AI Service on OpenShift | The bridge that connects watsonx.ai to Manage, Mobile, and the rest — nothing works without it | Parts 1, 5 |
| 2+ years of failure-coded work order history | The recommendation models learn from your data, not IBM's — thin history means weak recommendations | Parts 2, 5 |
| A trained set of recommendation models | Field, failure-code, and similar-record recommendations are trained per environment | Parts 2, 4, 5 |
| AppPoints entitlement | The shared MAS licensing currency that gates who gets AI access | Part 6 |
| A governed feedback loop | Turns everyday accept/reject decisions into a model that improves over time | Parts 5, 6 |
<aside>
💡 Key insight: The most common way teams get this wrong is scoping it as a software install. The operator install is a day or two. The prerequisites that actually determine value — clean historical data, trained models, a governed feedback loop, the right people with access — are weeks of work spanning platform, data, and maintenance disciplines. If you internalize only one thing from this index, make it that.
</aside>
The Series at a Glance
| Part | Title | Focus Area | Read Time |
|---|---|---|---|
| 1 | Intro & the watsonx Foundation | What the Assistant is, the watsonx.ai foundation, the AI Service, what it does not do | 15 min |
| 2 | Natural-Language Work Guidance | NL work order creation, plain-English asset search, confidence-scored field recommendations | 17 min |
| 3 | SME Collaboration & Knowledge Capture | Knowledge base search, similar-record detection, connecting field techs to experts | 16 min |
| 4 | Guided Troubleshooting Flows | Step-by-step diagnostics, failure-code identification, PM optimization recommendations | 16 min |
| 5 | Configuration & Deployment | AI Service operator, watsonx.ai connection, model training, the feedback loop | 18 min |
| 6 | Governance, Data Privacy & AppPoints | SaaS vs on-premises data residency, human-in-the-loop control, AppPoints licensing | 17 min |
Part-by-Part Guide
Part 1: Intro & the watsonx Foundation
[Read Part 1 — Maximo Assistant Intro & the watsonx Foundation](/blog/mas-assist-intro-watsonx)
Read time: 15 minutes
Before you can use the Assistant well, you need to know what it is standing on. This post covers the watsonx.ai foundation, the conversational assistant interface, the Maximo AI Service that connects the two, and — most importantly — an honest map of what generative AI in Maximo does and does not do.
You learn:
- What the Maximo Assistant is, in one clear definition
- How watsonx.ai foundation models power natural-language understanding and recommendations
- What the Maximo AI Service is and why nothing works without it
- The five things the Assistant does today (queries, search, drafting, recommendations, troubleshooting)
- The honest boundaries: it drafts but does not decide, and it learns only from your data
Part 2: Natural-Language Work Guidance
[Read Part 2 — Natural-Language Work Guidance](/blog/mas-assist-natural-language-work-guidance)
Read time: 17 minutes
This is the feature people mean when they say "AI in Maximo." This post covers drafting a work order from a plain-English description, searching assets without building a filter query, and the confidence-scored field recommendations that fill priority, work type, and failure codes as you type.
You learn:
- How natural-language work order creation drafts a WO from a sentence — and why it stops at "would you like me to submit it?"
- How plain-English asset search translates to Maximo queries
- The full list of fields the AI recommends in Manage 9.1, and how confidence scores work
- Why accept/modify/reject matters as much as the recommendation itself
- The data prerequisite that makes or breaks recommendation quality
Part 3: SME Collaboration & Knowledge Capture
[Read Part 3 — SME Collaboration & Knowledge Capture](/blog/mas-assist-sme-collaboration-knowledge)
Read time: 16 minutes
Your best fixes live in the heads of your most experienced technicians and in the long-description fields nobody reads. This post covers how the Assistant turns that buried knowledge into something a first-year tech can use — knowledge base search, similar-record detection, and connecting field workers to experts.
You learn:
- How knowledge base search pulls from manuals, SOPs, and historical repair narratives
- How similar-record detection transfers knowledge from veterans to new staff
- How remote technician assistance connects the field to subject-matter experts
- Why your work-order long descriptions are suddenly an asset, not a dumping ground
- The knowledge-capture habits that make the Assistant smarter over time
Part 4: Guided Troubleshooting Flows
[Read Part 4 — Guided Troubleshooting Flows](/blog/mas-assist-guided-troubleshooting)
Read time: 16 minutes
When something is broken and the tech does not know why, this is where the Assistant earns its keep. This post covers step-by-step troubleshooting guidance, AI failure-code identification, the tie-in to Visual Inspection, and PM optimization recommendations that tell you which preventive work to cut, tighten, or extend.
You learn:
- How troubleshooting guidance walks a technician from symptom to check to likely cause
- How failure-code identification recommends failure class, problem, cause, and remedy codes
- How the Assistant integrates with Visual Inspection for visual diagnosis
- How PM optimization flags low-value, too-frequent, and too-infrequent PMs
- Where guided flows help most — and where they still need a human's judgment
Part 5: Configuration & Deployment
[Read Part 5 — Configuration & Deployment](/blog/mas-assist-configuration-deployment)
Read time: 18 minutes
The Assistant is not a checkbox. This post covers the real deployment path: the Maximo AI Service operator on OpenShift, the watsonx.ai connection, model training on your data, and the feedback loop that keeps recommendations improving — mapped to IBM's own team exploration tasks and effort estimates.
You learn:
- The components of the Maximo AI Service (operator, model management, connector, feature store, inference, feedback loop)
- The end-to-end setup: watsonx.ai, AI Service, training data, model training, user training
- IBM's ten team-exploration tasks and the realistic 68–128 hour pilot estimate
- Why 2+ years of clean failure-coded history is the true prerequisite
- How the feedback loop turns accept/reject signals into better models
Part 6: Governance, Data Privacy & AppPoints
[Read Part 6 — Governance, Data Privacy & AppPoints](/blog/mas-assist-governance-privacy-apppoints)
Read time: 17 minutes (Series Finale)
Generative AI is a governance conversation before it is a technology one. This finale covers the data-residency decision baked into SaaS-versus-on-premises watsonx.ai, the human-in-the-loop controls that keep AI a recommender not a decider, and the AppPoints licensing that gates who gets access.
You learn:
- How the SaaS-vs-on-premises watsonx.ai choice is really a data-residency decision
- Why confidence scores and accept/modify/reject are your primary governance controls
- How the feedback loop must be governed, not just enabled
- How AppPoints license AI Assist, and why it may already be in your Premium contract
- A go-live governance checklist for AI features
Recommended Reading Paths
The Evaluator
"Should we even turn this on?"
Read: Part 1 → Part 6 → Part 5
Start with what it is, jump to the governance and licensing reality, then judge the deployment effort. You will know within three posts whether this is a this-quarter project or a next-year one.
The Maintenance Leader
"What will my planners and techs actually use?"
Read: Part 2 → Part 3 → Part 4
Start with work guidance, then knowledge and troubleshooting — the three surfaces your people touch daily. Skip the plumbing.
The Platform Team
"We have to build and run it."
Read: Part 5 → Part 1 → Part 6
Start with deployment, back-fill the foundation, then lock down governance and data privacy before go-live.
Key Themes Across the Series
It is an assistant, not an agent. Every capability ends with a human decision. The Assistant drafts a work order and asks "would you like me to submit it?" It recommends a failure code with a confidence score; you accept, modify, or reject. Treat it as a very fast, very well-read junior colleague — not as an autopilot.
It learns from your data. watsonx.ai supplies the language understanding, but the recommendations are trained on your history. Two-plus years of work orders with real failure codes is the difference between recommendations people trust and recommendations people mute. Garbage in, muted out.
Deployment is a project. watsonx.ai, the AI Service operator, model training, and a feedback loop add up to a 2–3 week pilot for a focused team — not a feature flag. Budget for it honestly.
Governance comes first. Where your data goes (SaaS vs on-premises watsonx.ai), who can use the AI (AppPoints), and how you keep humans in the loop (confidence + accept/reject) are decisions to make before go-live, not after.
The feedback loop is the engine. Accept/modify/reject is not just a UX nicety — it is the training signal. A governed feedback loop is what turns a mediocre day-one model into a genuinely helpful one by month six.
Version matters — confirm what you are on. The full conversational Assistant, natural-language search, and multi-language recommendations are strongly associated with MAS 9.1. Earlier recommendation-oriented AI Assist features exist in 9.0, but the complete conversational experience is a 9.1 story. Throughout the series we flag where a capability is version-gated, and the single most useful thing you can do before planning is confirm exactly which MAS version — and which of these features — your environment actually has.
<aside>
💡 Key insight: These themes are not six separate lessons — they are one lesson viewed from six angles. The Assistant is a bounded, trained, governed recommender. Every part of this series is really an argument that the boundaries are the feature, not a limitation. A maintenance system of record earns trust precisely because it does not let an AI act alone — and that is why this one is safe to put in front of the people who keep your plant running.
</aside>
References
- IBM Maximo Application Suite Documentation
- Maximo Manage — AI capabilities (IBM Documentation)
- IBM watsonx.ai Documentation
- AppPoints Licensing (IBM Documentation)
Series Navigation
| Previous: | You are at the beginning of the series |
|---|---|
| Next: | Part 1 — Intro & the watsonx Foundation |
About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.
Published by TheMaximoGuys | July 2026
Manasa Ganga
