Problem in setting breakdown of task executer

Question

question

Abdallh Omar asked Jun 13, '18 Joerg Vogel commented Jun 14, '18

Problem in setting breakdown of task executer

push1sc.fsmIm trying to make a breakdown for the task executer1 and stop its input but it's state didn't change

Any help?

task executors

push1sc.fsm (45.8 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.

Answer 1 · 2018-06-13T14:47:36Z

tannerp answered Jun 13, '18 Joerg Vogel commented Jun 14, '18

You can try exploring this thread to find details regarding how breakdowns and down time work: https://answers.flexsim.com/questions/51768/mtbt-mttr.html?childToView=52033#comment-52033

After examining your model, I found that the process flow is overriding what you have in the 3D model. I have changed the MTBF-MTTR settings to Stop Object instead of just Stop Input and now the state changes to "Breakdown" at your desired time.

Let me know if this helps solve your problem.

· 2

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.

Abdallh Omar commented · Jun 14, 2018 at 02:27 AM

Why process flow always override what i made in the 3D model?

0 ·

Joerg Vogel Abdallh Omar commented · Jun 14, 2018 at 03:40 AM

It isn't overriding. You can write the model logic in Process Flow easier. You bypass some structures or methods. But you are still free to adapt the same structures of the 3D into Process Flow. For example take the tasksequence in 3D. A tasksequence contains the action the operator will do before he gets the job to do. In Process Flow you can set for each activity equal to a task an option to wait until complete. Thus you can control the action of the operator while he does the sequence. Some user might argue that you can achieve the same in 3D, too. But it is much more code over several triggers distributed.

2 ·

question