Update List Pull requirement after quota met

Question

question

Dustin B asked Mar 3, '23 Jeanette F commented Mar 9, '23

Update List Pull requirement after quota met

Hi

I have a process where multiple product types run through the same processor.

These multiple types are placed in a List and Pulled to a Queue based on a calculated "Pullorder".

The Pullorder is a function of (wait time +/- some random variation) x product Priority value.

Type 2 is the middle priority, however we want to cap production of this at 20 units per month. This is despite there being more pending inventory available.

I tried to use a PF to count 20 entries of Type 2 and then adjust the Pull requirement to exclude Type 2 parts. This does not seem to have worked, although the logic and triggers activate the List Pull requirements don't seem to acknowledge the change and continue to pull based on "PullOrder".

Is there another way to achieve this mid process update and reset?

My goal is:

Items are pulled based on "Pull Order"
Once 20 Type 2 units are processed they are no longer pulled
At the end of the period a reset trigger is activated so that Type 2 can be processed again until it hits its 20 limit

Thanks,

Dustin

230303 List Pull Modifier.fsm

Software Version:

FlexSim 23.0.3

process flow list pull from list using list

230303-list-pull-modifier.fsm (39.1 KiB)

· 1

Jeanette F ♦♦ commented · Mar 09, 2023 at 02:37 AM

Hi @Dustin B, was Felix Möhlmann'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 unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2023-03-03T22:22:58Z

Felix Möhlmann answered Mar 3, '23 Jason Lightfoot commented Mar 3, '23

The pull requirement isn't used when pulling from a list, only when pulling through port connections.

You have to incorporate the condition into the pull query. For example, you could create a dynamic expression field for the item list which returns 1 if the item can be pulled (type != 2 or below the limit) and 0 if not.

In the attached model the Process Flow sets a label on Queue5 which is then used in the "mayPull" expression.

230303-list-pull-modifier_fm.fsm

230303-list-pull-modifier-fm.fsm (39.2 KiB)

· 2

Dustin B commented · Mar 03, 2023 at 10:40 PM

Thanks Felix

Is no simpler way than using this custom code route though?

0 ·

Jason Lightfoot ♦ Dustin B commented · Mar 03, 2023 at 11:02 PM

There will be many ways to do this. If it's just the custom code you don't like you can put this expression into the mayPull field directly:

value.Type !=2 || puller.pullType2 != 0

0 ·

question