Goals
To transport open protocol data securely using encryption across an enterprise network or even over the Internet.
Supported Sources
- Allen Bradley: ControlLogix, CompactLogix, GuardLogix, Micro800, MicroLogix, SLC 500, and PLC-5
- Siemens: S7-200, S7-300, S7-400, S7-1200, and S7-1500
- Modbus: Modbus TCP, Modbus RTU, and Modbus ASCII
- MTConnect
- OPC DA / OPC UA
- OPTO
- MQTT
- Azure IoT Hub
- Amazon AWS IoT Gateway
- Databases: SQL Server, Oracle, MS Access, mySQL, PostgreSQL, Cassandra, MariaDB, SQLite, InfluxDB, MongoDB
- Microsoft Excel
- Custom Applications: .NET, or any other environment that can send JSON over HTTP to our REST API
- Proprietary Data Sources or Protocols: supported with our Universal Driver Interface (UDI)
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:
OAS Universal Data Connector- Data Historian
- Allen Bradley Connector
- Siemens Connector
- Modbus Connector
- OPTO Connector
- OPC UA Connector
- OPC Client Connector
- Data Route
- OAS Recipe
- Excel Connector Connector
- Azure IoT Data Hub Connector
- AWS IoT Gateway Connector
- MQTT Connector
- .NET Data Connector
- REST API
Solution Description
Open Automation Software transports data from server to server and server to client with encrypted and compressed packets. This eliminates the threat of data being spoofed or intercepted and protects corporate intellectual property. OAS is commonly used to communicate to SCADA systems with open protocols to transfer to business applications. It can also be used for custom and proprietary data as well using the .NET or REST API.
The OAS Data Route feature provides end to end transport with no programming required with simple to define mapping of source to destination. The OAS Calculation engine can be used to combine values at the source into a JSON packet or other result ready for secure transport. Communications is bi-directional or can optionally be set to one way only for each individual tag or an entire server. Data protection is not just limited to industrial data, some OAS users have even implemented the OAS Excel connector to transport IP data between Excel Workbooks through the Internet.
OAS performs end to end encoding and decoding quickly and efficiently often reducing the packet size of open protocols like OPC UA and MQTT by more than a factor of 10. Multiple OAS engines can be used automate data transport securely between control networks and database engines. All engines are deployed as an edge solution to pre-process data at the data source, eliminating the need for a cloud hosted solution.
Setup
OAS data transport can be setup using one of the following methods.
- Manual mapping of source to destination.
- CSV import of tag mapping.
- Programmatic setup via .NET or REST API.
- Automated setup.
Deployment
OAS can be deployed to Windows or Linux with the following configurations.
- On-premise or closed network
- DMZ or public-facing subnet
- Secure cloud-hosted OAS
- One-way communications diodes
- Multi-tenant deployment
