OPC UA from Beckhoff: Technology, Products, Leadership How benefits from OPC Unified Architecture

Tom Burke, Global President, Hans Beckhoff, Managing Director and Owner, OPC Foundation: Beckhoff Automation:

“The OPC Foundation provides the best specifications, technologies, “Industrie 4.0 links the world of automation with the IT and Internet certifications and processes. One of the resulting technologies is world and will enable the resulting synergies to be leveraged. Network- OPC UA, the secure and reliable data exchange standard for manu- ing means communication, communication requires languages and facturer- and platform-independent industrial communication from associated functions and services. OPC UA offers a very powerful and the sensor to the cloud. Beckhoff was one of the first manufacturers adaptable standard basis that is accepted worldwide.” to integrate OPC UA directly into its control systems and is constantly launching trend-setting OPC UA products on the market. Beckhoff products and OPC UA optimally match to each other and offer the right solution for every challenge. Many other companies have followed Beckhoff and today also rely on OPC UA. The perfect interaction of Beckhoff products with OPC UA enables Beckhoff customers to master every challenge with the best and most advanced solutions. The Beckhoff culture is really great, as you can see from the dedicated teams behind the personal service and the high quality of the products. Hans Beckhoff himself is an inspiration, and it is great fun to work with him and the people in his company.” One of the central challenges of Industrie 4.0 and IIoT (Industrial Internet of Things) is the secure, standardized exchange of data and information between devices, machines and services – also from different industries. OPC UA is the data exchange standard for secure, reliable, manufac- turer- and platform-independent communication. RAMI 4.0 (Reference Architecture Model for Industrie 4.0) listed this IEC 62541 standard as a recommendation for the implementation of the communication layer as early as April 2015. The OPC UA standard enables cross-plat- form data exchange between products from different manufacturers. It combines specifica-

2 We reserve the right to make technical changes. How Automation benefi ts from OPC Unifi ed Architecture

Stefan Hoppe, Global Vice President, Sven Goldstein, TwinCAT Product Manager, OPC Foundation: Beckhoff Automation:

“Beckhoff has more than 10 years of experience with OPC UA. “The Beckhoff product range offers customers all the possibilities to In 2006, the company presented the world‘s fi rst embedded PLC use OPC UA in a wide variety of facets and applications. Our ongoing (a CX1020 with XPE) with an integrated UA server at the OPC UA involvement in the OPC Foundation working groups has a direct impact Developer Conference in Munich, Germany, and successfully launched on product development and is an important point in the roadmap of it on the market in 2007. The innovative corporate culture allows us the respective products.” to continually invent new ideas, it recognizes the value of important standards at an early stage and supports them in a pioneering man- ner – including OPC UA. This benefi ts Beckhoff‘s technology-oriented customers, as demonstrated by numerous applications in a wide variety of industries – from water management and manufacturing to renewable energies. OPC UA technology today offers an import- ant contribution to openness and secure exchange of information between the IT and OT worlds in the context of Industrie 4.0.”

tions developed in close cooperation between positively by the German Federal Offi ce for Infor- OPC Unifi ed Architecture: manufacturers, users, research institutes and mation Security (BSI). ƒ standardized and secure data consortia for exchanging information securely OPC UA is not only a communication exchange between devices, machines in heterogeneous systems. The OPC UA object protocol, it also allows systems to be modelled and industries model enables production data, alarms, events and mapped in the so-called OPC UA namespace ƒ integrated communication from the and historical data to be integrated in a single by means of an extendable information model. sensor to the cloud OPC UA server. This allows, for example, a Functionalities such as Historical Access or ƒ manufacturer- and platform-independent temperature measuring device to be displayed Alarms & Conditions can be used as well as the ƒ recommended in RAMI 4.0 for as an object with its temperature value, alarm extended security mechanisms. The equipment implementation of the communication parameters and the corresponding alarm limits. and machine manufacturer retains complete layer The security mechanisms of OPC UA ensure the control over the data. integrity and encryption of exchanged data and allow authentication of clients and servers. The above-mentioned mechanisms were rated very

