Work Management Reimagined: Work Orders, Job Plans, and PMs in Maximo Manage 9

Part 3 of the MAS MANAGE series. Work orders, job plans, and preventive maintenance are the daily currency of every maintenance operation. Here is what Manage 9 kept, and what it added.

<aside>
🎯 Who this is for: Maintenance planners, work managers, reliability engineers, and Maximo administrators who live in Work Order Tracking, Job Plans, and PM every day — and want to know exactly what is new in Manage 9 without re-learning what already works.
</aside>

Estimated read time: 24 minutes

🔧 The Engine Did Not Change

Let me start where Part 1 ended, because it matters most here: the work management engine in Manage 9 is the same engine you already know. A work order is still a row in WORKORDER. A status is still WAPPR, APPR, INPRG, COMP, CLOSE. A job plan still copies its tasks into a work plan. A PM still generates work on a schedule.

If you have spent years planning maintenance in Maximo, none of your core mental model is wrong. That is the reassuring part. The exciting part is what Manage 9 added on top of that stable engine — a Qualifications field on job plans, milestone tasks, a status field on Routes, and two genuinely new applications for coordinating and triaging work.

So this post does two things: it gives you a clean reference for the work management model (because the whole series builds on it), and it calls out precisely what is new in Manage 9.

<aside>
💡 Key insight: Treat work management in Manage 9 as "the Maximo you know, plus a handful of targeted additions." You are extending muscle memory, not replacing it.
</aside>

🔁 The Work Order Lifecycle

A work order is an instance of the WORKORDER object — the single most important table in Manage. It carries the work from request to closure, and almost everything else in the product attaches to it: labor, materials, tools, costs, failures, inspections, and schedule.

Statuses and the flow

The lifecycle is governed by the WOSTATUS domain plus security-group signature options that control who can move work between states:

   WAPPR  ──▶  APPR  ──▶  INPRG  ──▶  COMP  ──▶  CLOSE
 (waiting    (approved)  (in        (work      (financially
  approval)              progress)  done)       closed)

Industries layer additional statuses on top — a QA review state in pharma, a regulatory hold in nuclear — and approval paths are enforced through signature options to maintain separation of duties. Work types configured on the work order drive defaults like "requires approval," "is subject to planning," or "impacts asset downtime."

Tasks and child work orders

Two structures let a work order represent more than a single job:

  • Tasks are child records within the same WORKORDER object, distinguished by the ISTASK flag and a parent relationship. Each task can carry its own planned labor, materials, and tools — so a five-step overhaul is one work order with five tasks, each independently planned and reported.
  • Child work orders model follow-up work — for example, a corrective work order raised from an inspection finding — that needs its own lifecycle but traces back to a parent.

Execution is captured in the transaction tables you know — LABTRANS for labor, MATUSETRANS for materials, TOOLTRANS for tools — and rolls up into the work order's cost fields. Failure reporting (failure class → problem → cause → remedy) feeds reliability analysis, which we pick up in Part 4.

📋 Job Plans Got Smarter

A job plan (JOBPLAN) is the reusable template for a type of work: planned tasks, labor (craft, skill level, estimated hours), materials, services, tools, and safety. When a work order is created from a job plan, that plan is copied into the work order's work plan. This is unchanged — and still the backbone of consistent, repeatable maintenance.

What is new in Manage 9 is worth your attention:

Addition — What it does — Why it matters

Qualifications field — Lets a job plan (and Work Order Tracking) require specific qualifications or certifications for the work — Ties planning directly to who is allowed to do the work — the foundation for qualification-aware scheduling and dispatch (Part 7)

Milestone tasks (`Is Milestone`) — Flags a task as a milestone within the plan — Gives planners and dashboards meaningful checkpoints in long or multi-task work, surfaced in the scheduling tools

The Qualifications addition is more strategic than it looks. By attaching required qualifications at the planning layer, Manage 9 lets the downstream scheduling and Field Service Management capabilities (Part 7) make qualification-aware assignment decisions — the planner specifies the competency, and the scheduler respects it.

Advanced job-plan capabilities remain available too: conditional task inclusion, multiple revisions, and job plan selection rules that pick the right plan at runtime based on attributes like manufacturer, model, or asset criticality — so a high-criticality pump can receive a more rigorous plan under the same PM.

<aside>
💡 Key insight: The Qualifications field is the quiet hero of Manage 9 work management. It is the link that lets planning, scheduling, and dispatch agree on who can do what — instead of discovering a qualification mismatch on site.
</aside>

📅 Preventive Maintenance, Master PMs, and Conditional Work

Preventive maintenance is where job plans become a program rather than a one-off. A PM record associates a job plan with a target asset or location and a frequency.

Frequency models

  • Time-based — every N days, weeks, or months.
  • Meter-based — every N operating hours, cycles, or other meter units.
  • Mixed — both are defined, and whichever threshold is reached first triggers generation. This is how you model "every 500 hours or 6 months, whichever comes first."

