ISA-95 Levels OT to ERP: How Industrial Data Flows from PLC to Enterprise Systems

The ISA-95 levels OT to ERP framework defines exactly how manufacturing data should travel from the shop floor — sensors, PLCs, and RTUs — all the way up to enterprise resource planning systems like SAP. Understanding this model is not just an academic exercise; it is the foundation for building modern, scalable, and secure industrial architectures that connect operational technology with business intelligence. In factories and plants across oil and gas, pharmaceutical, renewable energy, and food and beverage industries, mastering ISA-95 is the difference between fragmented data islands and a unified, AI-ready industrial enterprise.

What Is ISA-95 and Why Does It Still Matter?

ISA-95 — formally known as ANSI/ISA-95, the international standard for integrating enterprise and control systems — was developed to give manufacturers a common language and architecture for connecting operational and business systems. It defines five functional levels (0 through 4), each representing a distinct layer of an industrial organization, from physical processes to enterprise planning.

Despite being decades old, ISA-95 remains deeply relevant today. The rise of Industrial IoT, cloud computing, and AI has not replaced this model — it has amplified the need for it. When a Siemens S7-1500 PLC running a production line needs to send quality data to an SAP ERP module, or when a Rockwell Automation ControlLogix system must report OEE metrics to a Power BI dashboard, the question of how data crosses each ISA-95 boundary becomes critical. Modern platforms must navigate all five levels cleanly, securely, and without data loss.

The Five ISA-95 Levels Explained

Level 0 — The Physical Process

Level 0 is where the physical world begins. This layer includes sensors, actuators, valves, flow meters, pressure transmitters, and any device that directly interacts with the industrial process. In a refinery, this means temperature sensors on distillation columns. In a pharmaceutical plant, it means flow meters from Endress+Hauser measuring API (active pharmaceutical ingredient) dosing. In a wind farm, it includes anemometers and pitch actuators on individual turbines.

Data at this level is raw, high-frequency, and analog or digital signal-based. It does not yet carry context or business meaning. Its value is entirely realized when it moves upward through the ISA-95 stack.

Level 1 — Sensing and Manipulation

Level 1 is occupied by PLCs (Programmable Logic Controllers), RTUs (Remote Terminal Units), and DCS (Distributed Control Systems). Devices like Siemens S7-300/400/1200/1500, Rockwell Automation Allen-Bradley PLCs, and Schneider Electric Modicon systems live here. These controllers read signals from Level 0 sensors, execute control logic, and drive actuators in real time, typically in scan cycles of milliseconds.

At Level 1, protocols such as Modbus RTU/TCP, Profinet, EtherNet/IP, and IEC 60870-5-104 are dominant. Data exists in registers, coils, and tags — structured for machine control, not yet for enterprise consumption. This is the ground floor of the ISA-95 levels OT to ERP journey.

Level 2 — Supervisory Control

Level 2 houses SCADA systems, HMIs (Human-Machine Interfaces), and distributed control consoles. This is where operators interact with the process in real time. Systems like Wonderware, atvise, and ABB Ability Symphony+ operate at this level, aggregating data from multiple Level 1 controllers and providing visualization and alarm management.

The challenge at Level 2 is that SCADA systems are often siloed — optimized for real-time process visibility, not for pushing data upward to MES or ERP systems. Bridging from Level 2 to Level 3 requires an integration layer that can handle multi-protocol translation, buffering, and structured data delivery without disrupting real-time control operations.

Level 3 — Manufacturing Operations Management (MES)

Level 3 is the domain of Manufacturing Execution Systems (MES), production scheduling, quality management, and plant-level data historians. This is where production orders meet real-time execution, where batch records are validated in pharmaceutical environments under FDA 21 CFR Part 11, and where OEE metrics are calculated from machine uptime data.

At this level, OPC UA — the OPC Foundation’s Unified Architecture standard — has emerged as the dominant interoperability protocol. It provides secure, structured, and semantically rich data exchange between plant-floor systems and MES platforms. Time-series historians, SQL databases, and REST APIs also play a critical role in making Level 3 data available for analysis and reporting.

In mining and oil and gas environments, Level 3 may also include centralized remote monitoring centers that aggregate data from geographically distributed assets — offshore platforms, pump stations, or mine sites — before forwarding consolidated operational intelligence to enterprise systems.

Level 4 — Enterprise Resource Planning (ERP)

