Maximo Manage 9.x Work Order Lifecycle: Configuration, AI, and the New Dispatching Model

The work order is the heart of Maximo Manage. Every maintenance activity, every inspection, every corrective action flows through the work order lifecycle, and the quality of your configuration directly determines the quality of your maintenance data. With Manage 9.x, IBM has introduced significant changes to how work orders are created, dispatched, executed, and reported. The legacy Work Centers are gone, replaced by role-based applications built on the Maximo Application Framework. AI is embedded in the lifecycle through Work Order Intelligence and the Maximo Assistant. The dispatching model has been overhauled with real-time assignment tracking. Job plans now carry qualification requirements and milestone tasks.

This is a practitioner-level deep dive into the work order lifecycle in Maximo Manage 9.x. We cover the role-based application model and what it means for work order management, the job plan enhancements that flow through to work order execution, the AI-driven Work Order Intelligence features, the new dispatching and assignment lifecycle, the inspection framework integration, and the admin and configuration layer that ties it all together. For each area, we explain what changed, how it works, and what implementation teams need to know to configure it correctly.

The Role-Based Application Model and the End of Work Centers

The most visible change in Maximo Manage 9.x is the removal of the legacy Work Centers. In Maximo 7.6.x and early MAS 8.x releases, Work Centers were the primary interface for technicians, planners, and dispatchers. They were web-based dashboards built on a combination of legacy Maximo UI technology and newer JavaScript frameworks. They worked, but they were inconsistent with each other, difficult to customize, and built on a technology stack that IBM was moving away from.

In Manage 9.0 and 9.1, the Work Center experiences have been replaced by role-based applications built on the Maximo Application Framework (MAF). MAF is a low-code application platform that allows administrators to build and configure role-based applications using a visual designer. The key role-based applications in Manage 9.1 include Work Order Planning, Work Queue Manager, Inspection Forms, Issues and Transfers, and the Operational Dashboard. In 9.2, these applications have been refined with additional capabilities based on customer feedback from the first year of production use.

Each role-based application is tailored to a specific user role and task. Work Order Planning gives planners a focused view of their work orders with filtering, sorting, and grouping capabilities that go beyond what was available in the Work Center. Work Queue Manager provides technicians with a queue-based view of their assigned work, with inline editing and status changes. The Inspection Forms application provides a form-based interface for creating and executing inspections, replacing the old Inspection Forms Work Center.

The advantage of MAF is not just visual consistency. It is configurability. Administrators can modify the role-based applications using the Application Designer, changing fields, layouts, and behaviors without writing code. This is a significant improvement over the Work Centers, which required JavaScript modifications and were difficult to maintain across upgrades. MAF applications are also built on REST APIs, which means the same data and logic that powers the web interface is available for integration with other systems and custom applications.

The transition from Work Centers to MAF applications is not transparent for organizations with custom Work Center modifications. Any custom JavaScript, custom dashlets, or custom Work Center pages built in 8.x will need to be rebuilt on MAF. IBM provides migration guidance, but the work is manual. Conduct an inventory of your Work Center customizations early in your upgrade planning and budget time for rebuilding them. In practice, most organizations find that the MAF applications cover the majority of their Work Center use cases out of the box, and the customizations they need to rebuild are fewer than expected.

The Operational Dashboard deserves specific attention. It provides a real-time view of work order status across a team, crew, or site, with drill-down capabilities into individual work orders. Dispatchers and supervisors use it to monitor progress, identify bottlenecks, and reassign work as needed. The dashboard is configurable, so you can tailor the displayed metrics and filters to your operational context. A common configuration pattern is to set up separate dashboard views for each shift, filtered by crew and work type, with auto-refresh enabled at 60-second intervals.

Job Plan Enhancements: Qualifications, Milestones, and Flow-Through

Job plans in Manage 9.1 and 9.2 add several capabilities that directly impact work order execution. The most significant is the Qualifications field, which allows you to specify required qualifications directly on job plan tasks. Previously, qualifications were managed at the labor record level and were not directly linked to job plan tasks. Now, when a work order is generated from a job plan, the qualification requirements flow through to the work order, and the scheduling system can match them against available technician qualifications.

