Skip to main content
Architecture guideEngineering guidance

The OT-to-AI reference architecture

A practical architecture for moving from plant signals to governed intelligence without bypassing industrial security, context or human control.

Talk to an engineer
The OT-to-AI reference architecture
Delfers PlatformsReference ArchitectureReviewed Jul 29, 2026

Industrial AI architecture should begin at the physical process and move outward through controlled layers. This guide outlines the responsibilities of the field, edge, context, intelligence and enterprise planes, and shows where governance belongs.

Layer 1: field and control

PLCs, DCS, instruments, cameras, drives and protection systems remain responsible for deterministic control and safe operation. AI should not create an uncontrolled path around these systems.

Connectivity begins with an explicit inventory of protocols, data owners, update rates and criticality.

Layer 2: edge acquisition and local intelligence

The edge acquires plant data, normalises protocols, buffers during network loss and runs time-sensitive inference. It is also the right place for local data-quality checks, site rules and production-line integration.

SensX and VisionX operate close to the process when sensing, visual inference or local workflow requires predictable response.

Layer 3: operational context

Raw tags become useful when they are connected to assets, process stages, products, work orders, events and operating limits. This layer should expose data quality and uncertainty rather than hide them.

Cortex provides living operational models, while SensX models assets and sensing states across sites.

Layer 4: intelligence and governed action

Advanced analytics and agentic AI use the contextual layer to identify patterns, evaluate scenarios and recommend action. Findings should cite their evidence and pass through human approval where the consequence demands it.

Sentrix is designed around cited, advisory intelligence, and Cortex supports bounded, approved operational steering.

A scalable architecture does not connect AI directly to every signal. It creates clear responsibilities, boundaries and evidence across the path from signal to decision.
Technical references

Standards and primary sources used for context.

These links provide technical context. Their inclusion does not claim product certification or compliance unless explicitly stated elsewhere.

  1. ISA-95 enterprise-control system integrationInternational Society of AutomationModels and terminology for integrating enterprise and control systems.
  2. OPC UA specificationsOPC FoundationOfficial published OPC UA specifications and companion information models.
  3. Sparkplug Specification 3.0Eclipse FoundationOfficial Sparkplug specification for MQTT-based industrial data integration.
  4. ISA/IEC 62443 seriesInternational Society of AutomationCybersecurity requirements and processes for industrial automation and control systems.