\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Automated Queue Management System},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2016-01-15 (revised: 15 January 2016)}
\def\TheID{\makeatother }
\def\TheDate{2016-01-15}
\title{Automated Queue Management System}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Md. Nasir  Uddin}

             \author[2]{Md. Nasir  Uddin}

             \author[3]{Md. Nasir  Uddin}

             \author[4]{Md. Nasir  Uddin}

             \affil[1]{  International Islamic University Malaysia}

\renewcommand\Authands{ and }

\date{\small \em Received: 8 December 2015 Accepted: 31 December 2015 Published: 15 January 2016}

\maketitle


\begin{abstract}
        


Automated queue management system is a system that helps service provider to manage customer in efficient way. The system can ease the customer flow management which is useful for manager of the service provider. The purpose of this project is to develop an Automated Queue Management System for organizing queuing system that can analyze the queue status and take decision which customer to be served first. This project focuses more on the banks queuing system, different queuing algorithm approaches which are used in banks to serve customer and the average waiting time. This queuing architecture model can switch between different scheduling algorithms according to the testing result i.e. the average waiting time by using two different queue control systems, which have developed. There are several process undergo, which control by Intel Galileo Microcontroller that is software-compatible with the Arduino software development environment. Finally, the systems have been tested under different conditions to evaluate its performance.

\end{abstract}


