Additive (Cumulative) Job Plan Sequencing for Preventive Maintenance

Problem:

Maximo PM job plan sequencing currently selects only one job plan per PM generation, using this rule:
The job plan with the highest sequence interval that evenly divides the PM counter is selected.

This exclusive selection model prevents correct execution of overlapping maintenance cycles (e.g. annual, biennial, triennial maintenance on the same asset). Lower-interval maintenance is skipped whenever a higher interval takes precedence, resulting in irregular and unintuitive scheduling.

Customers are forced to duplicate tasks across job plans, create multiple PMs per asset, or implement custom logic.

Current Behavior:

PM frequency: 3 months

Interval and intended maintenance 1       3 Months
4       12 Months
8       24 Months
12     36 Months

Maximo selects exactly one job plan per cycle.

Resulting behavior:
1-year tasks occur at 12..60... 84....132… months (irregular every 4 years then 2 years). 2-year tasks occur at the opposite irregular frequency i.e. 24, 48....96, 120 month (every 2 years then 4 years).  This is mathematically correct but operationally inconsistent with real maintenance programs.

Desired Enhancement:

Add an optional PM-level setting such as: “Additive Job Plan Sequencing” (Yes / No)

When enabled: Increment PM counter (unchanged) Include all job plans tasks where PM Counter MOD Sequence Interval = 0, i.e. where the pm counter divided by the sequence number leaves no remainder. The generate a single work order using the tasks from all Job Plans where this true, using the lowest sequence job plan first then adding in ascending order to create the work plan.

Example:
Using our example PM sequence above - At 72 months (counter 24), include 3-month + 1-year + 2-year + 3-year work.

Benefits:

• Correct execution of overlapping maintenance cycles
• Eliminates task duplication
• Improves predictability and auditability
• Reduces need for multiple PMs or custom logic
• Fully backward compatible (opt-in)