MAS 9 Work Order Operations: The Missing Pieces You Won't Find in the Core Work Order Guides

Who this is for: Maximo planners, schedulers, service-desk leads, approvers, reporting teams, and integration developers who already know the work order lifecycle — and keep hitting the edges of it in MAS 9 that nobody wrote down in one place.

Estimated read time for this index: 7 minutes | Total series read time: ~2 hours across 6 parts

Why This Series Exists

You already know how a work order works. You know the lifecycle — WAPPR, APPR, INPRG, COMP, CLOSE. You know tasks and child work orders, job plans and PMs, and you know how a technician executes work in Maximo Mobile. If you don't, that ground is already covered — the MAS MANAGE series walks the full work management lifecycle (Part 3), Maximo Mobile (Part 6), and graphical scheduling and dispatch (Part 7). Go read those. We are not going to repeat them here.

This series is about the other half — the parts of work order operations that the core guides breeze past, and that quietly change under you when you move to MAS 9:

"Where did the Work Supervisor Work Center go?"

"How do I approve a work order now — and why is there an AI recommending a failure code?"

"Why can't I find my Start Center result set, and what is this Operational Dashboard?"

"Do I really have to rebuild all my BIRT reports?"

"The integration team says the old work order endpoint changed — did it?"

None of these are the work order lifecycle. They are the operational machinery around the work order — intake, approval, monitoring, reporting, and integration. Each one has a real answer in MAS 9, and each one has a gotcha that surprises teams on upgrade day. This series is the map to those six edges — nothing more, nothing less. Every claim is grounded in the documented MAS 9.0 and 9.1 behavior, and every part tells you plainly when the honest answer is "that flow no longer exists — here's the workaround."

Where This Series Fits

This is deliberately a gap-filler, not a complete work order course. Here is the division of labor so you never read the same thing twice:

If you want… — Read…

The WO lifecycle, tasks, job plans, PMs, Work Queue Manager — MAS MANAGE — Part 3 (Work Management)

Technician execution, offline, mobile work — MAS MANAGE — Part 6 (Maximo Mobile)

Graphical scheduling, assignment, dispatch, FSM — MAS MANAGE — Part 7 (Graphical Scheduling & FSM)

The six edges below — This series

The Series at a Glance

Part — Title — Focus Area — Read Time

1 — Service Requests in Manage 9 — The SR application in Carbon, the Service Request RBA, and the SR mobile app — 18 min

2 — Work Order Approvals — Approval workflow, the Approvals RBA, Work Order Intelligence, and electronic signatures — 20 min

3 — The Operational Dashboard — Out-of-the-box WO KPIs, the Maintenance Manager view, and the dashboard access model — 20 min

4 — Building Custom Work Order KPIs — KPI Manager, card types, thresholds, and JSON-from-API KPIs — 20 min

5 — Work Order Reporting in MAS 9 — Rationalizing BIRT, KPI Manager as an alternative, and when Cognos is the answer — 18 min

6 — Work Order Integration Changes — The WO REST/JSON API, Kafka work order events, and where MIF still fits — 22 min

Part-by-Part Guide

Part 1: Service Requests in Manage 9

[Read Part 1 — Service Requests in Manage 9](/blog/wo-missing-pieces-service-requests)

Read time: 18 minutes

The Service Request Work Center is gone. This post covers what replaced it — the classic SR application in Carbon, the modern Service Request RBA on MAF, and the dedicated SR mobile app — plus the one flow that did not survive the transition and what to do about it.

You will learn:

  • What changed in the Service Request application from 7.6 to MAS 9 (Carbon UI, RBA, mobile)
  • What the Service Request RBA does and does not do
  • The MAS 9.0 and 9.1 mobile SR capabilities (rich text, duplication, map creation, self-registration)
  • The honest gap: why single-screen SR-to-WO conversion no longer exists, and the workaround
  • The MAS 9.1 AI touch: similar-SR detection at creation time

Part 2: Work Order Approvals

[Read Part 2 — Work Order Approvals](/blog/wo-missing-pieces-approvals-esignatures)

Read time: 20 minutes

Approving a work order looks different now. This post covers the Workflow Designer (unchanged), the new Approvals RBA that replaces the Work Supervisor approval flow, the watsonx-powered Work Order Intelligence that recommends failure codes at approval, and electronic signature enforcement on status changes.

You will learn:

  • Why the Workflow Designer is unchanged and your 7.6 workflows carry forward
  • What the Approvals RBA gives you — and the SR-to-WO conversion it does not
  • How Work Order Intelligence uses watsonx to recommend problem codes with a confidence score
  • The AppPoints and AI Service requirements behind that AI recommendation
  • How to enforce electronic signatures on specific status transitions for regulated work

