Outcome - sedioben/IoTproject GitHub Wiki

By using IoT technology to suggest meals to our customers automatically and to implement an automatic authentication method for the food deliverer, we expect the following improvement potential for Come'N'Eat, its customers and the food deliverer.

1. Identification of potential for improvement in time arrangement:

Through Come'N'Eat the customer doesn't have to waste a thought on what he or she is going to cook in the evening after work. The app takes that sorrow and allows the customer to have more quality time with family and friends or other stuff, which is essential to our client. Come'N'Eat takes care of the meals of our customer, so that one doesn't have to do the following tasks:

• Select the meal
• Shop the groceries
• Cook the meal
• Cleaning the kitchen afterward

2. Increase in quality of food and nutrition:

After our customers ate their meal, they will have the opportunity to rate the meal they just had. With this review, a ranking is created. The rating will be divided into reviewing the meal and reviewing the food deliverer. Through analysis of the rankings and results, we can answer the following questions:

• Which food is the most popular and highest rated food?
• Which food is often bought but poorly rated? This could be an indication that it is a popular food, but the recipe should be revised.
• Which food is rarely bought and is poorly rated? This food could be taken off the menu, for example.

With these answers, we would be able to increase the food quality provided to the customer.

3. Better order fulfillment for food delivery service:

Because the deliverer gets automatic access to the home of the customer (only after successful authentication), he can fulfill all his tasks without the client. The deliverer can process all his tasks and doesn't have to wait for the customer. Situations like waiting for the customer to get the money out and pay the food or the customer to open the door/ come to the door and get the food are going to belong to the past with our NFC authentication solution.

Identified Issues

1. Smart home setup is a requirement

If we take a closer look at the Come'N'Eat service, we find that we need several Smart Home or IoT devices for the desired replicator effect. The exploration phase already shows which devices we used. Consequently, every household should have a Voice Assistant like Amazon Alexa and a Smart Lock like Nuki. Setting up the individual IoT devices might be too overstraining for some customers. Furthermore, a Smart Lock cannot directly be installed in an apartment building, which is a prerequisite for our service.

2. Amazon Alexa acts not proactive

In the Ideation phase, we have designed the deliverer's entry into the house in such a way that when the Smart Lock is opened, Amazon Alexa is immediately triggered, and Alexa greets the supplier and navigates him or her accordingly. Currently, this is not possible in Germany. The Alexa Voice Assistant is not allowed to be triggered by another system. This means that Alexa cannot act proactively. For this problem, the deliverer has to say, "Alexa, I am the deliverer." which acts as a media break.

3. Smart lock needs an additional bridge

For a Smart Lock to be opened by a mobile phone, it is connected via Bluetooth. For our scenario, especially for the authentication of the supplier, the Smart Lock must be opened securely via the Internet. In the period of the exploration phase, it became apparent that the Nuki Standard Lock is not sufficient, as it only offers an ad-hoc connection via Bluetooth. For this reason, the Nuki Bridge has to be purchased to ensure a smooth authentication of the deliverer. For more information on how to set it up, click here.