Introduction
This application example explains, step by step, how a modular production is engineered using the MTP approach—from module modeling to an executable automation project. The focus is on the engineering workflow, starting with the ABB MTP Module Designer and ending with a runnable control project derived from the MTP package
Step 1: Modeling the Application Module in the MTP Module Designer
The workflow starts in the ABB MTP Module Designer, which provides a graphical environment for defining a process module.
In this step, the engineer:
-
Models the module structure using standardized MTP elements
-
Defines services representing the functional capabilities of the module
-
Configures parameters, signals, and interfaces
-
Specifies operational states and allowed transitions
-
Assigns alarms and diagnostics relevant for process operation
This approach allows the application module to be described in a structured and standardized way, independent of the orchestration system.
Step 2: From Engineering Model to MTP Package
Once the module model is complete, the Module Designer generates a compliant MTP package. This package represents the formal interface contract of the application module.
The generated MTP package:
-
Is based on a standardized, machine-readable XML structure
-
Contains services, parameters, states, alarms, and communication metadata
-
Uses OPC UA as the underlying communication model
-
Is portable across engineering and orchestration systems
At this point, the application module is fully described, but not yet executable.
Step 3: Importing the MTP Package into Automation Engineering
To execute the application module on a controller, the MTP package is imported into the automation engineering environment.
The import process uses the MTP file as input and performs:
-
Validation of the MTP structure and namespaces
-
Interpretation of services, states, and interfaces
-
Preparation for automatic project generation
This step marks the transition from module description to executable automation.
Step 4: Automatic Generation of Interfaces and Diagnostics
During import, key automation artifacts are generated automatically based on the MTP definition:
-
OPC UA interfaces for communication with the orchestration layer
-
Diagnostics, including alarms and events
-
Visualization metadata for HMI integration
This ensures that the application module exposes consistent interfaces and diagnostics without manual configuration.
Step 5: Generation of Services, States, and Tasks
The imported MTP services are transformed into executable structures within the automation project:
-
Each MTP service is mapped to a corresponding service task
-
Operational states and transitions are created according to the MTP definition
-
Equipment elements such as valves, pumps, and drives are instantiated
The result is a structured project skeleton reflecting the functional design of the application module.
Step 6: OPC UA Connectivity and Access Control
Connectivity settings are derived directly from the MTP package:
-
OPC UA nodes are created automatically
-
Access rights (read/write/no access) are applied per parameter
-
Parameters and signals are mapped consistently across systems
This guarantees that the orchestration layer interacts with the application module exactly as defined in the MTP package.
Step 7: Completing the Module Logic
The generated automation project provides a functional baseline:
-
Defined services and states
-
Equipment instances and diagnostics
-
Communication and connectivity
Depending on the module designer capabilities, logic may be partially generated or extended manually during engineering. This allows application-specific behavior to be added while preserving the standardized MTP interface.
Result: Executable Application Module Based on MTP
At the end of the workflow, the application production module is available as an executable automation project:
-
Interfaces, diagnostics, and services are standardized
-
The module is ready to be connected to a POL orchestration system
-
The architecture supports modular scaling and replacement of modules
This confirms that MTP can be used as a practical engineering artifact for modular applications.
Summary
Starting from the ABB MTP Module Designer , the modular production example shows a continuous and structured engineering workflow: module modeling, MTP package generation, import, and automatic creation of an executable automation project. The approach ensures standardized interfaces, consistent diagnostics, and clear separation between module control and orchestration, making MTP suitable for scalable and modular production systems.