Engineering & Industry 4 min readORG-F19

MES vs SCADA vs ERP: Draw the ISA-95 Boundary and Assign Data Ownership

Share

SCADA supervises process operation, MES coordinates production execution, and ERP plans enterprise resources and commercial commitments. Real systems overlap, so a reliable architecture assigns one authoritative owner for each business object, command, timestamp, state transition, and correction workflow.

The short answer

Use ISA-95 as a conversation framework rather than a product-label rule. Keep deterministic control and immediate process supervision near equipment; coordinate dispatch, genealogy, quality and production performance in manufacturing operations; keep orders, inventory valuation, procurement and finance in enterprise systems. For every exchanged object, name the system of record, allowed producer and consumer, units, identity, event time, correction authority, latency, outage behavior and reconciliation owner.

  • Assign ownership to data objects and transitions, not to vague “levels” or vendor applications.
  • Separate commands, master data, events, measurements and calculated KPIs because their authority differs.
  • Design store-and-forward, duplicate handling, sequence, time quality and reconciliation before integration.
  • Keep local control safe when MES, integration services or ERP are unavailable.
Boundaries become useful when every object has an accountable source of truth.
Text-free ISA-95 boundary diagram connecting control and SCADA, MES operations and ERP planning

Boundaries become useful when every object has an accountable source of truth.

Decision guide

System domainTypical responsibilityBoundary evidence
SCADA and controlLive status, supervisory commands, alarms, operator context and short-horizon process historyTag ownership, command authority, update rate and degraded-mode test
MES/MOMDispatch, execution state, genealogy, quality, labor context and production performanceObject model, event lifecycle, exception and reconciliation rules
ERPOrders, material planning, purchasing, inventory value, costing and financial commitmentsMaster-data authority, transaction states and posting controls
IntegrationTranslate identifiers and transport governed messages without becoming an accidental source of truthInterface contract, queue behavior, idempotency, monitoring and replay test

A practical workflow

  1. 01

    Map business decisions, plant operations, users, equipment, orders, materials, recipes, lots, events and KPIs.

  2. 02

    For each object and field, assign authoritative source, permitted writers, consumers, timestamps, units and retention.

  3. 03

    Define command and event flows, validation, acknowledgement, sequencing, idempotency and correction authority.

  4. 04

    Model outages and recovery: local fallback, buffering, replay, duplicate rejection, reconciliation and escalation.

  5. 05

    Test normal, delayed, duplicated, missing, out-of-order and corrected transactions before approving handover.

Ownership differs for master data, commands, events, measurements and calculated KPIs.
Text-free data ownership matrix for orders, recipes, states, measurements, genealogy and costs

Ownership differs for master data, commands, events, measurements and calculated KPIs.

Evidence and acceptance

Keep the context and object model, ownership matrix, interface contracts, mappings, units, identities, security boundaries, time rules, example payloads, failure modes, queue and replay tests, reconciliations, exceptions, approvals, support ownership and as-built integration versions.

Integration acceptance must include outage and reconciliation behavior.
Text-free integration recovery flow covering buffering, replay, duplicate handling and reconciliation

Integration acceptance must include outage and reconciliation behavior.

Common mistakes

  • Using ISA-95 levels as a rigid network diagram or product procurement list.
  • Letting two systems write the same status without a conflict and correction rule.
  • Calculating the same KPI differently across SCADA, MES and ERP.
  • Assuming reliable connectivity and ignoring delayed, duplicate or reordered messages.
  • Allowing integration middleware to become an undocumented master-data owner.

Engineering and security boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. ISA-95 Standard: Enterprise-Control System IntegrationInternational Society of Automation
  2. IEC 62264-1:2013 Enterprise-control system integrationInternational Electrotechnical Commission

Frequently asked questions

Is SCADA always ISA-95 level 2 and MES level 3?

Those are useful functional groupings, but real products overlap. Define actual responsibilities and interfaces instead of relying on labels.

Which system owns production quantities?

The answer depends on the event lifecycle. Define the raw equipment event, confirmed execution quantity and financially posted quantity separately.

Can ERP send commands directly to a PLC?

Direct command paths usually create safety, availability and governance risks. Use an engineered, validated boundary with local authority and fallback.

Does AutoNexit move MES or SCADA data?

No. It records the architecture, mappings, tests and evidence around the selected systems.

Related articles

ORG-F08

What Is a SCADA System? Layers, Components, Data Flow, and Security Boundaries

A SCADA system supervises an industrial process by acquiring data, presenting state, managing alarms and trends, and supporting authorized operator actions. A useful design must show each component, trust boundary, data path, failure mode, and operating responsibility rather than reducing SCADA to a screen or server.

ORG-F15

OPC UA vs MQTT: Which Belongs Where in an Industrial Data Architecture?

OPC UA and MQTT solve different parts of an industrial information problem. OPC UA defines interoperable services, information models, security, and client-server or PubSub behavior; MQTT is a lightweight publish-subscribe transport through a broker. Many architectures use both, but only when semantics, topic governance, security, quality, and ownership are explicit.