Operator Control Issues

I want to set up a model where an operator is used for the cycletime and transport for every flow item. I want the operator to stay with the flow item (eventhough something else maybe trying to call him away) until the operator is no longer needed for either the cycletime or transport...say for example, if he dumps the flow item into a queue. What would be the easiest way of doing this? I'm writing an elaborate task sequence for this that is very, very difficult....must be a better way.


Gavin

Do I understand you write, that you try to build an "one piece flow"? For this there are some different ways. But at least the tasksequeces will be the cleanest way. You are wright, that this means much difficult work.

I would try it this way:
Put a reference to the operator on a label on the item (tonum(op)), so the same operator can be use in the tasksequences for that item . Use a table in which you mark your operators as occupied or free on the start and on the end of processing the item...

Gavin,

If your operator is connected to a dispatcher then you can achieve what you want rather simply.

First, when you first get the item you can close the input port of the operator. This will keep the operator from receiving any future task sequences until you open the input again later.

Second, the flowitem will need to have a label that stores a pointer to the operator. So, maybe in the OnLoad of the operator you can setlabelnum(item, "Operator", tonum(current)); or some other code that does the same thing.

Third, to get the operator to execute future task sequences you will need to bypass the closed input port by passing them directly to the operator. To do this you only need to use the reference that you stored on the item as the dispatcher when you create the new task sequence.

Fourth, when the time comes that you want to release the operator to be used by another item then you simply need to open the input port of the operator.

The only real problem with the approach above is that it would keep track of the time where the operator is being restricted by the item but not used as IDLE. So, to distinguish this time as something else you would need to set the state of the operator with some sort of delayed message at the end of each task sequence that you gave it. Or you could use another approach.

Good Luck,
Brandon