topic Re: Shared Resource : with different cycle times in FlexSim Forum

Shared Resource : with different cycle times

kshitijdhake — Mon, 03 Feb 2025 18:51:19 GMT

[ FlexSim 22.2.0 ]

Flexsim Doubt.fsmI have a capacity of 15 units/resource. I want to route route 4, 2, 3 units in the resource.

Re: Shared Resource : with different cycle times

moehlmann_fe — Tue, 04 Feb 2025 10:58:10 GMT

You mean you want to first batch four units and then send them to the machine, afterwards two and then three, then repeat from the start? Or would the batches be formed by some condition?

Re: Shared Resource : with different cycle times

kshitijdhake — Tue, 04 Feb 2025 15:05:56 GMT

Every week, I will create 8 units at the source. Out of these, 2 units will be assigned to the 2-unit per cycle flow, 3 units to the 3-unit per cycle flow, and the remaining units will go to the 4-unit per cycle flow. This process will continue on a weekly basis.

Next week, I'll have another 8 units, and their availability will be checked for the 2-unit, 3-unit, and 4-unit per cycle flows. Depending on the available spots, units will be assigned to the respective flows.

Re: Shared Resource : with different cycle times

moehlmann_fe — Tue, 04 Feb 2025 16:23:16 GMT

How does the capacity of 15 units/resource factor into this if only a total of 9 tokens can be assigned to the flows?

Re: Shared Resource : with different cycle times

kshitijdhake — Tue, 04 Feb 2025 16:54:05 GMT

At the first week 9 tokens will be assigned to the flows, So first week only 9 units will be in the resource. Next week there will be 6 units empty in the resource. These 6 units can be accommodated in one of those 3 flows depending on which one is available

Re: Shared Resource : with different cycle times

moehlmann_fe — Tue, 04 Feb 2025 17:10:49 GMT

But then what determines if a flow is "available" if it doesn't have to be empty? Or, in other words: Assume that there are 4 tokens in the 4unit flow, 3 tokens in the 3unit flow and 2 tokens in the 2unit flow. What happens to newly arriving tokens in this case?

Re: Shared Resource : with different cycle times

kshitijdhake — Tue, 04 Feb 2025 17:17:55 GMT

In this scenario, there are 4 tokens in the 4-unit flow, 3 tokens in the 3-unit flow, and 2 tokens in the 2-unit flow, giving a total of 9 tokens and 5 empty spaces in the resource. The tokens will first check if the 2-unit flow is available. If it isn't, they will check the 3-unit flow. If the 3-unit flow is also unavailable, the tokens will flow into the 4-unit flow. Any excess tokens will wait in the queue.

Re: Shared Resource : with different cycle times

moehlmann_fe — Tue, 04 Feb 2025 17:45:37 GMT

You didn't answer what available means in this context. What you said so far are two conflicting rules.

So the first two tokens would enter the 2unit flow. Now either this flow is not available (because there are as many tokens as there are spaces in the flow), thus the next three tokens go to the 3unit flow and then four tokens go to the 4unit flow. By this logic all three flows are now unavailabe, thus limiting the resource to 9 tokens in total.
Or if the resource capacity is the deciding factor, the third and fourth token would also enter the 2unit flow, eventually ending up with 14 tokens in the 2unit flow and the rest waiting.

Which of these, if any, is the logic you are going for?

Re: Shared Resource : with different cycle times

kshitijdhake — Tue, 04 Feb 2025 18:02:30 GMT

The first one

Re: Shared Resource : with different cycle times

moehlmann_fe — Tue, 04 Feb 2025 18:34:39 GMT

You could push "spaces" in the cycles onto a list. Each list must then pull a space before it can continue. The pulled value determines where to send the token at the same time.

flexsim-doubt(1).fsm

Re: Shared Resource : with different cycle times

Jeanette_Fullmer — Tue, 11 Feb 2025 22:16:46 GMT

Hi @Kshitij Dhake, 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.