question

@sang, there are flowitems as person. They can behave like any task executer (operator, vehicle, ..). You exchange the shape and let them travel like normal taskexecuter objects. Parking areas are Queues. The stacking option is deactivated. You let the flowitems travel by a tasksequence to a location and then you move the flow item from model space into the queue. You copy the location coordinates projected from model space into queue space.

A complete different approach is a variant of @steven.hamoen. The drivers are resources and the only taskexecuters in your model. They change their shape accordingly what they do. They become a car when they drive a car. You load the car into the driver object, you hide the shape of the person and only the car stays visible. If the car is in the ship or reaches its parking position you unload the car to this location for example into a queue and the taskexecuter unhide the person shape again. Then you can think of how the driver get to a next car to drive.

The driver goes to the location of a flowitem in AStar area or you let him travel by a set of “travel to location” tasks. Maybe you connect the taskexecuter dynamically to network node path systems acting for your street map.

It is an interesting model, you have to build.

@sang I didn't see a picture but my first idea would be to use the floorstorage objects to store the cars and A* to drive around. The cars can either be taskexecuters them selfs or use some mini forklifts to move the cars if they are just flowitems.