ARENA simulation software

K.MAHESWARA RAO
09MF05
M.E(I.E)
 Ways To Study A
System *

Simulation, Modeling & Analysis (3/e) by Law and Kelton, 2000, p. 4, Figure 1.1
*
 Technical Attractions of
Simulation*
• Ability to compress time, expand time
• Ability to control sources of variation
• Avoids errors in measurement
• Ability to stop and review
• Ability to restore system state
• Facilitates replication

*
Introduction

With Arena, you can:

Model your processes to define, document, and

communicate.

Simulate the future performance of your system to

understand
complex relationships and identify opportunities for
improvement.

Visualize your operations with dynamic animation

graphics.

Analyze how your system will perform in its “as-is”

configuration
and under a myriad of possible “to-be” alternatives
so that you
can confidently choose the best way to run your
Entities are dynamic elements that pass through the
system.
Entities are distinguished by their attributes.
Attributes must be numerical values.
You may have different types of entities in the same model.

Resources have a name and a capacity (number of

identical units of the resource).
Resources may have a schedule (how many of them are
available and when).
Variables can be referenced in modules, can be
reassigned a new value with a particular module, and can
be used in any expression
Time Attribute Variables, Cost Attribute Variables…
The Arena modelling environment
 Flowchart and Spreadsheet
Views
• Model window split into two views
– Flowchart view
• Graphics
• Process flowchart
• Animation, drawing
• Edit things by double-clicking on them, get into a
dialog
– Spreadsheet view
• Displays model data directly
• Can edit, add, delete data in spreadsheet view
• Displays all similar kinds of modeling elements
at once
– Many model parameters can be edited in either
view
– Horizontal splitter bar to apportion the two
views
The Project Bar hosts panels with the primary types of
objects that you will work with:
Basic Process panel: Contain the modelling shapes,
called modules, that you’ll use to define your process.
Reports panel: Contains the reports that are available
for displaying results of simulation runs.
Navigate panel: Allows you to display different views of
your model, including navigating through hierarchical sub
models and displaying a model thumbnail.
Create

We’ll start the flowchart using a Create module, from the

Basic Process panel. This is the starting point for the flow of
entities through the model.
1.Drag the Create module from the Basic Process panel into
the model
window. A default name, Create 1, is given to the
module when it’s placed.

Every process flow starts with a Create module. When you

simulate the flowchart, individual entities will be created
according to timing information you supply in the Create
module properties. After it’s
created, each entity moves from the Create module to the
next shape in
the process flow
Process the applications
Next in our flowchart is a Process module that represents the
Review Application step.
1. Be sure that the Create module is selected so that Arena
will automatically connect the Process to the Create module.
2. Drag a Process module from the Basic Process panel into
the model window, placing it to the right of the Create. Arena
will automatically connect the two modules.

If no connection appears between Create and Process, click

the Object > Connect menu item or the Connect toolbar
button to draw a connection
Decide whether applications are complete

After the Process, we have a Decide module which

determines whether the process is complete.
1. If you’re using the Auto-Connect feature (i.e., it’s checked
on the Object > Auto-Connect menu), be sure that the
Process module is selected so that the Decide module will be
connected to it.
2. Drag a Decide module to the right of the Process module
Dispose the applications to terminate the process

Next we’ll place the Dispose module that represents accepted

applications, connecting to the True (right) output from the Decide
shape. Then, we’ll complete the flowchart with another Dispose for
returned applications.

1.Select the Decide shape so that our first Dispose will be

connected automatically
2.Drag a Dispose module to the right of the Decide module. Arena
will connect it
to the primary (True) exit point of the Decide module.
3.To add the second Dispose module, once again select the Decide
module, so
that Arena will automatically connect its False exit point to the
new Dispose module,
Dispose Module
Basic Arena
Simulations
 Create Module

drag & drop

double-click
 Delay Process

delay for processing time

holds entity in this

module for some period
of time
 Processes Requiring
Resources

seize resource
delay for processing time
release resource
 Decisions

right-click here to bring

up expression builder
Expression Builder
Connecting Modules

Object  Connect

then select output of one module

and input of next module

(watch for green & red boxes on

terminals)
 Entities

double-click
Resources
Resource Animation
 Simulation Run Setup

Run  Setup…
Dynamic Plots
Complete Simulation
 Technology Version
Forge 1.0

Arena Tutorial 3 –

Electronic Assembly
Process - Part 1

Arena Tutorial 3 - Electronic

Assembly Process - 1
Tutorial Objectives:

•Create a basic model of an electronic assembly

process.

•Use an Assign module to assign different delay times for

different assemblies.

•Use Record modules to create new measures of system

performance.

Arena Tutorial 3 - Electronic

Assembly Process - 1
Electroni Metal case
c comes in 2
Assembl versions:
Part A and Part
y B
Example
Top and
bottom case
pieces are
Metal identical.
Circuit
case board

Sealant

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Store Room

Part A Good
Ship
Part A Sealant assembly
Case Supplier Case

Circuit Board Circuit Electronic Salvaged

Salvage
Supplier board Assembly assembly

Part B
Part B
Case Scrap
Case Supplier assembly Scrap

