Maximo Manage 9.1 Deep Dive: Role-Based Apps, AI, and the New Work Order Lifecycle

Maximo Manage 9.1 Deep Dive: Role-Based Apps, AI, and the New Work Order Lifecycle

IBM Maximo Manage 9.1, released in June 2025 as part of MAS 9.1, represents the most significant update to the core EAM application since the move to the Application Suite architecture. The release removes the legacy Work Centers that served as the primary user interface since Maximo 7.6.x, replaces them with role-based applications built on the Maximo Application Framework (MAF), adds embedded generative AI through Work Order Intelligence and the Maximo Assistant, and overhauls the reliability, inspection, and scheduling workflows.

This is a practitioner-level deep dive into the key areas of Manage 9.1: the new work order lifecycle and job plan enhancements, the role-based application model, reliability strategies with the built-in FMEA library, the rebuilt inspection framework, the scheduling stack including the AI-driven Field Service Management solution, and the admin and configuration layer. For each area, we cover what changed, how it works, and what implementation teams need to know.

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

The most visible change in Maximo Manage 9.1 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.

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.

The New Work Order Lifecycle and Job Plan Enhancements

The work order is the heart of Maximo Manage, and version 9.1 brings several enhancements to the work order lifecycle and job plan configuration that practitioners need to understand.

Job plans in Manage 9.1 add the Qualifications field, which allows you to specify required qualifications (skills, certifications, or clearances) directly on job plan tasks. This is a significant addition for organizations that need to ensure only qualified technicians are assigned to specific 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.

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.

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.

<!-- Example: Job plan task with qualifications in Maximo Manage 9.1 -->
<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>

Reliability Strategies: FMEA, RCM, and the Built-In Library

Maximo Manage 9.1 includes a comprehensive Reliability Strategies application that integrates Failure Mode and Effects Analysis (FMEA) and Reliability-Centered Maintenance (RCM) directly into the EAM platform. This is not a new feature, but the 9.1 release significantly enhances the capability with a built-in FMEA library, AI assists, and improved workflow integration.

The built-in FMEA library is the most significant addition. It spans approximately 800 asset types and 58,000 failure modes, providing a pre-populated starting point for reliability analysis. Instead of building FMEA records from scratch for each asset type, reliability engineers can select from the library and customize the failure modes, effects, causes, and recommended actions for their specific operating context. This dramatically reduces the time required to implement a reliability program.

The FMEA workflow connects failure modes directly to job plans and PMs. When a failure mode is identified for an asset, the reliability engineer can link it to a preventive maintenance schedule or a corrective job plan. This creates a closed-loop process: the FMEA identifies what can fail and why, the PM schedule defines when to inspect or maintain the asset, and the job plan defines what to do during the maintenance. When the work order is completed, the failure data feeds back into the FMEA, updating the risk priority number (RPN) and refining the analysis.

Manage 9.1 adds Settings within Reliability Strategies, allowing administrators to define RPN categories and action types. RPN categories group assets by risk level, making it easier to prioritize reliability efforts. Action types define the categories of corrective actions that can be recommended, such as PM modification, inspection addition, design change, or operator training. These configuration options give organizations the flexibility to tailor the reliability workflow to their specific standards and terminology.

The AI assist added in Manage 9.1 provides intelligent recommendations during the FMEA process. When a reliability engineer is working on an asset type that exists in the built-in library, the AI can suggest failure modes, effects, and causes based on similar assets in the library. This is particularly useful for organizations that are new to FMEA and need guidance on what failure modes to consider. The AI suggestions are recommendations, not mandates, and the engineer can accept, modify, or reject them.

The Rebuilt Inspection Framework

The inspection framework in Maximo Manage 9.1 has been rebuilt from the ground up. The old Inspection Forms Work Center is gone, replaced by a MAF-based Inspection Forms application with a refreshed Form Builder, new question types, conditional logic, scoring, and follow-up work order generation.

The Form Builder in Manage 9.1 provides a visual drag-and-drop interface for creating inspection forms. Administrators can add questions of various types including text, numeric, multiple choice, date, checkbox, and signature capture. Each question can have a weight assigned to it, and the form can be configured with a scoring model that calculates a total score based on the responses. Pass/fail thresholds can be set, and the system can automatically generate a follow-up work order if the inspection fails.

Conditional logic is a powerful addition. Questions can be configured to appear or disappear based on the answers to previous questions. For example, if the inspector answers "Yes" to "Is there visible corrosion?", a follow-up question "Rate the severity of corrosion (1-5)" appears. If the answer is "No", the follow-up question is hidden. This keeps the form concise and relevant, reducing inspector fatigue and improving data quality.

Form versioning is supported, which means changes to a form create a new version rather than overwriting the existing form. This is critical for audit compliance, as it ensures that historical inspection records reference the exact form version that was used at the time of the inspection. When a form is updated, existing in-progress inspections continue to use the old version, while new inspections use the updated version.

