Dashboards to wrangle IoT data coming through gateways

As the internet of things (IoT) grows exponentially, so do the technologies that help manage the communication across internet networks. One such tool is a gateway. Gateways help manage the information coming from an object, across the internet, to a closed network where that object is controlled, and through which the object sends data. For instance, a security camera sends still images and video information, but it also communicates its position, its status, if it needs repairs, and so on. With the potential for any system to have hundreds or thousands of connected objects, the amount of data coming through can be quickly overwhelming.

We were asked to design a dashboard to organize the data so that it was easier to contextualize and visualize. This challenge gave us the opportunity to dig into the technical operations, examining the data to understand what was there and where it needed to go. After understanding the data, the design process could begin: foundational wireframing, visual designs, and a style guide.

After these tools were established, it was easy to plug in the components that would serve the needs of both the business and the user and help wrangle the data. We worked closely with the team to get the information hierarchy correct, establishing first, second, and third level information.

We focused design solutions around the reporting, scheduling, and alert functions. Reports consisted of all the data coming through the gateway, and could pertain to the hardware, software, or the IoT device itself. With so much data throughput, it needed to be scaled and edited for easier viewing. To help control the data, we designed a functionality for creating a report based on attribute choices and a date range. Regular reports could then be scheduled using a scheduling tool, and alerts could be set for when the reports were ready.

This made the data the most useful, and so the user wasn’t overwhelmed by the volume of information. The scheduling of the reports and the alerts made it so the user didn’t have to re-create the reports, or remember to pull them: they were already waiting for them. This helped save time, and enabled quicker decisions.

With the fast pace and continuous movement of the project, the style guide was a valuable asset. It outlined the design attributes so that when future modifications are made to any screen in the design, the same guidelines could be followed for continuity.


This project took vast amounts of constantly flowing new data and helped arrange it so that it was available in usable sections. It provided a snapshot of time in order to make informed decisions about how to improve and care for the objects in the system.

How can we help solve your problem?