














Use the Decide activity in your process flow to send tokens to activities by case and by condition.
Tutorial resources
These downloadable resources will be used to complete this tutorial:
Transcript
00:03
When creating a process flow in FlexSim,
00:06
the Decide activity sends a token to one of two or more possible activities based on conditions that you define.
00:13
From the Decide activity Quick Properties, you can define these conditions using many different methods,
00:19
such as diverting tokens to specific activities by case and by condition.
00:24
In this model, a process flow is already set up to represent shipments arriving with different types of items,
00:31
and each type requires a different length of time to process.
00:35
Items with longer times only need to be processed once, while items with shorter times need to be processed twice.
00:43
Two different types of Decide activities are used in the process flow to execute this model—Decide by case and Decide by condition.
00:52
In the ProcessFlow, click the first Decide—named Is Type 2?—to open its Quick Properties.
01:01
This Decide is set up to query the type of item and then send it to its respective processor by case.
01:07
Below the name, the Send Token To drop-down determines the logic used by the Decide.
01:14
Here, it is set to Connector By Case.
01:17
You also see the Connectors Out menu, with the Yes Connector selected,
01:22
as well as a Name of Yes, a destination of Acquire Long Processing, and a Rank of 2.
01:30
Click Edit Properties to view or set the specific criteria for each connector.
01:35
For this example, the Case Function is set to token.Type.
01:40
Under Setup Cases, Default is set to Connector 1, and Type 2 is set to Connector 2.
01:48
This means that the Decide uses the token’s type to determine its path.
01:52
Then, it sends Type 2 items to Long Processing, or the Yes connector,
01:57
while it sends tokens with types other than 2 to Short Processing, or the No connector.
02:03
After items finish Short or Long Processing, the next step in the flow is to keep track of how many times each item is processed.
02:11
Click the second Decide activity—Needs More Processing?—to see that Send Token To is set to Conditional Decide.
02:20
In the Connectors Out menu, the No connector is selected, which sends tokens to the Final Queue.
02:27
Click Edit Properties to view or set the conditions for this activity.
02:31
Here, the Condition field is set up to detect tokens that are not type 2, and to check for tokens processed fewer than 2 times.
02:40
If both conditions are true, then the token enters connector 1, or the Yes connector.
02:46
This returns the token to the Initial Queue to be processed a second time.
02:51
If one or both conditions are false, then the token enters connector 2, or the No connector, and proceeds to the Final Queue.
02:59
Reset and Run the simulation to see this in action.
03:03
The items in Long Processing take longer, however they flow directly to the Final Queue.
03:09
Items in Short Processing move more quickly, but return to the Initial Queue for a second round of processing.
03:16
Now you can use a Decide activity in your process flow to divert tokens to specific activities, by case and by condition.
00:03
When creating a process flow in FlexSim,
00:06
the Decide activity sends a token to one of two or more possible activities based on conditions that you define.
00:13
From the Decide activity Quick Properties, you can define these conditions using many different methods,
00:19
such as diverting tokens to specific activities by case and by condition.
00:24
In this model, a process flow is already set up to represent shipments arriving with different types of items,
00:31
and each type requires a different length of time to process.
00:35
Items with longer times only need to be processed once, while items with shorter times need to be processed twice.
00:43
Two different types of Decide activities are used in the process flow to execute this model—Decide by case and Decide by condition.
00:52
In the ProcessFlow, click the first Decide—named Is Type 2?—to open its Quick Properties.
01:01
This Decide is set up to query the type of item and then send it to its respective processor by case.
01:07
Below the name, the Send Token To drop-down determines the logic used by the Decide.
01:14
Here, it is set to Connector By Case.
01:17
You also see the Connectors Out menu, with the Yes Connector selected,
01:22
as well as a Name of Yes, a destination of Acquire Long Processing, and a Rank of 2.
01:30
Click Edit Properties to view or set the specific criteria for each connector.
01:35
For this example, the Case Function is set to token.Type.
01:40
Under Setup Cases, Default is set to Connector 1, and Type 2 is set to Connector 2.
01:48
This means that the Decide uses the token’s type to determine its path.
01:52
Then, it sends Type 2 items to Long Processing, or the Yes connector,
01:57
while it sends tokens with types other than 2 to Short Processing, or the No connector.
02:03
After items finish Short or Long Processing, the next step in the flow is to keep track of how many times each item is processed.
02:11
Click the second Decide activity—Needs More Processing?—to see that Send Token To is set to Conditional Decide.
02:20
In the Connectors Out menu, the No connector is selected, which sends tokens to the Final Queue.
02:27
Click Edit Properties to view or set the conditions for this activity.
02:31
Here, the Condition field is set up to detect tokens that are not type 2, and to check for tokens processed fewer than 2 times.
02:40
If both conditions are true, then the token enters connector 1, or the Yes connector.
02:46
This returns the token to the Initial Queue to be processed a second time.
02:51
If one or both conditions are false, then the token enters connector 2, or the No connector, and proceeds to the Final Queue.
02:59
Reset and Run the simulation to see this in action.
03:03
The items in Long Processing take longer, however they flow directly to the Final Queue.
03:09
Items in Short Processing move more quickly, but return to the Initial Queue for a second round of processing.
03:16
Now you can use a Decide activity in your process flow to divert tokens to specific activities, by case and by condition.