Looking to see if I’m barking up the wrong tree on this.
We have some jobs that have a handful of parts where material can saved by burning them as a single nested part, rather than individual parts on a plate (think a ring, inside of a ring, inside of a ring, etc…) However these rings are on separate parts of a BoM, so we would like to combine them to burn from a single nested part number/drawing, and split them back off into their separate parts on the job. (We’re also using NESTLink to generate burn table work-orders - modifying those work-orders too much will break the data returned from ProNest to NESTLink,
Thinking that Co-Parts might be the right solution here, and that a BPM could be written such that at ‘Job-Released’ set to True, it would scan through the job looking for Co-Parts ‘children’, and if all of the family are there, then prune the material/labor from the main job and create a stock job for the Co-Part parent to feed those demands (job-to-job demand links generated in stock job as well).
Am I totally off base, or is this an acceptable use case?
@LarsonSolutions - we are licensed for Advanced Production Module, so no worries there. We tested a Co-Part in our sandbox to verify that costs went where we wanted them to go - just wanting to see if that’s the route we should follow. The child parts are on separate assemblies, making different complete parts for a couple different assemblies on a single job. We would to remove the material and labor from the children, and allow a linked stock job to produce the parts from a single nested burn drawing (because NESTLink/ProNest issues).
Trying automate this to reduce workload of the person creating the job and relying on them to know that the Co-Part exists.
I feel that I’m capable of writing the code to accomplish the task, just want to see if I was totally off base with the theory, or if there was another/less user intensive solution.