question

Pongsakorn S avatar image
0 Likes"
Pongsakorn S asked Julie Weller commented

Resource management

Produce 2 types of products by using 2 people to lift the workpiece, which the working time of each product is different. If the product takes less time to work There are too many products waiting. require another worker to help lift the goods and return to the original job How can I do this?

FlexSim 23.1.1
resourceoperaterbottleneck
· 1
5 |100000

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

Julie Weller avatar image Julie Weller commented ·

Hi @Pongsakorn S, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. 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 comment back to reopen your question.

0 Likes 0 ·

1 Answer

·
Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Felix Möhlmann commented

"If the product takes less time to work There are too many products waiting."

I don't understand what you mean with this sentence.

Maybe have a look at the Coordinated Tasks Tutorial. It showcases a situation that sounds similar to what you describe.

· 2
5 |100000

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

Pongsakorn S avatar image Pongsakorn S commented ·

Hello, thank you for replying.

I'll attach the model file.

It is the nature of the production of 2 products.

The duration is not the same. If the operator of the 2nd type of product is unemployed, can he help the production line of another type of product? How can I do that?

thank you.12.fsm

0 Likes 0 ·
12.fsm (66.4 KiB)
Felix Möhlmann avatar image Felix Möhlmann Pongsakorn S commented ·

You would put both operators into a group and reference this group in a Process Flow resource, so both sides of the Process Flow acquire the operator from the same, shared pool.

To control priorities, you then use the query field in the Acquire activity and the Back Order Strategy of the Resource activity.

To be able to do this, you need to be able to distinguish between the operators which can be done by giving them a label with different values ("Id" in the attached model). You can then filter for a specific Id value or order by this value, prioritizing operators with lower or higher values.

The Back Order Strategy (see 'Advanced' options when clicking on the Resource) determines which token gets to acquire an operator if there are multiple tokens waiting. Here, you could for example also give the tokens a label that denotes which station they belong to. The following expression then compares this label ("StationId") to that of the operator. The comparison either returns 1/true or 0/false. If you order by this result in descending order, tokens of station 2 will have higher priority when pulling operator 2 and vice versa.

capture1.png

items_pull_operator_fm.fsm

Another, possible somewhat more intuitive way of modelling this would be to have each token represent an operator. These tokens would then pull items. Rather than each token representing an item and pulling an operator.

For this, the tokens that are created when an item enters a queue would push the item onto a list, after writing a label to them that denotes the station. You can then set up the query in a Pull From List activity so that the 'operator-tokens' preferably pull items from 'their' station.

operators_pull_items_fm.fsm

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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