question

Thibault.G avatar image
0 Likes"
Thibault.G asked Jeanette F commented

How to perform batching on a queue only at the beginning of the shift ?

On my simulation i'd like to create a WIP between 2 stations. The target is to fill the WIP until a certain limit for example 10pcs before an operator comes on the station to work and release the WIP. For that, i used the function "perform batching". However, i'd like now this function to be active only one time at the begining of the shift and then no batch necesary.

Does someone know how to set the parameters and create the code behind this need ? Thanks in advance.

FlexSim 21.2.4
queuebatchingshift schedule
· 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.

Jeanette F avatar image Jeanette F ♦♦ commented ·

Hi @Thibault.G, was Jason Lightfoot'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.

0 Likes 0 ·

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot edited

This is a seemingly simple question but the recommendation will depend on how the model is configured. Note that batching isn't really considered as a solution here since that could also be a requirement that is superimposed over the shift or control logic as another layer of complexity.

Operators transporting and processing

If you have operators in your model that are transporting from the queue to the processor and then working on the item in the processor, then by just putting the operator on a timetable, you will be preventing transport jobs from queue to the processor and the items will accumulate.

No operators - processor on a timetable

Without operators if you have the processor on a timetable you can close/stop the input of the processor when the shift ends to prevent more items entering and reopen/resume the input when the next shift starts.

No Operators - queue on a timetable

As above but instead of opening and closing (or stopping/resuming) inputs you'd open and close (stop/resume) the queue's outputs.


The references to the stop/resume vs open/close are there in case you need to mange the ports for some other control logic, beside the timetable/shifts. The difference is that while open/close are absolutes in that they always open or close the port, the stop/resume actions stack allowing you to stop for some control aspect(s) and then additionally stop for the end of shift. Then when the control part resumes the port, the timetable stop is still in effect and the port will not be open for transfer until that and any other stop on the in/output is also resumed.

5 |100000

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