Chapter 1 – Introduction to Arena

1.1 Introduction
We will use Arena simulation software as an introduction to simulation modeling. The
parent company for Arena is Rockwell Software. As part of their continuous
improvement efforts, upgrades are made every couple of years. Most of the features are
the same from one version to the next; however, both obvious and subtle differences do
exist between versions. The user must pay great attention to detail in construction a
simulation model from using the modules in each panel to using the data modules to
adding both static and dynamic animation features to defining the run length to de-
bugging a model. Developing a new model from scratch can be a very tedious, but also
very rewarding, experience once the model runs to completion.
1.2 Arena Simulation Software
Arena is a user-friendly software package that is based on, and includes, the SIMAN
simulation language. Arena provides interchangeable templates of graphical simulation-
modeling and analysis modules that can be used to build a wide array of simulation
models. The modules are typically grouped into panels. By switching panels, you gain
access to a different set of modeling constructs and capabilities. In most cases, modules
from different panels can be used in the same simulation model.
 Chapter 2 – Elements of a Simulation Model
Various elements of a simulation model are discussed in this section, all in reference to
Sample Model 1 in Figure 2.1 below.

Figure 2.1. Sample Model 1.

2.1 Entities
Entities are the dynamic objects in a simulation. They are created by the analyst, move
around, and are then disposed as they leave the system. It is also possible to have
entities that never leave the system, they keep circulating within the system. All entities
are created by either the analyst or automatically by the Arena software.
Most entities represent real things in a simulation. You can have different kinds of
entities in the model, such as different kinds of parts, each possibly requiring different
processing times and routes, perhaps having different priorities within the system.
You can add “fake” entities that do not pertain to anything tangible but rather account
for certain modeling operations, such as creating a “breakdown” to model machine
failures. Alternatively, you can add “break” entities that arrive periodically to take a
server off duty.
Determining what your entities are is one of the first things the analyst should do in
construction a simulation model.
2.2 Attributes
An attribute is a common characteristic of all entities, but with a specific value that can
differ from one entity to another. Consider the specific value as a label, or tag, that is
attached to an entity but the value on the tag can differ across entities to characterize
them individually. The value of the label, or tag, does not change for the entity during
the model run. As an example, an attribute for an entity could be an arrival time, a
rework priority, a due date, color, and so on, all of which are unique to that entity. It is
up to the analyst to determine what attributes your entities need, name the attributes,
assign values to the attributes, and then use the attributes in your model. An attribute is
a local variable, meaning that they are local to each individual entity.
2.3 Variables
A variable (also known as a global variable) is a variable that reflects a characteristic of
the system, regardless of the number of or what kinds of entities may be in your model.
With global variables, the value of the variable can change during the simulation run.
For example, a variable can represent something that changes during the simulation,
such as the number of reworked parts going through a rework process or the number of
completed units that exit the system, which is incremented by a part when it enters the
area and decrements when it leaves the area.
Whereas the analyst can have many different variables in a model, each variable is
unique. Arena has two types of variables: Arena built-in variables (such as number of
parts in queue, current simulation clock time, status of a machine (busy or idle), etc.)
and user-defined variables (such as mean throughput time, utilization rates, labor cost,
net profit, etc.). Unlike attributes, a variable is not attached to any specific entity, but
rather pertains to the system at large. A variable is accessible by all entities, and the
value of a variable can be changed by any entity.
2.4 Resources
Entities often compete for service from resources, such as personnel, machines,
equipment, or space in a storage area. In everyday life, a resource, such as a worker,
seizes an entity, performs some activity, and then releases the entity to the next
operation when finished. However, in the Arena world, it is the entity that seizes a
resource, undergoes some activity, and then the entity releases the resource when
finished.
A resource can represent a group of several individual servers, each of which is referred
to as a unit of that resource. An example would be several identical “parallel” billing
clerks at a health insurance company. The number of available units of the resource can
be changed during the simulation to represent different work shifts, break times, etc. If
a resource has multiple units, or a variable number of units, the resource utilization will
be the time-average number of units of the resource that are busy divided by the time-
average number of units of the resource that are available.
2.5 Queues
The purpose of a queue is to hold an entity that needs to seize a resource in a temporary
waiting area, but the resource is currently tied up with another entity. All queues have
names and the names are typically the name of the process followed by a .queue, such
as Assembly.queue. Queues can take on any one of four different priority rules: first in,
first out; last in, first out, lowest attribute value, and highest attribute value. The analyst
would select the appropriate priority rule in the Queue data module.
2.6 Statistical Accumulators
As the simulation progresses, Arena keeps track of various intermediate statistical
accumulators, such as the number of parts produced so far, the total of the waiting times
in queue so far, the total time in the system by all parts that have exited the system so
far, and so on. All of the accumulators should be initialized to 0 at the start of the
simulation. This is done by going to Run > Setup > Replication Parameters, then
checking off the boxes for Statistics and System under the heading Initialize Between
Replications (see Figure 2.2). Whether the analyst is running one replication or multiple
replications, this sets the value of statistical accumulators back to zero for each
replication.

Figure 2.2. Dialog box for Initialize Between Replications in Run > Setup
2.7 Events
An event is something that happens at an instant of simulated time that may change
attributes, variables, or statistical accumulators. Examples of events include: 1) the
Arrival of a new part that enters the system; 2) the Departure of a part that exits the
system, and 3) a Terminating Condition, such as the end of the simulation run. Another
example is when a part leaves a queue and enters a machine center for processing. This
only occurs if the machine center is currently empty or when a previous part has
finished processing on that machine center and exits the machine, thus allowing the
next part in queue to replace it in the machine center.
Arena keeps track of events that are supposed to happen in the simulated feature in
an event calendar. When the model runs, a record of information pertaining to a future
event is placed on the event calendar. The event record contains information on the
entity involved, the event time, and the kind of event it will be. Arena stores each newly
scheduled event on the event calendar so that the next event is at the top of the event
calendar. When it is time to execute the next event, the top record is removed from the
calendar and the information in this event record is used to execute the appropriate
logic. Then the next scheduled event moves to the top of the event calendar. This event
action sequence is repeated until the end of the simulation run.
2.8 Simulation Clock
The variable called simulation clock stores the current value of simulated time during
the simulation run. The simulation clock in Arena does not track real time when
nothing changes between events. Rather, the simulated time lurches forward from the
time of one event to the time that the next event is scheduled to happen. How each
event is executed depends on the kind of event it is as well as the model state at that
time, but could include the updating of variables and statistical accumulators, altering
entity attributes, removing the top event on the event calendar, and placing newly
scheduled event records onto the event calendar.
2.9 Starting and Stopping Times
The analyst must determine the starting and stopping times for your model. Arena
cannot do this for you. For example, the analyst must determine the appropriate
starting conditions (such as starting at time 0 or build in a delayed start time), how long
a simulation run should last (such as the run length in seconds, minutes, hours, or
days), and whether the simulation run should stop at a particular time (such as
designating the run length) or whether the simulation run should stop when something
specific happens (such as designating a terminating condition such as a specific time at
the end of a work day). Assumptions should be consistent with what you are modeling.
 Chapter 3 – Navigating Through Arena
Various elements of the Arena window are discussed in this section, all in reference to
Sample Model 1 in Figure 3.1 below.

Figure 3.1. Arena Window

3.1 Elements of the Arena Window
3.1.1 Toolbars
The Toolbar section of the Arena Window consists of several templates that can be
added or deleted. The first template consists of the familiar icons from
MicrosoftTM WindowsTM operating systems. These icons include Create a new
document, Open Folder, Save, and so on. To the right of this template is a template with
features that one would see on media equipment, such as Go or Run, Lurch Forward,
Turbo Speed, Lurch Backward, and Stop or End Run. In the second row, we find
different shapes that we can copy/paste into our model. Some shapes, like the Square,
Call-Out, and Ellipse can be enlarged or reduced in size by dragging one corner of the
shape. Additionally, the color of these shapes can change by clicking on the Paint Can
icon, which opens up a color palette, and then you can select which color you desire. By
right-clicking on the shape, the analyst is afforded an option as to place it in front of or
behind modules. You would left-click on the option you desire and position the shape
where you want in your model. Other templates may be added as desired, such as
Animate Transfer or Transporter. To add other templates to the Toolbar, move your
curser anywhere in the Toolbar ribbon, right-click to open a drop-down menu, and then
left-click on the template you wish to add.
3.1.2 Project Bar
The Project Bar displays different Panels on the left-hand side of the Arena Window. It
can be moved to the right-hand side of the Arena Window, if desired, but the Project
Bar is normally kept visible while constructing your model. If you want to hide the
Project Bar,
In the Project Bar, we observe panels for Basic Process, Statistics, Advanced Transfer,
Advanced Process, Flow Process, Packaging, Reports, and Navigate in Figure 3.1.
Within each panel, a series of modules and data modules resides, each with its own
specific function.
The Basic Process panel consists of modules such as Create, Dispose, Assign, Process,
Batch, Separate, and Record. Modules from the Basic Process panel are used for new
parts or people entering the system, for various processes in the system, and for
assigning values for attributes and variables to name a few.
The Advanced Transfer panel consists of modules such as Station, Route, Convey,
Access, Exit, Request, Transport, and Free to name a few. The Advanced Transfer panel
is used when we want to animate our model and if we desire to include material
handling equipment such as conveyors or forklifts to transport materials.
The Advanced Process panel consists of modules such as Match, Hold, Seize, Store, and
Unstore to name a few. The Advanced Process panel is used to match different parts
into a kit and for holding, seizing, storing, or unstoring entities during a simulation run.
The Reports panel will display another panel containing a road map to the simulation
results after the model has run to completion. Click on this panel to make it visible.
Click on any other panel to make it visible again.
The Navigate panel allows you to display different views of a model, including
different submodels in a hierarchical model.
3.1.3 Flowchart View
The right-hand side of the Arena Window is split into two views: the Flowchart View
and the Spreadsheet View. The Flowchart View is where we will construct the logic
portion of our model. This consists of the infrastructure of our model (by dragging
Modules from the Panels into the Flowchart View) and may also consist of both Static
and Dynamic resource images, if desired. By double-clicking any module to open its
dialog box, we can enter additional information. Modules are the fundamental building
blocks of any Arena model. Flowchart modules, each with a distinctive shape, describe
the dynamic processes in the model.
3.1.4 Spreadsheet View
Data modules are located beneath the set of Modules in each Panel. We can enter
additional information here that we are not able to enter in the Flowchart View. When
we click on any data module, it automatically opens the Spreadsheet View below the
Flowchart View for that particular data module. If you are only able to see the
Flowchart View, move your curser down to “grab” the top of the Spreadsheet View and
pull it up so that you see both the Flowchart View and the Spreadsheet View on the
right-hand side of the Arena Window.
Data modules (look like small spreadsheets beneath the modules in each panel) define
the characteristics of various process elements, such as entities, resources, and queues.
Data modules exist behind the scenes in a model to define different kinds of values,
expressions, and conditions. Single-click any data module in the Project Bar and a
spreadsheet for that type of module will appear in the spreadsheet view of the model
window. You can edit data modules and also add rows by double-clicking where
indicated.
3.1.5 Status Bar
The Status Bar at the bottom of the Arena Window displays information such as
simulated run time, replication x of x number of replications, and coordinates of the
curser.
 Chapter 4 – Basic Process Panel
4.1 Modules
We will use Sample Model 1 in Figure 4.1 and Sample Model 2 in Figure 4.19 to discuss
both the Modules and Data Modules used from the Basic Process panel in this course.

Figure 4.1. Sample Model 1.

4.1.1 The Create Flowchart Module
The Create module (see Figure 4.2) is the “birth” node for entity arrivals to the system
from the outside.
Figure 4.2. Create module.
Double-click it to open a dialog box like the one in Figure 4.3.
Figure 4.3. Dialog box for the Create module.
The dialog box contains fields for different kinds of information related to this
particular module. In the Name field, you would type in a short descriptive name that
will become the label for this Create module. In the Entity Type field, you would type in
a descriptive entity name, such as a particular part name. In the Time Between Arrivals
section, select the appropriate probability distribution from the Type drop-down menu.
You will notice four choices: Random(Expo), Schedule, Constant, and Expression. Select
Random(Expo) if the time between arrivals follows an exponential distribution. Select
Schedule if the time between arrivals follows a certain schedule that you can build into
Arena (i.e., incoming parts arrive between 7am and 8am). Select Constant if the time
between arrivals follows a constant time, such as the time between arrivals is 2 minutes
for all parts. Select Expression if the time between arrivals follows any other
distribution. When you select an option, you will notice the Expression field in the
middle of the dialog box will change (see Figure 4.4).
Figure 4.4. The Expression drop-down menu in the Create module.
You can select the appropriate distribution and manually enter the parameter values in
parentheses to replace the text.
The Units field offers a drop-down menu in Figure 4.5. These are time units of
measurements for arrivals. Select the appropriate choice of seconds, minutes, hours, or
days.
Figure 4.5. The Units drop-down menu in the Create module.
In the Entities per Arrival field, enter the number of entity arrivals at a time. Entities
may arrive one at a time or in batches (i.e., batches of 5). In the Max Arrivals field, enter
the maximum number of entity arrivals. If there is a cap like, say, no more than 10
arrivals, then enter the number 10. If there is no cap on the number of arrivals, then
enter Infinite. The case in this field is non-sensitive to upper or lower case letters.
In the First Creation field, enter the time that the first part, or entity, is expected to enter
the system (see Figure 4.6). If the first part is expected to enter the system as soon as the
simulation begins, then enter the value of 0, or 0.0. If you want to build in a delay, such
as the first part enters the system 5.5 minutes after the simulation begins, then enter 5.5
here. Be sure you selected Minutes in the Units field so that 5.5 in this example means
5.5 minutes.
Figure 4.6. First Creation field in the Create module.
4.1.2. The Dispose Flowchart Module
The Dispose module (see Figure 4.7) represents the end of a trunkline of modules, such
as a process or a decision, or the end of the modeled system.
Figure 4.7. The Dispose module.
Double-click it to open the dialog box (see Figure 4.8).
Figure 4.8. Dialog box for the Dispose module.
Simply enter a descriptive name in the Name field. This will become the label on the
face of the Dispose module. Be sure the checkbox for Record Entity Statistics is checked
for all modules so that Arena captures this information during the simulation run. This
data will impact the results at the end of the simulation run in one of the output reports,
such as the Category Overview report or the SIMAN Summary Report.
4.1.3 The Process Flowchart Module
The Process module in Figure 4.9 is used to describe a process, such as a value-added
like Burn In or non-value-added process like Walking from point A to point B.
Figure 4.9. The Process module.
Double-click the Process module to open the dialog box (see Figure 4.10).
Figure 4.10. Dialog box for the Process module.
In the Name field, enter a descriptive name and this will become the label for this
particular Process module. In the Type field, we have two options: Standard or
Submodel. Select Standard if a submodel is not used in your model.
In the Logic section, we see four options for the Action field in Figure 4.11.
Figure 4.11. Four options in the Action field.
The Action selected pertains to the relationship between the entity and the resource, if
any. The option Delay means that the entity is in a holding pattern of sorts. No activity
is being performed on the entity. The Seize Delay option means that the entity has
seized a resource an activity is being performed on the entity (the delay). The Seize
Delay Release option means that the entity has seized a resource, an activity is being
performed on the entity (the delay), and then the entity is released to continue on to the
next destination. The Delay Release option means that the entity has an activity being
performed on it and is then released to continue on to the next destination. Note that
the selection of either Seize Delay or Seize Delay Release triggers two significant things:
(1) it will automatically create a queue line above the Process module; and (2) we need
to add at least one resource (see Figure 4.12).
Figure 4.12. Burn In Station as a Resource.
To add a resource, click the Add button next to the Resources window (see Figure 4.13).

Figure 4.13. Resource dialog box to add Resources.

In the Type field, there are two options: (1) Resource; and (2) Sets. Select Resource if you
want to add a machine, a person, or equipment. In the Resource Name field, enter the
name of your resource. In the Units to Seize/Release field, select the Default value of 1
if you want one resource to work on each entity. The resource in this example is a Burn
In machine so we want one Burn In machine to work on each entity. If we were to enter
a different number here like, say, 5, then this means we need 5 Burn In machines to
work on each entity. If your resource becomes a bottleneck operation and you need
more than one resource to work on the shift (or day), then you would change the
number of resources needed in the Resource data module, not in the dialog box in the
Process module. For example, if you needed 5 Burn In machines on the shift but each
Burn In machine works on only one entity, then change the fixed capacity to 5 in the
Resource data module but keep retain the value of 1 in the Units to Seize/Release
dialog box in the Process module.
There are three options in the Priority field: High (1); Medium (2), and Low (3). Select
the appropriate priority.
The Delay Type section represents the processing time for the entity (see Figure 4.14).
Figure 4.14. Expression drop-down menu for Delay Type.
The drop-down menu for Expression provides the choices of Constant, Normal,
Triangular, Uniform, and Expression. Select Constant and enter the value in the
appropriate time unit of measurement if the processing time is constant, such as a 30
second Stamping operation. Select Normal if the processing time follows a Normal
distribution. Then enter the mean and standard deviation values. Select Triangular if
the processing time follows a Triangular distribution. Then enter the minimum, most
likely, and maximum values. Select Uniform if the processing time follows a Uniform
distribution. Then enter the minimum and maximum values. Otherwise, select
Expression (see Figure 4.15).

Figure 4.15. The Expression drop-down menu.

The Expression can be one of the probability distributions from the drop-down menu or
it can be a label, such as Burn In Time that we see in Figure 4.15. If you select a
probability distribution, then enter the appropriate parameter values. If you enter a
label, such as in our example, then the processing time values will appear in preceding
Assign modules but will be referenced by the Expression labeled Burn In Time. This
technique is employed when different entities pass through the same Process module,
but with different processing times.
Be sure to select the appropriate Units (seconds, minutes, hours, or days) and whether
the Allocation field should be Value Added or Non-Value-Added.
4.1.4 The Decide Flowchart Module
The Decide module allows for decisions to be made. The entity will be routed in a
certain direction depending on whether the decision takes on the value of True or False
(see Figure 4.16).
Figure 4.16. The Decide module.
Double-click to open the dialog box in the Decide module (see Figure 4.17).

Figure 4.17. Dialog box for the Decide module.

Enter a descriptive name in the Name field. This will become the label on the face of the
Decide module. In the Type field, we see four options in Figure 4.18.
Figure 4.18. Four options in the Type drop-down menu.
Select 2-way by Chance if there are only two possible outcomes, such as Pass/Fail or
Good/Bad. Select 2-way by Condition if there are only two possible outcomes based on
a condition that you define. Select N-way by Chance or N-way by Condition if there are
more than two possible outcomes for Chance or Condition. Enter the value for Percent
True (anywhere from 0-100%) based on what you entered in the Name field. The True
outcome will be routed one way and the False outcome will be routed another way.
Note that the Percent True value must align with the Name of your Decide module so
that the entity is correctly routed.
4.1.5 The Batch Flowchart Module
Sample Model 2 in Figure 4.19 is used to illustrate the Batch and Separate modules.
Figure 4.19. Sample Model 2 with Batch and Separate modules.
The Batch module (see Figure 4.20) is used to batch different entities into a “kit.”
Figure 4.19. The Batch module
Double-click to open the dialog box for this Batch module (see Figure 4.20).
Figure 4.20. Dialog box for Batch module.
Enter a name in the Name field that will be used as the label for the Batch module. In
the Type field, we have two options: (1) Permanent; and (2) Temporary. Make the
appropriate selection. In the Batch Size field, enter the number of different entities
needed to form a “kit.” In this example, three different entities (Leg Stock, Seat Stock,
and Hardware) form a kit. In the Save Criterion field, you will see four options: First,
Last, Sum, and Product. Select the appropriate option. For example, the option named
First will group the first of all different entities in the respective queues into a kit. In the
Rule field, you will see two options: Any Entity and By Attribute. If you are not using
attributes to define entities, then select Any Entity. In the Representative Entity Type
field, enter the name of the “kit.” This becomes a new entity in the model, in addition to
the entities previously defined in all Create modules in the model. You will also note
that a queue line is automatically created above the Batch module once you exit the
completed dialog box.
4.1.6 The Separate Flowchart Module
An example of the Separate module from Sample Model 2 is shown in Figure 4.21.
Figure 4.21. Separate module.
Double-click the Separate module to open the dialog box (see Figure 4.22).

Figure 4.22. Dialog box for Separate module.

Enter a name in the Name field. This will become the label for the Separate module. In
the Type field (see Figure 4.23), you will see two options: Split Existing Branch and
Duplicate Original.
Figure 4.23. Dialog box for Type field in Separate module.
Select Split Existing Branch if you desire to break down a “bulk” unit into individual
units. By selecting Split Existing Branch in Figure 4.24, the Member Attributes field will
display a drop-down menu consisting of three options: Retain Original Entity Values,
Take All Representative Values, and Take a Specific Entity Value. Make the appropriate
selection.
Figure 4.24. Dialog box for Split Existing Branch > Member Attributes field.
If you select Split Existing Branch > Retain Original Entity Values and the model
crashes when running, change your selection to Duplicate Original. The model might
crash due to short inter-arrival times of entities into the system. That is, entities are
entering the system at a faster rate than can be processed. We would want to retain
these inter-arrival times, rather than change them, because they represent the real
scenario we are trying to model.
Select Duplicate Original if you desire to duplicate the original entity. Be sure to make
connections from the Original and Duplicate output nodes to the next destination. In
the Percent Cost to Duplicates field, enter 100, meaning duplicate 100% of the original
entity. In the # of Duplicates field, enter the appropriate value. For example, if you are
separating a piece of wood stock into four legs for a chair, then the Original value is 1
and the # of Duplicates is 3, which makes a total of 4 legs per chair.
4.1.7 The Record Flowchart Module
An example of the Record module from Sample Model 1 is shown in Figure 4.25.
Figure 4.25. The Record module.
The Record module records statistics like throughput time (also known as cycle time)
and counts of units.
Double-click to display the dialog box for the Record module as shown in Figure 4.26.

Figure 4.26. Dialog box for Record module.

Click the Add button to add a new statistic that you would like Arena to monitor (see
Figure 4.27).
Figure 4.27. Statistic Definition dialog box for Record module.
In the Type field in Figure 4.28, a number of options are given, such as Count, Entity
Statistics, Time Interval, Time Between, and Expression.
Figure 4.28. Type dialog box for Statistic Definition.
Select Count if you want Arena to Record a count of entities passing through a point in
your model. Select Entity Statistics if you want Arena to Record throughput, time, and
cost for the entity type of the active entity. Select Time Interval if you want Arena to
record the cycle times of all entities. Select Time Between if you want Arena to record
the difference between the current simulation time and the time the last entity executed
this Record module for the Tally name specified. You would then have to specify the
Tally name in the field given. Select Expression if you want Arena to Record the value
specified for the Tally name specified. Here, you would have to enter a value and the
Tally name. Also note that the analyst is given the option to checkmark the box marked
Record into Set. This allows Arena to Record statistics into a Set by Set Index (a
previously defined entity selected from the drop-down menu) defined by the analyst in
the Sets data module. An example of a completed dialog box with Record into Set
checkmarked is shown in Figure 4.29.

