Custom States in MTBF MTBR

Question

question

mcretssinc asked Jul 08 2024 at 8:35 PM Felix Möhlmann commented Jul 10 2024 at 7:11 AM

Custom States in MTBF MTBR

Hello guys,

How is it possible to exclude custom states from being affected by the MTTR MTBF ?

My custom states don't appear on the left side.

Thank you.

Software Version:

FlexSim 24.1.0

mtbf mttr

1720470864737.png (45.5 KiB)

· 3

Joerg Vogel commented · Jul 09 2024 at 6:44 AM

States in general are discrete number values. You translate them as string information. States for 50 values are predefined. And if you don’t find your values in a GUI, you still can find them in the tree. Try it.

0 ·

Felix Möhlmann commented · Jul 09 2024 at 6:51 AM

Can you upload your model or an example model with the object with custom states so we can check why they don't appear in the list?

As a workaround you can edit which states the MTBF applies to directly in the tree. (Add a least one state to the right side for this node structure to appear. Then edit it to your liking. As far as I can tell the naming of the nodes does not matter, only the values which represent the state numbers of the affected states)

0 ·

1720507788136.png (16.5 KiB)

mcretssinc Felix Möhlmann commented · Jul 09 2024 at 8:34 PM

Hello guys,

I have uploaded the model. When running with just 1 resource the state pie chart registers only the wanted states but the Gantt registers also travel empty and travel loaded. When running with 2 resources both charts register travel empty and travel loaded.

The important thing is that MTBR/MTTR should take into consideration only travel empty/loaded states and not other states. But somehow it triggers even if I set different states to the task executers other than travel empty/travel loaded.

How can I fix this ?

Thank you so much.

State_test_model.fsm 1 task_executer.jpg 2 task_executers.jpg

0 ·

1-task-executer.jpg (583.7 KiB)

2-task-executers.jpg (622.5 KiB)

state-test-model.fsm (162.7 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2024-07-10T06:11:24Z

Felix Möhlmann answered Jul 10 2024 at 6:11 AM Felix Möhlmann commented Jul 10 2024 at 7:11 AM

The state pie chart filters out states with a time of 0 automatically.

The gantt chart does not have this option. So you will always see all states the object entered appear in the legend. Even if the object never spends any actual time >0 in the state. A possible workaround would be to install the chart components and clone the Statistics Collector with a Calculated Table while filtering out any entries where the start time and end time are equal. Then use the Calculated Table as input for the chart.

In your Process Flow you always set the state of TaskExecuter1, not the currently acquired resource. So any TEs past the first will always be in the default states.

state-test-model_1.fsm

1720591673600.png (2.8 KiB)

state-test-model-1.fsm (51.1 KiB)

· 2

mcretssinc commented · Jul 10 2024 at 6:53 AM

Hello @Felix Möhlmann ,

Even so the task executers they still go through travel empty/travel loaded states. Is there a way to fix that ?

0 ·

Felix Möhlmann mcretssinc commented · Jul 10 2024 at 7:11 AM

No, the default state change will always occur. You can force the TE into a different state afterwards, as you currently do, but not prevent the state switch. Though if the state is only assumed for 0s it should not make any difference as far as model functionality is concerned.

If you want full control over the state implement a custom state profile in addition to the default one. There are multiple posts on this forum that demonstrate how this is done.

https://answers.flexsim.com/questions/26312/add-custom-state-to-a-state-gantt-chart.html

0 ·

question