Change Operator in between process when shift changes

Hi,

I have a model in which I need to change the operator when the shift changes . Problem is when the process is not completed in the first shift itself the second shift operator is not called and remains "idle" and the processor "waits for the operator".


ex:
Suppose I have a station that does a process of time 40 mins.
Operator 1 works in shift 1.
Operator 2 works in shift 2.

I want to change the operator when shift changes .
Suppose a part is processed only for 20 mins at the end of first shift by the operator 1. I want the operator 2 to carryout the rest of the operation in shift 2..

Can someone help me with this...

Thanks in advance.
Good day.

Don´t know what other tasks you got for the second operator that isn´t in a shift. But a simple and fast solution for me would be, to use only on operator and notice this for evaluation. Maybe you can set a label what shift your operator is in.

Greetings

Hi Sebastian,

Thanks a lot for replying.

I have 4 operators working in 4 dedicated stations in 1st shift. In the 2nd shift, only 1 operator is available for all the 4 stations.

I want to use separate operators for each shift and study their stats.
How to change operators in between an ongoing process?

Thanks.

Hello Nataraj,

you use at shift end the freeoperator-command and write new tasksequences for each Operator to go somewhere else. To stop the processor use the command requestoperators. As a dispatcher you set the operator of the next shift.

Jörg

Hi,

if you use a timetable, let the Operators be the timetable members.
You can write the freeoperators-command in The Down Function. It expects the reference to the taskexecuter, which is the downobject and the involved object, which is the processing item. When a specific Operator is freed, write the requestoperators-command, so only one operator is ordered to the processor in the next shift.

Jörg

No need to write task sequences yourself, this can all be done using port connections and standard Flexsim functionality.

Remember that the operator himself is a dispatcher, when you preempt him he will (depending on the preemption type) try to dispatch his current unfinished task sequence to a dispatcher or operator connected to his output ports.

In this model I have 4 processors using each an operator for process and I have a team of operators for each shift (3 shifts, 3/2/1 operators respectively). I used Time Tables to define each shift, and used the Down Function pick option called "Create Task Sequence 1". In this option I changed the preempting to "PREEMPT_ONLY". Note that the Resume Function should be set to Do Nothing as the option instructs.

Each processor is connected only to the shift 1 dispatcher. The shift 1 operators are output connected to the shift 2 dispatcher so when their shift ends their active (unfinished) task sequences will be passed to the next shift team.

Note that the shift 1 dispatcher is also directly connected to the shift 2 dispatcher so that jobs will flow through during shift 2. I use a User Event to close and open inputs of the dispatchers to control the flow of task sequences according to the current shift. CAREFUL, since Shift1 feeds Shift2 which feeds Shift3 which feeds back to Shift1... you can very easily create an infinite loop if you don't get it right. Save your model before you run.

This method won't work for all situations, but the dispatcher side of TEs is often overlooked.

Here is a thread on the topic of preemption: http://www.flexsim.com/community/for...ead.php?t=1792

Hi Sebastian , Jörg , Kris

Thanks a lot for replying.

Jorg - I too was trying something similar to that using requestoperator, freeoperator & prempt task. Thanks a lot .

Kris - That was exactly what I was looking for and it is also simple . Thanks a lot .

It was good learning from you guys.

Thanks again
Good day
Naren

Hi Kris

I have used the same solution you gave.. But my model is getting crashed and I m not able to fix it.

Could you please help me with this. I have attached a sample model ( codes are in user event & Time table )

Thanks in advance
Naren

Hi Naren,

You doubled the concept, but forgot to extend the user event code to control the ports of Dispatcher4, 5 and 6 (just like Dispatcher1, 2, 3 respectively).

Kris