question

Arun Raj avatar image
0 Likes"
Arun Raj asked Felix Möhlmann answered

Change production shedule w.r.t rack storage

Hi,
I am having 3 types of products
A = 200 nos
B = 150 nos
C = 300 nos
I am having rack where these items are stored and from rack it goes to processor. I have assigned separate bay for each items.
Now when bay storage reaches 90% with A , source should hold producing A and produce B item and when Item A in bay falls to 20%, source need to continue to produce remaining A.

Is there any way.

FlexSim 21.0.3
rackdecide by percentagesheduled source
· 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.

Parker S avatar image Parker S ♦ commented ·

Hi @Arun Raj,

It's hard to know how to help without looking at your model. To receive a more accurate solution, please post your model or a sample model that demonstrates your question.

Proprietary models can be posted as a private question visible only to FlexSim U.S. support staff. You can also contact your local FlexSim distributor for phone or email help.

0 Likes 0 ·
Arun Raj avatar image Arun Raj Parker S ♦ commented ·

Hi @Parker S ,

I have attached sample file(not actual file) for ref.

1641404854344.png

here you can see model has choked up due to rack storage , for that i am trying to to skip production for next item when rack storage for item "A" reaches 90%. also when storage of "A" declined to 20% source need to produce remaining items of "A". pls notify if not clear.

sample.fsm

0 Likes 0 ·
1641404854344.png (137.0 KiB)
sample.fsm (47.5 KiB)

1 Answer

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

I would suggest to use a process flow to create the items instead of a source, as this gives you much more options to control what gets created when.

In the attached model I use an instanced process flow connected to Queue1. Queue1 possesses an array label "ProdData". The first number in each entry is the number of items that should get created and the second number is the type (I use numbers instead of letters as this makes referencing the correct array index much easier). The third number signifies whether the production of this type is currently allowed/active (1 = active, 0 = inactive) and the fourth number is how many items of this type are currently stored in the rack.

1641455656703.png1641456059178.png

A single token loops through the process flow and does the following steps. First it checks whether the capacity of the queue has been reached. If that is the case it waits until an item has exited the queue. Afterwards the ProdData label is checked for the first "active" entry that still has production queued (first number > 0). Then, the respective quantifier is reduced by one and an item of the type is created in the queue. If no eligible entry is found the token either waits until an item leaves the rack to check again if some entry has become "active". Or, if no quantity above zero is left, it goes to a sink, since all items have been created.

Setting the "active" value is handled by a different part of the process flow. Two event triggered sources react to items entering and leaving the rack. When an item enters, the stored quantity is incremented (fourth value in the array). If the stored number is above 108 (90%) the entry gets set as "inactive" (third value = 0). Conversely, when an item exits, the stored quantity is decremented and the active value is reset to 1 if the quantity falls below 24 (20%).

sample_1.fsm


1641455656703.png (3.9 KiB)
1641456059178.png (37.8 KiB)
sample-1.fsm (57.7 KiB)
5 |100000

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

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.