Mittelstand manufacturers and machine builders often have a backlog of integration work: connecting machines to an MES, exposing PLC data through OPC UA, building dashboards and traceability on top. The assumption is that this work must happen on the shop floor. In reality, most of the effort sits in information modelling, server and client software, data pipelines and testing, all of which can be done remotely if the interfaces are specified precisely and simulated faithfully. Commissioning, PLC changes on running lines and safety-related logic remain on site. This note describes how to draw the line and what artefacts make the split work.

Why the backlog keeps growing

The integration backlog is a direct consequence of how far digitalisation has spread on the shop floor. Bitkom's 2026 Industrie 4.0 study of 555 German manufacturers with 100 or more employees found that 97 percent use at least one Industrie 4.0 application, 45 percent already use digital twins and 40 percent use AI in production. Each of these depends on clean machine data, which is exactly what OPC UA and MES integration deliver. The people to build it are scarce. The VDMA counted slightly more than 1 million employees in German mechanical engineering in September 2025, including 190,000 engineers, after employment fell 2.4 percent within a year, and Bitkom counted 79,000 unfilled IT positions across the German economy in 2026, with 97 percent of companies reporting difficulty filling IT roles. Meanwhile the number of endpoints keeps rising: the IFR World Robotics 2025 report puts Germany's robot density at 449 robots per 10,000 manufacturing employees, the fourth highest worldwide.

Map the work to the automation pyramid

The ISA-95 model (IEC 62264) is a practical way to sort integration tasks. Levels 0 to 2 are the physical process, sensors, actuators and control. Level 3 is manufacturing operations (MES). Level 4 is business planning (ERP).

TaskISA-95 levelRemote suitability
ERP to MES order and material interfaces3 to 4High
MES connectors, traceability, OEE calculation3High
OPC UA information model design2 to 3High
OPC UA server on an edge gateway2High, with simulated PLC
OPC UA client and data pipeline to historian or cloud2 to 3High
PLC program changes (IEC 61131-3)1 to 2Medium. Development in simulation, deployment on site
Commissioning and line integration0 to 2Low. On site
Safety PLC logic1Not recommended for external remote work

The interface contract comes first

Remote integration fails when the interface is described in a spreadsheet and interpreted differently by each side. OPC UA offers a better artefact: the information model, exported as a NodeSet2 XML file. It defines object types, variables, data types, methods and their relationships. Where an OPC UA companion specification exists for your machine type, start from it rather than inventing a model, because customers and MES vendors increasingly expect them.

Treat the NodeSet as a versioned contract. Changes go through review, the version is tagged, and both the server implementation and the client code are tested against the same file. This single practice removes most of the ambiguity that otherwise consumes on-site time.

Simulate the endpoints

A remote team needs something to talk to. Three layers of simulation are useful:

  • Mock OPC UA server generated from the NodeSet, with scripted value changes and events. Open stacks such as open62541 or the OPC Foundation .NET Standard stack make this straightforward.
  • Soft PLC or PLC simulation, for example a CODESYS soft PLC or the vendor simulation for your controller family, running the real PLC program against simulated I/O. This allows testing of the actual data flow from PLC variables to OPC UA nodes.
  • Replay of recorded production data, captured from a real line over a representative period and replayed through the mock server. This exposes edge cases that scripted tests miss: counter wraparounds, quality flags, bursts during changeover.

Security is part of the specification

OPC UA has a well-defined security model: application instance certificates, security policies and modes (None, Sign, SignAndEncrypt), and user authentication. In many plants, servers still run with security mode None because certificate management was never set up. A remote team building new servers or clients should implement SignAndEncrypt by default and deliver a documented certificate management procedure (trust lists, renewal, revocation). If your customers ask for IEC 62443 alignment, this is one of the first places they will look.

Details that cause most rework

Three details account for a large share of integration rework, and all of them can be settled remotely before anyone travels to the plant.

  • Timestamps. OPC UA distinguishes source timestamp and server timestamp. Decide which one the MES uses, and make sure PLC, gateway and MES clocks are synchronised.
  • Engineering units and scaling. Raw PLC values often need scaling. Put units and ranges into the information model, not into undocumented client code.
  • Status codes. Values with bad or uncertain quality must be handled explicitly. Silent conversion of a bad value into zero is a classic source of wrong OEE figures.

The on-site windows

On-site work becomes a planned event rather than an open-ended presence. A typical sequence:

  1. Remote development against NodeSet, mock server and soft PLC, with automated tests in CI.
  2. Factory acceptance test (FAT) on a test bench or at the machine builder's site, with the remote team connected through a controlled session.
  3. Site acceptance test (SAT) at the plant, executed by your automation engineer or the operator's team, using a test protocol the remote team prepared.
  4. Hypercare for an agreed period, with log access and a defined escalation path.

The remote team writes the FAT and SAT protocols. That is a deliberate choice: the people who built the integration know which edge cases to test, and a written protocol makes acceptance under a Werkvertrag objective.

Acceptance criteria examples

  • The OPC UA server passes conformance checks for the agreed profile and exposes all nodes defined in NodeSet version x.y.
  • End-to-end latency from PLC variable change to MES record stays below the agreed threshold at the agreed signal rate, measured over a replay of one shift.
  • No data loss over a 24-hour soak test including a simulated network interruption of five minutes, with buffered values delivered in order after reconnect.
  • Certificate renewal procedure executed successfully on the test system.

The thresholds depend on your process and should be agreed per project.

Checklist before starting

  1. Identify whether a companion specification applies to your machine type.
  2. Decide who owns the NodeSet and how changes are approved.
  3. Provide a PLC program export and the controller simulation licence, or a soft PLC equivalent.
  4. Record at least one representative shift of production signals for replay.
  5. Define the OPC UA security policy and certificate handling up front.
  6. Schedule FAT and SAT windows at the start of the project.

Integration work splits well when the interface contract and the simulation exist before the first line of client code. In a niogod™ pod, the Projektleiter coordinates FAT and SAT windows in German with your automation engineers and plant staff, while the engineers in Bangalore build against simulated endpoints under a Werkvertrag with Abnahme per sprint, following our 72-hour protocol. If a line or plant integration is planned for next year, it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights