Todos

Advanced Process Panel


Since systems can vary greatly in how they operate, Arena SE provides tools that can help model your complex system actions.

If the module constructs provided in the Basic Process panel do not capture the system logic at the required level of detail, the module constructs in the Advanced Process panel provide the ability to model complex systems actions.This adds enormous power and flexibility to your ability to represent a system.

The following examples discuss the functionality of the modules contained in the Advanced Process panel.




CONCEPTS AND TERMINOLOGY

Seize, Delay, and Release

Up to this point, all of our resources have been seized, delayed, and released using the options contained within the Processmodule. In order to facilitate more complex models, the Advance Process panel contains three separate modules for each of the actions.

The Seize module allows an entity to take control of a resource. This module can be used to halt the entity’s movement through the system until a desired resource is available.

The Delay module causes the entity’s movement through the system to be delayedfor a specified amount of time. When used without a Seize module, the Delay module will allow an infinite number of entities to enter and be delayed.

The Release module allows an entity to relinquish control of a resource. This module is always used in conjunction with a Seize module. If an entity tries to release a resource that is not busy, Arena will generate an error.

For allof the following examples, the Seize, Delay, and Release modules will be used in place of the Process module. However, feel free to use either in your models.




Queue Ranking

Sometimes work is not completed in a First In First Out manner. To allow you to model this situation, Arena provides the ability to rank the entities waiting in a queue based on several rules.First In, First Out – Entities entering a queue that try to seize a resource will be ranked according to the time that they entered the queue. The first entity to enter the queue will be the first entity in line to seize the resource. Entities will not “jump” line. This is Arena’s default.

Last In, First Out – Entities entering a queue that try to seize a resource will be rankedaccording to the time that they entered the queue. The most recent entity to enter the queue will be the first entity in queue.

Lowest Attribute Value First – Entities entering a queue that try to seize a resource will be ranked according to a user-specified attribute with the lowest value given priority.

Highest Attribute Value First – Entities entering a queue that try to seize aresource will be ranked according to a user-specified attribute with the highest value given priority.


Failures

By default in Arena, a resource is available 100% of the simulation time. In reality, resources usually will be unavailable due to a variety of reasons such as a tool breaking on a machine, a worker leaving the workstation for a few minutes, a power outage, or any otherreason.

These unexpected losses of a resource can be modeled using failures.

A failure can remove a resource based on a time or count.

The Preempt, Wait, and Ignore options for failures of a busy resource work similar to these options in the schedule spreadsheet.

Reflected in failed statistic (Frequencies section).

You may define multiple failures for aresource.


Advanced Process Example 1

Two different part types enter a toy paint shop where they will undergo several different processes before exiting the system. Part 1, a toy boat, arrives exponentially with a mean of 6 minutes. Part 2, a toy truck, arrives exponentially with a mean of 9 minutes.

Both part types then enter a Preparation process where they must seize an...