We run wheels as well but the exact sequence doesn't sound as critical as yours - so we don't lock our job schedules.
Â
Putting my materials/operations hats on, I'd see value in showing jobs late (and working on internal processes for recovery & remediation on future wheel runs so it occurs less and less frequently) - You can't schedule your way out of operations problems.
Â
In lieu of that, if each part in the wheel shares very common methods, try a single multi-part job (and if they don't, perhaps try combining your jobs into a single batch job). That would enable you to NOT lock the schedule & it would self adjust (presuming you run the global frequently) to above and below std output.Â
Â
Rob Brown
________________________________
From: lilj8069 <lilj8069@...>
To: vantage@yahoogroups.com
Sent: Thursday, March 21, 2013 12:14 PM
Subject: [Vantage] Job Scheduling Issue
Â
We have a somewhat unique job scheduling issue. On a particular resource, we have approximately 15 jobs (parts) that need to run on this resource every month. The jobs need to run in the same order every month and some months, based on on-hand qty's, we will skip some jobs (parts) altogether. The jobs are created in a make to stock fashion and need to run in the pre-defined order regardless of the sales order dates that are entered throughout the month.
We can manually schedule the jobs at the beginning of the month and lock them in the schedule, but then variations in production don't get taken into account and we end up being past due on the jobs instead of having them automatically moved out based on what we've run. We are currently manually moving the jobs out, but there are about 325 different parts on 10 machines so it's very time consuming.
We call this process running the wheel as once we get through the set of parts, we start over from the beginning. Does anyone have a similar situation they've been able to work through that could offer any advice on this issue? We've really been struggling with this for some time.
Thanks,
John Kreger
[Non-text portions of this message have been removed]
Â
Putting my materials/operations hats on, I'd see value in showing jobs late (and working on internal processes for recovery & remediation on future wheel runs so it occurs less and less frequently) - You can't schedule your way out of operations problems.
Â
In lieu of that, if each part in the wheel shares very common methods, try a single multi-part job (and if they don't, perhaps try combining your jobs into a single batch job). That would enable you to NOT lock the schedule & it would self adjust (presuming you run the global frequently) to above and below std output.Â
Â
Rob Brown
________________________________
From: lilj8069 <lilj8069@...>
To: vantage@yahoogroups.com
Sent: Thursday, March 21, 2013 12:14 PM
Subject: [Vantage] Job Scheduling Issue
Â
We have a somewhat unique job scheduling issue. On a particular resource, we have approximately 15 jobs (parts) that need to run on this resource every month. The jobs need to run in the same order every month and some months, based on on-hand qty's, we will skip some jobs (parts) altogether. The jobs are created in a make to stock fashion and need to run in the pre-defined order regardless of the sales order dates that are entered throughout the month.
We can manually schedule the jobs at the beginning of the month and lock them in the schedule, but then variations in production don't get taken into account and we end up being past due on the jobs instead of having them automatically moved out based on what we've run. We are currently manually moving the jobs out, but there are about 325 different parts on 10 machines so it's very time consuming.
We call this process running the wheel as once we get through the set of parts, we start over from the beginning. Does anyone have a similar situation they've been able to work through that could offer any advice on this issue? We've really been struggling with this for some time.
Thanks,
John Kreger
[Non-text portions of this message have been removed]