Glossary · Data, timing and communication
NAMUR Open Architecture (NOA)
Also known as: NOA
German: NOA (NAMUR Open Architecture)
In process automation, the NAMUR Open Architecture (NOA) is a concept that adds a second, open communication channel to the existing core process control, so that field and plant data can be used for monitoring and optimization without compromising the availability and safety of the core automation.
- Data and interfaces
- Integrated systems
In one sentence
NOA adds a second, open data channel beside the core process control so plant data can be used for monitoring and optimization.
Example
Diagnostic data from HART devices is read via the NOA channel into a monitoring app, while the control system continues to run unchanged.
How it applies
- Engineering: NOA, described in NAMUR NE 175 and related recommendations, uses OPC UA information models; write access back into the core process control is restricted and must pass an explicit verification of request.
- Security: The one-way data flow by default helps protect the core process control, but still needs a security design along Zones and conduits.
- Documentation: Documentation should state which data a device or system exposes via NOA and whether any write-back is possible; the documentation team should keep data point lists consistent with the information model.
NOA vs. MTP
NOA opens data access for monitoring and optimization of existing plants. The Module Type Package (see ZVEI guide to Module Type Package (MTP)) describes process modules for integration into an orchestration layer in modular plants.