We reserve the right to make technical changes. 3 Advantage in OPC implementation: with Beckhoff

Beckhoff initiates and leads PLCopen working group Joining the for OPC UA. Milestone 1: OPC Foundation IEC 61131 mapping

1998 2006 2007 2008 2010

First OPC COM DA product: Prototyping of an OPC UA Beckhoff presents the First customer application: OPC Foundation elects TwinCAT OPC DA server server to validate OPC UA fi rst OPC UA product on the Areva offshore wind turbine Beckhoff employee as specifi cation market: TwinCAT OPC UA with OPC UA connection to President of OPC Europe server shore

Beckhoff has been a pioneer in open standards This means that an interoperability workshop for many years, so that customers can benefi t leads to optimization of product development. from particularly extensive interoperability Changes in the specifi cation are also conceivable between Beckhoff and third-party products. if defi cits are discovered by different interpreta- The great commitment in the area of OPC tions of the development. Beckhoff is one of the standardization is an essential part of this. few companies that has its products tested for Interoperability workshops organized annually real interoperability and stability every year in by the OPC Foundation, including in Europe, the latest versions and with the latest functions. are a central component of the interoperability The fi ndings are then fed into the development of many communication systems. This is where and into the specifi cation working groups. specifi cation aspects are tested in practice At present, Companion Specifi cations are to increase real interoperability between the defi ned in the different machine construction OPC UA products of the participating manu- domains. These are descriptions that contain facturers. domain-specifi c facts, based on the language

4 We reserve the right to make technical changes. PLCopen working group Beckhoff collaborates Milestone 2: OPC UA client in OPC UA Pub/Sub working IEC 61131 function blocks group

Beckhoff collaborates in OPC Beckhoff collaborates in UA Security working group OPC UA TSN working group Beckhoff is co-initiator and member of the cooperation Beckhoff collaborates in OPC Beckhoff collaborates in OPC between OPC Foundation UA OMAC working group UA I/O Link working group and M2M Alliance

2013 2014 2015 2016 2017

Beckhoff and Siemens First customer application First customer application Beckhoff presents the Beckhoff and Microsoft promote consistent node for water management in for world‘s fi rst real-time- promote OPC UA for the sets at the control level involving the IEC 61131 OPC connecting OPC UA servers capable prototype for vali- Microsoft Azure Cloud UA client function blocks to Microsoft Azure dation of Pub/Sub extension Beckhoff is co-host Beckhoff presents the Beckhoff hosts the OPC Day of the OPC Seminar Tour OPC UA-based SOA PLC at in Finland North America 2017 the Hannover Messe Beckhoff sponsors the OPC Foundation members OPC Seminar Tour North elect Beckhoff to the OPC America 2016 Board of Directors

Beckhoff provides Global Vice President of the OPC Foundation

resources of OPC UA. The reason for this is that tion and automatically set up a corresponding Milestones an OPC UA client that connects to a machine namespace. After the customer has carried out ƒ Member of the OPC Foundation should be able to understand it as a machine a mapping to the symbolism of his PLC program, since 1998 of a particular type by means of the UA repre- corresponding live data of the controller is pro- ƒ certifi ed OPC UA products since 2007 sentation, regardless of which manufacturer vided according to the Companion Specifi cations. ƒ annual participation in all major has built the machine. This means that concrete interoperability events machine specifi cations are accessed, rather than ƒ continuous collaboration in a structured list of variables, which is confi gured important working groups and differently for each manufacturer. Companion Specifi cations Beckhoff provides comprehensive generic ƒ since 2014: Beckhoff employee functions in its products. TwinCAT offers an is Global Vice President of the OPC UA interface that meets the corresponding OPC Foundation Companion Specifi cations of the domains. The TwinCAT OPCUA server can load such a descrip-

We reserve the right to make technical changes. 5 Service-Oriented Architecture: SOA PLC Concept

Transport Access rights

Beckhoff Customer Models Data-Services Engineering Models

1 2 3 4 App OS + TwinCAT 3 Moni- specific toring

Administration

Standardized Models

Beckhoff coined the term SOA PLC, in order communication channel. Beckhoff also offers a Level 1: to structure and present the different options diagnostic model. The outermost layer represents real-time control of OPC UA. SOA stands for Service-Oriented the transport of OPC UA via the given com- Architecture. It describes the interaction of the munication channels, including the encryption Level 2: OPC UA components. At the core is a real-time mechanisms. The SOA PLC concept is supported data, project planning, diagnostics control system, e.g. TwinCAT. Data and project by Beckhoff controllers. and monitoring accesses planning access as well as diagnostics and In addition to the actual read/write access monitoring accesses are built manufacturer- to data points, methods can be defined in the Level 3: independent around the actual real-time layer. models that can be executed directly in real-time. modelling The next level shows Companion Specifica- They can be understood as service calls. tions, i.e. interoperable, standardized machine Level 4: access. OPC UA also offers the option to add transport of information and manufacturer-specific extensions. Unique selling access rights points can thus be mapped through the same

6 We reserve the right to make technical changes. Highly scalable – from the smallest controller to the many-core system

P81 P90 Very high Andere performance Hersteller P80 als Beckhoff Very high 12 Cores performance P91 P70 High 5-8 Cores performance P60 P82 Mid Very high P92 performance performance 9-16 Cores P50 12 Cores Performance plus P83 P93 P40 Very high Performance Intel® Intel® Intel® performance 17-32 Cores Celeron® ULV Core™ i3 Core™ i5 P30 24 Cores Economy plus Intel® Intel® P94 Celeron® Core™ i7 P84 Very high 33-64 Cores P20 Intel® performance Economy Intel® Atom™ Pentium® 36 Cores ARM Cortex™-A8 ARM, 800 MHz AMD LX800

Together with associated software, PCs in the Beckhoff product philosophy, only compo- Scalable for all applications different form factors are at the core of a wide nents and processors of the latest technologies ƒ powerful Industrial PCs and software range of diverse automation tasks such as control are used in the development and design of for all automation tasks of machines, processes or logistics systems, Industrial PCs. Fine scaling is provided through ƒ Beckhoff philosophy: the latest networking of system components, data acquisi- processor graduations from Intel® Atom™ to technological standards as a basis tion, or image processing. Beckhoff is one of the Intel® Core™ i7. This scalability of Beckhoff ƒ scalable hardware and software pioneers of PC-based automation: The fi rst PC Industrial PC hardware can also be mapped to a that can be used throughout control system was delivered as early as 1986. high degree to Beckhoff OPC UA components. Beckhoff Industrial PCs are characterized by a The software components can be installed and wealth of technology know-how accumulated used consistently on all performance classes, be over recent years. In combination with the it a low performance class such as the CX8000 TwinCAT automation software, they offer a or CX8100 Embedded PC, or a high performance high-performance control system for PLC, class such as the C6670 industrial server. NC and CNC functionalities. In accordance with

We reserve the right to make technical changes. 7 At a glance: Beckhoff products for OPC UA

Cloud Service s

Microsoft Azure™ Amazon Web Services

Smart Factory SAP HANA® Cloud Platform Beckhoff

ERP/MES Smart Factory

MQTT AMQP OPC UA

IPC Diagnostics

TwinCAT HMI

OPC UA, ADS, EtherCAT Automation Protocol

IPC Diagnostics TwinCAT IoT PC-Control TwinCAT OPC UA TwinCAT Scope

I/O

= OPC UA enabled

8 We reserve the right to make technical changes. At a glance: Beckhoff products for OPC UA

Beckhoff is a long-standing member of OPC Foundation. Beckhoff already adapted OPC UA standards in their early days and was thus able to establish the corresponding know-how at an early stage and implement it in Smart Factory Smart Factory products. The fi rst OPC UA server was presented as early as 2006. From 2007 onwards, it was offi cially offered as a TwinCAT supplement and used in initial customer projects. The wide range of applications for OPC UA is thus also refl ected in the Beckhoff product portfolio. Beckhoff products offer a wide range of options for being used via OPC UA in automa- tion projects: Industrial PC diagnostics options made available via OPC UA, access to TwinCAT real-time data, connection of OPC UA devices to the TwinCAT HMI visualization system and even the cloud. In addition, the EK9160 IoT Bus Coupler is a hardware device that enables direct, simple and secure access to I/O terminals via OPC UA.

TwinCAT Scope

TwinCAT Target Browser

Beckhoff OPC UA products: ƒ Beckhoff IPC Diagnostics Page 10 ƒ TwinCAT OPC UA Page 12 ƒ TwinCAT IoT Page 16 ƒ IoT Bus Coupler Page 17 ƒ TwinCAT Scope Page 18 ƒ TwinCAT HMI Page 20 IoT Bus Coupler ƒ TwinCAT Target Browser Page 21 ƒ Modelling of information models Page 22 ƒ TwinCAT PackML Page 23

We reserve the right to make technical changes. 9 Beckhoff IPC Diagnostics: Diagnostics and Confi guration via OPC UA

OPC UA IPC Windows Server Diagnostics API

BIOS

OPC UA OPC UA Client Registry

API Local + Remote Local

OPC UA server namespace with system data of the control computer

Local + Remote Local

IPC Windows OPC UA OPC UA Diagnostics API Client Abstraction Layer BIOS ADS ADS Client

Registry TwinCAT ADS PLC C++/C#

Interfaces for Beckhoff IPC Diagnostics

10 We reserve the right to make technical changes. Beckhoff IPC Diagnostics: Diagnostics and Configuration via OPC UA

IPC Diagnostics website

The control computer is a central element of speed, RAID status, and also operating system IPC Diagnostics any PC-based machine control system. There­ information such as CPU load or embedded write ƒƒ secure access to system data of the fore, it is important to detect critical system filter settings. OPC UA access can be secured via control computer states, e.g. risk of overheating of the CPU or the certificates. ƒƒ detection of critical states of the motherboard, at an early stage. The monitoring By implementing the standardized OPC UA control computer of relevant PC parameters allows conclusions file types, any files and directories can be ƒƒ OPC UA server for data access and to be drawn about its availability or life expec- released on the Industrial PC and made available file transfer tancy. As a complimentary component of every via OPC UA, either for reading or writing files. ƒƒ for integration into own applications Beckhoff Industrial or Embedded PC, Beckhoff This enables all OPC UA clients that support ƒƒ integrated web page for visual and IPC diagnostics provides this parameter data via file types to securely exchange files with the simple presentation of system data various interfaces, such as a website or an inte- controller, e.g. for downloading log or config­ ƒƒ based on standardized grated OPC UA server. These can be used to read uration files. IEC 61131/OPC UA mapping out and, if possible, set hardware-related values such as CPU or mainboard temperature, fan

We reserve the right to make technical changes. 11 TwinCAT OPC UA: Basis for SOA PLC and universal Software Interface

TwinCAT OPC UA at a glance

OPC COM DA OPC UA OPC UA

UA Gateway

TwinCAT OPC UA Server TwinCAT OPC UA Client

TwinCAT Runtime PLCopen, I/O device

Access rights for TwinCAT OPC UA server

Login

TwinCAT OPC UA Server

TwinCAT Runtime

With the TwinCAT OPC UA product suite, a simple way. The UA gateway rounds off the access to TwinCAT 2 and TwinCAT 3 Runtime, Beckhoff has been providing a long-standing product range by offering a free OPC COM DA but also enables connection of Beckhoff Bus and established OPC UA product in the form interface for TwinCAT OPC UA server, which Terminal Controllers of the BC series. Supported of a TwinCAT supplement since 2007. On the legacy clients can use to simplify the migration OPC UA profi les range from simple data access one hand, this product suite with the TwinCAT from OPC COM DA to OPC UA. to method calls and functionalities such as OPC UA Server includes the possibility of Historical Access and Alarms & Conditions. The receiving read/write access to symbols from TwinCAT OPC UA server extensive functionalities for confi guring various the TwinCAT real-time environment and even The TwinCAT OPC UA server is the longest-run- security mechanisms not only enable securing of making methods callable from the real-time. ning OPC UA product from Beckhoff. Beckhoff of the communication channel via certifi cates, On the other hand, the TwinCAT OPC UA client presented the fi rst OPC UA server for access- but also confi guration of users, roles and access makes it possible to either communicate directly ing TwinCAT real-time at the OPC Developer rights at the namespace level down to individual with other OPC UA servers via standard PLCopen Conference as early as 2006. Based on this, nodes. All confi guration steps are performed IEC 61131 function blocks from the real-time the TwinCAT OPC UA server was developed in using a graphical confi gurator integrated into logic, or to confi gure this via an I/O driver in 2007. It not only offers the possibility of OPC UA Visual Studio®.

12 We reserve the right to make technical changes. Visual Studio® integration of the OPC UA server configurator

TwinCAT OPC UA configurator automation interface and automate the creation TwinCAT OPC UA Server The TwinCAT OPC UA server is configured of OPC UA server configurations. ƒƒ access to real-time variables from Visual Studio® via the TwinCAT OPC UA ƒƒ support of various profiles (DA, HA, AC) configurator. This offers the possibility to ƒƒ configuration of access rights parameterize all facets of the server, starting ƒƒ integrated MethodCall mechanisms with Data Access, through Historical Access provide the basis for SOA PLCs and Alarms & Conditions to Security Config­ uration. The configuration can be done either TwinCAT OPC UA configurator for the local system or a remote system. As ƒƒ based on Visual Studio® a special highlight, the configurator also uses ƒƒ local/remote configuration of a OPC UA as a communication channel between server via OPC UA Visual Studio® and the remote system to be ƒƒ API for automated creation of configured accordingly. An API for the Windows configurations Powershell is available to extend the TwinCAT

We reserve the right to make technical changes. 13 TwinCAT OPC UA: Basis for SOA PLC and universal Software Interface

OPC UA OPC COM DA

UA Gateway

TwinCAT OPC UA Server TwinCAT OPC UA Server TwinCAT OPC UA Server

TwinCAT Runtime TwinCAT Runtime TwinCAT Runtime

Server aggregation in the UA gateway

TwinCAT OPC UA Client The TwinCAT OPC UA client, which was created in 2012, enables communication with an OPC UA server directly via function blocks from the PLC control logic. In 2014, these PLC function blocks were standardized by PLCopen with support from Beckhoff. The implemented functionalities range from simple read/write accesses to method calls. In 2017, an I/O driver was added, which integrates the use of the TwinCAT OPC UA client functional- ities directly into the TwinCAT I/O system and thus further simplifi es their handling and also makes real-time available for TwinCAT 3 C++.

14 We reserve the right to make technical changes. TwinCAT OPC UA Client over PLCopen function blocks and I/O device

TwinCAT OPC UA Gateway TwinCAT OPC UA Client Since 2016, the TwinCAT OPC UA gateway has ƒƒ support for Data Access and Historical Access provided a free OPC COM DA interface in the ƒƒ based on PLCopen function blocks form of wrapper technology for the TwinCAT ƒƒ I/O driver for easy integration into the OPC UA server. This not only makes it easier for automation project users to switch to OPC UA, since both interfaces (OPC COM DA and OPC UA) are integrated in TwinCAT OPC UA Gateway one package and OPC UA is already used in the ƒƒ integrated OPC COM DA server background, but also offers the option of server ƒƒ aggregation of TwinCAT OPC UA servers aggregation, whereby several TwinCAT OPC UA servers can be combined in one network and www.beckhoff.com/english/twincat/tf6100 made accessible via a single server endpoint.

We reserve the right to make technical changes. 15 TwinCAT IoT: With OPC UA into the Cloud

Message Broker

Microsoft Amazon Web Azure™ Services

MQTT, AMQP, OPC UA

OPC UA TwinCAT IoT Data Agent OPC UA Server

The graphical confi guration interface of the IoT Data Agent facilitates parameterization of the IoT project TwinCAT Runtime

TwinCAT IoT Data Agent with OPC UA connection

The increasing convergence of IT and automation broker. The TwinCAT IoT Data Agent, a gateway TwinCAT IoT Data Agent technologies makes cloud-based communication application that is operated on an industrial PC, ƒ fl exible implementation of cloud-based services increasingly interesting for industrial third-party systems can be connected to the cloud production concepts with TwinCAT IoT control projects. Accordingly, PC-based control in addition to TwinCAT systems via the integrated ƒ connection of third-party systems to technology is gaining in importance. OPC UA client. the public or private cloud via OPC UA With TwinCAT IoT, Beckhoff TwinCAT supports The graphical confi gurator facilitates param- ƒ graphical confi gurator simplifi es connec- all relevant communication standards, such as eterization of all facets of the IoT confi guration, tion of the control system to cloud systems OPC UA and MQTT, and facilitates the imple- including access data for the OPC UA server, the ƒ enables retrofi t: Connecting legacy mentation of cloud-based production concepts. selection of the nodes to be used, and the settings systems to the cloud TwinCAT IoT offers various products for connect- of the cloud service and the data formats. ƒ uniform data format guarantees ing the control system to the cloud, whereby both The uniform data format of the TwinCAT IoT cross-product interoperability public cloud systems such as Microsoft Azure, and analytics products and the EK9160 ensures Amazon Web Services or Google IoT and private that all components are interoperable and can be www.beckhoff.com/twincat-iot cloud systems can be used via an MQTT message combined with each other.

16 We reserve the right to make technical changes. IoT Bus Coupler EK9160: Direct access to sensors and actuators via OPC UA

Configuration of cloud systems

Webseite der IPC-Diagnose

Configuration of I/O terminals Integrated OPC UA server of EK9160

EK9160 IoT Bus Coupler enables sensors and respective cloud services and security mechanisms, IoT Bus Coupler actuators to be transferred easily, safely and such as authentication or encryption, can also be ƒƒ plug-and-play concept for simple and cost-effectively to all common cloud systems. configured conveniently via a browser. After the secure connection of I/Os to the cloud With EK9160 IoT Coupler, Beckhoff offers direct parameterization, the coupler independently sends ƒƒ integrated OPC UA server for easy connection of EtherCAT I/Os to the Internet of the digital or analog I/O values to the cloud service, and secure access to I/Os Things. EK9160 converts the EtherCAT signal including a timestamp. All connected I/O terminals ƒƒ access rights to I/Os can be defined representation of the I/Os to IoT communication can also be accessed automatically via the inte- via OPC UA protocols such as OPC UA or MQTT. It thus enables grated OPC UA server. If required, this access can ƒƒ integrated web page for easy the simple and standardized integration of I/O data be restricted to different user roles. configuration of cloud access and I/Os into cloud-based communication and data services. Neither a controller nor programming is nec- www.beckhoff.com/EK9160 essary. The I/Os are configured and parameterized in a simple configuration dialog of the integrated web server via any web browser. Settings for the

We reserve the right to make technical changes. 17 TwinCAT Scope: OPC UA for analysis of Third-party Systems

TwinCAT Scope

TwinCAT ScopeView is an advanced charting tool for the graphical display of signals. It offers ease of operation and high performance in the presentation of line or bar charts. Signifi cant events can be marked.

TwinCAT Scope View

TwinCAT Scope Server ADS OPC UA Client

TwinCAT OPC UA Server 3rd Party OPC UA Server

TwinCAT Runtime TwinCAT Runtime 3rd Party Runtime

3rd Party

18 We reserve the right to make technical changes. Acquisition parameters in the Visual Studio® Property window for an OPC UA node

Multi-core oscilloscope the use of certificates make this process reliable TwinCAT Scope with standardized communication and secure. .. intuitive operation .. high-performance data logging The high-performance TwinCAT Scope software The charting tool of automation specialists .. standardized communication oscilloscope is divided into two basic components: TwinCAT ScopeView offers multi-core support .. different chart types Scope View integrated in Microsoft Visual Studio® as well as trigger, chart synchronization, cursor, .. multi-core support for the graphical display of measuring signals and data export and many zoom functions to enable .. trigger functions Scope Server for the actual data logging. Scope full utilization of the computing power of the .. data export Server has a TwinCAT-specific and a standardized system for displaying high-frequency signals. This communication channel. The standardized com- allows different signal curves as well as complex www.beckhoff.com/tc3-scope munication channel is implemented as an OPC representations such as XY plots or bar charts UA client. This enables the Scope to collect and to be drawn. Measurement and analytical tasks, display manufacturer-independent measurement e.g. output of frequency responses, can thus be data from heterogeneous systems. OPC UA and realized.

We reserve the right to make technical changes. 19 TwinCAT HMI: Open, extendable visualization solution with integrated OPC UA

Panel PC Panel PC

TwinCAT HMI Client 1 TwinCAT HMI Client TwinCAT HMI Server

HTTP(S), WS(S) TwinCAT HMI Server Extensions ADS OPC UA BACnet ...

ADS OPC UA BACnet … TwinCAT Runtime 3rd Party Runtime BACnet Device …

Multi-protocol scenario with OPC UA

TwinCAT integrates the development of human to all TwinCAT devices. For manufacturer-inde- TwinCAT HMI machine interfaces directly into the familiar pendent communication, an OPC UA client was ƒ effi cient engineering engineering environment of Visual Studio®. integrated directly into the TwinCAT HMI server. ƒ integration in Visual Studio® Regardless of the operating system and device, Support for ADS and OPC UA is complementary ƒ platform-independence the web-based user interface is always re- and expands the fl exible application possibilities ƒ web-based (HTML5, JavaScript) sponsive and adapts to the resolution, size and of the TwinCAT HMI. ƒ powerful architecture orientation. The TwinCAT HMI can be extended ƒ modular expandability fl exibly at all levels and enables you to develop ƒ high-level language integration your own controls or integrate business logics ƒ integrated OPC UA client for into the server. Safety and standards were at visualization of third-party systems the forefront of the development of the TwinCAT HMI. The TwinCAT HMI server supports the open www.beckhoff.com/TwinCAT-HMI ADS (Automation Device Specifi cation) from Beckhoff, which allows access

20 We reserve the right to make technical changes. TwinCAT Target Browser: All communication channels centrally managed

TwinCAT target browser in Microsoft Visual Studio® with node value preview

Multi-protocol scenario with OPC UA

The TwinCAT target browser is the central point the namespace of an OPC UA server and select TwinCAT Target Browser in TwinCAT engineering for accessing control nodes that are made available to OPC UA-sup- ƒƒ central basic tool for configurators data of distributed runtimes. The runtimes serve porting tools in TwinCAT system. ƒƒ support of multiple communication as data sources for various TwinCAT products channels, e.g. OPC UA such as the database server, ScopeView or the ƒƒ charting view for previewing live values OPC UA configurator. Various communication channels are available for access. Open and TwinCAT-specific communication via ADS protocol, MQTT in the field of IoT communication protocols and the OPC UA protocol, which is most widely used and standardized in the automation world. The integrated OPC UA client functionality makes it possible to use Target Browser to browse

