he big picture behind our IoT use case has existed for some time and is also valid for many other IoT applications. So we do not want to deprive you of it and describe it briefly.
Architecture of generic IoT use cases
The following diagram shows the local architecture of a generic IoT use case. In principle, the information runs from left to right. Individual devices (sensors, output devices, …) supply data to the central message broker. You can also receive events from the broker. For example, a socket or an LED could be controlled by an event from the control.
At the broker, different consumers log on to save the data, visualize it, and generate additional events based on rules (eg, if a threshold is exceeded). Since the information from the regulation return to the broker, these can also be taken into account during the visualization.
With this setup you can control and evaluate a machine or even a whole site quite well. In order to really benefit from „Big Data”, selected data should be loaded anonymously into the cloud.
Via a „cloud gateway” selected data are first anonymized and then loaded into the Azure Cloud. The data can be evaluated by the customer and the customer. The so-called „big picture” allows optimization potentials to be identified and passed on to customers and locations.
In principle, this architecture can be applied to many applications. For example, the data of leased machines could be recorded and analyzed anonymously in order to optimize maintenance processes or production itself. Customers or locations that share their data for analysis purposes also profit from the collected data of the others.