Process
we will be
simulatin
g
Context
Diagram
Arena Tutorial 3 - Electronic for this
Assembly Process - 1
Simulation goals are to collect statistics on:

•Resource utilization for each resource – What

percent of the available work time is each resource
in the process busy?

•Number of units in queue at each operation –

How many units are waiting to be worked on at
each operation?

•Time in queue at each operation – How long

does each unit wait to get worked on?

Arena Tutorial 3 - Electronic

Assembly Process - 1
Do not include
circuit boards
and sealant in
this model
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Desired statistics
for each process
module:
- Resource
utilization
- Units in queue
- Time in queue

Basic Model
Arena Tutorial 3 - Electronic
36
Assembly Process - 1
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Do these
next…

Configure
Create
Modules
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Configure
Finish Part A
Surfaces
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Configure
Finish Part B
Surfaces

Next

Arena Tutorial 3 - Electronic

Assembly Process - 1
Start configuring
the
Seal Assembly
module

We will return
to this module
later to specify
Delay Type Arena Tutorial 3 - Electronic
Assembly Process - 1
 Do this
next…

Configure
decision
modules Arena Tutorial 3 - Electronic
Assembly Process - 1
 Configure
Rework Seal
module

Arena Tutorial 3 - Electronic

Assembly Process - 1
Tutorial Objectives:

•Create a basic model of an electronic assembly process.

•Use an Assign module to assign different delay

times for different assemblies.

•Use Record modules to create new measures of system

performance.

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Finish configuring
the
Seal Assembly
module
Part A and
Part B have
different
delay times

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Start
configuring the
Assign module
Arena Tutorial 3 - Electronic for Part A
Assembly Process - 1
 Finish configuring
the
Assign module
Arena Tutorial 3 - Electronic for Part A
Assembly Process - 1
 Start
configuring the
Assign module
for Part B Arena Tutorial 3 - Electronic
Assembly Process - 1
 Finish configuring
the
Assign module
for Part B

Arena Tutorial 3 - Electronic

Assembly Process - 1
 −α ( α −1) −( x / β )α Weibull distribution
f ( x) = α β x e of Sealer Times

α= β=
2.5 5.3
0.25

0.2

y
til 0.15
i Time
b
a
b betwee
o
r 0.1
P n
arrivals
0.05
Probability of
next part arriving 0
x minutes after 0 2 4 6 8 10 12
previous part Sealer Time (minutes) x
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Finish configuring
the Seal Assembly
module
Arena Tutorial 3 - Electronic
Assembly Process - 1
 Run
simulation!

Desired statistics
for each process
module:
- Resource
utilization
- Units in queue Arena Tutorial 3 - Electronic
- Time in queue Assembly Process - 1
Desired statistics Review
for each process results
module:
- Resource
utilization
- Units in queue
- Time in queue

Arena Tutorial 3 - Electronic

Assembly Process - 1
Review Desired statistics
results for each process
module:
- Resource
utilization
- Units in
queue
- Time in
queue

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Change
pictures for
Part A and Part
B

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Animate
resources

Arena Tutorial 3 - Electronic

Assembly Process - 1
Arena Symbol Factory
Arena .plb picture files
Animated
model
Arena Tutorial 3 - Electronic
Assembly Process - 1
Tutorial Objectives:

•Create a basic model of an electronic assembly process.

•Use an Assign module to assign different delay times for

different assemblies.

•Use Record modules to create new measures of

system performance.

Arena Tutorial 3 - Electronic

Assembly Process - 1
Simulation goals are to collect statistics on:
•Resource utilization for each resource – What percent of the
available work time is each resource in the process busy?

•Number of units in queue at each operation – How many

units are waiting to be worked on at each operation?

•Time in queue at each operation – How long does each unit

wait to get worked on?

•Cycle time – How long does each part take to get through
the entire system?
• Good assembly cycle time,
• Salvaged assembly cycle time, Add
• Scrap assembly cycle time. cycle time
statistics
Arena Tutorial 3 - Electronic
Assembly Process - 1
Cycle time:
How long does each part take to get through the entire
system?
• Good assembly cycle time,
• Salvaged assembly cycle time,
• Scrap assembly cycle time.

How does
this split
out?

Arena Tutorial 3 - Electronic

Assembly Process - 1
 Add
cycle
time
recorders

Arena Tutorial 3 - Electronic

Assembly Process - 1
 From a Configure
few slides
ago
the
Record
modules

The other Record

modules are
configured
similarly Arena Tutorial 3 - Electronic
Assembly Process - 1
 Cycle times
for
assemblies

Arena Tutorial 3 - Electronic

Assembly Process - 1
Overview
the basic process of contact center simulation is to generate a stream
of arriving contacts,
assign them to trunk lines, and route them through the center to an
agent. To create a simulation model of a contact center or network of
contact centers, you will describe the
sequence of events that occur as contacts move through the system,
from the arrival of the contacts at the contact center to successful
resolution. You will also need to specify information about the contact
center itself (trunk-line capacity, agent skills, agent schedules,etc.).
As you build your contact center models, it may
be helpful to keep in mind the Contact Center Core Process, as
illustrated below.

The basic components of this process

are:
1.Contacts
2.Arrival Patterns
3.Trunk Groups
4.Routing Scripts
5.Schedules