question

Kevin S7 avatar image
0 Likes"
Kevin S7 asked Ryan Clark edited

Improve process flow

Buenos días, ¿cómo puedo corregir este error? Quiero darle prioridad al hecho de que cuando el operador ha terminado de traer la cola 5,6,7 al combinador, los operadores se quedan ahí en el tiempo de proceso que está en el combinador una vez finalizada esa opción el operador puede empezar de nuevo a cargar los productos y así sucesivamente


CARGAR 1.fsm


FlexSim 21.2.4
combineroperatordispatcher
load-1.fsm (33.5 KiB)
· 1
5 |100000

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

Ryan Clark avatar image Ryan Clark commented ·

Hi @Kevin S7, 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 unaccept and comment back to reopen your question.

0 Likes 0 ·

1 Answer

Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Ryan Clark edited

To have the operators stay at the combiner activate the "Use Operator" option on them. To make sure that the operators are not currently busy with the process flow transport task I placed a "Wait for Event" activity in front of the release activity that frees up the queue. This activity is waiting for the combiner to finish the process, so no new transport tasks will be given before the process is complete. Finally, I also added the "On Exit" trigger of the combiners to the "Wait for Item Exit" acitivity further up, to have the token reevaluate the acquire queue activity once the combining process has finished.

A quick tip/note:
It's much easier to properly plan how to approach building a model, if the entire process you want to represent is known from the start. Building one part and then expanding it often leads to unnecessary rebuilding/remodeling, because some requirement was not taken into account previously.

load-prue-tasksequence_1.fsm


· 7
5 |100000

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

Kevin S7 avatar image Kevin S7 commented ·

@Felix Möhlmann

Good evening, how can I do to keep track of each product that enters and leaves to know the time it takes for that product from entry to exit

0 Likes 0 ·
Felix Möhlmann avatar image Felix Möhlmann Kevin S7 commented ·
Use a trigger on the source to store the creation time in a label on the item (Model.time returns the current run time of the model). Then use another trigger at the exit to write the difference between the current time and that label to a global table.

Since the items don't leave individually but packed on a pallet, you will have to loop over all subnodes of the pallet in a custom code. That would look something like this (in this example the label the creation time is stored on is called "EntryTime"):

// Loop over all items inside the "mainitem" (pallet)
for(int index = 1; index <= item.subnodes.length; index++)
{
    // Add a new row to the global table with name "tableName"
    Table("tableName").addRow();
    // Write the staytime into the first column of the new row
    Table("tableName")[Table("tableName").numRows][1] = Model.time - item.subnodes[index].EntryTime;
}
0 Likes 0 ·
Kevin S7 avatar image Kevin S7 Felix Möhlmann commented ·

Good morning friend, I am wrong when I apply that, can you help me with an example please? It is for this same model that I want to apply

0 Likes 0 ·
Show more comments