Maximo Assistant on MAS 9: A Practical Eight-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: ~16 minutes for this index | Full series: ~2.5 hours | Updated: 20 October 2026 — expanded to eight parts for MAS 9.2
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. (In MAS 9.2 it became agentic — it can act as a single agent across a defined set of AI tools — but the tools are ones you expose and a human still confirms every write. More on that below.) 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. Eight parts, each grounded in documented MAS 9.0, 9.1, and 9.2 behavior, each concrete about what watsonx does and does not do — and, from Part 7 on, explicit about where IBM-documented capability ends and what you would have to build yourself begins.
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 (corrected October 2026). An earlier version of this index said "Maximo AI Assist" and "Maximo Assistant" were the same capability family. That was wrong, and the two names are worth keeping apart:
| Name | What it actually is | Status (Oct 2026) |
|---|---|---|
| Maximo Assist | The original MAS 8.x add-on for technician assistance — remote-expert video collaboration and knowledge sharing | Lives on as Maximo Collaborate in MAS 9.x; MAS 9.2 deprecates Collaborate as a suite add-on and makes it an add-on of Maximo Manage |
| Maximo Assistant | The watsonx-powered generative assistant (GA in MAS 9.1), configured in the AI configuration app and served by the Maximo AI Service | Agentic in MAS 9.2; extended by the Maximo MCP server |
This series keeps its "MAS ASSIST" series name, but everything it describes as the Assistant is the generative product. Where we touch remote-expert collaboration (Part 3), that is Collaborate, and we label it so.
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 eight parts is an expansion of one of these rows. The Evidence column says how firmly each row is grounded: IBM-documented means IBM describes it for the Assistant/AI Service; IBM, other product means IBM documents it, but under a different product; Build (9.2 MCP) means IBM gives you the toolkit but not the feature — you build it.
| Capability | What it does concretely | Evidence | Where it lives in the series |
|---|---|---|---|
| Conversational assistant | Ask questions in plain language in Manage, Health, and dashboards; agentic across a defined tool set in 9.2 | IBM-documented (9.1; agentic 9.2) | Parts 1, 8 |
| Natural-language work order creation | Draft a work order from a plain-English problem description | IBM-documented (9.2 MCP write examples) | Part 2 |
| AI-powered search | Replace filter queries with plain-English searches — assets, SRs, WOs, meters, PMs by default; any enabled Manage object since April 2026 | IBM-documented | Part 2 |
| Field value recommendations | Suggest priority, work type, failure codes, craft, and more — each with a confidence score | IBM-documented (9.1) | Part 2 |
| Similar-record detection | Surface similar work orders and records (9.1) and similar tickets (9.2 Tickets app) | IBM-documented | Part 3 |
| Knowledge base search | Pull answers from manuals, SOPs, and repair narratives | IBM-documented (docsearch config) | Part 3 |
| Remote-expert collaboration | Connect a field tech to an SME | IBM, other product — Maximo Collaborate (ex-Assist) | Part 3 |
| Guided troubleshooting | Walk a tech from symptom to check to likely cause | IBM-documented ("How do I…" prompts) | Part 4 |
| Failure-code identification | Recommend failure class, problem, cause, and remedy codes | IBM-documented (9.0+) | Part 4 |
| PM optimization | Recommend which PMs to cut, tighten, or extend | TMG assessment — confirm in your build | Part 4 |
| Query supply-chain objects | Ask about items, inventory balances, and PRs in plain language | IBM-documented once an admin enables those objects (April 2026 FC "supports all objects") | Parts 2, 5, 7 |
| Create an item from a description | Draft a new item master record for review | Build (9.2 MCP) — not native | Part 7 |
| Draft a purchase requisition | Assemble PR lines from a request and leave it in WAPPR | Build (9.2 MCP) — not native | Part 7 |
| Duplicate-item similarity | Flag "this item probably already exists" before creation | Build (9.2 MCP + your own similarity) — not native | Part 7 |
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. In MAS 9.2 the Assistant can act — IBM's documented write examples are changing a work order status, creating a follow-up work order, and creating a service request through the Maximo MCP server — but only through tools you expose, and every write still ends with a person confirming. That single fact — a human decides — 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 |
💡 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.
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 records and tickets, where Maximo Collaborate (ex-Assist) fits for expert connection | 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 |
| 7 | Supply Chain with the Assistant | Querying items, inventory, and PRs natively vs building item-creation, PR-drafting, and similarity tools on the 9.2 MCP server | 18 min |
| 8 | What Maximo Assistant Can Do Today | The October 2026 capability map — documented, announced, and build-it, by version | 15 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 and similar-record detection — and where remote-expert connection fits, which is Maximo Collaborate (the former Maximo Assist add-on), not the generative Assistant.
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
- Why connecting the field to subject-matter experts is a Maximo Collaborate (ex-Assist) job, not an Assistant feature
- 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
Generative AI is a governance conversation before it is a technology one. This part 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
Part 7: Supply Chain with the Assistant
[Read Part 7 — Supply Chain with the Assistant: Creating Items, Drafting PRs, and Similarity Search](/blog/mas-assist-supply-chain-items-prs-similarity)
Read time: 18 minutes
Storerooms and buyers ask the obvious question: can the Assistant create an item, raise a PR, or tell me the part already exists? This post separates what is native — querying supply-chain objects once an admin enables them — from what you build on the MAS 9.2 Maximo MCP server with object structures, automation scripts, and workflows, with a human confirmation step on every write.
You learn:
- Which supply-chain questions the Assistant answers natively after you enable ITEM, INVENTORY, and PR objects
- How to expose item creation as an MCP tool that lands records in PENDING, not ACTIVE
- How to draft a PR that stops in WAPPR and routes through your existing approval workflow
- Design options for duplicate-item similarity — and why IBM does not document it for the item master
- The governance guardrails that keep an agent away from approvals
Part 8: What Maximo Assistant Can Do Today
[Read Part 8 — What Maximo Assistant Can Do Today: The October 2026 Capability Map](/blog/mas-assist-current-capabilities-2026)
Read time: 15 minutes
Features move monthly on the Feature Channel. This post is the dated snapshot: what is documented in 9.1, what changed in 9.2 and the 2026 Feature Channel drops, what is announced but not yet documented, and what remains a build-it pattern.
You learn:
- The 9.0 → 9.1 → 9.2 timeline for the Assistant and the AI Service
- What "agentic" means in 9.2 and which tools the Assistant can call
- What the April 2026 "supports all objects" change unlocks
- Model and patch-level facts that affect planning (gpt-oss-120b, AI Service 9.2.3)
- How to label every AI claim by evidence tier before it reaches a steering deck
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.
The Storeroom & Buyer Lead
"Can it create items, raise PRs, and stop duplicate parts?"
Read: Part 7 → Part 8 → Part 6
Start with the supply-chain split between native querying and build-it MCP tools, check the current capability map so you know what is documented today, then read governance before you let any agent near procurement.
Key Themes Across the Series
It is agentic within a defined tool set — and a human still decides. Through MAS 9.1 the Assistant was a pure assistant. In MAS 9.2 IBM describes it as able to "act as a single agent" that analyzes a request and works across a defined set of AI tools, and the Maximo MCP server lets it perform writes — but only through the tools you expose, and with a human confirming. 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. MAS 9.0 brought watsonx problem-code suggestion (Work Order Intelligence). MAS 9.1 brought the AI assistant in Manage, Health, and dashboards, similar records, and AI-recommended field values, all served by the Maximo AI Service (which replaced the earlier AI broker on 1 August 2025). MAS 9.2 (GA 25 June 2026) made the Assistant agentic, added the Maximo MCP server for custom tools built from automation scripts, object structures, and workflows, put the assistant in Maximo Mobile (online only), and redesigned the AI configuration app. The April 2026 Feature Channel let the assistant find data in any Manage object, including custom objects, once enabled. Training and output data are currently English. Part 8 is the dated capability map; confirm exactly which version and Feature Channel level your environment runs before planning.
💡 Key insight: These themes are not separate lessons — they are one lesson viewed from several 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 unchecked — and that is why this one is safe to put in front of the people who keep your plant running.
References
- IBM Maximo Application Suite Documentation
- Maximo Manage — AI capabilities (IBM Documentation)
- IBM watsonx.ai Documentation
- AppPoints Licensing (IBM Documentation)
- Working smarter with agentic workflows in Maximo Assistant (IBM Think)
- Introducing Maximo Application Suite 9.2 (IBM announcement)
- What's new in Maximo Application Suite — Feature Channel (IBM Documentation)
- Maximo AI Service — AI features in Maximo Manage (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 | Updated October 2026
Manasa Ganga
Surendra Katta