To publish all data reliably to AWS IoT Gateway and retain data on failure of communications to cloud server. Transfer all data collected from Industry 4.0 systems with precise accuracy with no data loss on network failure.
Supported Data Sources
- SLC 500
AWS IoT Gateway
AWS IoT Gateway
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 AWS IoT Gateway interface has an easy to use store and forward feature built in to preserve data on communication failure when the AWS IoT Gateway is unavailable. In the driver configuration set the Enable Store and Forward property to true and define the Store and Forward path in OAS Options to determine where the retained data will be temporarily stored.
During communications failure to AWS IoT Gateway all data is retained until the service to AWS IoT Gateway is restored when all buffered data will be published in the order it was archived.
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 publish the result to AWS IoT Gateway.
Utilize One Click Allen Bradley, One Click OPC, or One Click OPC UA to automatically setup the transfer of data directly to AWS IoT Gateway. 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.