Dates are the backbone of the maintenance cycle in IBM Maximo: they drive Work Order (WO) generation, planning, compliance, and KPI tracking.
Between Preventive Maintenance (PM), Work Orders, Job Plans, and status changes, their logic is often misunderstood.

This article details the key date fields involved in the PM ↔ WO lifecycle, their visibility in the user interface (UI), and the main differences between Maximo 7.6 and MAS 9 (Maximo Manage).

🆚 MAS 9 :

• The PMWoGen engine is now a containerized microservice (PM Engine).
• The new React-based UI provides dynamic preview of due dates.
• Automation Scripts are managed directly in Manage UI, with Python 3 + Event Actions support and no EAR deployment required.

1. Types of Maintenance and Date Logic

🆚 MAS 9:

• Integrated with IoT Predict (event-stream-based).
• Can be linked to Watsonx AI Rules for intelligent triggering.

2. PM Module Date Attributes

💡 MAS 9:

• PMNEXTDUEDATE is updated automatically after WO closure.
• The calculation is performed by the PM Engine Service (REST) instead of the traditional Cron Task.

3. Work Order Module Date Attributes

🧭 Key takeaway:

• ACTSTART, ACTFINISH, and STATUSDATE close the PM ↔ WO feedback loop.
• PMDUEDATE records the original PM due date when the WO was created.

4. Date Calculation Logic in PM

⏱️ Time-based Scheduling

🧮 Formula:
Generation Date = NEXTDUEDATE - LEADTIME

🆚 MAS 9:

• Option "Recalculate Next Due Automatically" available in UI.
• Calculations handled by PM Engine microservice (REST).

⚙️ Meter-based Scheduling

• Generation is triggered when the meter threshold is reached.
• The MEASUREDATE becomes the base for the WO REPORTDATE.

🆚 MAS 9:

• Managed by Meter Events Service (Kafka / MQTT).
• Native IoT and predictive analytics support.

🔔 Condition-based Scheduling

• Triggered by Condition Monitoring or Automation Scripts.
• ACTSTART is initialized with the event date.

🆚 MAS 9:

• Configurable in Monitor Events UI.
• Can trigger Automation Policies or Event Actions.

5. Status Lifecycle and PM ↔ WO Feedback

5.1 Standard Statuses

🆚 MAS 9:

• Workflow transitions managed via Workflow Designer Web.
• Date fields automatically updated by Work Execution API.

5.2 PM ↔ WO Feedback Loop

1. PM calculates NEXTDUEDATE
2. PMWoGen Cron Task generates WO
3. WO progresses: WAPPR → APPR → INPRG → COMP → CLOSE
4. Closing the WO updates LASTCOMPDATE = ACTFINISH
5. PM recalculates NEXTDUEDATE based on FREQUENCY and USETARGETDATE

📊 Simplified Flow:

[PM: NEXTDUEDATE]

   ↓

[WO: WAPPR → APPR → INPRG → COMP → CLOSE]

   ↓

[PM: LASTCOMPDATE = ACTFINISH]

   ↓

[PM: NEXTDUEDATE recalculated → New WO]

🆚 Default MAS 9 Behavior:
PMWoGenCronTask remains the default execution mechanism.
Event listeners in MAS 9 are optional, enabling real-time updates without waiting for the Cron Task - only if custom event configuration is implemented.

6. Practical Use Cases

7. Best Practices

• Always close Work Orders (CLOSE) to ensure PM updates.
• Verify coherence between FREQUENCY and LEADTIME.
• Automate updates via script:
• if mbo.getString("STATUS") == "CLOSE":

   pmSet = MXServer.getMXServer().getMboSet("PM", mbo.getUserInfo())

    # update LASTCOMPDATE

• Use accurate Job Plans for reliable scheduling (SCHEDSTART / SCHEDFINISH).

🆚 MAS 9:

• Both Jython and Python 3 scripts are supported.
• Automation Policies allow low-code event-based automation.

