Strategy Maintenance Plan and Packages

[former_member732650]

Hello,

I wanted to ask your opinion regarding the best strategy proposed for the programming of machines with "concatenated" operations; I mean, when there is a set of operations for a lower preventive maintenance, (in this case the lower level is a weekly maintenance), and in the upper cycle (fortnightly/monthly/half-yearly...) the operations of the lower package are included and the hierarchy level would "override" the lower package.

That is, when I have to do a monthly maintenance, that implies that it contains the operations of the monthly itself and, in turn, of the fortnightly and weekly, and for this reason I want the date to coincide (for example, in the 4th week after the beginning of the cycle) to show said operations marked with a monthly/fortnightly/weekly package in the same order and on the same date.

Regarding the strategy, I have used packages with a daily cycle, the lower unit being the week (7 days) and the higher packages being multiples of this lower one (14 for the weekly (2*7), 28 for the monthly (4*7) , 84 for the quarterly (4*3*7), the half-yearly 168 (4*6*7), for the annual (52*7) (this is where my problem begins), 728 for the biennial, etc.

Doing it this way, with a single position that has a route sheet associated with operations and their respective packages assigned according to the case (weekly, fortnightly, monthly...) the operation by hierarchy and coincident dates in the programming is correct until half-yearly.

However, in the programming, when should the second semester (half-yearly) coincide with the annual one (yearly); these look a few days out of date (packages are not divisible by each other: (annual=364)/(half-annual=168)=2,166. How have you solved this? Have you experienced a similar case? Maybe this is not possible and I must use 2 strategies, one for the weekly and one for the monthly (2 plans for the machine, the weekly/fortnightly programmed independently of the rest of the superiors). It also makes that annual maintenance ("every 12 months") when using the 52-week cycles in this case go up to 13 months.

A strategy with monthly cycles (30 days) and fixed day programming is much more intuitive in terms of programming, however there are machines that require the lower level fortnightly or weekly.

Thank you so much for your opinions.

A cordial greeting.

[Inna_Sitnikova · Accepted solution]

Hello Eloy,

As of my experience you have several options:

1) 1) 1^st option which I prefer the most: adapt all your cycles starting from half-yearly and going further to yearly and bi-yearly, so that each cycle is multiple of previous cycle. Example: your yearly should be multiple of quarterly and half-yearly, your bi-yearly should be multiple of quarterly, half-yearly and yearly and so on. Here is how this strategy could look like:

2) 2) If the maintenance stick to exact dates and cannot be shifted, you may want to play with the offset.

In case you set up an offset for the first five cycles you would get the desired scheduling:

Schedule your plan:

…

However, this method is tricky and you would need to reschedule all your plans each year as the offset would work for the first year only:

3) The option which you already mentioned in the question: have 2 strategies, one for the weekly and one for the monthly. In this case you will still have not exact overlapping: your weekly and bi-weekly strategies will be scheduled separately from monthly/quarterly/yearly/… and you would have two work orders created each time. Example: on 28th day you have your bi-weekly order and on 30th day – monthly one.


Best regards,
Inna

[former_member732650 · Accepted solution]

Hello inna_sitni,

Thank you very much for your detailed response, it was very helpful.

Yes, third option implies 2 orders/plans and I wanted to avoid that one. Second one would be the right approach, but as you said rescheduling would be a nightmare.

First option would be the easier one to maintein, so I will try to make business to accept this one.

Thanks again for your support.

Best regards