Smart Queue Management System Real-Time Token Queue with Emergency Priority and Phone Notifications Project Journal

Author

Pragadees A.M, Naveen K.C, Jeevanesh .T, Ms. Nishmitha K.R


Abstract

 Waiting lines in hospitals, banks, billing counters and government offices are often managed with paper slips or by customers standing in a physical line, so a person cannot tell how many people are ahead or when the turn will come. This project presents the Smart Queue Management System, a web application in which a customer obtains a digital token, follows the queue live on a phone or computer, and can register the phone for a notification about the turn. The interface is written in React with TypeScript and built with Vite. Google Firebase provides the back end: Cloud Firestore stores the tokens and counters and streams every change to the open pages in real time, Firebase Authentication protects the admin panel, Firebase Cloud Messaging is used to register devices for push notifications, and Firebase Hosting is configured to serve the built application. Token numbers are generated inside a Firestore transaction so that two customers cannot receive the same number. Approved administrators sign in with an email and password, call the next token, skip a token, create emergency tokens that are served before ordinary tokens, and reset the queue. The customer page shows the current token, the number of people ahead, a wait estimate of five minutes for each person ahead, and alerts when the turn is near and when it arrives. This journal describes the design, data model, workflow and source-level behaviour of the supplied version, lists twelve manual test scenarios, and records its limitations. These include admin checks that run in the browser, a fixed wait estimate, and the absence of the server-side notification sender and of automated tests from the supplied archive. The project demonstrates a small serverless, real-time queue application.


Keywords

Queue Management, Token System, React, TypeScript, Firebase, Cloud Firestore, Real-time Updates, Push Notifications, Emergency Priority.



Full Text:

Download Paper PDF


References


  1. Meta Open Source, “React Documentation.” Available: https://react.dev/
  2. Vite, “Vite Documentation.” Available: https://vite.dev/
  3. Microsoft, “TypeScript Documentation.” Available: https://www.typescriptlang.org/docs/
  4. Google, “Cloud Firestore Documentation.” Available: https://firebase.google.com/docs/firestore
  5. Google, “Transactions and batched writes,” Cloud Firestore Documentation. Available: https://firebase.google.com/docs/firestore/manage-data/transactions
  6. Google, “Firebase Authentication Documentation.” Available: https://firebase.google.com/docs/auth
  7. Google, “Set up a Firebase Cloud Messaging client app on the web.” Available: https://firebase.google.com/docs/cloud-messaging/js/client
  8. Google, “Firebase Hosting Documentation.” Available: https://firebase.google.com/docs/hosting
  9. MDN Web Docs, “Service Worker API.” Available: https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API
  10. D. C. Little, “A Proof for the Queuing Formula: L = λW,” Operations Research, vol. 9, no. 3, pp. 383–387, 1961.
  11. Project source code, “Smart Queue Management System,” supplied project archive, Queue-management.zip. Includes src/App.tsx, src/Admin.tsx, src/Login.tsx, src/queueService.ts, src/notificationService.ts, src/firebase.ts, src/App.css, public/firebase-messaging-sw.js, firebase.json and package.json.

APPENDIX: PROJECT ARTIFACTS USED

The journal was prepared from the uploaded project archive. Files used to ground the implementation description include: src/App.tsx, src/Admin.tsx, src/Login.tsx, src/queueService.ts, src/notificationService.ts, src/firebase.ts, src/App.css, src/main.tsx, public/firebase-messaging-sw.js, firebase.json, .firebaserc, .gitignore, package.json and the Vite and TypeScript configuration files. Figs. 1, 2 and 3 were drawn for this journal from the project structure. Figs. 4 and 5 are to be captured from the running application. The archive did not contain Firestore security rules, server-side notification code, automated tests, or any recorded test results.

 

 

Share your valuable work from Social Media Buttons