1. COMP 410 Update

2. The Problems Story Time! Describe the Hurricane Problem Do this with pictures, lots of people, a hurricane, trucks, medicine all disconnected. We come in and connect (add in arrows) Now that we’re connected we can move resources to the right place Afterwards we have data to analyze and improve our resource management Use Emergency Response System slide to understand how to do this

6. But Connecting is Only One Piece… How do you interpret massive amounts of data? Where do you store this data? How do you transmit this data? Where do you analyze this data so you can understand it? What happens when a device disconnects intentionally or unintentionally? How does another device access and use this data? How can we make our solution extensible?

7. The Core Issues  High volume of data  It’s infeasible to have every sensor send every reading to every decision agent  Solution: Intermediate nodes to aggregate, analyze, and summarize sensor information  Disconnections  Our theoretical real-time always-connected data pipeline isn’t realistic  If devices disconnect, intentionally or unintentionally, information can be lost  Solution: Intermediate nodes store the information they receive, so they can re-emit it later  Different kinds of devices  Third-party sensors and actuators often speak different languages  Solution: An extensible framework that can use any communication protocol

8. High-Level Framework Design Framework Application Layer, a.k.a. Business Logic Network ProtocolStorage Protocol Disconnection Protocol

9. If historical data is too big to store locally, store it in the cloud. Solving: High Volume of Data Framework Application Layer, a.k.a. Business Logic Network ProtocolStorage Protocol Disconnection Protocol An intermediate node receives sensor data, analyzes it in the business logic, and sends a summary to decision agents.

10. We can use historical data to automatically send messages once a device (re)connects. Solving: Disconnections Framework Application Layer, a.k.a. Business Logic Network ProtocolStorage Protocol Disconnection Protocol On disconnection, we can notify a monitoring service, and attempt to reconnect if necessary.

11. Solving: Different Kinds of Devices Framework Application Layer, a.k.a. Business Logic Network ProtocolStorage Protocol Disconnection Protocol We’ll provide standard internet connections, but anything can plug in here.

12. How our Framework Solves these Problems How do you interpret massive amounts of data? It’s distributed through intermediate nodes that scale data down to manageable sizes Nodes are not defined by their hardware, so you can build them on something like Azure Where do you store this data? Databases, THE CLOUD, local cache, basically anywhere. Y’all want a cloud. Fluffy. Nodes are also not defined by their storage types How do you transmit this data? Any network protocol that you plug into the framework How do you make sure the data arrives at the right location? We don’t. But it’s not important because data storage let’s you ask for backups if you drop connection Where do you analyze this data so you can understand it? Intermediate nodes aggregate the data to smaller sizes, analysis nodes run analyses. What happens when a device disconnects intentionally or unintentionally? Nodes will try to reconnect if unintentional. Any data that is to be transferred will be temporarily stored. How does another device access and use this data? May access data from cloud. May receive data directly from other nodes in the network.

13. Emergency Response System There’s a hurricane People need water, food, and medicine The city has shelters that people are going to for relief How does the city use its food banks, hospitals, and relief trucks to distribute resources to those shelters? We connect these resources so that truck drivers know where to send food, food banks know when they will receive more inventory, and city leadership knows the status of these systems at all times Finally the city is back on its feet and city managers want to look back at how decisions were made to modify emergency response protocols for future disasters. First we solved the immediate problem then learned from those decisions to help us in the future

14. Timeline

15. Prototype 0 3/13

16. Prototype 0

17. 1) Can connect devices with different protocols ◦Fundamental to the project so that data can eventually be transferred 2) Can transfer and interpret data sent between devices ◦Can handle intermittent, predictable disconnection ◦Can store data in local storage and using cloud services

18. Prototype 0 Technologies Wunder Bar Demonstrates real time data access through a cloud service Demonstrates unreliable connections Kinect Demonstrates direct, reliable connection Intermittent data sending Laptops (2x) Demonstrate wireless connection Holds business logic Demonstrates local storage being pushed to a database intermittently

19. Prototype 1 3/27

21. Prototype 1

22. 1) Heavy focus on data storage, analysis, and interaction with cloud services ◦Now that devices are connected, we want to make sure we can use the data effectively 2) Added storage options more applicable to big data problems ◦Demonstrating the extensibility of the Framework

23. Prototype 1 Technologies Windows Azure ◦SQL database for storage ◦Virtual machines for computation ◦Machine learning for analysis Hadoop ◦Demonstrates large scale data aggregation

24. Prototype 2 4/10

27. Prototype 2 1) UX and UI added related to the Hurricane Story ◦Now that data can be sent and stored, implementing the business logic to solve a real problem ◦Human interaction with the data to make decisions

28. Prototype 2 Technologies Web Applications ◦Provide interfaces for users to interact with data ◦Display data in human readable format Mobile Devices ◦Add new networking technology to the system ◦Demonstrates extensibility of the design

29. Final Project 4/24

32. Final Prototype Full integration of all technologies ◦All protocols are in place so that devices can communicate through the Framework Complete solution for the hurricane problem ◦UX/UI refined for human interaction Increased Scale from Prototype 2 ◦Demonstrates ability of our Framework to tackle large scale data problems

33. Final Prototype Technologies External Weather Database ◦For pulling big data for simulation ◦Demonstrates full power of data handling technologies

34. Questions?