Designed new States in Subflow - How to insert my TimeTables

Question

question

Flexinator asked Nov 30, '23 Jason Lightfoot edited Dec 6, '23

Designed new States in Subflow - How to insert my TimeTables

Hi, i designed a Subflow with respect to my dispatcher to see, which of my operator is ulltilize on which processor. The problem is now, when my operator is starting the processing and he shuts down because of the time table, the subflow is still processing and i get a deviation into my dashboard results. I also put the processors into the timetable but still my subflow is running...How i can add the time tables into my subflow? I just have many subflows for each dispatcher btw.

Additional i have problems with the tokens in the Subflow. After the delay time the token is still in the delay Block and has got some delays that he goes down to the "FinishTS" block.

Thanks for your help!

SubFlow_Operator_assignment_state 1_4.fsm

Software Version:

FlexSim 23.1.0

subflow timetable

example.png (112.6 KiB)

subflow-operator-assignment-state-1-4.fsm (50.7 KiB)

· 2

Jason Lightfoot ♦ commented · Dec 04, 2023 at 05:54 PM

What do you want to happen?

1) Don't start the job if there's not enough time to finish before the down start

2) Preempt the operator away from the job and resume when the next shift starts

3) Wait unitl the job completes before the operator goes off shift

0 ·

Flexinator Jason Lightfoot ♦ commented · Dec 04, 2023 at 07:29 PM

Hi Jason, rather the second point. For example, he starts work 15 minutes before the break, then he has a break and then he has to continue working on it. So the token should stop when it is off time from the worker and then run again when the break is over. This gives me the correct utilization values for the respective operators for each processor

Thanks for your help!

0 ·

Answer 1 · 2023-12-04T22:13:32Z

Jason Lightfoot answered Dec 4, '23 Jason Lightfoot edited Dec 6, '23

Your subflow isn't running when the Operator is on a break. At time 3600 the Molding 1 process is scheduled to finish at 5407.8 - that's 1807.8 seconds. When the breakdown resumes at 14400 Moulding1 is scheduled to finish at 16207.8 which is the exact same 1807.8 seconds that should be remaining. I see no issue with this.

· 11

Flexinator commented · Dec 05, 2023 at 09:31 AM

Hi Jason, yes, you're right, the token only disappears when the remaining process time has expired due to the pause. I expressed myself badly. The problem is from time 14400 that operator1 has to return to the molding process to continue the work. Instead, it goes to the free printing process and on the state gantt you can see that 3 processors are working simultaneously, although there are only 2 operators in the model. That doesn't make sense and that's where I have my problems. Or are these just visual errors or are the SubFlow and the visualization not working synchronously? Or is the StateGantt not working correctly?

0 ·

1701768677183.png (10.4 KiB)

Flexinator Flexinator commented · Dec 05, 2023 at 09:46 AM

Is it possible that the operator thinks the task is finished because the exit time in the token is still regularly set to the time in the middle of the pause and therefore it changes the task? But the token itself is not finished. So, as it should be, the operator1 who last worked on the molding task continues to work on the molding task and finishes it. The same applies to operator 2 on the assembly. In this case, all 3 tasks are somehow started at the same time, although there are only 2 operators. It also confuses me visually

0 ·

Jason Lightfoot ♦ Flexinator commented · Dec 05, 2023 at 01:38 PM

Can I ask why you're using RunSubflow for the operator process dispatcher - why not just specify the operator directly?

0 ·

Show more comments

Jason Lightfoot ♦ Flexinator commented · Dec 05, 2023 at 01:23 PM

Sorry, I was focussed on the assertion of the subflow continuing while stopped and the event timing and didn't spot the operator going to the printer. We'll investigate some more.

I believe you should be using task type Utilize and stopRequestFinish for the operator rather than a delay but I'll check that along with the requirement to stop the machine when the operator is preempted from the Utilize task.

Also note that since you're sending the job back to the dispatcher, by default it can get reassigned to a different operator - there's no guarantee that Operator1 will get the Molding1 task after the break at the moment.

0 ·

question