Maximo Manage 9.1 Deep Dive: Work Orders, Reliability, and the New Role-Based Apps

Maximo Manage 9.1 Deep Dive: Work Orders, Reliability, and the New Role-Based AppsIBM Maximo Manage 9.1, released in June 2025 as part of MAS 9.1, is the most significant update to the core EAM application since the move to the Application Suite architecture. The release removes the legacy Work Centers, 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. For practitioners who have spent years in the classic Maximo interface, Manage 9.1 feels like a different product.

This article 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. Whether you are planning a migration or already on MAS 9, this guide covers what you need to know to get the most out of Manage 9.1.

The New Work Order Lifecycle and Job Plan Enhancements

The work order lifecycle in Maximo Manage 9.1 follows the same fundamental flow as previous versions: create, plan, schedule, assign, execute, report, and close. What has changed is the user experience, the depth of configuration options, and the AI capabilities that augment each step.

The Work Order Tracking application remains the primary interface for creating and managing work orders, but the underlying UI has been modernized. The classic Maximo look with its tab-heavy layout has been replaced with a cleaner, card-based interface that prioritizes the most relevant information. The Work Order Planning application, new in Manage 9.0 and refined in 9.1, provides a dedicated planning workspace where planners can estimate labor, materials, tools, and services without navigating the full Work Order Tracking application. The Work Queue Manager application, also new in 9.0, gives supervisors a consolidated view of work orders grouped by status, priority, or assignment, with batch actions for approvals and status changes.

Job plans received several important enhancements in 9.1. The most notable is the Qualifications field, which allows you to specify required qualifications (skills, certifications, or clearances) directly on job plan tasks. When a work order is generated from a job plan, the qualifications are copied to the work order tasks and used by the scheduling engine to match available labor. This closes a gap that previously required custom automation scripts or manual assignment verification.

-- Query: Find job plans missing required qualifications
SELECT jp.jpnum, jp.description, jpt.taskid, jpt.description AS task_desc
FROM jobplan jp
JOIN jobtask jpt ON jp.jpnum = jpt.jpnum AND jp.orgid = jpt.orgid
LEFT JOIN jobtaskqual jtq ON jpt.jpnum = jtq.jpnum
  AND jpt.taskid = jtq.taskid AND jpt.orgid = jtq.orgid
WHERE jp.status = 'ACTIVE'
  AND jtq.qualid IS NULL
  AND jpt.labortype IS NOT NULL
ORDER BY jp.jpnum, jpt.taskid;

Milestone tasks are another addition. A milestone task in a job plan marks a significant point in the work order execution: a safety checkpoint, a quality inspection gate, or a regulatory compliance verification. Milestone tasks can trigger notifications, require electronic sign-off, or block subsequent tasks until they are completed. This is particularly valuable for regulated industries where documented checkpoints are mandatory.

The Work Order Intelligence feature, introduced in MAS 9.0 and expanded in 9.1, uses AI to classify work orders and suggest similar work orders. When a user creates a work order description, the AI analyzes the text and suggests a classification (failure code, problem code, cause code) based on historical work order data. It also identifies similar past work orders, allowing planners to reuse job plans, labor estimates, and material lists. This reduces planning time and improves data quality by standardizing classifications.

For the work order report flow, 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.

The practical impact of these changes is that the work order lifecycle in Manage 9.1 is more streamlined for the most common workflows while providing deeper configuration options for complex scenarios. Planners spend less time navigating between applications, supervisors can manage work queues more efficiently, and the AI assists reduce the cognitive load of classification and planning.

Role-Based Applications and the Maximo Application Framework

The most visible change in Manage 9.1 is the removal of the legacy Work Centers (Dispatcher, Supervisor, Technician, etc.) and their replacement with role-based applications built on the Maximo Application Framework (MAF). MAF is a low-code application development framework that runs within MAS and produces web-based, mobile-friendly applications that work both online and offline.

