The way I have my model set up currently is there are multiple stations and shifts with different amounts of employees in each shift. Sometimes, the shift does not have enough people to occupy every station, which is as to be expected. However the reaction of the operators is as follows (assume 1 operator and two stations):
Operator picks Part A, puts it on Station A, Operator goes back and picks up Part B, puts it on Station B, Operator goes and works Part A to completion but doesn't transport it to next queue, Operator goes and works on Part B to completion then transports to queue, Operator goes back to Station A and transports finished part, repeat from start.
This pattern of operators finishing work but then prioritizing either filling a station with another piece of work or transporting finished work from a different station occurs at multiple points in my model. What I would prefer to happen is that the Operator picks a part, works it to completion, transports it, then repeats that cycle so that there isn't a load of "waiting for operator" or "waiting for transport" time at the stations. I've tried toying with the priorities of stations and the preempts of parts to no avail but it's also very possible I did not implement them correctly.
How can I go about making the workers prioritize working and moving the part they start instead of worrying about every station they are tied to?
An additional piece of information that may be affecting it is all operators concerned with that set of processors are connected to a Dispatcher that is in turn connected to each station in that set. For example, 6 operators in 3 different shifts are connected to a Dispatcher that is in turn connected to the 3 processors that the operators are responsible for and the queue they are responsible for transporting work from.