Mastering Work Order Automation in Maximo Manage: PM Generation, Cron Tasks, and Conditional Monitoring

Work orders are the heartbeat of Maximo Manage. Every maintenance activity, from routine inspections to emergency repairs, flows through the work order system. Yet many organizations still generate work orders manually, missing the automation capabilities that Maximo has built in for years. This article is a technical deep dive into the three primary automation mechanisms: Preventive Maintenance (PM) generation, Cron Task scheduling, and Conditional Monitoring triggers. By the end, you will understand how to configure each one, how they interact, and how to build a maintenance automation strategy that reduces manual effort while improving reliability.

The core premise is simple: maintenance should happen automatically when it is supposed to, and humans should only intervene when something unexpected occurs. Maximo Manage provides the tools to make this a reality. The question is whether your configuration takes advantage of them. Too many Maximo installations have PM records that generate work orders but require manual approval, manual assignment, and manual scheduling. That is not automation. That is assisted manual entry. True automation means the system generates the work order, assigns it, schedules it, and notifies the technician, all without a human touching a keyboard.

Building Effective PM Records

A Preventive Maintenance (PM) record in Maximo is the foundation of automated work order generation. It defines what maintenance should happen, on which asset or location, at what frequency, and using which job plan. The PM record is not the work order itself. It is the template and trigger that generates work orders on a schedule.

The essential PM configuration elements include:

• Asset or Location: The PM must be tied to an asset or location. If tied to a location, you can control whether the generated work order inherits the location's asset (if there is only one). In MAS 9.2, this auto-population behavior is now configurable, giving you more control over how single-asset locations are handled.
• Job Plan: The predefined template that specifies tasks, labor, materials, services, and tools required for the job. The job plan is what gives the generated work order its substance. Without a job plan, a PM generates an empty work order that someone has to fill in manually.
• Frequency: PMs can be time-based (daily, weekly, monthly, quarterly, annually) or meter-based (every X run hours, every Y cycles). For meter-based PMs, the asset must have a meter defined, and meter readings must be captured either manually through Maximo Mobile or via integration with SCADA or IoT systems.
• Calendar and Shift: The work calendar and shift determine which days and times are available for scheduling. A PM tied to a Monday-to-Friday calendar will not generate work orders for weekends unless the calendar is adjusted.
• Lead Time: How far in advance the work order should be generated before the target start date. A lead time of 7 days means the work order appears in the system a week before it is scheduled to start, giving planners time to review and assign.

PM options give you additional control. You can set the initial work order status on generation (such as WSCH for scheduled or WAPPR for waiting approval). You can control whether child routes and job plan tasks come along with the generated work order. You can specify target start dates, day-of-week preferences, and seasonal windows. For meter-based PMs, you need to ensure the meter, reading types, and thresholds are all correct, because the system relies on accurate meter data to trigger generation.

Here is a practical PM configuration example:

PM Number: 1001
Asset: PUMP-100 (Cooling Water Pump)
Job Plan: JP-CWP-PM-001 (Monthly Inspection)
Frequency: Time-based, every 30 days
Calendar: STD-7DAY (7-day work week)
Shift: DAY-SHIFT (06:00-18:00)
Lead Time: 5 days
Initial WO Status: WSCH (Scheduled)
Generate Work Order: Automatic via PMWoGenCronTask

This PM generates a work order every 30 days, 5 days before the target start date, with an initial status of Scheduled. The job plan attached to it defines the inspection tasks, required labor, and estimated duration. The work order appears in the system automatically and flows to the scheduler for assignment.

Cron Tasks: The Silent Workforce

Cron tasks are predefined jobs that run automatically on a fixed schedule to perform system operations. They are the engine behind PM generation, condition monitoring, escalations, inventory reordering, KPI calculation, and email processing. Understanding cron tasks is essential for building a fully automated Maximo environment.

The most critical cron tasks for work order automation are:

• PMWoGenCronTask: The Preventive Maintenance Work Order Generation cron task. This is the task that reads PM records, checks whether any are due based on the frequency and lead time, and generates work orders. It should be scheduled to run daily, typically overnight, so work orders are ready for planners by the start of the business day.
• MeasurePointWoGenCronTask: The Condition Monitoring work order generation cron task. This task checks whether meter readings or measurements have reached conditions defined in the Condition Monitoring application, and generates work orders when thresholds are breached. Depending on the criticality of the monitored assets, this can run every minute, every hour, or every few hours.
• ESCALATION: The escalation cron task processes escalations to ensure critical tasks are completed on time. It checks whether work orders have exceeded their target completion dates and triggers notifications, status changes, or reassignments based on escalation rules.
• KPICronTask: Generates key performance indicators. This task calculates metrics such as mean time to repair, work order completion rates, and PM compliance, feeding data into dashboards and reports.
• ReorderCronTask: Determines rules and parameters for scheduled reordering of inventory items, direct issue items, and inventory parts. This ensures that spare parts are available when work orders require them.

