On-shift activation

[maryamh11]

[ FlexSim 23.2.2 ]

Hi there,

In the model attached, how do we make sure that when operators switch from off-schedule state/location to getting to work, they check whether the count of active operators within their designated group falls below a predefined threshold? So, they only start into on-shift mode if the number of active operators in their group is below a certain limit. So, how is that possible?

TimeTable_ObjectProcessFlow_24.0.fsm

[jason_lightfoot_adsk · Accepted solution]

Where did you define your threshold? Can't you set the number of operators as a parameter instead?

[maryamh11]

Currently, I haven't defined any specific threshold. If I designate the number of operators as a parameter, would the operators in shift 2 wait until those in shift 1 complete their tasks before taking over?

[jason_lightfoot_adsk]

Instead of acquiring and releasing resources, give the jobs to a dispatcher. Then close the inputs of the operators when they go offshift and open the inputs when they come on shift.

[maryamh11]

@Jason Lightfoot can you show how we give jobs to dispatcher?

I never used it actually.

[jason_lightfoot_adsk]

Here's an example.

timetable-objectprocessflow-240_jl.fsm

The difference is that you connect the operators to the dispatcher output, and create task sequences and send them to a dispatcher.

You can also set the off shift task to be preempting and have the output of the operator go back to the dispatcher - so that interrupted jobs get sent to a different operator.

[maryamh11]

@Jason Lightfoot

Got it, thanks. Are we specifying the number of operators in each shift using Parameters then here?

[jason_lightfoot_adsk]

Here's an example using the Dispatcher objects as the references for the number of operators parameters, and timetables to stop/resume the inputs.

In this example I've used a third dispatcher to create the jobs and route them to the operators, but you could instead pull the operators from a list or acquire them as a resource and test that their inputs are open (as a dynamic list field expression, for example).

timetable-objectprocessflow-240_jl2.fsm

To constrain the number working in an area you should use a Zone.