Need ( 20 ) jobs of qty ( 25 ) , setup a job for qty 500 and used the split job function to split out qty’s of 25. The job creation works fine, but does not release the jobs…is there anywhere to release these jobs without having to go back into each individual job and release?
Job Status Maintenance is what you use for mass job releases.
I’d also look into setting a max lot size on your part and having MRP pre-split your jobs when it runs.
5 Likes
Job Status Maintenance can be used to release the jobs, but how do I get them all scheduled? We are not yet running global scheduling. Is there an option to schedule a list of jobs without running global?
If you’re not using global scheduling, then you have to A) accept wherever MRP dumps them in your schedule when it creates the job B) Have someone manually move jobs around on the scheduling boards.
Both options are, in my experience, insane. Yet I have had multiple schedulers try to do B) in my time here. In every case they simply couldn’t keep up with it. Eventually management got tired of the nonsense and we agreed to just move to GS, which has been a big shift. Mainly in mindset. You mark a job as hot and let the system move it up rather than moving rectangles around.
1 Like
That sounds awesome! We aren’t even at the point of having MRP working yet. Right now our engineer schedules the job when he releases it. Since we didn’t really care about the date that it gets scheduled for, we haven’t looked at this field in the past. I think this point might be moot. We had headed down this path when we were considering splitting a job that already had labor applied. Now we are thinking we want to split the job in Epicor before we log any labor. Or at least, not log labor against the top job when the work is done on the split job.
Have you tested it yet?
I’m not sure this is realistic. You’re aerospace. You’re going to be splitting jobs after it hits the floor because life happens and you still have to maintain traceability. SubCons short ship. Parts need rework.
This is also going to be a scheduling issue since Epicor assumes an entire job is moving in lock-step together. If some fraction of the lot is out of sync with the rest, it should be split and scheduled accordingly UNLESS you know it can catch up before the last op.
Basically, prepare for both eventualities.
2 Likes