taco bell’s drive-thru - utoledo engineeringgrafe/4100/bch061.pdf · taco bell’s drive-thru...

TACO BELLTACO BELL’’S S DRIVEDRIVE--THRUTHRU

SIMULATION SYSTEMSSIMULATION SYSTEMS

MIME 4100/5100MIME 4100/5100

Ethan HooverEthan HooverNelly BarberyNelly Barbery

Matt Matt CuthbertsonCuthbertson

HISTORYHISTORY

First Taco BellFirst Taco Bell’’s facilitys facility

FACTSFACTS

Founded March 21, 1962 by Glen Bell.Founded March 21, 1962 by Glen Bell.More than 5,800 restaurants in the U.S.More than 5,800 restaurants in the U.S.Generates more than $1.8 billion in sales Generates more than $1.8 billion in sales per year.per year.Employs over 144,000 people.Employs over 144,000 people.

PROJECT SUMMARYPROJECT SUMMARY

1) Introduction1) Introduction

2) Objective2) Objective

3) Process of the system3) Process of the system

4)Experiemental Setup4)Experiemental Setup

5) System Operation5) System Operation

6) Data collection 6) Data collection

7) Results7) Results

8) Tactical consideration 8) Tactical consideration

9) Decision to the best alternative 9) Decision to the best alternative

INTRODUCTIONINTRODUCTION

The process of Taco BellThe process of Taco Bell’’s s drivedrive--through was studied through was studied because of their noticeably because of their noticeably lengthy lines at the location of lengthy lines at the location of Reynolds and Door Ave. inReynolds and Door Ave. inToledo, OH.Toledo, OH.

OBJECTIVEOBJECTIVE

Find deficiencies in the driveFind deficiencies in the drive--through through processprocess

Accurately simulate the system using Accurately simulate the system using Arena software.Arena software.

OBJECTIVEOBJECTIVEUse results to find possible improvements Use results to find possible improvements in the systemin the system

Find out:Find out:

a. The average time in systema. The average time in systemb. The average waiting time in queueb. The average waiting time in queue

PROCESS OF THE SYSTEMPROCESS OF THE SYSTEM

Inter arrival points being consider are:Inter arrival points being consider are:

1. Entity enters the system queue and it stops at 1. Entity enters the system queue and it stops at the the ““intercom boxintercom box””

2. Entity time to place an order2. Entity time to place an order

3. After the order is placed, entity goes from the 3. After the order is placed, entity goes from the ““ordering portalordering portal”” to the server windowto the server window

4. Entity at the server window4. Entity at the server window

5. Entity exits the system5. Entity exits the system

EXPERIMENTAL SETUPEXPERIMENTAL SETUP

Observed system to come up with a Observed system to come up with a proper Arena model.proper Arena model.

EntitiesEntities-- Cars going through systemCars going through system--VariablesVariables-- size of car, quantity of food and drinks ordered, size of car, quantity of food and drinks ordered, payment type, change given or not.payment type, change given or not.

ResourcesResources-- Ordering Intercom BoxOrdering Intercom Box-- Server WindowServer Window

EXPERIMENTAL SETUPEXPERIMENTAL SETUP

DelaysDelays-- Size of orderSize of order-- Number of cars in queueNumber of cars in queue-- Customer delaysCustomer delays-- UnexpectedUnexpected

-- Car break down, intercom malfunction, server difficultiesCar break down, intercom malfunction, server difficulties

SYSTEM OPERATIONSYSTEM OPERATION

DATA COLLECTIONDATA COLLECTIONData collected consisted of:Data collected consisted of:

1.1. Time study of the system (5 timings per entity)Time study of the system (5 timings per entity)2.2. Amount of food orderedAmount of food ordered3.3. Amount of beverages orderedAmount of beverages ordered4.4. Type of carType of car5.5. Type of payment Type of payment

a. Casha. Cash-- Change/no change Change/no change recievedrecieved

b. Debit/Credit Card b. Debit/Credit Card

RESULTSRESULTS

Amount of food and drinks ordered Amount of food and drinks ordered corresponded to amount of time spent at corresponded to amount of time spent at ““intercom boxintercom box”” and server window.and server window.Average time in systemAverage time in system

-- 2.74 minutes2.74 minutesAverage waiting time between resources Average waiting time between resources

-- 35.05 seconds35.05 seconds

RESULTSRESULTS

Not enough information to conclude Not enough information to conclude whether payment type affected time at whether payment type affected time at server windowserver windowType of car did not affect time through Type of car did not affect time through systemsystem

RESULTSRESULTS

RESULTSRESULTS

RESULTSRESULTS

TACTICAL CONSIDERATIONTACTICAL CONSIDERATION

Add a second server windowAdd a second server windowBenefitsBenefits•• Increase capacity of customers per dayIncrease capacity of customers per day•• Increased server availabilityIncreased server availability•• Decrease amount of time it takes to go through the Decrease amount of time it takes to go through the

systemsystemIncreasing customer satisfaction ensuring future Increasing customer satisfaction ensuring future business.business.

TACTICAL CONSIDERATIONSTACTICAL CONSIDERATIONS

LossesLosses•• Decreased server utilizationDecreased server utilization•• High cost to construct new windowHigh cost to construct new window

Loss of business during construction periodLoss of business during construction period

•• Saves only seconds off of total time in systemSaves only seconds off of total time in system

DECISION TO BEST DECISION TO BEST ALTERNATIVEALTERNATIVE

Keep the current systemKeep the current system’’s processs process

Thank YouThank You

Questions?Questions?Comments?Comments?