Avoiding collisions with dynamically placed fixed resources

I am new to Flexsim and am looking for a good example of a model where an operator (task executor) uses collision to avoid dynamically placed fixed resources (a queue).
Problem Description:
I have a Pick to Light production line of 120 pick stations, each pick station is fed by a 1m feeder (in this case a queue). We have 10 extensions (also 1m long queues) which get added to the busiest feeders at the start of each production run.
All of the feeders are replenished by operators who pick replenishment stock off pallets and place it on the feeders. There are 2 replenishment operators who manage the whole line.
I could use network nodes and paths to direct the operators but would have to draw the network each new production run as the position of the extension feeders changes. What I was hoping to use is the collision handling capability to enable the replenishment operators to move around the extension feeders rather than walk through them. I have tried to use the collision but could get it to function and was unable to find out why from the manual.

I think it would be best if you could upload your model, because the explanation is quite complex and specific.

In general: Only Taskexecuter-Items can have collision spheres and no other objects.
As far as I understand, the best option would be to draw multiple network nodes, like a rectangular grid and set the networknode connections to nonpassing depending on where your queues are.



Note the green / yellow dots

I would definitely go for the path solution. Simply make the complete path with 2 nodes connected to your feeders (1 for the short one and the other for the long 1). You have to create and place the extensions anyway so if you let your operator go to the right extension it will automatically follow the correct path and you don't have to do anything with the pathnetwork. And if you need to do something use either close and open connections or use the defaultdragconnection command.

Reasons for doing it that way are:
1. This is much, much and I mean much simpler
2. Using the collisions detection makes your model slow, especially with a few operators. If you want to be accurate you have to test for a collision every second or maybe even faster that means that every second you place a number of events on the event list that have to be dealt with.

Thanks for the advice, I will avoid collision detection and layout a rectangular path network which I will then manage by restricting access in given directions.
Thanks