AGV vs Transporters on paths

Question

question

Patrick Cloutier asked Apr 21, '17 Maston Lyons answered Apr 24, '17

AGV vs Transporters on paths

I'm trying to understand the difference between the behavior of "regular transporters on paths" vs AGVs on those same paths. I'm taking about the behavior difference in Flexsim, not in real life.

I have to model a factory to evaluate the impact of implementing AGVs instead of the current operator driven transporters. I was planning to build 2 models. The first one of the current system with transporters on paths and then another model with AGVs on paths instead.

The main differences between the 2 models will be: speed, load/unload times, distribution throughout the plant instead dedicated per zone.

So now I'm wondering if I really need 2 models to model the 2 scenarios or if I can't model both scenarios with the same model using AGVs instead of transporters. That would save me and my client a lot of time.

In other words, can I use AGVs to model the current operator driven transporters? What are the reasons not to?

Software Version:

FlexSim 17.1.0

agv transporters

· 2

Patrick Cloutier commented · Apr 21, 2017 at 07:19 PM

As you can see from my question, I have not used the AGV module at all so please feel free to correct my logic.

0 ·

David Seo commented · Apr 22, 2017 at 10:12 PM

AGV objects of TaskExecuter can run without AGV module.

They have excellent behaviors in both network-node and AGV module.

You will find the difference if you use AGV instead operators in your current model.

0 ·

Answer 1 · 2017-04-23T04:13:54Z

Joerg Vogel answered Apr 23, '17

It doesn't depend on the exchange of the taskexecuter class object if you can use the AGV module for both scenarios. It depends on how you build the difference in the behavior of the module in general. The AGV module is able to drive the connected taskexecuter class objects the same way as you would it expect just from taskexecuter object. But in reality there are some differences if there is an operator that drive the transporter instead of a automated dispatcher system. The backbone is the same in both models path network, load- and unload stations, parking areas. But the load and unload process depends on the installed features of the AGV. If the AGV hasn't got a feature like the fork and thus another object does the loading you have to build this in the logic of the AGV module behavior. Another difference is the travel direction. An AGV can drive always in both directions. A transporter doesn't. If the size of loaded item block the sight to the pathway the transporter travels backward to get the sight again. Then differs the route of the two vehicles. But this has got an influence to the access of other members on network, too. AGVs might pass the loading area transporters won't in nearer aisles.

Answer 2 · 2017-04-24T15:22:58Z

Maston Lyons answered Apr 24, '17

Do your AGV's need to pull items as trailers? AGV Network makes this easy to implement.

Answer 3 · 2017-04-21T21:12:40Z

David Seo answered Apr 21, '17

If two models have only the difference of operator or AGV, you can use one model.

All properties of two transporter objects are same as you can find in the flexsim.

But there is something different behaviour in two transporter in real life.

question