When someone says "we want the PLC to talk to the ERP", they rarely need a direct connection: they need a model. ISA-95 (published as the international standard IEC 62264) has been solving this problem for more than twenty years and is still the most useful reference for not improvising an industrial data architecture.

The levels of the model

ISA-95 builds on the Purdue reference model and organises the plant into levels, each with its own function and time horizon:

  • Level 0 — Physical process: sensors and actuators.
  • Level 1 — Sensing and manipulation: PLCs, robot controllers, drives. Milliseconds.
  • Level 2 — Supervision: SCADA and HMI. Seconds to minutes: visualisation, alarms, recipes.
  • Level 3 — Manufacturing operations (MES/MOM): hours and shifts. Work orders, traceability, OEE, quality.
  • Level 4 — Business planning (ERP): days and months. Purchasing, sales, planning, costs.

The value of ISA-95 is not drawing the layers but defining what information crosses from one to another: orders go down, production results go up, and each system does its job without invading its neighbour’s.

Mistake 1: connecting everything to everything

The temptation of "total connectivity": every PLC with its own client talking to the ERP, every machine with its own export-to-Excel script. Two years later you have a tangle of point-to-point integrations that nobody documented and that break in a chain every time a software version changes at either end.

If you are not sure what role the PLC plays in this stack, start with What is a PLC and what is it used for?

Mistake 2: connecting nothing

The opposite mistake, just as expensive but less visible: paper records, manual spreadsheets and an isolated SCADA with no central history. The cost does not appear on any integration invoice; it appears in the days lost preparing an IFS or BRCGS audit, rebuilding by hand data scattered across half a dozen systems.

Which protocol to use at each level

There is no single "right" protocol for the whole stack. Each layer has its tool:

  • Level 1 ↔ level 2: PROFINET, EtherNet/IP or Modbus TCP, fieldbus protocols built for real time.
  • Level 2 ↔ level 3: OPC UA is the de facto standard: structured information model, built-in security and vendor independence.
  • Level 3 ↔ level 4: APIs or the ERP’s own connectors. Here the language is business: orders, batches, consumption, costs.
  • Telemetry from distributed sites: MQTT, for its lightness and tolerance of intermittent connections; a common pattern in aquaculture, pumping stations or remote installations.

Newer architectures such as the Unified Namespace, usually built on MQTT, do not replace ISA-95: they use it to organise data hierarchically.

A sensible architecture, layer by layer

In a typical food traceability project, a sensible architecture would be: the PLC (for example an S7-1500) controls the machine in real time; the SCADA (WinCC Unified or Ignition) centralises recipes and alarms and captures production events; an OPC UA server exposes that data in a structured way; a SQL Server database stores batch, temperatures, operator and time; and a scheduled integration, not a direct cable, synchronises work orders from the ERP and sends results back.

Each layer can fail, be updated or be replaced without bringing down the others, which is exactly what does not happen with point-to-point integration.

If the cell has safety functions, their status (emergency stop pressed, door open) can be published upwards for diagnostics. The safety logic, however, always stays at control level.

When do you need an MES?

Not every plant needs a full MES. If there are few orders a day and the SCADA already centralises traceability and history, that may be enough. A dedicated MES starts to make sense when several lines compete for the same resources, detailed production scheduling is needed, or in-line quality control must block batches automatically.

Frequently asked questions

Can the PLC write directly into the ERP?

Technically yes, but it is not advisable. It skips the layer that gives the data context (batch, order, shift) and creates a fragile dependency: if the ERP changes, the PLC program has to change too.

OPC UA or MQTT to send plant data upwards?

OPC UA for structured exchange inside the plant (levels 2 and 3). MQTT for lightweight telemetry to the cloud or from remote sites with intermittent connectivity. In large projects both coexist, each in its own layer.

Do I need an MES if I already have SCADA and ERP?

Not always. A well-designed SCADA with history and traceability covers much of level 3 in small plants. It depends on order volume and whether you need detailed production scheduling.

What happens if I do not follow any level model?

In small projects it may go unnoticed. With several lines or plants, the lack of a model produces unmaintainable point-to-point integrations where every change breaks two or three undocumented connections.