This creates a closed-loop process from job plan definition to work assignment. A reliability engineer defines the required qualifications when creating the job plan. A planner generates a work order from that job plan. The scheduler sees the qualification requirements and assigns technicians who hold those qualifications. If no qualified technician is available, the system flags the gap before the work is dispatched. This prevents the common scenario where a technician arrives on site only to discover they lack the certification required to perform the work.

Manage 9.1 also introduces milestone tasks within job plans. Milestone tasks allow planners to mark specific tasks as critical milestones in the work order execution sequence. This is useful for tracking progress on complex multi-task work orders and for reporting on milestone completion rates. Milestone tasks are visually distinguished in the work order tracking interface and can be included in KPIs and dashboards. A common application is in shutdown and turnaround work, where certain tasks must be completed before subsequent tasks can begin. By marking these as milestones, supervisors can track the critical path and identify delays before they cascade.

The work order status flow has been enhanced with additional status values and more granular status control. The dispatching status for work order assignments is a new addition that provides real-time and historical dispatching information about assignments. Dispatchers can see when an assignment was created, when it was dispatched, when the technician accepted it, and when work began. This visibility into the dispatching lifecycle helps dispatchers identify bottlenecks and improve assignment accuracy.

For work order reporting, Manage 9.1 adds the ability to record electronic signatures on inspection form status changes. This is configured in the Database Configuration application, where you can enable e-signature requirements on specific status transitions. When a technician or inspector changes the status of an inspection form, the system prompts for credentials and records the signature in the audit log. This is particularly important for regulated industries where electronic signature capture is a compliance requirement under FDA 21 CFR Part 11 or similar regulations.

<!-- Example: Job plan with qualifications and milestone in Maximo Manage 9.x -->
<JOBPLAN>
  <JPNUM>PUMP-PM-001</JPNUM>
  <DESCRIPTION>Monthly Pump Preventive Maintenance</DESCRIPTION>
  <STATUS>ACTIVE</STATUS>
  <TASKS>
    <TASK>
      <JPTASK>10</JPTASK>
      <DESCRIPTION>Inspect pump seals and bearings</DESCRIPTION>
      <QUALIFICATIONS>
        <QUALIFICATION>
          <QUALCODE>MECH-L2</QUALCODE>
          <DESCRIPTION>Mechanical Technician Level 2</DESCRIPTION>
        </QUALIFICATION>
      </QUALIFICATIONS>
      <MILESTONE>true</MILESTONE>
    </TASK>
    <TASK>
      <JPTASK>20</JPTASK>
      <DESCRIPTION>Replace seals if wear exceeds tolerance</DESCRIPTION>
      <QUALIFICATIONS>
        <QUALIFICATION>
          <QUALCODE>MECH-L3</QUALCODE>
          <DESCRIPTION>Senior Mechanical Technician</DESCRIPTION>
        </QUALIFICATION>
      </QUALIFICATIONS>
    </TASK>
  </TASKS>
</JOBPLAN>

Work Order Intelligence: AI-Driven Classification and Duplicate Detection

Work Order Intelligence is the AI feature family that most directly impacts the daily work of planners and technicians. It consists of three capabilities: recommended failure codes, duplicate detection, and Condition Insight integration. Each addresses a different pain point in the work order lifecycle, and together they reduce the administrative overhead that has historically made Maximo work order management feel burdensome.

The most visible feature is the recommended failure code. When a technician describes a problem in free text on a work order, the AI analyzes the text and suggests a failure code based on patterns learned from historical work order data. The configuration is straightforward. The AI broker is enabled in the ManageWorkspace custom resource, and the model is referenced by name. Inference happens at the moment the technician saves the long description, not at the moment the work order is created. The recommendations appear in a panel on the work order, and the technician can accept, reject, or override.

The second feature is duplicate detection. When a new work order is created, the system compares it against recent work orders on the same asset, the same location, or the same problem code. If a probable duplicate is found, the technician is shown the existing work order and asked to confirm. This is a meaningful reduction in duplicate work, especially in environments where field crews raise work orders independently and visibility across crews is limited. The duplicate detection algorithm considers asset identity, location identity, problem code, time window (typically 72 hours), and work order status.

The third feature, available in 9.2, is Condition Insight integration within work orders. When a work order is generated from a condition monitoring alert, the Condition Insight summary is embedded in the work order's long description. This gives the technician context about why the work order was created, what the asset condition trends look like, and what corrective actions the AI recommends. Instead of arriving at the asset with only a work order number and a brief description, the technician has a full AI-generated analysis of the situation.

