first… remember that even if you have 10 resources, it will only schedule the FIRST resource in the list for ALL jobs, UNLESS you do Finite Scheduling. It is the finite scheduling that forces the system to choose from available resources.
With Finite, it will first schedule one resource, and then the second job that comes along needing a resource from the resource group will select the next one in line, etc., until all the resources are consumed, then it will use the next avialable time slot for the next resource.
To “Prioritize” which resource is chosen, you need to use another feature that works really well, but takes more setup. You can use the “Capability” feature:
- define a capability (Assemble Level 1).
- define which resources can do this capability. Within this you can also set the sequence for each resource to be consumed. Example: if you have level 1, 2, and 3 assemblers, (each with more talent), you can tell the scheduling system to use the level 1 assemblers first before using 2 and 3. Even though a level 3 can do level 1 work, you want to use up the level 1 first. Note that you can also specify the efficiency that each resource has when doing this capability… for example, level 3 assembler might be 10% more efficient.
- define the same for level 2 and level 3… but obviously, only level 3 assembler resources would be in the level 3 capability.
- LASTLY, you need to change your BOM/BOO so that the operation points to the CAPABILITY instead of the RESOURCE GROUP. This allows the capability to work.