If the other model uses the same process flow, then yes, you should be able to simply copy the new activity and the changes to the delay time assignment.
The token has a reference to the AGV. From its variables treenode, I get to the node of the AGV inside the navigators tree.
The navigator stores the following information:
- The distance the AGV has already traveled during its current movement. ('cachedTravelDist')

- The current travel path of the AGV. This path is split into sections by control points and transfers between paths.
- Each section contains information about the start position of the travel on that section (fromDist) and the end position (toDist). Both are given as distance along that path object.
- Each section also knows how far into the total travel distance the AGV will arrive at it (atTravelDist).

In this screenshot we see that the travel starts 0.1m along Path1. The AGV will then travel to the end of Path1 at 6.22m with a control point at 4.69m inbetween. So after a total travel distance of 6.12m it will transfer to Path8 at travel another 6.02m on it (from 0 to 6.02).
Together with the total travel distance from the picture above, this allows us to determine which section the AGV is currently on (by comparing the 'cachedTravelDist' to the 'atTravelDist' values. Once we know the section, we can calculate the current position on that path.