For relatively easy scaling I'd do it the following way:
On the queues where the pallets arrive, add labels to the item in the "OnEntry" that define three things. The y-position the momcar should travel to, to pick up the pallet, the soncar that transports the pallet to the elevator and the elevator itself.

In the process flow, after copying these labels to the token, they can then be used to acquire to correct objects. For this, two more groups, containing the elevators and "elevator soncars" respectively, were added and used as reference in the resources. In the acquire activity, the Query/Array/Object field is used to determine, which of the objects should be acquired from the resource.
The same labels are used to reference the objects in the travel and move activities.
The "y-Pos" label is in the "Travel to PickUp" activity to tell the momcar where it should drive to pick up the pallets from the elevator.
1003_1.fsm