PNO MTP 2.0 Specification¶

The PNO MTP 2.0 document series "specifies general concepts for the automated integration of intelligent equipment, called Process Equipment Assemblies (PEAs), in higher-level automation systems, called Process Orchestration Layers (POL) and provides the basic definitions for the specification of interfaces, information models and workflows. The term of “process” in Process Equipment Assembly and Process Orchestration Layer refers to all kind of processes independent of any concrete industry, e.g., process, logistics or manufacturing industry." (PNO MTP Part1)

Part 1 : General Concepts, Interfaces and Models¶

Part 1 specifies the basic conceptual elements.
See Part1 for an overview on the concepts and links to the codebase.

Part 2 : Process Displays¶

Part 2 specifies the concepts and model elements, which are necessary to monitor and control PEAs from the central HMI system within the POL.
Not implemented.

Part 3 : Base Interfaces¶

Part 3 specifies basic functions and the definition of the DataAssembly the base class for all the derived classes in the other parts.
See Part3 for an overview on the concepts, their implementation status in MTPPY2.0 and links to the codebase.

Part 4 : Automation Services and Process Values¶

Part 4 introduces [Services] and concepts for process value interconnections. See Part4 for an overview on the concepts, their implementation status in MTPPy2.0 and links to the codebase.

Part 5 : Runtime and Communication¶

Part 5.1 : Open Platform Communications - Unified Architecture¶

MTPPy 2.0 implements a PEA-hosted OPC UA server and contains a standalone OPC UA client helper for checking configured nodes. The initial Part 6 alarm path neither adds nor uses that client and provides no external-device runtime integration. See Part5 for the current boundary and the communication decisions required before future Managed Part 6 alarms.

Part 6 : Alarms and Events¶

Part 6 specifies i) a base profile with a POL-centric event and alarm mechanism and ii) an extended profile for PEA-managed alarms. MTPPy 2.0 implements an initial static subset of AlarmSet.Base. See Part6 for the exact API and CAEX mapping, verification boundary, limitations, and open TODOs. PEA-managed alarms and events are not implemented.