NAMUR Open Architecture (NOA) - Innovation and integration in process automation
NOA, the NAMUR Open Architecture is a concept for industrial automation, providing secure access to process data for monitoring and optimization without interfering with the core control system. Access to data closest to the process is key when applying AI based data analytics to improve plant efficiency. PA-DIM is the selected information model.
NOA concepts deals with challenge of accessing big data
This creates a fundamental conflict:
AI requires Openness · Data · Agility
Industrial Automation requires Stability · Certification · Control
Challenges and opportunities
Traditional automation systems optimized for the process industry are often monolithic and based on manufacturer-specific technologies. This has several disadvantages:
- Delayed implementation of new technologies.
- Need for costly system modernization.
- High demands on reliability and availability, which make rapid changes difficult.
Traditional process automation systems (DCS/PLC-based):
- Are closed and vendor‑specific
- Prioritize determinism, safety, availability
- Treat data access as a risk, not as an asset
- Are hard to modify once validated
NOA resolves this conflict by architectural separation and decoupling of operational control from data-driven innovation.
Modern IT innovations such as AI, IoT, Industry 4.0, data analytics and cloud computing are developing rapidly and offer immense opportunities to optimize process automation towards lower energy consumption and higher efficiency. However, implementation in "traditional" process automation is lagging behind. Against this backdrop, NOA was developed to enable a structured convergence of IT and OT systems and to utilize the respective advantages.
NOA - NAMUR Open Architecture
Use Cases
The Core concept of NOA
The core concept of NOA is a separation of core process control related communication (sometimes called primary channel) and communication related to monitoring and optimization (sometimes called secondary channel), staring at the interface between field level (level 1) and process control level (level 2). The multi-level model or Perdue Enterprise Reference Architecture has been an established structure for the automation of processes since its publication. It consists of the following levels:
Field level (level 1):
This is where the physical interaction with the process takes place via sensors and actuators.
Process control level (level 2):
This level focuses on stable and reliable automation and plant operation, including the human-machine interface (HMI), taking into account a large amount of data from the field level of strict requirements for real-time capability and system availability.
Operations control level (level 3): This is where the processing of condensed and contextualized information takes place, with real-time requirements in the range of minutes or hours.
Business and logistics systems (level 4):
These include IT systems in which standard, business and logistics processes take place.
NOA Architecture and Data Flow
As technology advances, functions at these levels can be integrated into higher-level systems, especially for smaller systems. Nevertheless, the model remains a highly available and mature automation architecture in operational practice and is not limited to chemical plants.
The main data flow is assumed from field (level 1) to business and logistics system (4) and shall be read-only. Any backflow of data shall be prevented or blocked.
Despite NOA standardization is hosted by PI, it is open for any applicable protocol used for automation and monitoring.
Those protocols have their strengths on efficiency, speed, minimum overhead, real time communication capability, availability/redundancy or functional safety but often miss one or more of three essential capabilities:
- secure communication
- semantics
- route ability
This makes them not well suitable for IT like comms typical on level 3 and 4 and cloud. Protocols supporting all three, such as https or OPC UA miss expectations on the field level or would require performance and memory not available in field instruments.
This led to a dedicated point of translation between automation and semantic protocols from level 1 to level 2 and called NOA Server. NOA defines OPC UA as the protocol for NOA Server and PA-DIM as its information model. On automation systems, following the network centric design principle and with protocols such as PROFINET, data can be read directly from devices via the existing network interface in parallel to the controller to device communication link. For fieldbus systems, such as PROFIBUS or HART, additional gateways might be needed.
The NOA Aggregation Server collects data from NOA Servers across the network and transfers it to a NOA Security Gateway. Security gateway sits between level 2 (core process control) and a DMZ / level 3+. It can be a second path in parallel to the DCS firewall or integrated in same firewall with extensions of its rule set.
Target Group of NOA
Who will benefit most by applying NOA?
NOA is made for operators, aiming to apply IT technology to modernize plants without touching the core process control or minimize the impact at least.
By introducing NOA, the process industry can benefit from the advantages of digitalization and Industry 4.0 without jeopardizing the reliability and stability of established automation systems. NOA thus offers a forward-looking solution to master the challenges of modern process automation while opening up new opportunities for innovation and efficiency. NOA concept is not limited to applications in large chemical plants. The targeted features apply to process automation regardless of its size. Existing concepts typically lag on one or more of the following challenges:
- Being simple and light weight – but suffering on limitations on security.
- Vendor lock in due to very specific hardware and software
- Super complex and time consuming to setup and engineer
Who shall implement NOA in products, solutions and services?
NOA combines the advantages of innovative IT developments with existing OT automation systems. Therefor products and solutions, offering data extraction from automation systems and products, such us PLCs, DCS’, field instruments, analyzers, drives and electrical equipment. Asset information management systems (AIMS), air gap gateways, data collectors, firewalls but also data analytics software and simulation and optimization software.
Applying and installing those products may require installation, engineering, consultancy, support and maintenance. This opens opportunities for engineering companies.
NOA Working Groups
NOA committee coordinates the following joint working groups and is composed by its leads:
JWG 1 – NOA Architecture and Strategy
JWG 1 – NOA Architecture and Strategy
The Joint Working Group NOA Architecture and Strategy defines the core principles and architecture. It is led by Bernd Wansner, ABB and Sten Gruener, ABB.
JWG 2 – NOA Data Aggregation
JWG 2 – NOA Data Aggregation
The Joint Working Group NOA Data Aggregation pursues the following objectives:
- Define support of OPC UA client server infrastructure: Enable NOA OPC UA clients to reach all (decentral) NOA Security Gateways via a single (central) aggregation server in a secure and transparent manner (via the same way as the original NOA Security Gateway) and with no additional mapping effort caused by the aggregation server.
- Define support of (given) broker infrastructure (e.g. MQTT) with lowest possible mapping effort.
- Define harmonized support of SW/FW update processes and NOA Information Models for NOA infrastructure components like security Gateways, Aggregation Server, MQTT Broker …
The JWG NOA Data Aggregation is led by Ralf Huck, self-The Joint Working Group employed consultant.
JWG 3 – NOA Verification of Request
JWG 3 – NOA Verification of Request
The Joint Working Group NOA Verification of Request pursues the following objectives:
- Work is based on the already existing NAMUR recommendation NE 178 Verfification of Request
- Define a system of systems architecture distributed between M+O (Monitoring and Optimization) and CPC (Core Process Control)…
- that implements a sequence of technology-agnostic information processing steps that need to be applied to optimization/change requests so they can safely & securely traverse the IT/OT domain boundaries.
- that offers separation of concern between optimization/change request issuer and plant owner by ensuring request issuers do neither require obtain knowledge of the plants automation specifics.
- Define key technologies, requirements and models for information exchange interfaces between processing steps.
Define compliance profiles and rating criteria to promote interoperability and functional completeness of commercial solutions.
JWG 4 – NOA Security Validation of Concepts
JWG 4 – NOA Security Validation of Concepts
The Joint Working Group NOA Security Validation pursues the following objectives:
- Ensure that all NOA components and interfaces meet robust security standards to protect production data and system integrity.
- Focus on easy implementation and consistent life cycle consideration.
- Leverage concepts from other working groups at user organizations, standards bodies, and other institutions – including the EU – with particular consideration of NAMUR NE177, CRA, and NIS2.
The JWG NOA Security Validation is led by Hermann Berg, Moxa Europe GmbH.
JWG 5 – NOA Implementation
JWG 5 – NOA Implementation
The Joint Working Group NOA Implementation is continuously evaluating requirements, concepts and prototype implementation in the IDEA 4.0 test plant at Bilfinger labs in Industriepark Hoechst, Frankfurt. The JWG is lead by Ronny Becker, Bilfinger and Wilfried Grote, Phoenix Contact.
JWG 6 – NOA Quality
JWG 6 – NOA Quality
The Joint Working Group NOA Quality pursues the following objectives:
- Define requirements to be checked during conformance tests regarding NOA specifications and used security standards
- Initiate, create, review, and maintain Test Specifications
- Prepare the certification process
- Interaction with other SDOs in context of conformance tests
The JWG NOA Quality is led by Matthias Riedl, ifak e.V.
JWG 7 – NOA Marketing
JWG 7 – NOA Marketing
The Joint Working Group NOA Marketing pursues the following objectives:
- Build a marketing strategy ("value proposition”) and continuous check and improvement synchronized with the activities in the technical WGs
- Planning events and exhibitions (national and international) with devices, demonstrators, visuals in close collaboration with PI’s PA-Marketing WG
- Publications (white papers...), presentations and social media (Videos, Interviews, LinkedIn...)
- How to utilize the existing IDEA plant for marketing (remote access, video...)
The JWG NOA Marketing is led by Tilo Merlin, ABB.