Hi @Sudheer R,
I walked through this part of the tutorial and I can see how this might be confusing. There is an important distinction between these two lists that I will try and clarify so you can see why both are being used.
In the AGV Process Flow, there is a default list called "AGVWork". This list is used by tokens that try and pull tasks from the list. The Staging1 and Staging2 Processors are sending requests to this list that basically tell the AGV Process Flow that, "Hey, I have a box that needs to be moved. Can I have an AGV come get the item from me?"
The Item List that we create in this tutorial, "ItemsReadyForDelivery", is to handle the items themselves. The Staging1 and Staging2 Processors push the items themselves to a list (rather than a request for transport). Then the LoadingDock pulls the items from the list "ItemsReadyForDelivery", which means that the items now have a place to go. How do they get there? ...They use the AGVWork list that has requested the help of an AGV to come move the item.
So, think of the AGVWork as a task list and the ItemsReadyForDelivery as an item list.
Send To Port only handles Items. Use Transport only handles Task Executers.
Hopefully this makes a little more sense. Let us know if you have more questions.