Configuring a cron task is straightforward but requires attention to detail. Each cron task has a schedule (defined in CRON format), an active flag, and parameters specific to the task. For PMWoGenCronTask, the key parameters include the organization and site filters, the generation window (how far ahead to look for due PMs), and whether to generate work orders for PMs with no job plan.

Here is an example of PMWoGenCronTask configuration:

Cron Task: PMWoGenCronTask
Instance: PMGEN-BEDFORD
Schedule: Every day at 02:00 (0 0 2 * * ?)
Active: Yes
Organization: BEDFORD
Site: (All sites)
Generation Window: 30 days
Generate WOs for PMs without Job Plans: No

This configuration runs every night at 2:00 AM, checks all PMs in the BEDFORD organization, generates work orders for any PMs due within the next 30 days, and skips PMs that do not have a job plan attached. The 30-day generation window means planners always have at least a month of visibility into upcoming PM work.

For the MeasurePointWoGenCronTask, the schedule depends on how time-sensitive the condition monitoring is. For critical assets where a threshold breach should trigger a work order within minutes, set the cron task to run every minute. For less critical monitoring, every 15 minutes or hourly may be sufficient. The trade-off is system load: running every minute generates more database queries and consumes more CPU cycles.

Conditional Monitoring: Trigger-Driven Maintenance

Conditional Monitoring in Maximo Manage is the mechanism that connects sensor data and meter readings to work order generation. It is the bridge between condition-based maintenance strategy and automated execution. When a meter reading falls outside defined thresholds, the system can automatically generate a work order to investigate or address the issue.

The setup involves three components:

1. Meter on the Asset: The asset must have a meter defined. Meters can be continuous (gauge-type, such as temperature or vibration readings) or characteristic (reading-type, such as inspection pass/fail). The meter must be associated with the asset record.
2. Condition Monitoring Record: This defines which meter to monitor, what the upper and lower action limits are, what warning thresholds to set, and what job plan or PM to trigger when limits are breached.
3. Cron Task Activation: The MeasurePointWoGenCronTask must be active and scheduled to check the condition monitoring records against incoming meter readings.

Here is a practical conditional monitoring setup for a conveyor belt motor:

Asset: CONV-001 (Conveyor Belt Motor)
Meter: TEMP-MOTOR (Gauge meter, continuous, Fahrenheit)
Condition Monitoring Record:
  - Title: Motor Temperature Monitoring
  - Asset: CONV-001
  - Meter: TEMP-MOTOR
  - Upper Action Limit: 200°F
  - Upper Warning Limit: 180°F
  - Lower Action Limit: 32°F
  - Lower Warning Limit: 40°F
  - Job Plan: JP-MOTOR-TEMP-001 (Motor Overheating Investigation)
  - Priority: 1 (Urgent)
  - Work Type: Corrective Maintenance

Cron Task:
  - Task: MeasurePointWoGenCronTask
  - Instance: CONDMON-CRITICAL
  - Schedule: Every 1 minute
  - Active: Yes
  - Organization: BEDFORD

When a meter reading above 200°F is recorded for the motor temperature, the system generates a corrective maintenance work order with priority 1, linked to the Motor Overheating Investigation job plan. The work order appears in the system within 1 minute of the reading being recorded, assuming the cron task is running at that frequency.

Meter readings can enter the system in several ways. Technicians can enter them manually through Maximo Mobile, scanning the asset's QR code and recording the reading on their device. They can be entered through the desktop interface using the Meter Readings application. They can also be fed in automatically through the Maximo Integration Framework, which supports integration with OSI Pi systems, SCADA historians, and IoT platforms. For low-frequency data (such as daily run-hour readings), the integration framework is sufficient. For high-frequency, real-time sensor data, Maximo Monitor is the appropriate tool, as it handles time-series data at scale and can trigger actions based on analytics rules.

Job Plans: The Templates That Make Automation Work

Job plans are the templates that give automated work orders their substance. A well-structured job plan defines the tasks, labor requirements, materials, services, tools, and estimated duration for a job. Without a good job plan, an automated work order is just an empty record that requires manual effort to complete.

A job plan includes:

• Tasks: Sequential steps that describe what work needs to be done. Each task has a description, an estimated duration, and can require specific labor crafts or skills.
• Labor: The crafts, skill levels, and number of people required for each task.
• Materials: The items and quantities needed, pulled from the inventory or special-ordered.
• Services: External services required, such as contractor work or specialized testing.
• Tools: Equipment needed to perform the job, such as cranes, test equipment, or safety gear.
• Safety Plans: Linked safety procedures and hazard information that apply to the job.

