Professional Documents
Culture Documents
Credit
Project
IE 417: Operations Research II
Travis Guzman
Amanda Smith
David Trigg
2|Page
Problem Statement
The problem statement can be found on page 1094, problem #3 from Operations
Research by Wayne L Winston, 4th edition.
a. At present, the finance department and the marketing department each have one
typist. Each typist can type 25 letters per day. Finance requires that an average
of 20 letters per day be typed, and marketing requires that an average of 15
letters per day be typed. For each department, determine the average length of
time elapsed between a request for a letter and completion of a letter.
b. Suppose that the two typists were grouped into a typing pool; that is each typist
would be available to type letters for either department. For this arrangement,
calculate the average length of time between a request for a letter and
completion of the letter.
d. Under the pooled arrangement, what is the probability that more than .200 day
will elapse between a request for a letter and completion of the letter?
3|Page
Summary of the Problem
Before beginning the problem, we must have an understanding of the type of queuing
system presented in the problem, as well as associated formulas that will be employed
with this type of queuing system.
First, we begin with the type of queuing system given. The Kendell-Lee Notation for
Queuing Systems can be described by six characteristics:
Kendell-Lee Notation
1/2/3/4/5/6
Arrival process/service process/parallel servers/ queue discipline/max customers/population size
For our problem the Kendell-Lee Notation looks like the following:
M/M/s/GD/∞/∞
Where
4|Page
𝜋j = P(j) = Probability that j units are in the system
***Note: Cost Formulas are located in cost analysis section for clarity****
Rate Diagram
5|Page
Part A:
First we extract the information the problem gives us:
s = 2 typist
λMarketing = 15 letters/day
The problem asks, “For each department, determine the average length of time elapsed
between a request for a letter and completion of a letter.” In essence this means find W,
the total time each letter is in the system for each department. The diagram below will
help in analyzing the problem:
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
λFinance=20 μFinance=25 𝑑𝑎𝑦
𝑑𝑎𝑦 Finance Dept.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
λMarketing=15 𝑑𝑎𝑦 MarketingDept. μMarketing=25 𝑑𝑎𝑦
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
For this part, number of servers is equal to one when we are analyzing traffic intensity.
There is only one server in each department, and we are analyzing the departments
separately. Keep in mind that when we are analyzing departments separately we are
6|Page
looking at a M/M/1/GD/∞/∞. With the given information, we only need one formula, W,
from the M/M/1 system. We proceed to make the following calculations:
FINANCE MARKETING
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
20 15
𝑑𝑎𝑦 𝑑𝑎𝑦
ρ= 𝑙𝑒𝑡𝑡𝑒𝑟𝑠 = .80 ρ= 𝑙𝑒𝑡𝑡𝑒𝑟𝑠 = .60
(25 ) (1 𝑠𝑒𝑟𝑣𝑒𝑟)(25 )
𝑑𝑎𝑦 𝑑𝑎𝑦
ρ = 0.80 ρ = 0.60
0< ρ<1 0< 0.80<1so a steady state exists 0< ρ<1 0< 0.60<1so a steady state exists
Time in System: Time in System:
1 1 1 1 1 1
W = µ−𝜆 = = day W= µ−𝜆 = = 10 day
25−20 5 25−15
We also make the following extra calculations for later comparison purposes:
Number Waiting in Line: Number Waiting in Line:
𝑝2 .802 𝜌2 .602
Lq = (1−𝜌) = (1−0.80) = 3.2 letters . Lq = (1−𝜌) = (1−0.60)= 0.90 letters
𝑝 .80 𝑝 .60
L = (1−𝜌) =(1−0.80)= 4 letters L = (1−𝜌) =(1−0.60)= 1.5 letters
1
As you can see, it takes the finance department 5 day between a request for a letter and
1
completion of a letter. It only takes the marketing department 10 day between a request
for a letter and completion of a letter. This is expected since the marketing department
receives 5 less letters a day as compared to the finance department and both
departments have the same process time.
7|Page
Part B:
Essentially, Part B asks the same question as Part A, but in this scenario, the typists
can type letters for either department.
Finance Dept.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
λM&F=35 𝑑𝑎𝑦
μM&F=50 𝑑𝑎𝑦
MarketingDept.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
8|Page
Then, we proceed to the calculations. Now, we don’t have to perform calculations for
separate departments since we are viewing the departments as one team.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
35
𝑑𝑎𝑦
ρ= 𝑙𝑒𝑡𝑡𝑒𝑟𝑠 <1
(2 𝑠𝑒𝑟𝑣𝑒𝑟)(25 )
𝑑𝑎𝑦
Number in System:
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
35
𝑑𝑎𝑦
L = Lq + Ls = 1.33 𝑙𝑒𝑡𝑡. + 𝑙𝑒𝑡𝑡𝑒𝑟𝑠 = 2.73 letters
25
𝑑𝑎𝑦
Time in System:
𝐿 2.73 𝑙𝑒𝑡𝑡.
W=𝜆= 𝑙𝑒𝑡𝑡𝑒𝑟𝑠 = .078 days
35
𝑑𝑎𝑦
Thus, when the typists were grouped the new average length between a request for a
letter and completion of the letter is .078 days.
9|Page
Part B: Performance Measures
Performance measures were added for Part B of this problem because in this section of the
problem the typists reflected two true parallel servers with one arrival rate and one service rate.
All performance measures learned in lecture regarding queuing theory thus far were
calculated and placed in the summary table below. Thus you can ask any question of
the name given and find its corresponding value from this table.
10 | P a g e
Part C
The results of parts (a) and (b) can be summarized in the following table:
When we analyzed part (a) by itself, we see that the marketing department has a
shorter time in system value (W) than the finance department. This is expected because
the marketing department receives less letters a day than the finance department, while
both have the same processing capabilities. However, we can note that the effective
service rate for each department is equal to the arrival rate of letters to each
department. Therefore, within the same time span, the marketing department must type
15 letters while the finance department must type 20.
When the typists for each department work together, we have the lowest time in system
value (W) of 0.078 days. Letters arrive at a rate of 35 letters per day while they can be
processed at 50 letters per day. Because a letter can go to either typist, the W value is
lower since a letter is not waiting on only one typist. This queuing system is the more
opportune system.
11 | P a g e
ρ = .80
WAVG = 0.15
day
ρ = .60
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
λMarketing=15 𝑑𝑎𝑦
Lq = .9 Letters MarketingDept. μMarketing=25 𝑑𝑎𝑦
L = 1.5 Letters
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
W = 1/10 day
VS
Finance Dept.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25 𝑑𝑎𝑦
ρ = .70
𝑙𝑒𝑡𝑡𝑒𝑟𝑠 𝑙𝑒𝑡𝑡𝑒𝑟𝑠
λM&F=35 Lq = 1.33 Letters μM&F=50
𝑑𝑎𝑦 𝑑𝑎𝑦
L = 2.73 Letters
W = .078 day
MarketingDept.
𝑙𝑒𝑡𝑡𝑒𝑟𝑠
μ = 25
𝑑𝑎𝑦
12 | P a g e
Part D
The problem states, “Under the pooled arrangement, what is the probability that more
than .200 day will elapse between a request for a letter and completion of the letter?”
In other words, what is the probability that the total time in the system, W, is more than
.200 day.
First off, we must locate the necessary formula to calculate the distribution of waiting
time. To determine the probability, we need to know the distribution of a letter’s waiting
time. On page 1090 the following formula is given:
1 − 𝑒 −𝜇𝑡(𝑠−1−𝑠𝜌)
𝑃(𝑊 > 𝑡) = 𝑒 −𝜇𝑡 {1 + 𝑃(𝑗 ≥ 𝑠) }
𝑠 − 1 − 𝑠𝜌
The t value given in the problem statement is .200 day. From Part C, we know all other
values in the equation. Now, we just have to plug and chug numbers:
𝟏 − 𝒆−𝟐𝟓(.𝟐)(𝟐−𝟏−𝟐(.𝟕))
𝑷(𝑾 > .200) = 𝒆−𝟐𝟓(.𝟐) {𝟏 + (. 𝟓𝟕) }
𝟐 − 𝟏 − (𝟐)(. 𝟕)
13 | P a g e
WINQSB- Performance Measures & Cost Analysis
Cost values were chosen for this problem and their relative calculations were made in
the table below. The following costs given are:
Cs (Cost of Busy Server) at $72/day. This value was chosen based on an 8 hour
Notice work day and a typist working at $9/hour.
these Ci (Cost of Idle Server) at $72/day. This value was chosen based on an 8 hour
values are work day and an idle typist costing the company $9/hour.
the same Customer Waiting- It costs the company $1/day for a letter to be waiting in the
queue to be typed.
Loss in Good Will- It costs the company $.08/letter of the goodwill of the
customer bringing the letters to be typed.
Cost of Space- Since letters are so small, the cost of space is almost negligible
at $.02/letter. However, to reflect understanding of material, it was calculated in
the cost table.
Loss of Customer- N/A with ∞ Capacity
14 | P a g e
The Queuing System problem was input into WinQSB. The values calculated in the
Cost Table (Table 3) and Performance Measure Summary (Table 1) match that of
WinQSB.
Additionally, WinQSB contains a probability and cumulative probability feature that can
be seen Figure 6 below:
15 | P a g e
Figure 6: WinQSB Output- System Probability Summary
The application/use of the system probability summary in Figure 6 can be utilized in situations
like:
Finding the probability that there are more than a specific number of letters in the
system. For example, what is the probability that there are more than 5 letters in the
system? 7 letters? 10 letters? 20 letters?
Finding the probability that there are a specific number of letters in the system. For
example, what is the probability that there are 0 letters in the system? 11 letters? 15
letters? 20 letters?
Finding the probability that there are less than a specific number of letters in the system.
For example, what is the probability that there are less than 3 letters in the system? 5
leters? 10 letters?
16 | P a g e
P(j<5) = 1-P(j>4) = 1-.8023 = .1977 = 19.77%
P(j<10)= 1-P(j>10) = 1-.9767 = .0233 = 2.33%
Finding the probability that there are less than or equal to a specific number of letters in
the system. For example, what is the probability that there are less than or equal to 5
letters in the system? 10 letters? 20 letters?
17 | P a g e
WINQSB- Sensitivity Analysis
We chose to do our first sensitivity analysis on Arrival Rate. Currently, the arrival rate is
35 letters/day. We created a range above and below this number. From past research,
we know that a minimum of 25 letters/day arrive for the typists to type and at maximum
50 letters/day. We decided to stop at 50 because when arrival rate equals the service
rate (which is currently 50), the system will blow up due to variation.
and all costs go up. This was expected because naturally, having more letters in the
system causes such a relationship (common sense).
18 | P a g e
Figure 8: WinQSB Output Table- SA #1
WinQSB also has the capabilities of showing all the performance measures given in the table above in a graphical form.
We chose to graph the system utilization graph. As was already discussed, as arrival rate increase so does the system
utilization. This is indicated by the positive slope of the graph in Figure 9.
Figure 9: WinQSB Output Utilization Graph- SA #1
Sensitivity Analysis #2: Service Rate
We chose to do our second sensitivity analysis on Service Rate. Currently, the service
rate is 25 letters/day. We created a range above and below this number. From past
research, we know that a minimum of 10 letters/day can be typed by the typists and a
maximum 35 letters/day.
From the output, at service rates ranging from 10 letters/day to 17 letters/day the
system is unstable. At a service rate of 18/letters per day, the system can begin to
handle the 35 letters/day arrival rate.
and all costs decrease. This was expected because naturally, processing letters at a
faster rate causes such a relationship (common sense).
21 | P a g e
Figure 11: WinQSB Output Table- SA #2
Again, we chose to graph the system utilization graph. As was already discussed, as service rate increases system
utilization decreases. This is indicated by the negative slope of the graph.
Figure 12: WinQSB Output Utilization Graph- SA #2
When we put the two graphs from Figures 9 and 12 side by side in Figure 13, we can
see that there is an inverse relationship of system utilization when we either increase
arrival rate (left graph) system utilization goes up or increase service rate (right graph)
system utilization goes down.
Bibliography:
Chang, Yih-Long, and Kiran Desai. WinQSB Version 2.0. New York: Wiley, 2003. Print
Winston, Wayne L. Operations Research Application and Algorithms. 4th Edition. New York;
Software Used:
24 | P a g e