Looking at it for co-parts and job batching. How are other people using it? It seems a little expensive just for co-parts.
Job batching is poor in Epicor and needs work, the co part functionality is good, but you can only realise the co parts at the last op. For example a job with four ops, laser, fold, weld paint.
if some of the parts are just lasered, you only get the option to receive them after paint, rather than after laser.
So in a situation where a bunch of parts are nested together for plasma or laser, but they go to different ops after (e.g some to welding and some to machining), would job batching work out well or does it have the same limitation as the co-parts?
I guess it depends on what you think is the right process.
my idea of job batching is i have four jobs, all lasered then go off on their merry ways.
you batch the first op, all material linked to the first op and times are amalgamated onto a new batch job with co parts for all the parts.
All parts are nested then lasered then received back onto their respective jobs.
Epicor doesn’t do this and closes all the jobs bar one where all the materials have been moved to. We have been looking into doing something ourself, but never got round to it.
So if I am understanding right, it sounds like batching only makes sense the way they have it if its the last operation… I wonder if you could sort of work around this by making a sub-assembly for the material that gets nested and make jobs for that to batch?
You would have to test, i have never tried it with a multi level assembly
I don’t actually have the module. Wasn’t sure it was worth it
I have been able in our test environment to batch laser jobs together of the same material. That then went to different operations such as blast, bend, roll, machine. You have to make sure you select the right direction for the batch, it defaulted opposite of what we needed. The other thing is figuring out how to distribute the material and labor time between the different parts. It will default to an even split if I remember correctly so I created a tab to sum the total material usage and give a ratio for each parts usage. When the laser operator would close the operation, they would do so in co-parts instead and claim the quantity of each part made. This would close the batch job and close the first operation on the individual jobs if I remember correctly. They would then show up for their next operation. It has been a long time since I looked at it but that is what I remember.
That is not my experience. When I have batched the laser operation, it creates a new Job and when that Job is done, it pushes all of the material back to their original jobs.