Explanation of resource group planning rules

Earliest Completion - Use this rule to select a resource that will finish a task "Soonest". This takes account of the current load on the resources as well as any setup that will be incurred due to other tasks on the plan.The sequence number in the resource group is used to determine which resource will be chosen in the event of a tied result. Multiple resources can have the same sequence number.

Minimize Setup Unless Late - Use this rule to select a resource for a task that minimizes setup unless the task is late. Note that this uses the task deadline. When the setup is tied, and the tasks are not late the rule chooses the earliest completion for the task. When the setup is not tied, the rule chooses the resource that will minimize setup. When the tasks are late, the rule reverts to earliest completion irrespective of sequence

Preferred Resources Unless Late (With Earliest Completion) - This rule is void because it only allows for a single preferred resource and replaced with rule 6

Preferred resources unless late with minimum setup - This rule is void and replaced with rule 7

Minimize setup - Appears to minimize setup, then Earliest completion, then sequence number

Preferred Resources only with Earliest Completion - Some customers only wish to plan to Preferred Resources and wish to have other options in the resource group for drag / drop. We would expect this rule to only plan to preferred resources and to choose the preferred resource that produces the earliest completion. This rule now allows for multiple preferred resources. Prior to Orchestrate version 7.58 this rule was not working properly.

Preferred Resources only with minimum setup - Some customers only wish to plan to Preferred Resources and wish to have other options in the resource group for drag / drop. The rule chooses from the preferred resources and chooses the resource that minimizes setup. It allows for multiple preferred resources

Earliest Completion with Rotate Resource Group - This rule attempts to balance the workload on the resources by rotating around the resources. This allows more than one preferred resource, If a task is unplanned and re-planned using this rule it will most likely land on a different resource because the rotation sequence will be different at the point of planning.

Rotate preferred resources unless late with earliest completion - This rule attempts to balance the workload on the resources by rotating around the preferred resources. Allows more than one preferred. Rotates around the preferred resources. If a task is late it chooses a non - preferred resource based upon earliest completion. If a task is unplanned and re-planned using this rule it will most likely land on a different resource because the rotation sequence will be different at the point of planning.

Campaign within the day - Where a customer wishes to create a batch of orders on the same resource unless the batch goes into a different day. These "Campaign within …" rules were designed for a customer to choose the same machine and build a block of work unless the work planned outside of a day, week or month. If the task is beyond a day it will choose a different resource. In code it is called Minimum Setup within day. The tasks must have a setup for the campaign rules to work.

Campaign within the Week - Where a customer wishes to create a batch of orders on the same resource unless the batch goes into a different week. unless the batch goes into a different week. In code it is called Minimum Setup within Week

Campaign within the Month - Where a customer wishes to create a batch of orders on the same resource unless the batch goes into a different month. In code it is called Minimum Setup within Month

Select Resources

Resource Groups

Click Edit

Click New Row