16
On production order scheduling, if there's multiple resources that meet the same requirements and have the same best available time slot, scheduling selects resource with alphabetically smallest resource-id.
If the load is less than 100%, work will be split unevenly between resources; smallest resource id has high load and resources with high id will have smaller load.
In healthcare, where healthcare professionals are seen as resources, this kind of uneven splitting of work load is an issue.
Proposal: New parameter for "Random selection" to be used in Scheduling. If the new parameter is selected, and if in production order scheduling there's multiple resources that meet the same requirements and have the same best available time slot, from these resources choose the resource randomly (not alphabetically).
If the load is less than 100%, work will be split unevenly between resources; smallest resource id has high load and resources with high id will have smaller load.
In healthcare, where healthcare professionals are seen as resources, this kind of uneven splitting of work load is an issue.
Proposal: New parameter for "Random selection" to be used in Scheduling. If the new parameter is selected, and if in production order scheduling there's multiple resources that meet the same requirements and have the same best available time slot, from these resources choose the resource randomly (not alphabetically).
STATUS DETAILS
Needs Votes
Comments
SInce I can see no workaround, I think this idea really deserves a lot of votes, as always selecting smallest resource ID barely serve any purpose
Category: Planning