Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SharePoint Saturday Warsaw 2018 21st-century lunchbell


Published on

A 21st-century lunch bell based on Azure, Cognitive Services and Office365.

Published in: Technology
  • My brother found Custom Writing Service ⇒ ⇐ and ordered a couple of works. Their customer service is outstanding, never left a query unanswered.
    Are you sure you want to  Yes  No
    Your message goes here
  • Hello! I can recommend a site that has helped me. It's called ⇒ ⇐ So make sure to check it out!
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

SharePoint Saturday Warsaw 2018 21st-century lunchbell

  1. 1. Thomas Gölles & Stephan Bisser
  2. 2. Sponsors & Partners
  3. 3. • Thomas Gölles • Microsoft MVP (O365) • SOLVION @thomyg Head of Modern Workplace Solutions Graz, Austria • Stephan Bisser • Microsoft MVP (AI) • SOLVION @cloudguy_pro #AskCloudguy Graz, Austria
  4. 4. Agenda 1 Background 2 “Bussiness Problem” 3 Tech geek out 4 Demo
  5. 5. Background
  6. 6. Our Office in Graz, Austria
  7. 7. This was Thomy‘s view before he switched rooms
  8. 8. Lunchtime at our office (around 10:45)
  9. 9. Yummy
  10. 10. This is Thomy‘s view after he switched rooms (now)
  11. 11. How can Thomy solve that problem?
  12. 12. Possible solutions • Create a recurrent event in Outlook • “Ping” a colleague everyday • Stand up and have a look • Use technology to solve the problem
  13. 13. As a geek you have to do something awesome
  14. 14. MOCADESYMO was born • Penny: Well, you know, it’s the Cheesecake Factory. People order cheesecake, and I bring it to them. • Leonard: So, you sort of act as a Carbohydrate Delivery System. • Penny: Yeah, call it whatever you want, I get minimum wage. Mobile Monitor
  15. 15. Who or what is MOCADESYMO?
  16. 16. Hi, I‘m MOCADESYMO – your 21st century lunchbell
  17. 17. MOCADESYMO‘s view
  18. 18. Architecture of the 21st century lunchbell
  19. 19. Raspberry Pi + camera module
  20. 20. Parts
  21. 21. Shell script
  22. 22. Azure components Blob Storage Azure Function Custom Vision API Storage Tables
  23. 23. 1. Raspberry PI camera takes photo of food truck, after it has arrived 2. Paspberry PI uploads the taken image into an Azure Blob Storage 3. Raspberry PI triggers an Azure Function after the image has been uploaded successfully 4. Azure Function calls the Custom Vision API in order to check wether the food truck is present or not 5. If Custom Vision API responds with a high probability that the truck has arrived, the Azure Function sends a notification to Teams 6. Users can ask the Lunchbell Bot in Teams wether the food truck has arrived or not or if it is still present 7. Azure Bot Service checks the entries in an Azure Table Storage where the arrival and departure time is stored
  24. 24. Bots & Cognitive Services
  25. 25. The future: Conversations • Natural language between people and technology • Conversational canvas • Bots and agents 2000s: Mobile • Social • User download apps from App Stores 1990s: Internet • Search • User “visits” websites 1980s: PC • Desktop The evolution of computers and IT
  26. 26. Bots 101 “a computer program designed to have a conversation with a human being, especially over the internet” * *
  27. 27. Bots 101 • It’s one thing: it’s an app that performs an automated task • It solves the user’s needs in the quickest/easiest way compared to any other option... like an app, or a website • What makes a bot great: • It is not how much AI it has • It is not how much natural language it offers • It is not whether it uses voice or not
  28. 28. Bots 101 { Your Code } REST Endpoint
  29. 29. Microsoft Bot Framework
  30. 30. Modelling your conversation Flexibility Effort to implement Dialogs FormFlow QnA Bespoke FAQs, command & control Data capture, “Web forms” scenarios Multi layered conversations Roll your own state management etc.
  31. 31. Conversational mechanisms • Text, with optional media attachments • Traditional chat, can contain media attachments (e.g., image, video, audio, file) • Input prompts • Suggested actions: Buttons, numbered items in a list, etc. • Rich cards, rendered as a list or carousel • Images, buttons, audio, animations, video, user sign-in, etc. • Hero | Audio | Animation | Thumbnail | Receipt | Sign In | Video | Adaptive | Purchase • Speech • Text-based chat using Speech Recognition & Synthesis (TTS)
  32. 32. Continuous Improvement • Instrumentation provided by App Insights; added by default in Bot Service • Extend instrumentation through AI SDK • If you are not building bots that will actually be used, then you are not building bots
  33. 33. Microsoft Cognitive Services
  34. 34. Custom Vision Service • Build a custom image classifier in 10 minutes or less • Diversity of images is key: angles, lighting, backgrounds • Not for object detection and is robust to subtle differences • Handles tuning model for edge cases (like misses)
  35. 35. Custom Vision Service Normal State98,53 % True100 % True99,9 % True
  36. 36. Building image classification using the Microsoft AI platform • BRK3334
  37. 37. Language Understanding [ $LunchBell.Object ] [ $LunchBell.Operation ] „Has the food truck arrived?“ „Has the food truck arrived?“ Intent = CheckArrivalState
  38. 38. Where does the lunchbell ring?
  39. 39. Microsoft Teams
  40. 40. SharePoint Online
  41. 41. DEMO
  42. 42. Demo Case
  43. 43. Thank you! #SPSWarsaw