Figure 4.29. Completed dialog box with checkmarked Record into Set.
4.2 Data Modules
Data modules define the characteristics of various process elements, such as entities,
resources, and queues. They can also be used to set up variables and other types of
numerical values and expressions that pertain to the entire model. The icons for data
modules look like small spreadsheets in the Project Bar below the Modules section. Data
modules for the Basic Process panel include Attribute, Entity, Queue, Resource,
Variable, Schedule, and Set. Other panels contain different sets of data modules.
Data modules exist “behind the scenes” and define different kinds of values,
expressions, and conditions. To edit a data module, click on it in the Project Bar and it
will automatically appear in the Spreadsheet view of the Model Window, below the
Flowchart view. If the Flowchart view takes up the entire Model Window, move your
cursor down to “grab” the top of the spreadsheet view and pull it up into view. Unlike
Modules that may be used more than once in the Flowchart, there is only one of each
type of data module in every model. Within each data module, however, there may be
any number of rows that correspond to what is included in the model for that type of
data module.
Flowchart and data modules in the model are related by the names for objects that they
have in common, for example, queues, resources, entity types, and variables. Arena
stores in memory the names of objects the analyst defines and then presents these
names in a drop-down menu in the appropriate places in the flowchart and data
modules. This helps the analyst to remember what you’ve named things and maintains
consistency in the model development.
4.2.1 Attribute Data Module
By clicking on the Attribute data module in the Project Bar, the Attribute spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 4.30.
Figure 4.30. The Attribute data module.
In this example, we observe four rows in the Attribute data module, each row
representing a different Attribute included in the model. In the Data Type column, we
are given two options in the invisible drop-down arrow to the right of this field: Real
and String. If you select String, double-click to add new attributes or select those you
wish to edit. The value of the string attribute is assigned via the ReadWrite module. In
most cases, the analyst would opt for Real to show real numbers rather than a string of
numbers. In the Initial Values column, the Default is 0 rows. If an Attribute needed an
initial value other than the value of 0, then click to add a row, then enter the initial
value. If the Attribute’s initial value is 0, then do nothing.
4.2.2 Entity Data Module
By clicking on the Entity data module in the Project Bar, the Entity spreadsheet opens
up at the bottom of the Model Window, as shown in Figure 4.31.
Figure 4.31. The Entity data module.
The Entity data module shows all entities currently in the model in the Entity Type
column. Entities are typically added in the Create module; however, an entity can also
be added in the Batch module by entering a new entity name. In the Initial Picture
column, a drop-down menu exists that displays numerous entity pictures, arranged in
alphabetical order as shown in Figure 4.32. Select an entity picture to represent the
given entity. Initial cost values can be manually entered in the various cost columns, if
appropriate.
Figure 4.32. Drop-down menu for Initial Picture in the Entity data module
spreadsheet view.
4.2.3 Queue Data Module
By clicking on the Queue data module in the Project Bar, the Queue spreadsheet opens
up at the bottom of the Model Window, as shown in Figure 4.33.
Figure 4.33. The Queue data module.
By clicking on the Queue data module, the Spreadsheet view displays rows for each
queue in the model. In the Name column, we see the name of each queue, which
follows the pattern of the name of a Process followed by a .queue. The Type column
displays the priority rule used for each queue. A drop-down menu displays the
following options for the analyst to select: First In First Out, Last In First Out, Lowest
Attribute Value, and Highest Attribute Value. Select the appropriate priority rule for
each queue. If Lowest Attribute Value or Highest Attribute Value is selected, then select
the appropriate Attribute in the drop-down menu for the Attribute Name column. The
selected Attribute would be a previously defined Attribute in the model that was stored
in memory by Arena.
4.2.4 Resource Data Module
By clicking on the Resource data module in the Project Bar, the Resource spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 4.34.
Figure 4.34. The Resource data module.
By clicking on the Resource data module, the Spreadsheet view displays rows for each
resource in the model. The Name column displays all resources included in the model
by row. In the Type column, there are two options in the invisible drop-down menu:
Fixed Capacity and Schedule. Select Fixed Capacity if the analyst wants to edit the
number of each resource in the model by changing the capacity value in the Capacity
column. Select Schedule if the resource will be used based on some schedule to be
further defined in the Schedule data module. For example, a forklift driver in the
Receiving area might only unload incoming trucks between the hours of 7am-8am
rather than all day long. Values for the number of each resource that are busy or idle
per hour can be manually entered in the respective columns. The analyst can also build
in a Failure for a given resource, such as a machine breakdown. Failures can be added
by clicking to add a new row in the Failures column, then describing the type of Failure
and the Failure Rule (Wait, Ignore, Preempt) that should be applied (see Figure 4.35).
The Wait option will wait until the in-process entities release their units of the resource
before starting the actual capacity decrease. The Ignore option immediately decreases
the resource capacity, ignoring the fact that the resource is currently allocated to an
entity, but work (or processing) on the in-service entities continues unabated. The
Preempt option attempts to preempt the last unit of the resource seized by taking it
away from the controlling entity. If the preempt is successful and a single unit of
capacity is enough, then the capacity reduction begins immediately. If the preempt is
unsuccessful or if more than one unit is needed, then the Ignore rule will be used for
any remaining capacity.

Figure 4.35. Building in a Failure for a given resource.

Additional information regarding failures can be entered in the Failure data module in
the Advanced Process panel, as shown in Figure 4.36.
Figure 4.36. The Failure data module in the Advanced Process panel.
4.2.5 Variable Data Module
By clicking on the Variable data module in the Project Bar, the Variable spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 4.37.
Figure 4.37. The Variable data module.
By clicking on the Variable data module, the Spreadsheet view displays rows for each
variable in the model. The Name column displays all variables included in the model by
row. In the Data Type column, there are two options in the invisible drop-down menu:
Real and String. In the Clear Option column, three options are given: Statistics, System,
and None, so the analyst can choose which option to clear. The analyst may manually
enter initial values for each variable if it differs from zero. Else, the Default initial value
is zero.
4.2.6 Schedule Data Module
By clicking on the Schedule data module in the Project Bar, the Schedule spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 4.38.
Figure 4.38. The Schedule data module.
By clicking on the Schedule data module, the Spreadsheet view displays rows for each
type of schedule in the model. The Name column displays all schedules included in the
model by row. In the Type column, we observe three options: Capacity, Arrival, and
Other. Select Capacity or Arrival if a numerical value must be entered for Value and
Durations in the Durations column.
For example, if Arrival is selected for a schedule named PartsArrive, the values in the
Durations column would represent the number of resources needed in the Value
column and the number of time periods (i.e., hours) needed in the Durations column. In
Figure 4.38, the values in the Durations column for the schedule named PartsArrive is
interpreted as zero resources are needed for the first 7 hours, then one resource is
needed for the next hour, based on a 24-hour clock.
A similar logic applies if Capacity is selected. In Sample Model 2, Capacity represents
the WorkDay hours when a resource is or is not needed based on a 24-hour clock.
4.2.7 Set Data Module
By clicking on the Set data module in the Project Bar, the Set spreadsheet opens up at
the bottom of the Model Window, as shown in Figure 4.39.

Figure 4.39. The Set data module.

Recall that information in the Set data module was initiated in the Record module by
checkmarking the box labeled Record into Set. In the Name column, the name Finished
was entered in the Record module and is then transferred directly to the Set data
module. In the Type column, the options given are Resource, Counter, Tally, Entity
Type, and Entity Picture. The selected Type originated in the Record module. In the
Member Definition Method column, there are two options: Manual List and Data File.
The Default value is Manual List. If Counter is selected in the Type column, then
double-click in the Members column to manually add each Counter Name. This is an
important, but easy to overlook, step. This enables Arena to record statistics in the Set
named Finished by Board Types Part 602A and Part 917AT that were defined in our
Create modules. Otherwise, by forgetting to add the appropriate Counter Names in the
Members column, Arena would not know for which Members (or Board Types) to
record statistics. It could only obtain overall statistics rather than statistics broken down
by Member (or Board Type). Another way to count the number of units given that they
have been counted into a Set is to add a variable display with the expression. For
example, if we use the Set feature to count the number of different colors of marbles,
such as blue marbles, red marbles, green marbles, and purple marbles, we could use the
variable command, or expression, NC(blue marbles) to obtain the current number count
of blue marbles.
4.3 Defining the Run Length
We will use Sample Model 2 in Figure 4.40 to define the run length of a simulation
model.

Figure 4.40. Sample Model 2.

Click on the Run tab in the NavBar, then click on Setup to define the model run length,
as shown in Figure 4.41.
Figure 4.41. Run > Setup in Sample Model 2.
Click on Setup to open the Replication Parameters dialog box (see Figure 4.42).