Level 4 is where business systems live: SAP ERP, Oracle, Microsoft Dynamics, CMMS platforms, financial systems, and supply chain management tools. At this level, data must be clean, contextualized, and reliable. A procurement manager at a food and beverage company does not need raw PLC register values — they need structured production quantities, material consumption figures, and quality certifications derived from those values.

The gap between Level 3 and Level 4 is historically one of the most difficult integrations in industrial automation. ERP systems speak REST APIs, SQL, and web services. PLCs speak Modbus and Profinet. Bridging this gap without a proper integration layer typically means months of custom middleware development, fragile point-to-point connections, and ongoing maintenance nightmares. This is precisely where understanding the full ISA-95 levels OT to ERP flow becomes commercially decisive.

Where Cloud, IIoT, and AI Fit: The Extended ISA-95 Model

Modern industrial architectures have extended the original ISA-95 model to include cloud platforms, IIoT hubs, and AI/ML systems above Level 4 — sometimes referred to as Level 5. AWS IoT, Azure IoT Hub, and Google Cloud IoT receive structured industrial data from plant-floor systems. AI models running on these platforms can detect anomalies, predict failures, and optimize energy consumption — but only if the data flowing from Levels 0 through 4 is reliable, structured, and continuous.

The ISA-95 levels OT to ERP framework therefore now encompasses not just the traditional enterprise boundary but also the edge-to-cloud continuum. An industrial data platform operating across all levels must support protocols like MQTT with Sparkplug B — the lightweight messaging protocol standard optimized for constrained IIoT environments — alongside traditional OPC UA and SQL-based integrations.

The Industrial DMZ: Cybersecurity at the ISA-95 Boundary

One of the most important architectural considerations when traversing ISA-95 levels OT to ERP is cybersecurity. The boundary between Level 3 (OT) and Level 4 (IT/enterprise) is where the attack surface is most exposed. Frameworks like ISA/IEC 62443 define zones and conduits — controlled communication paths between network segments — that govern how data crosses this boundary.

A properly designed industrial DMZ at the Level 3.5 boundary should enforce several principles:

1. Data flows should be initiated from the OT side (reverse connection), preventing inbound access from IT networks into control systems.
2. Only necessary data should cross the boundary — not raw PLC memory maps, but structured, filtered, and contextualized datasets.
3. One-way data flows (data diode architectures) should be considered for critical infrastructure segments, such as power substations and oil and gas facilities operating under NERC CIP requirements.
4. All data transfers should be logged and auditable, supporting incident evidence requirements under frameworks like NIS2 and NIST CSF.

Ignoring cybersecurity at this boundary — relying instead on direct database connections or OPC DA tunnels between OT and ERP — is a configuration that regulators, insurers, and industrial cybersecurity auditors increasingly flag as unacceptable risk.

Common Integration Challenges Across ISA-95 Levels OT to ERP

Even with a clear architectural model, organizations implementing ISA-95 levels OT to ERP connectivity face practical challenges that slow projects and increase costs:

1. Protocol fragmentation: A single plant may have Siemens S7 controllers, Schneider Modicon RTUs, ABB DCS systems, and Endress+Hauser field instruments — each speaking different protocols requiring different drivers and configurations.
2. Tag licensing costs: Legacy integration platforms charge per data point (tag), making full plant connectivity economically prohibitive for large installations with tens of thousands of variables.
3. Data loss during network disruptions: Without buffering mechanisms, connectivity interruptions between plant and enterprise systems result in permanent data gaps — a critical problem in regulated industries like pharmaceutical and oil and gas.
4. Lack of data context: Raw PLC values without engineering units, timestamps, and quality codes are not directly consumable by ERP or analytics systems.
5. Custom coding overhead: Traditional middleware approaches require significant software development effort, creating fragile integrations that are difficult to maintain as systems evolve.
6. Security gaps: Point-to-point OT-to-ERP connections that bypass proper DMZ architecture expose critical control systems to IT network threats.

How vNode Solves This

The vNode Industrial Data Platform was purpose-built to address every layer of the ISA-95 levels OT to ERP architecture — from PLC data acquisition at Level 1 to SAP/ERP and cloud delivery at Levels 4 and 5 — without custom coding and without per-tag licensing limitations.

Here is how vNode addresses each critical challenge across the ISA-95 stack:

1. Universal protocol support across all levels: vNode connects natively to Siemens S7-300/400/1200/1500, Rockwell EtherNet/IP, Schneider Modicon via Modbus TCP/RTU, ABB systems, Endress+Hauser instruments, OPC UA/DA servers, DNP3, IEC 60870-5-104, IEC 61850, BACnet, SNMP, REST APIs, and SQL/ODBC databases — covering every level of the ISA-95 model with a single platform.
2. Unlimited tags — no per-tag licensing: Unlike competitors that charge per data point, vNode imposes no tag-based licensing restrictions. A Minera México mining operation can connect hundreds of thousands of process variables without cost penalties.
3. Store and Forward — zero data loss: vNode’s built-in Store and Forward capability buffers data locally during network disruptions and automatically forwards it when connectivity is restored. For Pemex or Ecopetrol remote facilities with intermittent WAN links, this guarantees data continuity across the entire ISA-95 levels OT to ERP path.
4. Cybersecurity-ready DMZ architecture: vNode deploys natively at the Level 3.5 Industrial DMZ, supporting reverse connection, data diode-compatible architectures, role-based access control (RBAC), and zone/conduit designs aligned with ISA/IEC 62443 — protecting the OT-to-ERP boundary without sacrificing data availability.
5. No-code configuration: vNode’s web-based configuration interface requires no programming. System integrators — who represent 70% of vNode’s customer base — can deploy and configure complete ISA-95-spanning architectures significantly faster than traditional custom middleware approaches, improving project margins and delivery timelines.
6. MES, ERP, and cloud delivery: vNode delivers structured industrial data to SQL databases (MySQL, SQL Server, Oracle, PostgreSQL), OSIsoft PI historians, SAP/ERP systems via REST API, AWS IoT, Azure IoT Hub, Google Cloud IoT, Power BI, and AI/ML platforms — covering the full enterprise and cloud layer of the ISA-95 model.
7. AI-ready data pipeline: With the vNode MCP Server module, structured industrial data from any level of the ISA-95 hierarchy becomes directly available to LLM-based AI tools and industrial copilots, enabling predictive maintenance, anomaly detection, and process optimization without additional middleware.
8. Proven at scale: National Oilwell Varco (NOV) deployed vNode to integrate a hydraulic model with Siemens PLC-based systems for real-time well drilling optimization — a direct ISA-95 Level 1-to-Level 4 integration. Infinity Power connected the Taiba N’Diaye Wind Power Station in Senegal to its UK Control Center using IEC 60870-5-104, TLS encryption, and MySQL — spanning ISA-95 Levels 2 through 4 across continents.

To explore how vNode can bridge your plant-floor systems with enterprise and cloud applications, contact the vNode team or consult the vNode technical documentation for detailed module and protocol configuration guides.

Frequently Asked Questions

What are the ISA-95 levels and how do they relate to OT-to-ERP data integration?

ISA-95 defines five levels (0–4) ranging from physical sensors and actuators at Level 0, through PLCs and SCADA at Levels 1–2, manufacturing operations and MES at Level 3, and enterprise ERP systems at Level 4. Understanding the ISA-95 levels OT to ERP model is essential for designing integrations that move operational data securely and reliably from control systems to business applications.

Why is the ISA-95 Level 3 to Level 4 boundary so difficult to integrate?

The Level 3 to Level 4 boundary separates OT networks (running industrial protocols like OPC UA, Modbus, and DNP3) from IT networks (using REST APIs, SQL, and web services), requiring protocol translation, data contextualization, and cybersecurity controls simultaneously. Without a dedicated integration platform, this boundary typically requires custom middleware development that is expensive to build and fragile to maintain.

How does vNode support ISA/IEC 62443 compliance at the OT-to-IT boundary?

vNode supports ISA/IEC 62443-aligned architectures by enabling Industrial DMZ deployment at Level 3.5, enforcing controlled data flows through reverse connection and data diode-compatible configurations, and providing RBAC, audit logs, and network segmentation support. This makes vNode a strong enabler of compliance-oriented OT-to-ERP architectures without replacing dedicated security tools like firewalls or SIEM systems.

Can vNode connect legacy PLCs at ISA-95 Levels 1–2 directly to cloud or ERP systems at Levels 4–5?

Yes. vNode supports a wide range of legacy and modern industrial protocols — including Siemens S7, Modbus TCP/RTU, EtherNet/IP, DNP3, and OPC DA — and can deliver that data directly to SQL databases, REST APIs, SAP ERP, AWS IoT, Azure IoT Hub, and AI platforms. The entire ISA-95 levels OT to ERP path can be covered by a single vNode deployment, with Store and Forward ensuring zero data loss across the full integration chain.