The inspection framework integrates with the mobile application, allowing technicians to complete inspections offline on their mobile devices. The forms are preloaded to the device before the technician goes offline, and the completed inspection data syncs back to the server when connectivity is restored. Electronic signature capture on inspection form status changes is supported in the mobile app, with the same configuration as the web interface.

The Scheduling Stack: Graphical Scheduling, Assignment, and AI-Driven FSM

Maximo Manage 9.1 includes a comprehensive scheduling stack that spans from long-horizon project scheduling to short-horizon daily dispatch. The stack has four layers: crafts/crews/calendars, Graphical Scheduling, Graphical Assignment, and the AI-driven Field Service Management solution.

The crafts/crews/calendars foundation defines the labor resources available for scheduling. Crafts define the skill types, crews define working groups, and calendars define availability. In Manage 9.1, the calendar system has been enhanced with support for shift times, availability reason codes, and more granular availability management. The availability reason code allows dispatchers to know not just that a technician is unavailable, but why (sick, training, vacation, assigned to another job).

Graphical Scheduling is the Gantt-based scheduling tool for outages, projects, and complex multi-asset work orders. It provides a visual timeline of work orders, resources, and dependencies, allowing schedulers to drag and drop assignments to optimize the schedule. In Manage 9.1, the Gantt view has been enhanced with map integration. When you open a map from the Gantt chart within the Dispatching dashboard, the map displays markers for each assignment, and clicking a marker shows a preview card with work order details.

Graphical Assignment handles the short-horizon dispatch, assigning individual work orders to technicians based on availability, skills, and location. The dispatching status values added in 9.1 provide real-time visibility into the assignment lifecycle, from creation through dispatch, acceptance, and completion.

The AI-driven Field Service Management solution, introduced in Manage 9.0 and extended in 9.1, is the most significant addition to the scheduling stack. It uses AI and machine learning to optimize schedules and labor assignments. The labor assignment optimization model includes new parameters for overtime and modified availability, giving the AI more flexibility to find optimal assignments. The Planning Dashboard added in 9.1 helps optimize schedule forecasting, resource allocation, cost management, and schedule inefficiency minimization.

A new parameter called TATImpactAlgo supports the RBF algorithm for understanding the impact on turnaround time (TAT). This allows the scheduling system to model how different assignment strategies affect the overall turnaround time for a set of work orders, helping dispatchers make data-driven decisions about resource allocation.

Admin and Configuration: What Changed for Administrators

For administrators, Manage 9.1 brings changes across the configuration stack. The Automation Scripts framework continues to be the primary extension mechanism, but the framework has been enhanced with the IMGLIB framework for image storage, allowing automation scripts to handle image storage, retrieval, and deletion from custom storage targets through the Maximo integration framework endpoint handler.

The Database Configuration application now supports electronic signature configuration on inspection form status transitions, giving administrators a no-code way to enforce signature capture for compliance. The ManageWorkspace custom resource in the MAS operator layer allows administrators to define attachment configuration as either file-based or object-based storage, providing flexibility in how attachments are managed.

API key management has been enhanced with expiry dates and certificate support. Administrators can now specify the expiry date and time when creating an API key, and they can insert a certificate for the API key. This is important for organizations that need to manage API key lifecycle and enforce rotation policies.

Maximo Manage 9.1 supports Java 17, which is a significant change from previous versions that ran on Java 11. This change affects custom code and integrations that may need to be recompiled and tested against the new Java version. BIRT reporting has been updated to version 4.16, which includes its own set of improvements and compatibility considerations.

The AI Configuration application is new in 9.1, providing administrators with a centralized interface for configuring the AI capabilities including the Maximo Assistant, similar work orders, similar records, and AI-recommended field values. This is where administrators enable and configure the AI features that are embedded throughout the Manage applications.

Practical Implications

Maximo Manage 9.1 is not a minor update. It is a platform shift that requires implementation teams to rethink how they configure and extend the system. The removal of Work Centers means that any organization upgrading from 8.x needs to plan for rebuilding customizations on MAF. The embedded AI capabilities require new configuration and potentially new skill sets in the administration team.

The built-in FMEA library is a game-changer for organizations that have been hesitant to implement reliability-centered maintenance because of the effort required to build FMEA records from scratch. With 800 asset types and 58,000 failure modes pre-populated, the barrier to entry is dramatically lower. The AI assist further accelerates the process by suggesting failure modes and actions based on similar assets.

The scheduling improvements, particularly the AI-driven FSM solution, are most valuable for organizations with large field service teams. Smaller organizations with simple scheduling needs may not see immediate value from the AI optimization, but the Graphical Scheduling and Graphical Assignment improvements are useful at any scale.

The Bottom Line

Maximo Manage 9.1 is the version that makes the MAS architecture feel mature. The role-based applications are polished, the AI integration is practical rather than experimental, and the reliability and inspection frameworks are production-ready. If you are upgrading from 8.x, the transition requires work, particularly around Work Center customizations, but the result is a more maintainable, more configurable, and more capable EAM platform. The 9.2 release builds on this foundation with mobile and field service improvements, but 9.1 is where the fundamental architecture shift happened.