Figure 4.42. Replication Parameters tab for Run > Setup in Sample Model 2.
You will notice seven tabs of which we will use only three: Replication Parameters,
Reports, and Project Parameters. From Figure 8.3, we see the dialog box for the
Replication Parameters tab. In the Number of Replications field, manually enter the
number of replications to wish to run. The Start Date and Time field automatically
displays the current date and time. In the Warm-up Period field, you can leave the
Default value of 0.0 or you can change this to a numerical value that is coupled with the
Time Units field, which offers options such as Seconds, Minutes, Hours, and Days,
thereby creating a warm-up period before the model gets to a normal operating
condition status. There are two ways to define a terminating condition, or the run
length, of your model: 1) enter values in the Replication Length and Time Units fields.
For example, the run length in Sample Model 2 from Figure 8.3 is 20 Days; or 2) enter an
expression in the Terminating Condition field. Enter a value in the Hours Per Day field.
In the Base Time Units field, select from the options in the drop-down menu: Seconds,
Minutes, Hours, or Days. Your selection here converts all time measurements in your
model to your chosen selection in the output report.
In the Reports tab shown in Figure 4.43, select from the choices in the drop-down menu.
Figure 4.43. The Reports tab for Run > Setup in Sample Model 2.
As you can see, there are quite a number of different output reports that Arena
generates when the model runs to completion. If the model crashes because it has one
or more bugs, or errors, in the model, an output report will not be generated. Two of the
most common output reports are the Category Overview report and the SIMAN
Summary Report. Both reports contain the same output information, albeit in different
formats.
The analyst can click on a radio dial to let Arena know whether to always display the
selected output report when the model runs to completion, or to never show the output
report, or to prompt the analyst for the selected output report. The analyst would then
have the option to accept or decline viewing the output report.
In the Project Parameters tab shown in Figure 4.44, the analyst can enter a Project Title,
the Analyst Name(s), and a brief description of what the simulation model represent in
the Project Description field.
In the Statistics Collection section, the analyst can check the boxes for which he/she
wants Arena to capture statistics during the simulation run. These results would be
incorporated in the output report.
Figure 4.44. The Project Parameters tab in Run > Setup for Sample Model 2.
 Chapter 5 – Advanced Transfer Panel
5.1 Modules
We will use Sample Model 3 in Figure 5.1, Sample Model 4 in Figure 5.6, and Sample
Model 5 in Figure 5.20 are used to discuss both the Modules and Data Modules used
from the Advanced Transfer panel in this course.

Figure 5.1. Sample Model 3.

5.1.1. The Station Flowchart Module
The Station module (see Figure 5.1) precedes a Process module and signals the arrival of
an entity at that process.
Figure 5.1. The Station module.
Double-click it to open the dialog box (see Figure 5.2).
Figure 5.2. Dialog box for the Station module.
Simply enter a descriptive name in the Name field. This will become the label on the
face of the Dispose module. The Station Type field offers two options: Station and Set,
meaning is the current Station module an individual station or is it part of a set? In the
Station Name field, click on the drop-down menu and select the appropriate previously
defined Station name that represents the current station. As the analyst adds more
Stations in the model, Arena will store the names of all Stations in memory and will
display the current list of Stations in appropriate places. Be sure the box marked Report
Statistics is checked.
5.1.2 The Route Flowchart Module
The Route module (see Figure 5.3) is used to route, or transfer, an entity from one
location to another.
Figure 5.3. Route module.
Double-click it to open a dialog box like the one in Figure 5.4.
Figure 5.4. Dialog box for the Route module.
The dialog box contains fields for different kinds of information related to this
particular module. In the Name field, you would type in a short descriptive name that
will become the label for this Route module. In the Route Time field, you would enter a
numerical value coupled with a time unit of measurement in the Units field (seconds,
minutes, hours, or days) to form the entity route time. In the Destination Type field,
there are four options: Station, By Sequence, Attribute, and Expression. (see Figure 5.5).
That is, in its next destination, will the entity be routed to a Station, by a Sequence, by
an Attribute (in which case the analyst must identify the Attribute), or by an
Expression?
Figure 5.5. The Destination Type drop-down menu in the Route module.
You can select the appropriate distribution and manually enter the parameter values in
parentheses to replace the text.
5.1.3 The Access Flowchart Module
Sample Model 4 in Figure 5.6 is used to discuss Modules pertaining to entity transfer,
such as a conveyor or forklift that may be used to transport products from one location
to another location. The Access, Convey, and Exit modules are used in sequence for
material handling equipment, such as conveyors.
Figure 5.6. Sample Model 4.
The Access module in Figure 5.7 is used to access available space on a conveyor. If the
amount of requested space is available, then the product enters the conveyor. Else, the
conveyor continues until the amount of space requested becomes available for the
product.
Figure 5.7. The Access module.
Double-click the Access module to open the dialog box (see Figure 5.8).
Figure 5.8. Dialog box for the Access module.
In the Name field, enter a descriptive name and this will become the label for this
particular Access module. In the Conveyor Type field, we have three options:
Conveyor, Attribute, or Expression. Make the appropriate selection. In the Conveyor
Name field, enter the name of your conveyor. In the # of Cells field, enter the number of
cells you are requesting to occupy on the conveyor. The cell size is defined by the
analyst in the Conveyor data module. In the Queue field, make the appropriate
selection among the options Queue, Set, Internal, Attribute, or Expression. In the Queue
Name field, select the appropriate queue from the drop-down menu.
5.1.4 The Convey Flowchart Module
The Convey module in Figure 5.9 is used to convey the entity from one location to
another via the chosen method, such as a conveyor.
Figure 5.9. The Convey module.
Double-click the Convey module to open the dialog box (see Figure 5.10).
Figure 5.10. Dialog box in the Convey module.
In the Name field, enter a descriptive name and this will become the label for this
particular Convey module. Select the appropriate conveyor from the drop-down menu
in the Conveyor Name field. The selection would have been defined in an Access
module and stored in memory by Arena. In the Destination Type field, select from the
options By Sequence, Station, Attribute, or Expression. In the Station Name field, enter
the name of a new destination station unless the destination station is already stored in
the drop-down menu.
5.1.5 The Exit Flowchart Module
The Exit module in Figure 5.11 is used to exit the conveyor and free up the space once
occupied for other entities to occupy.
Figure 5.11. The Exit module.
Double-click the Exit module to open the dialog box (see Figure 5.12).
Figure 5.12. Dialog box for the Exit module.
In the Name field, enter a descriptive name and this will become the label for this
particular Exit module. In the Conveyor Type field, make the appropriate selection from
Conveyor, Attribute, or Expression in the drop-down menu. In the Conveyor Name
field, select the conveyor that you want to exit in the drop-down menu. In the # of Cells
field, enter the number of cells to be exited that were once occupied. This frees up space
on the conveyor for other entities that need to be conveyed.
5.1.6 The Request Flowchart Module
Sample Model 4 in Figure 5.6 is used to discuss Modules pertaining to entity transfer,
such as a conveyor or forklift that may be used to transport products from one location
to another location. The Request, Transport, and Free modules are used in sequence for
material handling equipment, such as forklifts.
The Request module in Figure 5.13 is used to request the availability of a transporter,
such as a forklift.
Figure 5.13. The Request module.
Double-click the Request module to open the dialog box (see Figure 5.14).
Figure 5.14. Dialog box in the Request module.
In the Name field, enter a descriptive name and this will become the label for this
particular Request module. Enter the name of a transporter in the Transporter Name
field. This name will be stored in memory by Arena. In the Selection Rule field, there
are six options, as shown in Figure 5.15: Cyclical, Random, Preferred Order, Specific
Member, Largest Distance, and Smallest Distance.
Figure 5.15. Selection Rules in Request module.
Each selection rule is defined below.
Cyclic rule: attempts to cycle through the transporters, thus leveling their utilizations
Preferred Order rule: attempts to always select the available transporter with the
lowest number.
Smallest Distance rule: results in an allocation of the cart closest to the requesting
entity. A new Attribute, Cart #, is defined and used to save the number of the cart that
was allocated. Also select the Transport option for the Connect Type.
Largest Distance rule: results in an allocation of the cart farthest from the requesting
entity. A new Attribute, Cart #, is defined and used to save the number of the cart that
was allocated. Also select the Transport option for the Connect Type.
Random rule: attempts to select any available transporter at random.
Specific Member rule: attempts to select a transporter by specific name.
In the Priority field, select the appropriate Priority Rule from among High(1),
Medium(2), and Low(1). In the Entity Location field, select STATION(StationID) for the
current station location of the entity. Be sure to replace StationID with the name of the
current station. In the Velocity field, enter a numerical value (in feet) to represent how
fast the transporter moves along the path. In the Units field, select from Per Second, Per
Minute, Per Hour, or Per Day. The Velocity and Units field are matched to represent the
velocity per unit of time (i.e., 25 feet per minute). In the Queue Type field, select from
Queue, Set, Internal, Attribute, or Expression. In the Queue Name field, select the
appropriate transporter queue from the drop-down menu.
5.1.7 The Transport Flowchart Module
The Transport module in Figure 5.16 is used to transport an entity from one location to
another.
Figure 5.16. The Transport module.
Double-click the Transport module to open the dialog box (see Figure 5.17).

