Follow

Configure a Time Based Nested PM

Overview

This article will demonstrate how to create a time based nested preventive maintenance. Nested planned maintenances, or nested PMs, permit structured scheduling of maintenance events that are dependent on other events. To set up maintenance tasks that are periodic, and tied to another event, a user is able to specify the parent event, and the occurrence of the other child events. The events occur at specific intervals.

Note: This feature is not compatible with multi-asset scheduled maintenances

When setting up nested PMs, the next PM event is assigned a multiplier of the first PM cycle. For example, if the first PM is weekly, an annual PM happens every 52 weeks, so it has a multiplier of 52. Similarly, in this example, monthly maintenance would have a multiplier of 4. 

PM Cycle Multiplier
Weekly 1
Monthly 4
Quarterly 13
Annual 52
5 Year PM 260 (52 x 5)

Important Note about Nested PMs

The Nested PM feature comes standard with the professional and enterprise packages. If you already have one of these packages, you'll notice the new Nested PM tab on your scheduled maintenance. Not every scheduled maintenance is a nested PM so you can ignore the nested PM tab if you are building a traditional, non-nested scheduled maintenance.

Setting up a time based Nested PM

  1. Follow the procedure to set-up a single asset scheduled maintenance. Configure your trigger to be the lowest interval in your nested PM. In this example, the base interval is one week. 
    SM_w_Start_Time.png
  2. Next, select Nested PM. This is where the nesting levels are configured. Click on the default nested level, and add description into the Summary of PM field. Nested PM functionality assumes that the organization combines all tasks from the more frequent cycles, into less frequent cycles. For example, monthly PM tasks are included in the final annual PM task list.
  3. Click Add to add another nested level
  4. Add a Summary of PM, select the Parent, add a Multiplier, and click OK. The N1 code is always the base level, with an interval defined by the scheduled maintenance trigger. All nested events are a multiplier of the base level. In the following example, ordinarily months can have up to 31 days, but in this case, we are going to perform the monthly PM every 4 weeks (28 days). 
    3.png
  5. Repeat the process for other the levels
  6. Next, select Labour Tasks to assign the tasks to each level. To assign an individual task to a level, select the default task.
  7. Enter the task details, select the nesting level from the dropdown menu, and click OK
  8.  To assign a task group to a nesting level, first create the task group, and select New. 
  9. Select a task group
  10. Assign the task group to a user, select the nesting level from the dropdown menu, and click OK
  11. Assign the remaining tasks to the nesting levels.
  12. Next, the Nested PM start point needs to be configured. If the scheduled maintenance is triggered now, it will trigger at the start of the cycle which is a weekly PM. To change the starting point, select Nested PMs, and Change

    Let's say the next PM is the 3rd Quarterly PM. The starting iteration needs to be adjusted to the 39th week of the cycle (the 3rd quarterly pm happens on the 39th week)
  13. The Time Based Nested PM is complete. Activate the scheduled maintenance as normal by clicking Paused

 

Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request

Comments