question

Patrick Cloutier avatar image
0 Likes"
Patrick Cloutier asked Jeff Nordgren commented

Force Task Executer to take something right away if available

In the attached sample model, I'm trying to force a TE to take a green box (if there's one available) as soon as he drops a blue one. If there is no green box, he just continues as usual. It needs to be the same TE that dropped the blue who takes the green when that happens.

I assume it probably involves pushing a new Task to the top of the Sequence whenever "Green ready" is fired and to force it to be done by the same TE. I just don't know how to do those things...

Help will be very much appreciated. Thanks,

release-but-stay.fsm

process flowtask executer
release-but-stay.fsm (35.5 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

2 Answers

Jeff Nordgren avatar image
0 Likes"
Jeff Nordgren answered Jeff Nordgren commented

@Patrick Cloutier

Patrick,

I think my solution is pretty simple as well. Basically, after a lift truck drops off a flowitem to Q2, I have it run a Sub Flow to check for the existence of a green box. If there is one, it will Pull the flowitem off of List1 (GreenBoxes) where it was pushed to that list in the OnEntry trigger of Q3. Then the lift truck will travel to Q3 and load the green box, then travel to Q4 where the green box is unloaded. If there are no green boxes to pick up it just returns from the Sub Flow without doing anything.

release-but-stay-jn1.fsm


q6cz0.png (28.9 KiB)
release-but-stay-jn1.fsm (36.9 KiB)
· 6
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Jeff Nordgren avatar image Jeff Nordgren commented ·

@Patrick Cloutier

A slightly different version of the model.

release-but-stay-jn2.fsm

0 Likes 0 ·
release-but-stay-jn2.fsm (36.8 KiB)
nef2e.png (29.0 KiB)
Jeff Nordgren avatar image Jeff Nordgren Jeff Nordgren commented ·

@Patrick Cloutier

Patrick,

Did any of the answers to your question work for you? Or is there still a problem?

0 Likes 0 ·
Patrick Cloutier avatar image Patrick Cloutier commented ·

Thanks but I haven't had time to work on this since Friday. I'll reply when I'm there probably tomorrow. Thanks a lot !

0 Likes 0 ·
Jeff Nordgren avatar image Jeff Nordgren Patrick Cloutier commented ·

@Patrick Cloutier

Patrick,

If you're interested at all, here is the same model as jn2 but in FlexSim Version 2017. It uses the new Dot Syntax style.

release-but-stay-jn2-v17.fsm

0 Likes 0 ·
release-but-stay-jn2-v17.fsm (37.0 KiB)
Patrick Cloutier avatar image Patrick Cloutier commented ·

Since I don't have v17, its telling that model can't be updated.

0 Likes 0 ·
Jeff Nordgren avatar image Jeff Nordgren Patrick Cloutier commented ·
@Patrick Cloutier

Patrick,

You can get V17 by logging into your FlexSim account and going to Downloads and clicking on the More Versions button next to the main blue Download button. This will allow you to download the beta version of 2017.

0 Likes 0 ·
Regan Blackett avatar image
0 Likes"
Regan Blackett answered Regan Blackett edited

@Patrick Cloutier

The simplest way to to do this in the model as you have it configured is probably to let the green box have an item type that isn't 1 or 2 (your red and blue box types) and let the resource have a Queue Strategy. Since the Resource uses a list behind the scenes you can sort the the requests using an ORDER BY query in the Queue Strategy. So saying something like:

ORDER BY Puller.dest DESC

Will sort the requests on the resource using a descending sort on your dest label. So if the green box was assigned itemtype 3, and and that value gets copied to your dest label like the red and green boxes, then if there's a green box, that request on the resources gets filled first if it's there.

5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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