Figure 5.17. Dialog box for the Transport module.

In the Name field, enter a descriptive name and this will become the label for this
particular Transport module. In the Transporter Name field, select the appropriate
transporter from the drop-down menu. All transporters that appear in the drop-down
menu were previously defined in a Request module. In the Unit Number field, make
the appropriate selection if a transporter is identified by a unit number. In the Entity
Destination Type field, select the entity’s next destination type from the options in the
drop-down menu: By Sequence, Station, Attribute, or Expression. In the Station Name
field, enter the name of the next destination. This will be stored in memory in Arena. In
the Velocity and Units fields, enter the speed of the transporter and then select the time
units of measurement from the drop-down menu. In the Guided Tran Destination Type
field, select Entity Destination from among the many options.
5.1.8 The Free Flowchart Module
The Free module in Figure 5.18 is used to free up a transporter so that it can continue
making the rounds in the system.
Figure 5.18. The Exit module.
Double-click the Exit module to open the dialog box (see Figure 5.19).

Figure 5.19. Dialog box for Free module.

In the Name field, enter a descriptive name and this will become the label for this
particular Exit module. In the Transporter Name field, select the particular transporter
you want to free up from the drop-down menu, including the unit number, if
applicable.
5.2 Data Modules
Data modules define the characteristics of various process elements, such as entities,
resources, and queues. They can also be used to set up variables and other types of
numerical values and expressions that pertain to the entire model. The icons for data
modules look like small spreadsheets in the Project Bar below the Modules section.
Data modules that we will use in this course for the Advanced Transfer panel include
Station Data, Sequence, Conveyor, Segment, Transporter, and Distance.
Other panels contain different sets of data modules. Data modules exist “behind the
scenes” and define different kinds of values, expressions, and conditions. To edit a data
module, click on it in the Project Bar and it will automatically appear in the Spreadsheet
view of the Model Window, below the Flowchart view. If the Flowchart view takes up
the entire Model Window, move your cursor down to “grab” the top of the spreadsheet
view and pull it up into view. Unlike Modules that may be used more than once in the
Flowchart, there is only one of each type of data module in every model. Within each
data module, however, there may be any number of rows that correspond to what is
included in the model for that type of data module.
Flowchart and data modules in the model are related by the names for objects that they
have in common, for example, queues, resources, entity types, and variables. Arena
stores in memory the names of objects the analyst defines and then presents these
names in a drop-down menu in the appropriate places in the flowchart and data
modules. This helps the analyst to remember what you’ve named things and maintains
consistency in the model development.
5.2.1 Station Data Data Module
We will use Sample Model 5 in Figure 5.20 to discuss the data modules in the Advanced
Transfer panel.
By clicking on the Station Data data module in the Project Bar, the Station Data
spreadsheet opens up at the bottom of the Model Window, as shown in Figure 5.20.
Figure 5.20. Spreadsheet view of the Station Data data module.
In this example, we observe five rows in the Station Data data module, one for each
Station module that is included in the Flowchart view.
5.2.2 Sequence Data Module
By clicking on the Sequence data module in the Project Bar, the Sequence spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 5.21.
Figure 5.21. Spreadsheet view of the Sequence data module.
In the Name field, the Sequence data module displays the different sequences involved
in the parts processing system. The Steps column further defines the particular
sequence each part will follow (see Figure 5.22).
Double-click to add a new row for each sequence. Double-click the Steps column to add
Steps (or the actual sequence that each part will follow as well as their respective
processing times), also shown in Figure 5.22.
Figure 5.22. The Steps and Assignments columns in the Sequence data module.
In the Sample Model 5 example, we can define the Steps (or sequence) that each part
follows. For example, Part 1 will follow the Sequence of CellStationA, then CellStationB,
then EndProcess. Within each station, the analyst can define the processing time for the
part in the Assignments column. For example, for CellStationA (for Part 1), the
processing time follows the Attribute named CellTime and the processing time will
follow a Triangular distribution with parameter times of a minimum of 6.3 minutes, a
most likely processing time of 9.1 minutes, and a maximum time of 12.5 minutes). The
analyst will perform this sequence of steps by defining the assignment times for each
part by the sequence in which each part follows. An important, but easy to forget, point
is to remember to conclude each sequence in the Steps column with a row named
EndProcess. This signals to Arena the end of a sequence for a given part. Of course, the
analyst would need to add the EndProcess Station in the Flowchart view prior to
defining the sequence of each part.
5.2.3 Conveyor Data Module
We return to Sample Model 4 to discuss the data modules for Conveyer, Segment,
Transport, and Distance in the Advanced Transfer panel.
By clicking on the Conveyor data module in the Project Bar, the Queue spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 5.23.

Figure 5.23. Spreadsheet view of the Conveyor data module.

The Name column displays the unique name of the conveyor entered in the Access
module in the Flowchart view. The Segment Name shows the name of the first conveyer
followed by a .Segment. If additional conveyors are added in the model, then the drop-
down menu in the Segment Name column will show all conveyors in the order that
they were added followed by a .Segment. In the Type column, a drop-down menu will
display both Accumulating and Non-Accumulating options. With an Accumulating
conveyor, entities will “bunch up” on the conveyor if not removed in a timely manner,
much like luggage will accumulate in a cul-de-sac area at an airport baggage claim area
if not retrieved by their owners in a timely manner. With a Non-Accumulating
conveyor, the conveyor continues to go round and around, carrying entities (or
luggage), but never accumulate if not retrieved by their owners in a timely manner. The
analyst will select the appropriate option. The analyst will enter the Velocity and select
the time unit of measurement in the Velocity and Units columns. The numerical value
in the Velocity column represent the speed (in feet) that the conveyor travels. The Units
column provides four options in the drop-down menu: Per Second, Per Minute, Per
Hour, and Per Day. The analyst manually enters a numerical value representing cubic
feet to define the cell size occupied in the Cell Size column. The analyst will also enter a
value for the Max Cells Occupied column. This value should correspond to the value
entered in the Access module in order to free up the cell(s) once occupied. The Initial
Status column drop-down menu provides options for Active and Inactive. Make the
appropriate selection.
5.2.4 Segment Data Module
By clicking on the Segment data module in the Project Bar, the Segment spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 5.24.

Figure 5.24. The Segment data module.

By clicking on the Segment data module, the Spreadsheet view displays rows for each
Segment in the model. The Name column displays all Segments included in the model
by row. The Beginning column shows the beginning station for each segment. The Next
Stations column shows the next destination station by making the appropriate selection
from the drop-down menu. The analyst will manually enter the length of the conveyor
(in one direction) in the Length column.
5.2.5 Transporter Data Module
By clicking on the Transporter data module in the Project Bar, the Transporter
spreadsheet opens up at the bottom of the Model Window, as shown in Figure 5.25.

Figure 5.25. The Transporter data module.

By clicking on the Transporter data module, the Spreadsheet view displays rows for
each transporter in the model. The Name column displays all transporters included in
the model by row. In the Number of Units column, the Default value is one unit in each
row; however, the analyst can manually change this number to any number desired.
The Type column has a drop-down menu consisting to two options: Free Path and
Guided Path. The Free Path option means that the transporter may travel freely in any
direction desired. The Guided Path option means that the transporter must follow a
guided path, much like a guided track system. Make the appropriate selection. The
Distance Set column shows the transporter name followed by a .Distance for each row.
The Velocity and Units columns work in conjunction to represent the speed of the
transporter (in feet) per time unit of measurement (Per Second, Per Minute, Per Hour,
or Per Day). The analyst will manually enter the velocity and then make the appropriate
selection in the Units column. The analyst may elect to define an Initial Position Status
by double-clicking in this column to add an initial status of the transporter or to simply
do nothing.
5.2.6 Distance Data Module
By clicking on the Distance data module in the Project Bar, the Distance spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 5.26.

