Hi everyone,
We are currently configuring a meter-based Preventive Maintenance (PM) process in Maximo and would like to confirm whether the following requirement can be achieved using standard functionality or if customization is required.
We have an asset with a continuous odometer meter (ODOMETRO). The maintenance program must follow fixed mileage milestones.
The first maintenance is due at 15,000 km, and after that, maintenance must occur every 30,000 km:
15,000
45,000
75,000
105,000
135,000
...
The important requirement is that these milestones must remain fixed regardless of the actual meter reading when the PM work order is generated or when the vehicle enters the workshop.
For example, suppose the PM corresponding to the 45,000 km milestone is not generated until the vehicle has already reached 50,000 km.
What we need is:
Scheduled milestone: 45,000 km
Actual reading: 50,000 km
However, with our current meter-based PM configuration, Maximo uses the meter reading at the last work order generation as the basis for the next occurrence.
For example:
Meter Reading at Last WO Generation: 50,000
Frequency: 30,000
Meter Reading at Next WO: 80,000
Therefore, instead of preserving the expected 75,000 km milestone, the schedule is shifted to 80,000 km.
Enabling Generate Work Order Based on Meter Readings (Do Not Estimate) does not appear to change this behavior.
Our requirement is essentially for the PM meter frequency to behave as a fixed mileage schedule, rather than recalculating the next target based on the actual reading at which the previous WO was generated.
In other words:
Required:
15k → 45k → 75k → 105k → 135k
Current behavior if a WO is generated late:
15k → 50k → 80k → 110k → 140k
We also need the PM to become due based on those fixed milestones. It is not sufficient for us to simply store the expected mileage on the generated work order; the PM generation criteria itself should continue to use the original fixed sequence.
- Is there a standard PM/PM Meter configuration that preserves fixed meter milestones?
- Is there a setting that prevents
Meter Reading at Last WO Generation from shifting the next meter reading?
- Would manually/automatically maintaining
PMMETER.LASTPMWOGENREAD or PMMETER.READINGATNEXTWO be a supported approach?
- If customization is required, what would be the recommended extension point: automation script, PM generation logic, or another approach?
We would like to avoid modifying Maximo's PM calculation fields directly unless that is considered a safe/supported approach.
#MaximoApplicationSuite
------------------------------
Francisco Huesca
defalliance
------------------------------