Custom state

Question

question

arn-k asked Sep 28 2023 at 11:02 PM arn-k commented Oct 22 2023 at 5:55 PM

Custom state

Hi all,

I am using process flow and dashboards to indicate when my two processors are faulty and when they are being repaired (I have attached my model). I have two questions in this regard:
1) the state of my machine doesn't change after the process time changes. I want this event to be shown in my states bar and state Gantt in some type of way like "faulty process". I read many sources to see if I can define a new state myself but apparently it is not possible. An easy way to do so is to use a default state and just rename it for the dashboards. In my case I chose "off-shift" state and changed it to "faulty processing" but it is still not showing anything. Am I doing this the right way?
2) The logic I had in mind was that once the machine is repaired, the process time reverts back to normal right away. However, in my model processing with longer process time continues until the product leaves the machine and then it resets the process time. Is there a way I can prevent this from happening?

Thank you!

processs flow faults_autosave.fsm

Software Version:

FlexSim 23.2.1

dashboards processs flow states custom

1695942120967.png (296.0 KiB)

processs-flow-faults-autosave.fsm (73.7 KiB)

· 1

______

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 · 2023-09-29T06:51:21Z

Jason Lightfoot answered Sep 29 2023 at 6:51 AM Jason Lightfoot commented Sep 30 2023 at 2:58 PM

When items are processed by the processor it will by default be in STATE_PROCESSING. This is set for each item that enters - your setting the state once at the time of the fault will be overridden by the next item's process start (actually as soon as an item enters or finsihes setup, processing or exits).

You can investigate use a custom state profile to record parallel states to indicate normal processing or processing with a fault. Here's a comment on another post describing this a little more.

Also - rather than have 3 (or more) process flows - one for each fault, and parameterise those, I would create a fault table on the object and have a single object process flow that reads and processes the fault information. This then is much more scalable and manageable.

Also note that by modelling the fault generation in this way you're unable to say that the time between faults is based on the time in processing state (the MTBF/MTTR object has this) and so they can happen while idle - at any time. It also means that two faults can occur at the same time and I then wonder if that would result in another slower process time than the 60 you have for Processor 2.

For example the label on processor 2 could contain this fault table:

1695970272892.png (12.0 KiB)

· 3

arn-k commented · Sep 29 2023 at 5:50 PM

Thank you so much @Jason Lightfoot for your help,

can you please attach this FlexSim file containing the table as well? thanks

0 ·

Jason Lightfoot ♦♦ arn-k commented · Sep 30 2023 at 2:47 PM

Attached is the model with the table on Processor 2. I've also added that processor to an Object Process Flow called "Processor Faults" so that I could show you how to set that up to create a token for each fault for each processor and read the information from the table.

The big difference you will see is that instead of getstream(activity) I'm using labelStream(c) which is a user command I created. The reason is that when the expression to be samples is stored on a token's label (toggled as Flexscript) it doesn't know what activity means so instead I've added commands to use the label to find the activity and processor and create a stream based on that combination. It's related to overriding the getstream() function which I describe here.

The table data is stored in a processor label called FaultDefinitions. You can right click this label and choose 'Explore as Table' to view and edit it.

In the process flow we access that (more easily) using another label on the processor called faultTable that points to it - for example the source quantity is the number of rows in the table:

Table(current.faultTable).numRows

where 'current' refers to the processor, and we read the expressions for interval and repairTime into labels using:

Table(current.faultTable)[tokenIndex]["interval"]

Then to sample the interval the syntax is simply

token.interval

which will yield a different value each time using the correct* stream setup.

I've also added pTime label to each processor so that you know to what value it should be restored when the fault is cleared. You access that value using current.pTime since current refers to the processor.

I've just set up delays to test the sampling:

but you should insert the rest of your logic and change the values to use those of the token or processor (current).

Note that the token should be retained since it has the information from which to sample the interarrival times. If you want that to be independant from the other activities that just have a simple loop for the interval delay that creates a token for the rest of the process

processs-flow-faults-autosave_jl.fsm

0 ·

1696084481852.png (26.6 KiB)

1696085445204.png (17.7 KiB)

1696085458355.png (10.5 KiB)

processs-flow-faults-autosave-jl.fsm (80.1 KiB)

Jason Lightfoot ♦♦ Jason Lightfoot ♦♦ commented · Sep 30 2023 at 2:58 PM

I've not added Processor1 to the object flow, I've left that for you to do and become familiar with.

0 ·

Answer 2 · 2023-10-22T16:39:39Z

Vinay S answered Oct 22 2023 at 4:39 PM arn-k commented Oct 22 2023 at 5:55 PM

try 3.fsmCheck this model. This will solve your problem.

Pls, go through the model and understand the changes I made to your original model

try-3.fsm (54.7 KiB)

· 1

question

Custom state

2 Answers

Things to know…

question details

Cookie preferences

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

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

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

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

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

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

Are you sure you want a less customized experience?

Your experience. Your choice.

question

Custom state

2 Answers

Things to know…

question details

Related Questions

Cookie preferences

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

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

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

THIRD PARTY SERVICES

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

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

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

Are you sure you want a less customized experience?

Your experience. Your choice.