From a configuration perspective, the ManageWorkspace custom resource controls how Work Order Intelligence operates. The confidence threshold determines how aggressive the AI is in making recommendations. A threshold of 0.65, which is the default, means the AI will only show recommendations where it is at least 65% confident. The maxRecommendations parameter controls how many options are presented. The feedback loop, when enabled, allows the system to learn from technician acceptances and rejections, improving recommendation quality over time.

# ManageWorkspace configuration for Work Order Intelligence
apiVersion: mas.ibm.com/v1
kind: ManageWorkspace
metadata:
  name: manage-workspace
  namespace: mas-inst1-manage
spec:
  settings:
    workOrderIntelligence:
      enabled: true
      model: "maximo-failure-code-v2"
      confidenceThreshold: 0.65
      maxRecommendations: 3
      feedbackLoop: true
      duplicateDetection:
        enabled: true
        timeWindowHours: 72
        matchCriteria:
          - "asset"
          - "location"
          - "problemCode"
    conditionInsight:
      enabled: true

The New Dispatching and Assignment Lifecycle

The dispatching model in Manage 9.x provides visibility into the assignment lifecycle that was previously impossible. In Maximo 7.6.x and 8.x, assignments were created and dispatched, but the system did not track the granular status changes between creation and completion. A dispatcher could see that an assignment existed and whether it was completed, but the intermediate steps were opaque.

In 9.x, the dispatching status captures the full lifecycle. When a dispatcher creates an assignment, the system records the creation timestamp. When the assignment is dispatched to a technician, the dispatch timestamp is recorded. When the technician accepts the assignment, an acceptance timestamp is added. When work begins, a start timestamp is captured. Each of these status changes is visible in real-time on the Operational Dashboard and in the assignment history.

This visibility has practical applications. A dispatcher can identify technicians who consistently take longer to accept assignments, which may indicate a training gap or a process issue. A supervisor can see how long assignments sit in the dispatched state before being accepted, which may indicate that technicians are not checking their devices frequently enough. A planner can analyze the time between assignment creation and work completion to identify scheduling inefficiencies.

The assignment lifecycle also integrates with the Maximo Mobile application. When a dispatcher assigns work to a technician, the technician receives a push notification on their mobile device. The technician can accept or reject the assignment from the notification, without opening the full application. If the technician rejects the assignment, the dispatcher is notified immediately and can reassign the work. This real-time feedback loop reduces the time between assignment and confirmation from hours to minutes.

In 9.2, the conversational scheduling feature adds an AI layer to the dispatching process. A scheduler can ask the system to explore what-if scenarios using natural language. The system applies the organization's constraints, including technician availability, skill qualifications, travel time, and work order priority, to return optimized assignment options. This does not replace the scheduler's judgment, but it accelerates the evaluation of alternatives that would otherwise require manual calculation.

Inspection Framework Integration and Electronic Signatures

The inspection framework in Manage 9.x is tightly integrated with the work order lifecycle. Inspections can be generated from work orders, from PM records, or from condition monitoring alerts. The Inspection Forms application, built on MAF, provides a form-based interface for creating and executing inspections. Forms support conditional questions, where subsequent questions appear only when a specific answer is selected, and formulas that calculate values based on previous responses.

The integration between inspections and work orders is bidirectional. An inspection can generate a follow-up work order if it identifies a deficiency. A work order can include inspection tasks as part of its job plan. The results of the inspection are recorded on the work order and contribute to the asset's history and failure analysis. This closed-loop process ensures that inspection findings are not just recorded but acted upon.

Electronic signatures on inspection form status changes are a significant addition for regulated industries. The configuration is done in the Database Configuration application, where administrators can enable e-signature requirements on specific status transitions for the INSPECTIONFORM object. When enabled, the system prompts the user for credentials when they attempt to change the status of an inspection form. The signature is recorded in the audit log with the user's identity, the timestamp, and the previous and new status values.

The practical application is in industries where inspection results must be authenticated. A quality inspector completes an inspection form and changes the status to COMPLETED. The system prompts for their credentials, verifies their identity, and records the signature. A supervisor then reviews the inspection and changes the status to APPROVED. The supervisor's signature is also recorded. This creates a tamper-evident audit trail that satisfies regulatory requirements without requiring a separate electronic signature system.

