Best practice for handling 100+ operators

berkayguz — Sun, 10 May 2026 21:04:38 GMT

Hi everyone,

I am currently working on a model where I might eventually need up to 400 operators. So far, I have been dragging and dropping them manually into the 3D environment, but this approach is obviously not scalable.

Having this many operators present in the model is causing a major issue: I am using the A* navigation module, and having hundreds of idle operators standing around creates massive congestion, as they act as obstacles for each other and block the paths.

Since I won't need all 400 operators active at the exact same time, I want to handle them dynamically. My idea is to make them appear in the 3D environment only when they are assigned a task, and disappear when they are done.

What is the best practice and most performant way to handle this in Process Flow? I would appreciate any advice, workflow tips, or simple examples on how to set this up efficiently.

Thanks in advance!

Re: Best practice for handling 100+ operators

ezhilan-ak — Wed, 13 May 2026 10:57:54 GMT

Hi ,
You can utilize Process flow "People Activity" to dynamically create and remove operators from the Model, It works in A* as well as normal Network Node based flows.

However, I Feel, when you have large number of transporters in A* it may slow your model, caching the A* paths may help you.

topic Re: Best practice for handling 100+ operators in FlexSim Forum

Best practice for handling 100+ operators

Re: Best practice for handling 100+ operators