Sales: [email protected] · WhatsApp +86 136 4542 9121 — CE-certified packaging machinery since 2008
Insights

Connected End-of-Line Machines 2026: OPC UA, WMS and MES Integration Without Custom Headaches

Technical Knowledge

Oct 30, 2026 SunAura Engineering Team

A decade ago an end-of-line machine was a black box. It started, stopped, built a pallet and wrapped it, and the operator read the counter on the HMI. Today the palletizer, the stretch wrapper and the conveyor are expected to know which order is on the line, report the count to the warehouse system, raise an alarm that reaches maintenance on a phone, and hand the finished pallet to the WMS for dispatch. That shift is what buyers mean by connected end-of-line. The technology is no longer exotic; the risk is in writing the integration spec loosely and paying for a custom one-off project that never finishes. This post sets out what OPC UA, WMS and MES integration actually require in 2026, and what a buyer should pin in writing before order.

Why end-of-line machines now talk upstream

Three pressures pushed the connection upstream. First, orders fragmented: a pallet is no longer a pallet of one SKU, but a build-to-order load for a specific customer, so the palletizer and wrapper need to know the order number, the layer pattern and the destination as the case arrives. Second, warehouses need real-time counts — how many pallets are built, which are ready, which are waiting for film — to drive dispatch and truck loading. Third, maintenance moved to condition-based monitoring: a wrapper whose film-force curve drifts should raise a ticket before it produces a loose load, not after.

The connection therefore runs in both directions: order release and recipe selection flow down to the machine; status, counts, alarms and cycle data flow up to the WMS, MES and historian. This is the same integration discipline described in our end-of-line integration guide, and it is why the machine you buy in 2026 is less a standalone device and more a node on the plant network.

Hardwired I/O, classic fieldbus and OPC UA, compared

Three generations of connection sit next to each other on modern floors, and buyers should know which one they are paying for. Hardwired I/O runs a separate wire per signal — start, stop, fault, pallet-ready — between the palletizer and the upstream PLC. It is simple, deterministic and famously expensive to change: every new signal is a new cable, a new terminal block and a new engineering trip. Classic fieldbus (PROFIBUS, DeviceNet, and later PROFINET/EtherNet/IP at the field level) puts many signals on one cable and lets drives, sensors and robots share a network. It is the workhorse of modern end-of-line cells. OPC UA sits above the fieldbus: a service-oriented protocol that exposes machine data as structured objects (order, product, cell, alarm) rather than as a pile of bits, so an MES or WMS can read a standard “palletizer” information model without a bespoke driver.

OPC UA is not a replacement for PROFINET or EtherNet/IP on the factory floor; it is the layer those networks carry upward to business systems. ISO publishes the OPC UA companion specifications and the wider industrial communication standards that make this layering work, and PMMI continues to publish guidance on how packaging machinery suppliers and plant IT should agree on the signals they exchange. The practical effect for a buyer is that a machine which exposes a clean OPC UA interface can be connected to any modern WMS or MES without a custom driver, which is where the “no custom headaches” promise lives.

Interface Flexibility Typical cost Commissioning Maintenance
Hardwired I/O Low; one wire per signal; changes need re-wiring Low parts cost, high engineering and cabinet cost Straightforward but slow per point Fault-finding in a large marshalling cabinet is painful
Classic fieldbus (PROFINET / EtherNet/IP) Good; devices share one cable; new device = one node Medium; needs managed switches and network design Familiar to automation teams; device GSD/EDS files Diagnostics available per node; standard skill set
OPC UA (upper layer) High; structured objects; WMS/MES reads a standard information model Medium; software license and engineering on the machine controller Needs a named signal list and test plan up front; otherwise delays Versioned data model; alarms and events logged centrally

What a WMS actually expects from a palletizer and wrapper

Vendors who say “we have OPC UA” are not finished. The buyer has to spell out the data points, because WMS teams build their integration against a defined list. The minimum set is: cell state (idle, running, paused, faulted), count of completed pallets this shift, current order or recipe number, layer count and target, alarm code and text, pallet-ready handshake to the outfeed conveyor, and wrapper status including film reel low and cut/reset events. Add to that timestamps, energy usage for the wrapper heater and a cycle-time histogram if the MES does OEE.

What kills projects is the opposite: a signal list that arrives after the cabinet is built, alarms that the machine vendor codes in-house and the WMS cannot decode, and an HMI that shows the fault in Chinese while the MES logs a generic “machine stopped.” The signal list must be a delivered document — signed off by both the machine builder and the plant IT — before the cabinet is wired. This is the discipline in our RFP and specification template, the same checklist we publish for writing a packaging machine RFP.

