How can you prioritise which color comes first in the process? For example, if you want to make sure that in the queue Color red is taken priority in the queue before Process 1, how do you adjust for this? Thank you for your help!
You can control the RULES of the queue. When you use Seize-Delay-Release, you must specify at least one resource that entities have to wait for. They wait in a queue. You can see the queues of your model by clicking QUEUES in the basic process tab (where you also find the CREATE, PROCESS, DISPOSE, etc.). TYPE is a parameter of the queue that reflects that rule. The default is First in- First out (FIFO). Other alternatives are Last in, first-out (LIFO), or based on the value of an attribute of the entities. For example in a hospital, it would be the condition of the patient. You can sort ascending or descending on that attribute by selecting Lowest Attribute Value first, or Highest Attribute Value first.
I have a question about ARENA: is it possible to use different times in the same resource? For example, I have 3 types of trucks arriving and they have to be weighed on the same scale. Truck A is weighed in 03 minutes, truck B is weighed in 05 minutes and truck C is weighed in 7 minutes. After weighing, they are released and the process is closed. So, how to build this model in ARENA? Could you help me? Thank you in advance.
That is computed as a probability using queueing theory. P of waiting = 1-P0, where P0 is the probability of having zero customers in the system in a system with 1 server.
@@dralbertomarquez yes got my point but what about if we are dealing with complex models same situations arise in queueing, inventory, supply chain models... So how can one calculated probability of an event.... There so many events possible...
hello, would please help me with the decide module? Every time I run the model, the result of the decide module is exactly the same, why is that? I set the decide module with "N- way by chance"
How can you prioritise which color comes first in the process? For example, if you want to make sure that in the queue Color red is taken priority in the queue before Process 1, how do you adjust for this? Thank you for your help!
You can control the RULES of the queue.
When you use Seize-Delay-Release, you must specify at least one resource that entities have to wait for. They wait in a queue. You can see the queues of your model by clicking QUEUES in the basic process tab (where you also find the CREATE, PROCESS, DISPOSE, etc.). TYPE is a parameter of the queue that reflects that rule. The default is First in- First out (FIFO). Other alternatives are Last in, first-out (LIFO), or based on the value of an attribute of the entities. For example in a hospital, it would be the condition of the patient. You can sort ascending or descending on that attribute by selecting Lowest Attribute Value first, or Highest Attribute Value first.
I have a question about ARENA: is it possible to use different times in the same resource? For example, I have 3 types of trucks arriving and they have to be weighed on the same scale. Truck A is weighed in 03 minutes, truck B is weighed in 05 minutes and truck C is weighed in 7 minutes. After weighing, they are released and the process is closed. So, how to build this model in ARENA? Could you help me? Thank you in advance.
Yes, you can use sequences or attributes for having different processing times at the resource.
How to calculate the probability that an arriving entity has to wait in the process queue/area??
That is computed as a probability using queueing theory. P of waiting = 1-P0, where P0 is the probability of having zero customers in the system in a system with 1 server.
@@dralbertomarquez yes got my point but what about if we are dealing with complex models same situations arise in queueing, inventory, supply chain models... So how can one calculated probability of an event.... There so many events possible...
@@VLM234 the complexity is what makes the problem intractable, and justifies the need for simulation.
hello, would please help me with the decide module? Every time I run the model, the result of the decide module is exactly the same, why is that? I set the decide module with "N- way by chance"
The value of the criteria variable that you are using does not change from entity to entity