8. Useful Queries

SELECT p.pmnum, w.wonum, w.status, w.statusdate, w.actstart, w.actfinish,

       p.nextduedate, p.lastcompdate

FROM workorder w

JOIN pm p ON w.pmnum = p.pmnum

WHERE w.origrecordclass = 'PM';

🆚 MAS 9 REST Equivalent:
/oslc/os/mxpm?oslc.select=pmnum,nextduedate,lastcompdate&lean=1

Conclusion

Consistency between PM and Work Order date fields ensures reliable scheduling and effective preventive maintenance.
In Maximo 7.6, logic relies on Cron Tasks and local scripts.
In MAS 9, the same functional logic is enhanced through an event-driven microservice architecture, enabling faster and more reliable updates.

✅ MAS 9 modernizes without changing the core:
same functional model, improved reliability, and near real-time updates.
PMWoGenCronTask remains the process backbone, while event listeners provide optional real-time responsiveness for advanced environments.

Dates are the backbone of the maintenance cycle in IBM Maximo: they drive Work Order (WO) generation, planning, compliance, and KPI tracking.
Between Preventive Maintenance (PM), Work Orders, Job Plans, and status changes, their logic is often misunderstood.

This article details the key date fields involved in the PM ↔ WO lifecycle, their visibility in the user interface (UI), and the main differences between Maximo 7.6 and MAS 9 (Maximo Manage).

🆚 MAS 9 :

• The PMWoGen engine is now a containerized microservice (PM Engine).
• The new React-based UI provides dynamic preview of due dates.
• Automation Scripts are managed directly in Manage UI, with Python 3 + Event Actions support and no EAR deployment required.

1. Types of Maintenance and Date Logic

🆚 MAS 9:

• Integrated with IoT Predict (event-stream-based).
• Can be linked to Watsonx AI Rules for intelligent triggering.

2. PM Module Date Attributes

💡 MAS 9:

• PMNEXTDUEDATE is updated automatically after WO closure.
• The calculation is performed by the PM Engine Service (REST) instead of the traditional Cron Task.

3. Work Order Module Date Attributes

🧭 Key takeaway:

• ACTSTART, ACTFINISH, and STATUSDATE close the PM ↔ WO feedback loop.
• PMDUEDATE records the original PM due date when the WO was created.

4. Date Calculation Logic in PM

⏱️ Time-based Scheduling

🧮 Formula:
Generation Date = NEXTDUEDATE - LEADTIME

🆚 MAS 9:

• Option "Recalculate Next Due Automatically" available in UI.
• Calculations handled by PM Engine microservice (REST).

⚙️ Meter-based Scheduling

• Generation is triggered when the meter threshold is reached.
• The MEASUREDATE becomes the base for the WO REPORTDATE.

🆚 MAS 9:

• Managed by Meter Events Service (Kafka / MQTT).
• Native IoT and predictive analytics support.

🔔 Condition-based Scheduling

• Triggered by Condition Monitoring or Automation Scripts.
• ACTSTART is initialized with the event date.

🆚 MAS 9:

• Configurable in Monitor Events UI.
• Can trigger Automation Policies or Event Actions.

5. Status Lifecycle and PM ↔ WO Feedback

5.1 Standard Statuses

🆚 MAS 9:

• Workflow transitions managed via Workflow Designer Web.
• Date fields automatically updated by Work Execution API.

5.2 PM ↔ WO Feedback Loop

1. PM calculates NEXTDUEDATE
2. PMWoGen Cron Task generates WO
3. WO progresses: WAPPR → APPR → INPRG → COMP → CLOSE
4. Closing the WO updates LASTCOMPDATE = ACTFINISH
5. PM recalculates NEXTDUEDATE based on FREQUENCY and USETARGETDATE

📊 Simplified Flow:

[PM: NEXTDUEDATE]

   ↓

[WO: WAPPR → APPR → INPRG → COMP → CLOSE]

   ↓

