Future-proof
plant automation
Ethernet-APL, NAMUR Open Architecture, MTP
Future-proof
Future-proof digitalization concepts are becoming increasingly important in the process industry. The aim is to boost efficiency, output, and availability through predictive maintenance, data-based process optimizations, and targeted plant modularization. With automation technology from Beckhoff, you have the tools to seamlessly integrate digitalization into your process technology plant in a way that suits your needs, for both greenfield and brownfield projects.
What potential does digitalization offer for the process industry?
- saves resources thanks to holistic recording of data and consumption
- increases output with intelligent system monitoring and optimization
- minimizes downtime through predictive maintenance of field devices
- shorter time-to-market thanks to modular system concepts
Discover our solutions for future-proof plant automation:
Ethernet-APL
The Ethernet Advanced Physical Layer (Ethernet-APL) provides the process industry with a new communication standard that enables fast and consistent data transmission. The aim is to use an Ethernet base to implement the entire communication in process technology plants – from field level to higher-level control systems. This includes pure process data and, more specifically, status information from field devices for diagnostics and predictive maintenance. Beckhoff has developed the compact ELX6233 EtherCAT Terminal to integrate Ethernet APL-capable field devices on a modular basis.
NAMUR Open Architecture
The NAMUR Open Architecture (NOA) is a concept developed by NAMUR for implementing plant monitoring and optimization in the process industry. NOA makes previously unread data usable via an additional second channel without changing the existing automation structure. Brownfield systems can easily be retrofitted. To implement NOA, Beckhoff has developed an NOA edge device, which consists of an embedded PC, EtherCAT Terminals, and a TwinCAT software project.
Module Type Package
The Module Type Package (MTP) is a manufacturer-independent standard for simplifying the modularization of process technology systems. The MTP contains all the necessary information and standardized interfaces to easily integrate individual process modules into the superordinate level process orchestration layer. Regardless of the control system manufacturer, modules developed once can be easily reused in other systems. With TwinCAT MTP, Beckhoff integrates the Module Type Package into the familiar TwinCAT Engineering environment.
A compact tabular overview of the technologies and concepts for digitalization in the process industry can be found in our onepager:
Applications: MTP and NOA in use
NAMUR Open Architecture implementation at Bayer
Process analytical technology (PAT) plays a crucial role in the chemical industry. Bayer AG, for example, is enhancing efficiency and transitioning from time-based to condition-based maintenance by embracing the cutting-edge NOA concept. This is implemented via the seamless integration of a compact edge device featuring a CX8110 Embedded PC, EL3182 EtherCAT HART Terminals, and TwinCAT OPC UA Server from Beckhoff, all without any alterations to the existing control technology.
Module Type Package (MTP) in industrial use at Ajinomoto Omnichem
In this use case, Ajinomoto Omnichem (an Ajinomoto Group company) and Beckhoff successfully demonstrated how the modular type package concept can be used to automate an industrial plant.
Our industry experts answer frequently asked questions
How can I combine Ethernet-APL with existing technologies?
In many applications, Ethernet-APL is to be used alongside existing communication technologies such as HART, Profibus, and digital signals; however, the market does not yet offer any solutions for this kind of mixed operation. This is why Beckhoff integrates Ethernet-APL into the existing terminal portfolio on a modular basis, allowing different signal types to be flexibly combined.
How is explosion protection implemented with Ethernet-APL?
Ethernet-APL specifies various energy levels for intrinsically safe Ethernet based on IEC specification 60079-47. These levels are outlined in the port profile specifications that every APL port in a network must comply with, and there is a clear definition of which ports may be connected to each other. With all of this information available, it is not necessary to perform a separate calculation of the proof of intrinsic safety.
How many devices can I connect to the NOA edge device?
The NOA edge device can be flexibly expanded with additional I/O terminals until the required number of channels is reached. There is no limit to the number of field devices that can be connected. In terms of software, the data from all connected channels is made available via the OPC UA server.
Can I only operate the NOA edge device with HART field devices?
No, the NOA edge device is also compatible with other communication protocols. By expanding with corresponding I/O terminals, field devices can also be connected via other protocols and flexibly combined with each other in an edge device.
Can I combine the NOA with other functions such as condition monitoring?
The central component of the NOA edge device is an industrial PC. In addition to the NOA functionality, it can also run other software components for tasks such as condition monitoring and energy management. To do this, simply expand the I/O terminals and integrate the necessary software blocks.
How does TwinCAT facilitate MTP-compliant programming?
TwinCAT allows for straightforward MTP programming without requiring in-depth guideline knowledge: It starts by defining the MTP interface, which produces the MTP file. This is then used for automatic code generation for the PLC and the HMI, allowing developers to concentrate primarily on the actual process logic and leave a large part of the programming to TwinCAT.
Does an MTP module have to have its own controller?
No, this is not necessary with our PC-based control technology. It is also possible to run several MTP modules simultaneously on our high-performance industrial PCs. The resulting ‘MTP hub’ makes the individual modules available to the control level independently of each other.
Can TwinCAT MTP use information from upstream planning steps?
Yes, this is possible thanks to the integrated engineering features in TwinCAT. In addition to the MTP import, it is also possible to read the DEXPI format or proprietary data sources into TwinCAT. This means information from upstream planning steps can be used directly in the engineering environment and passed on to the control level.
