Sequence Table - Destination as 'Node list property'

[mohmed Shaikh]

Hello All,

I am new to Simio and trying out a simulation of an aircraft component assembly shop.

I am using Sequence table for my jobs routing and processing scenarios which is -

Source -> Set A (4 servers) -> Set B (7 servers) -> Set C (5 servers) -> Set D (2 servers) -> Sink

Here each Set denotes similar workbenches to any of which a job can be routed based on utilization and availability at that point of time.

So for routing job based on above criteria from Source, I created sequence table with 'Node list property' (which is list of input nodes on 4 servers of Set A) instead of 'SequenceDestination Property' as required by Sequence table. I want to replicate the sequencing from Source -> Set A -> Set B and so on. But want simio to pick the server of these sets based on my criterion. 

Unfortunately it is not working as I assume Sequence table need to have specific node as SequenceDestination. I am not sure if I am doing it right or what is correct and way to do it.

I will highly appreciate any suggestions to make this happen in Simio. 

Thank  you.

-Mohmed

 

[CWatson]

You can still use your various 'lists' of servers in SetA, SetB, etc.). You still will need a Sequence table with the Sequence Destination property column. This tells Simio within the Sequence table the destination to route. So, within your Facility window, add a TRANSFERNODE before each 'set' of areas, let's say named SetA, SetB, SetC, SetD. Then, within the TransferNode, use the 'Select From List' for Entity Destination Type property and specify the appropriate list (SetAList, etc.). Then, within the Sequence table, route to the TRANSFERNODE that uses the particular list - so in the above, you would have within your Sequence table, SetA, SetB, SetC, SetD and Input@Sink. Within each of your Server's output nodes, specify Entity Destination Type as 'By Sequence'.  You may wish to look at the example named SchedulingDiscretePartProduction to see the layout of the nodes within each section and the Routings table used (this is a much larger example, but the concept of the nodes, the sequence table and in that case a RoutingDestinations table (which is like a node list in Lists) is basically the same.

[mohmed Shaikh]

On 4/29/2019 at 2:16 PM, CWatson said:

You can still use your various 'lists' of servers in SetA, SetB, etc.). You still will need a Sequence table with the Sequence Destination property column. This tells Simio within the Sequence table the destination to route. So, within your Facility window, add a TRANSFERNODE before each 'set' of areas, let's say named SetA, SetB, SetC, SetD. Then, within the TransferNode, use the 'Select From List' for Entity Destination Type property and specify the appropriate list (SetAList, etc.). Then, within the Sequence table, route to the TRANSFERNODE that uses the particular list - so in the above, you would have within your Sequence table, SetA, SetB, SetC, SetD and Input@Sink. Within each of your Server's output nodes, specify Entity Destination Type as 'By Sequence'.  You may wish to look at the example named SchedulingDiscretePartProduction to see the layout of the nodes within each section and the Routings table used (this is a much larger example, but the concept of the nodes, the sequence table and in that case a RoutingDestinations table (which is like a node list in Lists) is basically the same.

Many thanks CWatson. This worked. I was able to use 'Select from List' from the transfer node.