Skip to content

Modular Automation Standards

Process plants are moving from monolithic DCS installations toward modular automation: skids and process equipment arrive pre-engineered with their own control logic, advertise their services through a typed interface, and are orchestrated by a plant-level layer that does not need to know the internals of each module. A parallel push from NAMUR (Open Architecture, NOA) separates the safety- and quality-critical core control path from a richer monitoring and optimization data flow that can be consumed by cloud, MES, and analytics workloads without touching the regulated control loop.

Cloud-Native DCS is designed to sit at the orchestrator layer of this emerging stack. This section summarizes the relevant standards and states our current adherence posture on each.

Standards covered

Standard Scope Page
VDI/VDE/NAMUR 2658 — Module Type Package (MTP) Service-based modular automation; vendor-neutral package format describing a Process Equipment Assembly MTP
IEC 63280 International rollup of MTP, harmonizing VDI/VDE/NAMUR 2658 with the IEC catalog IEC 63280
NAMUR NE 148 Automation requirements for the modular orchestrator and the module-orchestrator interface NAMUR NE 148
NAMUR NE 175 (NOA) NAMUR Open Architecture — data flow between core control and a parallel monitoring and optimization plane NAMUR NE 175 (NOA)

Where Cloud-Native DCS fits

Read top to bottom. This is the role we play in a modular plant.

A NAMUR NE 148 / IEC 63280 orchestrator consuming PA-DIM-modeled devices and MTP-packaged modules via OPC UA, with a NAMUR NE 175 (NOA)-style monitoring and optimization data flow alongside the core control path.

In practical terms:

  • Orchestrator. The control system runs the plant-level procedure (ISA-88 recipes, batches, units) and invokes module services. It does not impose internal control logic on a module that already brings its own.
  • Module interface is service-based. Each module exposes its capabilities as named services with parameters, states, and a defined state machine, compatible with the MTP ModuleTypePackage / ModuleService model and with NAMUR NE 148 §4 orchestrator requirements.
  • Device model is OPC UA companion-spec-aligned. Smart instruments bind through Unit.spec.serviceBinding (see ADR-0001) and resolve against PA-DIM, OPC 40080, OPC 40223, and similar companion specifications. Raw register addresses never enter that resolution.
  • Two data planes. The core control loop (gateway + operators + unit runtimes) carries the regulated commands and feedback. A parallel monitoring plane (historian, MQTT telemetry, data interface, audit trail) carries everything else. That is the topology NAMUR NE 175 calls a "monitoring and optimization" channel that runs outside the protected control path.

Adherence posture, at a glance

Standard Posture Summary
VDI/VDE/NAMUR 2658 (MTP) Aligned, package import implemented Architecture matches the MTP service/state model, and a vendor's MTP package imports natively. The Part 5.1 runtime binding, MTP export and certification are not implemented, and no round trip against a vendor PEA has been run.
IEC 63280 Aligned Tracks MTP — see MTP posture.
NAMUR NE 148 Substantially Aligned The DCS plays the orchestrator role NE 148 describes; module-side requirements depend on the integrating party.
NAMUR NE 175 (NOA) Substantially Aligned Core control and monitoring/optimization channels are already physically separated by component; formal NOA verification information model is on the roadmap.

Per-clause detail lives in the individual pages.

Why this matters for pharma orchestration

Pharma plants are moving toward modular trains (skids for buffer prep, CMC analysis, fill/finish, and continuous bioprocessing), and the procurement story increasingly requires the master control system to consume vendor modules through a standardized interface, sparing the re-engineering of each one. Aligning with MTP / IEC 63280 / NE 148 means a customer can specify a module from any vendor that ships an MTP package and expect Cloud-Native DCS to orchestrate it without bespoke integration work. Aligning with NOA means the same plant can feed high-volume telemetry to a cloud analytics or PAT workload without expanding the qualified, validated control footprint.

  • ADR-0001 (Asset dissolution) — why smart devices and OPC UA companion specifications bind to the ISA-88 hierarchy through Unit.spec.serviceBinding, and why no dedicated device CRD exists.
  • SCADA Integration — the REST, WebSocket, and SSE surfaces a supervisory system or NOA monitoring consumer can call against the gateway.
  • Compliance Traceability Index — formal requirements-to-implementation matrices for ISA-88, ISA-95, IEC 62443, 21 CFR Part 11, and adjacent standards.
  • MES Integration — Level 3 / Level 4 data flow over the B2MML-capable REST API.