67
In the current Operations resource model, it is not possible to plan for shifts, as a job cannot be split by shifts (Often the worker is the secondary resource on a machine resource, what makes it even more complex). The consequence is that you have to set up "Generic" worker resources, that have not worker assigned but just represent the worker required on a specific resource or resource group.
In essence, this actually may work well for master planning, but the Shopfloor supervisor needs to have a dispatching / shift-planning instrument at his hands, where he can see the required times (how much is the generic resource loaded?) and dispatch the tasks of the generic resource to specific resources.
Technically, this might be something to use the Scheduling board from professional services - but we need to make sure that we are not making Shopfloor resources more expensive (falling into different license terms).
Warehouse and Quality supervisors have a similar problem, but the definition of the work ahead is different and not related to a resource model. Still would be good to have a generic solution, as for example waterspiders might be loaded with production AND warehouse work.
In essence, this actually may work well for master planning, but the Shopfloor supervisor needs to have a dispatching / shift-planning instrument at his hands, where he can see the required times (how much is the generic resource loaded?) and dispatch the tasks of the generic resource to specific resources.
Technically, this might be something to use the Scheduling board from professional services - but we need to make sure that we are not making Shopfloor resources more expensive (falling into different license terms).
Warehouse and Quality supervisors have a similar problem, but the definition of the work ahead is different and not related to a resource model. Still would be good to have a generic solution, as for example waterspiders might be loaded with production AND warehouse work.
STATUS DETAILS
New