Scribd
Upload
190 views7 pages

IE 305 Recitation 2: Introduction To Arena 18.10.2021

The document provides instructions for several exercises using Arena simulation software. Exercise 3.1 asks to run 5 replications of Model 3-1 and note the variation in performance measures across runs. Exercise 3.9 modifies Model 3-1 to have 3 sources of arriving parts (blue, green, red) and collects statistics separately by part color. Exercise 3.14 simulates 5 machines that break down and are repaired by 2 technicians, tracking the number of machines down over time.

Uploaded by

Esra Tanyıldız
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
190 views7 pages

IE 305 Recitation 2: Introduction To Arena 18.10.2021

The document provides instructions for several exercises using Arena simulation software. Exercise 3.1 asks to run 5 replications of Model 3-1 and note the variation in performance measures across runs. Exercise 3.9 modifies Model 3-1 to have 3 sources of arriving parts (blue, green, red) and collects statistics separately by part color. Exercise 3.14 simulates 5 machines that break down and are repaired by 2 technicians, tracking the number of machines down over time.

Uploaded by

Esra Tanyıldız
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

IE 305

RECITATION 2
INTRODUCTION TO ARENA

18.10.2021
EXERCISE 3.1 (SWA - EDT. 4)

• Make five replications of Model 3-1 by just asking for them in


Run/Setup/Replication Parameters.
• Look at the output and note how the performance measures vary
across replications, confirming Table 2-4 (next slide).
• To see the results for each of the five replications individually,
you’ll need to open the Category by Replication report; the
confidence-interval half-widths can be seen in the Category
Overview report, however.
EXERCISE 3.9 (SWA - EDT. 4)

• In Model 3.1, suppose that instead of having a single source of parts, there are
three sources of arrival, one for each of three different kind of parts that arrive:
Blue (as before), Green and Red.
• For each color of arriving part, interarrival times are exponentially distributed
with a mean of 16 minutes.
• Run the simulation for 480 minutes, and compute the same performance
measures as for Model 3.1.
• Once the parts are in the system, they retain their correct color (for the
animation) but are not differentiated for collection of statistics on time in queue,
queue length, or utilization (that is, they’re lumped together for purposes of
processing and statistics collection on these output performance measures);
however, collect statistics separately by part color for total time in system.
EXERCISE 3.9 (SWA - EDT. 4)

• Processing times at the drilling center are the same as in Model


3.1 and are the same regardless of the color of the part.
• Make just a single replication. Put a text box in your Arena file
with the values for the output performance measures mentioned
(average time in queue for all part types together, average
queue length for all part types together, server utilization for all
types together, and three average time-in-system results, one
for each part type separately).
EXERCISE 3.14 (SWA - EDT. 4)

• Five identical machines operate independently in a small shop.


Each machine is up (that is, works) for between 7 and 10 hours
(uniformly distributed) and then breaks down.
• There are two repair technicians available, and it takes one
technician between 1 and 4 hours (uniformly distributed) to fix
machine; only one technician can be assigned to work on a broken
machine even if the other technician is idle.
• If more than two machines are broken down at a given time, they
form a (virtual) FIFO “repair” queue and wait for the first available
technician. A technician works on a broken machine until it is fixed,
regardless of what else is happening in the system.
EXERCISE 3.14 (SWA - EDT. 4)

• All uptimes and downtimes are independent of each other.


Starting with all machines at the beginning of an “up” time,
simulate this 160 hours and observe the time-average number of
machines that are down (in repair or in queue for repair), as well
as utilization of the repair technicians as a group; put your results
in a Text box in your model. Animate the machines when they’re
either undergoing repair or in queue for a repair technician, and
plot the number of machines down (in repair plus in queue) over
time.
HINT: Think of the machines as “customers” and repair
technicians as “servers” and note that there are always five
machines floating around in the model and they never leave.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy