I am learning how to use co-parts. I am wondering what is the part type or source type that the co-parts should be? I would think Manufactured… but they don’t have a method themselves… I’m troubleshooting because I ran MRP and I am not seeing job suggstions for the co-parts (or even the main part with the method structured to it). I thought maybe I need to set them up a certain way.
All co-parts that we use have are manufactured and have their own method.
Thank you. So if parts A and B are co-parts, then I would setup both A and B with a method and each would reference the other as a co-part? Do I understand that correctly?
No, you cannot have a circular logic like that. We setup A and B and then add B as a co-part of A.
You can then setup a relationship between A and B on A’s method that indicates how many As and how many Bs you get depending on the situation. It is an integer relationship so it does have to be a whole number. You also indicate if it is sequential or concurrent processing on the method.
If it’s not that consistent or you want to be flexible on your combinations, you can alternatively do a batch job.
So Part B will just have a method that consumes the same materials as though no co-parts are made?
For our use case, the parts share the same sheet of material.
YS2261 = Part A
YS2262 = Part B
We can make YS2262 separately but for every sheet we put up for this operation we get 23 YS2261s and 9 YS2262s. These are setup as concurrent co-parts because we make both at the same time within the same cycle of the program. Noting that the method of manufacturing details are setup for 1 YS2261 and that we use standard cost.
We have another operation that uses nesting to determine based on demand which parts we are going to make at the same time to optimize our sheet usage. For that use case, predefined co-parts doesn’t work so we will be using batch jobs.
Your explanations have been helpful. Thank you.
I was playing around with it and I came up with a question. I see the circular logic reference you spoke of. As an example, I ended up with multiple jobs which essentially doubled up what I needed. But my question I was trying to answer is:
Suppose Part A and Part B are both needed in an assembly. 1 of Part B is damaged and scrapped. Thus, a new job is needed and you will get 1 of Part A and 1 of Part B. But now you’ll have an extra Part A. How do you tell MRP that you want to use the lower of the co-parts as the basis for determining when to build a job?
The reason I’m questioning this is that we have a different scenario than what it’s probably intended. Our supplier is our customer and they want to sell us 1 “kit” of raw materials (their proprietary parts) that are actually 9 separate part numbers (some have more than 1 qty per kit also). So I was looking to use Co-Parts as a way to take their 1 purchased kit and create a job that then breaks the 1 kit into 9 separate co-parts. But it is inevitable that we are going to end up where the count is off for some reason and we will need to trigger to buy kits based on the 1 part that we have the fewest of. I was hoping that by having each part setup the same where the only way you get the 1 part is by also getting all of the other parts that I would achieve that goal. But as you correctly pointed out, I ended up with circular references and it just made a bunch of jobs when all I really needed was 1.
When we end up needing additional part B, we just run them on their own job. MRP is only going to suggest a job with the method information. You can edit in the job the quantities. Unengineer the job and then go to the job quantities in the tab at the bottom of the screen and on the co-parts tab you can adjust the co-part quantities.
OK. So MRP won’t do it is what you’re saying. I would need to take MRP’s suggestion and modify it to fit our situation. I can live with that.
Thanks again!