SCADA, MES and ERP Integration with ISA-95

SCADA, MES and ERP Integration with ISA-95

Modern plants rarely fail because they lack data; they fail because data is trapped in silos. SCADA systems excel at real-time monitoring and control, MES platforms manage production execution, and ERP systems handle planning, finance, and supply chain. The engineering challenge is not simply connecting these layers, but doing so in a way that preserves timing, data integrity, cybersecurity, and operational responsibility. ISA-95 provides the common language for this integration, helping engineers define what data moves, when it moves, and which system owns it.

Why ISA-95 Matters in SCADA Integration

ISA-95, formally aligned with IEC 62264, defines a functional model for enterprise-control system integration. Its main value is that it separates responsibilities across levels: Level 0-2 for sensing, control, and SCADA; Level 3 for MES; and Level 4 for ERP. This prevents the common anti-pattern of forcing ERP to make millisecond decisions or using SCADA as a production historian without governance.

In practice, ISA-95 helps answer questions such as:

• Which production events belong in SCADA versus MES?
• How should work orders be translated into executable operations?
• What master data should be shared across systems?
• How do we maintain traceability from order to batch to equipment to alarm?

For European projects, ISA-95 also supports clean integration with compliance obligations. Cybersecurity requirements under IEC 62443 and the EU NIS2 Directive are easier to implement when interfaces are well-scoped and segmented. Similarly, machine and process documentation under the EU Machinery framework is more defensible when the control architecture is explicit and auditable.

ISA-95 Functional Layers and System Roles

Although site architectures vary, the practical division of labor is usually as follows:

• SCADA: real-time supervision, alarms, trends, HMI, telemetry, basic sequencing, and operator actions.
• MES: dispatching, production scheduling, genealogy, quality enforcement, material consumption, WIP tracking, and electronic batch records.
• ERP: demand planning, inventory, finance, purchasing, master business orders, and cost accounting.

ISA-95 does not mandate a vendor stack. It standardizes the information model so that a work order, for example, can be represented consistently regardless of whether the plant uses Siemens, Rockwell, Schneider, Ignition, SAP, Oracle, or a custom MES.

Typical Data Boundaries

• ERP to MES: production orders, due dates, routing, material reservations, target quantities.
• MES to SCADA: dispatch instructions, setpoint targets, recipe selection, equipment state requests, operator prompts.
• SCADA to MES: actual counts, alarms, equipment states, timestamps, quality measurements, consumption events.
• MES to ERP: completed quantities, scrap, inventory movements, labor confirmations, order closeout.

Integration Architecture Patterns

Three integration patterns dominate industrial projects.

1. Point-to-Point Integration

ERP talks directly to MES, MES talks directly to SCADA, and sometimes ERP also talks to SCADA. This is simple at first, but it scales poorly. Every added interface increases testing effort, version coupling, and failure modes.

2. Hub-and-Spoke Integration

An integration layer or middleware platform brokers messages between systems. This is better for governance, transformation, and monitoring. It is especially useful when multiple plants or multiple ERP instances must be harmonized.

3. ISA-95 Object Model with Event-Driven Messaging

This is the most robust approach for complex plants. Master data and production events are modeled explicitly and exchanged using APIs, queues, or publish/subscribe mechanisms. The result is better traceability and easier change management.

From a cybersecurity perspective, this approach aligns well with IEC 62443 zoning and conduits concepts, because interfaces can be segmented by trust level and function. It also supports the principle of least functionality and least privilege expected in NIS2-oriented security programs.

What Data Should Be Shared?

A common engineering mistake is over-sharing. Not every tag in SCADA belongs in MES, and not every business attribute in ERP belongs in the control network. ISA-95 encourages a minimal, purpose-driven data model.

Data Category	Typical Source	Typical Consumer	Notes
Work order ID	ERP	MES	Business identifier; not a control tag
Operation status	SCADA	MES	Running, stopped, faulted, idle
Equipment state	PLC/SCADA	MES	Should be normalized to ISA-95 states where possible
Actual production count	SCADA	MES/ERP	Usually aggregated before ERP posting
Material consumption	MES or SCADA	ERP	Often batch- or lot-based
Alarm history	SCADA	MES	Usually for context, not direct ERP posting

In most plants, the best practice is to let SCADA own real-time state, MES own production context, and ERP own commercial truth. When ownership is blurred, reconciliation problems multiply.

Worked Example: Packaging Line Integration

Consider a packaging line producing 12,000 bottles per hour with three shifts per day. The ERP system releases a daily order for 90,000 bottles. MES breaks this into three 30,000-bottle dispatches, and SCADA provides real-time counts and downtime events.

Assume the line runs at a nominal speed of 200 bottles per minute:

$$200 \times 60 = 12{,}000 \text{ bottles/hour}$$

For a 30,000-bottle order, the ideal runtime is:

$$\frac{30{,}000}{12{,}000} = 2.5 \text{ hours}$$

Now assume the line experiences 18 minutes of unplanned downtime and 12 minutes of micro-stops during that dispatch. The effective runtime becomes:

$$2.5 + \frac{18 + 12}{60} = 2.5 + 0.5 = 3.0 \text{ hours}$$

The actual hourly throughput is then:

$$\frac{30{,}000}{3.0} = 10{,}000 \text{ bottles/hour}$$

MES can calculate performance loss and publish a production confirmation to ERP at order closeout. If the plant targets 98% yield and actual good output is 29,400 bottles, then scrap is 600 bottles:

$$\text{Yield} = \frac{29{,}400}{30{,}000} \times 100 = 98\%$$

That 600-bottle scrap quantity should not be inferred loosely from a single SCADA counter. It should be reconciled from validated production events, rejects, and operator confirmations in MES before posting to ERP inventory and costing.

For timing, suppose SCADA publishes counts every 5 seconds, MES aggregates every 1 minute, and ERP receives only order-level confirmations. This layered cadence reduces network load and business-system churn while preserving operational detail where it matters.

Decision Matrix: Which System Owns Which Function?

Function	SCADA	MES	ERP	Preferred Owner
Real-time interlocks	Yes	No	No	SCADA/PLC
Alarm management	Yes	Context only	No	SCADA
Work order dispatch	Limited	Yes	Source	MES
Production scheduling	No	Yes	Master planning	ERP + MES
Genealogy and traceability	Partial	Yes	No	MES
Financial valuation	No	Inputs only	Yes	ERP
OEE calculation	Data source	Yes	No	MES

Engineering Standards and Clause-Level References

For industrial automation projects in Europe, the following standards are especially relevant:

• IEC 62264 / EN IEC 62264: enterprise-control system integration and object models for manufacturing operations management.
• ISA-95: the underlying functional model widely used in practice, especially Parts 1 and 2 for models and object characteristics.
• IEC 62443-3-2: security risk assessment and system design for industrial automation and control systems.
• IEC 62443-3-3: system security requirements and security levels.
• IEC 61131-3: PLC programming languages relevant when SCADA/MES integration depends on control tags and state machines.
• EN 60204-1: electrical equipment of machines, relevant when integration affects operator interfaces, stop categories, and machine control circuits.
• NFPA 79: electrical standard for industrial machinery, often used in multinational projects alongside IEC-based design.

From a compliance standpoint, clause-level attention should focus on interface control, cybersecurity zoning, alarm rationalization, and data integrity. IEC 62443-3-3 requirements on identification and authentication, use control, system integrity, and data confidentiality become highly relevant when MES or ERP exchanges cross the OT/IT boundary. For machine-related systems, EN 60204-1 and IEC 60204-1 require that control functions remain safe and predictable even if higher-level systems fail or disconnect.

In alarm design, SCADA should follow good engineering practice such as ISA 18.2 principles for alarm management and rationalization. While ISA 18.2 is not an IEC standard, it is widely adopted in process industries and helps prevent MES or ERP from becoming a secondary alarm sink for nuisance events.

Implementation Best Practices

• Define a single source of truth for each master data object.
• Normalize equipment states before exposing them to MES.
• Use event timestamps in UTC and define timezone handling explicitly.
• Separate production events from telemetry floods.
• Use buffered messaging so that temporary network loss does not corrupt order history.
• Validate order completion rules before posting to ERP.
• Document interface ownership, retry logic, and error handling.
• Apply IEC 62443 zoning and conduits to all SCADA-MES-ERP pathways.

Architecturally, the most resilient systems use asynchronous messaging for production events and synchronous APIs only for bounded queries such as “what is the current order?” or “what recipe version is approved?”. This reduces coupling and makes failure recovery much easier.

Common Failure Modes

Integration projects usually fail for one of four reasons:

1. Semantic mismatch: the ERP “quantity” does not mean the same thing as the MES “quantity.”
2. Temporal mismatch: SCADA data arrives every second, but ERP expects batch postings once per order.
3. Ownership confusion: multiple systems edit the same production record.
4. Cybersecurity neglect: direct trust between business IT and OT creates avoidable risk.

The cure is disciplined scope control. Use ISA-95 to define the business object model, IEC 62443 to define trust boundaries, and a formal master data governance process to prevent uncontrolled change.

Conclusion

SCADA, MES, and ERP integration is not just a software exercise; it is an industrial architecture decision that affects throughput, traceability, compliance, and cybersecurity. ISA-95 gives engineers a practical framework to decide what belongs at each layer and how data should move across the enterprise-control boundary. The most common mistakes are over-connecting systems, letting ERP reach into real-time control, ignoring data ownership, and treating cybersecurity as an afterthought. To avoid these failures, define clear functional boundaries, use standardized object models, validate event timing, and design interfaces with IEC 62443 and IEC/EN compliance in mind from the start.