If you set up the PM jobs on a schedule (like every 6 months) the jobs are automatically created in the request queue waiting for you to approve and firm schedule. Once scheduled, time is blocked out in the schedule. Not too bad.
Greg
If you set up the PM jobs on a schedule (like every 6 months) the jobs are automatically created in the request queue waiting for you to approve and firm schedule. Once scheduled, time is blocked out in the schedule. Not too bad.
Greg
Hi all,
I am wondering how other people are scheduling times that machines are down for maintenance or other tasks which you need to make visible to schedulers.
I have RIGS that I need to schedule build times and testing but cannot think of a simple way to do it other than creating a job for 'Testing' for example and then creating an operation against the resource and blocking off some time. That works ok if for one machine, but then for the other 22 RIGS do I create another 22 operations and then when you schedule a new op it will move all the other operations to match the sequence of the new op.
Driving me mad to say the least!
Does the Maintenance module help with this problem?
Thanks
Andy
Yea, it's definitely not a friendly module, especialy with multi-plant. You can however set up a scheduled maintenance (PM) job as a template with an operation using one of the machines. If you then define that template job as the PM job for let's say 10 other similar machines, the PM jobs that get created for each of the 10 machines will automatically adjust to the correct machine resource.
Greg
Thanks Sent from Yahoo Mail on Android
|