Paul Toone avatar image
Paul Toone posted


operators can be called by objects to be utilized during setup, processing or repair time. They will stay with the object that called them until they are released. Once released, they can go work with a different object if they are called. They can also be used to carry flowitems between objects. operators can be placed on a network if they need to follow certain paths as they travel.


The operator is a sub-class of the TaskExecuter. It implements offset travel depending on whether there's in an involved item for the offset. If there is no item, then it implements the offset exactly like the TaskExecuter. It travels so that its x/y center and z base arrives at the destination location. If there is an involved item, then the operator only travels along the x/y plane. It also only travels up to the point where its front edge is at the edge of the flow item, instead of its x/y center. This done by decreasing the total travel distance by (xsize(operator) / 2 + xsize(item) / 2).

The operator has animations in order to Walk, Walk Loaded, and Stand. These animations can be viewed in the Animation Creator by right clicking an Opearting and selecting Edit > Animations....


As mentioned above, the xsize of the item is queried to decrease the total offset distance. This may not work perfectly if you have flowitems whose x size is very different from their y size, and the operator approaches from the y side of the flowitem. If this is the case, and you want it to look more exact, you could try switching x and y sizes of the item and rotate it 90 degrees right before the operator picks it up, then undo those changes from the operator's load/unload trigger.


This object follows TaskExecuter states.

Properties pages


Related Topics

Task Sequences

flexsim users manual
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.



paul.t contributed to this article


FlexSim 2016.1