Industrial networking and IT/OT service

SCADA, MES and ERP Integration

We identify which system production orders come from and where production quantity and scrap data are generated. We design the interface between MES and ERP together with how it behaves during duplicate records or temporary access outages.

Your situation

What problem does this service solve?

Production quantities in the ERP not matching reality on the shop floor

Quantities entered manually or transferred in bulk at the end of a shift distort inventory, costing and planning. The error is noticed days later.

The idea of a direct connection between PLC and ERP

Opening the control network directly to business systems is both a security and an operational risk. ERP maintenance or an update can stop the line.

Work orders not reaching the line

The plan changes, but the correct recipe and work order do not reach the operator in time.

An interface nobody owns

When the interface fails, it is unclear who will investigate. No message queue, error log or owner has been defined.

Technical framework

What we cover, and within what limits

SCADA and HMI monitor and control the process in near real time. MES manages the execution of production: work orders, traceability, quality, downtime, OEE. ERP carries planning, inventory, purchasing and costing. ISA-95 (IEC 62264) is the widely used reference for defining the information exchange and responsibility boundaries between these layers. In most scenarios, work order and material information flows from ERP to production management, and production confirmations flow from production management to ERP; if the plant’s data ownership is different, we define the interface accordingly. In most designs, the control network is not opened directly to business systems; data passes through a middleware layer with defined rules and error handling, and through the controlled transition zone between OT and IT (OT DMZ). We connect to ERP systems such as SAP through the interfaces and authorisation model published by the ERP side.

Technical scope

Process and data flow analysis

In which system do work order, material, production confirmation, downtime and scrap information originate, and who owns them? This is clarified first.

Interface definitions

Message contents, triggers (event-based / periodic) and the record ID that distinguishes each message. What happens when the same document arrives a second time, where messages wait during a temporary access outage, and the reconciliation record comparing the two systems’ records are defined in the interface document approved by both sides.

Middleware and OT DMZ design

Data transformation, queuing and logging between the control network and business systems; a security boundary that allows only the necessary connections.

SCADA/HMI data access

Options for getting data from the existing SCADA or historian; licence and performance impact are assessed in advance.

Testing and parallel running

End-to-end business scenarios in a test environment; running in parallel with the manual process for a set period in production and comparing the results.

Operating model

Interface monitoring, error queue management and a responsibility matrix stating who intervenes for which error.

Layers and responsibility boundaries

LayerTypical systemResponsibility of this layer
Enterprise (business)SAP and other ERP systemsPlanning, inventory, costing; work order and material master data
Production managementMES, quality and traceability systemsExecuting work orders, production confirmation, downtime and scrap recording
Transition zoneOT DMZ, middleware, historian replicaTransformation, queuing, logging and security boundary
Supervision and monitoringSCADA, HMI, historianProcess monitoring, alarms and operator control
Control and fieldPLC, remote I/O, drivesReal-time control and safety functions

The layer split is a general framework adapted from ISA-95 and common reference architectures.

Prerequisites: what we need to get started

We list any gaps together in the first meeting and complete them during the survey.

  • List and versions of existing SCADA/HMI, MES and ERP systems
  • A person or consultant who can do interface development/authorisation on the ERP side
  • The opportunity to work with production, planning and quality process owners
  • A test environment or a company code/plant set aside for testing
  • IT security policies and network transit rules

Deliverables

Process and data flow map

Approved interface definition document

Middleware and OT DMZ architecture document

List of security and network transit rules

Test scenarios and parallel running report

Monitoring, error management and responsibility matrix

Sample scenario

Representative scenario: production confirmations entered in bulk at the end of the shift

Production quantities are entered into the ERP manually at the end of the shift; inventory and reality on the shop floor drift a little further apart every day. The work order is taken from the ERP. PLC counters and downtime information are collected in the middleware and matched to the work order; production confirmations are sent to the ERP interface at defined intervals. Messages that cannot be processed go to an error queue and the owner is notified. Each confirmation carries a record ID; a resent confirmation is not processed twice. Manual entry continues in parallel for a while and the two sources are compared.

This is a representative project flow; it is not a completed customer reference.

Service summary

Related services

IT/OT Integration Consulting

In a new machine, MES or energy monitoring project, we define who owns the network, the data and the access rules.

View details →

Scope limit

ERP or MES product consulting, licensing and customisations inside these systems are not in our scope; for these, we work together with your product consultant. The field, network, middleware and security side of the integration is ours. If order and enterprise application data is also to be connected once production data reaches the ERP, that side is handled by our enterprise ERP and API integration service.

Project approach

How do we proceed?

No step that could affect production is carried out until the maintenance window, configuration backup and rollback plan are clear.

01 / STAGE

Process analysis

Data flow, ownership and timing are mapped.

02 / STAGE

Interface design

Message and error behaviour is approved by both sides.

03 / STAGE

Architecture

Middleware, OT DMZ and security rules are defined.

04 / STAGE

Test

Scenario tests and parallel running are carried out.

STAGE 05

Operation

Monitoring, the error queue and the responsibility matrix are put into operation.

Frequently asked questions

Questions about SCADA, MES and ERP Connections

01

Should we connect the PLC directly to the ERP?

In most scenarios, no. We prefer a manageable middleware layer with audited security; this keeps the responsibilities and maintenance windows of the control network and business applications separate.

02

Can ERP integration be done without an MES?

For simple production confirmations, yes; the middleware can take on some basic MES functions (counter collection, work order matching). If traceability, quality and detailed downtime management are needed, the need for an MES is assessed separately.

03

Do you do the SAP integration?

Development and authorisation inside SAP are the job of the SAP side. We write the interface definition together, build the field and middleware side, and run the test from start to finish.

04

Why is an OT DMZ needed?

An OT DMZ is a transition zone that prevents business systems from accessing the control network directly. Data changes hands here; a failure or update on the IT side is not passed directly to the production network.

Technical survey

Let's plan a technical survey for SCADA, MES and ERP connections

Briefly describe the line, the PLC and network equipment you use and the problem you want to solve; we will respond with a written proposal covering scope, assumptions and deliverables.