operators by task

[10Dulkar]

[ FlexSim 22.0.0 ]

I am working on a project where there will be many different types of operators working. I couldn't find an effective way to model this. For example: Electrical Crew will work on Electrical and may have 2 to 4 crews. Mechanical might have 2-4 crews. I am representing one operator as one crew. however I have to create multiple dispatchers and create multiple operators, use Parameters to play around with the number of operators etc. The model has become messy with connectors all over. I want to know if there is a efficient way to reduce the connectors and dispatcher object in the model.

Please check the snapshot.

Below 2 snapshot shows how I want to play around the number of Crews using parameters, When i vary the numbers that many operators will be created ( One operator is one crew). But I have to use dispatcher to create Crew different operator quantity.

[moehlmann_fe · Accepted solution]

You could use lists instead of dispatchers. Each operator pushes itself onto the respective list (structure TE's, mechanical TE's,...) in their "On Resource Available" trigger. The processors can then pull one from the respective list in the "Use Operator" option.

To limit the number of available operators, I would suggest to build a simple process flow that pulls some operators from the lists depending on the value in the parameters table.

By adding a switch-case (or if conditions) to the code in the processor option, you can also control which list is used through the parameter table. This is demonstrated on Processor1 in the attached model.

operatorByTask.fsm

[jason_lightfoot_adsk]

You could also partition a single list by the task/function name for a more scalable solution.

[ryan_c10]

Hi @sachin T3, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.