\keywords{two different queue control systems, which have developed.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction a) Background}]{Introduction a) Background}\par
owadays, customer service oriented companies facing difficulties of lengthy queues. These problems often occurred in the banks, post office and airport and it became worsen when the time reached peak hour. The improper management of such queues will cause tension and stress among customers and employees. Customers will tend to shift to other service companies that provide better services and it reduced job satisfaction of the employees.\par
According to Bain \& Company net, a global management -consulting firm, "a customer is four times more likely to defec to a competitor if the problem is service related than price or product related". Moreover, Lee Resources International net, a general business consulting stated that for "every customer complaint there are 26 other unhappy customers who have remained silent". Thus, any companies need a provide good services in order to attract customers to attain sustainability doing business.\par
In general, queuing is a line of people waiting to be serve and the movement is from a central to a specific place. Thus, a queue management system must handle and organized queue formation in the most efficient way. 
\section[{b) Problem Statement}]{b) Problem Statement}\par
Many companies provide queue management system for controlling queues of people in various situations and locations in a queue area. Most of the techniques used are manually for a small space and simple flow. On the other hand, automated queue management system deal for a larger space and complex flow. These can be see widely used in banks, hospitals or clinics and post offices.\par
Bylayat, Nahid, Moqbull and Habibur (2011) had designed a Microcontroller Based Electronic Queue Control Systems. The aim of that designed systems is to maintain a queue with order and efficiency. There are two different queue control systems which have been implemented with slightly different queue control systems which have been implemented with slightly different features in the research which are EQC system-1 and EQC system-2, EQC system-1displays token number and service counter number whereas EQC system-2 display token number individually in each service counter with separate displays.\par
The fundamental of the designed system is similar like the one, which has been use broadly todays in queue area. The flexibility is that customers have the flexibility of being processed by more than one service point and service points possess the capability of processing more than one customer class. However, the system cannot integrate to the number of customers per certain time. The sytem cannot change and remain it is when there are not much customers in the waiting area and when there are crowded of customers in the waiting are.\par
Therefore, the purpose of this research is to design and built an automatic queue management system that has more flexibility when dealing with its surrounding. 
\section[{c) Research Objectives}]{c) Research Objectives}\par
The aim of this research is to develop an Automated Queue Management System in a way that solve queuing problems. The objectives of this project to:\par
1) Investigate the current approaches for queue management system. 2) Design a working system for automated queue control system. 3) Implement the system using mechatronic solution. 4) Evaluate the system for effectiveness. 
\section[{d) Research Questions}]{d) Research Questions}\par
The study is conduct based on these two research questions:\par
1) Which surrounding should be use as model to develop an automatic queue management system? 2) What are the parameters should take in order to achieve optimal performance in queue system? 
\section[{e) Project Scope}]{e) Project Scope}\par
The Automated Queue Management System is design to manage certain customers with single department and multiple counters. There are three operations, which customers can choose i.e. Service A, Service B, Service C and three customer counters that provide services i.e. Counter 1, Counter 2 and Counter 3. The related information of this system will be displayed at the display module i.e. Liquid Crystal Display and sound module i.e. Buzzer.f) Research Methodology g) Gantt Chart Chapter 2 II. 
\section[{Literature Review a) Introduction}]{Literature Review a) Introduction}\par
A queue management system is the organization of queues of people within a retail or public sector department. It can be either reactive through a system that can organize the existing queue or proactive through queue management statistics gathering system, so that the trends can be identified and anticipated. People that join queue in a standing line queue are direct to the next position by the system or be given issued with a ticket. With a ticketed system, customers are took out of the standing line queue, which can give comfort and less stress for the customers as well as their turns are not neglect. This queuing environment is and essential part of our daily lives and it is important for manufacturer to build the most cost-effective queuing solution. 
\section[{b) Types of Queue}]{b) Types of Queue}\par
There are two types of queue, which are structured and unstructured queues. Structured queue is a queue in a fixed form and people that included are in predictable position. We can see this at supermarket paying counter and some other retail locations such as banks and post offices. This type of queue systems often being set up to manage ticket ranking for a service with identification and thus enable a stress-free waiting. Extending the different possibilities, some of this system is planned reception by appointment or remotely rank allocation on Smartphone or through SMS.\par
Whereas, unstructured queue is where people form a queue in unpredictable and varying locations and directions. This is often the case in some forms of retail, taxi queues, ATMs and at period of high demand in many situations. Some of the existing solutions are rank allocation for service, pages or RFID badges or simply by reading the customer card. In fact, it is hardly to implement a way of structuring these queues to be successful. The reason is that one cannot easily calculate the behavior of man. 
\section[{c) Queue Management Techniques}]{c) Queue Management Techniques}\par
Various queue management techniques exist are physical barrier, signage and signaling systems and automatic queue measurement system.\par
Physical barrier is aim at guiding queue formation and organizing it in a neat way. While signage and signaling systems are aim to provide information to people, queuing and aid efficient queue formation flow as well as setting service expectations. Differently, automatic queue measurement system uses a variety of measurement technologies, which predict and measure lengths and waiting times, which provide management information to help service levels and resource deployment. 
\section[{d) Queue Management Concept}]{d) Queue Management Concept}\par
Many researches have done previously on the queue management concepts such as Shortest Processed First 9SPF), First Come First Serve (FCFS), Singe Queue (SQ), Multiple Queue (MQ), Diffuse Queue (DQ) and Head of Queue (HQ).\par
SPF works as scheduling policy that choose lesser time execution to process first. In a supermarket, a specific paying counter only process transaction which customer buying goods less than 10 goods. SPF can work well because of its simplicity and minimizes the average amount of waiting time for each process. However, the setback is that it requires long time to complete if short process are continually add and customers do not perceive the right degree of fairness from the system. It is important to explain why customers are being serve in that order and ensure the understanding of customers to see the logic of this alternative approach.\par
On the other hand, FCFS is a method that deal the oldest entry being process first. FCF's behavior is where people leave the queue in the order, which they arrive. It is the most fairly service provision where all customers think of themselves as equal.\par
The single queue, SQ is the familiar snake format. Each person waiting is serve in turn and the format discourages pushing in. The queue also provides visible reassurance to customers that they will be serve fairly while the queue is progressing.\par
Besides that, the multiple queue, MQ is the improvement of SQ, it is essential to use this method when handling larger amount of people. This queue is the format that always being use at the supermarket.\par
Other than that is the diffuse queue, DQ, which has no formal queue line but customers registr place in 
\section[{Global Journal of Management and Business Research}]{Global Journal of Management and Business Research}\par
Volume XVI Issue I Version I 
\section[{Year ( )}]{Year ( )}\par
A the process with a ticket. Figure 2.1 is the example of using this method.\par
Last is the head of queue, HQ, which place the next person to be serve waits in a single queue environment. This method is significant when the number of checkout is higher than five. It is vital that customers able to see along the line of service position to avoid significant gaps in service provision. In order to maintain fairness in this system, there are several rules have been set: ? Queue must be fair and be managed systematically that cannot allowed to descend into a chaotic situation.\par
? Perception of waiting time should be manage.\par
? The process must be clearly identify; start and ends must be visible. ? The process must include positive feedback of progress. 
\section[{e) Advantages of Queue Management System}]{e) Advantages of Queue Management System}\par
Queue management system gives benefits either to customer service provider or to the customer itself. The benefits can be directly or indirectly to the system. There are:\par
? Keeps track and forecast the flow of customers.\par
? Optimum utilization of staff forecast.\par
? Constant monitoring the staff's performance.\par
? Enhance productivity and morale of the staff, as operation were efficient and systematic. ? Gives flexibility in dealing with customers.\par
? Increase service reliability, as customers are treated fairly and efficient. ? Producing statistical reports, which facilitate top management's decision making process. 
\section[{f) Eisting Queue Management System}]{f) Eisting Queue Management System}\par
There are many products available on the market produced by many queue management companies for delivering optimum customer service, which are Stand Alone Queue System and Centralized Control Queue System. 
\section[{i. Stand Alone Queue System}]{i. Stand Alone Queue System}\par
Stand Alone Queue System (SAQS) design based on First Come First Serve, FCFS queue model, where there is only one service counter operation. All customers will be manage at the single counter. This system operates by calling or displaying number in sequential or randomized order and the customers will be treat fairly. The SAQS is performing well in a single department, service operation environment such as clinic. 
\section[{ii. Advance Queue System}]{ii. Advance Queue System}\par
Advance Queue System (AQS) based on SAQS design where additional service counters are add to give flexibility in queue system process. This system can support up to 32 service counters and additional of 60 counters. It also can provides useful queue features as well as comprehensive reports. Besides that, it allows manager of real-time monitoring status for the queue management analysis. AQS is performing well in bank, hospital or any organization that has multiple department service operation. 
\section[{iii. Centralized Control Queue System}]{iii. Centralized Control Queue System}\par
Centralized Control Queue System (CCQS) design is use for higher range of customers in different department. This system has the capability to support up to 20 departments which each department can have up to 32 service counters and 60 counters. CCQS is network compatible because each department has been located at different part of a building or even in geographical area. Thus, CCQS is connect through LAN or Internet and it also provide real-time status monitoring. 
\section[{g) Customer Flow Management}]{g) Customer Flow Management}\par
There are few manager of service provider know what happens with their customers throughout the whole interaction process in real-time. If the supply and production managers know the flow of material and product in detail, why does not the head of operations know the flow of customers equally well? Is the flow of customers less important than the flow of material and products? Is the flow of customers more difficult to monitor and control? By knowing absolutely the customers is a key success factor for any service provider that wants to be competitive. Therefore, Customer Flow Management (CFM) is managing the flow of customers and their experience from initial contact to final service delivery.\par
The Customer Flow Management process consist of several phases including pre-arrival, arrival, queuing or waiting, serving, post-serving and managing as illustrated in figure 2.14. It is view of the entirety of the customer service operation, the resulting framework for making informed business decisions and the frames the boundaries of CFM. 
\section[{i. Pre-arrival}]{i. Pre-arrival}\par
CFM can start before the customers physically visits the shop or service center by implementing a method to book appointments before arrival. This reduces the time spent waiting by the customer and produce a positive impact on the customer's service experience. 
\section[{ii. Arrival}]{ii. Arrival}\par
Customers need to be place in an appropriate queue on arrival. Customer Flow Management stresses the possibility of segmenting the customers in different queues rather than entering all customers in the same queue.\par
iii. Queuing/waiting Most customers will endure a period of waiting after queue entry. A balanced and controlled waiting period is the desired optimum results of any managers.\par
No one wants to have a completely empty waiting area as it reflected that you are overstaffed or impression of abandonment. Equally, too many customers waiting is simply as off-putting. In the case of a hospital or public service center, certain citizens might not accept it as they can demonstrate this during elections. CFM can help managers get the balance rightly by improving staff planning and by adding more flexibility to the process. iv. Serving When calling the customer forward, staff can start preparations if the service chooses to identify and tracking customer's history before the customer actually arrives at the service point.\par
v. Post-serving After a customer has been serve, a case handling function can continue to manage the case throughout its lifetime if needed and each step is document and process.\par
vi. Managing Managers can uses the gathered data in CFM process to evaluate the current processes. Reports can be generate on employee-customer interactions, service times and customer wait times. Operational inefficiencies can be identified and addressed through process changes or training.  
\section[{System Design a) Conceptual Design}]{System Design a) Conceptual Design}\par
Banks have been one of the major units of the public for the past years. Many researchers try to develop new technology in order to increase customer satisfaction. Thus, an active research should be focuses on analyzing the queues to optimize their operations, which customer's waiting time can be reduce.\par
In this research paper, an automated queue control system has been develop for organizing queue in banking for a low-cost and efficient way. The system can analyses the queue status and take decision which customer to serve, as the factor of the average waiting time is take into consideration. 
\section[{b) System Design Overview}]{b) System Design Overview}\par
The scenario of the proposed system can be described as shown in the Figure  {\ref 2}.1. Customer will select required services either Service -A, Service-B or Service-C and gets an acknowledgement receipt. The receipt consists of information like token number, service selected, date, time and retail or organizational name. The customer proceeds towards the service counter when his token number displayed on the screen. Therefore, instead of worrying about their places in the line, customers can relax and have a great customer service experience.\par
The automated queue control system can be divide into several process. First, customers will select require service and proceed to the waiting area. The system will records the customers token number with the type of service selected. Then, the system will analyzes the data collected and decides customers turn to be serve. At the waiting area, a display will be place and shows customers token number and service counter number that indicate which customer to be serve next. Lastly, different display located at the different service counter will display current customer's token number which is now being serve. 
\section[{c) Component Selection i. Intel Galileo Gen-2}]{c) Component Selection i. Intel Galileo Gen-2}\par
The Intel Galileo board is a microcontroller board based on the Intel Quark soC x 1000 application processor, a 32-bit Intel Pentium brand system on a chip (soC). It is the second-generation board based on Intel Architecture design to be hardware and software pin-compatible with shields designed for the Arduino Uno R3.\par
In addition to Arduino hardware and software compatibility, the Intel Galileo board has several PC industry standard I/O ports and features to expand native usage and capabilities beyond the Arduino shield ecosystem. A full-sized mini-PCI Express slot, 12V power-over-Ethernet (PoE) capable, Micro-SD slot, 6pin FTDI header, USB host port, USB client port and 8 Mbyte NOR Flash come standard on the board. 
\section[{ii. Push-Button}]{ii. Push-Button}\par
A push-button is a simple switch mechanism for controlling some aspect of a machine. It is usually made of hard material likes plastic or metal. To accommodate the human finger or hand, the surface is usually flat. The push-button is required for this project as input from the arriving customers and as the control pendant at the service counter. 
\section[{iii. Liquid-Crystal Display}]{iii. Liquid-Crystal Display}\par
A liquid -crystal display (LCD) is a flat panel that uses the light modulating properties of liquid properties of liquid crystals. Liquid crystals do not emit light directly. LCDs are available to display arbitrary images or fixed images which can be display or hidden, such as preset words, digits and 7-segment display as in digital clock. They use the same basic technology, except that arbitrary images are made of a large number of pixels, while other displays have larger elements. For this project, LCD is use for displaying token number at ticket counter, waiting area and service counter. 
\section[{iv. Buzzer}]{iv. Buzzer}\par
A buzzer or beeper is an audio signaling device, which may be mechanical, electromechanical or piezoelectric. Typical uses of buzzers and beepers include alarm devices, timers and confirmation of user input such as a mouse click or keystroke. For this project, buzzer is use for alarming which indicate of next customer service at the service counter. 
\section[{v. Ds307 Real-Time Clock Module}]{v. Ds307 Real-Time Clock Module}\par
The DS1307 Real-Time Clock is a low power, full binary-coded decimal (BCD) clock plus 56 bytes of NV SRAM. The clock provides seconds, minutes, hours, day, date, month and year information. Address and data are transferred serially via a 2-wire, bi-directional bus. The DS1307 has a built-in power sense circuit that detects power failures and automatically switches to the battery supply. Meanwhile, the DS1307 happens to possible the getting of customers arrival time data. which is important for the system analysis. 
\section[{vi. PCF8574N}]{vi. PCF8574N}\par
The PCF8574N is an 8 bits I/O port expander that uses the 12C protocol, which communicates using a 2-wire seria interface i.e. one wire is a serial clock (SCL) and the other is for serial data (SDA). The reason for choosing the PCF8574N is to minimize the using of Galileo ports for LCD's circuitry. 
\section[{d) Complete Circuit}]{d) Complete Circuit}\par
All the hardware components are connect together as shown in the figure below.  
\section[{e) Bill Of Material}]{e) Bill Of Material} 
\section[{Result and Discussion}]{Result and Discussion} 
\section[{a) Analysis on Input Module i. Push Button}]{a) Analysis on Input Module i. Push Button}\par
There are total of six push buttons used for connecting the Galileo. The pins used are digital pin 2 to digital pin 7. Push buttons for digital pin 2, 3 and 4 used for collecting data from customers. They will choose either service A, B or C. In contrast, push buttons for digital pin 5, 6 and 7 are place at the service counter. Teller will use it to call for next customer to provide require service.\par
The way a push button works with Galileo is that when the button is pushed, the voltage will goes Low, which in turn Galileo read this and reacts accordingly. A pull-up resistor is use to keep the voltage HIGH when the push button is not being press. In other words, a small amount of current is following between VCC and the input pin (not ground). thus the input pin reads close to VCC. 
\section[{ii. DS1307 RTC Module}]{ii. DS1307 RTC Module}\par
The DS1307 RTC module works very well in keeping the time. However, the external temperature can affect the frequency of the oscillator circuit, which drives the DS1307's internal counter. This may sound like a problem, however it usually result with the clock being off by a round five or so minutes per month. Besides that, proper ventilation is use for the container in this project. 
\section[{b) Analysis on Output Module i. LCD}]{b) Analysis on Output Module i. LCD}\par
A standard 16x2 LCD is use but using just two pins. The way it can achieve by the PCF8574, an I/O expander that communicates with Galileo by 12C. With this IC, two ports of Galileo can control up to eight digital I/O ports. In the 12C protocol, each IC has different address. In this project, first four of the address is use as there are four different LCDs used.\par
ii. Buzzer A piezo buzzer will makes a small "click" when voltage is applying to it. If the voltage is turn on and off hundreds of times per second, the piezo buzzer will produce a tone. Then, if a bunch of tones is string together, it will produce a music. Simple music will ring when a service counter calls a customer. 
\section[{c) Algorithm Development i. Rule Based System}]{c) Algorithm Development i. Rule Based System}\par
Rule based system is a system. which problems can written in the form of IF-THEN rules. The problem are usually is not large. If there are too many rules, the system can become difficult to maintain and can suffer a performance hit.\par
In this project, there are three rules will be looking at before deciding which one will be implemented in the system. There are:\par
1) Rule 1: All service counters are multipurpose type. 2) Rule 2: Service counter 1 only for customer choosing Service-A. 3) Rule 3: Each service has one service counter.\par
In addition, two parameters set for all the rules, which are Service-A, B and C have duration to complete 60sec, 120sec and 180sec respectively. The second parameter is that customer is assume to follow this arrangement: "customer-A customer-B customer-C customer-A customer-B customer-C?" Figure  {\ref 4}.4 shows that Rule 1 is the least time consuming to finish all the customers and thus the rule will be use throughout this project.\par
ii. Queuing System Model This part presents a different technique for queue management system in banks proposed by \hyperref[b0]{Ahmed and Huda (2011)}. The technique can build an automated queue control system by using the DQ concept. To select the next customer to be serve during a specific period, the system chooses and appropriate algorithm among more than one scheduling algorithm, which are FCFS and SPF.\par
Moreover, to achieve the best waiting time for all the customers that are waiting to be serve, it is depend on the testing result for selecting the scheduling algorithm. To achieve this, additional components to the traditional queue management system are need.\par
In customer area, customer selects required service at the ticket counter and waits until the ticket number shown in a display.\par
In queuing area, the system chooses one of the waiting customers by using the queuing algorithm that is choose by the testing area.\par
In testing area, the system test and compare all the result for the expected waiting and response time then selects the best algorithm.\par
All the needed scheduling algorithms, the testing result and the number of customers are stored in this area. The testing result and the customer's numbers are save temporarily.\par
In service area, the system serves the customer according to the different services that a bank can gives such as transaction, open account and balance. Each service has their own specific time. 
\section[{iii. Result Analysis}]{iii. Result Analysis}\par
To test the performance of the new proposed system, several simulations were carry. A randomized generated number is use to generate a sequence of customer's arrival time and option of services that they can choose. The different services are open an account, transaction and balance with the period of each services which are 15, 10 and 5 minutes respectively. In this proposed system, two scheduling algorithm are used which are FCFS and SPF. Differs to the ordinary system (FCFS) which is usually being use in the most of the banks queuing system. The proposed system will test the queuing system using testing algorithm every specific period, consider in this research to be 15 minutes. Then, make comparison of the results of waiting time and average waiting time. The results shown in figure  {\ref 4}  Through the extensive experiments conducted, the primary goal is to determine the ability of the new queuing system against the ordinary queuing system. Figure  {\ref 4}.7 shows that the new approach decreases the average waiting the time compared to the ordinary queuing system while Table \hyperref[tab_0]{3} shows the average waiting time for the ordinary queuing system and the new queuing system.   
\section[{Conclusion and Recommendation a) Conclusion}]{Conclusion and Recommendation a) Conclusion}\par
Design and development of Automated Queue Management System starts with the understanding of the queue system itself. which is very crucial to broaden the horizon of understanding. Then, the consideration of the control strategy and component to be use plays important role as guidelines to accomplish this project.\par
In addition, several articles have been review to investigate the current approaches for queue management system. Although the current approaches have proven to ease and give benefits to service providers, yet there are space of improvement in order for a queue system function efficiently.\par
Besides that, the early queue system design for this FYP (implemented using mechatronics solution) has been present on the chapter 3 and several analysis were carry on the chapter 4 of this report. 
\section[{b) Limitation}]{b) Limitation}\par
The assumption of the queuing theory may be too restrictive to be able to model real-world situations exactly. The mathematical models often assume infinite number of customers, infinite queue capacity or constant inter-arrival or service times (same service type), when it is quite apparent that these bounds do not exist in reality. In other words, the theoretical solution may prove insufficiently informative to be useful. 
\section[{c) Recommendation}]{c) Recommendation}\par
There are some improvement can be made such as addition of sensors of cameras that can detect customers at a certain time. This method can improve the efficiency of a queue system as it alerts manager to counter fast on the situation. Lastly, the system can being made to become a product as in this project only being made as for research and learning.\begin{figure}[htbp]
\noindent\textbf{47}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Fig. 4 . 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3} \par 
\begin{longtable}{P{0.5105345911949685\textwidth}P{0.04544025157232705\textwidth}P{0.2940251572327044\textwidth}}
Component\tabcellsep Bill\tabcellsep Expected Price (RM)\\
Intel Galileo Gen-2\tabcellsep 1\tabcellsep RM 245.00\\
LCD (16x2)\tabcellsep 4\tabcellsep RM 80.00\\
PCF8574N\tabcellsep 4\tabcellsep RM 32.00\\
Wire Jumper\tabcellsep 100\tabcellsep RM 13.60\\
Trimpot 10K\tabcellsep 4\tabcellsep RM 8.00\\
DS1307RTC Module\tabcellsep 1\tabcellsep RM 6.30\\
Plastic Container\tabcellsep 1\tabcellsep RM 5.90\\
6x6x1 Push Button 4 Pin\tabcellsep 6\tabcellsep RM 3.30\\
Screw and Screw PCB Stand\tabcellsep 4\tabcellsep RM 2.80\\
Buzzer 6-12v\tabcellsep 1\tabcellsep RM 3.00\\
Resistor 10k?\tabcellsep 8\tabcellsep RM 0.40\\
Total\tabcellsep \tabcellsep RM 400.30\\
Chapter 4\tabcellsep \tabcellsep \\
IV.\tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_0}Table 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.12027027027027026\textwidth}P{0.05405405405405405\textwidth}P{0.013513513513513513\textwidth}P{0.5135135135135136\textwidth}P{0.002702702702702703\textwidth}P{0.04189189189189189\textwidth}P{0.02837837837837838\textwidth}P{0.07567567567567567\textwidth}}
\tabcellsep \tabcellsep c.\tabcellsep \multicolumn{3}{l}{? Testing Area Testing 3 rd 15 minutes using the two scheduling algorithms}\\
\tabcellsep \tabcellsep \tabcellsep FCFS\tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{C9}\tabcellsep C10\tabcellsep C11\tabcellsep C12\\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{75 80 SPF}\tabcellsep 90\tabcellsep 100\tabcellsep 105 ? Scheduling Algorithm Database Area\\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{C6}\tabcellsep C7\tabcellsep C8\tabcellsep C9\\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{75 80}\tabcellsep 85\tabcellsep 95\tabcellsep 105\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep ? Service Area\\
Year\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
36\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Volume XVI Issue I Version I\tabcellsep ? Customer Area\tabcellsep \tabcellsep \tabcellsep \\
( ) A\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Global Journal of Management and Business Research\tabcellsep FCFS C1 ? Queuing Area C2\tabcellsep C3 a. b.\tabcellsep \multicolumn{3}{l}{C4 Fig. 4.6 : Ordinary Queuing System Gantt chart C5 C6 C7 C8 C9 Testing first 15 minutes using the two scheduling algorithms C10 C11 FCFS C1 C2 C3 C4 C5 0 15 20 3 5 50 60 SPF C1 2 C5 C3 C4 0 15 20 30 45 60 Testing 2 nd 15 minutes using the two scheduling algorithms}\tabcellsep C12\\
\tabcellsep \tabcellsep \tabcellsep FCFS\tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{C6}\tabcellsep C7\tabcellsep C8\tabcellsep C9\\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{60 15}\tabcellsep 20\tabcellsep 35\tabcellsep 50\\
\tabcellsep \tabcellsep \tabcellsep SPF\tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{C6}\tabcellsep C7\tabcellsep C8\tabcellsep C9\\
\tabcellsep \tabcellsep \tabcellsep 60\tabcellsep 65\tabcellsep 70\tabcellsep 75\tabcellsep 80\end{longtable} \par
 
