1. Project May07-14: Restaurant Automation April 24, 2007

2. Project Team Information Client – Senior Design Team: – Chris Ford – Sean McVeigh (Project Manager) – Obioma Ohia – Nichole Taylor – Anthony VanSant Advisor: – Dr. Manimaran

3. Agenda Problem Objective Requirements Assumptions and Limitations Design Testing Resources and Schedule Closure Material Summary

4. Project Objective To prove that it is possible to increase the efficiency and customer service in a restaurant. Central Computer Handheld Kitchen Display Database

5. Acknowledgement Academic Advisor – Dr. Manimaran Electrical and Computer Engineering Department

6. Definitions eBox – Emulates a handheld device MySQL – Database software Windows CE – Operating system used on handheld devices

7. Intended Users/Uses Users – Servers – Cooks – Managers – Customers Uses – To take orders – Order payment – Ability for cook to view orders – Ability to create and modify menus

8. Assumptions and Limitations Assumptions – Central Computer would have a static IP address – Inputs into the system would be valid – No security threats Limitations – The lack of programming skills of the group – The cost of the items for the project

9. Expected Final Product Handheld ordering software – Ordering – Complete transactions Central computer software – Main communications Database – Holds the menu, orders and transactions Database software – Menu creation and edit Kitchen Display – Displays orders

10. Operating Environment Used and stored in an indoor, dry environment – Operating Temperature ~50 °F - 80 °F Courtesy of http://www.seattle-city.com/earth-ocean-restaurant.php

11. Design Objectives Develop a database – Use MySQL Develop kitchen software Develop a central computer server Develop handheld software

12. Design Constraints Handheld – User interface – Communications Central computer server – User interfaces – Minimal wireless communications Kitchen – User interface – Communications

13. Central Computer - Software Central hub of communications – Redirects traffic – Updates database – Notifies either kitchen or handheld of current orders

14. Central Computer - Software

16. Handheld - Software Inputs – Order number – Seat number – Menu item – Order done – Payment type – Payment amount Outputs – Order matrix Steps for taking an order

17. Handheld - Software Startup/update function Create order function Edit order function Payment function

18. Handheld - Communication Handheld to central computer server Credit card reader to handheld Handheld to printer Handheld Central Computer Credit Card Reader Printer

19. Handheld - Hardware ICOP Technology eBox-II USB Wireless card Credit card reader Bluetooth printing

20. Kitchen - Software Java Application – Receives orders from central computer and displays them on kitchen display. Communication – User-confirmation of completed order sends message to Central Computer with order number and IP address of handheld from which order came.

21. Kitchen - Software

22. Database - Software MySQL database with GUI – Purpose Used to keep track of order history and inventory – GUI Ability to modify and add menu items

23. Database - Software

24. Pictures of Whole System Server Handheld Manager Software Kitchen Display

25. Testing Communication – Verify packets sent and received – Verify packets processed properly Software/GUI – Verify software interacted properly with user input

26. Actual Personal Hours Task 1 – Problem Definition Task 2 – Technology Considerations and Selections Task 3 – End Product Design Task 4 – End Product Prototype Implementation Task 5 – End-Product Testing Task 6 – End-Product Documentation Task 7 – End-Product Demonstration Task 8 – Project Reporting

27. Actual Financial Requirement

28. Schedule of Work

29. Closure Material Project Evaluation Commercialization / Additional Work Lessons Learned Risk Management

30. Project Evaluation MilestonesRelative ImportanceEvaluation ScoreResultant Score Task 1: Problem definition15%100%15% Task 2: Technology considerations and selection5%100%5% Task 3: End-product design10%100%10% Task 4: Prototype implementation20%75%15% Task 5: End-product testing15%95%14.25% Task 6: End-product documentation10%100%10% Task 7: Project demonstration10%55%5.5% Task 8: Project reporting15%100%15% Total100%89.75% Previously defined passing score = 80%

31. Project Evaluation (cont.) Handheld Software ComponentsStatus Taking orderFully Met Payment functionFully Met Editing an orderFully Met CommunicatingPartially Met Kitchen Software ComponentsStatus Receive orderFully Met Order completion communicationFully Met Display ordersFully Met CommunicatingFully Met Get orders when starting upExceeded Expectations Manager SoftwareStatus Create menuFully Met Edit menuFully Met DatabaseStatus Create database to hold orders, menus, and transactions Fully Met Central Computer SoftwareStatus Send menusFully Met Forward order to kitchenFully Met Forward order to databaseFully Met Forward order completion to database Fully Met Forward order completion to handheld Fully Met Send current orders to handheldFully Met Send current orders to kitchenFully Met Forward transaction completion to database Fully Met

32. Project Evaluation (cont.) System DemonstrationStatus Independent software workingFully Met Basic system demoFully Met Kitchen to central server functionFully Met Handheld to central server functionPartially Met Central Server to database functionFully Met Manager software functionFully Met Whole system integrationPartially Met

33. Commercialization / Additional Work Commercialization – Proof of concept so this was not explored Recommendation for Additional Work – Increase the functionality of the manager software – Add error checking to the central computer software – Add security to the communications – Port the handheld software to a handheld device – Develop a handheld device that would incorporate everything required for the handheld

34. Lessons Learned What went well: – Central computer and Kitchen display interaction work – Individual programs work separately – Central server works What did not go well: – Integration of GUIs – Communications integrations Knowledge gained: – Java network programming – Database building – Java-MySQL interaction programming What would we change: – Start programming in November – Start with GUI program instead of text based – Program for eBox right away

35. Risk and Risk Management Anticipated risk: – Difficulties with programming languages Unanticipated encountered risk: – Course work was higher than expected Resultant changes for unanticipated risk: – Changing of the project definition

36. Summary To prove that it is possible to increase the efficiency and customer service in a restaurant. Handheld device – place orders – receive payments – print receipts Database – Holds the menus and transactions Kitchen – Shows the current orders Central Computer – Redirects traffic and updates the database

37. Questions ?