First Pass Yield, item color

Question

question

Mike asked Oct 14, '20 tannerp commented Oct 26, '20

First Pass Yield, item color

This model has different failure rates for each processor. Each processor has an on exit trigger that will change the color depending on if it failed or not at that particular station. The color red means it failed at a processor and the brown color implies it passed. The problem we are having is if processor 1 fails the item, we want processor 2 to also fail that item and keep the color red. Processor 2 can keep the item on the line and take the normal processing time but it should not change the color again. In the end, we need any red item to be counted as a failure by the sink. Keeping the red items on the line is necessary as they continue to pass through the process since there is no scrap line. We can not figure out how to only change the color once when using the "set label by percentage and set color" on exit triggers.

Thank you

Software Version:

FlexSim 20.2.2

flexscript item type color change multiple processors first pass yield

1602635584911.png (63.6 KiB)

· 1

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.

Ben Wilson ♦♦ commented · Oct 20, 2020 at 03:02 PM

Hi @Mike, was tannerp's or Aida Chaikh's answer helpful? If so, please click the red "Accept" button on one of their answers. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

1 ·

Answer 1 · 2020-10-14T22:44:16Z

tannerp answered Oct 14, '20

@Mike,

If I understand correctly, you want items that are already failed to stay failed and items that are not failed to be evaluated at each processor. I think that sums it up, but correct me if I'm off base.

You can use Process Flow or Custom Code to create a conditional. I did it in Process Flow so the visuals helped with the concept. The conditional essentially checks to see if the item is already "failed". If so, then it is not re-evaluated. If it is not already "failed", then it will potentially receive a "failed" label (based on whatever statistics you want).

Take a look at this and see if you could implement the conditional idea (IF "failed" -> THEN "failed" -> ELSE evaluate)

failed label pf_1.fsm

failed-label-pf-1.fsm (35.6 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 2 · 2020-10-14T07:09:27Z

Aida Chaikh answered Oct 14, '20 Mike commented Oct 14, '20

Hi Mike, you can try using a label on the items, for example a label called Failed. This label is 0 when you create items in the source and, when the process is finish, you change this label. Using the command Math.max() you have the value 1 in the label Failed if the previous process is fail. Then, you change the color of the item if the label Falied is 1, as you can see in the image.

trggers-processor.png (48.8 KiB)

· 1

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.

Mike commented · Oct 14, 2020 at 03:58 PM

I applied this trigger logic to processor 1 and processor 2. This works for not changing the failed product after processor 2 if it failed at processor 1. However, it does not allow for processor 2 to fail "unfailed" units. Essentially the only failed units are coming out of processor 1 but processor 2 also has a first pass yield fail rate.

0 ·

question