Connectivity Endpoint and Data Formats
SMARTUNIFIER provides comprehensive connectivity support for a variety of equipment, devices and IT systems. This includes many different preconfigured communication protocols and formats e.g., OPC-UA, file-based, database, message bus, Webservices and direct PLC connections. Preconfigured interfaces are available also for many standard software applications. A number of these connectivity endpoints / communication protocols require a first time customization from Amorph Systems for a specific customer connectivity use case. Please contact Amorph Systems for detailed information.
The following connectivity endpoints / communication protocols are supported by SMARTUNIFIER:
Format | Decription |
---|---|
ADLink OpenSplice | Connectivity to ADLink OpenSplice middleware via Data Distribution Service (DDS) |
AMQP | Interface to AMQP Message Broker via Active MQ |
AODB | Interface to various Airport Operational Database (AODB) Systems that support standard communications via e.g., HTTP, REST, SQL |
Apache Active MQ | Interface to Active MQ Message Broker |
AWS Elastic Container Service (ECS) | Interface to applications running in AWS ECS |
AWS Elastic Compute Cloud (EC2) | Interface to applications running in AWS EC2 |
AWS IoT | Interface to AWS IoT |
AWS IoT Greengrass | Interface to AWS IoT Greengrass via MQTT |
AWS IoT Sitewise | Direct interface to AWS IoT SiteWise or via OPC-UA |
AWS CloudWatch | Interface to CloudWatch |
AWS DynamoDB | Interface to AWS DynamoDB |
AWS S3 | Interface to AWS S3 |
AWS SNS | Interface to AWS Simple Notification Service (SNS) |
AWS SES | Interface to AWS Simple Email Service (SES) |
Barcode Reader | Connectivity to any TCP/IP-based barcode reader (or other identification systems) |
Beckhoff | Interface to Beckhoff PLC via Beckhoff OPC-UA Server |
CNC | Connectivity to various CNC controllers (e.g., ABB, Fanuc, Heidenhain, Heller, Sinumerik, Traub, W&T Wiesemann & Theis) |
DDS | Connectivity to Data Distribution Service (DDS) |
File | Read and write files from any directories (read: File Reader / File Tailer, write: File Writer) |
FIWARE | Interface to FIWARE IoT |
Flink | Interface to Apache Flink to enable real-time streaming |
FTP | Upload and Download files to/from FTP servers |
HTTP | Send request to HTTP servers |
HTTPS | Send request to HTTPS servers |
InfluxDB | Interface to InfluxDB |
InfluxDB v2.0 | Interface to InfluxDB v2.0 |
IBM MQ | Interface to IBM MQ Message Broker |
In-Memory | Communication via local machine |
ISO-on-TCP | (RFC1006) Connectivity of S7 automation devices with any communication partner |
JDBC | Access databases through SQL and JDBC (refer to SQL Databases) |
JMS | Send and receive messages to/from a JMS Queue or Topic using plain JMS |
Kafka | Interface to Apache Kafka to enable real-time streaming |
MES | Interface to a Manufacturing Execution System (MES) that support standard communications via e.g., HTTP, REST, SQL |
Mendix (REST) | Interface to Mendix via REST |
Mendix (MQTT) | Interface to Mendix via MQTT |
Mendix (Kafka) | Interface to Mendix via Kafka |
Modbus-TCP | Communication via Modbus TCP Server / TCP Client |
Microsoft Azure (IoT Hub) | Interface to Microsoft Azure Iot Hub via MQTT |
MTConnect | Communication Interface to MTConnect compliant agent applications |
MQTT | Connectivity by implementing MQTT Client |
NoSQL Databases | Cassandra, MongoDB, Hbase |
OEE | Interface to various Overall Equipment Efficiency (OEE) Applications that support standard communications via e.g., HTTP, REST, SQL |
OPC-UA Client | Connectivity by deploying one or multiple OPC-UA Client instances per SmartUnifier Communication Instances |
OPC-UA Server | Connectivity by deploying one or multiple OPC-UA Server instances per SmartUnifier Communication Instances |
PLC | Connectivity to various PLCs (e.g. Allen-Bradley, B&R, FANUC, General Electric (GE), Hilscher, Honeywell, Krauss Maffei, Mitsubishi, Toshiba, Wago) via TCP/IP |
PM | Interface to a various Predictive Maintenance Systems that support standard communications via e.g., HTTP, REST, SQL |
POP/IMAP | Receiving emails from a mail server |
REST | Communication via REST using REST Server / REST Client (Webservices) |
SAP MII | Interface to SAP MII |
SAP RFC | Interface to SAP via remote function call (RFC) |
SAP Netweaver | Interface to SAP Netweaver via HTTP |
SCADA | Interface to various SCADA Systems that support standard communications via e.g., HTTP, REST, SQL |
SECS/GEM | Communication with semiconductor or photovoltaic equipment using SECS/GEM interface protocol for equipment-to-host data communications (TCP/IP) |
Siemens Industrial Edge | Deployment of SmartUnifier Communication Instances via Siemens Industrial Edge Platform |
Siemens MindSphere (REST) | Interface to MindSphere via REST |
Siemens MindSphere (MQTT) | Interface to MindSphere via MQTT |
Siemens S7 PLC/TCP | Interface to Siemens S7 1500 / 1200 / 400 / 300 via TCP protocol |
Siemens S7 PLC/OPC-UA | Interface to Siemens S7 1500 / 1200 via OPC-UA protocol |
Smart Devices | Interface to various Smart Devices (e.g., Smart Phones, Tablets) that support standard communications via e.g., HTTP, REST, SQL |
SMTP | Sending emails from SMTP servers |
SOAP | Communication via SOAP (Webservices) |
Splunk | Interface to Splunk via HTTP Event Collector |
Splunk | Interface to Splunk via Metrics Interface |
SQL Databases | Interface to any SQL-based database like e.g., DB2, HSQLDB, MariaDB, MSSQL, OracleDB, PostgreSQL, SQLServer and others |
SFTP | Upload and Download files to/from SFTP servers |
TCP | Communication from/to any (binary) TCP based protocol |
UDP | Communication from/to any (binary) UDP based protocol |
VANTIQ | Interface to VANTIQ |
VIPA Speed 7 | Interface to VIPA Speed 7 PLC |
WAGO PLC/IP | Connectivity to WAGO PLCs via OPC-UA |
Websocket | Interface to Websocket Server (TCP/IP) |
Note: In case a customer requires to connect to other endpoints (e.g., computing devices, PLCs) not listed in the table, please contact Amorph Systems.
Data Formats
The following data formats can be used in conjunction with the above defined connectivity endpoints. The possible formats for a certain connectivity endpoint may be restricted based on the selected communication protocol. For detailed information please contact Amorph Systems.
Format | Description |
---|---|
Binary | Handling of any binary communication format (e.g., fixed/variable lengths fields, headers/footers) |
CSV | Handle CSV (Comma separated values) payloads |
JSON | Encode and decode JSON formats |
TEXT | Handling of any text-based communication format |
XML | Encode and decode XML formats |
Note: In case a customer requires another data format not listed in the table, please contact
Amorph Systems.