Figure 5.26. The Distance data module.

By clicking on the Distance data module, the Spreadsheet view displays rows for each
type of distance traveled in the model. The Name column displays all Distances
included in the model by row. Click on the Stations column in each row to define the
beginning and end stations. Both beginning and end stations should be selected from
their respective drop-down menu options as these stations were previously defined in
the Flowchart view. The analyst will manually enter a numerical value in the Distance
column to represent the distance that the transporter must travel in one direction from
one location to another.
 Chapter 6 – Advanced Process Panel
6.1 Modules
We will use Sample Model 2 in Figure 6.1 and Figure 6.4 to discuss both the Modules
and Data Modules used from the Advanced Process panel in this course.

Figure 6.1. Sample Model 2.

6.1.1. The Match Flowchart Module
The Match module in Figure 6.2 matches different entities into a batch, or group.
Figure 6.2. The Match module.
Double-click it to open the dialog box (see Figure 6.3).
Figure 6.3. Dialog box for the Match module.
Simply enter a descriptive name in the Name field. This will become the label on the
face of the Match module. In the Number to Match field, enter the number of different
entities you want to match into a batch, or group. Arena will automatically generate the
number of queue lines for the Match module that correspond to the number to match
and you can click and drag each queue line where desired in the model. In the Type
field, two options are given: Any Entities and Based on Attribute. Make the appropriate
selection. In the Batch Action after Matching field, three options are given: No Batch,
Temporary Batch, or Permanent Batch. These same options are given in the Batch
module, which is added to the module sometime after the Match module is added. You
can make the appropriate selection in either the Match or Batch modules.
6.2 Data Modules
Data modules define the characteristics of various process elements, such as entities,
resources, and queues. They can also be used to set up variables and other types of
numerical values and expressions that pertain to the entire model. The icons for data
modules look like small spreadsheets in the Project Bar below the Modules section.
Data modules that we will use in this course for the Advanced Process panel include
Failure to build in a failure mechanism that resembles a real-life production situation.
Other panels contain different sets of data modules. Data modules exist “behind the
scenes” and define different kinds of values, expressions, and conditions. To edit a data
module, click on it in the Project Bar and it will automatically appear in the Spreadsheet
view of the Model Window, below the Flowchart view. If the Flowchart view takes up
the entire Model Window, move your cursor down to “grab” the top of the spreadsheet
view and pull it up into view. Unlike Modules that may be used more than once in the
Flowchart, there is only one of each type of data module in every model. Within each
data module, however, there may be any number of rows that correspond to what is
included in the model for that type of data module.
Flowchart and data modules in the model are related by the names for objects that they
have in common, for example, queues, resources, entity types, and variables. Arena
stores in memory the names of objects the analyst defines and then presents these
names in a drop-down menu in the appropriate places in the flowchart and data
modules. This helps the analyst to remember what you’ve named things and maintains
consistency in the model development.
6.2.1 Failure Data Module
We will continue to use Sample Model 2 to discuss the Failure data module in the
Advanced Process panel.
By clicking on the Failure data module in the Project Bar, the Station Data spreadsheet
opens up at the bottom of the Model Window, as shown in Figure 6.4.
Figure 6.4. Spreadsheet view of the Failure data module.
In this example, we observe only one row in the Failure data module, but we can add as
many failures as necessary to model a real production system. In the Name field, the
Default name is Failure 1; however, the analyst can change this to a more descriptive
name. In the Type field, there are two options: Count and Time. Count would be
selected if the failure occurred after so many cycles or number of units processed. Time
would be selected if failures occurred following a probability distribution or after a
known run time period.
In the Up Time column, a drop-down menu provides many probability distributions, as
shown in Figure 6.5.
Figure 6.5. Drop-down menu for Up Time column in Failure data module.
The analyst would select the appropriate distribution and manually enter parameter
values in the parentheses where indicated. In the Up Time Units column, make the
appropriate selection from the options Seconds, Minutes, Hours, or Days.
In the Down Time column shown in Figure 6.6, the analyst would make the appropriate
selection for the probability distribution and then manually enter parameter values in
the parentheses where indicated. In the Down Time Units column, make the
appropriate selection from the options Seconds, Minutes, Hours, or Days.
Figure 6.6. Drop-down menu for Down Time column in Failure data module.
 Chapter 7 – Adding Animation
7.1 Icons
We will use Sample Model 3 in Figure 7.1 to discuss how to add animation to
simulation models in this course.

Figure 7.1. Sample Model 3.

In Figure 7.1 above, right-click anywhere in the white space in the Toolbar area to see
which options have been selected as indicated by the check marks. Be sure all options
are selected that appear in the window pane in the upper right-hand corner of Figure
7.1. This adds all of the toolbars you will need in this course.
7.1.1. The Segment Icon
The yellow Segment icon appears in the bottom row of the Toolbar. It is mostly
rectangular in shape. By clicking on the Segment icon, a dialog box will appear in the
Flowchart view, as shown in Figure 7.2.
Figure 7.2. Dialog box for the Segment icon.
In the Identifier field, select the appropriate Station in the drop-down menu. All
Stations in the drop-down menu have been previously defined in various Station
modules above the animation in the Flowchart view. Place as many Segment icons in
the Animation portion of the Flowchart view as you have in Station modules. The
number of Segment icons should match the number of Station modules in the logic
portion of your model in the Flowchart view.
7.1.2. The Route Icon
Connect the Segment icons by clicking on the Route icon in the Toolbar. The Route icon
is the R icon with Segments indicated to the left and above the R. There are two ways to
connect routes: 1) by clicking on the Route icon to open its dialog box as shown in
Figure 7.3.
Figure 7.3. Dialog box for the Route icon.
Select the From Station and To Station in the respective drop-down menus. Once these
selections have been made, click the X in the upper right-hand corner to close the dialog
box, then use your cursor to click on the From Station segment and drag and click on
the To Station segment, then double-click to release. This creates the blue route line that
connects two segments (or Stations).
The second way to connect Segments is to click on the Route icon and simply bypass the
dialog box that opens and directly click on the From Station segment and drag and click
on the To Station segment, then double-click to release. This creates the same blue route
line that connects two segments (or Stations) by eliminating one step.
The number of routes in the animation portion of the model should match the number
of Route modules that were added in logic portion of the model in the Flowchart view.
The Default value for the number of points is 2, indicating a straight line with 2 end
points. The analyst has the option to change the number of points to as many as desired.
7.1.3 Adding Static Images with Arena Symbol Factory
Static images are images that do not change states (i.e., from an idle state to a busy
state). A static image is a “what you see is what you get” kind of image. We can find a
wide assortment of templates, each with its own set of static images, in Arena Symbol
Factory, as shown in Figure 7.4.

Figure 7.4. How to access Arena Symbol Factory.

To access Arena Symbol Factory, click on the Tools tab in the NavBar. Then scroll down
and click on Arena Symbol Factory. It should open to what we see in Figure 7.5.
Figure 7.5. Arena Symbol Factory templates and images.
If you do not see what is shown in Figure 7.5, go through the following steps:
Open > This PC > Windows (C:), double-click to open
Program Files
Rockwell Software
Arena
Symbol Factory
Symbol Factory3 (the application file)
This will take you to what we see in Figure 7.5. Notice on the left-hand side, there are
approximately 50 different templates, each with its own set of images. As an example,
Figure 7.5 currently displays the Containers template and we can clearly see numerous
images associated with containers. Click on any image of interest and it will be
displayed in the Preview window pane to the right of the list of templates. You can add
this image to your Arena model simply by right-clicking on the image, then select Copy
as GIF, go back to your model and right-click again to insert this image into your
model. You can change the size by dragging one corner to increase or decrease the size
of the image. You can also place it anywhere in your model by left-clicking on the
image and moving it to the desired location, then click again to release the cursor. As an
example, we have just added a static image of the wood pallet into our Sample Model 3
in Figure 7.6 by following the above steps.

