Bug: MTBF/MTTR breaks state gantt of BasicFR

[FelixMoehlmann]

Hi,

in one of my models I use BasicFR objects as representations of some 'virtual' equipment that otherwise only exists as a resource in Process Flow, so that I can track states.

I noticed that the state gantt chart no longer works for these when they are added to an MTBF/MTTR that applies only to a subset of states.

The attached model demonstrates this. It contains a processor and a BasicFR whose states are changed to a random value every five seconds. A state gantt chart tracks the states of both objects. They are both a member of an MTBF/MTTR. If you run the model in this state, the chart works correctly.

Now change the MTBF to only apply to some state. The chart continues to work for the processor but the state changes of the BasicFR are no longer recognized and the state remains as "other" indefinitely in the chart.

Reverting the change to the MTBF does not fix the chart. It remains 'broken' with respect to the BasicFR even if the MTBF is deleted alltogether.

Since the problem does not occur with the processor I can only guess that it might have something to do with the fact that the BasicFR uses a different state change event. But so far I didn't get any further in examining this bug.

Any input or possible workaround is appreciated.

Best wishes,

Felix

[FelixMoehlmann]

Sorry for the missing attachment. Had an invalid character in the tags and had to submit the post again, but apparently the attached file was longer there.

I don't a way to edit the post or upload something in a comment. So here is an additional screenshots that shows the entire model.

[logan_gold]

Hi @FelixMoehlmann, this appears to be an issue with the MTBF/MTTR inserting a subnode into the BasicFR's behaviour node:

MODEL:/BasicFR1>behaviour/eventfunctions/OnStateChange

If you delete the eventfunctions node (or even just the OnStateChange node), clear the checkbox for "Apply MTBF to a set of states" (and hit Apply or OK), then reset and run the model, the State Gantt chart should start working as expected again.

I'm not sure why having the OnStateChange node interferes with the State Gantt chart.  Even with the added nodes, the state profile for the BasicFR seems to keep track of the state information just fine.  And something else like a Processor has the same eventfunctions/OnStateChange node added, but the State Gantt chart doesn't break in that case.  I'm guessing there is something in the chart's internal Statistics Collector that is having an issue with the OnStateChange node, but I have not been able to track down where in the collector this issue is happening.

I have added a bug report to the dev list (FLEXSIM-12598), so I will wait to see what they are able to determine.  In the meantime, the easiest solution is to not use the "Apply MTBF to a set of states" and make sure the OnStateChange node has been destroyed for the BasicFR.

The only other possibility I can think of is to install the components of the State Gantt chart and modify the State Gantt Collector that gets installed.  The hard part is trying to figure out what is causing the collector to stop working when the BasicFR has that OnStateChange node.  I don't think you can just destroy the node programmatically after the model has been reset and starts running.