MESS QUEUEMANAGER
Shorter lines and less waiting. A smart rule system that checks the crowd at every counter, opens extra counters at rush hour, and tells you exactly where to go.
01 · Problem statement
Long lines. Empty counters.
At lunch, the mess food counters get very crowded. Some counters are full while others sit empty. We need a simple, smart rule system that checks queue size and moves students to less crowded counters, so food is served faster and nobody waits too long.
OBJECTIVES
- Reduce total waiting time for students getting food.
- Use step-by-step logic to manage line capacity.
- Open extra counters automatically during rush hours.
- Show a clear flowchart and pseudocode for the process.
- Collect and apply feedback from students and mess staff.
WHO USES IT
- Students: scan the QR code, see the best counter, crowd % and wait time.
- Mess staff: update crowd counts, receive alerts, open or close counters.
- Admin (optional): change thresholds, capacity and serving time.
Runs as a web app on any phone or laptop browser, so there's nothing to install.
02 · Upgrade
Same problem, smarter logic
| OLD LOGIC | NEW LOGIC |
|---|---|
| One overall crowd % | Crowd calculated per counter |
| Only 80% and 50% thresholds | Added 45% early alert (from survey feedback) |
| Counters could flip open/closed repeatedly | Added hysteresis: close only below 40% |
| No waiting time shown | Added estimated wait time per counter |
| No direction for students | Added "best counter" recommendation |
| Only a displayed message | Added staff alerts with a 2-minute notice |
03 · Core logic
The rules
CROWD PERCENTAGE
crowd_% = (people_in_queue / capacity) × 100
// capacity 20, people 16 → 80%
ESTIMATED WAIT TIME
wait_min = (people × avg_serve_sec) / 60
// 16 × 30 s = 480 s → 8 minutes
EARLY ALERT
Staff get a 2-minute notice to prepare the standby counter.
STAFFOPEN STANDBY
The extra standby counter opens.
STAFF + STUDENTSCROSS ACCESS
National students may use the international counters.
STAFF + STUDENTSCLOSE / NORMAL
The standby counter closes and normal routing resumes.
STAFF| CROWD % | COLOR | LABEL |
|---|---|---|
| Below 50% | GREEN | Free |
| 50% to 80% | AMBER | Busy |
| Above 80% | RED | Very crowded |
04 · Algorithm
Step by step
STEPS
- Read the queue count of every counter.
- Calculate crowd % and wait time for each counter.
- Calculate the national zone average.
- Above 80%: cross-counter access ON and standby open.
- Else 50% or more: open the standby counter.
- Else 45% or more: send an early alert to staff.
- Below 40%: close standby and cross access.
- Choose the best counter and update the student screen.
- Wait 1–2 minutes and repeat.
START LOOP every 1-2 minutes: FOR each counter: crowd_pct = queue / capacity * 100 wait_min = queue * avg_serve_sec / 60 ENDFOR zone_avg = average crowd_pct of national counters IF zone_avg > 80 THEN cross_access = ON ; standby_open = ON ELSE IF zone_avg >= 50 THEN standby_open = ON ELSE IF zone_avg >= 45 THEN SEND alert "Prepare standby in 2 min" ELSE IF zone_avg < 40 THEN cross_access = OFF ; standby_open = OFF ENDIF best = open + allowed counter with lowest wait SHOW "Go to " + best.name ENDLOOP END
flowchart TD
A[Start: read queue count of each counter] --> B[Calculate crowd % and wait time per counter]
B --> C[Calculate national zone average]
C --> D{Zone crowd > 80%?}
D -- Yes --> E[Turn ON cross-counter access and open standby]
D -- No --> F{Zone crowd >= 50%?}
F -- Yes --> G[Open standby counter]
F -- No --> H{Zone crowd >= 45%?}
H -- Yes --> I[Alert staff: 2-minute notice]
H -- No --> J{Zone crowd < 40%?}
J -- Yes --> K[Close standby and cross access]
J -- No --> L[Keep current state]
E --> M[Pick best counter by lowest wait]
G --> M
I --> M
K --> M
L --> M
M --> N[Update student screens]
N --> O[Wait 1-2 minutes]
O --> A
05 · Computational thinking
The four pillars
DECOMPOSITION
Split the problem into measuring queues, checking thresholds, opening counters, directing students, and notifying staff.
PATTERN RECOGNITION
National counters fill up at lunch while international ones stay free. The rush peaks at lunch time.
ABSTRACTION
Track only queue count, capacity, and serving time. Ignore what food each student picks.
ALGORITHMIC THINKING
Fixed IF/ELSE rules (45/50/80/40), repeated on a timer.
06 · Feedback
Built from your feedback
| FEEDBACK FROM SURVEY | FEATURE IN THE NEW DESIGN |
|---|---|
| Students didn't know which line to join | "Go to Counter X" recommendation and big signs |
| Staff need advance alert | 45% early alert with a 2-minute notice |
| Students missed seeing screens | Floor arrows, plus the phone view via QR code |
| Extra counters helped at 50% | Kept the 50% standby rule |
| Cross-counter access saved time | Kept the 80% rule |
FUTURE SCOPE
- Camera-based people counting
- Student QR check-in / check-out
- Daily and weekly rush-hour reports
- Rush prediction from past data
- Pre-order so food is ready
- Hindi and English options
SUCCESS MEASURES
- Lower average waiting time (before vs after)
- Students find the message clear
- Standby opened within 2 minutes
- Smaller gap between busiest and emptiest counter
07 · Team 3
Team Decrypted
IPS: Computational Thinking as an Engineering Mindset · Section SE-302A · Faculty: Dr. Sujithra · Venue: Canteen Mess, Jain (Deemed-to-be University)
Aditya Kumar LEAD
logic.js and Firebase
Ojash Kumar Gupta
Rules, tests, pseudocode, flowchart
Charvi Krithika
Student view
Kirtee Jain
Staff view and presentation
Aman Singh
Canteen test, serving-time measurement
Senthil Kumar S
Student feedback round 2
Thulasi Prasadr
Report, screenshots, evidence