question

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.