Job plans can be nested. A parent job plan can reference child job plans, creating a hierarchical structure for complex maintenance activities. This is particularly useful for large shutdowns or turnarounds, where a single work order may encompass dozens of sub-tasks across multiple crafts.

The Reliability Strategies add-on (available since MAS 8.11) provides a library of 800 asset types with over 58,000 failure modes and 5,000 recommended PM tasks. Instead of building job plans from scratch, you can select an asset type from the library, review the recommended mitigation activities, and copy them directly into your job plans. This brings decades of RCM expertise into your configuration without requiring a reliability engineer on staff.

Putting It All Together: An Automated Maintenance Workflow

Let us walk through a complete automation scenario that combines all three mechanisms. Consider a fleet of 50 cooling water pumps across a manufacturing facility.

Step 1: Create job plans for each maintenance type: - Monthly inspection (JP-CWP-INSP-001): Visual inspection, temperature reading, vibration check, 2 hours estimated. - Quarterly service (JP-CWP-QSRV-001): Filter replacement, seal inspection, lubrication, 4 hours estimated. - Annual overhaul (JP-CWP-OVER-001): Complete disassembly, bearing replacement, alignment, 16 hours estimated.

Step 2: Create PM records for each pump and maintenance type: - Monthly PM: Time-based, 30 days, lead time 5 days, initial status WSCH. - Quarterly PM: Time-based, 90 days, lead time 10 days, initial status WSCH. - Annual PM: Time-based, 365 days, lead time 30 days, initial status WAPPR (requires approval due to cost).

Step 3: Set up condition monitoring for critical pumps: - Monitor motor temperature on the 10 most critical pumps. - Upper action limit at 200°F, triggers corrective maintenance work order. - Upper warning limit at 180°F, generates notification to maintenance supervisor.

Step 4: Configure cron tasks: - PMWoGenCronTask: Daily at 2:00 AM, generates work orders for all due PMs. - MeasurePointWoGenCronTask: Every 5 minutes, checks condition monitoring records. - ESCALATION: Every 30 minutes, checks for overdue work orders and triggers notifications.

Step 5: Configure escalations: - If a corrective work order from condition monitoring is not assigned within 2 hours, notify the maintenance manager. - If a PM-generated work order is not completed within 7 days of its target finish date, escalate to the operations director.

With this configuration, the monthly and quarterly inspections generate automatically, are assigned by the scheduler, and flow to technicians via Maximo Mobile. The annual overhaul generates in WAPPR status, requiring planner approval before proceeding. Temperature monitoring runs continuously, and if any critical pump exceeds 200°F, a corrective work order is generated within 5 minutes with priority 1. Escalations ensure that nothing falls through the cracks.

Practical Implications

The difference between a Maximo installation that uses automation and one that does not is the difference between a maintenance team that is proactive and one that is reactive. Organizations that fully leverage PM generation, cron tasks, and conditional monitoring report significant reductions in unplanned downtime, improved PM compliance rates, and reduced administrative overhead. The maintenance planners spend their time optimizing schedules and analyzing trends rather than creating work orders by hand.

If you are starting from scratch, begin with PM generation. Get your job plans defined, your PM records created, and your PMWoGenCronTask running daily. Once that is stable, add conditional monitoring for your most critical assets. Start with a handful of assets, define meaningful thresholds, and let the system generate work orders when those thresholds are breached. Finally, configure escalations to ensure that generated work orders do not sit idle. The goal is to build a system where the routine maintenance happens automatically, and human effort is focused on exceptions, analysis, and continuous improvement.

One modern pattern worth considering is externalizing some Maximo automation to external orchestrators like GitHub Actions. Some organizations are moving operational orchestration (such as triggering PM generation, monitoring integration health, and managing data sync schedules) to external schedulers while keeping business logic (such as escalation rules and condition monitoring thresholds) inside Maximo. This hybrid approach gives you better observability and governance for the operational layer while keeping Maximo as the system of record. The key principle is: if it is business logic, keep it inside Maximo. If it is operational orchestration, consider externalizing it.

Bottom Line

Work order automation in Maximo Manage is not a single feature you turn on. It is a combination of PM records, cron tasks, conditional monitoring, job plans, and escalations working together. The configuration effort is front-loaded: you invest time in building job plans, defining PMs, and setting up condition monitoring records. Once configured, the system runs on its own, generating work orders, triggering alerts, and escalating overdue items without manual intervention. The result is a maintenance operation that is proactive rather than reactive, efficient rather than administrative, and data-driven rather than intuition-based. Start with your most critical assets, build the automation foundation, and expand from there. The tools are all there. The question is whether you are using them.