How to Avoid Duplicating PM Work Orders?

We have seen cases that customers have duplicate work orders for preventive maintenance for the same PM Plans and assets. Calem recommends "Floating" release type for high frequent PM work orders. The "Floating" release type prevents Calem from generating PM work orders if there are open PM work orders. Here is the notes of "Release type":

• PM release type can be a) Fixed; b) Floating; or c) Other. It is defined at PM Plans.
• The "other" type will not be used in generating work orders from PMs. It is used to define a job template that is not PM.
  
• Floating type scheduling will not generate a work order from a PM if there are open work orders from this PM.
  
• Fixed release type will generate a work order from a PM whenever it is due regardless if there are open work orders from this PM.
  
• For time based PMs with time intervals less than a week or so, and there is no regulatory requirements of fixed time maintenance, "Floating" PMs may be used to avoid duplicate work orders. For instance, a daily work order for machine inspection might be configured as a "Floating" release type.

1. Weekly Floating PMs

A weekly or weeks floating schedule can be accurately implemented by a) "Every XY weeks"; or b) "Every 7*XY days". See screenshots below. 

• When a work order of a floating PM is completed, the next due date of the PM is calculated by "1" week or "7" days. 
• The weekday "on Monday" of the weekly schedule "Every 1 weeks on Monday" is ignored.
• Do not use "Weekly" (this first option of the repeat schedule). The "Next due date" is adjusted by the checked week days. For instance, a weekly PM is set to every Saturday, a job is completed on Tuesday, the next due date is this Saturday even with floating release type, instead of coming Tuesday.

2. Monthly Floating PMs

A monthly or months floating schedule can be accurately implemented by a) "Every XY months"; or b) "Every XYZ days". The day portions of the monthly schedule (Every XY months on Day of Week, or Day of Month) are ignored. For instance, a monthly floating PM (Every 1 months on Day of month 1) was completed on the 4th of January, the next due date will be the 4th of February.

 3. Floating PMs by Days

As shown above you can use "Every XYZ days" as a repeat schedule to implement maintenance schedules by days accurately for floating release type.

Additional Resources

• How to Implement PM Checklist
• Asset Module Training
• PM Module Training
• Work Order Module Training

• User Guide and Admin Guide (customer account required)
  
• Calem Enterprise Training Site
  
• Calem Enterprise Blogs
  
• Calem Enterprise demo