The MAF applications in Manage 9.1 include: Technician (for field execution), Supervisor (for work management oversight), Dispatcher (for scheduling and assignment), Inventory (for stockroom management), and several others. Each application is configured through Mobile Studio, a visual development environment where you define the app layout, data sources, actions, and security.

The shift from Work Centers to MAF applications is not just a UI refresh. It is a fundamental change in how Maximo applications are built and maintained. Work Centers were pre-built applications with limited configuration options. If a Work Center did not meet your business requirements, you needed custom development. MAF applications are configurable: you can modify the layout, add or remove fields, change the data sources, define custom actions, and control access through role-based security, all without writing code.

For organizations migrating from Maximo 7.6, the MAF transition requires careful user management planning. Users who were accustomed to the Work Center interfaces need training on the new applications. The navigation is different, the terminology has changed in some cases, and the offline capabilities work differently. Plan for a structured training program with role-specific guides and hands-on workshops.

The Operational Dashboard, another new surface in Manage 9.1, provides a configurable landing page for users. Unlike the classic Start Center, which was personal and limited in layout options, the Operational Dashboard uses a widget-based architecture with real-time data updates. Administrators can create role-specific dashboards: a maintenance manager dashboard with KPIs for PM compliance, backlog, and wrench time; a dispatcher dashboard with assignment status maps and workload charts; a reliability engineer dashboard with failure trends and asset health scores.

{
  "dashboard": {
    "name": "Maintenance Manager Overview",
    "roles": ["MAINT_MANAGER"],
    "widgets": [
      {
        "type": "kpi-card",
        "title": "PM Compliance",
        "dataSource": "MXR_PMCMP",
        "target": 95,
        "color": "#2E7D32"
      },
      {
        "type": "chart-bar",
        "title": "Backlog by Priority",
        "dataSource": "MXR_BACKLOG",
        "groupBy": "WOPRIORITY"
      },
      {
        "type": "chart-line",
        "title": "Wrench Time Trend",
        "dataSource": "MXR_WRNCHT",
        "timeRange": "30d"
      }
    ]
  }
}

The admin split between MAS Suite and Manage is another important architectural change. In Maximo 7.6, all administration was done in the Maximo application. In MAS 9, some administrative functions moved to MAS Suite-level tools (user management, licensing, workspace configuration) while others remain in Manage (database configuration, automation scripts, workflow designer, application designer). Understanding which tool to use for which task is a common source of confusion in early migrations.

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

Reliability Strategies in Maximo Manage 9.1 is the application that connects failure modes to maintenance actions. It implements Failure Mode and Effects Analysis (FMEA) and Reliability-Centered Maintenance (RCM) methodologies within the Maximo data model, providing a structured framework for building and maintaining reliability programs.

The built-in Reliability Strategies library is one of the most valuable but underutilized features in Manage 9.1. The library spans approximately 800 asset types and 58,000 failure modes, providing pre-built failure hierarchies, failure effects, and recommended maintenance actions. Instead of starting from scratch for each asset type, reliability engineers can import the relevant portions of the library and customize them for their specific operating context.

The FMEA Builder Assistant, introduced in MAS 9.1, uses AI to help build out failure and remediation descriptions. Given an asset type and operating context, the assistant suggests failure modes, effects, and recommended actions based on the library and historical data. This dramatically reduces the time required to build a comprehensive reliability program, especially for organizations with diverse asset portfolios.

The connection between reliability strategies and maintenance execution is through job plans and PMs. Each failure mode in a reliability strategy can be linked to one or more job plans that define the maintenance tasks for mitigating that failure mode. The Risk Priority Number (RPN) drives prioritization: failure modes with high RPN values (calculated from severity, occurrence, and detection ratings) are flagged for priority action. The system can automatically generate PM work orders for high-RPN failure modes based on the associated job plan schedule.

Custom strategies allow organizations to extend beyond the library. A custom strategy defines a failure hierarchy, failure modes, effects, and actions for a specific asset type or operating context that is not covered by the library. Custom strategies are particularly valuable for specialized equipment, proprietary manufacturing assets, or unusual operating environments.

