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: 8 minutes | Total series read time: ~2 hours across 6 parts
<aside>
💡 Key insight: In MAS 9, your work order business process survived intact. What changed is every tool you use to run it — intake, approval, monitoring, reporting, and integration. This series is a map to those tools, not a rerun of the lifecycle you already know.
</aside>
🎯 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."
There is a reason these edges get skipped. Core work order training is written to teach the happy path: create the WO, plan it, schedule it, execute it, close it. That path is stable across the 7.6-to-MAS-9 jump because the WORKORDER table, the statuses, and the hierarchy did not change. The parts that did move are the surfaces a person touches on the way in and out of that path — and those are exactly the surfaces a feature-list guide has no room for. A planner who never leaves Work Order Tracking barely notices. A service-desk lead, an approver in a regulated plant, or an integration developer notices on the first day.
🔄 What Changed in Work Order Management — The 30-Second Map
Before you dive into any single part, hold this in your head: the engine is the same, the cockpit is new. Here is the honest split.
| What Stayed the Same | What Changed Dramatically |
|---|---|
| WORKORDER table, WO statuses, WO hierarchy | Every screen renders in the IBM Carbon Design System |
| Work Order Tracking, Tasks, and PM still exist as classic apps | Work Centers are removed — replaced by role-based apps (RBAs) and Maximo Mobile |
| PM generation, frequency logic, and forecasting | Start Center result sets give way to the Operational Dashboard and Work Queue Manager |
| Job Plan structure (tasks, labor, materials, tools) | Maximo Anywhere is dead — Maximo Mobile on React/MAF replaces it |
| Workflow Designer, escalations, communication templates | AI is now native: Work Order Intelligence (9.0) and the AI Assistant (9.1) |
| Automation Scripts as the primary customization mechanism | Reporting shifts toward dashboards, queues, exports, and Cognos — BIRT must be rationalized |
Read that table top to bottom and the strategy writes itself: your process knowledge transfers; your muscle memory does not. The planner who lived in the Work Execution Work Center now works out of the Operational Dashboard plus Work Queues plus Graphical Scheduling. The supervisor who used the Work Supervisor Work Center now uses the Approvals application. The technician who used Maximo Anywhere now uses Maximo Mobile. Every one of those workflows feels different even though the underlying data is identical.
<aside>
💡 Key insight: Treat this upgrade as a workflow redesign, not a technical uplift. The data migrates cleanly. The habits do not. Budget your training and change-management effort for the surfaces in the right-hand column — that is where adoption succeeds or fails.
</aside>
🧭 The Six Edges — And the Gotcha Behind Each
Each part of this series exists because there is a specific surprise waiting for a specific role. Here is the whole series as a problem-to-answer map, so you can jump straight to the edge that is about to bite you.
| # | The Edge | Who Feels It | The Gotcha |
|---|---|---|---|
| 1 | Service Requests | Service desk, intake leads | Single-screen SR-to-WO conversion is gone; the RBA and classic apps split the job |
| 2 | Approvals & e-signatures | Supervisors, regulated industries | Approval moved to a new app, and an AI now recommends failure codes at approval time |
| 3 | Operational Dashboard | Managers, analysts | Your Start Center result set isn't there; the dashboard is the new command center |
| 4 | Custom WO KPIs | KPI owners, planners | Out-of-the-box KPIs run out fast; you build the rest yourself in KPI Manager |
| 5 | Reporting (BIRT) | Report developers | The trap is treating your report catalog as a rebuild backlog instead of a rationalization exercise |
| 6 | Integration (REST/Kafka) | Integration developers | The old access patterns are deprecated; new work is REST and Kafka, not MIF |
If you only have ten minutes, read the row that matches your job and then the corresponding part. If you own the whole upgrade, read them in order — they build a complete picture of the operational machinery around the work order.
📚 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. It walks the intake lifecycle from a phone call or a QR-code scan through to a work order, and it is honest about where the modern apps stop and the classic apps take over.
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. It is the part regulated industries should read twice.
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, the Work Queues integration, and the governance model that determines who sees which dashboard.
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 and governance model — public, private, and role-standard dashboards
- Why many teams run Start Centers and Operational Dashboards side by side during transition
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. It includes a set of copy-ready WO KPI recipes.
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. It gives you a decision framework you can apply report-by-report.
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. It also names what actually broke — RMI, direct SQL, and basic auth.
You will learn:
- Querying and creating work orders through the JSON API (
/api/os/mxwodetail,lean=1) - What changed from the legacy access patterns 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
🧑🔧 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. Pay attention to the SR-to-WO gap in Part 1 and the Approvals RBA limits in Part 2 — together they define your intake-to-approval handoff.
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. By the end you can retire half your Start Center portlets and a chunk of your BIRT catalog with confidence.
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. Part 6 tells you what to build new work on; Parts 1 and 2 tell you what business rules sit behind the objects you're touching.
Upgrade Lead / Solution Architect
"I own the whole cutover."
Read: All six, in order.
The parts are sequenced to build a complete picture of the machinery around the work order. Combined with the MAS MANAGE lifecycle series, they give you a full go-live readiness view — intake, approval, monitoring, reporting, and integration.
🔑 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.
AI is now inside the workflow. Work Order Intelligence recommends failure codes at approval, and the AI Assistant answers natural-language WO questions. Both are optional, both depend on data quality, and both are covered honestly — including the AppPoints they cost.
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.
<aside>
💡 Key insight: Almost every "MAS 9 broke my workflow" complaint traces back to one of two root causes: a Work Center that was removed, or a reporting/integration pattern that was deprecated. Once you can classify a complaint into one of those buckets, the fix is nearly always in one of these six parts.
</aside>
References
- IBM Maximo Application Suite Documentation
- Maximo Manage — Work Orders Module (IBM Documentation)
- Work Order Operations Are Now Tasks — Overview and FAQ (IBM Support)
- Operational Dashboard and KPI Manager (IBM Documentation)
- Maximo Manage REST/JSON API (IBM Documentation)
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
Manasa Ganga
Swetansh Kumar