set operator state from idle to repair when processor breakdown

Question

question

kongxincaier asked Feb 21, '24 Jeanette F commented Feb 26, '24

set operator state from idle to repair when processor breakdown

demo.fsmHi ， now my model have a problem. I want to write a PF :when processor state switch from processing to breakdown, processor require an operator to do some repair work , and when processor state switch to processing ,the operator will travel to the rest place.

I have set the MTBF in the model, but i don't know how to set the state monitor in PF 。

Software Version:

FlexSim 22.2.0

call operators switch statement monitor processor state

demo.fsm (41.6 KiB)

· 1

5 |100000

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

Jeanette F ♦♦ commented · Feb 26 at 05:45 PM

Hi @kongxincaier, was Felix Möhlmann'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 ·

Answer 1 · 2024-02-21T07:45:29Z

Felix Möhlmann answered Feb 21, '24

When setting the state of a task executer directly after some task is finished in Process Flow, you need to insert a "Breathe", a 0s delay. Otherwise the natural state change back to idle will override the custom state due to how the timing works out.

Currently, the Event-Triggered Source creates a token on any state change of the processor. You should specify that the "toState" has to match the breakdown state.

The better event to listen for in this case would actually be the "Down Function" of the MTTR. It allows you to get a reference to the processor and the duration of the down time. Which in turn allows you to use a delay task in place of setting the state manually and having to use Wait for Event activity to check when the breakdown ends.

demo_1_fm.fsm

Another solution would be to not use a Process Flow at all. Instead use the "Stop Object and Call Operator" option for the down function in the MTTR. You can then customize the code to use the "Repair" state instead of "Utilize" and add an extra task to return to the rest position.

demo_2_fm.fsm

capture1.png (4.3 KiB)

capture2.png (41.7 KiB)

demo-1-fm.fsm (39.2 KiB)

demo-2-fm.fsm (154.4 KiB)

5 |100000

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

question