Resource Groups from multiple sites on same operation

We are moving a few production lines into our new site. As I’m preparing to set up all the BAQs and DMTs that will be required, I have a question about operations.

Scenario:
Our part has an operation that was originally setup in Site A but is going to be moved to Site B. It currently has a resource group from Site A. I have noticed that if I add an additional resource group to the operation (from Site B), it appears to only use the resource group from the site that the job is in. Is this acceptable? Or should I create entirely new operations with independent scheduling resources? My main concern is that there are probably some assemblies that may continue to be manufactured in Site A and if I can get away with the same operation, it makes setting up the Alternate Method a little easier since there wouldn’t actually be any work required in Engineering Workbench.

Does anyone have advice/feedback/gotchas that I may not have found yet?

If you look at the OpMasDtl table, you will see that there is actually a Plant field there. That ties to the Resource Group/Resource/Capability and controls what Scheduling Resource defaults when a user is creating the MOM. If you are in Site A building a MOM, it will default to RG A. If you are currently in Site B, it will default to RG B.

You are able to change it on the MOM, so if you want a certain Operation to go to RG B while you are in Site A, you can change it.

I would recommend doing one Operation with multiple scheduling resources as (I believe, you would need to double check) you cannot have the same ID/Name for scheduling resources across Sites. That is, you can’t have both Sites with a RG Description of Machine.

1 Like

That’s the direction I’m leaning. Thank you!

1 Like