question

Monte123 avatar image
0 Likes"
Monte123 asked Monte123 commented

Unlimited Capacity Process with Per-Type Single-Token Flow

Hello,

I’m trying to simulate a process with an unlimited overall capacity—meaning it can handle multiple product types simultaneously. However, each product type is effectively processed by a dedicated “machine,” so only one token per product type can be processed at any given time.

For example:

  • If two different product types arrive at the same time, they are processed in parallel (each has its own “machine”), but within each type, only one token enters processing at once.

  • If a third product type arrives, it too has its own “machine,” again processing only one token at a time for that type.

I’m using a Delay activity to represent the processing time, and tokens queue up there as needed. Once a sufficient sub-batch of the same product type has been processed, that batch is released together to the next destination.

How can I set up my Process Flow to ensure that:

  1. The overall process can handle multiple product types at the same time (unlimited capacity).

  2. Each product type is restricted to one token at a time in the Delay.

  3. Tokens remain in a queue while they await their turn in the Delay.

Thank you!
batch-processing-4 (5).fsm

FlexSim 24.2.1
delayrelease
5 |100000

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

1 Answer

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

Maybe I'm missing something here but it sounds like that could be solved by a zone that allows one token per batchID (which is akin to a 'type' in this model, correct?) enter at a time.

batch-processing-4-6.fsm


· 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.

Monte123 avatar image Monte123 commented ·

Yes, that’s exactly what I’m aiming for. Unfortunately, when I tried to set it up myself, it didn’t behave the way it should.
Thank You!

0 Likes 0 ·