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.
Decision guide
| System domain | Typical responsibility | Boundary evidence |
|---|---|---|
| SCADA and control | Live status, supervisory commands, alarms, operator context and short-horizon process history | Tag ownership, command authority, update rate and degraded-mode test |
| MES/MOM | Dispatch, execution state, genealogy, quality, labor context and production performance | Object model, event lifecycle, exception and reconciliation rules |
| ERP | Orders, material planning, purchasing, inventory value, costing and financial commitments | Master-data authority, transaction states and posting controls |
| Integration | Translate identifiers and transport governed messages without becoming an accidental source of truth | Interface contract, queue behavior, idempotency, monitoring and replay test |
A practical workflow
- 01
Map business decisions, plant operations, users, equipment, orders, materials, recipes, lots, events and KPIs.
- 02
For each object and field, assign authoritative source, permitted writers, consumers, timestamps, units and retention.
- 03
Define command and event flows, validation, acknowledgement, sequencing, idempotency and correction authority.
- 04
Model outages and recovery: local fallback, buffering, replay, duplicate rejection, reconciliation and escalation.
- 05
Test normal, delayed, duplicated, missing, out-of-order and corrected transactions before approving handover.
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.
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
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.