Question on inactivating Resources within Resource Groups


(George Hicks) #1

Hello All;
We have Resource Groups that were established long ago, and someone created 20 or so Resources within those groups. Example, we have a Resource Group called PACKAGING and then resources under it, PACK1, PACK2, PACK3…

We are just now getting into using the scheduling functions better and I would like to inactivate these Resources since we cannot delete them.

What is the best way to do this?
There are active Jobs that have these Resources on the Operations, so if I inactivate the Resource, what happens to these Jobs?
Do I need to modify All Jobs to use the Default Resource in the Group PACK1, via a UDASH?
If I just inactivate all the Resources I don’t want, could I just do a Global Reschedule and the Jobs will see no Resource and default the operations to PACK1 or will this cause an “Invalid Resource” error. I have see than error in testing.

Any guidance appreciated, from someone who has set a Resource as Inactive.

Regards,

George Hicks
Visionalire Lighting


(Rye) #2

You need to change the scheduling resource for any open job, especially if you are running MRP, before you inactivate the resource. If you run MRP and have resources for an open job that are inactive, it will hang up MRP. You should update your methods as well.


(Andris Skulte) #3

George - Why not set the operation to use the resource group only, both on active jobs and on MOM’s (for future jobs that MRP would create)? And let those resources sit in the resource group until they’re needed down the road?


(James McKinnon) #4

Having recently done this having appeared to have successfully tested in a test instance without thinking it fully through, causing the MES to do a massive “computer says no”, and then having to manually reschedule lots of jobs to use active resources a few things to note

  1. It is dependent on how you have configured scheduling, if you just schedule based on the resource group as Andris suggests, Epicor will typically try and fill resource 1 and then fill resource 2 on any given day in resource alphanumeric order - so in theory if you have pack 1-20 and the load never fills any more than pack 1-15 - you can make pack 16-20 inactive without issue. If you do a query/baq on the resourcetimeused table you can see what open load is against each resource - if a resource has no load and is not specifically called out on production route then you should be able to make it inactive without impact on released jobs.
  2. To get an idea of whether a resource is specifically called out on a production route/mom do a query/baq on the partopdtl table - you could then identify any route with that resource and use the DMT to mass update and replace with a resource that is still active
  3. Another way of doing this is a more staggered and cautious approach is to do step 2 and then decide when you want the resource to become inactive and as an example on that resource put two weeks worth of non working days in that resources calendar from that date. This means E10 will not schedule any work against that resource on those days, and once you hit the period you entered non working days for, check that there are no remaining open jobs using that resource, and can make it inactive. Two weeks is an example, it really depends on how far you/MRP plans and releases work.
  4. Assuming you have a small number of active jobs and you have done step 2 you can ignore step 1 and step 3 and just make the resource inactive - then run a query against resourcetimeused for the inactive resources with current jobs - use that query as a list of jobs that you need to manually reschedule within job manager/entry - you might need to run on the ability to schedule in the past in company/system config (can’t remember which) if the original job start is in the past and you wish to keep the integrity of that - for example an overdue job.

From bitter experience, as our system is configured global rescheduling does not fix making an active resource with load resource inactive - there may be some other config that does allow if to fix this.


(Dean Chamberlain) #5

There is a menu option under Engineering > General Operations called “Mass Resource Group Replace.” I don’t know if that will be helpful. I thought we used it for the resource, but now I remember we were changing resource groups. I hope it helps some when you’re trying to change the method master. We call them BOMs but I think a MOM is the same thing.