Scheduling tokens is not working properly and how to campaign batches?

Question

question

Mohamed A17 asked Jun 01 2022 at 1:41 PM Mohamed A17 commented Jun 21 2022 at 11:20 AM

Scheduling tokens is not working properly and how to campaign batches?

Hi,

I am working on a model where 10 batches are created where each batch has a priority and needs to be picked by one processor then sent to a line for filing and packaging. The processor is picked based on the batch size. After the processor or the line finishes their job, an inspector is required. My questions are:

How to process the batches based on their priority in series (1,2,3...etc) as my model process the batches in a different priority order (1,3,6). The main reason I found that the model processes the batches of the highest order for each processor but not based on the global priority.
How to not pick the inspector if there are three order of the same batch as can be seen in BatchCode A1 (How to process these tokens in campaign).
How to measure the time each token spends in either the processor or the line. Or, how to know the time a token spends in the model since being assigned to a processor until it leaves the model.

Please find the attached model for more information.

Best regards,

Flexsim_Question.fsm

Software Version:

FlexSim 22.0.1

tokens scheduling campaign

flexsim-question.fsm (169.8 KiB)

· 1

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2022-06-01T22:13:15Z

Kavika F answered Jun 01 2022 at 10:13 PM Mohamed A17 commented Jun 21 2022 at 11:20 AM

Hey @Mohamed A17, I think I've made a solution that answers most of your questions.

1. You want to make sure batches are processed in their global priority defined in the first Source Activity. Simply add a Resource that must be acquired one at a time so as items are pulled from the list in the correct priority order, they are processed in that order (so you'll have 1, 2, 3...). However this will mean that only one processor will be used at a time.

2. What I understand from this question is that you want to process all products with the same BatchCode at the same time and you don't want the inspector to inspect these products? One approach would be to determine when you have multiple products with the same BatchCode, process one, and throw the other ones away (given that they all have the same stats and you don't need to keep track of their count in the future).

3. As for stats collecting, I referred to this post which helped me create a StatisticsCollector in your model that tracks the staytime of tokens in the system since creation.

Honestly I think it would be easier to use actual flowitems in your model rather than just changing the colors of things. Then you could take advantage of some of the built-in 3D model features like sending items from processors to other processors, using an actual operator to move and perform inspections on processors and lines, etc. It could even solve some of your batching problems because you could batch flowitems into different totes/pallets and move them as a group.

solution.fsm

1654120965400.png (72.8 KiB)

1654121512538.png (15.8 KiB)

solution.fsm (56.7 KiB)

· 7

Mohamed A17 commented · Jun 02 2022 at 6:47 PM

Hi @Kavika F,

Thank you for your kind reply. I really appreciate it. Please find below my reply on your comments.

1. The main idea is to use multiple processors in parallel based on the global priority of each batch as I can't afford using one processor at a time. Is there a way to pull a processor from list if the global priority of the current token is higher than the previous token by 1?. Maybe this can solve that issue.

2. For this part, the orders having the same batch code need to be processed in a campaign mode; the batches of the same code are processed in series at the same processor. In my case, there are 3 orders having the same batch code. These orders need to be processed in P1. After P1 is used 3 times, the inspector is called. If an order has a unique batch code, the processor is used 1 time then the inspector is called. I hope this explains the question well.

3. This works perfectly.

I would appreciate if you could share more thoughts on how to tackle these points.

Thanks in advance,

Mohamed

0 ·

Kavika F ♦ Mohamed A17 commented · Jun 02 2022 at 7:00 PM

Glad the stats collection works for you!

1. I think the problem here is that certain items can only be processed on specific processors based on size (i.e., P1 can only process items of size 20, P4 for size 10, P5 for size 2). So if you have an item 'A' with [priority 1, size 20] and the next item 'B' is [priority 2, size 20], your item 'B' has to wait for P1 to become available, thus creating the bottleneck on priority.

2. Your explanation helped me understand this point better, thank you. Will items with the same BatchCode always have sequential/back-to-back priority (i.e., 1, 2, 3...) or can they possibly be spread apart (i.e., 1, 5, 9...)?

Maybe if I knew a bit more about the problem you're trying to solve, then I could try to help with a solution that best fits your needs. I understand if you can't disclose that information though.

0 ·

Mohamed A17 Kavika F ♦ commented · Jun 03 2022 at 1:43 PM

Hi @Kavika F,

Thanks again for your help. Please find my comments:

1. Noted.

2. In this case, the orders of the same BatchCode should either have a sequential priority (1,2,3) to ensure the same processor is used to process these batches or have the same priority (1,1,1) which I hope will lead to the same required behavior.

Thanks again,

Mohamed

0 ·

Show more comments

question