question

• How do you define the bottleneck:
  • machine least in working
  • waiting longest to setup
  • waiting longest to being unloaded
  • waiting longest to being loaded
  • product on machine most expensive so far or at the end of process
  • rise the priority by inactive time or costs equal on all machines or by attributes
  • and so on

• Do you need the operator for setup, process, load and unload tasks?
• Do you allow to stop a process to start on another machine a new job?
• How and when can the operator gets available?
• From which squenced steps of a process can the operator go away?

You can let the FlexSim engine set the order by using tasksequences and therein the priority parameter. Or you can push the different tasks or blocks of tasks to a list and query the most suitable block to be excuted next . A token contains the data to execute the tasks. You push this token to a list with fields that you use to set an order to your conditions. And when you pull the next job for the operator from the list you query the most prioritized token.

You put a block of tasks on a token that you cannot preempt ever, for example [load item from buffer, unload at machine, setup machine], [process], [load finished processed item, unload item], [clean machine], [maintain machine], [personal break].There are two blocks always available: [simply waiting for distinct time]. These blocks have got the lowest priority. But if nothing is to do the operator can always wait.

bumped