[PM: LASTCOMPDATE = ACTFINISH]

   ↓

[PM: NEXTDUEDATE recalculated → New WO]

🆚 Default MAS 9 Behavior:
PMWoGenCronTask remains the default execution mechanism.
Event listeners in MAS 9 are optional, enabling real-time updates without waiting for the Cron Task - only if custom event configuration is implemented.

6. Practical Use Cases

7. Best Practices

• Always close Work Orders (CLOSE) to ensure PM updates.
• Verify coherence between FREQUENCY and LEADTIME.
• Automate updates via script:
• if mbo.getString("STATUS") == "CLOSE":

   pmSet = MXServer.getMXServer().getMboSet("PM", mbo.getUserInfo())

    # update LASTCOMPDATE

• Use accurate Job Plans for reliable scheduling (SCHEDSTART / SCHEDFINISH).

🆚 MAS 9:

• Both Jython and Python 3 scripts are supported.
• Automation Policies allow low-code event-based automation.

8. Useful Queries

SELECT p.pmnum, w.wonum, w.status, w.statusdate, w.actstart, w.actfinish,

       p.nextduedate, p.lastcompdate

FROM workorder w

JOIN pm p ON w.pmnum = p.pmnum

WHERE w.origrecordclass = 'PM';

🆚 MAS 9 REST Equivalent:
/oslc/os/mxpm?oslc.select=pmnum,nextduedate,lastcompdate&lean=1

Conclusion

Consistency between PM and Work Order date fields ensures reliable scheduling and effective preventive maintenance.
In Maximo 7.6, logic relies on Cron Tasks and local scripts.
In MAS 9, the same functional logic is enhanced through an event-driven microservice architecture, enabling faster and more reliable updates.

✅ MAS 9 modernizes without changing the core:
same functional model, improved reliability, and near real-time updates.
PMWoGenCronTask remains the process backbone, while event listeners provide optional real-time responsiveness for advanced environments.

Dates are the backbone of the maintenance cycle in IBM Maximo: they drive Work Order (WO) generation, planning, compliance, and KPI tracking.
Between Preventive Maintenance (PM), Work Orders, Job Plans, and status changes, their logic is often misunderstood.

This article details the key date fields involved in the PM ↔ WO lifecycle, their visibility in the user interface (UI), and the main differences between Maximo 7.6 and MAS 9 (Maximo Manage).

🆚 MAS 9 :

• The PMWoGen engine is now a containerized microservice (PM Engine).
• The new React-based UI provides dynamic preview of due dates.
• Automation Scripts are managed directly in Manage UI, with Python 3 + Event Actions support and no EAR deployment required.

1. Types of Maintenance and Date Logic

🆚 MAS 9:

• Integrated with IoT Predict (event-stream-based).
• Can be linked to Watsonx AI Rules for intelligent triggering.

2. PM Module Date Attributes

💡 MAS 9:

• PMNEXTDUEDATE is updated automatically after WO closure.
• The calculation is performed by the PM Engine Service (REST) instead of the traditional Cron Task.

3. Work Order Module Date Attributes

🧭 Key takeaway:

• ACTSTART, ACTFINISH, and STATUSDATE close the PM ↔ WO feedback loop.
• PMDUEDATE records the original PM due date when the WO was created.

4. Date Calculation Logic in PM

⏱️ Time-based Scheduling

🧮 Formula:
Generation Date = NEXTDUEDATE - LEADTIME

🆚 MAS 9:

• Option "Recalculate Next Due Automatically" available in UI.
• Calculations handled by PM Engine microservice (REST).

⚙️ Meter-based Scheduling

• Generation is triggered when the meter threshold is reached.
• The MEASUREDATE becomes the base for the WO REPORTDATE.

🆚 MAS 9:

• Managed by Meter Events Service (Kafka / MQTT).
• Native IoT and predictive analytics support.

🔔 Condition-based Scheduling