The RCM analysis workflow in Manage 9.1 follows a structured path: select the asset or asset type, review or build the failure hierarchy, assign severity/occurrence/detection ratings, calculate RPN, link maintenance actions (PMs, job plans, inspections, condition monitoring), and review the strategy effectiveness through the Asset Health application. The integration between Reliability Strategies and Asset Health (from the MAS Health application) provides a closed-loop process: the strategy defines what to monitor and maintain, and Asset Health provides the feedback on whether the strategy is working.

Inspections: The Rebuilt Framework

The inspection framework in Maximo Manage 9.1 has been rebuilt from the ground up. The Inspection Forms Work Center has been replaced by a MAF-based Inspections application, and the Form Builder has been refreshed with a more intuitive interface and expanded capabilities.

Inspection forms in Manage 9.1 support a wide range of question types: text, numeric, date, multiple choice, yes/no, checklist, signature, image capture, barcode scan, and meter reading. Conditional logic allows questions to appear or be skipped based on previous answers. For example, if a visual inspection question identifies a crack, a follow-up question about crack length and orientation appears automatically. Scoring and pass/fail criteria can be defined at the form level or the section level, with automatic calculation of overall inspection results.

Follow-up work orders are a key integration point. When an inspection identifies a defect or failure condition, the technician can create a follow-up work order directly from the inspection form. The follow-up work order inherits the asset, location, and failure information from the inspection, reducing manual data entry and ensuring traceability between the inspection finding and the corrective action. In Manage 9.1, this process was streamlined: technicians can create follow-up work orders from the multiple asset and location section of the work order, and they can choose which assets and locations the follow-up applies to.

Form versioning ensures that inspection forms can evolve without losing historical data. When you modify a form (add questions, change scoring, update conditional logic), the system creates a new version. Completed inspections are always associated with the form version that was in effect when the inspection was performed. This is critical for regulatory compliance, where you need to demonstrate exactly what was inspected and what the form looked like at the time of inspection.

The offline mobile execution of inspections is handled by Maximo Mobile, which syncs inspection forms to the mobile device and allows technicians to complete inspections without network connectivity. The sync architecture is REST-based, with a local SQLite database on the device for offline storage. When the device reconnects, the inspection results are uploaded to Manage, and any follow-up work orders are created.

Electronic signatures on inspection form status changes, added in 9.1, provide an additional layer of compliance. When a technician signs off on an inspection, the system records the user identity, timestamp, and form version. This signature is tamper-evident and stored in the audit log.

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

The scheduling stack in Maximo Manage 9.1 has three layers: the foundation (crafts, crews, calendars), the traditional scheduling tools (Graphical Scheduling and Graphical Assignment), and the AI-driven Field Service Management (FSM) solution.

The foundation layer defines the labor capacity: crafts (skills and qualifications), crews (teams of labor with shared availability), and calendars (working hours, shifts, holidays). This data feeds all scheduling tools and must be accurate for any scheduling to work properly.

Graphical Scheduling provides Gantt-based scheduling for complex, multi-task work such as outages and projects. The Gantt chart in Manage 9.1 has been enhanced with map integration: when you open a map from the Gantt chart, it displays markers for each assignment, and clicking a marker shows a preview card with work order details. This is particularly useful for distributed assets like pipelines, transmission lines, or transportation networks.

Graphical Assignment handles short-horizon dispatching: assigning today's and tomorrow's work to available labor. The Dispatching dashboard provides a consolidated view of assignments, labor availability, and workload. Dispatchers can drag and drop assignments, see conflicts (double-booking, qualification mismatches), and optimize routes.

The FSM solution, introduced in MAS 9.0 and extended in 9.1, brings AI-driven optimization to scheduling and dispatching. The Scheduling dashboard uses the Maximo Optimizer engine to automatically assign work orders to labor based on qualifications, availability, travel time, priority, and workload balance. The optimization model parameters can be tuned: overtime weight (penalty for overtime assignments), modified availability handling (respecting time-off requests and schedule changes), work type restrictions (preventing certain work types during modified availability periods), and travel time consideration (including travel to and from work in the optimization).

