question

Ankur A3 avatar image
0 Likes"
Ankur A3 asked Ankur A3 commented

Resetting random breakdown during model run?

Hi Team,

I am modelling a scenario where there are 2 processors, and the logic is as below:

When processor 1 is down, another processor 2 also stops and its random breakdown series gets reset from starting and vice versa.

I have tried it by updating number in global table for downtime distribution in case of downtime event. But it doesn't make any difference whether values are linked to global table or used directly in distribution.

Currently, I am stopping the processor 2 when processor 1 is down and vice versa. Along with that I want to reset the breakdown clock of processor 2 which is not happening.

1720087689620.png

Could you help me to know how to reset the random breakdown series for the processor 2 in case of downtime event for processor 1?

Thank you!

Reset_Random_Breakdown_Series.fsm

FlexSim 23.1.1
downtime functionreset breakdown value
5 |100000

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

1 Answer

Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Ankur A3 commented

You can get the same behaviour by using a single MTBF/MTTR for both processors and set it to breakdown for all objects at the same time. Then determine the up time by getting two values from the distribution and choosing the lower one (the first processor to break down would have determined the time).

1720088952139.png

reset-random-breakdown-series_1.fsm


· 8
5 |100000

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

Ankur A3 avatar image Ankur A3 commented ·
Hi @Felix Möhlmann,

Thank you for your response!

Could you help me to understand it more?

1. Why did you use the two distribution and taken the min value?

2. Processor 2 is following the Processor 1 downtime every time here while they are supposed to breakdown independently and controlling the behavior of other processor.

Thank you!

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Ankur A3 commented ·

Other than possibly using different states (which could still be added to this method) I don't see a difference between both processors breaking down always at the same time or independently and then stopping the other. The result is the same: Both processors are stopped at the same time.

Two processors breaking down independently and stopping the other would overall be down more often than if a single MTBF/MTTR was used. That is why I generate two random values and choose the lower one: To simulate the breakdown that would have occured first stopping both processors and resetting the up time on both.

0 Likes 0 ·
Ankur A3 avatar image Ankur A3 Felix Möhlmann commented ·
Hi @Felix Möhlmann,

Thank you for the explanation!

Yes, it's correct that ultimately it is going to be down state whichever is the cause. Still, I would like to make it independent and making the other one force down. The reason I need it because I have to measure the cause of failure when their failure is happening at different rate.

I would like to understand why you have taken the min value only. Could it be any random value or max value?

0 Likes 0 ·
Show more comments