The AI Inside Manage: Work Order Intelligence, the Maximo Assistant, and AI Configuration

Part 10 of the MAS MANAGE series. This is the AI that lives inside the Manage application — not the standalone suites bolted on beside it.

<aside>
🎯 Who this is for: Maximo developers, administrators, and reliability teams who want to know exactly what generative AI ships inside Manage 9, what it does, what it needs to run — and what it is not.
</aside>

Estimated read time: 20 minutes

🧭 What "AI Inside Manage" Actually Means

There is a lot of AI in the Maximo Application Suite, and it is easy to blur it all together. So let us draw the boundary first, because it matters for licensing, architecture, and your expectations.

This post is about the generative AI that runs inside the Manage application itself — the features you reach from the same Work Order Tracking, Failure Codes, and Administration screens your team already uses. There are three pieces:

  1. Work Order Intelligence — added in Manage 9.0.
  2. The Maximo Assistant — added in Manage 9.1, expanded in 9.2.
  3. The AI Configuration application — added in Manage 9.0, the place you enable and customize all of it.

What this post is not about: the standalone AI add-on suites — Maximo Health, Maximo Monitor, Maximo Predict, and Maximo Visual Inspection. Those are separate products with their own applications, data pipelines, licensing, and deployment footprints. Each has its own series. They sit beside Manage; the features here live inside it.

<aside>
💡 Key insight: "AI in MAS" is not one thing. The AI inside Manage augments the work and asset application you already run. The AI suites are separate products. Conflating them leads to wrong licensing assumptions and wrong architecture decisions.
</aside>

┌──────────────────────────────────────────────────────────────┐
│   WHERE THE AI LIVES                                          │
├──────────────────────────────────────────────────────────────┤
│                                                              │
│   INSIDE MANAGE (this post)                                  │
│   ├─ Work Order Intelligence   (9.0)                         │
│   ├─ Maximo Assistant          (9.1 → 9.2)                   │
│   └─ AI Configuration app       (9.0, Administration)        │
│                                                              │
│   BESIDE MANAGE — standalone suites (other series)           │
│   ├─ Maximo Health      ├─ Maximo Predict                    │
│   ├─ Maximo Monitor     └─ Maximo Visual Inspection          │
│                                                              │
│   Shared plumbing:  watsonx.ai  +  Maximo AI Service         │
│                                                              │
└──────────────────────────────────────────────────────────────┘

🤖 Work Order Intelligence

Work Order Intelligence is the first piece of generative AI IBM built directly into Manage, arriving with Manage 9.0. It is watsonx-powered, and its goal is unglamorous in the best way: make the everyday flow of work orders faster and cleaner.

It does three concrete things:

  • Speeds work-order approval. Instead of a planner reading every line before routing, the AI surfaces what matters so approvals move faster.
  • Improves data quality. Work-order records are notoriously inconsistent — free text, missing codes, half-filled fields. The AI nudges records toward completeness and consistency.
  • Recommends the Problem code from the description. This is the standout. After a work order has a failure class, it reads the free-text work-order description and suggests the most likely problem code, with a confidence score.

That third point quietly fixes one of the oldest pains in Maximo. Failure coding is the data that powers reliability analysis (Part 4), yet technicians skip it or guess because picking the right value from a deep hierarchy is tedious. When the system reads "pump losing prime, suction line vibrating" and proposes the most likely problem code under the selected failure class, the code is more likely to be captured — and your downstream reliability data gets better without anyone trying harder.

<aside>
💡 Key insight: Work Order Intelligence is most valuable not for speed but for data quality. Better problem-code capture at the source feeds Reliability Strategies, failure analysis, and every report built on top of them.
</aside>

What it requires

Work Order Intelligence depends on a watsonx.ai API key. This is not a checkbox you flip — it is an entitlement and connectivity exercise. You need the watsonx.ai service available to your environment, a valid API key configured, and the AI features enabled through AI Configuration (below). That ties directly into the AppPoints and entitlement discussion from Part 1 and the administration work in Part 11.

💬 The Maximo Assistant

Manage 9.1 added the Maximo Assistant — a natively built generative-AI chat experience delivered as part of the Maximo AI Service. Where Work Order Intelligence works quietly behind the work-order flow, the Assistant is something you talk to.

The idea is plain-language access to your data. You stop building a query, an ad-hoc report, or a saved search, and instead ask:

  • "Which work orders are missing job plans?"
  • "Show me the sum of the total cost of work orders per site."

The Assistant interprets the question, runs against your asset and work data, and returns the answer. For anyone who has watched a maintenance supervisor wait two days for a report that a query could have answered in seconds, the value is obvious.

It also adds a "View Similar Work Orders" action — surface past work orders that resemble the one in front of you, so you can reuse what worked and avoid repeating what did not.

9.2 feature channel — the scope expansion

In Manage 9.1, the Assistant's reach was meaningful but bounded. IBM documents default coverage for assets, work orders, and service requests. In the 9.2 feature channel, the Assistant can retrieve data for any object, including custom objects, when the relevant object structures are configured for assistant access. IBM's documented defaults in that channel include work orders, assets, service requests, meters, preventive maintenance, job plans, work logs, assignments, and persons.

That "including custom objects" clause is the part that matters for real implementations. Almost every Maximo deployment carries custom objects and extensions. An assistant that only understood out-of-the-box objects would stall the moment it hit your customizations. Enabling object structures for assistant access means the Assistant can answer questions about your data model, not just the vanilla one.

Capability — Manage 9.1 — 9.2 feature channel

Natural-language queries — ✅ — ✅

View Similar Work Orders — ✅ — ✅

Default data coverage — Assets, work orders, service requests — Work orders, assets, service requests, meters, PMs, job plans, work logs, assignments, persons

Reaches additional object structures — Checkbox exists, but default-supported scope is limited — ✅ Any enabled object structure

Reaches custom objects — — — ✅ When enabled for assistant access

<aside>
⚠️ Watch out: The Assistant answers over the data and objects it can reach and that the user is authorized to see — it does not bypass security, and it is only as good as your data. If failure codes are missing or sites are mislabeled, the Assistant will faithfully report the gap. Treat its answers as a fast read of your data, not an audited source of truth, and confirm version-specific behavior and object coverage against IBM documentation for your release.
</aside>

⚙️ AI Configuration — Where You Turn It On

The AI Configuration application, added in Manage 9.0 within the Administration module, is the control surface for all of this. It is where you set up and customize the AI functionality in Maximo Manage — the governance and enablement layer that sits between your watsonx.ai entitlement and the features your users see.

Practically, this is where administrators connect the watsonx.ai credentials, enable the relevant AI capabilities, and tune how they behave. If Work Order Intelligence is the engine and the Maximo Assistant is the conversation, AI Configuration is the ignition and the dashboard. It connects directly to the administration work covered in Part 11.

   watsonx.ai entitlement + API key
              │
              ▼
   ┌─────────────────────────┐
   │   AI Configuration app   │   ← enable / customize (Admin module)
   └─────────────────────────┘
              │
      ┌───────┴────────┐
      ▼                ▼
 Work Order      Maximo Assistant
 Intelligence    (Maximo AI Service)

🛰️ Adjacent, Not Inside: Maximo Condition Insight

One newer capability is worth a brief mention so you can place it correctly. Maximo Condition Insight is delivered via the Maximo AI Service 9.2.0 (released 24 December 2025) and provides real-time asset intelligence and AI-driven insights and decision support.

It sits in the broader APM / AI Service portfolio adjacent to Manage rather than being a feature buried inside the Manage application itself. We flag it here because it rides on the same Maximo AI Service plumbing as the Assistant, so it will come up when you scope AI infrastructure — but the asset-health and APM story belongs to those suites, not to this Manage-centric post.

🧱 The Infrastructure Reality

It is tempting to read "AI inside Manage" as features you simply switch on. They are not. Every capability here depends on two shared components:

  • watsonx.ai — the generative-AI foundation. Work Order Intelligence explicitly requires a watsonx.ai API key.
  • The Maximo AI Service — the MAS component that the Maximo Assistant (and Condition Insight) are delivered through.

Enabling them is therefore an infrastructure and entitlement exercise, not a configuration afterthought. You need the entitlements (tie this back to AppPoints in Part 1), the components deployed and connected (Part 11), and the credentials wired through AI Configuration. Budget for that the way you would budget for any platform service — capacity, connectivity, and licensing — rather than assuming it comes free with Manage.

<aside>
⚠️ Watch out: Do not promise users the Assistant or code recommendations until watsonx.ai and the Maximo AI Service are actually provisioned, entitled, and connected. The features are real, but they are not zero-effort, and they are not part of the base work engine.
</aside>

🎯 The Commandments of AI Inside Manage

  1. Thou shalt distinguish the AI inside Manage from the standalone suites — Health, Monitor, Predict, and Visual Inspection are not this.
  2. Thou shalt treat enablement as infrastructure — watsonx.ai and the Maximo AI Service, not a checkbox.
  3. Thou shalt govern through AI Configuration, the Administration-module control surface.
  4. Thou shalt feed it good data — the Assistant and code recommendations are only as good as your records.
  5. Thou shalt remember it augments, not replaces — the asset and work engine still does the work.
  6. Thou shalt confirm object coverage and behavior against IBM docs for your specific release.

Key Takeaways

  • Work Order Intelligence (Manage 9.0) is watsonx-powered AI inside Manage that speeds approval, improves data quality, and recommends problem codes from the work-order description after a failure class is specified. It requires a watsonx.ai API key.
  • The Maximo Assistant (Manage 9.1) is a native generative-AI chat experience, part of the Maximo AI Service, for natural-language queries over asset and work data, plus a View Similar Work Orders action.
  • The 9.2 feature channel expanded the Assistant to retrieve data from any enabled object structure, including custom objects, with broader defaults than 9.1.
  • AI Configuration (Manage 9.0, Administration module) is where you enable and customize these AI features — the governance and enablement surface.
  • This AI is distinct from the standalone Health, Monitor, Predict, and Visual Inspection suites, which have their own series; Maximo Condition Insight (AI Service 9.2.0) sits adjacent in the APM portfolio.
  • Enabling any of it is an infrastructure and entitlement exercise on watsonx.ai and the Maximo AI Service — and it augments practitioners, it does not replace the work engine.

References

IBM Official

Community

Series Navigation

Previous: — Part 9 — Inventory and Procurement

Next: — Part 11 — Configuring and Administering Manage

Published by TheMaximoGuys | June 2026

About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS — from architecture and migration planning to the day-to-day work of configuring, extending, and running Maximo Manage. This series is the guide we wish we'd had.