question

Adil M avatar image
0 Likes"
Adil M asked Felix Möhlmann commented

Capacity Logic and loading/unloading time

Hi,Extra Small Packages Model.fsm

I have a model built in which operators pick two packages from the conveyor and place on a queue(pallet) based on package "type". The model I had initially built did not utilize process flow as I wasn't confident but it wasn't working well. So I was able to get assistance from the FlexSim community to help build the process flow for this.


The issue now however is that I want to change the capacity of the operator and the loading/unloading time. I made changes to the operator directly but since process flow is being used it did not affect the model. Can you help me understand which portion needs to be edited in order to change capacity and loading/unloading time? Also, when I put the loading time for an operator who has a capacity of say 2. Is the loading time per package or is it for 2 packages?

FlexSim 23.1.3
capacityloadingunloading
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 Felix Möhlmann commented

After loading an item the Process Flow compares the current number of loaded items to a numeric value in the "Load More" Decide activity.

1688018713092.png

If the condition is true (the number of loaded items is smaller than the number it is compared to) the token loop will loop back to the top and pull another item to load. The capacity is thus controlled by editing the number in the condition.

The token runs through the activity block below for each item, including the "Loading Delay". So the load time you enter there is used per item.

1688018807988.png

The unloading happens in a subflow that does not currently have a delay. To add an unload time, add a delay activity to the subflow as seen above (and change the state the operator is in during the delay to 'unloading')

1688018884251.png


1688018713092.png (20.4 KiB)
1688018807988.png (13.2 KiB)
1688018884251.png (2.8 KiB)
· 3
5 |100000

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

Adil M avatar image Adil M commented ·

Thank you, Felix! I noticed that making changes to loading/unloading time on the properties window does impact the operator as well. Does this override the time we have put in the process flow?


Also want to confirm that this time is also per package irrespective of what the capacity is. So a capacity of 2 would take double of the time put in the loading/unloading window.

1688050766499.png

0 Likes 0 ·
1688050766499.png (12.9 KiB)
Adil M avatar image Adil M commented ·

An issue that I noticed with just making the recommended change is that even though the associate is picking up 4 packages now its only unloading 2 and then returning back to pick 2 more packages. Essentially the capacity still remains 2.

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Adil M commented ·

The task executers load/unload time are used for the respective tasks in a task sequence. In Process Flow you use the Unload activity which will use the unload time specified on the operator.

You have to adjust how often you run the subflow (and how you refer to the individual items) to sync up with the number of loaded items. A flexible way that keeps (some of) the logic to unload to the closest queue first would be to push all loaded items onto a list. Each subflow token then pulls the item with the closest destination off the list and tells the operator to unload it. You can partition this list by the operators, so they can all use the same list.

extra-small-packages-model-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.