question

Harrison avatar image
0 Likes"
Harrison asked Natalie White commented

The other operator takes over the incomplete work during breaktime

Demo.fsm

Hi, I have one scenario where there are 8 wafers in 1 clamshell, at model time 8:05, I create 8 wafers at Queue2 to indicate 1 clamshell arrive at the current step.

1691290255413.pngNormally once 1 operator receives the 8 wafers, he will be the main person responsible for them since he physically holds the clamshell. Now 1 tool will process 2 wafers at a time, so the 8 wafers are divided into 4 batches, each batch contains 2 wafers. In addition, the general practice is that once the operator finishes loading the first batch, while the first batch is processing, he will start to load the second batch based on the tool availability. Now how I approach this scenario shown in the pic below where I use the same operator in subflow to run the 4 batches, and use pull from tool list and Create TS sequence as the gating points. And it is working fine for me.
1691291066320.png

However, the problem comes when this person is preempted by a high priority task (eg: Break). I don't want operator to finish processing the 8 wafers then go to break, I want him to go break straight away, during his break time, all the tools are being claimed by tokens already and there is no one to unload the processed batch. 1691291436479.pngMy question are:
1. Is there a better way to approach the scenario where the same person is responsible for 8 wafers and he can start load the 2nd batch based on tool availability after loading the first batch.
2. A separate question will be, with the current design, how can I pass the incomplete tasks to the 2nd operator, so the 2nd operator takes over when the 1st operator goes to break.


Really appreciate your help.

FlexSim 23.0.3
break time
1691290255413.png (85.3 KiB)
1691291066320.png (64.8 KiB)
1691291436479.png (60.9 KiB)
demo.fsm (60.8 KiB)
· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Natalie White avatar image Natalie White commented ·

Hi @Harrison, was Jason Lightfoot's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 Likes 0 ·

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot edited

When you preempt an operator, the active task will look for output ports to which it can release the current tasks sequence. So if you connect the operators together the task sequence will get put in the queue of the other operator.

If there are some tasks that need repeating - like travelling to the part locations then you will need to add milestone tasks with an appropriate range value.

You can also re-dispatch the preempted task sequence. This example may help you gain further understanding of the mechanisms at play.

5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.