Part 3: The Operational Dashboard

[Read Part 3 — The Operational Dashboard](/blog/wo-missing-pieces-operational-dashboard)

Read time: 20 minutes

Start Centers still work, but the strategic replacement is the Operational Dashboard. This post covers the out-of-the-box work order KPIs, the pre-built Maintenance Manager dashboard, and the current governance limitation that keeps many teams on Start Centers.

You will learn:

  • The out-of-the-box WO KPIs (emergency work, PM compliance, overdue, backlog, MTBF/MTTR)
  • What ships in the Maintenance Manager dashboard and how to customize it
  • Card types that matter for work orders (KPI Value, KPI Trend, Work Queues, Threshold Tile)
  • The dashboard access model and the honest 9.1 limitation on per-user assignment
  • Why many teams run Start Centers and Operational Dashboards side by side

Part 4: Building Custom Work Order KPIs

[Read Part 4 — Building Custom Work Order KPIs](/blog/wo-missing-pieces-custom-wo-kpis)

Read time: 20 minutes

Out-of-the-box KPIs run out fast. This post is the hands-on guide to KPI Manager: defining a work-order KPI query, setting thresholds and trend calculations, choosing the right card, and the MAS 9.1 ability to feed a KPI from an external JSON API.

You will learn:

  • How to define a custom WO KPI against any Maximo object in KPI Manager
  • Setting refresh intervals, color thresholds, and trend calculations
  • Matching KPIs to the right card type for the story you're telling
  • The MAS 9.1 capability to return KPI values from an external JSON API
  • Common WO KPI recipes (schedule compliance, wrench time, aging backlog)

Part 5: Work Order Reporting in MAS 9

[Read Part 5 — Work Order Reporting in MAS 9](/blog/wo-missing-pieces-reporting-birt-to-kpi)

Read time: 18 minutes

The wrong move is to rebuild every BIRT report. This post covers how to rationalize your BIRT catalog: which reports become KPI Manager cards, which stay as reports, and where Cognos Analytics is the right destination.

You will learn:

  • Why BIRT is not deprecated but should not be blindly rebuilt
  • A decision framework: KPI card vs. report vs. Cognos
  • Which classic WO report types map cleanly to KPI Manager cards
  • Where Cognos Analytics earns its place for complex, multi-page WO reporting
  • Export paths from the dashboard and role-based applications

Part 6: Work Order Integration Changes

[Read Part 6 — Work Order Integration Changes](/blog/wo-missing-pieces-integration-rest-kafka)

Read time: 22 minutes (Series Finale)

The integration surface for work orders moved. This finale covers the WO REST/JSON API (with lean=1), Kafka events for near-real-time work order changes, and the honest truth that MIF still works but is no longer where the investment goes.

You will learn:

  • Querying and creating work orders through the JSON API (/api/os/mxwodetail, lean=1)
  • What changed from the legacy /maxrest endpoints and why
  • Publishing work order changes as Kafka events for event-driven integrations
  • Where MIF Publish Channels and Enterprise Services still fit
  • A migration posture: new integrations on REST/Kafka, existing MIF left alone

Where This Series Fits (Recommended Reading Paths)

Service Desk / Intake Lead

"I own how requests come in and become work."
Read: Part 1 → Part 2
Start with the Service Request RBA and mobile intake, then follow the request into the approval flow.

Maintenance Manager / Analyst

"I live in the numbers."
Read: Part 3 → Part 4 → Part 5
Start with the Operational Dashboard, learn to build your own WO KPIs, then rationalize your reporting.

Integration Developer

"I move work order data in and out."
Read: Part 6 → Part 1 → Part 2
Start with the REST/Kafka surface, then understand the SR and approval objects you'll be integrating with.

Key Themes Across the Series

Work Centers are gone, and their jobs were split. The single Work Supervisor Work Center became the Service Request RBA (intake) and the Approvals application (approval). Knowing which half owns what saves you a lot of "where did that go?"

The dashboard is the new result set. Start Centers still work, but out-of-the-box WO KPIs and the Operational Dashboard are where IBM is investing. Learn KPI Manager and you stop missing your old Start Center portlets.

Don't rebuild — rationalize. BIRT still runs. The upgrade mistake is treating a report catalog as a rebuild backlog instead of a rationalization exercise.

Integration moved, it didn't vanish. REST/JSON and Kafka are the new front door for work order data; MIF is the door that still opens but isn't being repainted.

The honest gaps matter most. The single biggest surprise — losing one-screen SR-to-WO conversion — isn't a bug, it's a design change. This series names the gaps instead of pretending they aren't there.

References

Series Navigation

Previous: — You are at the beginning of the series

Next: — Part 1 — Service Requests in Manage 9

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