We are getting vaguely qualified mentions and requests from potential customers in the F&B and chem area - Is it something IA is looking into ? I just came across marketing material which looks very promising :
https://www.controlglobal.com/articles/2021/7-module-type-package-resources/
Pinging this since we have received several inquiries as well.
Never heard of this. Might be a better question for sales / sales engineering.
Any update on this? Seems MTP is getting supported by more and more serious SCADA providers.
Up
Hi guys. Wanted to add that I have a project that would like to implement this functionality as well. Most major DCS offer some import tool for MTP filetypes. The MTPs are being developed by the OEM of separate process equipment. Once configured at the MTP level you can import the MTP for automated configurations of OPCUA process steps, alarms/events etc. Hoping we could find a rev that would include this at a later date. Makes commissioning a breeze. There would definitely be a business case imo opinion to include this functionality.
Can you tell me a little bit about how you imagine support for MTP in Ignition would look?
Is it something like: you have some kind of modular process equipment, the vendor of which is providing MTP file(s) for it. You import that file into Ignition somewhere, and then suddenly what? OPC connections are created automatically? Tags are created? More?
The goal of MTP is a consistent operator experience and plug-and-produce integration of modules with minimal engineering effort.
MTP is an industry-standard specification for modular automation. MTP 1.x was specified by VDI/VDE/NAMUR 2658; MTP Version 2.0 was released in January 2026 by PI in cooperation with NAMUR and ZVEI.
Major automation vendors such as Siemens, Rockwell Automation, and Schneider Electric provide MTP-enabled PLC engineering environments and complete automation solutions.
POL systems import MTP files to automatically generate automation objects, such as HMI objects, service orchestration objects based on ISA-88 concepts (such as phases), and communication interfaces.
So far from my point of view.
These MTP seem to be an xml code and probably some other meta-data. To me it seems that what you just described is the way to go : a converter of the standard into the existing way ignition operates --> Comm driver, Tag structure & perspective object/graphic linked to such object.
I imagine the implementation is not at all straightforward but I'm guessing that a first approach to create the tag structure and graphic (without any process) already can help by reading from the beginning the information that the manufacturer deems useful for the process.