Jørgen Berg

Solution Sales Engineer

Beckhoff Automation ApS
Edge Computing
 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

3
Edge device basic concept

Microsoft
Azure

IoT connectivity and Realtime Processing on Connectivity Firewall

edge analytics the Edge

Beckhoff
Edge Device

Azure IoT Edge, AWS ect… TwinCAT OPC

New Beckhoff Old Beckhoff 3rd party control

Machine Level

Controller with TC3 Controller with TC2

 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

5
Use case 'IoT connectivity and edge analytics'

 Beckhoff provides Azure and AWS

certified, industrial-proven edge hardware
 Support for Greenfield and Brownfield
Microsoft
application scenarios Azure

 Based on cloud provider edge runtimes Docker / Kata Container Docker / Kata Container

 Secure connectivity with cloud platforms

MQTT
 Typically running on Linux OS AWS Greengrass Azure IoT Edge

Docker / Kata Container Docker / Kata Container

Beckhoff Customer-specific application
Edge Device

Node-RED
MQTT and/or OPC-UA

Beckhoff 3rd party device

Controller
 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

7
Use case 'TwinCAT on the edge'

 Support for Greenfield and Brownfield application

scenarios
 Many use cases can be solved: Microsoft
Azure
 Edge analytics based on TwinCAT Analytics
 IoT connectivity based on TwinCAT IoT
Realtime HTML5 Machine DataBase
 OPC UA connectivity based on TwinCAT OPC UA MQTT
kernal HMI Learning Server

 Fieldbus connectivity
 and much more Beckhoff
Edge Device
I/O Cloud
Connectivity Analytics
Scope
Server
Driver

MQTT and/or OPC-UA

Beckhoff 3rd party device

Controller
 Edge computing for pre-processing

 Edge Computing
 Beckhoff provides ideal solutions for Edge Computing scenarios
 Use Case: Analytics, pre-processing

Aggregated analysis
Φ(Ψ 𝑓 (𝑥) ) "in the Cloud"
Aggregated analysis
"at the edge"
- Tx35xx Analytics
- TF3600 CM
- TE1400 Mat./Sim.
- ...

Local real-time analysis

- TF3510 Analytics Lib.
Ψ(𝑓 (𝑥)) - TF3600 CM
𝑓 (𝑥) 𝑓 (𝑥) - TE1400 Mat./Sim.
- ...

9
 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

10
Use case 'OPC UA connectivity'

 Very popular use case

 Support for Greenfield and Brownfield application
scenarios
 OPC UA Client/Server functionalities
 Data Access to underlying devices
 Historical Access
OPC UA
 Alarms & Conditions
 Companion specifications Beckhoff
Edge Device
 Security
 OPC UA / COM DA gateway OPC UA/DA

 Wrapper technology to convert OPC COM DA

(classic OPC) to OPC UA Beckhoff 3rd party device
Controller
Use case 'OPC UA connectivity'

 Aggration of OPC UA Servers into one single server

 Reduce firewall port exposure

OPC UA

Beckhoff
Edge Device

OPC UA/DA

Beckhoff 3rd party device

Controller
Use case 'OPC UA connectivity'

 Single server url for clients

 Reduced certificate managment complexity TrustCertificate ( )

Connect(opc.tcp://gateway-pc:4840)

OPC UA

Beckhoff
Server aggregation
Edge Device

OPC UA

Beckhoff 3rd party device

Controller
 MQTT vs. OPC UA ?

 Why focus on MQTT and OPC UA?

 OPC UA : standard for Industri 4.0 Microsoft
Azure
 Pub/Sub will be extension to OPC UA specification
 OPC Foundation specifies "OPC UA over MQTT"
 MQTT : wide adoption in IT/Cloud world MQTT
IoT Client
OPC UA ?
 Amazon Web Services
Beckhoff
 Microsoft Azure Edge Device

 IBM Watson
OPC UA/DA
 Google IoT

Beckhoff 3rd party device

Controller

14
MQTT vs. OPC UA ?

 It's not a question of "OPC UA or MQTT ?"

 Instead it's a question of "OPC UA over what transport ?"
 Client/Server is the classic communication architecture
 OPC UA now extended with Publisher/Subscriber

Application

MQTT MQTT
MQTT
Explanation:
{
Timestamp : x, {
Values : { DayTime : x,
Var1 : 42
OPC UA encoding  MQTT as bi-directional transport to the Cloud
Var1 : 42
} }  Devices 1 and 2 use JSON encoding as payload
}
 But: JSON documents can look different
 Receiving application has to understand every dialect
 Device 3 uses new OPC UA encoding as payload
3rd Party
 Receiving application only has to understand OPC UA
Device 1 Device 2 Device 3
OPC UA Publisher/Subscriber

 OPC UA has been based on client/server architecture since 2006

 Introduction of new transports based on Publisher/Subscriber
1. Machine-to-Machine communication via UDP
 Fast communication within machine network
UDP UDP
Beckhoff demonstrated first
Multicast realtime implementation world-wide
on SPS/IPC/Drives 2016

2. Machine-to-Cloud communication via MQTT

 Message Broker based connectivity
MQTT MQTT

Message Broker
 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

17
Use case firewall gateway'

 Support for Greenfield and Brownfield

application scenarios
 Firewall gateway to physically decouple
controller / machine network from office Other network
network
 Port filter allows to control which
applications are allowed data Firewall Configuration website
communication (inbound / outbound)
Beckhoff
Edge Device

Beckhoff 3rd party device

Controller
 Contents

1. Edge device basic concept

2. IoT connectivity and edge analytics
3. Realtime Processing on the Edge
4. OPC-UA Connectivity
5. Firewall Gateway
6. Industrial-proven hardware for edge computing

19
C60xx | industrial-proven hardware for edge computing
 C60xx | industrial-proven hardware for edge computing

C6015 C6017 C6030

Prozessor Intel® Atom™, bis zu 4 Cores Intel® Atom™, bis zu 4 Cores Intel® Celeron®, 2 Cores
Motherboard kompaktes Motherboard für Intel® Atom™ kompaktes Motherboard für Intel® Atom™ kompaktes Motherboard für Intel® Celeron®, Pentium®, Core™
i3, i5, i7 der 6. und 7. Generation

Speicher 2…4 GB DDR3L-RAM 2…4 GB DDR3L-RAM 4…32 GB DDR4-RAM

Grafik im Prozessor integriert, 1 DisplayPort-Anschluss im Prozessor integriert, 1 DisplayPort- im Prozessor integriert, 2 DisplayPort-Anschlüsse
Anschluss
Ethernet 2 on-board 2 on-board, optional 2 zusätzliche Anschlüsse 4 on-board

Festplatten/Flash 30-GB-M.2-SSD 30-GB-M.2-SSD 40-GB-M.2-SSD

Anschlüsse 1 USB-3.0-Port, 1 USB-2.0-Port 1 USB-3.0-Port und 1 USB-2.0-Port, optional 2 4 USB-3.0-Ports
weitere USB-2.0-Ports
Netzteil 24 V DC 24 V DC 24 V DC

21