The destination travel time matrix, which calculates travel times between service addresses, can now be run as a cron task in 9.1, ensuring that travel times are always current. This is important for organizations with mobile workforces in urban areas where traffic patterns change throughout the day.

# FSM Optimization Parameters (Manage 9.1)
optimization:
  tatImpactAlgo: RBF  # Radial Basis Function for turnaround time impact
  overtimeWeight: 1.5  # Penalty multiplier for overtime assignments
  ignoredModAvailReasons: "TRAINING,PTO"
  modAvailForbidWorkType: "EMERGENCY,SHUTDOWN"
  modAvailWorkBased:
    considerTravel: true
  modAvailOvertime:
    global:
      duration: 120  # minutes
  modAvailOvertimeCostByReasonCode: "TRAINING=1.2,PTO=1.0"

Admin and Configuration: Automation Scripts, Workflow, and the New Tools

The admin layer in Maximo Manage 9.1 retains the core configuration tools that Maximo practitioners know: Database Configuration, Application Designer, Security Groups, Domains, and Workflow Designer. But several new tools and changes have been added that change how administrators work.

Automation Scripts remain the primary customization mechanism. In 9.1, the script engine supports JavaScript (Nashorn), Python (Jython), and the Maximo expression language. Scripts can be triggered by object events (save, delete, status change), launch points (custom buttons or menu items), or cron tasks. The script editor in the UI has been improved with better syntax highlighting and error reporting.

The Formulas feature, introduced in MAS 8.x and refined in 9.1, allows administrators to define calculated fields without writing scripts. Formulas use a spreadsheet-like expression language and can be associated with object attributes in the Database Configuration application. For example, you can create a formula that calculates the estimated cost of a work order based on labor hours, material costs, and service costs, and display it as a read-only field on the work order.

The in-MAS Application Configuration tool allows administrators to configure application-level settings (UI themes, navigation, default values, field labels) without using Application Designer. This is part of IBM's strategy to move configuration from code-level changes to configuration-level changes, reducing the need for Java expertise.

Workflow Designer in 9.1 is visually similar to 7.6 but has been rebuilt on modern web technology. Workflow processes can be enabled on any Maximo application, with task nodes for assignments, condition nodes for branching, and notification nodes for alerts. The interaction between workflow and the role-based MAF applications requires careful configuration: the workflow actions need to be exposed in the MAF application through action definitions.

The Operational Dashboard configuration is a new admin responsibility. Administrators create dashboard templates, assign them to security groups, and configure the data sources (SQL queries or REST API calls) that feed the dashboard widgets. The dashboards are not user-customizable in 9.1, so the admin needs to design dashboards that work for each role.

Practical Implications

For practitioners, the shift to Manage 9.1 requires relearning some familiar workflows and taking advantage of new capabilities. The Work Centers are gone, and the MAF applications are the future. If your organization has heavily customized Work Centers, those customizations need to be rebuilt in MAF, which is an opportunity to simplify and standardize rather than replicate legacy complexity.

The AI capabilities in 9.1 are not just marketing features. Work Order Intelligence and the FMEA Builder Assistant can materially reduce planning time and improve data quality. But they require a sufficient volume of historical work order data to be effective. Organizations with sparse or inconsistent work order history will see limited AI value initially, with improving results as data quality improves.

The admin split between MAS Suite and Manage means that some tasks that were once in one place are now in two. Invest time in understanding which tool handles which function before the migration, and document the admin workflows for your specific configuration.

Bottom Line

Maximo Manage 9.1 is a mature, capable EAM application that preserves the depth of Maximo's asset management model while modernizing the user experience, adding AI capabilities, and providing a more flexible configuration layer. The removal of Work Centers and the shift to MAF applications is the most disruptive change for existing users, but it also unlocks the ability to tailor applications to specific roles and business processes without custom Java development. The reliability strategies, inspection framework, and AI-driven scheduling provide operational value that justifies the migration effort for most organizations.