Hi all. We started sequencing PMs a couple years ago and have had some eye openers, like an annual WO kept open for several months waiting for parts, so the monthly maintenance WOs were not generating. Our second eye opener just happened. An asset was not cleaned at the scheduled time and it overheated and burned up. Here's what happened. For simplicity, the asset has a 1 (inspect filter), 6 (clean filter), 12 (replace filter) month sequenced plan. At month 9, when the monthly came up they decided to do the full 12 month maintenance. When the 12 month came up, they indicated that it was already done at month 9 and closed the WO. (That should have been a flag to get us involved, but they didn't.) The 6 month needed to appear six months after the last 12 was actually performed, meaning we needed it to come up at month 3 the following year. However, following the sequence, it is not scheduled to come up until month 6. Between month 3 and 6, the asset failed because it did not get a much needed 6 month cleaning.
The only 2 options i can think of to address this is they submit a ticket for me to alter the PM schedule whenever to do anything out of sequence; or at month 9, they pull forward and generate 3 more WOs to get to the 12 month WO and then cancel the four monthly WOs.
The first option relies on them remembering/knowing to submit a ticket. The second option seems complicated to figure out exactly how many to pull forward, what day or date to put in generate WO window, and I can see causing more 'clean up' on my end if it isn't done correctly. It doesn't happen often so everyone's memory on what to do will be rusty at best.
Is there a better way?
Thanks!
#WorkManagement------------------------------
gail smith
chevron
------------------------------