Operators working simultaneously (task sequences) and aesthetics of operation.

Question

question

Adarsh Jeyes asked Oct 15, '17 Sam Stubbs commented Oct 19, '17

Operators working simultaneously (task sequences) and aesthetics of operation.

Hi all,

PFA a sample simulation model FYR, built in version 17.0.3.

01-query-2operatorsworking-15oct2017.fsm

In this model, I have Operator1 working on Table1 (process time: 10s) on 8 parts one after the other, and placing the parts on Table2 (process time: 30s) for Operator2 to work on.

Question 1:

This is regarding operation. If Operator1 completes all his 8 parts and has transferred it to Table2, I want Operator1 to work on parts left on Table2 simultaneously with Operator2. For example, once Operator1 completes 8 parts and places it on Table2, where Operator2 has only completed 4 parts, Operator1 will pick up a part and work on it on Table2 (PT: 30s) and Operator2 will pick up another part and work on it on Table2 (PT: 30s) simultaneously with Operator1.

How can I make this happen?

Question 2:

This is regarding aesthetics. The operators are travelling through the tables to pick up and place the parts, and are not facing the table while working on a part.

1. How can I make the operators avoid walking through tables? (A solution without adding network nodes is preferred as the operator will be engaged in other tasks that require him not to be constrained to a network node.)

2. How can I make the operators face the Table/part while he is processing the part?

3. How can I show hand movements for the operators while they are working on the part?

Any help would be appreciated. Thanks!

Software Version:

FlexSim 17.0.3

operator animation task sequence

01-2opsworking-16oct2017.jpg (127.3 KiB)

01-query-2operatorsworking-15oct2017.fsm (39.7 KiB)

· 5

5 |100000

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

Adarsh Jeyes commented · Oct 18, 2017 at 09:49 AM

@Jörg Vogel @phil.bobo @Sam Stubbs

Could you guys help me out with this please?

0 ·

Kari Payton commented · Oct 18, 2017 at 01:36 PM

Have you tried the above using process flow? That's the only way I can think of that will quickly answer both questions? @Adarsh Jeyes

0 ·

Adarsh Jeyes Kari Payton commented · Oct 18, 2017 at 03:33 PM

Hi @Kari Payton, thanks for your response.

I am not very adept at using the Process Flow module yet. I have gone through the tutorials, and my understanding and usage of the PF module is limited in scope.

For this specific case, I was expecting to use some form of Task Sequences.

However, if PF works well, I shall try the same. Could you get me started on how I can approach this problem using PF?

0 ·

Joerg Vogel commented · Oct 18, 2017 at 02:47 PM

Normally the operators go to a position at the object they are working at. If there is a visual collision you can change the location of the shape of the object. Then the operators are still at the same location but you prevents the collision of the shapes.

0 ·

Adarsh Jeyes Joerg Vogel commented · Oct 18, 2017 at 03:37 PM

Hi @Jörg Vogel, thanks for your response.

Do you mean changing the location using the following command?

item.setLocation(x,y,z);

As you've mentioned, my requirement is that the aesthetics of the operation be realistic (avoiding visual collisions).

0 ·

Answer 1 · 2017-10-18T20:31:00Z

Sam Stubbs answered Oct 18, '17 Sam Stubbs commented Oct 19, '17

Another way to keep the Operators from walking through the table is to use a travel network. Here's an example of your model using an A*Star network to manage where the Operators can walk. Just remember to turn Offset travel off in the operator's properties.

9067-01-query-2operatorsworking-15oct2017.fsm

As to your first question, you can do as Jorg Suggested and use code to control the tasks and task execution of the Operators. An alternative would be as Kari stated, to use a process flow. Essentially you could use lists to push items to a list and then pull them in your Process Flow to work on them in batches. Acquire the operators as resources, have them load /unload or process the items etc. Then have a Decision activity determine whether the first operator has more boxes to work on, or if he should be "released" and acquired by the other operation table to help process those items. Then just loop back around with the logic. If you need to see an example of this, let me know and I might be able to make one for you.

9067-01-query-2operatorsworking-15oct2017.fsm (40.9 KiB)

· 2

5 |100000

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

Adarsh Jeyes commented · Oct 19, 2017 at 12:43 PM

Hi @Sam Stubbs, thanks for your response!

The AStar navigator seems to work for aesthetics. However, the operator is travelling in circles, instead of staying on one side of the table.

Regarding the operation, I'm currently trying to build the logic using Process Flow as suggested by @Kari Payton. If I face any issues, I'll ask for help!

Thanks!

0 ·

Sam Stubbs ♦ Adarsh Jeyes commented · Oct 19, 2017 at 02:12 PM

Okay. If you don't want the Operators to travel to the far side of table , you can block their path to it using the barrier objects found in the A*Star network.

0 ·

Answer 2 · 2017-10-18T15:39:30Z

Joerg Vogel answered Oct 18, '17 Adarsh Jeyes commented Oct 19, '17

I adjust the standard transport tasksequence and utilze tasksequence in the OnReceiveTaskSequence Trigger of the Operator.

adjust-offset-travel-on-receive-ts.txt

in combination of setting the location of the shape of the processor (table) y-value to 0.76 the operator stands in front of the table by forcing a rotation of the object to 90 degree.

change-offsettravel-in-standard-transport-tasksequ.jpg (146.7 KiB)

move-shape-of-object.jpg (140.5 KiB)

adjust-offset-travel-on-receive-ts.txt (1.4 KiB)

· 1

5 |100000

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

Adarsh Jeyes commented · Oct 19, 2017 at 12:39 PM

Hi @Jörg Vogel, thanks for your response!

I have tried your code on the model and here's what is happening:

1. Operation: There seems to be no change in operation of both operators. Operator1 finishes parts and puts it on Table2 queue and Operator2 picks that up and works on it, just as before. At the end, when Operator1 has finished 8 parts, he stands idle near Table2. However, I want him to pick up a part left in the Table2 queue and process it on Table2 simultaneously with Operator2, and repeat this sequence.

If I was to state the objective, it would be as follows:

"A batch of 8 parts have to get processed as quickly as possible. For this, once Operator1 finishes processing his batch of 8 parts, he should aid Operator2 in processing any parts left on Table2."

2. Aesthetics: Editing shape factors is offsetting the flowitem as well, causing it to be placed outside off the table (floating in mid air).

I have applied your code in the OnReceiveTaskSequence trigger of Operator1 and edited shape factors of Table1. Am I doing something wrong?

0 ·

question