Figure 7.6. Adding a static image of a wood pallet from Arena Symbol Factory.
Take a few minutes to explore the many templates and see the images that you may one
day want to add to your future simulation models.
7.1.4 Dynamic Resource Images
Dynamic resource images are images of resources that change states (i.e., from Idle state
to Busy state) during a simulation run. These images are added by clicking on the
Resource icon in the Toolbar. The Resource icon is a green icon that resembles a
gasoline pump from yesteryear with a line arrow going through it from top left to right.
Clicking on the Resource icon opens a dialog box, as shown in Figure 7.7.
Figure 7.7. Dialog box of Resource icon.
In the Identifier field, select the appropriate Resource from the drop-down menu. The
Identifier must be a previously defined Resource in your model, which typically comes
from a resource that was added in a Process module. You can select an image to
represent Idle and Busy states from a picture library file. The Basic Process picture
library file is shown in Figure 7.7. The slider bar to the right of the images moves up
and down to reveal all images associated with the Basic Process picture library. Other
picture libraries are available by clicking on the Open button and then selecting another
picture library, as shown in Figure 7.8. Remember where you saved this file so you can
open it whenever needed.
Figure 7.8. Finding the .plb files.
Once you locate the .plb files, click on the folder labeled .plb files to view all picture
library files, as shown in Figure 7.9. Then select the picture library file of interest.
Figure 7.9. Viewing all .plb files from the .plb Folder.
Here, we’ve selected the Workers .plb file, which now appears in our Resources dialog
box in Figure 7.10.

Figure 7.10. Workers.plb file.

When viewing the images within each picture library file, the analyst should select
images that represent both an idle state and a busy state. For example, in Figure 7.10
above, the first two images are of a forklift. One image could represent an Idle state and
the other image could represent a Busy state. To add an Idle state image, click on the
Idle button with a white box first, then click on the image you want to represent the Idle
state, then click on the << button to send the image over and replace the white box for
the Idle state, as shown in Figure 7.11. The analyst should do likewise for the Busy state
image.
Figure 7.11. Idle and Busy state images.
Notice the Resource Picture Placement in the top middle of the screen. Observe that the
State field and the Picture ID field changed when new images were added. Be sure to
also select an Identifier image from the drop-down menu. Else, the model will have an
error bug if this step is overlooked. You also have the option whether to click on the
check box for Seize Area. By checking the box for Seize Area, the dynamic image in the
model will have a circle with a dotted line. Click on the circle to move it where desired,
normally in the middle of a Busy state image to show a part being worked on when the
simulation runs.
Take time to explore the images contained in the various picture libraries to get an idea
of what is available for your future simulation models.
7.1.5 Dynamic Transporter Images
Dynamic transporter images are images of transporter, such as a forklift, that change
states (i.e., from Idle state to Busy state) during a simulation run. These images are
added by clicking on the Transport icon in the Toolbar. The Transport icon is a green
icon that resembles a green railroad car from yesteryear with two wheels, as shown in
Figure 7.12.

Figure 7.12. Clicking on the Transport icon.

Clicking on the Transport icon opens a dialog box, as shown in Figure 7.13.
Figure 7.13. Dialog box for the Transporter icon.
Notice the Transporter Picture Placement in the top middle of the screen. Also observe
that this dialog box very closely resembles the dialog box for the Resource icon;
however, this dialog box pertains to transporters that would be added in a Request
module rather than resources like machines, equipment, or people that would be added
in a Process module.
The actions required to add Idle or Busy state images, Identifiers, and changing picture
libraries is identical to those actions required in the Resources icon discussed in the
previous section.
7.1.6. The Distance Icon
The yellow Segment icon appears in the bottom row of the Toolbar. It is mostly
rectangular in shape. By clicking on the Segment icon, a dialog box will appear in the
Flowchart view, as shown in Figure 7.14.
Figure 7.16. The Distance icon in Sample Model 4.
Connect Segments (or Stations) for Transporters by clicking on the Distance icon and
then either 1) complete the dialog box as we did for the Segment icon, or 2) simple
ignore the dialog box and make the appropriate Segment (or Station) connections
directly. The Default value for the number of points is 2, indicating a straight line with 2
end points. The analyst has the option to change the number of points to as many as
desired as we see in the green line loop-de-loop path configuration for the forklift in
Figure 7.16.
7.1.7 Level Indicator
We will use Sample Model 6 to discuss how to add a Level Indicator or a Time Plot to
your model.
A Level Indicator displays a fluctuating level, such as reservoir water level, during a
simulation run. The Level Indicator icon is located in the same toolbar as the Resource
icon, as shown in Sample Model 6 in Figure 7.17.
Figure 7.17. Level Indicator icon in Sample Model 6.
Click on the Level Indicator icon to open the dialog box (see Figure 7.18).

Figure 7.18. Dialog box for Level Indicator.

In the Expression field, select the variable that you want Arena to monitor from the
drop-down menu. Manually enter the minimum and maximum values in the Minimum
and Maximum fields. In the Type area, click on the radio dial for the type of display you
want to see. Whatever you select will appear in the upper right-hand corner of the
dialog box, such as the rectangle in Figure 7.18. In the Fill Direction area, make the
appropriate selection. The analyst can also choose to remove border around the level
indicator by clicking on the check box for No Border. Click the Fill button to open a
color palette and you can select the color of choice for your level indicator. Check the
box for Use Title to add a title to your image. Once you complete the dialog box and
click OK, Arena will give you cross-hairs and you can decide where you want to put
your level indicator in your model. You can move it around your model as well as
increase or decrease the size of your level indicator by dragging one corner of the image
in the appropriate direction. You can also add static images from Arena Symbol Factory
to enhance the image in your model, as seen in Figure 7.17.
7.1.8 Time Plot
A Time Plot displays a graph that tracks the value of a variable over time. The Time Plot
icon is in the same toolbar as the Resource icon, as shown in Figure 7.19.
Figure 7.19. Time Plot icon in Sample Model 6.
Click on the Time Plot icon to open the dialog box, as shown in Figure 7.20.

Figure 7.20. Dialog box for Time Plot icon in Sample Model 6.
You will notice six tabs in the dialog box of which we typically use only three. The Data
Series tab will be blank; however, after you enter a name in the Name field of the Source
Data section, Arena will automatically create a Data Series. Also in the Source Data
section, select the variable that you want Arena to track over time from the drop-down
menu.
Make appropriate selections in the Fill section, including your choice of color. In the
Line section, the Draw Mode field offers two options as shown in Figure 7.21: Point to
Point and Stairs.

Figure 7.21. Line > Draw Mode options in Sample Model 6.

The Style field in Figure 7.22 offers different types of line style in your graph, such as
Solid, Dash, Dot, Dash Dot, Dash Dash Dot, and Small Dots. Make the appropriate
selection.
Figure 7.22. Line > Style options in Sample Model 6.
We use the Axes tab to label and create tic marks for both the X-axis and Y-axis, as
shown in Figure 7.23.
Figure 7.23. The Axes tab in Sample Model 6.
Select the (X) Axis option in the Axes window and then make appropriate selections in
the fields to the right: Major and Minor Gridlines, Labels, Line, Scale, and Title. The
Scale section allows the analyst to enter minimum and maximum values on the axis, as
well as major increments (the tick marks), as shown in Figure 7.24.
Figure 7.24. The Scale section for the (X) Axisin the Axes tab in Sample Model 6.
Then select the (Y) Axis option in the Axes window and then make appropriate
selections in the fields to the right: Major and Minor Gridlines, Labels, Line, Scale, and
Title. The Scale section allows the analyst to enter minimum and maximum values on
the axis, as well as major increments (the tick marks), as shown in Figure 7.25.
Figure 7.25. The Scale section for the (Y) Axisin the Axes tab in Sample Model 6.
In the Legends tab, the analyst has the option whether to add or not add a legend to the
time plot graph, as shown in Figure 7.26.
Figure 7.26. The Legend tab in Sample Model 6.
Check the box for Show Legend to display the legend “Reservoir Water Level” in the
Sample Model 6 example. If the box is left unchecked, then no legend will appear and
the window will be filled by the time plot graph.