Planner has five resources, one of which is seasonal, and they have stopped using the seasonal resource. However, Orchestrate is now planning on this resource, following an upgrade.
Certain tasks are planning onto the wrong resource.
After a new Orchestrate database has been created, with the latest dataflow, lots of tasks are planning to a single resource.
Solution 1
If the Gantt Chart doesn't draw the task on the relevant resource when the Application Type has been set to Required For Setup+Work. It seems that the task has been drawn on the resource underneath the resource where it is allocated. The planning logic in Orchestrate version 7.77 now prevents you from combining Required For Setup Only/Required For Setup+Work (left hand pane edit tasks, resources tab) with a Same Resource dependency from a Predecessor task (in exactly the same way as we now prevent them entering/importing a setup time or Use Setup Table on any Task that has a Same Resource dependency from a Predecessor.) This prevents it from drawing on the wrong Gantt Chart row. Please upgrade to Orchestrate version 7.77 or above.
Solution 2
Check the works order is actually planned from the order planner (i.e. no black square in the planned checkbox) and the routing for the manufactured part is correct in FactoryMaster. If the routing is fine, you need to delete any duplicate resource groups via the following steps:
Log into Orchestrate
Select Resources
Select Resource Groups
Clicked Edit
Highlight relevant resource groups and click Delete Row(s)
Solution 3
You may also have unnecessary resources added to a machine or labour resource group, that need removing to correct the sequence the planning logic will use when planning tasks. Below are the steps to amend a machine resource group (these resources will also need to be made redundant from FactoryMaster via Resource Maintenance):
Log into Orchestrate
Select Resources
Select Resource Groups
Clicked Edit
select relevant resource group
select relevant resource
click remove resource(s)
Check all relevant shift patterns have been assigned to the correct resources, for the correct days via the following steps:-
Select resources
Default Shift Pattern Assignment
In FactoryMaster, check the relevant resource groups have been created and the relevant resource is added to the relevant resource group via the following steps:-
Select production
Resource Maintenance
Solution 4
Check you are using the correct data flow option when importing from FM to Orchestrate e.g.
Option C1 - Alternative Resource Groups, Associated Labour, No Tooling
Option C3 - Standard Resource Groups, Associated Labour, No Tooling
Then, upgrade to FactoryMaster sub version 12.14.11 or above, to prevent the sequence numbers of multiple resources assigned to a particular resource group, to be overwritten during the data import. The sequence number defaults as number 1 because of the Resource Group Items view on the FactoryMaster (FM) database. In Orchestrate, the resource groups items can have the same or different sequence numbers; so having them all set to 1 would be valid if the resources all had the same priority. The problem is initially the imported sequence numbers are all 1, as that's the data we are receiving from FM; When you change the sequence number in Orchestrate, and then perform another import, the sequence numbers are overwritten. The expected behaviour is that the sequence numbers they have entered into Orchestrate should be preserved, not overwritten by the 1 being received from FM on the second import. Stored procedure pr_Merge_orc_ResourceGroupItems, which is responsible for merging the resource group items contains the following logic:
If the sequence number received from FM is NULL and a Sequence number already exists in Orchestrate, then preserve the Orchestrate value.
If the sequence number received from FM is NULL and a Sequence number does not exist in Orchestrate, then set the Orchestrate value to 1.
If the sequence number received from FM is NOT NULL, then set the Orchestrate value to whatever we receive from FM.
Our development team changed the vOrcData_ResourceGroupItems_1_NoLabour view to do the following:
If the sequence number is not known, then select NULL as SequenceNumber
If the sequence number is known, then pass that
If the issue persists, please check the Required By date in FactoryMaster is correct for the relevant works orders. This date is used by the resource group planning rule, when planning the works order in Orchestrate.
If the issue persists, please check the Required By date in FactoryMaster is correct for the relevant works orders. This date is used by the resource group planning rule, when planning the works order in Orchestrate.