I have 3 operators and three processors. Operators are connected to the processors through a dispatcher. All the processors and operators are on the same schedule. However, the utilization % of operators differs from the utilization of processors. I am trying to understand why this can happen. Any insights?
I even exported the data from these graphs and made a pivot table. As you can see the seconds are also different.
Hi @mohammadmajd, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.
I noticed that the total non-excluded time of the processors is higher than that of the operarators.This is probably due to an unwanted side effect of all objects using the same time table. If an operator goes down while a processor is utilizing it, the processor's state will change to "Waiting for Operator". This also happens if the processor itself is down. As a result, if a processor goes down before its operator while it is active, it will spend the down time in the "Waiting for Operator" state. To work around this, make sure that the operators go down first by placing them at the top of the time table's members list.
This does not explaing the discrepency between the processing/setup and utilize times. I could not recreate that issue in a test model. Could you attach your model or an example model where the issue is present, so we can investigate further?
Sorry, I didn't notice you had uploaded the model.
The break times of the operators offer from those of the processors by 1 minute accross the board.
The operators start their break one minute earlier. During that time the processor is in the "Waiting for Operator" state. The operators also end their break one minute earlier. However, they still spend the time until the processor also resumes its process in the "Utilize" state. This results in an offset of 60s between the utilized times of operators and processors every time a break happens while a processor is in use.
Thanks. I made the one minute difference to make sure processor does not stay in "waiting for operator" state until the operator becomes available again. Instead of one minute I will change it to 1 second.
18 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