\caption{\label{tab_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5} \par 
\begin{longtable}{P{0.5759868421052632\textwidth}P{0.11631578947368422\textwidth}P{0.09506578947368421\textwidth}P{0.04361842105263158\textwidth}P{0.015657894736842103\textwidth}P{0.003355263157894737\textwidth}}
Time Slice\tabcellsep Average Waiting Time and\tabcellsep Average Waiting Time and\tabcellsep \multicolumn{3}{l}{Difference the between}\\
\tabcellsep Algorithm (Ordinary Queuing\tabcellsep Algorithm (New Queuing\tabcellsep Ordinary\tabcellsep and\tabcellsep New\\
\tabcellsep System)\tabcellsep System)\tabcellsep Algorithm\tabcellsep \\
1 st Group\tabcellsep 16.4/FCFS\tabcellsep 14.4/SPF\tabcellsep \tabcellsep 2\\
2 nd Group\tabcellsep 42.5/FCFS\tabcellsep 42.5/FCFS\tabcellsep \tabcellsep 0\\
3 rd Group\tabcellsep 47/FCFS\tabcellsep 43.66/SPF\tabcellsep \tabcellsep 3034\\
Total Average\tabcellsep 32.75\tabcellsep 31.083\tabcellsep \tabcellsep 1.667\\
Waiting Time\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{Equation 1 used to calculate the waiting time for}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{each customer and Equation 2 used to calculate the}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{average waiting time for each group of customers}\tabcellsep \tabcellsep \tabcellsep \\
(Willin, 1999).\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{CWT I = SSTC I -ATC I}\tabcellsep \tabcellsep \tabcellsep \\
Where:\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{CWT is a Customer Waiting Time}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{SSTC is a Start Serving Time for a Customer}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{ATC is Arrival Time for a Customer}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{I is the number of customer}\tabcellsep \tabcellsep \tabcellsep \\
\tabcellsep AWT =(?CWT i)/TN\tabcellsep \tabcellsep \tabcellsep \\
Where:\tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{AWT is Average Waiting Time}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{CWT is a Customer Waiting Time}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{TN is total number of customer served}\tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{2}{l}{i is the number of customer}\tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_2}Table 5 :}\end{figure}
 			\footnote{© 2016 Global Journals Inc. (US) 1} 			\footnote{© 2016 Global Journals Inc. (US)} 			\footnote{Automated Queue Management System} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Willig ()]{b12}\label{b12} 	 		‘A Short Introduction to Queuing Theory’.  		 			Willig 		.  	 	 		\textit{Telecommunication Networks Group Sekr. FT 5-2},  				 (Berlin)  		1999.  		 			Technical University Berlin 		 	 
