Conditional Decide in Decide ProcessFlow

Conditional Decide in Decide ProcessFlow

Roland8
Not applicable
265 Views
9 Replies
Message 1 of 10

Conditional Decide in Decide ProcessFlow

Roland8
Not applicable

[ FlexSim 23.1.1 ]

We are woriking on a trafic simulation control. Now we are trying to set conditions for our vehicules coming from node NN4, to either continue the path (to node NN9 at left or node NN10 at right) or stop at node NN6 as soon as vehicles generated from node NN11 get to NN9.

However the first mentioned vehicles always exit out of connector "Decide 2" while they should also exit out of connector "Delay" depending on the conditions mentioned before.

1683846246251.png

network nodes and trafic control essai 01.fsm

0 Likes
Accepted solutions (1)
266 Views
9 Replies
Replies (9)
Message 2 of 10

moehlmann_fe
Advocate
Advocate

I don't see any problem in the attached model. The first decide activity is set to send the token to either of the two connectors with a 50/50 distribution and that is also what is happening in the model.

capture1.png

0 Likes
Message 3 of 10

issiak_kanazoe2601
Explorer
Explorer

He means he wants to trigger his mentioned events "Decide2" and "Delay" both based on conditions, not on a random distribution or a percentage.

"Delay" event, which corresponds to "vehicles stop at node NN6" is triggered as soon as vehicles generated from node NN11 arrive to NN9.

"Decide2" event, which is " either continue the path (to node NN9 at left or node NN10 at right)", is triggered when vehicules coming from node NN4 arrive to node NN9.

Actually, we are working on the same project.

Here is the full version of the model: network-nodes-and-trafic-control-update.fsm

Expecting for a quick reply please, we are really running out of time.

0 Likes
Message 4 of 10

joerg_vogel_HsH
Mentor
Mentor

@Issiaka, decide activities aren’t meant for being an event triggered or waiting for states situations. Decides activities are instantly acting. If you need to wait for a state you achieve this by backorders in a list. Or you can collect tokens in a batch activity to match certain labels. Or you can build a process flow of split and synchronized activities to wait for mile stones in a process to be mutual dependent before allowing any further progress of your tokens.

0 Likes
Message 5 of 10

issiak_kanazoe2601
Explorer
Explorer

Thanks. I am still trying to implement each process you mention.

But I have another question, that is how do I make vehicles stop right after each other when one vehicle stopped on a node (in here specifically node NN6) and avoid that they all group together on the node.

0 Likes
Message 6 of 10

joerg_vogel_HsH
Mentor
Mentor
Restrict number of travelers at network nodes. But you should ask a new question to get more information about it.
0 Likes
Message 7 of 10

issiak_kanazoe2601
Explorer
Explorer
I set the max travellers to 1 but vehicles still don't stop one after the other on the connection between the two nodes when a vehicle already stopped at the destination node
0 Likes
Message 8 of 10

joerg_vogel_HsH
Mentor
Mentor

@Issiaka, do it with a traffic controller or use an AGV network.Wait_at_traffic_controlled_node.fsm

0 Likes
Message 9 of 10

moehlmann_fe
Advocate
Advocate
Accepted solution

As Joerg suggested, you can try to use the Traffic Control object to manage the entries into the intersection.

In the attached model I tried to emulate what the Untimed Traffic Modes option of the Traffic Control does in a Process Flow. With the addition that the different modes can have priorities, since in your question it sounds like the task executers travelling in west-east-direction should have priority over those crossing in north-south-direction.

network-nodes-and-trafic-control-update_fm_1.fsm

0 Likes
Message 10 of 10

julie_weller
Not applicable

Hi @roland, 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 Likes