Work orders are generated either manually or, far more commonly, by a cron task that evaluates due PMs and creates the work. In Manage 9 that cron task runs inside a dedicated pod on OpenShift (see Part 1), so you set its resource limits and monitor the pod — but the PM configuration itself is unchanged.

Master PMs and conditional PMs

  • Master PMs are templates. Child PMs inherit from a master and can override attributes locally, so you maintain a fleet of similar assets from one definition while still allowing per-asset variation.
  • Conditional PMs are triggered by attributes, automation scripts, or inspection results — for example, a failed critical inspection or a vibration meter crossing a threshold raises corrective work automatically. This is the bridge between scheduled maintenance and condition-based maintenance, and it is where work management meets the reliability and inspection content in Parts 4 and 5.

🗺️ Routes Got a Status Field

A route groups inspection or maintenance points into a sequence — think of an operator's rounds, where each stop is tied to an asset or location and an optional job plan, and the route generates child tasks or work orders per stop. Routes are the natural home for meter readings and recurring inspection rounds.

New in Manage 9: the Routes application added a status field with draft / active / inactive values. It is a small change with real operational value — you can now build and revise a route in draft, promote it to active when it is ready for use, and retire it to inactive without deleting it. That lifecycle control was a genuine gap in earlier releases.

🆕 Two New Applications for Coordinating and Triaging Work

Beyond the field-level additions, Manage 9 introduced two applications that change how planners and supervisors handle volume.

Work Order Planning

The Work Order Planning application manages parent-child work order relationships and coordinates labor, materials, and tools across related work. Where a complex job spans multiple linked work orders, this application gives planners a coordinated view and the ability to manage the relationships and resources together rather than hopping between individual records.

Work Queue Manager

The Work Queue Manager manages work queues across multiple record types — work orders, purchase requests, purchase orders, incidents, and service requests — in one place. Instead of triaging incoming work from several separate application list views, a planner or supervisor works a single queue surface, routing and assigning across record types from one application.

┌───────────────────────────────────────────────────────────┐
│   WORK QUEUE MANAGER — ONE TRIAGE SURFACE                  │
├───────────────────────────────────────────────────────────┤
│                                                            │
│   Incoming:                                                │
│     • Work Orders        ┐                                 │
│     • Service Requests   │                                 │
│     • Incidents          ├──▶  one queue  ──▶  route /     │
│     • Purchase Requests  │                     assign /    │
│     • Purchase Orders    ┘                     prioritize  │
│                                                            │
└───────────────────────────────────────────────────────────┘

<aside>
⚠️ Watch out: These applications coordinate and triage work — they do not replace Work Order Tracking or the PM application. Think of them as a planner's command layer on top of the records you already maintain, not a substitute for them.
</aside>

🔗 How It All Connects

Work management does not live in isolation. The same WORKORDER that this post describes is the hub the rest of the series plugs into:

  • Materials are drawn from inventory, creating reservations and reorder demand (Part 9).
  • Meter readings — from inspections or technicians — trigger meter-based PMs and conditional work (Parts 5 and 8).
  • Failure reporting feeds reliability analysis and strategy (Part 4).
  • Scheduling and dispatch consume work orders, honoring the Qualifications you planned (Part 7).
  • Maximo Mobile lets technicians execute and report all of this in the field, offline (Part 6).

That is the point of keeping the engine stable: every other capability in Manage 9 is, in some sense, a richer way to feed or act on a work order.

🎯 The Commandments of Manage 9 Work Management

  1. Thou shalt trust the engine — the WORKORDER object and lifecycle are unchanged.
  2. Thou shalt use the Qualifications field — it is the link between planning and dispatch.
  3. Thou shalt flag milestones on long job plans so dashboards show real checkpoints.
  4. Thou shalt manage route lifecycle with the new draft/active/inactive status.
  5. Thou shalt let conditional PMs bridge scheduled and condition-based maintenance.
  6. Thou shalt triage from one surface with the Work Queue Manager, not five list views.

Key Takeaways

  • The work order lifecycle, statuses, tasks, and child work orders are unchanged — same WORKORDER object, same mental model.
  • Job Plans gained a Qualifications field and milestone tasks (Is Milestone) in Manage 9, linking planning to competency and creating dashboard checkpoints.
  • PMs support time-based, meter-based, and mixed frequencies, generated by cron tasks running in OpenShift pods; master PMs and conditional PMs handle fleets and condition-based triggers.
  • The Routes application added a draft/active/inactive status field for proper route lifecycle control.
  • Work Order Planning and Work Queue Manager are new applications — one coordinates parent-child work and resources, the other triages queues across work orders, PRs, POs, incidents, and service requests.

References

IBM Official

Community

Series Navigation

Previous: — Part 2 — From Work Centers to Role-Based Applications

Next: — Part 4 — Reliability Strategies

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.