To maintain 100% accuracy and delivery of data to Azure IoT Data Hub during network failures or service outages. To deliver all values, not just the latest value to Azure IoT Data Hub from Industry 4.0 data sources.
Supported Data Sources
- SLC 500
AWS IoT Gateway
Azure IoT Data Hub
OAS Components Used
This example Use Case utilizes the following OAS Platform Components and can be deployed in many different configurations to achieve the best performance and reliability:
The OAS Azure IoT driver interface has an optional store and forward feature to retain data to disk on network failure when the Azure IoT Hub is unreachable. In the Azure IoT driver configuration set the Enable Store and Forward property to true and set the Store and Forward path in OAS Options.
Data can be buffered to disk for any amount of time until the network can be restored, at which time all data is published in the order it was received. Once all buffered data is delivered successfully live data publishing resumes.
Data Route Features
Data Transfer Types:
- Continuous: Transfer data every time the Tag Value changes.
- Dead-band: Transfer data when the tag change exceed the preset dead-band.
- Specified Rate: Transfer data a a specified rated regardless of value change.
Built in Calculation Engine:
Use the OAS calculation engine to perform complex calculations on multiple items and transfer the result to Azure IoT Hub.
Utilize One Click Allen Bradley, One Click OPC, or One Click OPC UA to automatically setup the transfer of data directly to Azure IoT. Or utilize programmatic setup of Tags and Data Route with a .NET application or REST API. CSV export and import is also a fast way to setup all data transfer quickly.
Multi Platform Deployment:
Easy deployment and operation using Linux, Windows, Windows IoT Core, Raspberry Pi, and Docker.