For organizations new to e-signature in Maximo, the configuration steps are as follows. First, identify which inspection form status transitions require signatures. Second, enable e-signature on those transitions in the Database Configuration application. Third, train users on the signature process, including what to expect when prompted. Fourth, test the configuration in a non-production environment to verify that the signature prompts appear correctly and that the audit log captures the required information. Finally, establish a periodic review process to verify that signature records are being captured and stored correctly.

Admin and Configuration Layer: ManageWorkspace and AI Configuration

The admin and configuration layer in Manage 9.x is more complex than in 7.6.x, primarily because the platform now runs on OpenShift and configuration is split between the OpenShift-level custom resources and the application-level configuration. Understanding this split is essential for administrators who need to configure and maintain the platform.

The ManageWorkspace custom resource is the primary OpenShift-level configuration object for Maximo Manage. It controls database configuration, attachment storage, build options, AI service configuration, and a long list of operational parameters. Changes to ManageWorkspace are applied through the OpenShift CLI or the MAS admin interface, and they trigger a reconciliation process that updates the Manage pods.

The AI Configuration application is new in 9.1 and provides administrators with a centralized interface for configuring the AI capabilities. This is where administrators enable and configure the Maximo Assistant, similar work orders, similar records, and AI-recommended field values. The application provides a single pane of glass for AI configuration, which is important because AI features are embedded throughout the Manage applications and configuring them individually would be difficult.

The Database Configuration application remains the primary tool for object-level configuration. Administrators can create and modify objects, attributes, relationships, and indexes. The application also supports electronic signature configuration, audit logging, and formula definitions. In 9.x, the Database Configuration application has been improved with a cleaner interface and better performance when working with large object structures.

A key configuration consideration is attachment storage. In Manage 9.x, attachments can be stored as file-based or object-based storage, configured through the ManageWorkspace custom resource. File-based storage uses the persistent volume attached to the Manage pod, while object-based storage uses an S3-compatible object storage service. Object-based storage is recommended for production environments, as it provides better scalability and durability than file-based storage. The configuration is straightforward but must be planned before deployment, as migrating from file-based to object-based storage after go-live requires data migration.

# ManageWorkspace attachment storage configuration
apiVersion: mas.ibm.com/v1
kind: ManageWorkspace
metadata:
  name: manage-workspace
  namespace: mas-inst1-manage
spec:
  settings:
    attachments:
      storageType: "object"
      objectStorage:
        endpoint: "https://s3.us-east.cloud-object-storage.appdomain.cloud"
        bucket: "mas-manage-attachments"
        prefix: "prod"
    aiService:
      enabled: true
      provider: "watsonx"
      model: "maximo-assistant-v1"
    features:
      assistant:
        manage: true
        health: true
        operationalDashboard: true
      failureCodeRecommendation:
        enabled: true
      conditionInsight:
        enabled: true

Practical Implications

The work order lifecycle changes in Manage 9.x are not just feature additions. They represent a shift in how maintenance work is planned, dispatched, executed, and analyzed. Organizations that configure the new capabilities without changing their processes will get incremental improvements. Organizations that redesign their processes to take advantage of the AI features, the dispatching visibility, and the role-based applications will get transformational improvements. Plan to revisit your work order processes as part of the upgrade, not just your system configuration. The qualification-to-assignment flow, the AI-driven failure classification, and the real-time dispatching visibility each represent an opportunity to eliminate a long-standing inefficiency in your maintenance operation.

Bottom Line

Maximo Manage 9.x is the most significant update to the core EAM application since the move to the Application Suite architecture. The role-based application model, the AI-driven Work Order Intelligence features, the new dispatching lifecycle, and the enhanced job plan capabilities collectively change how planners, dispatchers, and technicians interact with the system. If you are upgrading from 8.x or 7.6, budget time for process redesign alongside the technical upgrade. If you are already on 9.1, the 9.2 enhancements are incremental but valuable, particularly Condition Insight integration and conversational scheduling. Configure the AI features early, train your users on the role-based applications, and use the new visibility into the dispatching lifecycle to identify and fix the bottlenecks in your maintenance workflow.