Professional Documents
Culture Documents
ARENA
ARENA
ARENA
3.1 - Entities
Entities are dynamic elements that pass through As we build the flowchart, its helpful to think of the system. the process from the perspective of the entity.
The trigger for an action to be is Entities are distinguished byaccomplished their attributes .
Entities must be created to get them into the module and are disposed when they leave.
Attributes must be numerical values. You may have different types of entities in the same model.
ARENA
3.2 - Resources
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). Resources are automatically defined by some modules (e.g., Process). Resources can be defined manually, and the properties of all resources can be edited in the same way.
ARENA
3.3 - Queues
Entities queue when they need processing An entity tries to seize a resource. The time the entity uses the resource is the delay. If the resource is not available, the entity waits in a queue. The entity releases the resource when processing is complete. Queues are created automatically by some modules (e.g., Process), and can be defined manually.
6
ARENA
3.4 - Variables
Arena allows the user to work with simulation variables. They contain information about particular dimensions of the model. See the Variables Guide Many of them are built-in.
Time Attribute Variables, Cost Attribute Variables
Variables can be referenced in modules, can be reassigned a new value with a particular module, and can be used in any expression.
ARENA
3.5 - Processes
Entity must be processed. This activity is performed by one or more resources and requires some time to complete.
ARENA
The Output
The Entity
Its Queue
A Process
ARENA
Project Bar
Flowchart View
Spreadsheet View
10
ARENA
The Project Bar hosts panel with the primary types of object to work with.
Basic Process, Advanced Process, Advanced Transfer Panels
Reports Panel
Navigate Panel
The Flowchart View is the real environment and it Here theall objects are connected by a particular will contain of your model graphics, including the instrument: there isanimation, no difference between data drawing process flowchart, and other connectors and logical connectors. elements. The Spreadsheet View displays model data, such as times, costs, and other parameters.
11
We will mainly work with Basic Process modules. The modules are the classes.
Esempio Classe: ASTRONAVE
As you drag a module to the Flowchart View, you create an instance of that module; thus, you have Esempio Oggetto: an object. It is a visual representation of object-oriented programming language (such as Java or VB.NET).
MILLENNIUM FALCON
12
Push (possibly) batches of entities into the model with a (possibly) random time between.
Assign values (especially Attributes) when an entity passes through. Record information when entities pass through, typically statistics on entities. Combine multiple single entity. Split multiple combined, or entity.
14
entities
into
Each time you create an instance of an object, you have to define its attributes, in order to completely definite it. These attributes can be set in the prompt window obtained by double-clicking on the object itself. You can see all the attributes of the modules watching the spreadsheet in the corresponding window. There are elements not represented by modules: their attributes can only be set via spreadsheet.
15
ARENA
16
ARENA
4.3 - Analyzers
The Input Analyzer is useful for determining an appropriate distribution for input to an Arena model. The Input Analyzer allows the user to take raw data and fit it to a statistical distribution which can be incorporated directly into your model. The Output Analyzer is used to display and analyze model data after the simulation run (or runs) has been performed. The Output Analyzer also provides analysis features such as confidence intervals. Both the Input and Output Analyzers are directly available on the Arena Tools menu.
17
ARENA
The time on the simulation clock is accessible through the Arena variable TNOW.
18
ARENA
File Classic Windows File Menu Edit Classic Windows Edit Menu View Zoom, grid, layers, toolbars Tools Input/Output Analyzer, Add-Ins, VBA Arrange Drawing, group, rotate Module Connections, panel, breakpoint Run Run, check, pause step through Windows Classic Windows Windows Menu
19
ARENA
4.6 - Running
Go Step Fast-Forward Pause Start Over End Check Model Like compiling Review Errors For most recent check View Results Summary for most recent run SIMAN See, save underlying SIMAN files Command Interactive command-line window Break Set times, conditions to interrupt Trace Generate detailed history Watch Watch a variable or expression during run Report See a numerical status when paused Setup Alter run conditions Speed Control speed of animation display
20
ARENA
5 - AN EXERCISE /1
The first model we are going to build is a single server queuing model. The underlying system can be defined as follows. - Customers arrive in the system one at a time. - The inter-arrival times, probability distribution. follow a certain
Further assumptions of the arrival process are not made at this point. - There is a single server that can serve one customer at a time.
21
ARENA
5 - AN EXERCISE /2
- The processing times follow a certain probability distribution. Further assumptions of this distribution are not made yet. - If the server is busy at the time when a customer arrives in the system, the customer is placed in a queue to wait for the server to become free.
- The customers in the queue are served according to FIFO queuing discipline, i.e. the first of the customers to arrive in the queue is served first.
22
ARENA
Expected average queuing time of a customer D is the delay in queue of the ith customer. Expected average number of customers in the queue Q(t) is the number of customers in queue at time t and T(n) the total simulation time when simulating the passage of n customers through the system.
23
ARENA
Utilization of the server Let B(t) be 0, if the server is idle at time t and 1, if it is working.
24
ARENA
The create-module represents the arrival of customers into the system. The process module represents customer service and the disposemodule represents the departure of customers from the system.
25
Correct naming Name-field: Customer arrivals Entity type-field: Customer Distribution of inter-arrival time of customers Constant inter-arrival time of 1 hour Parameters - Entities per arrival: 1 It states that each customer arrives alone. - Max arrivals: 3 Defines the maximum number of customers created during the simulation. - First creation: 0 The first customer is created at time 0.
26
The process-module defines, what happens during customer service. Correct naming Name-field: Customer service Entity type-field: Standard Define the logic of the process Action-field: Seize-Delay-Release This that anand entity that is activity being isprocessed The means resource is seized released. The delayed. As we takes selected the Seize-Delay-Release a queue named first control of ,(seizes) the Customer required service.Queue Then, was automatically created by Arena to handle a resources. the entity experiences entities that wait for service. processing delay and, when done, releases the control of the resources it has held.
27
Selecting the Seize-Delay-Release option opens another field named Resources to define what resources are required to complete the task. Click Add and define in the opening dialogue box: Type Resource, Server and Quantity This value is theName number of resources simultaneously used by the resource. 1. The and
The capacity of the resource (how many resource-items are in the system)takes must be edited the spreadsheet Server resource care of in customer service serves 1 customer at field. a time.
Lastly, define a constant 2 hour processing delay. Still, make sure that the Report statistics option is selected and leave the dialogue box.
28
Correct naming Name-field: Departures Check that the Record entity statistics -option is selected.
29
ARENA
5.4 - Simulation
Our model is now complete and we can start simulating. The specifics of the simulation run are defined by selecting from the Run-menu Setup.
Our simulation ends when the three entities leave the system. So, we dont need to make specifications. Usually, it is possible to specify the run simulation length. Start the simulation by selecting Go from the Runmenu and wait.
30
ARENA
The type of report that Arena will show is by default the Category overview report. It basically lists the values of all performance indicators for which the statistics collection option was activated. Remember that we used constant inter-arrival (1 hour) and processing times (2 hours) as input data and created only 3 customers.
31
This allows us to say, without simulating the system, that the expected average queuing delay for a customer is 1 hour, the expected average queue length is 0.5 and that the server utilization is 1.
ARENA
The simulation results should tell us exactly the same thing and allow us to be a little more confident about the implementation of the model.
Now, go through the report and locate the values of Wait time in the Entity-category, Number waiting in the Queue-category as well as Instantaneous utilization in the Resourcecategory.
32
ARENA
BIBLIOGRAPHY
Arena Software Tutorial; David A. Takus, David M. Profozich Simulation with Arena, Chapter 4; Working with Arena Mat-2.170 Simulation Spring 2006, Exercise 3 Introduction to Arena Software Arena Basics; ISyE 6644; Seong-Hee-Kim (Georgia Tech), Barry Nelson (Nortwestern) Arena Users Guide; Doc ID ARENA-UM001A-EN-P
33