1. Web EnabledPatron Queuing System Professor Weibo Gong Raj Wadwal Subash Unni Vinh Pham John Danaher

2. Introduction • Background • Development Approach • Principle of Operation • Design Constraints • Sensor Configurations • Determining Success • Deliverables MDR • Conclusion

3. Background • Why a Web Enabled PQS? • Patron • find long lines • wastes time • no fun • Customer • presented with bursty patron traffic • slow service time • patron may bypass establishment

4. Background • Broad Solution • Detect Congestion locally • Inform Potential Patrons via Customer website • Patron adjusts schedule • Life is better

5. Development Approach • Multi-Phase Design Approach • Phase I – Show Efficacy • Implement and Install a PQS • Advertise System to Public • Measure Performance • Refine Sensor Arrangement

6. Development Approach • Multi-Phase Design Approach • Phase II – Improve System • Design lower cost sensors • Scale micro-controller • Minimize sensor number • Wireless

7. Principle of Operation • Detect Events • Compare to Congestion Threshold • Determine Congestion Level • Conveys Conclusion via WIFI • Patron visits web page

8. Principle of Operation

9. Design Constraints • Human Nature • Strict Queue • Unfeasible • Lumped Queue • Requires Smart Controller • Non-Interfering Web interface

10. Design Constraints • Strict Queue - Unfeasible • Conspicuous • May conflict with existing lobby configuration • Human Nature • Use exit for entrance • Sensor Interference

11. Sensor Configurations Strict Queue with Entrance Trigger with time out

12. Sensor Configurations Strict Queue with Entrance and Exit Counting

13. Sensor Configurations • Lumped Queue • Volume Detection • Patrons and non-Patrons mixed • Multiple Detection Points/ Areas • Live Image Capture • Low Resolution for privacy

14. Sensor Configurations Lumped Queue with Volume Estimation

15. Sensor Configurations Lumped Queue with Volume Estimation

16. Design Constraints • Web Interface • Seamless non-interfering • Security

17. Determining Success • Installed and Functioning PQS • PQS function must correspond to observed data • Patron Feedback • Customer Feedback • Reasonable Cost

18. Deliverables for MDR • One (1) implementation of a PQS • Ready for Test Installation • Controller • Sensors • Server Side Software

19. Conclusion • Technology Useful Daily • Human nature impacts solution • Thoughtful Engineering • Reduces Costs • Improves System Predictability