Nested maintenance is a function of iterations designed for tasks that are cyclical. An example of this type of maintenance can be found in vehicles, since certain activities are performed repetitively according to the mileage travelled, and some of these tasks may overlap.
This is why nested maintenance is able to determine in which part of the cycle of a task, each subtask should be executed and thus have a better control of the complete maintenance cycle.
This functionality is not only limited to the execution of tasks, but also allows to configure the resources to be used, depending on the iteration that is executed in the maintenance cycle.
How to implement nested maintenance?
-
Before implementing nested maintenance, it is advisable to map out the repetitive tasks that occur throughout the maintenance plan of interest.
-
After identifying the repetitive tasks, the next step is to extract the frequencies associated with these tasks and organise them in a preferred way, ideally from lowest to highest. This process allows for an ordered view of the different frequencies present in the maintenance plan. In a tabular format, we could represent this step as follows:
-
In the third step, a common factor is identified between the frequencies with which the maintenance plan is carried out, following the example mentioned above. In this context, the common factor identified is 50 hours, as it is a divisor of both 250 hours and 500 hours (usually the minimum frequency).
-
In the fourth step, the maximum frequency of actions is divided by the frequency identified as the common factor. Following the previous example, the operation 500 hours (maximum frequency) divided by 50 hours (frequency identified as the common factor), in this case is 10. The result of this division represents the number of iterations, which must be incorporated when scheduling maintenance tasks in Fracttal One.
-
In the fifth step, we proceed to determine which type of iteration corresponds to each frequency. Following the previous example, the frequency identified as the common factor, in this case 50 hours, is taken and divided by each of the frequencies identified in the maintenance plan. In this way:
-
In the sixth step, the iterations in which each action should be repeated are assigned. Following the example above, for actions with a frequency of 50 hours, they should be carried out in iterations 1 (corresponding to 50 hours), 5 (corresponding to 250 hours) and 10 (corresponding to 500 hours). In the case of actions with a frequency of 250 hours, they must be carried out in iterations 5 and 10. Finally, for actions with a frequency of 500 hours, they must be carried out exclusively in iteration 10. The recurrence of these actions is the one that is selected in the maintenance plan from Fracttal One, directly from the corresponding subtask.
Note: In the case of managing resources and supplies with their respective frequencies, the same steps as above must be repeated for each of the elements to be used. In this way, global and coordinated planning of all activities is guaranteed, taking into account both the actions to be carried out and the resources and supplies associated with the respective frequencies.
For more information, you can consult these articles:
