In recent years, the concept of modular devices has gradually gained popularity in the life sciences and the broader automation industry. This trend facilitates the commissioning of production equipment, but also increases the complexity of defining plant-wide automation systems.

For life sciences manufacturers, horizontal dimension integration (device-to-device interactive interface-based automation) and vertical integration (device-to-plant automation) are often key steps before production begins. These include programmable logic controller (PLC) control functions to validate shop floor process equipment, such as packaging equipment, and distributed control system (DCS) functions for plant automation.

1756-OB32 Pharmaceutical companies are increasingly exploring modularity, and so are the potential challenges they face. For example, they use one company to supply a plant-wide distributed control system (DCS), another to supply production equipment and corresponding automation components, and even third-party components for other equipment. As a result, the number of programmable logic controllers (PLCS) used in factories has multiplied.

Some members of the life sciences work team are realizing that ordering pre-standardized equipment directly has a lead time advantage over reconfiguring the equipment on site, but on-site process and automation integration for these standard products can be very stressful and difficult. Therefore, when automation engineers choose automation components for process equipment, components with “plug and produce” capabilities become a better choice, just like the application logic 1756-OB32 of printers. At the same time, Rockwell Automation and its member organizations and companies in the industry are actively working to stabilize and strengthen the foundation of plug-and-production technology.

The driving force behind modularity

NAMUR, headquartered in Germany, is one of the groups driving the development of plug-and-go production technology, is the user association of automation technology in the process industry, and is an international group representing users of automation technology and process control technology experts. The group has more than 150 member companies worldwide who understand the value of plug-and-produce modules. Specifically, it’s easier to replace function-specific field process equipment based on production needs, as well as a better understanding of how plant operators work, using standard interfaces to process standard data.

The group is helping to develop a modular standard known as the MTP Module Type Package (VDI/VDE/NAMUR 2658), which covers everything from data to human machine interface (HMI). The standard uses the OPC Unified Architecture (UA) to describe communication, alarm, security and other functions.

1756-OB32

The MTP standard was written in accordance with the NE148 standard and the Industry Reference Architecture Model (RAMI) 4.0, and has evolved into an IEC standard for the life cycle of factory components. This standard basically stipulates that any design should follow a modular concept so that components can be upgraded or replaced at any time. In addition, the MTP standard also has the following functions:
From a safety perspective, a process 1756-OB32 equipment component (PEA) is an automated, autonomous, modular processing unit consisting of one or more process equipment that represents the process equipment or infrastructure that performs a process in a modular plant
The Process Orchestration Layer (POL) is a device component that spans automation and information technology levels to modularize system operations
•MTP formally describes the interfaces and capabilities of automation technologies in modular processing units

How MTP works

The MTP file provided by the equipment vendor is the core of the MTP standard and represents the PEA interface. This file contains all the information that POL needs to set up its communications, labels, services and HMI in order to monitor/control the PEA.

In the MTP file, each device is defined using an automation-specific XML 1756-OB32 data format (called AML Automation Markup Language) specified by the International Standard (IEC 62714). For example, a bioreactor with its own control and HMI system will provide an MTP file that defines a variety of available content, including the following:
• Service – heating, stirring, pH control
• Data – temperature, pressure, flow
• Visualization – Operator graphical interface related to POL operations
• Call the Police
• Event/trigger condition

In addition, MTP compliant POL can be used to obtain OPC UA connection and labeling information for the above projects, and can also help import MTP PEA files from various process equipment in the plant system, and use this information to develop plant level visualization and batch processing systems for monitoring and controlling process equipment in the shop floor. POL already allows plant-level operators to use a unified graphics, object monitoring and control package, and also allows batch systems to use standard formulations to monitor and control services, regardless of process equipment functionality or brand.