\bibitem[Ab ()]{b9}\label{b9} 	 		 			Q-Matic Ab 		.  		\textit{an Introduction to Customer Flow Management, Version L1.5},  				2008.  	 
\bibitem[Sanjay ()]{b10}\label{b10} 	 		\textit{an Introduction to Queuing Systems},  		 			Bose K Sanjay 		.  		2002. Springer.  	 
\bibitem[Ahmed and Huda ()]{b0}\label{b0} 	 		\textit{Automatic Queuing Model for Banking Applications},  		 			S A Ahmed 		,  		 			K T Huda 		.  		2011.  	 
\bibitem[Hossain et al. ()]{b3}\label{b3} 	 		‘Design and Development of Microcontroller Based Electronic Queue Control Systems’.  		 			Md B Hossain 		,  		 			Md N Hossain 		,  		 			Hossen 		,  		 			. M Md 		,  		 			Md H Rahman 		.  	 	 		\textit{Proceeding of the 2011 IEEE Students' Technology Symposium},  				 (eeding of the 2011 IEEE Students' Technology Symposium)  		2011.  	 
\bibitem[Tocci ()]{b11}\label{b11} 	 		\textit{Digital Systems},  		 			R J Tocci 		.  		2000. New Jersey: Prentice -Hall. 7.  	 	 (th edition) 
\bibitem[Zhang and Tay ()]{b13}\label{b13} 	 		‘Discrete-event simulation of queuing systems’.  		 			No \& Zhang 		,  		 			Tay 		.  	 	 		\textit{Ministry of Education},  				 (Singapore)  		2000.  	 	 (published in the Proceedings of the sixth youth conference) 
\bibitem[Lustsik ()]{b5}\label{b5} 	 		‘E-Banking in Estonia: Reasons and Benefits of the Rapid Growth’.  		 			O Lustsik 		.  	 	 		\textit{Kroon and Economy}  		2003. 3 p. .  		 			University of Tartu 		 	 
\bibitem[Mobarek ()]{b7}\label{b7} 	 		‘E-Banking Practices and Customer Satisfaction-A Case study in Botswana’.  		 			A Mobarek 		.  	 	 		\textit{th Australasian Finance \& Banking Conference},  				2007. 20.  	 
\bibitem[Fazli Alias ()]{b8}\label{b8} 	 		\textit{Front Desk Customer Service for Queue Management System},  		 			Mohamad Fazli Alias 		.  		2007.  	 
\bibitem[Goluby and Preston Mcafeez ()]{b1}\label{b1} 	 		 			B Goluby 		,  		 			R Preston Mcafeez 		.  		\textit{Firms, Queues and Coffee Breaks: A Flow Model of Corporate Activity with Delays},  				2011. Springer-Verlag. 15 p. .  	 
\bibitem[Maister ()]{b6}\label{b6} 	 		 			David H Maister 		.  		\textit{the psychology of Waiting Lines},  				2005.  	 
\bibitem[Gurumurthi and Benjaafar ()]{b2}\label{b2} 	 		\textit{Modelling and Analysis of Flexibile Queuing Systems},  		 			S Gurumurthi 		,  		 			S Benjaafar 		.  		 \xref{http://dx.doi.org/10.1002/nav.20020}{10.1002/nav.20020}.  		2004. Wiley Periodicals, Inc. DOI.  	 
\bibitem[Koole and Mandelbaum ()]{b4}\label{b4} 	 		‘Queuing Models of Call Centers, An Introduction’.  		 			G Koole 		,  		 			A Mandelbaum 		.  	 	 		\textit{Ann Oper Res}  		2002. 113 p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
