question

Hey @Sia Sengchoon193, my apologies for the delay.

The double ASRS is interesting, and getting it to work in your model will depend on how you want it to be used.

You can just copy and paste the object from the double-asrs.fsm model to your model. An error does occur if you try to use it with your Object Process Flow as is, but those errors can be worked around by modifying the On Receive Task Sequence trigger of ASRSvehicle1. You have to make the changes in the tree of ASRSvehicle2 since ASRSvehicle1 is not normally accessible from the 3D view. I am attaching your model with these changes already made to show you what that looks like (0517single-multi.fsm). I just commented out the rest of the code in the On Receive trigger since it isn't actually doing anything anyway.

Within the attached model, the two ASRSvehicles will kind of take turns handling the work. However, ASRSvehicle1 won't ever move to get in place when loading and unloading items since ASRSvehicle2 is the one that handles those movements. The double-asrs.fsm model works better with this type of movement since it sends two Task Sequences at the same time, and the load and unload locations are the same locations for both task sequences.

If you want to make it so both vehicles work on separate tasks at the same time, you can just change the Source in the Process Flow to create two tokens:

However, ASRSvehicle1 still doesn't move to the location of the items when picking them up or dropping them off.

If you want to make it so the two vehicles act together, that will require recreating the Process Flow with the double ASRS in mind. It will probably require using the Split, Join, and Synchronize activities to handle controlling both vehicles at the same time, as a coordinated task sequence. You can send Task Sequences to the "main" vehicle, ASRSvehicle2, to handle travelling, and Load and Unload tasks to both when needed. With how it's currently set up, as long as ASRSvehicle2 is in the middle of a task sequence, a second task sequence that is sent will be passed straight to ASRSvehicle1. Otherwise, you would need to reference ASRSvehicle1 directly, which is possible, but a little tricky. The changes will also most likely need to handle when to use both ASRS vehicles or just one, and will probably be similar to how the Decide activities are being used in your original model.

Making these changes may fall out of the scope of the FlexSim support team. I will try to see if I can come up with something, and we can also see if anybody else in the community is willing to give it a try. You can also contact your local distributor about a possible consulting project if you want to go that route.

That being said, you can just add a second ASRS to your original model, attach it to the Object process flow, and run the model that way. Both ASRS vehicles will then just work independent of each other, but you won't need to worry about adding more complex logic to the Process Flow to handle the double ASRS.