We reserve the right to make technical changes. 21 For different Information Models: OPC UA

OPC UA Server namespace with system informa- tion of the control computer

Transport Access rights Companion Information Models Beckhoff Customer PLCopen, BACnet, AutomationML, IO-Link, AutoID, Models Models IEC 61850/61400, PackML Data- Engineering Services Built-in Information Models OS + TwinCAT 3 App Moni- specifi c toring

Administration OPC UA Meta Model

Standardized Models

The OPC UA metamodel describes how clients manufacturer-specifi c and defi ned by different Information models with OPC UA access information in the server. It defi nes a organizations, which then form a working group ƒ OPC UA offers several basic information set of uniform node types that can be used to for the defi nition of a so-called Companion models that are already integrated display objects in the address space. This model Specifi cation. Beckhoff is represented in all ƒ modelling of special models is possible represents objects with their variables, methods, working groups that are important for automa- ƒ working groups on Companion events and their relationship to other objects. tion and actively supports the defi nition and Specifi cations defi ne type systems for The properties of each node are described by extension of the specifi cation, e. g. PackML, different domains OPC UA defi ned attributes. Attributes can have Pub/Sub, OPC UA TSN, IO-Link, IEC 61850, data values, which can be simple or complex. PLCopen, BACnet. OPC UA enables modelling of any object and vari- able types and the relationships between them. The semantics are displayed by the server in its address space and can be captured by clients. The type information can be standardized or

22 We reserve the right to make technical changes. TwinCAT PackML: reduces the Engineering Effort through OPC UA integration

Tag Database, MES Apps Historian, etc. PackML, OPC UA

OPC UA PackTags network Case Packing/ Palletizing Shrink Wrapping Unscrambling

PackML, OPC UA Labelling/ Sealing Filling Capping

PackML, OPC UA

Washing/Drying/ PackML, OPC UA Sterilizing

PackML, OPC UA PackML, OPC UA

Function blocks of the Tc3_PackML_V2 library

In TwinCAT 3, a supplementary PLC library with every OPC UA client can access them directly. TwinCAT PackML PackML blocks (ISA-TR.00.02) standardized Admin, command and status tags are available ƒ Tc3_PackML_V2 library contains according to OMAC is now available free of within these structures. Thus, commands and the current state of all standardized charge for the packaging industry. OMAC PackML information can be communicated by each device PackML function blocks provides the defi nition of a state machine for use via a standardized interface. ƒ function blocks for simple use of in machines and plants. In addition, a terminology the PackML State Machine for this state machine is defi ned and its use is ƒ function blocks for switching between documented by means of examples. the freely confi gurable, application- Additional structures, so-called PackTags, are specifi c PackML state machines provided as a central interface for the communica- ƒ structures of the PackTags included tion of machines and systems among each other in PackML and with other devices (HMI/Master Computer/ ƒ simple engineering: library is auto- MES/SCADA). These are automatically preconfi g- matically prepared for use via the ured for use in TwinCAT OPC UA server, so that TwinCAT OPC UA server

We reserve the right to make technical changes. 23 DK3312-1117

OPC UA from Beckhoff. Further information www.beckhoff.com/opc [email protected]

Beckhoff Automation GmbH & Co. KG Huelshorstweg 20 33415 Verl Germany Phone: + 49 5246 963-0 [email protected] www.beckhoff.com

Beckhoff®, TwinCAT®, EtherCAT®, EtherCAT P®, Safety over EtherCAT®, TwinSAFE®, XFC® and XTS® are registered trademarks of and licensed by Beckhoff Automation GmbH. Other designations used in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owners.

© Beckhoff Automation GmbH & Co. KG 12/2017

The information provided in this brochure contains merely general descriptions or characteristics of performance which in case of actual application do not always apply as described or which may change as a result of further development of the products. An obligation to provide the respective characteristics shall only exist if expressively agreed in the terms of contract.