The goal of the system is to help clear tables at eating establishments more quickly and easily. This improves efficiency for the customers and the business.
The system will sense the presence of customers using weight sensors in the seats and temporary objects at the table using computer vision with cameras above the tables.
The system will move between tables and its home location without running into customers.
The system will determine whether a table needs to be cleared based on the sensing of temporary objects on the table. The system will also recognize the presence of actors within the system.
The system will notify waiters when the table is ready to be cleared. It will have a way of receiving customer and waiter requests to serve a particular table or return to its default location.
| Functional Area | Decription |
|---|---|
| 1 – SNS | Sensing of sitting clientele and waste on table |
| 2 – BIN | Bin’s movement and local sensing |
| 3 – CNTL | Interface for bin control by incoming clientele and local staff |
| 4 – NOTIF | Notifications sent from system to users |
| Word | Meaning |
|---|---|
| Bin | moving bin that can be deployed to a table |
| Table | each individual table available to the incoming clientele |
| Table sensors | groups of sensors that are going to collect data about the presence of customers at the table and the presence of objects on the table |
| Interface | application that allows control of the bin |
| System | medium that connects together the interface |
| Default spot | the bin’s default location when it has not been deployed to a table |
| Cleaning session | time period in which either the sitting clientele or the local staff is actively making use of the bin |
| FR | Title | Description | Priority |
|---|---|---|---|
| 1.1 | Customer Sensing | The table sensors will detect the sitting clientele as it abandons the table, leaving all the chairs empty | 1.1 |
| 1.2 | Object Sensing | The table sensors will detect the presence of objects on the table, as opposed to an empty table | 1.1 |
| 1.3 | Object Distinction | System will be able to distinguish between movable objects that belong on the table and foreign objects that must be removed | 1.3 |
| 2.1 | Bin Deployment | The system will trigger the bin deployment to a specified table | 1.1 |
| 2.2 | Bin Return | Upon end of a cleaning session, the bin will return to its default spot | 5.4 |
| 3.1 | Client table selection | The incoming clientele will select a table and commit to clean it (if any object was detected on it) before occupying it | 1.1 |
| 3.2 | Staff table selection | The local staff will select a table (marked as free, objects detected on it) to clean | 1.1 |
| 3.3 | Default spot selection | The local staff will be able to set up a default spot for each bin connected to the system | 5.3 |
| 3.4 | Cleaning session end | The local staff and the sitting clientele will be able to signal the end of a cleaning session to the bin | 4.4 |
| 3.5 | Show table status | System will show the status of each table to staff or clientele | 1.1 |
| 4.1 | Cleaning required | The system will send a notification to the interface whenever a table is detected to have objects on it | 2.3 |
| 4.2 | Table cleaned | The system will send a notification to the interface whenever a table has been cleaned | 5.4 |
| 4.3 | Table taken | The system will send a notification to the interface whenever a table has been taken | 4.4 |
| NFR | Description | Area |
|---|---|---|
| 1 | The interface will provide a list of the tables | Portability |
| 2 | The interface will be tablet only | Portability |
| 3 | The interface will support Android OS from version 5.0(Lollipop) up | Standards |
| 4 | The system should be able to operate within an already existing local network | Interoperability |
| 5 | The system should be able to manage multiple bins | Usability |
| 6 | The interface will allow only for the reservation of tables that are marked not cleaned | not taken |