Avoiding the one-off custom integration

Most integration pain comes from treating the connection as a software project after the machine ships. The fix is procedural, not technical. Use a published companion specification or a named standard information model for the machine class rather than a bespoke object tree. Fix the network topology on the drawings: which switch, which VLAN, which firewall rule between the cell and the office network, which device gets which IP. Require the vendor to export the HMI alarm list in a machine-readable file (CSV or JSON), not as a screenshot. Ask for a factory acceptance test that includes a simulated WMS exchanging the agreed signals, so the integration is proven before the crate leaves the factory.

Statista and Smithers both track the wider move toward connected warehouse and packaging equipment as a steady, technology-led trend rather than a spike, and the OECD and European Commission have published guidance on digital maturity and cybersecurity for industrial sites. The direction is clear; the buyer’s job is to lock the interface language before purchase.

Cybersecurity basics for the shop-floor network

A connected end-of-line machine is now a node on a network, and the old “air-gap” assumption no longer holds. The baseline is not exotic: place the cell on a separate VLAN or industrial DMZ, allow outbound connections only to named historians and MES servers, disable unused USB and remote-service ports on the controller, keep vendor remote access behind a managed VPN with named accounts, and log who connects to the machine. Standards referenced by the European Commission and ISO for industrial automation security set the baseline; the plant IT team should treat the palletizer and wrapper as production IT assets, not as isolated devices. A short clause in the order — “vendor to provide a network topology drawing, a VLAN assignment list and a remote-access procedure” — prevents the afterthought that ends in a months-long security review.

What This Means for Your Buying Decision

Put five lines in the order, not a wishlist. (1) Named protocol: OPC UA over the agreed fieldbus, with the information model version specified. (2) A signed signal list: status, counts, alarms, order number, film/reel status, timestamps. (3) Network topology: VLAN, switch, firewall rule, IP range, remote-access VPN. (4) HMI alarm export in machine-readable form, in English. (5) A factory acceptance test that exchanges those signals with a simulated WMS. If the vendor pushes back on any of the five, that pushback is itself the data point you need. A machine that cannot accept a written signal list is a machine that will absorb your engineering budget for a year after installation.

The connected palletizer and wrapper also fit the broader picture of why manual stations are disappearing across warehouses, a shift we track in the 2026 end-of-line automation trends. Safety and compliance obligations still apply on the connected cell, and the integration spec should reference the same standards a standalone machine does — see our notes on CE, UL and ISO packaging machine safety. Once the line runs, the data that OPC UA exposes is what makes preventive maintenance real rather than a calendar: the signals drive the routine checks in our preventive maintenance checklist, so a drift on the wrapper film tension or a stalled conveyor segment becomes a ticket instead of a fault call.

Frequently asked questions

Is OPC UA a replacement for PROFINET or EtherNet/IP?

No. OPC UA sits above the fieldbus and exposes structured machine data upward to the WMS, MES or historian. PROFINET and EtherNet/IP still do the deterministic motion and I/O work on the cell. A modern connected machine uses both: fieldbus on the floor, OPC UA to the business system.

What is the minimum data list a buyer should ask for?

Cell state (idle, running, paused, faulted), completed pallet count, current order or recipe number, target and actual layer count, alarm code and text, pallet-ready handshake, and wrapper status including film-reel low and reset events. Add timestamps and cycle-time data if you run OEE.

Can one custom integration be avoided if the machine already has OPC UA?

Mostly, if the vendor uses a standard information model and delivers a signed signal list before cabinet build. The remaining custom work is on the WMS side and is small compared with a bespoke driver. The failure mode is when “we have OPC UA” means a private, undocumented object tree that no WMS can read without a consultant.

Do I need to put the palletizer on the office network?

No. Best practice is a separate VLAN or industrial DMZ for the machine, with outbound connections only to named MES and historian servers, a managed VPN for vendor remote access, and unused USB and service ports disabled. Treat the machine as a production IT asset, not as an isolated device.

When in the project should the signal list be agreed?

Before the cabinet is wired, and it should be signed off by both the machine builder and your plant IT. Require it as a contract deliverable, and include a factory acceptance test that exchanges those signals with a simulated WMS so the integration is proven before the machine ships.

James Wang
James Wang Technical Director — End-of-Line Systems
18+ years in packaging machinery engineering and project delivery

James oversees the engineering architecture for full end-of-line projects: defining machine sequence, conveyor layout, line balance, footprint and expansion capacity before individual machines are ordered. He reviews customer specifications, production rates and facility constraints, and signs off on the engineering drawings and acceptance tests. His articles take the system-level view a procurement manager needs.

System Design Project Engineering End-of-Line Layout