• Triggered by Condition Monitoring or Automation Scripts.
• ACTSTART is initialized with the event date.

🆚 MAS 9:

• Configurable in Monitor Events UI.
• Can trigger Automation Policies or Event Actions.

5. Status Lifecycle and PM ↔ WO Feedback

5.1 Standard Statuses

🆚 MAS 9:

• Workflow transitions managed via Workflow Designer Web.
• Date fields automatically updated by Work Execution API.

5.2 PM ↔ WO Feedback Loop

1. PM calculates NEXTDUEDATE
2. PMWoGen Cron Task generates WO
3. WO progresses: WAPPR → APPR → INPRG → COMP → CLOSE
4. Closing the WO updates LASTCOMPDATE = ACTFINISH
5. PM recalculates NEXTDUEDATE based on FREQUENCY and USETARGETDATE

📊 Simplified Flow:

[PM: NEXTDUEDATE]

   ↓

[WO: WAPPR → APPR → INPRG → COMP → CLOSE]

   ↓

[PM: LASTCOMPDATE = ACTFINISH]

   ↓

[PM: NEXTDUEDATE recalculated → New WO]

🆚 Default MAS 9 Behavior:
PMWoGenCronTask remains the default execution mechanism.
Event listeners in MAS 9 are optional, enabling real-time updates without waiting for the Cron Task - only if custom event configuration is implemented.

6. Practical Use Cases

7. Best Practices

• Always close Work Orders (CLOSE) to ensure PM updates.
• Verify coherence between FREQUENCY and LEADTIME.
• Automate updates via script:
• if mbo.getString("STATUS") == "CLOSE":

   pmSet = MXServer.getMXServer().getMboSet("PM", mbo.getUserInfo())

    # update LASTCOMPDATE

• Use accurate Job Plans for reliable scheduling (SCHEDSTART / SCHEDFINISH).

🆚 MAS 9:

• Both Jython and Python 3 scripts are supported.
• Automation Policies allow low-code event-based automation.

8. Useful Queries

SELECT p.pmnum, w.wonum, w.status, w.statusdate, w.actstart, w.actfinish,

       p.nextduedate, p.lastcompdate

FROM workorder w

JOIN pm p ON w.pmnum = p.pmnum

WHERE w.origrecordclass = 'PM';

🆚 MAS 9 REST Equivalent:
/oslc/os/mxpm?oslc.select=pmnum,nextduedate,lastcompdate&lean=1

Conclusion

Consistency between PM and Work Order date fields ensures reliable scheduling and effective preventive maintenance.
In Maximo 7.6, logic relies on Cron Tasks and local scripts.
In MAS 9, the same functional logic is enhanced through an event-driven microservice architecture, enabling faster and more reliable updates.

✅ MAS 9 modernizes without changing the core:
same functional model, improved reliability, and near real-time updates.
PMWoGenCronTask remains the process backbone, while event listeners provide optional real-time responsiveness for advanced environments.

Dates are the backbone of the maintenance cycle in IBM Maximo: they drive Work Order (WO) generation, planning, compliance, and KPI tracking.
Between Preventive Maintenance (PM), Work Orders, Job Plans, and status changes, their logic is often misunderstood.

This article details the key date fields involved in the PM ↔ WO lifecycle, their visibility in the user interface (UI), and the main differences between Maximo 7.6 and MAS 9 (Maximo Manage).

🆚 MAS 9 :

• The PMWoGen engine is now a containerized microservice (PM Engine).
• The new React-based UI provides dynamic preview of due dates.
• Automation Scripts are managed directly in Manage UI, with Python 3 + Event Actions support and no EAR deployment required.

1. Types of Maintenance and Date Logic

🆚 MAS 9:

• Integrated with IoT Predict (event-stream-based).
• Can be linked to Watsonx AI Rules for intelligent triggering.

2. PM Module Date Attributes

💡 MAS 9:

• PMNEXTDUEDATE is updated automatically after WO closure.
• The calculation is performed by the PM Engine Service (REST) instead of the traditional Cron Task.

3. Work Order Module Date Attributes

🧭 Key takeaway:

• ACTSTART, ACTFINISH, and STATUSDATE close the PM ↔ WO feedback loop.
• PMDUEDATE records the original PM due date when the WO was created.

4. Date Calculation Logic in PM

⏱️ Time-based Scheduling

🧮 Formula:
Generation Date = NEXTDUEDATE - LEADTIME

🆚 MAS 9:

• Option "Recalculate Next Due Automatically" available in UI.
• Calculations handled by PM Engine microservice (REST).

⚙️ Meter-based Scheduling

• Generation is triggered when the meter threshold is reached.
• The MEASUREDATE becomes the base for the WO REPORTDATE.

🆚 MAS 9:

• Managed by Meter Events Service (Kafka / MQTT).
• Native IoT and predictive analytics support.

🔔 Condition-based Scheduling

• Triggered by Condition Monitoring or Automation Scripts.
• ACTSTART is initialized with the event date.

🆚 MAS 9:

• Configurable in Monitor Events UI.
• Can trigger Automation Policies or Event Actions.

5. Status Lifecycle and PM ↔ WO Feedback

5.1 Standard Statuses

🆚 MAS 9:

• Workflow transitions managed via Workflow Designer Web.
• Date fields automatically updated by Work Execution API.

5.2 PM ↔ WO Feedback Loop

1. PM calculates NEXTDUEDATE
2. PMWoGen Cron Task generates WO
3. WO progresses: WAPPR → APPR → INPRG → COMP → CLOSE
4. Closing the WO updates LASTCOMPDATE = ACTFINISH
5. PM recalculates NEXTDUEDATE based on FREQUENCY and USETARGETDATE

📊 Simplified Flow:

[PM: NEXTDUEDATE]

   ↓

[WO: WAPPR → APPR → INPRG → COMP → CLOSE]

   ↓

[PM: LASTCOMPDATE = ACTFINISH]

   ↓

[PM: NEXTDUEDATE recalculated → New WO]

🆚 Default MAS 9 Behavior:
PMWoGenCronTask remains the default execution mechanism.
Event listeners in MAS 9 are optional, enabling real-time updates without waiting for the Cron Task - only if custom event configuration is implemented.

6. Practical Use Cases

7. Best Practices

• Always close Work Orders (CLOSE) to ensure PM updates.
• Verify coherence between FREQUENCY and LEADTIME.
• Automate updates via script:
• if mbo.getString("STATUS") == "CLOSE":

   pmSet = MXServer.getMXServer().getMboSet("PM", mbo.getUserInfo())

    # update LASTCOMPDATE

• Use accurate Job Plans for reliable scheduling (SCHEDSTART / SCHEDFINISH).

🆚 MAS 9:

• Both Jython and Python 3 scripts are supported.
• Automation Policies allow low-code event-based automation.

8. Useful Queries

SELECT p.pmnum, w.wonum, w.status, w.statusdate, w.actstart, w.actfinish,

       p.nextduedate, p.lastcompdate

FROM workorder w

JOIN pm p ON w.pmnum = p.pmnum

WHERE w.origrecordclass = 'PM';

🆚 MAS 9 REST Equivalent:
/oslc/os/mxpm?oslc.select=pmnum,nextduedate,lastcompdate&lean=1

Conclusion

Consistency between PM and Work Order date fields ensures reliable scheduling and effective preventive maintenance.
In Maximo 7.6, logic relies on Cron Tasks and local scripts.
In MAS 9, the same functional logic is enhanced through an event-driven microservice architecture, enabling faster and more reliable updates.

✅ MAS 9 modernizes without changing the core:
same functional model, improved reliability, and near real-time updates.
PMWoGenCronTask remains the process backbone, while event listeners provide optional real-time responsiveness for advanced environments.