TACO BELL`S DRIVE-THRU

TACO BELL’S
DRIVE-THRU
SIMULATION SYSTEMS
MIME 4100/5100
Ethan Hoover
Nelly Barbery
Matt Cuthbertson
HISTORY
¾ First Taco Bell’s facility
FACTS
¾ Founded March 21, 1962 by Glen Bell.
¾ More than 5,800 restaurants in the U.S.
¾ Generates more than $1.8 billion in sales
per year.
¾ Employs over 144,000 people.
PROJECT SUMMARY
1) Introduction
2) Objective
3) Process of the system
4)Experiemental Setup
5) System Operation
6) Data collection
7) Results
8) Tactical consideration
9) Decision to the best alternative
INTRODUCTION
The process of Taco Bell’s
drive-through was studied
because of their noticeably
lengthy lines at the location of
Reynolds and Door Ave. in
Toledo, OH.
OBJECTIVE
¾ Find deficiencies in the drive-through
process
¾ Accurately simulate the system using
Arena software.
OBJECTIVE
¾ Use results to find possible improvements
in the system
¾ Find out:
a. The average time in system
b. The average waiting time in queue
PROCESS OF THE SYSTEM
¾
Inter arrival points being consider are:
1. Entity enters the system queue and it stops at
the “intercom box”
2. Entity time to place an order
3. After the order is placed, entity goes from the
“ordering portal” to the server window
4. Entity at the server window
5. Entity exits the system
EXPERIMENTAL SETUP
¾
Observed system to come up with a
proper Arena model.
z
Entities- Cars going through system
-Variables- size of car, quantity of food and drinks ordered,
payment type, change given or not.
z
Resources
- Ordering Intercom Box
- Server Window
EXPERIMENTAL SETUP
z
Delays
-
Size of order
Number of cars in queue
Customer delays
Unexpected
- Car break down, intercom malfunction, server difficulties
SYSTEM OPERATION
DATA COLLECTION
¾
1.
2.
3.
4.
5.
Data collected consisted of:
Time study of the system (5 timings per entity)
Amount of food ordered
Amount of beverages ordered
Type of car
Type of payment
a. Cash
- Change/no change recieved
b. Debit/Credit Card
RESULTS
¾ Amount of food and drinks ordered
corresponded to amount of time spent at
“intercom box” and server window.
¾ Average time in system
- 2.74 minutes
¾ Average waiting time between resources
- 35.05 seconds
RESULTS
¾ Not enough information to conclude
whether payment type affected time at
server window
¾ Type of car did not affect time through
system
RESULTS
RESULTS
RESULTS
TACTICAL CONSIDERATION
¾ Add a second server window
z
Benefits
•
•
•
Increase capacity of customers per day
Increased server availability
Decrease amount of time it takes to go through the
system
z
Increasing customer satisfaction ensuring future
business.
TACTICAL CONSIDERATIONS
z
Losses
• Decreased server utilization
• High cost to construct new window
z
Loss of business during construction period
• Saves only seconds off of total time in system
DECISION TO BEST
ALTERNATIVE
¾ Keep the current system’s process
Thank You
¾ Questions?
¾ Comments?